INVOICE PROCESSING
Map Invoice Lines to GL Budget Categories in BigQuery
On each new vendor invoice, matches every line item to a GL budget category using your BigQuery mapping table.
How it runs
The automated pipeline, trigger to output.
- TriggerNew invoice received via webhookHTTP webhook
- ActionQuery BigQuery for vendor GL mapping rulesBigQuery
- LogicScore each line against GL categories by confidence
- LogicBranch: confident match vs. uncategorized
- ActionInsert matched lines into categorized-spend tableBigQuery
- OutputAppend unmatched lines to controller review queueBigQuery
What it does
When a vendor invoice lands, this workflow reads its line items and matches each one to a general-ledger budget category using a mapping table in BigQuery (vendor + description keywords to GL code). Confidently matched lines are written to a categorized-spend table; lines it can't map are flagged as uncategorized for controller review.
When to use it
Run this when AP receives invoices faster than your team can hand-code them to the budget, and you want a single source of truth in BigQuery for categorized vs. uncategorized spend before month-end close.
How it works
- 1A new invoice arrives via webhook from your AP intake system.
- 2The flow queries BigQuery for the vendor's historical GL mappings and active keyword rules.
- 3For each line, it scores the best GL category match against a confidence threshold.
- 4A branch splits confident matches from low-confidence or unmatched lines.
- 5Matched lines are inserted into the BigQuery categorized-spend table.
- 6Unmatched lines are appended to a controller review queue table with the invoice reference and reason.
Set it up
What you configure once, before turning it on.
- 1Connect HTTP webhookTrigger any URL on agent actions.
- 2Connect BigQueryDatasets, queries, schemas.
- 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.