INVOICE PROCESSING
Three-Way Match Invoice Exceptions to Airtable Review Queue
On each incoming vendor invoice, compares it against the matching purchase order and goods-receipt record.
How it runs
The automated pipeline, trigger to output.
- TriggerInvoice received via webhookHTTP webhook
- ActionFetch matching PO + goods receipt from AirtableAirtable
- LogicCompare qty, price, totals against tolerance
- LogicClassify exception type (price / qty / missing receipt)
- OutputWrite exception row to Airtable review queueAirtable
What it does
Runs the classic accounts-payable three-way match: invoice vs. purchase order vs. goods receipt. When the three agree within tolerance, the invoice is flagged auto-approve. When they don't, it lands in a structured Airtable queue with the exact fields that broke so a finance reviewer can act in seconds instead of hunting across systems.
When to use it
Use this when your AP team manually cross-checks invoices against POs and receiving records before payment, and exceptions get lost in email. It gives you a single triage board instead of a shared inbox.
How it works
- 1A new invoice arrives via webhook (from your OCR or e-invoice intake).
- 2The flow pulls the referenced PO and the goods-receipt line items from Airtable.
- 3It compares quantity, unit price, and line totals against tolerance thresholds.
- 4A logic branch separates clean matches from exceptions and tags the mismatch type (price, quantity, or missing receipt).
- 5Matches are stamped approved; exceptions are written as a new row in the Airtable Exception Queue with the variance detail and a suggested owner.
Set it up
What you configure once, before turning it on.
- 1Connect HTTP webhookTrigger any URL on agent actions.
- 2Connect AirtableBases, tables, views, automations.
- 3Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 4Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 5Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Invoice Processing workflows
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.
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.
AI agent that investigates suspected duplicate invoices
When a new invoice can't be cleared by exact-match rules, an AI agent reviews paid history for near-duplicates (split bills, renamed vendors, rounding) and recommends pay, hold…
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.
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.
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.
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.