SAP MM Procure-to-Pay Explained: From Requirement to Payment
Understand the SAP MM procure-to-pay process from purchase requisition and purchase order through goods receipt, invoice verification and FI integration.
The business problem behind procure-to-pay
Procure-to-pay is the controlled journey from recognising a business need to paying the supplier. The objective is not merely to buy an item. The organisation has to ensure the requirement is legitimate, the supplier and price are appropriate, the order is authorised, the received quantity is recorded, the invoice agrees with what was ordered and received, and the financial liability is recognised correctly.
Purchase requisition: expressing internal demand
A purchase requisition represents an internal request for procurement. It can originate from a person, maintenance activity, planning process or another business need. Consultants care about more than the document itself: who can raise the requirement, what material or service is required, which plant or cost object is affected, whether approval is required and whether the demand should lead to external procurement.
Purchase order: the commercial commitment
The purchase order formalises what the organisation intends to buy, from whom, at what price, for which location and under which commercial conditions. Real consulting discussions often involve approval thresholds, purchasing organisations, account assignment, delivery tolerances, taxes and exceptions. A purchase order therefore sits at the intersection of business policy, master data and system configuration.
Goods receipt: proving that something arrived
When goods are received, inventory or consumption can change and an accounting impact may be triggered depending on the scenario. The goods receipt also creates evidence against which the supplier invoice can later be checked. Understanding this step means understanding quantities, movement types, stock status, valuation and the downstream effect on finance.
Invoice verification and three-way matching
Invoice verification compares the supplier invoice with the purchasing and receipt history. The familiar three-way-match idea is simple: what was ordered, what was received and what is being invoiced should make commercial sense together. Tolerances and exceptions exist because real business is messy. Consultants need to understand how the organisation wants those exceptions controlled rather than merely knowing where an invoice is entered.
MM and FI are one process viewed by two functions
Procurement users think in materials, suppliers and receipts while finance users think in valuation, liabilities and payments. SAP connects those perspectives through integrated documents and account determination. This is why MM learners benefit enormously from understanding the accounting consequences of procurement events, even if they never become FI consultants.
Connect this concept to the complete business-first learning path.
Explore the related N2i Minds SAP path · Browse the SAP Knowledge Centre