INVOICE PROCESSING
Flag Statement Invoices Missing From the AP System on File Upload
When a vendor statement is uploaded to Google Drive, this finds every invoice the vendor billed that has no record in your Postgres AP system and creates a follow-up task…
How it runs
The automated pipeline, trigger to output.
- TriggerStatement file uploaded to DriveGoogle Drive
- ActionParse statement into invoice numbersOpenAI
- ActionLook up each invoice in Postgres AP tablePostgres
- LogicKeep only invoices with no AP match
- OutputCreate Asana follow-up task per missing invoiceAsana
What it does
Focuses on one decision: which invoices does the vendor say we owe that we have no trace of? On upload, it parses the statement, checks each invoice number against the AP invoices table in Postgres, and isolates the ones with zero match. Those become actionable follow-ups so AP can either obtain the missing invoice copy or dispute the line, instead of silently letting it slip into aging.
When to use it
Reach for this when missing invoices, not amount disputes, are your main reconciliation headache, and your AP records live in Postgres. It is a lightweight, single-purpose complement to a fuller tie-out.
How it works
- 1A new file landing in the Drive statements folder triggers the flow.
- 2The statement is read and parsed into invoice numbers and amounts.
- 3Postgres is queried for each invoice number in the AP table.
- 4A filter keeps only invoices with no matching AP record.
- 5For each missing invoice, an Asana task is created tagging the AP owner with vendor, invoice number, and amount.
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.
- 4Connect AsanaTasks, projects, milestones — everywhere.
- 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
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.
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.
AI agent that investigates suspected duplicate invoices
When a new invoice can't be cleared by exact-match rules, an AI agent reviews paid history for near-duplicates (split bills, renamed vendors, rounding) and recommends pay, hold…
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.
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.
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.
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.