SAP MM Procure-to-Pay (P2P) Process: End-to-End Guide for S/4HANA

November 3, 2026

Procure-to-pay (P2P) is the backbone of most SAP implementations. It covers everything from identifying a need to paying the supplier, and it touches purchasing, warehouse, accounts payable, and finance. SAP Materials Management (MM) sits at the center. Training providers describe SAP MM as a core functional module that manages a company’s Procure-to-Pay cycle.

This guide walks through each step of the SAP MM P2P process, the documents and transactions involved, how it integrates with finance and other modules, what changes in S/4HANA, and where things typically go wrong.

Transaction codes below are the classic ones many SAP users know. In S/4HANA, many tasks also have Fiori app equivalents, and some screens differ by release, so verify in your system.

P2P at a Glance

Step	Business purpose	Key SAP document	Common transaction (classic)
1. Master data setup	Define who, what, and where	Supplier (business partner), material, info record, source list	BP, MM01, ME11
2. Purchase requisition	Request goods or services	Purchase requisition	ME51N
3. Sourcing	Find and select a supplier	RFQ, quotation, contract	ME41, ME47, ME31K
4. Purchase order	Commit to buy	Purchase order	ME21N
5. Goods receipt	Receive goods or confirm services	Material document, accounting document	MIGO, ML81N for services
6. Invoice verification	Match and post the supplier invoice	Invoice document	MIRO
7. Payment	Pay the supplier	Payment document	F110
8. Reconciliation and reporting	Clear, analyze, and audit	GR/IR clearing, reports	MR11, ME2x, others

A common training outline lists the standard flow as purchase requisition, source selection and vendor evaluation, purchase order creation, and goods receipt, followed by invoice verification and payment.

Step 1: Master Data Setup

Reliable P2P starts with clean master data:

Supplier master: in S/4HANA, created through the business partner approach, as many training courses on S/4HANA procurement now teach.
Material master: material type, valuation, purchasing view, plant data.
Purchasing info record: price and delivery details for a supplier-material combination.
Source list and quota arrangements: which suppliers are allowed or preferred.
Organizational structure: purchasing organization, purchasing group, plant, storage location, company code.

Common problems: missing purchasing views, wrong tax or payment terms, blocked suppliers, inconsistent units of measure.

Step 2: Purchase Requisition (PR)

A PR is an internal request. It can be created manually, by MRP, from a project or maintenance order, or through self-service buying.

Contains material or service description, quantity, delivery date, plant, and account assignment where needed.
May trigger a release strategy (approval workflow) based on value, group, or other criteria.

Common problems: missing account assignment, wrong plant or purchasing group, release strategy not found, or approvers not assigned.

Step 3: Sourcing

Procurement selects a supplier through:

RFQ and quotation processes for competitive pricing
Outline agreements (contracts and scheduling agreements) for longer-term pricing
Source determination using source lists, info records, and contracts

Many companies run strategic sourcing and contract management in separate tools, such as SAP Ariba or Coupa, and feed results into SAP MM. See our related posts on Coupa and SAP Ariba for how these fit together.

Step 4: Purchase Order (PO)

The PO is a legally binding order to the supplier.

Contains supplier, items, quantities, price, delivery dates, payment terms, and account assignment.
Can reference a PR or contract.
Item categories control the flow: standard, subcontracting, consignment, third-party, and service.
Output (print, email, EDI, or cXML) sends the PO to the supplier.
A PO release strategy may require approval before sending.

Common problems: price not defaulting from info record or contract, tax code errors, output determination not firing, supplier not receiving the PO.

Step 5: Goods Receipt (GR) or Service Entry

When goods arrive, the warehouse posts a goods receipt against the PO (commonly movement type 101).

Updates stock quantity and value (for stock materials).
Creates a material document and a related accounting document.
For non-stock items, posts directly to the expense or asset account.
For services, a service entry sheet is created and accepted.
Quality inspection may block or hold stock if QM is active.
With EWM or WM, putaway tasks follow the receipt in the warehouse system.

Accounting effect (typical stock item): debit inventory, credit GR/IR clearing account.

Common problems: quantity over delivery tolerance, wrong storage location, batch or serial number issues, missing valuation data, posting period closed.

Step 6: Invoice Verification (IV)

The supplier invoice is entered and compared with the PO and goods receipt, known as the three-way match (PO, GR, invoice).

Standard transaction: MIRO (or the relevant Fiori app).
If values and quantities fall within tolerance, the invoice posts.
Tolerance limits control how much variance the system accepts before blocking the invoice.
Blocked invoices are released after review.
Options include Evaluated Receipt Settlement (ERS), where the buyer settles automatically based on receipts, and invoice verification in background for high volumes.

Accounting effect (typical): debit GR/IR clearing (and tax), credit supplier account.

Common problems: price or quantity variance beyond tolerance, missing goods receipt, tax code errors, duplicate invoice, and invoice entered against the wrong PO line.

Step 7: Payment

Accounts payable pays the supplier according to payment terms.

