INVOICE PROCESSING
Reconcile Vendor Statement Against Stripe AP and Flag Mismatches to Slack
When a vendor emails a monthly statement, this matches each line item against your Stripe payment records and posts any missing or amount-mismatched invoices to a Slack channel…
How it runs
The automated pipeline, trigger to output.
- TriggerVendor statement email receivedGmail
- ActionExtract invoice lines from attachmentOpenAI
- ActionFetch matching Stripe payments for periodStripe
- LogicJoin lines and classify match / missing / mismatch
- LogicBranch on whether discrepancies were found
- OutputPost reconciliation summary to AP Slack channelSlack
What it does
Takes an incoming vendor statement (PDF or spreadsheet attachment), extracts every invoice line, and compares each one against payments recorded in Stripe. It surfaces three problem classes: invoices on the statement that have no matching Stripe payment, invoices where the statement amount differs from what was paid, and Stripe payments the vendor never listed. A clean summary lands in Slack so AP can act before the statement ages.
When to use it
Run this when vendors send recurring statements and your team manually ties them out line by line. It is ideal for AP teams that pay through Stripe and want a fast monthly close without exporting spreadsheets by hand.
How it works
- 1A new statement email arrives and triggers the flow.
- 2The attachment is parsed with OpenAI to pull invoice number, date, and amount per line.
- 3Stripe is queried for charges and invoices matching the vendor over the statement period.
- 4A reconcile step joins on invoice number and computes per-line status: matched, missing, or mismatched.
- 5If any discrepancies exist, a formatted breakdown is posted to the AP Slack channel; clean statements post a single confirmation.
Set it up
What you configure once, before turning it on.
- 1Connect GmailRead, draft, send, label.
- 2Connect OpenAIModels, embeddings, files.
- 3Connect StripeCustomers, subscriptions, payments.
- 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
Dollar-Threshold Match Variance Escalation Chain
Routes three-way match variances up an approval ladder by dollar size — small ones to the line manager, large ones to the controller.
Front vendor invoice to Airtable approval packet with line-item parse
Watches a Front inbox for vendor invoice emails, extracts header and line-item data from the body and PDF attachment, and writes a structured.
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.
Three-Way Match Exception Router by Variance Type
When a new invoice fails three-way match against its PO and receiving record, this workflow classifies the mismatch (price, quantity, or missing receipt) and routes each variance…
Route parsed Front invoices to the right Slack approver by amount
Parses an incoming Front vendor invoice and posts an interactive Slack approval card to the approver whose spending threshold matches the invoice total.
Three-way match Front invoices against purchase orders in Postgres
Parses a Front vendor invoice and runs a three-way match against the matching purchase order and receipt records in Postgres, posting pass or exception results to Slack.
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.