INVOICE PROCESSING
Flag recurring-vendor invoices that spike above their billing baseline
Watches incoming invoice emails from recurring vendors, compares each amount against that vendor's historical average.
How it runs
The automated pipeline, trigger to output.
- TriggerNew invoice email in AP inboxOutlook
- ActionParse vendor and invoice total
- ActionFetch vendor baseline from historyBigQuery
- LogicAmount exceeds baseline band?
- OutputPost spike alert to finance channelSlack
What it does
Monitors invoices arriving from your known recurring vendors and catches the ones that cost noticeably more than usual before they get paid. It compares each new invoice against a rolling baseline of that vendor's prior charges and raises a flag when the amount jumps past a tolerance threshold.
When to use it
Use this when you have dozens of monthly SaaS, utility, or service vendors and a surprise overage (extra seats, usage tiers, a price increase) routinely slips through to payment. It turns "we found out at month-end" into a same-day alert.
How it works
- 1An invoice email lands in the shared AP inbox in Outlook and triggers the run.
- 2The vendor name and total are parsed from the message and attachment.
- 3The vendor's trailing 6-invoice average and standard band are pulled from the BigQuery invoice history table.
- 4A branch checks whether the new amount exceeds the baseline by more than the configured percentage.
- 5If it does, a Slack alert fires to the finance channel with the vendor, the new amount, the baseline, and the delta so an approver can review before paying.
Set it up
What you configure once, before turning it on.
- 1Connect OutlookMail, calendar, contacts.
- 2Connect BigQueryDatasets, queries, schemas.
- 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.