INVOICE PROCESSING
AI Adjudicator for Ambiguous Duplicate Invoices
When the fingerprint check returns a near-but-not-exact match, an AI agent compares the two invoices line by line.
How it runs
The automated pipeline, trigger to output.
- TriggerAmbiguous near-match received (webhook)HTTP webhook
- ActionAgent compares both invoices line by lineOpenAI
- LogicBranch: duplicate, legit repeat, or escalate
- ActionBlock or release the Stripe payoutStripe
- ActionEscalate uncertain cases to APSlack
- OutputRecord verdict and rationale to audit logPostgres
What it does
Exact fingerprints catch obvious duplicates; this workflow handles the gray zone. When a new invoice partially matches a paid one (same vendor and amount but a different number, or a recurring charge that looks like a repeat), an AI agent reads both documents, weighs the evidence, and adjudicates. Confident duplicates are blocked at the Stripe step; legitimate repeats are released. Every decision is written back with a rationale so AP keeps an audit trail.
When to use it
Use this when your duplicate guard produces too many ambiguous flags for humans to triage, or when recurring vendors (rent, retainers, subscriptions) generate look-alike invoices that should actually be paid.
How it works
- 1An ambiguous near-match from the guard triggers the flow with both invoice records.
- 2The agent compares line items, dates, references, and vendor context to classify the pair.
- 3It branches on the verdict: true duplicate, legitimate repeat, or needs human review.
- 4True duplicates halt the Stripe payout; legitimate repeats release it.
- 5Uncertain cases are escalated to AP in Slack with the agent's reasoning.
- 6The verdict and rationale are recorded to the Postgres audit log.
Set it up
What you configure once, before turning it on.
- 1Connect HTTP webhookTrigger any URL on agent actions.
- 2Connect OpenAIModels, embeddings, files.
- 3Connect StripeCustomers, subscriptions, payments.
- 4Connect SlackChannels, DMs, threads, mentions.
- 5Connect PostgresAny Postgres URL — query, write, migrate.
- 6Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 7Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 8Test, 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 this workflow in your colony.
14-day trial. No DevOps. No Sales call. Provisioned in under a minute.