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

Published by Isun TECHNOVA

Introduction

Procure-to-Pay (P2P) is one of the most important business processes in SAP Materials Management (SAP MM). It covers the complete purchasing cycle, from identifying a business requirement to ordering goods, receiving materials, verifying supplier invoices, and processing payment.

In SAP S/4HANA, the Procure-to-Pay process connects purchasing, inventory management, supplier information, and financial accounting. A properly configured P2P process helps organizations improve purchasing visibility, maintain accurate inventory records, control costs, and reduce invoice discrepancies.

In this guide, we will explore the SAP S/4HANA P2P process step by step, with a practical business example, important SAP transaction codes, MM-FI integration, common errors, and troubleshooting tips.

What Is Procure-to-Pay in SAP S/4HANA?

Procure-to-Pay is the end-to-end process an organization follows to purchase goods or services from external suppliers and settle the resulting financial obligations.

The process generally includes:

1. Purchase requisition
2. Purchase requisition approval
3. Source determination and supplier selection
4. Purchase order creation
5. Goods receipt or service confirmation
6. Supplier invoice verification
7. GR/IR reconciliation
8. Payment processing by Finance

The exact steps depend on the procurement scenario, such as stock materials, consumables, services, subcontracting, or third-party procurement.

SAP S/4HANA P2P Process Flow

Business Requirement → Purchase Requisition → Approval → Purchase Order → Goods Receipt → Invoice Verification → GR/IR Reconciliation → Supplier Payment

Each step creates or updates business documents. These documents allow users to trace the purchasing process and investigate discrepancies.

Step 1: Create a Purchase Requisition (PR)

A purchase requisition is an internal request to procure a material or service. It informs the purchasing department that a requirement exists.

A PR may be created manually by a user or generated through planning processes such as Material Requirements Planning (MRP).

Typical information includes:

1. Material or service description
2. Requested quantity
3. Delivery date
4. Plant and storage location, where applicable
5. Purchasing group
6. Account assignment for consumption or service procurement, when required

The requisition may need approval based on the company's release strategy or workflow configuration.

Example: A manufacturing plant requires 100 units of packaging material for next month's production. The requesting department creates a PR for 100 units with the required delivery date.

Common SAP transaction: ME51N — Create Purchase Requisition in SAP GUI.

Step 2: Approve the Purchase Requisition

Before purchasing proceeds, the PR may need approval from an authorized manager or department.

Approval controls can depend on factors such as:

1. Requisition value
2. Plant or purchasing organization
3. Material group
4. Account assignment
5. Company-specific approval policies

Once approved, the purchasing team can continue with supplier selection and purchase order creation.

Consultant tip: If a requisition cannot be converted into a purchase order, check its approval status, outstanding workflow tasks, item-level errors, and applicable configuration.

Step 3: Determine the Source of Supply

The purchasing team identifies a suitable supplier and purchasing source.

Depending on the scenario and configuration, SAP can use purchasing information records, source lists, contracts, scheduling agreements, quotations, or other approved sources.

The purchasing team should evaluate relevant commercial and operational factors, including price, delivery time, quality, and supplier reliability.

Example: Three suppliers can provide the packaging material. The buyer selects an approved supplier based on price, lead time, and business requirements.

Consultant tip: If a suitable supplier is not proposed automatically, review source determination settings and the validity of relevant purchasing master data.

Step 4: Create a Purchase Order (PO)

A purchase order is the formal purchasing document sent to the supplier. It records what the organization intends to buy and under which conditions.

A purchase order typically includes:

1. Supplier
2. Material or service
3. Quantity and price
4. Delivery date
5. Plant and delivery location
6. Payment terms
7. Tax and other applicable conditions
8. Account assignment, where required

After the required approvals, the PO is communicated to the supplier using the organization's configured output method.

Common SAP transaction: ME21N — Create Purchase Order in SAP GUI.

Example: The buyer creates a PO for 100 units at ₹500 per unit.

Purchase order value: 100 × ₹500 = ₹50,000, before applicable taxes and additional charges.

Step 5: Post the Goods Receipt (GR)

When the supplier delivers the materials, the receiving team checks the delivery against the purchase order.

The team verifies the quantity, material, delivery condition, and other relevant details before posting the goods receipt.

For a standard goods receipt against a stock-material PO, movement type 101 is commonly used. The appropriate movement type depends on the business scenario.

A successful goods receipt updates the relevant inventory and purchasing document history. The received quantity becomes available according to the stock type and other applicable controls.

Common SAP transaction: MIGO — Goods movements in SAP GUI. The corresponding app or process may differ by SAP S/4HANA edition.

