INVOICE PROCESSING
Build a Three-Way Match Exception Queue in Airtable
On a schedule, joins purchase orders, goods receipts, and invoices from Postgres, flags any line where quantity or amount disagrees across the three.
How it runs
The automated pipeline, trigger to output.
- TriggerNightly schedule fires
- ActionQuery joined PO + receipt + invoice linesPostgres
- LogicCompare qty and price across all three
- LogicDrop clean matches, keep exceptions
- OutputUpsert exceptions into Airtable review queueAirtable
What it does
Reconciles every open invoice against its purchase order and the warehouse receipt, then surfaces only the lines that fail the three-way match into a single Airtable queue your AP team works from. Clean matches are auto-cleared and never bother a human.
When to use it
Use this when invoices, POs, and receipts all live in your ERP/Postgres but AP still eyeballs matches in spreadsheets. It replaces the manual reconcile with a nightly job that only escalates true exceptions.
How it works
- 1A nightly schedule fires the run.
- 2Postgres returns each invoice line joined to its PO line and the matching receipt line by PO number and SKU.
- 3A logic step compares ordered vs received vs billed quantity and PO unit price vs invoiced price, classifying each line as matched, price variance, quantity variance, or missing receipt.
- 4Matched lines are dropped; only exceptions continue.
- 5Each exception is upserted into the Airtable AP Review table with the variance type, the three source values, and the dollar delta.
- 6A summary count is written back so the queue shows how many opened today.
Set it up
What you configure once, before turning it on.
- 1Connect PostgresAny Postgres URL — query, write, migrate.
- 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.