INVOICE PROCESSING
Block Duplicate Vendor Prepayments in Stripe
Watches outgoing Stripe payments and holds any charge that matches a recently paid invoice in amount, vendor, and reference.
How it runs
The automated pipeline, trigger to output.
- TriggerStripe payment intent createdStripe
- ActionFetch recent payments to same destinationStripe
- LogicCompare amount, reference, and time window
- LogicBranch if confident duplicate detected
- OutputHold payment and alert finance in SlackSlack
What it does
When your team initiates a vendor prepayment through Stripe, this workflow checks whether a near-identical payment already cleared in the last 60 days. It compares amount, destination account, and the invoice reference on the payment metadata, catching the classic mistake of paying the same supplier from two different staff queues. Matches are held and escalated; clean payments pass straight through.
When to use it
Use it when finance pays vendors via Stripe transfers or payouts and multiple people can initiate the same disbursement. It is the safety net for teams without a centralized approval queue, where two operators might each act on the same emailed invoice.
How it works
- 1A Stripe payment-intent created event triggers the workflow.
- 2The workflow pulls recent payments to the same destination from the Stripe API.
- 3A logic step compares amount, reference, and time window against each recent payment.
- 4If a confident duplicate is found, it branches to the hold path and the payment is flagged for manual release; otherwise it records an all-clear.
- 5A Slack alert names the original transaction, the new one, and the matched fields for fast human confirmation.
Set it up
What you configure once, before turning it on.
- 1Connect StripeCustomers, subscriptions, payments.
- 2Connect SlackChannels, DMs, threads, mentions.
- 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.