INVOICE PROCESSING
Compare Emailed Vendor Invoice PDFs Against the Stored Baseline
When a vendor invoice PDF lands in Gmail, this extracts its line items, compares them to the vendor's last stored invoice in Postgres.
How it runs
The automated pipeline, trigger to output.
- TriggerNew vendor invoice PDF in Gmail inboxGmail
- LogicExtract line items and quantities from PDF
- ActionLoad vendor baseline invoice from PostgresPostgres
- LogicDiff parsed invoice against baseline; branch on changes
- OutputPost flagged differences to AP Slack channelSlack
What it does
It watches a billing inbox for incoming vendor invoice PDFs, parses the line items and quantities out of each one, and diffs them against the most recent invoice on file for that vendor in Postgres. Differences in items, rates, or counts are flagged before the bill is entered for payment.
When to use it
Use this when vendors bill by emailed PDF rather than through a portal or API, and you want to catch creep at the moment of receipt instead of after manual entry. It removes the need for someone to eyeball each PDF against last month's.
How it works
- 1A new email with a PDF attachment arrives in the monitored Gmail inbox.
- 2The flow extracts line items, quantities, and totals from the PDF.
- 3A Postgres query loads the vendor's last stored invoice as the baseline.
- 4A diff step compares the parsed invoice to the baseline.
- 5A branch proceeds only when meaningful changes are found.
- 6A Slack message posts the flagged differences to the AP channel for review.
Set it up
What you configure once, before turning it on.
- 1Connect GmailRead, draft, send, label.
- 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.