INVOICE PROCESSING
Block duplicate invoices from a Dropbox folder against a BigQuery ledger
Watches a shared Dropbox vendor folder for new invoices, fingerprints each one against the BigQuery payments ledger.
How it runs
The automated pipeline, trigger to output.
- TriggerNew invoice file in Dropbox vendor folderDropbox
- ActionParse invoice and compute fingerprint
- ActionQuery BigQuery payments ledger for a matchBigQuery
- LogicBranch on match and dollar threshold
- ActionPage on-call AP via PagerDuty for high-value duplicatesPagerDuty
- OutputLog match disposition to BigQuery for auditBigQuery
What it does
This workflow guards an AP team that receives invoices through a shared Dropbox folder and reports spend in BigQuery. Each new file is parsed, fingerprinted, and checked against the BigQuery payments ledger. Duplicates above a dollar threshold page on-call AP immediately through PagerDuty, since a high-value double payment is urgent; lower-value matches are logged for the next review cycle.
When to use it
Use it when invoices arrive as files in Dropbox and your source of truth for payments lives in BigQuery. The PagerDuty escalation is for shops where a large duplicate payment is a money-out-the-door incident that can't wait for a daily digest.
How it works
- 1A new file in the Dropbox vendor folder triggers the run.
- 2The invoice is parsed and a fingerprint is computed.
- 3BigQuery is queried for a matching paid invoice.
- 4A logic branch splits on match found and amount threshold.
- 5High-value duplicates trigger a PagerDuty incident to on-call AP.
- 6All matches and the file disposition are written back to BigQuery for audit.
Set it up
What you configure once, before turning it on.
- 1Connect DropboxFiles and folders.
- 2Connect BigQueryDatasets, queries, schemas.
- 3Connect PagerDutyIncidents, on-call, escalations.
- 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.