INVOICE PROCESSING
Email a monthly pre-bill reconciliation summary to finance leadership
After the cycle's invoices are validated, aggregates BigQuery usage versus Stripe invoiced totals into a single accuracy report and emails finance leadership the net…
How it runs
The automated pipeline, trigger to output.
- TriggerSchedule fires after cycle invoices finalize
- ActionQuery monthly usage and revenue by account from BigQueryBigQuery
- ActionFetch finalized Stripe invoice totalsStripe
- LogicCompute net variance, accuracy, and rank top gaps
- OutputEmail reconciliation digest to finance leadershipOutlook
What it does
This is the reporting bookend to per-invoice checks. Once the cycle closes, it rolls up the full month's usage from BigQuery against the totals Stripe actually invoiced, computes the aggregate billing-accuracy figures, and emails leadership a digest: total reconciled revenue, net exposure from over- and undercharges, and the accounts with the largest gaps.
When to use it
Use it for the monthly finance review when leadership wants a one-page confidence signal that metered billing is accurate, plus a shortlist of accounts that needed correction — without logging into Stripe or a BI tool.
How it works
- 1A scheduled trigger fires after the billing cycle's invoices have finalized.
- 2Query BigQuery for total billable usage and revenue by account for the closed period.
- 3Fetch the corresponding finalized Stripe invoice totals for the same accounts.
- 4Logic step computes net variance, percent accuracy, and ranks the top over/undercharged accounts.
- 5Send finance leadership an Outlook email with the summary metrics, exposure figures, and the ranked account table attached.
Set it up
What you configure once, before turning it on.
- 1Connect BigQueryDatasets, queries, schemas.
- 2Connect StripeCustomers, subscriptions, payments.
- 3Connect OutlookMail, calendar, contacts.
- 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
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.