INVOICE PROCESSING
Release Stripe Vendor Payouts Only After Three-Way Match Passes
On a schedule, scans pending vendor invoices, confirms each one matches its PO and receipt in Snowflake.
How it runs
The automated pipeline, trigger to output.
- TriggerScheduled payout run
- ActionRead pending invoices with PO and receiptSnowflake
- LogicValidate match within tolerance
- ActionRelease Stripe payout for clean matchesStripe
- ActionMark invoice paid with payout IDSnowflake
- OutputPost held-invoice summary to SlackSlack
What it does
This workflow gates outbound vendor payments behind a passing three-way match. Nothing pays out unless the invoice, the purchase order, and the proof of receipt all agree, which closes the door on duplicate and over-billed payments.
When to use it
Use this when you pay vendors through Stripe and want payment release to be a controlled, evidence-backed step rather than someone clicking pay from an invoice alone. It is the financial-control counterpart to a matching engine.
How it works
- 1A scheduled run fires (for example, every weekday morning).
- 2All invoices in `pending_match` status are read from Snowflake along with their PO and receipt records.
- 3For each invoice a match check validates totals, line counts, and quantities against tolerance.
- 4Passing invoices trigger a Stripe payout to the vendor's connected account.
- 5The invoice status flips to `paid` in Snowflake with the Stripe payout ID recorded.
- 6Failing invoices stay on hold and a summary of held items posts to Slack for AP review.
Set it up
What you configure once, before turning it on.
- 1Connect SnowflakeWarehouses, queries, shares.
- 2Connect StripeCustomers, subscriptions, payments.
- 3Connect SlackChannels, DMs, threads, mentions.
- 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.