INVOICE PROCESSING
Vendor Dispute Letter Drafter for Match Variances
For invoices that fail three-way match on price or quantity, an agent drafts a vendor-ready dispute email citing the PO terms and receipt counts, queues it for AP sign-off.
How it runs
The automated pipeline, trigger to output.
- TriggerVendor-side variance flaggedPostgres
- ActionGather PO, receipt, and invoice linesPostgres
- LogicAgent drafts cited dispute email
- ActionPost draft for AP sign-offSlack
- ActionSend approved email to vendorGmail
- OutputRecord open dispute with follow-up datePostgres
What it does
When the variance is the vendor's error, someone has to write the dispute. This agent reads the PO terms, the receiving record, and the invoice, then drafts a specific, professional dispute email that quotes the contracted price or received quantity and states the requested correction. AP reviews and sends with one click.
When to use it
Use it when match failures frequently trace back to vendor billing errors and your team spends time composing the same correction emails. It standardizes tone and makes sure every claim cites the supporting document.
How it works
- 1An invoice flagged as a vendor-side variance triggers the workflow.
- 2The agent gathers the PO, the goods-receipt record, and the invoice lines from Postgres.
- 3It reasons over which lines are wrong and drafts a dispute email with exact figures and references.
- 4The draft is posted to the AP channel in Slack for human sign-off.
- 5On approval the email is sent to the vendor contact via Gmail.
- 6The dispute is recorded as open in Postgres with a follow-up date.
Set it up
What you configure once, before turning it on.
- 1Connect PostgresAny Postgres URL — query, write, migrate.
- 2Connect SlackChannels, DMs, threads, mentions.
- 3Connect GmailRead, draft, send, label.
- 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.