Procure-to-pay process: connect approvals to payment evidence

A paid invoice does not establish that the right goods were approved, received, and matched to the right order.

Kartik Deshpande··5 min read

The procure-to-pay process connects an approved need to purchasing, receipt, invoice verification, and payment. It should preserve the document links and decision owner at every handoff so accounts payable can explain why an invoice is payable and operations can explain what was received. A completed payment is the last event in that chain, not proof that all earlier controls were satisfied.

SAP’s procure-to-pay explanation places purchasing and accounts payable in one process spanning selection, compliance, receiving, reconciliation, invoicing, and payment. The exact stage labels can differ between organizations. Start with your actual documents and approval authority rather than copying a diagram whose controls do not fit the purchase.

Approve the request and establish the order

The requester defines the need, quantity, required date, delivery location, and business owner. The budget or delegated approver decides whether the request can proceed. Keep that approval attached to a version of the request so a later quantity change does not inherit approval for a different amount or purpose.

Purchasing confirms the supplier, item or service specification, price, units, taxes where relevant, and delivery terms before issuing the order. A supplier acknowledgement can differ from the order sent, so compare the accepted quantity, price, and date. Keep approved revisions (including their effective dates) and the current revision distinct. The purchase order approval workflow covers authority at that boundary.

Use supplier identifiers across the request, order, and invoice records. A trading name and a legal payee can differ, while several entries can refer to the same vendor. Resolve those references through the approved vendor process rather than treating a matching name as permission to pay. Supplier-bank changes need their existing verification controls; a procurement report is not that verification.

Record receipt and acceptance at the line level

Receiving confirms what arrived, where it arrived, and which order line it fulfills. Record shortages, damaged goods, and the quantities still awaiting inspection. A carrier delivery event does not establish that every ordered unit passed acceptance. For services, identify the authorized service owner and the milestone or other evidence used to confirm performance.

SAP Learning’s process walkthrough describes goods receipt and invoice verification against the purchase order. Apply those document relationships at the correct grain. A header total can hide a missing line or an overdelivery on a different item, even when the total invoice amount looks familiar.

Retain the link from a return or receipt correction to the original receipt. If ten units were returned after receipt, the accepted quantity available for matching may change. Do not delete the first receipt and lose the evidence that supported an earlier approval. Use explicit status and adjustment records so purchasing and accounts payable can review the same history.

Documents connect the purchasing and payment decisions
Approved request
Order and receipt
Invoice and payment
Each handoff needs its own owner; an order reference alone does not establish receipt or payment approval.

Resolve a partial delivery before authorizing payment

Assume a hypothetical order for 100 pieces at $20 each, with no tax, freight, discounts, or tolerance differences. Receiving records 70 accepted pieces, while the supplier sends an invoice for all 100. Under this example’s policy, payment approval requires an accepted receipt for the invoiced quantity. The purchase order value is $2,000, but only $1,400 is supported by the current receipt.

Document or comparisonQuantityAmount
Approved purchase order100 pieces$2,000
Accepted receipt70 pieces$1,400
Supplier invoice100 pieces$2,000
Unmatched invoice quantity30 pieces$600

Accounts payable holds the exception and assigns purchasing or receiving to resolve it. Perhaps another receipt was omitted, the invoice should be corrected, or the order allows a different billing arrangement. The table does not determine which explanation is true. Preserve the supplier response and the resulting approved treatment before releasing the payment block.

If a corrected invoice for 70 pieces replaces the original, retain both invoice identifiers and their relationship. Mark the superseded document under the existing policy so a later import does not reintroduce it as a new payable. If the original remains valid but is partially held, record the approved payable portion and outstanding exception without fabricating a second invoice.

Inspect a purchasing exception across documents

Start with a permitted request, order, receipt, and invoice for one disputed line.

Confirm payment without closing unresolved delivery

The authorized payment owner confirms the approved payable, due date, payee, and release controls. After execution, retain the payment reference and remittance allocation. A scheduled batch and a completed payment are different states; a rejected payment can leave the invoice open. Keep payment status separate from invoice approval and from order delivery status.

Reconcile invoice credits and payment allocations before labeling an invoice settled. A payment covering several invoices needs line-level allocation or an explicit unapplied amount. Purchasing may still need to follow up on open ordered quantities even after an advance or milestone payment. The purchase order tracking article addresses that continuing delivery obligation.

Use the three-way matching article for the narrower comparison of order, receipt, and invoice. The end-to-end review should show which stage is blocked, the amount or quantity affected, the owner, and the evidence required to unblock it. Measure stage duration from explicit events so a document correction does not silently reset the clock.

For project purchasing, construction purchase order software also needs to preserve job and cost-code references. Those dimensions explain where the commitment belongs; they do not replace receipt and invoice evidence. Keep the project allocation attached when an order serves more than one job.

Where Permute connects process evidence

Permute sells connected business data and custom applications. We can combine permitted purchasing, receiving, and accounts payable records with supplied approval registers, resolving vendor, order, and line references under your declared rules. That can make a blocked invoice traceable to a missing receipt or unresolved document revision.

We can reuse the same definitions in a recurring exception report or a scoped application. A procurement manager could inspect outstanding receipts while an accounts payable manager sees the invoice evidence within their current permissions. Agree on source history and refresh timing before depending on the view for a payment run.

Keep financial control and payment authority explicit

This analytical workflow does not approve purchases, accept goods, change supplier details, or release payments. We do not choose accounting treatments or replace the authorized financial control owners. Any supported external action requires its own declared capability, explicit approval, and current permissions. Keep those execution checks separate from visibility into a document.

Connect the procure-to-pay process through the approved request, current order, accepted receipt, verified invoice, and completed payment. Preserve revisions and partial quantities so each owner can explain the remaining obligation. Assign exceptions to the person who can resolve the missing evidence. Close the payment and delivery states only when their own supporting records establish completion.

Review a blocked invoice handoff

Bring a disputed invoice and the related order and receipt evidence to identify the missing links in the process.

Questions about purchasing and payment handoffs

Can purchases without a purchase order fit this process?

Yes, when the company permits them and defines the alternative approval and acceptance evidence. Mark them as a different route rather than fabricating an order reference. Accounts payable still needs an authorized basis for the liability and payment.

How does source-to-pay differ from procure-to-pay?

Source-to-pay includes upstream sourcing and supplier selection work as well as purchasing and payment. The boundary varies by organization, so label the scope in the process map. Keep sourcing decisions linked where they establish the contract or supplier used by an order.

Which handoffs should be automated first?

Start where document references and exception rules are stable enough to verify. A read-only comparison can expose missing receipts before you automate a decision. Keep uncertain matches with an owner until the business has approved the relevant rule.