INVOICE PROCESSING
PDF Invoice OCR Extraction with Three-Way Match Validation
Watches a Google Drive folder for new invoice PDFs, extracts line items with an LLM, matches them against the PO and receipt, and files clean invoices while queuing mismatches.
How it runs
The automated pipeline, trigger to output.
- TriggerNew invoice PDF in Google Drive folderGoogle Drive
- ActionExtract line items from PDF with LLMOpenAI
- ActionFetch PO + goods receipt from PostgresPostgres
- LogicMatch qty/price within tolerance, flag discrepancies
- OutputFile matched invoice or queue exceptionGoogle Drive
What it does
Handles invoices that arrive as PDFs. It reads each new file, extracts vendor, PO number, and line-item detail with an LLM, then runs the three-way match against your purchase order and receiving data. Validated invoices are filed; anything that fails the match is held for review with the extracted data attached.
When to use it
Use this when vendors send invoices as email attachments or scanned PDFs rather than structured e-invoices, and someone is currently typing those line items in by hand.
How it works
- 1A new PDF appears in the monitored Google Drive invoices folder.
- 2The file content is read and passed to OpenAI to extract structured fields: vendor, PO reference, line items, unit prices, and totals.
- 3The flow fetches the referenced PO and goods receipt from Postgres.
- 4A logic step matches quantities and prices within tolerance and flags discrepancies.
- 5Clean invoices are filed to a 'matched' Drive subfolder; exceptions are recorded with the parsed data for a reviewer.
Set it up
What you configure once, before turning it on.
- 1Connect Google DriveDocs, sheets, slides, files.
- 2Connect OpenAIModels, embeddings, files.
- 3Connect PostgresAny Postgres URL — query, write, migrate.
- 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.