INVOICE PROCESSING
Weekly Three-Way Match Exception Digest from the Data Warehouse
Each week, runs a Snowflake query over all unresolved PO-receipt-invoice exceptions, ranks them by aged dollar value and vendor.
How it runs
The automated pipeline, trigger to output.
- TriggerWeekly schedule fires
- ActionQuery open exceptions in SnowflakeSnowflake
- LogicAggregate and rank by exposure and age
- OutputEmail digest to AP leadershipOutlook
- OutputPost summary to Teams finance channelMicrosoft Teams
What it does
Gives AP managers a standing view of where matching keeps breaking. Instead of one alert per invoice, it aggregates every unresolved exception in the warehouse into a single weekly report ranked by money at risk and by which vendors cause the most friction.
When to use it
Use this when your reconciled data already lands in Snowflake and leadership wants trend-level visibility: aging exceptions, repeat-offender suppliers, and total dollars stuck in dispute, rather than line-by-line noise.
How it works
- 1A weekly schedule starts the run.
- 2Snowflake returns all open exceptions with variance type, dollar amount, age in days, and vendor.
- 3A logic step aggregates by vendor and aging bucket, ranks by total exposure, and isolates exceptions older than the SLA.
- 4The digest is composed with the top vendors, total dollars at risk, and the count breaching SLA.
- 5The report is emailed to the AP leadership distribution via Outlook.
- 6The same summary is posted to a Microsoft Teams finance channel for visibility.
Set it up
What you configure once, before turning it on.
- 1Connect SnowflakeWarehouses, queries, shares.
- 2Connect OutlookMail, calendar, contacts.
- 3Connect Microsoft TeamsChannels, chats, 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
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.