INVOICE PROCESSING
Daily Three-Way Match Exception Digest to Finance
Each morning it aggregates the prior day's unmatched and disputed invoices from Snowflake, builds an aging-ranked digest.
How it runs
The automated pipeline, trigger to output.
- TriggerScheduled morning digest run
- ActionQuery prior-day open exceptionsSnowflake
- LogicGroup by reason, rank by aging and value
- ActionPost digest to finance Slack channelSlack
- OutputEmail summary to AP manager listGmail
What it does
This gives finance one daily picture of every invoice that failed three-way match and is still open. Instead of hunting through a queue, the team gets a ranked digest showing the oldest and highest-dollar exceptions first, with the failure reason on each.
When to use it
Use this alongside any real-time matching flow as the daily safety net and accountability layer. It is for AP managers who need a standing report of what is stuck, how long it has been stuck, and who owns it.
How it works
- 1A scheduled morning run fires.
- 2All open exceptions from the prior day are queried from Snowflake, with PO, receipt status, and failure reason.
- 3The records are grouped by reason and sorted by aging days and dollar value.
- 4A digest is formatted with totals, the worst offenders, and per-owner counts.
- 5The digest posts to the finance Slack channel.
- 6The same summary is emailed to the AP manager distribution list for the record.
Set it up
What you configure once, before turning it on.
- 1Connect SnowflakeWarehouses, queries, shares.
- 2Connect SlackChannels, DMs, threads, mentions.
- 3Connect GmailRead, draft, send, label.
- 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.