INVOICE PROCESSING
Monthly Invoice Budget-Mapping Coverage Report to Notion
At month-end, computes what share of invoice spend was successfully mapped to GL budget categories versus left uncategorized, broken down by vendor and category.
How it runs
The automated pipeline, trigger to output.
- TriggerMonth-end schedule
- ActionQuery BigQuery for mapped vs. uncategorized totalsBigQuery
- ActionRank vendors and categories by unmapped spendBigQuery
- LogicCompute coverage % and month-over-month delta
- OutputPublish coverage report page in NotionNotion
What it does
Once a month this workflow measures the quality of your invoice-to-budget mapping: total spend, dollars and lines that mapped cleanly, what stayed uncategorized, and the worst offenders by vendor. It assembles the numbers into a formatted Notion page the controller can review at close.
When to use it
Use this for month-end close hygiene and to track whether your mapping rules and agent passes are actually improving coverage over time. It turns the categorized-spend tables into a digestible scorecard without manual SQL.
How it works
- 1A month-end schedule triggers the report.
- 2The flow queries BigQuery for the month's total spend, mapped totals, and uncategorized totals.
- 3A second query ranks vendors and GL categories by unmapped dollars.
- 4A logic step computes coverage percentages and the month-over-month delta.
- 5It composes a structured summary with headline coverage, breakdown tables, and the top gaps.
- 6The report is published as a new Notion page in the controller's close workspace.
Set it up
What you configure once, before turning it on.
- 1Connect BigQueryDatasets, queries, schemas.
- 2Connect NotionPages, databases, comments.
- 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
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.