INVOICE PROCESSING
Catch mis-coded invoice lines before they post
Reviews newly-coded invoice lines against department budget patterns in BigQuery, flags GL codes that look wrong for the vendor or amount.
How it runs
The automated pipeline, trigger to output.
- TriggerCoded invoice event via webhookHTTP webhook
- ActionPull vendor spend pattern from BigQueryBigQuery
- ActionScore each line for coding anomaliesOpenAI
- LogicRoute clean vs anomalous invoices
- OutputOpen Linear issue for flagged linesLinear
What it does
Acts as a second set of eyes on GL coding. When an invoice is coded, it checks each line against historical spend patterns by vendor, GL account, and amount range in BigQuery, and surfaces lines that deviate sharply from the norm.
When to use it
Use it when coding is already happening (manually or via another workflow) and you want a control that catches expense-misclassification and wrong-cost-center errors before the GL closes. Aimed at controllers and FP&A.
How it works
- 1A coded-invoice event (webhook) triggers the run.
- 2A BigQuery query returns the typical GL account, amount distribution, and cost center for that vendor.
- 3An OpenAI step compares the submitted coding to the pattern and scores each line for anomaly risk with a short rationale.
- 4A logic step passes clean invoices through and routes anomalous ones onward.
- 5For flagged invoices, a Linear issue is opened for the controller with the suspect lines and suggested correct codes.
Set it up
What you configure once, before turning it on.
- 1Connect HTTP webhookTrigger any URL on agent actions.
- 2Connect BigQueryDatasets, queries, schemas.
- 3Connect OpenAIModels, embeddings, files.
- 4Connect LinearIssues, projects, cycles, triage.
- 5Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 6Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 7Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Invoice Processing workflows
Dollar-Threshold Match Variance Escalation Chain
Routes three-way match variances up an approval ladder by dollar size — small ones to the line manager, large ones to the controller.
Front vendor invoice to Airtable approval packet with line-item parse
Watches a Front inbox for vendor invoice emails, extracts header and line-item data from the body and PDF attachment, and writes a structured.
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.
Three-Way Match Exception Router by Variance Type
When a new invoice fails three-way match against its PO and receiving record, this workflow classifies the mismatch (price, quantity, or missing receipt) and routes each variance…
Route parsed Front invoices to the right Slack approver by amount
Parses an incoming Front vendor invoice and posts an interactive Slack approval card to the approver whose spending threshold matches the invoice total.
Three-way match Front invoices against purchase orders in Postgres
Parses a Front vendor invoice and runs a three-way match against the matching purchase order and receipt records in Postgres, posting pass or exception results to Slack.
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.