INVOICE PROCESSING
Missing Goods-Receipt Chaser for Unmatched Invoices
Finds invoices that have a valid PO but no recorded goods receipt, opens a tracked task for the receiving owner, and nudges until the receipt is logged so the match can complete.
How it runs
The automated pipeline, trigger to output.
- TriggerDaily scan for PO-matched invoices missing a receiptPostgres
- ActionCreate receipt-confirmation task for receiving ownerAsana
- LogicCheck task age and reminder threshold
- ActionClose task when receipt is logged in PostgresPostgres
- OutputPost open receipt-gap summary to TeamsMicrosoft Teams
What it does
Targets the silent killer of three-way matching: invoices stuck because nobody logged that the goods actually arrived. It surfaces every invoice with a PO match but a missing receipt, assigns the receiving owner a task to confirm delivery, and keeps nudging until the receipt exists and the invoice can be matched.
When to use it
Use this when invoices pile up in a held state and the bottleneck is the receiving team, not finance. It closes the loop between the warehouse and AP without finance chasing manually.
How it works
- 1A daily scheduled run queries Postgres for invoices with a matched PO but no linked goods receipt (trigger).
- 2For each, the workflow creates an Asana task assigned to the PO's receiving owner, including the expected items and delivery date.
- 3A logic step checks task age; tasks open past the threshold trigger a reminder.
- 4When the receipt is finally logged in Postgres, the workflow detects it and closes the Asana task.
- 5A summary of still-open receipt gaps is posted to the procurement channel in Microsoft Teams.
Set it up
What you configure once, before turning it on.
- 1Connect PostgresAny Postgres URL — query, write, migrate.
- 2Connect AsanaTasks, projects, milestones — everywhere.
- 3Connect Microsoft TeamsChannels, chats, files.
- 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.