INVOICE PROCESSING
Investigate stale unmatched payments and draft vendor follow-ups
Weekly, the CEO agent reviews payments that have stayed unmatched for over a week, researches each vendor.
How it runs
The automated pipeline, trigger to output.
- TriggerWeekly review schedule
- ActionQuery Postgres for aged unmatched paymentsPostgres
- ActionPull Stripe detail and scan Dropbox for near-matchesStripe
- LogicAgent assesses cause, urgency, and ranks items
- ActionDraft per-vendor follow-up emails
- OutputDeliver ranked queue and drafts to SlackSlack
What it does
Turns the pile of stubbornly unmatched payments into action. A reasoning agent pulls every outbound payment that has sat without a matching invoice for more than seven days, looks into each vendor and payment for context, and produces a prioritized follow-up: who to chase, why, and a ready-to-send draft email asking for the missing invoice.
When to use it
Use it when simple matching has run its course and what remains needs judgment, not rules: aging items, ambiguous vendors, or partial payments. It hands the controller a worked queue instead of a raw exception dump.
How it works
- 1A weekly schedule starts the review.
- 2The agent queries Postgres for payments flagged unmatched older than seven days.
- 3For each, it pulls the full Stripe payment detail and checks Dropbox for any near-match invoice it can reason about.
- 4It assesses likelihood, root cause, and urgency for every item and ranks them.
- 5It drafts a personalized follow-up email to each vendor requesting the missing or corrected invoice.
- 6It delivers the ranked action list and the draft emails to the controller in Slack for one-click sending.
Set it up
What you configure once, before turning it on.
- 1Connect PostgresAny Postgres URL — query, write, migrate.
- 2Connect StripeCustomers, subscriptions, payments.
- 3Connect DropboxFiles and folders.
- 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.