The payment run (often F110) selects open items due for payment, proposes, and posts payments.
Payment methods may include check, bank transfer, ACH, or wire, depending on region and configuration.
Cash discounts apply if paid within terms.
Payments post to the bank and clear the supplier open item.

Common problems: blocked payment, missing bank details, wrong payment method, supplier on hold, or payment terms mismatch.

Step 8: Reconciliation and Month-End

Finance and procurement reconcile open items:

GR/IR clearing account shows goods received but not invoiced (or invoiced but not received). Aged items need investigation and clearing.
Accruals for uninvoiced receipts and open commitments.
Reporting on open POs, price variances, supplier performance, spend, and invoice cycle time.

How P2P Connects to Other SAP Modules

Module	Connection
FI	Accounting documents, GR/IR, supplier accounts, payments
CO	Cost center and order assignment on POs and invoices
PP	Components for production orders, subcontracting
SD	Third-party orders, stock transfers, availability
QM	Inspection at goods receipt
WM / EWM	Putaway and warehouse tasks after goods receipt
PM	Maintenance purchase requisitions and spare parts
TM	Inbound freight, if used

What Changes in SAP S/4HANA

Business partner replaces separate customer and supplier master records as the central model.
Fiori apps provide role-based access to many P2P tasks, alongside classic transactions.
Simplified data model (for example, in material documents and finance) changes how some reports and tables work.
Embedded analytics and real-time reporting are more accessible.
Integration with cloud procurement and network solutions such as Ariba is a common pattern.
Central procurement and other options exist for multi-system landscapes.

Always check SAP’s simplification list for your release, since details vary.

Integration and Automation

Modern P2P often extends beyond core MM:

E-procurement and punch-out catalogs for guided buying
EDI or cXML for PO transmission and supplier confirmations
Invoice automation with OCR, e-invoicing, and automated matching
Workflow for approvals
Process mining with tools like SAP Signavio to find bottlenecks (see our post on Signavio for P2P)

Common P2P Issues and Quick Checks

Symptom	Likely cause	First check
Invoice blocked for price	Price variance beyond tolerance	PO price vs. invoice, tolerance settings
Invoice blocked for quantity	Invoice quantity exceeds received quantity	Goods receipt posted? Correct PO line?
Goods receipt can’t be posted	Closed period, missing data, over-delivery	Posting period, PO status, delivery tolerance
PO not sent to supplier	Output determination or interface failure	Output status, message log, middleware
GR/IR balance growing	Receipts not invoiced, or invoices not matched	GR/IR report, open PO items
Wrong account posted	Account determination or account assignment error	Valuation class, account assignment, OBYC settings
Duplicate invoice	Duplicate check not active or bypassed	Invoice reference, duplicate settings
Requisition stuck	Release strategy or approver missing	Release strategy and workflow

KPIs to Track

PO cycle time (requisition to PO)
Percentage of POs created before the invoice (no retroactive POs)
Three-way match rate and invoice exception rate
Touchless invoice rate
Days payable outstanding and on-time payment rate
GR/IR aging
Spend under contract
Supplier delivery performance

Best Practices

Keep master data clean. Most P2P errors start there.
Design approval rules to match risk, not every purchase needs five approvers.
Use tolerances thoughtfully to reduce blocks without losing control.
Enforce “no PO, no pay” where policy allows.
Monitor GR/IR regularly instead of waiting for month-end.
Separate duties between requisition, approval, receiving, and payment.
Automate routine steps such as invoice capture and approvals.
Measure end to end, not just within MM.

Skills and Career Angle

SAP MM and P2P knowledge is one of the most requested skill sets in SAP projects, and it pairs well with FI, Ariba, EWM, and S/4HANA migration experience. Useful skills include:

Master data, purchasing, inventory, and invoice verification
Account determination and integration with FI
Release strategies, output determination, and tolerances
S/4HANA and Fiori
Troubleshooting across MM, FI, and interfaces
Integration with Ariba, Coupa, EDI, or other procurement tools

Check SAP’s certification site for current MM and procurement exam details.

FAQs

What is the P2P process in SAP MM?
The end-to-end flow from requisition and purchase order through goods receipt, invoice verification, and payment.

What is a three-way match?
A check that the purchase order, goods receipt, and supplier invoice agree on quantity and value before the invoice is paid.

What is GR/IR?
A clearing account that holds the value of goods received but not yet invoiced. It is cleared when the invoice is posted.

Is the P2P process different in S/4HANA?
The core steps are the same, but S/4HANA uses the business partner model, Fiori apps, and a simplified data model.

Can I skip a purchase requisition?
Yes. POs can be created directly, though many organizations require requisitions for approvals and control.

What causes blocked invoices?
Usually price or quantity variances beyond tolerance, missing goods receipts, or other configured block reasons.

What’s the difference between MM P2P and Ariba or Coupa?
MM executes procurement transactions inside SAP. Ariba and Coupa add strategic sourcing, supplier collaboration, guided buying, and invoicing capabilities, and usually integrate with SAP MM.

Back to blog

Item added to your cart