Invoice Matching is where ERP discipline either begins or breaks.
Two-Way PO/Invoice Match (No Goods Receipt) looks operational from far away. In a real finance team, it is a chain of assertions: the right actor started the work, the required records existed, the control policy was applied, the state change was preserved, and the outcome can be explained later without rebuilding the transaction from emails and spreadsheets.
The expected business outcome is specific: Service invoices processed without manual GL coding; over-invoicing blocked at match stage; full traceability from invoice line to PO line.
The control flow a finance team actually needs.
Step 1
Two-Way Match Activated For PO Lines...
Step 2
Comparison: Invoice Quantity Vs PO...
Step 3
Configurable Tolerance Same As...
Step 4
Service Confirmation Sign-Off Optional...
Step 5
Auto-Approve When All Lines In...
The ERP surface involved.
Module
Invoice Matching
Actors
AP Clerk, Procurement System, ERP Matching Engine
Tier
Tier 1
Finance area
Accounts Payable & Procure-to-Pay
Region lens
US and UK finance teams
Publication date
March 15, 2026
Two-way match activated for PO lines with receipt_type = SERVICE; comparison: invoice quantity vs PO quantity and invoice unit price vs PO unit price per line; configurable tolerance same as three-way match; service confirmation sign-off optional flag per PO line; auto-approve when all lines in tolerance and (no confirmation required OR confirmation received); GL account inherited from PO line; partial invoicing supported: track cumulative invoiced quantity vs PO quantity; over-invoicing beyond PO quantity blocked unless PO amendment approved; audit trail captures match method (two-way vs three-way) per invoice.
US and UK teams have different compliance hooks, but the same control problem.
US teams usually care about clean evidence for audit support, vendor records, payment controls, tax reporting, and management review. UK teams usually care about VAT-ready records, approval evidence, digital-record discipline, and traceable postings. The country-specific details differ, but the operating pattern is the same: the ERP needs controlled records, explicit ownership, defensible state changes, and evidence that survives beyond the person who completed the task.
The control matrix.
| Control area | Requirement | Acceptance proof |
|---|---|---|
| Control 1 | Two-way match activated for PO lines with receipt_type = SERVICE | Given a PO with receipt_type SERVICE exists and no GRN is required |
| Control 2 | comparison: invoice quantity vs PO quantity and invoice unit price vs PO unit price per line | when a vendor invoice is submitted and all lines match PO qty and unit_price within tolerance |
| Control 3 | configurable tolerance same as three-way match | then invoice is auto-approved and GL accounts inherited from PO lines are used |
| Control 4 | service confirmation sign-off optional flag per PO line | negative) when invoice quantity exceeds PO cumulative invoiced quantity without an approved PO amendment then 422 with error code OVER_INVOICING_BLOCKED is returned. |
| Control 5 | auto-approve when all lines in tolerance and (no confirmation required OR confirmation received | Service invoices processed without manual GL coding; over-invoicing blocked at match stage; full traceability from invoice line to PO line. |
| Control 6 | GL account inherited from PO line | Service invoices processed without manual GL coding; over-invoicing blocked at match stage; full traceability from invoice line to PO line. |
Audit evidence is a chain, not a folder.
| Evidence layer | What should be preserved |
|---|---|
| Business event | For service-based purchases (consulting, SaaS, maintenance) where no physical goods receipt exists, the system performs a two-way match between the vendor invoice and the purchase order. The matching engine compares invoice lines to PO lines on quantity (days, hours, or units) and unit price. If all lines match within tolerance, the invoice is auto-approved and coded to the GL accounts on the PO. If a service delivery confirmation is configured, the system also requires sign-off from the requesting department before approval proceeds. |
| Control rules | Two-way match activated for PO lines with receipt_type = SERVICE; comparison: invoice quantity vs PO quantity and invoice unit price vs PO unit price per line; configurable tolerance same as three-way match; service confirmation sign-off optional flag per PO line; auto-approve when all lines in tolerance and (no confirmation required OR confirmation received); GL account inherited from PO line; partial invoicing supported: track cumulative invoiced quantity vs PO quantity; over-invoicing beyond PO quantity blocked unless PO amendment approved; audit trail captures match method (two-way vs three-way) per invoice. |
| Acceptance proof | Given a PO with receipt_type SERVICE exists and no GRN is required; when a vendor invoice is submitted and all lines match PO qty and unit_price within tolerance; then invoice is auto-approved and GL accounts inherited from PO lines are used; (negative) when invoice quantity exceeds PO cumulative invoiced quantity without an approved PO amendment then 422 with error code OVER_INVOICING_BLOCKED is returned. |
| Data record | |
| System event | |
| Lifecycle state | |
The useful version of this workflow is not only fast. It is inspectable. A controller, auditor, or operator should be able to move from source event to system record to state transition to final business outcome without guessing.
Implementation contracts.
Reference data model
`purchase_orders` { id: string, vendor_id: string, receipt_type: enum(GOODS|SERVICE), status: enum(OPEN|PARTIALLY_INVOICED|FULLY_INVOICED|CANCELLED), external_id: string }; `po_lines` { id, po_id, description, qty: decimal, unit_price_minor: int64, currency_code: char(3), gl_account: string, cumulative_invoiced_qty: decimal }; `invoices` { id, po_id, match_method: enum(TWO_WAY|THREE_WAY), status }; (reference, product may differ).API and events
`POST /v1/invoices` { vendor_id, po_id, match_method: TWO_WAY, lines: [{po_line_id, qty, unit_price_minor}], external_id } -> 201 { id, status, match_result }; `GET /v1/purchase-orders/{id}/invoiced-quantities`; emits `ap.invoice.matched` event; idempotent via `external_id`.State transitions
`PENDING_MATCH -> MATCHED -> APPROVED -> PAID`; branch `PENDING_MATCH -> EXCEPTION`; guard: cumulative invoiced qty cannot exceed PO qty without amendment; SERVICE POs skip GRN requirement.Common implementation traps.
Treating the workflow as data entry
If the ERP only stores the final record, the team loses the decision trail that explains how the record became valid.
Hiding exception logic
Exceptions need owners, reason codes, and time stamps. A vague pending state is not a control.
Posting without recovery design
Retries, duplicate submissions, and partial failures must be explicit so the system does not create inconsistent records.
Skipping evidence design
A workflow that cannot produce evidence on demand will eventually push finance teams back into manual screenshots and spreadsheets.
Where Rivane fits.
Rivane is built for finance workflows where automation must stay tied to source documents, approvals, state transitions, ledger impact, reporting, and audit evidence. Use this guide as a checklist for evaluating whether an ERP workflow is merely digitized or actually controlled.
References and source basis.
These sources provide the standards, regulatory, or government context around the flow. They are included so the guide is useful to finance operators, auditors, and implementation teams, not only buyers reading software copy.