INVOICE PROCESSING
Investigate flagged invoice variances and draft a corrective credit memo
When a reconciliation variance is reported via webhook, an agent pulls usage and invoice detail, reasons about the likely root cause.
How it runs
The automated pipeline, trigger to output.
- TriggerWebhook delivers flagged invoice and varianceHTTP webhook
- ActionFetch invoice line items from StripeStripe
- ActionQuery raw usage events from PostgresPostgres
- LogicAgent classifies root cause and sizes the adjustment
- OutputPost draft credit memo to Slack for approvalSlack
What it does
This picks up where a numeric reconciliation leaves off. Given a flagged invoice and its variance, an agent gathers the underlying usage records from Postgres and the invoice breakdown from Stripe, then reasons about whether the gap is a proration error, a dropped meter event, or a legitimate spike. It produces a plain-language explanation and a proposed credit-memo amount for a human to approve.
When to use it
Use it when the hard part isn't detecting variances but explaining and resolving them. Good for billing teams that spend hours diagnosing each flagged account before they can correct or message the customer.
How it works
- 1An HTTP webhook delivers a flagged invoice ID and computed variance from your detector.
- 2The agent fetches the invoice's line items and metered quantities from Stripe.
- 3The agent queries Postgres for the raw usage events behind the disputed period.
- 4It reasons over the evidence to classify the root cause and compute a defensible adjustment.
- 5It drafts a credit-memo summary and recommended Stripe credit note, then posts both to Slack for an operator to approve or edit before issuing.
Set it up
What you configure once, before turning it on.
- 1Connect HTTP webhookTrigger any URL on agent actions.
- 2Connect StripeCustomers, subscriptions, payments.
- 3Connect PostgresAny Postgres URL — query, write, migrate.
- 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.