INVOICE PROCESSING
Duplicate Invoice Scanner Across Vendors (Snowflake)
Scans every new invoice against your full payment history in Snowflake to catch near-identical bills submitted under different vendor names.
How it runs
The automated pipeline, trigger to output.
- TriggerNew invoice staged (webhook)HTTP webhook
- ActionQuery payment history within tolerance windowSnowflake
- LogicScore amount, vendor, and invoice-number similarity
- LogicBranch if match score clears duplicate threshold
- OutputPost side-by-side duplicate alert to AP channelSlack
What it does
Before an invoice reaches approval, this workflow compares it against the full AP history sitting in Snowflake and flags near-duplicates that slip past exact-match checks: same amount and date posted by a renamed vendor, the same invoice number with a transposed digit, or a re-submitted bill from a parent company. Suspected duplicates land in a Slack channel with both records side by side so an AP clerk can confirm or clear before money moves.
When to use it
Use it when vendors get acquired, renamed, or maintain multiple billing entities, and exact-match dedupe in your ERP misses the overlaps. Ideal for high-volume AP teams paying thousands of invoices a month where a single double-payment can run into five figures.
How it works
- 1A new invoice row is inserted into the staging table, firing the webhook.
- 2The workflow queries Snowflake for invoices within a tolerance window of amount, date, and normalized vendor name.
- 3A fuzzy-match step scores each candidate on amount delta, vendor-name similarity, and invoice-number distance.
- 4If the top score clears the duplicate threshold, it branches to the alert path; otherwise it logs a clean result.
- 5A formatted Slack message posts both invoices with the match score and a hold recommendation.
Set it up
What you configure once, before turning it on.
- 1Connect HTTP webhookTrigger any URL on agent actions.
- 2Connect SnowflakeWarehouses, queries, shares.
- 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.