INVOICE PROCESSING
Quarterly Recurring-Spend True-Up Auditor
Each quarter, an agent aggregates all recurring vendor payments from Snowflake, compares the trailing run-rate to contracted annual values.
How it runs
The automated pipeline, trigger to output.
- TriggerQuarterly schedule fires
- ActionAggregate recurring payments in SnowflakeSnowflake
- LogicCompare run-rate to contracted annual
- ActionAgent drafts narrative true-up report
- ActionPublish report to NotionNotion
- OutputPost top-drift summary to SlackSlack
What it does
Produces a quarterly true-up: it totals what you actually paid each recurring vendor over the trailing period from your Snowflake finance warehouse, compares that run-rate to the contracted annual commitment, and identifies vendors trending over or under budget. An agent writes a readable narrative report - which vendors drifted, by how much, and the likely cause - publishes it as a Notion page, and posts a short summary with the top drifts to Slack.
When to use it
Use it at quarter-end when finance needs a defensible spend-versus-contract review across the whole vendor book, not just exception alerts. Ideal when the warehouse already holds clean payment data and you want a synthesized document rather than raw numbers.
How it works
- 1A quarterly schedule starts the audit.
- 2The flow queries Snowflake for trailing recurring payments grouped by vendor.
- 3A logic step compares each run-rate against the contracted annual value.
- 4The agent drafts a narrative true-up explaining each material drift.
- 5The report publishes to Notion and a top-drift summary posts to Slack.
Set it up
What you configure once, before turning it on.
- 1Connect SnowflakeWarehouses, queries, shares.
- 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.