INVOICE PROCESSING
Match incoming SaaS charges to your known vendor registry
Reconciles each new Stripe outbound charge against a Snowflake registry of approved SaaS vendors.
How it runs
The automated pipeline, trigger to output.
- TriggerNew Stripe charge postedStripe
- ActionLook up merchant in Snowflake vendor registrySnowflake
- LogicBranch: known vendor vs unknown merchant
- ActionMark known charge reconciled in SnowflakeSnowflake
- OutputPost unknown charge to Slack for owner reviewSlack
What it does
Every time a SaaS charge posts, this workflow checks it against your authoritative vendor list. Recognized recurring subscriptions are reconciled silently; charges from vendors you have never approved get surfaced before the money is forgotten.
When to use it
Run this when your card or Stripe account pays dozens of software vendors a month and finance keeps discovering charges nobody remembers approving. It turns a monthly spreadsheet audit into a continuous, charge-by-charge match.
How it works
- 1A new Stripe charge event fires the workflow with the descriptor, amount, and last-four.
- 2The vendor registry table in Snowflake is queried for a matching normalized merchant name.
- 3A branch splits the charge: known vendor versus unknown merchant.
- 4Known charges are written back to Snowflake as `reconciled` with the matched vendor id.
- 5Unknown charges post to a Slack review channel tagging the finance owner with the descriptor and amount, asking them to approve or dispute.
- 6The owner's reaction or reply is logged so the same merchant auto-clears next cycle.
Set it up
What you configure once, before turning it on.
- 1Connect StripeCustomers, subscriptions, payments.
- 2Connect SnowflakeWarehouses, queries, shares.
- 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.