INVOICE PROCESSING
Reconcile Stripe foreign-currency payouts against invoiced base-currency totals
On each Stripe payout, converts the settled foreign-currency amount to your base currency and compares it to the original invoice total.
How it runs
The automated pipeline, trigger to output.
- TriggerStripe payout settled in foreign currencyStripe
- ActionLook up matching invoice and booked totalPostgres
- LogicConvert payout, compute FX gain/loss vs booked
- ActionWrite reconciliation record to PostgresPostgres
- OutputAlert finance in Slack if variance over thresholdSlack
What it does
When Stripe settles a payout in a foreign currency, this workflow normalizes the settled amount to your reporting currency, matches it to the originating invoice, and records the FX gain or loss so your pre-ledger entries reflect actual realized rates rather than booked estimates.
When to use it
Use it when you collect in multiple currencies through Stripe and need realized FX variance captured before the entry hits your general ledger. It eliminates spreadsheet reconciliation of payout rates against invoice booking rates.
How it works
- 1A Stripe payout event triggers the workflow with the settled currency and amount.
- 2The matching invoice and its originally booked base-currency total are pulled from Postgres.
- 3A logic step converts the settled amount at the payout rate and computes FX gain or loss versus the booked total.
- 4The reconciliation record, including both rates and the variance, is written to Postgres for ledger import.
- 5A Slack message alerts finance when variance exceeds a configured threshold.
Set it up
What you configure once, before turning it on.
- 1Connect StripeCustomers, subscriptions, payments.
- 2Connect PostgresAny Postgres URL — query, write, migrate.
- 3Connect SlackChannels, DMs, threads, mentions.
- 4Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 5Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 6Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Invoice Processing workflows
Catch duplicate invoices as they hit your AP inbox
Watches your accounts-payable Gmail inbox for incoming invoice emails, fingerprints each one, and routes likely duplicates to a review label instead of into the approval queue.
Gate invoice approvals on a duplicate cross-check
When an approver clicks Approve in your AP system, a webhook re-validates the invoice against paid history in Postgres and Stripe charges.
Nightly audit that flags duplicate payments already made
Runs every night to scan the last 90 days of Stripe payments against your Postgres invoice ledger.
Block duplicate Stripe payouts before they send
When a new vendor invoice is queued for payment in Stripe, cross-check it against your paid-invoice history in Postgres and halt any payout that matches an already-paid invoice.
Agent that codes Front invoices to GL accounts and drafts a bill
An agent reads each Front vendor invoice, assigns GL account codes per line item using your chart of accounts and past coding history.
Detect duplicate Front invoices and archive originals to S3
Parses each Front vendor invoice, checks it against a history table for duplicates, archives the source PDF to S3 with a normalized key, and alerts AP when a duplicate is caught.
Run it inside a business
This workflow drops into a full company template. Import the org, and this is one of the playbooks its agents run.
Run this workflow in your colony.
14-day trial. No DevOps. No Sales call. Provisioned in under a minute.