INVOICE PROCESSING

Three-Way Match Exception Router to AP Queue

When a vendor invoice arrives by email, compares it against the matching purchase order and goods receipt, and routes any quantity, price, or missing-receipt mismatch…

CategoryInvoice Processing
Enginesim
Difficultyintermediate
Triggerevent
Steps6
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerNew invoice email in AP inboxGmailGmail
  • ActionExtract PO number and line items from invoiceOpenAI
  • ActionLook up matching PO and goods receiptAirtableAirtable
  • LogicCompare price, quantity, and receipt; flag variance
  • ActionCreate exception row in AP queueAirtableAirtable
  • OutputNotify assigned approver in SlackSlack

What it does

Catches invoices that fail a classic three-way match (purchase order vs. goods receipt vs. invoice) and turns each failure into a tracked, owned exception instead of a stalled payment. Clean matches pass through silently; only genuine discrepancies reach a human.

When to use it

Run this when your AP team manually eyeballs PO numbers, receipt quantities, and invoice totals before approving payment. It removes the clean-match noise so reviewers spend time only on the invoices that actually disagree.

How it works

  1. 1A new invoice email lands in the shared AP inbox and triggers the flow.
  2. 2The PO number and line items are extracted from the invoice attachment.
  3. 3The flow looks up the matching PO and goods-receipt records in Airtable.
  4. 4A branch compares unit price, quantity ordered vs. received vs. billed, and flags any delta beyond tolerance or a missing receipt.
  5. 5On mismatch, an exception row is created in the Airtable AP queue with the variance details and a status of Needs Review.
  6. 6A Slack message notifies the assigned approver with the variance summary and a link to the queue row.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect GmailRead, draft, send, label.
  2. 2
    Connect AirtableBases, tables, views, automations.
  3. 3
    Connect SlackChannels, DMs, threads, mentions.
  4. 4
    Connect OpenAIModels, embeddings, files.
  5. 5
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  6. 6
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  7. 7
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.