INVOICE PROCESSING
Triage Three-Way Match Exceptions to Slack with Inline Approvals
On a schedule it pulls open match exceptions, classifies each by failure type, and posts a Slack message to the right approver with the discrepancy details and approve or reject…
How it runs
The automated pipeline, trigger to output.
- TriggerScheduled exception triage sweep
- ActionRead open exceptions with PO/receipt figuresPostgres
- LogicClassify failure type and assign approver
- ActionPost discrepancy with approve/reject in SlackSlack
- OutputUpdate invoice status from decision in PostgresPostgres
What it does
Gives match exceptions a human-in-the-loop workflow. It groups unresolved discrepancies, explains why each failed, routes them to the owning buyer or approver in Slack, and acts on their decision.
When to use it
Use it when your exception queue piles up because nobody knows which discrepancies are theirs. It assigns each exception, surfaces the numbers in context, and lets approvers clear or reject without opening another tool.
How it works
- 1A schedule runs the triage sweep (trigger).
- 2The flow reads open exceptions and their invoice, PO, and receipt figures from Postgres.
- 3A logic step classifies each exception (price variance, quantity short, missing receipt, no PO) and maps it to the responsible approver.
- 4It posts a Slack message to that approver showing the three figure sets, the failure reason, and Approve and Reject actions.
- 5On Approve it marks the invoice Approved in Postgres; on Reject it sets it Disputed with the approver's note.
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.