INVOICE PROCESSING
Catch vendors still billing after you canceled the subscription
On a weekly schedule, cross-checks Stripe charges against vendors marked canceled in Snowflake and raises a PagerDuty incident plus a Slack alert whenever a supposedly-canceled…
How it runs
The automated pipeline, trigger to output.
- TriggerWeekly schedule
- ActionPull recent Stripe chargesStripe
- ActionFetch canceled subscriptions from SnowflakeSnowflake
- LogicFind charges after cancel date
- ActionOpen PagerDuty incident for zombie chargePagerDuty
- OutputPost dispute alert to SlackSlack
What it does
Verifies that cancellations actually stopped the money. It compares recent charges to your list of subscriptions marked canceled and surfaces any vendor that is still billing you after the cancel date, which is real recoverable cash.
When to use it
Use it when your team cancels subscriptions but has no systematic check that the vendor honored it. Zombie charges on canceled plans are common and easy to dispute if caught quickly.
How it works
- 1A weekly schedule triggers the watchdog.
- 2Recent Stripe charges are pulled for the lookback window.
- 3Snowflake is queried for subscriptions whose status is canceled along with their effective cancel dates.
- 4A logic step finds charges that posted after a vendor's cancel date.
- 5Clean weeks end silently with a logged all-clear.
- 6Any zombie charge opens a PagerDuty incident for the finance on-call and posts a Slack alert with the vendor, amount, and cancel date so a dispute can be filed before the refund window closes.
Set it up
What you configure once, before turning it on.
- 1Connect StripeCustomers, subscriptions, payments.
- 2Connect SnowflakeWarehouses, queries, shares.
- 3Connect PagerDutyIncidents, on-call, escalations.
- 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.