INVOICE PROCESSING
Three-Way Match Exception Router with Buyer Routing
Compares each incoming invoice against its purchase order and goods receipt in Postgres, auto-approves clean matches, and routes price, quantity, or missing-receipt exceptions…
How it runs
The automated pipeline, trigger to output.
- TriggerNew invoice row inserted in PostgresPostgres
- ActionJoin invoice to PO and goods receiptPostgres
- LogicClassify match vs price/quantity/no-receipt exception
- ActionMark clean matches approved in PostgresPostgres
- OutputEmail exception detail to the PO's buyerGmail
What it does
Runs the classic procurement three-way match: it lines up the invoice, the purchase order it references, and the goods receipt confirming delivery. Invoices that match on vendor, quantity, and unit price within tolerance are flagged auto-approved; anything outside tolerance is classified by exception type and sent to the buyer who owns the PO.
When to use it
Use it when your AP team manually cross-checks POs, receipts, and invoices in spreadsheets before approving payment. It removes the clean-match cases from the human queue and turns the messy ones into a tidy, typed exception list.
How it works
- 1A new invoice row lands in the Postgres `invoices` table and fires the trigger.
- 2The flow joins the invoice to its PO and goods-receipt records by PO number.
- 3A decision step compares vendor, line quantities, and unit prices against configured tolerances, tagging each as match, price variance, quantity variance, or no-receipt.
- 4Clean matches are written back to Postgres as `approved`.
- 5Exceptions are written back as `needs_review` with the variance detail.
- 6An email goes to the buyer named on the PO summarizing the mismatch and the dollar impact.
Set it up
What you configure once, before turning it on.
- 1Connect PostgresAny Postgres URL — query, write, migrate.
- 2Connect GmailRead, draft, send, label.
- 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.