Accounts Payable Intake: PO Matching and Exception Workflows

Start here

Overview

AP automation is less about “AI” and more about disciplined intake: clean purchase data, receipt signals, and predictable exception handling.

Core concept

Definition

PO matching compares purchase order lines, receipts, and invoices—flagging quantity, price, and tax variances for review.

Business impact

Why it matters

Payment errors and late payments damage vendor relationships and audit posture. Automation should accelerate *matching*, not bypass controls.

Practical model

Framework

Standardize vendor channels

Email PDFs, EDI, portals—normalize into one intake queue.

Exception taxonomy

Reason codes: price mismatch, missing receipt, duplicate invoice.

Implementation detail

Detailed breakdown

Segregation of duties

Automation roles must not combine approval and payment initiation against policy.

In practice

Real-world example

A manufacturer cut invoice cycle time by routing only true exceptions to AP specialists—routine matches posted automatically.

Avoid these

Common mistakes

OCR without validation—garbage in, wrong payments out.
No audit trail linking invoice to PO and receipt artifacts.

Engineering layer

Technical patterns

Three-way match

Join invoice, PO, and receipt lines; apply tolerances before posting.

Python

def match_three_way(inv_line: dict, po_line: dict, rcpt_line: dict, *, price_tol_pct: float) -> bool:
    """invoice_line ↔ po_line ↔ receipt_line on SKU/qty with price tolerance."""
    if inv_line["sku"] != po_line["sku"] or inv_line["sku"] != rcpt_line["sku"]:
        return False
    qty_ok = inv_line["qty"] <= po_line["qty"] and inv_line["qty"] <= rcpt_line["qty_received"]
    price_a, price_b = inv_line["unit_price"], po_line["unit_price"]
    price_ok = abs(price_a - price_b) / max(price_a, price_b) <= price_tol_pct
    return qty_ok and price_ok

Build patterns

Code examples

Tolerance check

Flags variance for workflow.

TypeScript

export function withinTolerance(a, b, pct = 0.01) {
  return Math.abs(a - b) / Math.max(a, b) <= pct;
}

System view

System architecture

YAML

[Invoice ingest: EDI / email / portal]
        → [OCR + field extract]
        → [PO lookup + receipt lookup]
        → [Match engine → post | exception]
        → [ERP GL]

Keep learning