INVOICE PROCESSING
Fingerprint S3-dropped invoices against the paid ledger before approval
Watches an S3 bucket for new invoice PDFs, computes a content fingerprint (vendor + amount + invoice number + date).
How it runs
The automated pipeline, trigger to output.
- TriggerNew invoice PDF lands in S3 intake bucketAWS S3
- ActionParse PDF and extract vendor, number, amount, date
- ActionCompute normalized fingerprint hash
- ActionQuery Postgres paid-ledger for matching fingerprintPostgres
- LogicBranch: duplicate match vs. clean
- OutputQuarantine alert to Slack or write to approval queueSlack
What it does
This workflow stops duplicate payments at the front door. Every invoice that lands in your intake S3 bucket is parsed, normalized, and turned into a deterministic fingerprint. That fingerprint is matched against your already-paid ledger in Postgres. Clean invoices route to approval; suspected duplicates are quarantined and the AP team is alerted in Slack with the matching prior payment.
When to use it
Use it when vendors email or re-upload the same invoice twice, when multiple intake channels feed one bucket, or when you've been bitten by paying the same invoice number under a slightly different file name. It runs entirely before approval, so no human ever sees a confirmed duplicate.
How it works
- 1A new object in the S3 invoice-intake bucket triggers the run.
- 2The PDF is parsed and key fields are extracted (vendor, invoice number, amount, date).
- 3A normalized fingerprint hash is computed from those fields.
- 4Postgres is queried for any paid invoice with a matching fingerprint.
- 5A logic branch splits on match found vs. clean.
- 6Duplicates post to a Slack quarantine channel with the prior payment reference; clean invoices are written back to the pending-approval queue.
Set it up
What you configure once, before turning it on.
- 1Connect AWS S3Buckets, objects, signed URLs.
- 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.