INVOICE PROCESSING
Monthly recurring-vendor spend-drift digest for finance review
On the first of each month, aggregates the prior month's vendor invoices from BigQuery, ranks recurring vendors by how far their spend drifted from their trailing average.
How it runs
The automated pipeline, trigger to output.
- TriggerSchedule fires on the first of the month
- ActionAggregate prior-month vendor spend in BigQueryBigQuery
- LogicCompute and rank percent drift per vendor
- ActionPublish ranked drift report to NotionNotion
- OutputPost digest link and top movers to SlackSlack
What it does
Gives finance a once-a-month view of which recurring vendors are quietly costing more than they used to. Instead of alerting on single invoices, it rolls up a full month and ranks vendors by spend drift, surfacing slow creep that per-invoice checks miss.
When to use it
Use this for the monthly close or vendor review meeting when you want a single artifact showing where recurring spend is trending up and which vendors deserve a renegotiation conversation. Complements real-time anomaly catchers with a strategic rollup.
How it works
- 1A schedule fires on the first of each month.
- 2The flow queries BigQuery to total each recurring vendor's spend for the prior month and their trailing-6-month average.
- 3A logic step computes percent drift and sorts vendors from largest increase to largest decrease.
- 4A formatted drift table is published as a new Notion page in the finance workspace.
- 5A Slack message links the report and calls out the top three vendors by upward drift.
Set it up
What you configure once, before turning it on.
- 1Connect BigQueryDatasets, queries, schemas.
- 2Connect NotionPages, databases, comments.
- 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.