Example: The supplier delivers all 100 units. The receiving team posts the goods receipt with reference to the PO.

Important: If only 80 units arrive, the team should record the actual quantity received rather than posting the full ordered quantity.

Step 6: Perform Supplier Invoice Verification (IR)

After delivering the goods or services, the supplier submits an invoice.

The Accounts Payable or invoice-processing team verifies the invoice against the relevant purchasing documents and receipts, according to the configured process.

This commonly involves a three-way match:

1. Purchase order: What was ordered?
2. Goods receipt: What was received?
3. Supplier invoice: What is being charged?

The system checks relevant quantities, prices, taxes, and tolerances. Depending on configuration, discrepancies can trigger warnings, payment blocks, or other exception handling.

Common SAP transaction: MIRO — Enter Incoming Invoice in SAP GUI for applicable processes.

Example: The PO specifies 100 units at ₹500 each, and the goods receipt confirms 100 units. The invoice also shows 100 units at ₹500 each. If all other relevant conditions match, the invoice can proceed according to the organization's validation and approval rules.

Step 7: Understand GR/IR Clearing

GR/IR stands for Goods Receipt/Invoice Receipt. It is a clearing account used to manage timing differences between goods receipts and supplier invoices in applicable procurement processes.

For a typical valuated stock-material procurement, the goods receipt commonly posts:

1. Debit: Inventory
2. Credit: GR/IR clearing account

When the supplier invoice is posted, the system commonly posts:

1. Debit: GR/IR clearing account
2. Credit: Supplier reconciliation account

The exact accounting entries depend on the procurement scenario, valuation, account assignment, price differences, and configuration.

When the expected goods receipt and invoice values match, the relevant GR/IR balance can clear. If quantities or values differ, an open balance may remain.

Example: Goods are received for ₹50,000, but the supplier invoice is posted for only ₹40,000. The remaining balance may require a subsequent invoice, a receipt correction, or investigation before any permitted clearing action.

Common SAP transaction: MR11 is used for applicable GR/IR maintenance and clearing scenarios in SAP GUI. Available Fiori apps and processing options depend on the edition and release.

Best practice: Investigate missing receipts, missing invoices, incorrect quantities, price differences, and delivery-cost postings before clearing residual balances. Do not clear an item merely to make the balance disappear.

Step 8: Process Supplier Payment

After the invoice has passed the relevant checks and approvals, Finance processes payment according to the company's payment terms and payment-run procedures.

The payment process can include:

1. Reviewing due invoices
2. Checking payment blocks and exceptions
3. Selecting items for payment
4. Executing an approved payment run
5. Generating payment media where configured
6. Reconciling the resulting accounting entries

Payment is generally handled through Financial Accounting and Accounts Payable, with the exact process depending on the SAP S/4HANA edition and company configuration.

Example: If the supplier's payment terms are 30 days, Finance schedules payment based on the invoice's applicable due date and the organization's payment policies.

The invoice is not necessarily paid immediately after posting. Payment timing depends on due dates, approval status, payment blocks, and the payment process.

Practical End-to-End Example

Consider a company purchasing 100 units of raw material from an approved supplier.

This example assumes that the full quantity is received, the invoice matches the relevant purchasing details, and no additional differences or blocks prevent processing.

Important SAP P2P Transaction Codes

The following transaction codes are commonly associated with SAP GUI processes. Their availability and exact usage can vary by SAP S/4HANA release, edition, role, and configuration.

SAP S/4HANA also provides role-based Fiori apps for many procurement and invoice-processing activities. In SAP S/4HANA Cloud Public Edition, users generally work through the supported Fiori apps and processes rather than assuming that every traditional transaction code is available.

How SAP MM Integrates with SAP FI

One of the most important aspects of Procure-to-Pay is its integration between Materials Management and Financial Accounting.

When a relevant goods receipt or invoice is posted, SAP generates accounting effects according to the procurement scenario and account determination.

For a typical stock-material purchase:

1. Goods receipt affects inventory valuation and the GR/IR clearing account.
2. Invoice posting clears the relevant GR/IR amount and recognizes the supplier liability.
3. Payment processing reduces the supplier liability and updates the relevant bank or payment-clearing accounts.

For consumables, services, and other account-assigned procurement, the debit posting may go to a cost center, asset, project, or another relevant account rather than inventory.

The accounting result depends on factors such as valuation, account assignment, tax settings, price control, and automatic account determination.

Common SAP P2P Errors and Troubleshooting

1. Purchase requisition cannot be converted to a purchase order

Possible causes:

