INVOICE PROCESSING
Exception-to-Payment-Hold and Stripe Reconciliation
When a three-way match exception is unresolved, places a payment hold and pauses the related Stripe payout, then auto-releases it once the exception is approved and reconciled.
How it runs
The automated pipeline, trigger to output.
- TriggerScheduled read of exception invoices and statusAirtable
- LogicSplit into still-open vs newly approved exceptions
- ActionPause Stripe payout for unresolved exceptionsStripe
- ActionRelease Stripe payout for approved exceptionsStripe
- OutputWrite reconciliation results and notify finance in SlackSlack
What it does
Connects match exceptions directly to money movement. If an invoice fails three-way match and isn't resolved in time, the workflow places a hold and pauses the corresponding Stripe payout so an unverified invoice never gets paid. When the exception is later approved, it releases the hold and confirms the payout, keeping AP and treasury in sync.
When to use it
Use this when unresolved invoice exceptions risk being paid anyway because payment runs on a separate schedule. It makes the hold automatic and reversible rather than a manual stop-payment scramble.
How it works
- 1A scheduled run reads exception invoices from Airtable and checks their resolution status (trigger).
- 2A logic step splits records into still-open exceptions and newly approved ones.
- 3For still-open exceptions past the cutoff, it pauses the linked Stripe payout and flags the invoice On Hold.
- 4For newly approved exceptions, it releases the corresponding Stripe payout.
- 5The reconciliation result and current hold list are written back to Airtable and posted to the finance Slack channel.
Set it up
What you configure once, before turning it on.
- 1Connect AirtableBases, tables, views, automations.
- 2Connect StripeCustomers, subscriptions, payments.
- 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.