INVOICE PROCESSING
Screen incoming invoices for duplicates and fraud signals
On each emailed invoice, extracts vendor, invoice number, and bank details, checks Postgres for prior payments and changed payee accounts.
How it runs
The automated pipeline, trigger to output.
- TriggerInvoice received in inboxGmail
- ActionOCR vendor, number, amount, bank detailsOpenAI
- ActionLook up prior payments and verified bank accountPostgres
- LogicDetect duplicate number or changed payee account
- ActionQuarantine suspect invoicePostgres
- OutputAlert finance-controls channelSlack
What it does
Every inbound invoice is screened before it ever reaches approval. The flow OCRs the document, then checks two risks: a duplicate (same vendor and invoice number already paid) and payment fraud (the vendor's bank details differ from the last known account on file). Either condition quarantines the invoice and raises an alert.
When to use it
Use this as a front-line control when you process high volumes of vendor invoices and worry about double-payments or business-email-compromise scams that swap in attacker bank accounts.
How it works
- 1A vendor invoice arrives in the inbox and triggers the run.
- 2OCR pulls vendor name, invoice number, amount, and bank/routing details.
- 3Postgres is queried for any prior invoice with the same vendor and number, plus the vendor's last verified bank account.
- 4A risk check flags exact-duplicate numbers and any mismatch in payee bank details.
- 5Suspect invoices are written as quarantined so they cannot be paid.
- 6A detailed fraud/duplicate alert is sent to the AP and finance-controls channel.
Set it up
What you configure once, before turning it on.
- 1Connect GmailRead, draft, send, label.
- 2Connect OpenAIModels, embeddings, files.
- 3Connect PostgresAny Postgres URL — query, write, migrate.
- 4Connect SlackChannels, DMs, threads, mentions.
- 5Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 6Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 7Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Invoice Processing workflows
Dollar-Threshold Match Variance Escalation Chain
Routes three-way match variances up an approval ladder by dollar size — small ones to the line manager, large ones to the controller.
Front vendor invoice to Airtable approval packet with line-item parse
Watches a Front inbox for vendor invoice emails, extracts header and line-item data from the body and PDF attachment, and writes a structured.
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.
Three-Way Match Exception Router by Variance Type
When a new invoice fails three-way match against its PO and receiving record, this workflow classifies the mismatch (price, quantity, or missing receipt) and routes each variance…
Route parsed Front invoices to the right Slack approver by amount
Parses an incoming Front vendor invoice and posts an interactive Slack approval card to the approver whose spending threshold matches the invoice total.
Three-way match Front invoices against purchase orders in Postgres
Parses a Front vendor invoice and runs a three-way match against the matching purchase order and receipt records in Postgres, posting pass or exception results to Slack.
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.