SAP procure-to-pay (P2P) process flow with T-codes
Editable SAP procure-to-pay process flow from purchase requisition (ME51N) to payment run (F110), with release strategies, MIGO goods receipt, MIRO invoice verification and tolerance blocks in swimlanes.
What the SAP procure-to-pay (P2P) process flow with t-codes process is
Most SAP P2P diagrams are one of two things: a slide with six boxes (requisition, PO, receipt, invoice, payment) that tells a key user nothing, or a configuration document that only the MM consultant can read. The useful version sits in between. It shows who does each step, which transaction they use, and where the system stops the document and waits for a person.
Those stops are where the design decisions live. The release strategy on the requisition and the PO decides who approves what. Source determination decides whether a buyer touches the requisition at all. Tolerance keys in invoice verification decide which variances block payment. Drawing them as decisions with the real branch conditions is what turns a P2P overview into something you can run a fit-to-standard workshop on.
The template is built on S/4HANA transactions, but the flow is the same in ECC 6.0: only the Fiori app names differ. Rename lanes to your plants and purchasing organisations, delete the quality inspection branch if you do not run QM, and add your own release levels.
What this flowchart covers
In this template
- Purchase requisition entry (ME51N) with account assignment, and the release strategy that routes it for approval (ME54N / ME55)
- Source determination: outline agreements and info records versus an RFQ cycle (ME41, ME47, ME49) before the purchase order
- Purchase order creation with reference (ME21N), PO release (ME29N) and output to the supplier
- Goods receipt with MIGO movement type 101, with an optional QM inspection lot and usage decision (QA11)
- Logistics invoice verification (MIRO) against PO and goods receipt, with tolerance-based payment blocks released in MRBR
- The automatic payment program (F110) and clearing of the vendor open item
When to use this template
- You are running fit-to-standard or blueprint workshops for an S/4HANA implementation and need a P2P flow key users can challenge
- Auditors or a new controller ask how purchasing actually works in your SAP system and the answer lives only in configuration
- You are training buyers, warehouse staff and AP clerks and want one picture that shows how their transactions connect
- Invoices keep landing in the blocked list and you need to show where the variance originates upstream
- You are moving from ECC to S/4HANA and want to confirm the P2P flow before the conversion locks it in
How it works
Open the template and rename the lanes
Replace the generic roles with your own: requesting departments, the release approvers named in your release strategy, the purchasing group, the receiving plant and accounts payable.
Set your release strategy on the decision
Write the real release conditions on the branch labels (for example value above 10,000 or account assignment K) so the diagram states the rule rather than 'Yes' and 'No'.
Remove or keep the optional branches
Delete the QM inspection branch if you do not use quality management in procurement, and the RFQ branch if every material has a contract or info record.
Add the exceptions your team handles every week
Partial deliveries, returns to vendor (movement type 122), invoices without a PO and down payments each need their own path if they are common in your business.
Send the flow for review and approval
Route the finished flow to the process owner and the SAP functional lead; the approval and every later change are kept in the chart's version history.
Frequently asked questions
What are the main T-codes in the SAP P2P cycle?
ME51N creates the purchase requisition, ME54N or ME55 releases it, ME21N creates the purchase order and ME29N releases it, MIGO posts the goods receipt (movement type 101), MIRO enters the supplier invoice, MRBR releases blocked invoices and F110 runs the automatic payment program. ME57, ME41, ME47 and ME49 cover assigning sources and the RFQ cycle.
Is the procure-to-pay flow different in S/4HANA compared with ECC?
The business flow is essentially the same. The differences are underneath: Business Partner replaces the separate vendor master, the Universal Journal changes how postings are stored, and many steps have Fiori apps (Manage Purchase Requisitions, Create Supplier Invoice) alongside the classic transactions. A P2P process map drawn for ECC usually survives the move with relabelled steps.
What is a release strategy in SAP purchasing?
It is the approval procedure for purchase requisitions and purchase orders. Characteristics such as total value, material group, plant or account assignment select a strategy, and the strategy defines which release codes must approve and in what order. On a process map it belongs on a decision with the actual conditions written on the branches.
Why is my SAP invoice blocked for payment?
Usually because invoice verification found a variance outside tolerance: price (tolerance key PP), quantity (DQ) or a missing goods receipt. MIRO posts the invoice with a payment block, and someone resolves it and releases it in MRBR. Mapping where those variances start, such as POs created after the fact or receipts posted late, is the fastest way to shrink the blocked list.