Glossary

The function responsible for receiving, validating, and paying supplier invoices. AP owns the process where invoice exceptions surface and get resolved.

The set of rules that decides who must sign off on an invoice or purchase before it proceeds, usually based on amount, category, or budget owner.

Contracting an operational process, such as invoice exception handling, to an external vendor that charges per invoice or per full-time equivalent. Lowers the cost per exception without lowering the count.

The part of the organization a cost is charged to, recorded as part of an invoice's GL coding.

The fully loaded cost of processing a single invoice, including labor, systems, and overhead. A touchless invoice is cheap and an exception is not.

An invoice that bills for something already invoiced, often because a supplier resubmitted one they thought was lost. A common source of overpayment.

Exception aging describes what happens to an unresolved invoice exception over time: supporting evidence gets harder to find, discount windows close, and the cost of resolving it increases.

The share of invoices that fail an automated check and require review. The most direct measure of manual work in AP.

Exception routing is the process of assigning a stalled invoice to whoever can actually resolve it, based on the fact needed to close it rather than department or dollar value.

The share of invoices that clear the three-way match on the first attempt, with no human touch.

A stricter control that adds an inspection or acceptance record to the three-way match before payment.

Assigning an invoice to the correct general ledger account and cost center so it lands in the right place in the financial statements.

The record confirming that ordered goods arrived, and in what quantity. A missing or late goods receipt is a frequent reason a match fails.

Any invoice that can't be paid automatically because it fails a validation check and has to be routed to a person.

Purchases made outside the agreed procurement process, which usually surface as non-PO invoices.

An invoice with no matching purchase order, common for services and tail spend. These invoices need a different validation path and often become exceptions.

A difference between the invoiced unit price and the price on the purchase order or contract.

The end-to-end process that runs from ordering goods or services through to paying for them. Invoice matching and exception handling sit near the end of this flow.

The document stating what a company agreed to buy, at what quantity and price, before anything is delivered. It is the reference point most invoice checks measure against.

A difference between the quantity billed and the quantity received, usually caused by partial deliveries or late receipts.

The internal request that starts the procure-to-pay process, recording what is needed and who approved it.

A centralized internal team that runs a process, such as accounts payable, for every business unit of a company. Standardizes the work and concentrates the exception queue in one place.

The broader process that includes finding and contracting suppliers as well as buying and paying. It contains procure-to-pay as its back half.

The widest process label, extending source-to-pay through settlement, reconciliation, and spend analysis.

An invoice that is validated and paid with no human involvement, also called touchless processing. Raising this rate is the main goal of AP automation.

The long list of small, infrequent purchases that gets little sourcing attention and produces many non-PO invoices.

The control that compares the purchase order, the goods receipt, and the invoice before payment.

The allowed difference between documents before a match is flagged as an exception, set as a fixed amount, a percentage, or both.

A lighter control that compares only the purchase order and the invoice, skipping the goods receipt. Common for services and low-risk spend.