INVOICE PROCESSING
Pre-Screen Emailed Invoices for Duplicates (Outlook)
Reads invoices arriving in a shared Outlook inbox, extracts vendor and amount, and checks them against Snowflake history so re-sent or resubmitted bills are caught at intake…
How it runs
The automated pipeline, trigger to output.
- TriggerNew invoice email in shared AP inboxOutlook
- ActionExtract vendor, amount, invoice numberOpenAI
- ActionLook up matching invoice in ledgerSnowflake
- LogicBranch duplicate vs first-seen by confidence
- OutputTag email and surface prior recordOutlook
What it does
Vendors love to re-send invoices: a reminder copy, a corrected PDF, a forward from a second contact. This workflow watches a shared Outlook AP inbox, extracts the vendor, amount, and invoice number from each attachment, and checks that fingerprint against your Snowflake AP ledger. If the same invoice was already received or paid, it tags the email and warns the team before anyone keys it into the ERP.
When to use it
Use it when invoices arrive primarily by email to a shared mailbox and duplicates creep in as reminder copies or multi-recipient forwards. It stops the duplicate at the front door rather than relying on a downstream three-way match.
How it works
- 1A new message in the AP Outlook inbox triggers the workflow.
- 2An extraction step parses vendor, amount, and invoice number from the body and attachment.
- 3The workflow queries Snowflake for any prior invoice matching that fingerprint.
- 4A logic branch decides duplicate versus first-seen based on match confidence.
- 5On a duplicate, it categorizes the Outlook message and posts the prior record so the clerk can archive the re-send.
Set it up
What you configure once, before turning it on.
- 1Connect OutlookMail, calendar, contacts.
- 2Connect SnowflakeWarehouses, queries, shares.
- 3Connect OpenAIModels, embeddings, files.
- 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
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.
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.
AI agent that investigates suspected duplicate invoices
When a new invoice can't be cleared by exact-match rules, an AI agent reviews paid history for near-duplicates (split bills, renamed vendors, rounding) and recommends pay, hold…
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.
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.
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.
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.