INVOICE PROCESSING
Three-Way Match Vendor Invoices and Auto-Approve Clean Matches
When a vendor invoice lands, it pulls the matching purchase order and goods-receipt record, compares quantity and price within tolerance.
How it runs
The automated pipeline, trigger to output.
- TriggerNew invoice row added in CodaCoda
- ActionFetch matching PO and goods-receipt from PostgresPostgres
- LogicCompare qty and price within tolerance
- OutputAuto-approve clean match in CodaCoda
- OutputRoute mismatch to Coda exception queueCoda
What it does
Runs the classic accounts-payable three-way match on every incoming vendor invoice. It reconciles the invoice against its purchase order (PO) and the goods-receipt note (GRN), and only releases invoices for payment when all three agree within a configured tolerance.
When to use it
Use it when your AP team manually cross-checks invoices against POs and receiving records before approving payment. It removes the rote matching work and surfaces only the invoices that genuinely need a human.
How it works
- 1A new invoice row is added to the Coda invoices table (trigger).
- 2The flow queries Postgres for the referenced PO header and lines, then the goods-receipt record for the same PO.
- 3It compares invoiced quantity and unit price against received quantity and PO price, applying a percentage tolerance.
- 4A logic branch splits clean matches from any quantity, price, or missing-receipt mismatch.
- 5Clean matches are written back to Coda with status Approved and a match-evidence note.
- 6Mismatches are inserted into the Coda exception queue with the specific failure reason and the three sets of figures side by side.
Set it up
What you configure once, before turning it on.
- 1Connect CodaDocs, packs, automations.
- 2Connect PostgresAny Postgres URL — query, write, migrate.
- 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
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.