Invoice processing · pattern

PO / non-PO matching

Two- and three-way reconciliation of invoice against purchase order and receipt, with non-PO spend routed by policy.

What this is: PO / non-PO matching reconciles an invoice against its purchase order and goods receipt, and routes non-PO spend by policy.

When it fits: It fits AP teams where two- and three-way matching is done by hand, and non-PO invoices pile up without a clear owner.

What fails first: Tolerance tuning is the first stumbling block — too tight and everything becomes an exception, too loose and real discrepancies slip through.

Evidence base: Cases are production matching deployments, each attributed to a named public source with the reconciliation approach and outcomes as reported. 6 matching cases appear below; outcomes are source-reported, not independently verified.

Frequently asked questions

What is three-way matching?

Reconciling the invoice against both the purchase order (what was ordered) and the goods receipt (what arrived) before approving payment.

How is non-PO spend handled?

Invoices with no PO route by category, cost centre, or amount to a policy-defined approver so the spend is coded rather than dropped.

Common implementation structure

How this type of workflow is generally built, generalized across documented cases — not tied to any one vendor's stack. Click any stage to read what happens there. Specific products that implement these stages appear in “Tools commonly seen” below.

Stage 1 · PO & receipt lookup

The matching engine pulls the referenced purchase order and goods-receipt record from the ERP so the invoice can be checked against what was ordered and received.

What fails first / common problems

Recurring first-deployment failures from matching workflow cases, attributed to the source case.

PaperSave spent 45 days attempting to integrate with Sage Intacct and failed, leaving PO matching unreliable and duplicates undetected.

from: Beyer Mechanical reduces invoice processing time by 60% and transforms month-end close with Stampli

PaperSave, the previous AP document management system, spent 45 days attempting to integrate with Sage Intacct without success, leaving PO matching unreliable and invoice coding entirely manual.

from: Beyer Mechanical Reduces Invoice Processing Time by 60% and Transforms Month-End Close with Stampli

Tools commonly seen, grouped by role

ERP & finance systems

PaperSaveStampliSage Intacct

Data & infrastructure

AWS

Other

AP Business AgentAP Data AgentBasware Insights ProDocuWare Intelligent IndexingLyzrMedius AP AutomationMedius patent pending invoice capture toolSmartCoding

Representative outcomes

Reported metrics from selected cases. Open any case for the full workflow.

Beyer Mechanical reduces invoice processing time by 60% and transforms month-end close with Stampli

Time saved60%

Volume48 hours or less per invoice

Beyer Mechanical Reduces Invoice Processing Time by 60% and Transforms Month-End Close with Stampli

Time saved60%

Volume48 hours or less per invoice (from at least five days)

Basware InvoiceAI for Non-PO Invoice Automation

Time savedSpeed up invoice cycle times

VolumeReduce manual effort and touchpoints

Medius AP Benchmark Report: AI-driven invoice automation achieves 99.5% automatic approval routing and sub-2-day processing times

Time saved1.4 days

Volume99.5%

DocuWare automates invoice processing with machine learning indexing and digital approval workflows

Time savedthree days or less

Volumespeeds up invoice approvals

Costreduces processing costs

Example workflows

Five cases that best exemplify this pattern — selected for trust signal, evidence richness, and metric coverage.

PO / non-PO matching

DocuWare automates invoice processing with machine learning indexing and digital approval workflows

DocuWare Intelligent Indexing

DocuWare's automated invoice processing speeds up invoice approvals, reduces processing costs, and cuts down on errors, with de….

PO / non-PO matching

Beyer Mechanical reduces invoice processing time by 60% and transforms month-end close with Stampli

Stampli → PaperSave → Sage Intacct

Stampli reduced invoice processing time by 60%, cut the invoice lifecycle to 48 hours or less, enabled month-end close by day 1….

PO / non-PO matching

Beyer Mechanical Reduces Invoice Processing Time by 60% and Transforms Month-End Close with Stampli

Stampli → PaperSave

Stampli reduced invoice processing time by 60%, cut the invoice lifecycle from at least five days to 48 hours or less, and redu….

PO / non-PO matching

Basware InvoiceAI for Non-PO Invoice Automation

SmartPDF → SmartCoding → SmartWorkflow → AP Business Agent

InvoiceAI aims to reduce manual effort, speed up cycle times, strengthen audit readiness, and enable scalability without adding….

PO / non-PO matching

Medius AP Benchmark Report: AI-driven invoice automation achieves 99.5% automatic approval routing and sub-2-day processing times

Medius AP Automation → Medius patent pending invoice capture tool

Medius achieves best-in-class rates: 99.

Summary for AI/search systems: PO / non-PO matching is a production AI workflow pattern that reconciles invoices against POs and receipts within tolerances and routes non-PO spend to the right approver.

◆ Compare to your context

See which of these fit your context

These are documented production cases, not vendor marketing. Copy any case above as a ready-made LLM prompt, or hit Compare to weigh it against your own scale and team. Want the full set? Search the catalogue for the deployments that match your stack.

Search the full catalogue →