INVOICE PROCESSING
Validate invoices against the Snowflake spend warehouse before release
On each approval request, queries the enterprise Snowflake spend warehouse across all subsidiaries for matching paid invoices.
How it runs
The automated pipeline, trigger to output.
- TriggerApproval-pending webhook from AP systemHTTP webhook
- ActionRead invoice fingerprint fields from payload
- ActionQuery Snowflake spend warehouse across all entitiesSnowflake
- LogicBranch on cross-entity duplicate hit
- OutputHold and notify controller in MS TeamsMicrosoft Teams
What it does
Large orgs pay the same invoice twice across different entities, ERPs, or business units. This workflow checks every approval-bound invoice against the consolidated Snowflake spend warehouse, which aggregates payments from all subsidiaries. If the invoice fingerprint already appears paid anywhere in the enterprise, the release is blocked and the controller is notified.
When to use it
Use it when payments are decentralized but reporting is centralized in Snowflake. It's the enterprise-grade backstop for multi-entity AP, where one vendor invoices several of your subsidiaries and a duplicate slips between systems.
How it works
- 1An approval-pending event fires via webhook from your AP system.
- 2The invoice's fingerprint fields are read from the payload.
- 3Snowflake is queried across all entity spend tables for a fingerprint or vendor+amount+number match.
- 4A logic branch separates a cross-entity hit from a clean invoice.
- 5Confirmed duplicates are held and an alert with the paying entity goes to the controller in MS Teams.
- 6Clean invoices return an approved-to-release response to the AP system.
Set it up
What you configure once, before turning it on.
- 1Connect HTTP webhookTrigger any URL on agent actions.
- 2Connect SnowflakeWarehouses, queries, shares.
- 3Connect Microsoft TeamsChannels, chats, files.
- 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.