INVOICE PROCESSING
Release Vendor Payment via Stripe Once Three-Way Match Passes
On a scheduled run it scans approved invoices, re-verifies the three-way match against PO and receipt data, and issues a Stripe payout to the vendor.
How it runs
The automated pipeline, trigger to output.
- TriggerDaily scheduled payment run
- ActionRead approved unpaid invoices and PO/receipt dataPostgres
- LogicRe-verify match within tolerance before paying
- ActionIssue Stripe transfer to vendorStripe
- OutputRecord transfer reference and mark Paid in PostgresPostgres
What it does
Closes the loop from a passed three-way match to an actual outbound payment. On a schedule it picks up invoices marked Approved, confirms the PO, receipt, and invoice still reconcile, and pays the vendor through Stripe.
When to use it
Use it when matching is already automated but disbursement is still manual, or when you want a final guardrail that re-checks the match immediately before money leaves the account.
How it works
- 1A daily schedule fires the payment run (trigger).
- 2The flow reads approved-and-unpaid invoices and their PO and goods-receipt rows from Postgres.
- 3A logic step re-validates that invoiced amount equals received-quantity times PO price within tolerance, blocking any row that drifted since approval.
- 4For each validated invoice it creates a Stripe transfer to the vendor's connected account for the matched amount.
- 5It writes the Stripe transfer id, paid timestamp, and amount back to the Postgres ledger and marks the invoice Paid.
Set it up
What you configure once, before turning it on.
- 1Connect PostgresAny Postgres URL — query, write, migrate.
- 2Connect StripeCustomers, subscriptions, payments.
- 3Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 4Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 5Test, 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.