INVOICE PROCESSING
Agentic Vendor Entity Resolution for Duplicate Holds
When a possible duplicate is flagged, an agent investigates whether two differently-named vendors are actually the same entity, gathers evidence, and recommends a hold-or-pay…
How it runs
The automated pipeline, trigger to output.
- TriggerCandidate duplicate pair receivedHTTP webhook
- ActionPull both vendor masters and historiesSnowflake
- LogicEstimate same-entity probability from shared signals
- ActionConfirm parent/subsidiary via web searchExa
- OutputPost hold-or-pay brief to approverSlack
What it does
The hardest duplicates hide behind vendor identity: "Acme LLC" and "Acme Holdings Inc" billing the same service. When a candidate pair is flagged, this agent investigates whether the two vendors are really one entity. It pulls both vendor records and payment histories from Snowflake, weighs signals like shared bank details, addresses, and tax IDs, optionally checks public records, and produces a hold-or-pay recommendation with a written rationale routed to the approver.
When to use it
Use it for the gray-area cases your deterministic scanners cannot resolve alone, where a human would otherwise spend twenty minutes cross-referencing vendor masters. It turns ambiguous flags into a decision-ready brief.
How it works
- 1A candidate duplicate pair arriving via webhook triggers the agent.
- 2The agent queries Snowflake for both vendors' master records and payment histories.
- 3It reasons over shared bank, address, and tax-ID signals to estimate same-entity probability.
- 4It optionally runs a web search to confirm parent-subsidiary or name-change relationships.
- 5It writes a hold-or-pay recommendation with evidence and posts the brief to the approver in Slack.
Set it up
What you configure once, before turning it on.
- 1Connect HTTP webhookTrigger any URL on agent actions.
- 2Connect SnowflakeWarehouses, queries, shares.
- 3Connect ExaNeural search across the web.
- 4Connect SlackChannels, DMs, threads, mentions.
- 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
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.