INVOICE PROCESSING
Monthly SaaS subscription spend digest with anomaly callouts
On a monthly schedule, aggregates all reconciled subscription charges from Snowflake, compares each vendor's spend to its trailing average.
How it runs
The automated pipeline, trigger to output.
- TriggerMonthly schedule after billing close
- ActionAggregate reconciled charges by vendor in SnowflakeSnowflake
- LogicClassify vendors: new, dropped, anomalous
- OutputPost spend digest to finance SlackSlack
- ActionWrite summary rows to Snowflake reporting tableSnowflake
What it does
Produces a once-a-month rollup of every recurring software charge, grouped by vendor, with month-over-month deltas. It calls out vendors that are new this month, vendors that stopped billing, and any spend that deviated sharply from its norm.
When to use it
Use it when leadership wants a single recurring view of SaaS burn without anyone hand-building a spreadsheet. It is the close-of-month companion to per-charge reconciliation.
How it works
- 1A monthly schedule triggers the workflow after the billing cycle closes.
- 2Snowflake is queried for all reconciled charges in the period, grouped by vendor with trailing averages.
- 3A logic step classifies each vendor as new, dropped, steady, or anomalous based on its delta.
- 4A formatted digest is composed with totals, the anomaly list, and a per-vendor table.
- 5The digest is posted to the finance Slack channel.
- 6The same summary rows are written back to a Snowflake reporting table for trend history.
Set it up
What you configure once, before turning it on.
- 1Connect SnowflakeWarehouses, queries, shares.
- 2Connect SlackChannels, DMs, threads, mentions.
- 3Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 4Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 5Test, 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.