INVOICE PROCESSING
Draft Vendor Dispute Notes for Statement Discrepancies
An agent reviews reconciliation gaps between a vendor statement and recorded invoices, researches each discrepancy in the ledger.
How it runs
The automated pipeline, trigger to output.
- TriggerReconciliation produces unresolved gaps
- ActionQuery full invoice history from PostgresPostgres
- LogicCategorize each gap and choose a resolution
- LogicCompose per-vendor dispute note
- OutputCreate dispute note in NotionNotion
What it does
Takes the raw gaps from a statement reconciliation and turns them into something AP can act on: for each discrepancy the agent investigates the underlying invoice history, decides whether it looks like a vendor error, a timing difference, or a genuine missing invoice, and writes a clear dispute note with a recommended next step.
When to use it
When reconciliation already surfaces gaps but a human still has to spend hours figuring out which ones are real and what to say to the vendor. Use it to pre-draft disputes so AP only reviews and sends.
How it works
- 1Triggered when a reconciliation run produces unresolved discrepancies.
- 2The agent reads each flagged line item and queries Postgres for that invoice's full history (amounts, dates, payment status).
- 3It reasons over the evidence to categorize the gap and pick a recommended resolution.
- 4For each vendor it composes a dispute note explaining the discrepancy and the recommended action.
- 5The note is created as a Notion page in the AP disputes database for human review and send.
Set it up
What you configure once, before turning it on.
- 1Connect PostgresAny Postgres URL — query, write, migrate.
- 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
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.