The Procure-to-Pay (P2P) process is the backbone of any organization's supply chain and financial operations. It encompasses every step from identifying a need for materials or services to finalizing the payment to the vendor.
In SAP S/4HANA, the P2P process has been significantly optimized. With features like the Fiori user interface, embedded analytics, and seamless integration between Materials Management (MM) and Financial Accounting (FI), the process is faster, more transparent, and less prone to manual errors.
The 6 Core Steps of the SAP P2P Process
While specific company configurations may add approval workflows or custom steps, the standard end-to-end P2P cycle in SAP S/4HANA consists of six fundamental stages:
Determination of Requirements (Purchase Requisition)
The process begins when a department realizes it needs a specific material or service. This need is documented in a Purchase Requisition (PR).
- How it happens: A PR can be created manually using
ME51Nby a user (e.g., a manager requesting office supplies) or automatically by the system. Automatic creation usually happens during a Material Requirements Planning (MRP) run when inventory falls below a specified reorder point. - S/4HANA Fiori App: Manage Purchase Requisitions or Create Purchase Requisition.
- Key Data: Material number, quantity required, desired delivery date, and the requesting plant or cost center.
- Financial Impact: None. A PR is internal and does not impact accounting.
Source Determination and Vendor Selection
Once the PR is approved, the purchasing department must decide who to buy the materials from.
- Sourcing Options: The buyer checks the system for existing sources using tools like Source Lists, Purchasing Info Records, or Outline Agreements (Contracts and Scheduling Agreements).
- Request for Quotation (RFQ): If no source exists, the buyer creates an RFQ using
ME41and sends it to multiple vendors. - Quotation Evaluation: Vendors submit their quotes. The buyer enters these prices into SAP using
ME47and uses the Compare Quotations app to select the best vendor based on price, delivery time, and reliability.
Purchase Order (PO) Processing
With the vendor selected, the internal PR is converted into an external, legally binding document: the Purchase Order (PO).
- How it happens: The buyer references the PR, RFQ, or Contract to generate the PO using
ME21N. This transfers all relevant data without manual re-entry. - S/4HANA Fiori App: Manage Purchase Orders.
- Release Strategy: Before the PO is sent to the vendor, it often goes through an electronic approval workflow based on its total value (e.g., POs over $10,000 require manager approval).
- Financial Impact: Creating a PO generates a commitment in the Controlling (CO) module, reserving the budget, but no actual FI posting occurs yet.
Goods Receipt (GR)
When the vendor delivers the materials to the warehouse, the receiving team verifies the delivery against the Purchase Order.
- How it happens: The warehouse clerk enters the PO number into
MIGOand posts a Goods Receipt. The standard movement type is 101 (Goods receipt for purchase order). - S/4HANA Fiori App: Post Goods Receipt for Purchasing Document.
- System Updates: Inventory quantities are immediately updated in the Material Master.
- Financial Impact: This is a crucial financial step. The system automatically debits the Inventory Account and credits the GR/IR (Goods Receipt/Invoice Receipt) Clearing Account. A Material Document and an Accounting Document are generated.
MIGO with movement type 102) to undo it. Always verify quantities before posting.Invoice Verification (MIRO)
The vendor sends an invoice requesting payment. The accounts payable (AP) team must verify that the invoice matches what was ordered and what was actually received.
- The 3-Way Match: SAP automatically compares the Purchase Order (what was requested), the Goods Receipt (what arrived), and the Invoice (what is being billed).
- S/4HANA Fiori App: Create Supplier Invoice or Manage Supplier Invoices.
- Tolerance Limits: If the invoice amount slightly differs from the PO (e.g., due to minor shipping costs), SAP can accept it if it falls within predefined tolerance limits. If outside the limits, the invoice is blocked for payment.
- Financial Impact: Upon successful posting, the system debits the GR/IR Clearing Account (clearing it out) and credits the Vendor Account (Accounts Payable).
Payment Processing
The final step in the P2P cycle is paying the vendor.
- How it happens: This is handled by the Finance (FI) module. The system looks at the baseline date and payment terms defined in the vendor master record to determine when the payment is due.
- Automatic Payment Program (
F110): Most companies use the automatic payment program to process payments in batches via bank transfers, checks, or other methods. - Financial Impact: The system debits the Vendor Account (clearing the liability) and credits the Bank Account.
Why S/4HANA Makes P2P Better
| Feature | The S/4HANA Advantage |
|---|---|
| Ariba Integration | Native integration with the SAP Ariba Network allows POs and Invoices to be sent back and forth electronically, eliminating manual data entry. |
| Embedded Analytics | Purchasing managers can view real-time KPIs directly on their Fiori Launchpad, such as "Overdue Purchase Orders" or "Off-Contract Spend." |
| Universal Journal (ACDOCA) | All financial postings during Goods Receipt and Invoice Verification are stored in a single table, ensuring absolute reconciliation between MM and FI. |
| Business Partner Framework | Vendors are now centrally managed as Business Partners, ensuring cleaner master data and easier compliance management. |
Key Takeaway
The SAP P2P process covers everything from identifying a need to paying the supplier. The core documents are Purchase Requisition (Internal), Purchase Order (External), Goods Receipt (Logistics), and Invoice (Financial). Financial postings occur during two specific steps: Goods Receipt (updates inventory value) and Invoice Verification (creates vendor liability). The GR/IR clearing account acts as an essential bridge between the arrival of goods and the arrival of the invoice.
