INVOICE PROCESSING
Three-Way Match Exception Routing with Slack Approval
Runs the three-way match on each new invoice and, when quantities or prices fail to reconcile, posts a structured discrepancy card to Slack so an AP approver can release…
How it runs
The automated pipeline, trigger to output.
- TriggerNew invoice row inserted in PostgresPostgres
- ActionFetch linked PO and receipt linesPostgres
- LogicCompute per-line variance vs tolerance
- ActionPost discrepancy card to Slack with approve/rejectSlack
- ActionRelease payment via Stripe on approvalStripe
- OutputRecord override decision and approver in PostgresPostgres
What it does
This workflow catches the invoices that do not cleanly match their PO and receipt, and turns each mismatch into an actionable Slack approval rather than a silent block. The approver sees exactly which lines disagree and decides whether to override and pay.
When to use it
Reach for this when matched invoices already pay automatically elsewhere, but you need a fast, auditable human path for the exceptions: short shipments, price changes, or partial receipts. It keeps held invoices from aging in a queue nobody watches.
How it works
- 1A new invoice row is inserted into Postgres (by your ingestion step or ERP sync), triggering the run.
- 2Postgres returns the linked PO and goods-receipt lines for comparison.
- 3A logic step computes per-line variances and flags any that exceed tolerance.
- 4Clean invoices exit immediately; mismatched ones build a discrepancy summary.
- 5A Slack message posts the variance card with Approve and Reject actions to the AP channel.
- 6On approval, Stripe releases the payment and Postgres records the override, approver, and reason.
Set it up
What you configure once, before turning it on.
- 1Connect PostgresAny Postgres URL — query, write, migrate.
- 2Connect SlackChannels, DMs, threads, mentions.
- 3Connect StripeCustomers, subscriptions, payments.
- 4Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 5Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 6Test, 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.