PROCURE TO PAY · VERIFY
How does SAP verify a supplier invoice?
Logistics Invoice Verification compares the supplier claim with the commercial commitment and the relevant evidence of receipt, then records the liability and any payment block.
PROCESS ROLE
Invoice verification separates liability recognition from payment permission
A valid invoice can be posted while a material variance blocks payment. PO quantity and price, goods receipt or accepted service, tax, planned delivery cost, tolerances, duplicates, and payment terms shape the result.
OPERATIONAL FLOW
What happens in SAP
Read the sequence as one connected business event, not as isolated transactions.
Record the supplier claim
Supplier, invoice reference, date, amount, currency, tax, PO reference, and payment information establish the proposed liability.
Compare commitment and receipt
SAP evaluates ordered value, received or accepted quantity, prior invoices, expected price, tax, and applicable tolerances.
Create the liability
The invoice normally debits GR/IR, expense, asset, or tax and credits the supplier reconciliation account.
Handle blocks and differences
Quantity, price, tax, duplicate, or workflow exceptions are investigated, corrected, released, credited, or reversed with evidence.
DESIGN & CONTROL
What shapes the result
These controls work together; a locally correct setting can still produce the wrong end-to-end outcome.
Matching basis
PO-based or GR-based verification, service acceptance, delivery costs, invoice-before-receipt policy, and final-invoice indicators define what is compared.
Tolerance and duplicate control
Tolerance keys, company-code settings, supplier reference checks, amount checks, and stochastic or manual blocks protect liability quality.
Tax and payment status
Tax code, jurisdiction, withholding, payment terms, baseline date, payment block, and release authority govern downstream settlement.
DIAGNOSTIC EVIDENCE
Explain the match result before releasing payment
A blocked invoice is a result, not a diagnosis. Identify which comparison failed and whether the underlying PO, receipt, invoice, or tolerance is wrong.
Supplier, reference, dates, gross and net value, currency, tax, PO items, quantities, price units, and prior invoices.
Ordered, received, accepted, and invoiced quantities and values; variance type; tolerance key; and blocking reason.
Accounting document, GR/IR clearing, supplier open item, due date, payment terms, block status, and release decision.
PROJECT MOMENT
The supplier invoices ten but only nine were received
SAP posts or parks the invoice according to policy and records a quantity variance. Payment remains blocked until the missing receipt, supplier credit, or approved exception resolves the mismatch.
- Duplicate check passes
- Variance is explicit
- Liability is traceable
- Release follows authority
See how demand, sourcing, commitment, receipt alternatives, invoice matching, accounting entries, payment, and clearing connect.