INVOICE PROCESSING
Three-Way Match Invoice Router with Exception Approval
Matches each incoming vendor invoice against its open purchase order and goods receipt in Postgres, auto-approves clean matches.
How it runs
The automated pipeline, trigger to output.
- TriggerNew invoice row inserted in PostgresPostgres
- ActionFetch matching PO and goods receiptPostgres
- LogicCompare price, quantity, and total to tolerance
- ActionMark clean matches approved for paymentPostgres
- LogicClassify exception type for mismatches
- OutputPost exception to Slack approval threadSlack
What it does
Runs the core three-way match. For every new invoice it pulls the referenced purchase order and the goods-receipt record from your AP database, compares line-item price, quantity, and total against tolerance thresholds, and decides whether the invoice can pay automatically or needs a human.
When to use it
When your AP team manually cross-checks invoices against POs and receiving records before approving payment, and clean invoices are slowing down because they sit in the same queue as the genuine exceptions.
How it works
- 1A new invoice row lands in the Postgres `invoices` table and fires the trigger.
- 2The flow looks up the matching purchase order and goods receipt by PO number.
- 3A logic step compares unit price, quantity, and extended total against configured tolerance (e.g. +/- 2% price, exact qty).
- 4Clean matches are marked `approved` in Postgres for the payment run.
- 5Any mismatch is classified by exception type (price variance, quantity variance, missing receipt).
- 6Exceptions post to a Slack approval thread with the variance detail and Approve/Reject buttons for the AP lead.
Set it up
What you configure once, before turning it on.
- 1Connect PostgresAny Postgres URL — query, write, migrate.
- 2Connect SlackChannels, DMs, threads, mentions.
- 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.