INVOICE PROCESSING
Three-Way Match: S3 Invoice Ingest to Auto Payment Release
Watches an S3 bucket for incoming vendor invoice PDFs, extracts line items with OpenAI, matches them against the PO and goods-receipt records in Postgres.
How it runs
The automated pipeline, trigger to output.
- TriggerNew invoice PDF uploaded to S3 bucketAWS S3
- ActionExtract invoice fields and line items with OpenAIOpenAI
- ActionFetch matching PO and goods-receipt from PostgresPostgres
- LogicCompare qty, price, amount within tolerance
- ActionRelease vendor payment via Stripe on clean matchStripe
- OutputWrite PAID status and match evidence to PostgresPostgres
What it does
This pipeline turns a drop folder of vendor invoices into a hands-off payment decision. When a new invoice PDF lands in S3, it parses the document, reconciles it against the matching purchase order and receiving record, and pays the vendor automatically when the three-way match is clean.
When to use it
Use this when your AP team manually opens every emailed invoice, hunts for the PO, and checks the receiving log before cutting a payment. It fits high-volume, low-exception vendor relationships where most invoices match and only edge cases need a human.
How it works
- 1An invoice PDF is uploaded to the monitored S3 bucket, triggering the run.
- 2OpenAI extracts the vendor, invoice number, PO reference, and line items (qty, unit price, totals).
- 3Postgres is queried for the referenced PO and its linked goods-receipt record.
- 4A logic step compares invoiced quantity, price, and amount against the PO and receipt within a configured tolerance (e.g. 2%).
- 5On a clean match, Stripe releases the vendor payment; the result is written back to Postgres as PAID with the match evidence.
Set it up
What you configure once, before turning it on.
- 1Connect AWS S3Buckets, objects, signed URLs.
- 2Connect OpenAIModels, embeddings, files.
- 3Connect PostgresAny Postgres URL — query, write, migrate.
- 4Connect StripeCustomers, subscriptions, payments.
- 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.