1. Approval is incomplete.
2. Required purchasing data is missing.
3. No valid source of supply is available.
4. The item contains validation errors.

What to check: Review the requisition status, item details, source determination, and relevant workflow or configuration settings.

2. Goods receipt cannot be posted

Possible causes:

1. The purchase order is closed or otherwise restricted.
2. The entered quantity exceeds an applicable tolerance.
3. The material or plant data is incomplete.
4. The posting date or stock details are invalid.

What to check: Review the PO item, open quantity, delivery status, material data, posting period, and exact error message.

3. Supplier invoice is blocked

Possible causes:

1. Invoice price exceeds an applicable tolerance.
2. Invoice quantity does not match the receipt.
3. The PO, receipt, and invoice contain inconsistent details.
4. A required approval or validation is incomplete.

What to check: Compare the PO conditions, posted receipts, invoice values, tax details, and configured tolerance limits. Resolve the underlying discrepancy before releasing a block.

4. GR/IR account contains an open balance

Possible causes:

1. Goods have been received but the invoice has not arrived.
2. The invoice quantity differs from the received quantity.
3. A receipt or invoice was reversed.
4. Price or delivery-cost differences remain.

What to check: Analyze the relevant PO history and accounting documents. Determine whether a further receipt, invoice, correction, or authorized clearing action is appropriate.

5. Accounting entries are not as expected

Possible causes:

1. The procurement item uses account assignment instead of stock procurement.
2. Automatic account determination is configured differently than expected.
3. Price control, valuation, tax, or additional charges affect the posting.
4. The transaction uses a different procurement scenario.

What to check: Review the purchasing item category, account assignment, material valuation, accounting document, and relevant configuration with the authorized SAP FI/MM team.

Best Practices for SAP S/4HANA P2P

1. Maintain accurate material, supplier/business partner, purchasing, and accounting master data.
2. Use approval workflows appropriate to the organization's procurement policy.
3. Keep purchase order quantities, prices, delivery dates, and account assignments accurate.
4. Post only the quantities actually received and use the correct movement type for the scenario.
5. Investigate invoice discrepancies before releasing payment blocks.
6. Monitor GR/IR balances regularly and resolve underlying differences before period-end close.
7. Use role-based Fiori apps and reports where appropriate for your SAP S/4HANA edition.
8. Maintain traceability between requisitions, purchase orders, receipts, invoices, and accounting documents.
9. Test procurement and invoice scenarios in the appropriate test environment before applying configuration changes in production.

Frequently Asked Questions

What is the difference between a purchase requisition and a purchase order?

A purchase requisition is an internal request to procure goods or services. A purchase order is the formal purchasing document used to order them from a supplier.

What is the difference between goods receipt and invoice receipt?

Goods receipt records the delivery of goods or completion of a relevant receipt process. Invoice receipt records the supplier's billing document. They are separate events and may occur at different times.

What is GR/IR in SAP MM?

GR/IR is the Goods Receipt/Invoice Receipt clearing account used to account for timing and value differences between goods receipts and supplier invoices in relevant procurement scenarios.

Which transaction codes are commonly used in SAP P2P?

Common SAP GUI transaction codes include ME51N, ME21N, MIGO, MIRO, and MR11. Availability varies by edition, release, and configuration.

Is SAP P2P fully automatic in SAP S/4HANA?

Not necessarily. SAP can automate or streamline selected activities, but approvals, supplier selection, receipt confirmation, invoice exceptions, and payments depend on business rules, configuration, integrations, and user roles.

How does SAP MM integrate with SAP FI in the P2P process?

Relevant procurement postings generate accounting entries based on the transaction and account determination. Examples include inventory or expense postings, GR/IR clearing, supplier liabilities, and payment entries.

Conclusion

The Procure-to-Pay process is a core business process in SAP S/4HANA. It connects purchasing, inventory management, invoice verification, and financial accounting in a traceable workflow.

Understanding each stage—from purchase requisition and purchase order through goods receipt, invoice verification, GR/IR reconciliation, and supplier payment—helps SAP professionals troubleshoot issues, improve process control, and support accurate business operations.

For SAP MM learners and consultants, practicing complete business scenarios is an effective way to understand not only individual transactions but also their impact on inventory and finance.

Isun TECHNOVA shares practical SAP learning resources to help professionals strengthen their understanding of enterprise business processes and SAP implementation concepts.

Learn | Implement | Grow

Technical note: This article describes common SAP S/4HANA procurement scenarios. Exact steps, apps, transaction availability, and accounting postings may vary by edition, release, configuration, and procurement type. Always validate the procedure against the relevant system and official SAP documentation before using it in production.