INVOICE PROCESSING
Investigate unrecognized charges and propose a vendor identity
An agent-driven workflow that takes a Stripe charge no vendor registry could match, researches the merchant descriptor on the web, proposes the likely vendor and category.
How it runs
The automated pipeline, trigger to output.
- TriggerUnmatched charge received via webhookHTTP webhook
- ActionSearch web for merchant behind descriptorExa
- LogicReason and propose vendor identity
- ActionWrite pending vendor row to SnowflakeSnowflake
- OutputPost proposal to Slack for approvalSlack
What it does
When a charge cannot be matched automatically, this workflow does the detective work a finance analyst would: it interprets the cryptic billing descriptor, searches for what company it belongs to, and proposes a structured vendor record so the registry self-improves over time.
When to use it
Use it when your auto-match rate stalls because descriptors like "DRI*SVC8842" are unreadable. Instead of manually googling each one, the agent drafts an identity and a human just confirms.
How it works
- 1An unmatched charge from the reconciliation pipeline triggers the workflow via webhook.
- 2The agent normalizes the raw descriptor and searches the web for the underlying merchant.
- 3It reasons over the results to propose a vendor name, category, and likely subscription type.
- 4A draft vendor registry row is written to Snowflake in a pending state.
- 5The proposal, with confidence and sources, is posted to Slack for an analyst to approve or correct.
- 6On approval, the pending row is promoted so future charges from the merchant auto-clear.
Set it up
What you configure once, before turning it on.
- 1Connect HTTP webhookTrigger any URL on agent actions.
- 2Connect ExaNeural search across the web.
- 3Connect SnowflakeWarehouses, queries, shares.
- 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.