INVOICE PROCESSING
Hold Mismatched Invoices and Alert AP in Slack on Arrival
When a new invoice posts via webhook, instantly matches it to its PO and receipt.
How it runs
The automated pipeline, trigger to output.
- TriggerInvoice posted webhookHTTP webhook
- ActionLook up PO and receipt linesPostgres
- LogicMatch qty and price within tolerance
- ActionMark invoice on-hold if mismatchedPostgres
- OutputPost variance alert to AP Slack channelSlack
What it does
Intercepts each invoice the moment it enters the system, runs the PO-receipt-invoice match in real time, and stops any mismatched invoice from flowing to payment until a human approves it. The exception lands in Slack with the exact numbers in dispute.
When to use it
Use this when invoices arrive continuously from an OCR or supplier portal and you cannot wait for a nightly batch. It prevents an unmatched invoice from ever reaching the pay run.
How it works
- 1An inbound webhook fires when a new invoice is posted.
- 2Postgres is queried for the referenced PO line and its receipt line.
- 3A logic step checks for missing PO, missing receipt, quantity over-billing, or price above PO tolerance.
- 4If the invoice matches cleanly, it is released and the run ends silently.
- 5If it fails, Postgres marks the invoice status on-hold so it cannot be paid.
- 6A Slack message posts to the AP channel naming the vendor, PO number, variance type, and dollar gap, with the values laid out for quick sign-off.
Set it up
What you configure once, before turning it on.
- 1Connect HTTP webhookTrigger any URL on agent actions.
- 2Connect PostgresAny Postgres URL — query, write, migrate.
- 3Connect SlackChannels, DMs, threads, mentions.
- 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.