INVOICE PROCESSING
Agent-Built Vendor Dispute Packet From Reconciliation Exceptions
After a statement is reconciled against BigQuery AP data, a CEO agent investigates each exception, drafts a vendor-ready dispute email per discrepancy.
How it runs
The automated pipeline, trigger to output.
- TriggerReconciliation completes with exceptions
- ActionQuery full invoice history from BigQueryBigQuery
- LogicAgent reasons over each discrepancyOpenAI
- ActionDraft tailored dispute email per exceptionOpenAI
- OutputFile dispute packet to Dropbox for sign-offDropbox
What it does
Goes beyond flagging to actually preparing the response. Once a statement is reconciled against AP records in BigQuery, an agent reviews every exception, gathers the relevant invoice context, and composes a clear, professional dispute or clarification email tailored to each discrepancy type (missing invoice, overcharge, duplicate). It assembles the evidence into a packet and files it to Dropbox so an AP manager can review and send.
When to use it
Use this when disputes are frequent enough that drafting them by hand is a real time sink, and you want a human to approve rather than author each message. Best for teams whose AP detail lives in BigQuery.
How it works
- 1A completed reconciliation event triggers the flow with the exception set.
- 2The agent queries BigQuery for full invoice and payment history behind each exception.
- 3It reasons over each discrepancy and decides the appropriate dispute stance.
- 4It drafts a tailored vendor email per exception.
- 5It compiles the emails plus supporting evidence into a dispute packet.
- 6The packet is saved to a Dropbox review folder for AP sign-off.
Set it up
What you configure once, before turning it on.
- 1Connect BigQueryDatasets, queries, schemas.
- 2Connect OpenAIModels, embeddings, files.
- 3Connect DropboxFiles and folders.
- 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.