What Is the Purchase-to-Pay (P2P) Process? Steps, Controls and ERP Workflow
Purchase-to-pay (P2P) is the controlled business process that connects purchasing, goods receipt, supplier invoicing, accounts payable and payment settlement. This guide explains the P2P workflow, the documents created at each stage, the controls that prevent errors and how ERP systems keep procurement, inventory and accounting aligned.
A company can have good purchasing staff, a disciplined warehouse and an experienced accounting team and still lose control of supplier spending.
The problem usually appears between departments. Purchasing creates an order. The warehouse receives goods. Finance receives an invoice. Accounts payable schedules payment. If each stage lives in a different file, inbox or system, nobody has one reliable transaction chain showing what was ordered, what arrived, what was invoiced and what remains payable.
Purchase-to-pay solves that problem by connecting the operational and financial stages of supplier purchasing.
A strong P2P process connects purchasing, receiving, inventory, supplier invoices, accounts payable and accounting through one traceable document chain.
Scope of this guide
P2P terminology differs between ERP products and organizations. Some processes begin with requisitions or sourcing, while others begin with an approved purchase order. This guide explains the broader concept first and then clearly separates the workflow currently implemented in Gruvero ERP.
What is the Purchase-to-Pay (P2P) process?
Purchase-to-pay is the end-to-end process used to control a supplier purchase from the purchasing commitment through receipt, invoice validation, accounts payable and settlement.
Depending on the organization, the broader process may also include purchase requisitions, sourcing, supplier selection and bank payment execution. The core P2P transaction chain normally answers five questions:
- What did the company authorize or order?
- What goods or services were actually received?
- What did the supplier invoice?
- What amount does the company owe?
- How was that obligation settled and recorded?
ERP systems are valuable in P2P because these questions are not independent. A receipt can affect inventory before an invoice arrives. A supplier invoice can create an AP obligation. A payment can settle that obligation. Each stage should remain linked to the source documents that created it.
Purchase-to-Pay vs Procure-to-Pay
Purchase-to-pay and procure-to-pay are often used interchangeably. In practice, some organizations use procure-to-pay for a broader process that begins earlier with requisitioning, sourcing or supplier selection, while purchase-to-pay begins closer to the purchase order.
| Term | Typical starting point | Typical ending point |
|---|---|---|
| Procure-to-Pay | Requisition, sourcing or supplier selection | Supplier payment and financial settlement |
| Purchase-to-Pay | Purchase order or purchasing commitment | Supplier payment and financial settlement |
The terminology matters less than the control objective: the business should be able to trace a supplier obligation back to the purchasing and receiving evidence that created it.
The Purchase-to-Pay process in an ERP system
A controlled P2P workflow turns each business event into a source document and connects those documents through inventory, accounts payable and the general ledger.
Step 1: Create the purchase order
The purchase order establishes the purchasing commitment. It identifies the supplier, items or services, quantities, prices, expected delivery, commercial terms and other information required to control the purchase.
The purchase order becomes the reference for later receiving and invoice validation. If quantity, price or supplier terms are wrong at this stage, the problem usually appears again during receipt or invoice matching.
Step 2: Receive the goods
A goods receipt records what physically arrived. The receipt should not simply copy the purchase order quantity. It should capture the quantity actually received and preserve the relationship to the relevant order lines.
For inventory items, the receipt can also affect warehouse quantity and inventory value. That is why receiving is both an operational and a financial event.
Purchase order connected to the goods receipt
This Gruvero ERP example shows the purchase commitment together with the quantity ordered, quantity received and remaining open quantity.
The related posted goods receipt remains directly traceable from the purchase order, connecting the purchasing commitment with the physical receipt.
Step 3: Record inventory and GRNI
Goods can arrive before the supplier invoice. When this happens, the organization already controls the inventory even though the final supplier liability has not yet been recorded from the invoice.
Many accounting models use a goods-received-not-invoiced concept to bridge that timing difference. The receipt creates evidence that inventory has arrived, while the later invoice clears or reclassifies the interim obligation according to the company's accounting model.
We will cover this topic in more depth in a dedicated GRNI guide because it is one of the most important connections between warehouse operations and finance.
Step 4: Record the supplier invoice
The supplier invoice records what the vendor is requesting to be paid. It should remain connected to the purchasing and receiving evidence rather than becoming an isolated AP entry.
Invoice lines may differ from the purchase order because of price changes, freight, partial delivery, tax, quantity differences or other commercial reasons. These differences need to be reviewed before the invoice becomes an approved payable obligation.
Vendor invoice linked to the source goods receipt
This Gruvero ERP example shows a posted supplier invoice connected to the goods receipt that supports the invoiced quantity.
The invoice preserves the supplier, source GRN, quantity, unit price and amount so the financial document remains traceable to receiving evidence.
Step 5: Perform three-way matching
Three-way matching compares the purchase order, goods receipt and supplier invoice.
The match asks whether:
- the supplier invoiced an authorized purchase
- the invoiced quantity is supported by receiving evidence
- the invoice price is consistent with the purchase order
- the invoice should be approved or investigated
Our detailed guide to three-way matching explains how the purchase order, receipt and invoice work together.
Step 6: Create the accounts payable obligation
Once an invoice has passed the required controls, the amount becomes an accounts payable obligation. The system should preserve the open item, due date, supplier, currency, original document and outstanding balance.
This is the point where operational evidence becomes a financial obligation that the company can schedule and settle.
Supplier invoices become traceable AP open items
Gruvero keeps each open supplier obligation connected to its source invoice, outstanding balance and due date.
AP open items provide a controlled view of supplier obligations before payment and internal settlement.
Step 7: Settle the payable
Accounts payable records the payment or settlement against the open supplier obligation. A strong process does not merely reduce a supplier balance; it identifies exactly which open item or items were settled and preserves the payment reference.
Step 8: Preserve remittance and accounting evidence
The process should end with a clear financial and audit trail showing the original purchase, receipt, invoice, payable item and settlement.
Payment execution itself may occur through an external bank or payment platform. The ERP should still preserve the internal settlement and remittance information needed to explain which supplier obligations the payment covers.
Where Purchase-to-Pay processes break
Purchase orders are created after the fact
If the order is created only after goods arrive, it no longer acts as a meaningful purchasing control. Matching becomes documentation after the event rather than validation against a prior commitment.
Goods are received without a source order
Receiving without a reliable purchase reference makes it harder to validate quantities, expected prices and supplier terms.
Invoices reach finance before receipts are posted
This creates timing differences between the warehouse and accounting. Finance sees the supplier claim while the system still has no evidence that the goods arrived.
Invoice differences are resolved through email
When price and quantity disputes are handled outside the ERP, the final invoice may be approved without preserving why the difference was accepted.
Payments are detached from open items
A payment should close specific obligations. If settlement is recorded as a general supplier balance change, later reconciliation becomes much more difficult.
Warehouse and accounting maintain separate truth
When goods receipt, inventory value and supplier liabilities are not connected, month-end reconciliation becomes a manual exercise. This is one reason warehouse and accounting records can disagree.
Manual P2P vs ERP-controlled P2P
| Area | Manual or disconnected process | ERP-controlled process |
|---|---|---|
| Purchase order | Spreadsheet, email or standalone purchasing tool | Structured source document linked to later events |
| Goods receipt | Warehouse records quantity separately | Receipt updates operational records and remains linked to the PO |
| Invoice validation | Manual comparison across documents | PO, receipt and invoice evidence can be matched in one workflow |
| Accounts payable | Re-entered into accounting | Approved invoice becomes a traceable open payable item |
| Settlement and audit | Bank, spreadsheet and accounting records reconciled later | Settlement remains connected to the supplier obligation and audit history |
This is one of the points where companies often outgrow spreadsheet-based operating control.
Key controls in Purchase-to-Pay
Controlled purchase orders
A purchase order should be created before the receipt and contain the commercial terms required for later validation.
Receipt against the correct order lines
The warehouse should record what actually arrived and link each receipt to the purchasing commitment it fulfils.
Three-way matching
Supplier invoices should be compared with the relevant order and receiving evidence before becoming payable.
Segregation of duties
The same user should not automatically control every stage of a material supplier transaction. Permissions should reflect the organization's risk and approval policy.
Open-item settlement
Payments should identify which supplier obligations they settle rather than only changing a total balance.
Document-level audit history
Users should be able to trace the supplier obligation back through the invoice, receiving evidence and purchasing document.
Purchase-to-Pay example
Consider a distributor purchasing 100 units of Item FG-4200 from a supplier at an agreed unit price.
- A purchase order is created for 100 units.
- The supplier delivers 96 units and the warehouse posts the goods receipt.
- Inventory increases based on the verified receipt.
- The supplier later invoices 100 units.
- Three-way matching identifies a four-unit quantity difference.
- The invoice requires investigation before the full amount can become payable.
- Once the accepted amount is posted, AP records the supplier obligation.
- A later AP payment settles the relevant open item and preserves remittance evidence.
The value of the P2P chain is not that each department completed its own step. The value is that the system can explain the relationship between the purchase commitment, physical receipt, supplier claim and financial settlement.
How Gruvero approaches Purchase-to-Pay
Gruvero currently approaches Purchase-to-Pay as a connected flow beginning with the purchase order and continuing through receiving, supplier invoice control, accounts payable and internal settlement.
The implemented Gruvero flow includes:
- Purchase Order
- Goods Receipt
- Inventory and GRNI accounting consequences
- Supplier Invoice
- Three-Way Matching
- AP Open Item
- AP Payment
- Internal Settlement
- Remittance Data
Each stage is intended to preserve the relationship between operational documents and financial evidence instead of requiring users to reconstruct the transaction later from spreadsheets or email.
Gruvero connects purchasing, goods receipt, inventory, supplier invoicing and accounts payable in one traceable P2P chain. External bank execution remains outside the ERP, while Gruvero preserves the internal AP settlement and remittance information.
FAQ
What does Purchase-to-Pay mean?
Purchase-to-Pay is the end-to-end process that connects a purchasing commitment with goods receipt, supplier invoice validation, accounts payable and financial settlement.
What are the main steps in the P2P process?
The core steps typically include purchase order creation, goods receipt, supplier invoice processing, invoice matching, accounts payable and payment settlement. Broader procure-to-pay models may also include requisitioning and sourcing.
What is the difference between Purchase-to-Pay and Procure-to-Pay?
The terms are often used interchangeably. Some organizations use Procure-to-Pay for a broader process beginning with requisition or sourcing, while Purchase-to-Pay begins with the purchasing commitment or purchase order.
What is three-way matching in P2P?
Three-way matching compares the purchase order, goods receipt and supplier invoice to determine whether the supplier claim is supported by the authorized purchase and receiving evidence.
What is GRNI in Purchase-to-Pay?
GRNI, or goods received not invoiced, represents the timing gap created when goods have been received but the supplier invoice has not yet been processed. It helps connect the physical receipt with the later supplier liability.
Why is P2P important for inventory companies?
Inventory-heavy businesses need purchasing, receiving, stock value, supplier invoices and AP to remain aligned. A disconnected P2P process can create quantity differences, valuation errors, duplicate invoices and difficult month-end reconciliation.
Does an ERP system execute supplier bank payments?
It depends on the ERP and integration model. Some systems execute or transmit payments directly, while others create and settle AP records internally and leave bank execution to an external banking or payment platform.
How does Gruvero support Purchase-to-Pay?
Gruvero's currently implemented P2P flow connects purchase orders, goods receipts, inventory and GRNI consequences, supplier invoices, three-way matching, AP open items, AP payments, internal settlement and remittance data. External bank execution is outside Gruvero.
Conclusion
Purchase-to-Pay connects supplier purchasing with the operational and financial evidence created after the order.
A controlled process should show what was ordered, what was received, what the supplier invoiced, what became payable and how that obligation was settled.
When these stages are disconnected, procurement, warehouse and finance can each hold a different version of the same transaction. ERP creates value by keeping the source documents, inventory consequences, AP records and accounting evidence connected.
Purchase-to-Pay works best when every supplier obligation can be traced back to the purchasing and receiving evidence that created it.
If your P2P process currently depends on spreadsheets, email or separate purchasing and accounting records, the Gruvero Pilot Program can help you evaluate one connected workflow before a broader ERP implementation.
Related ERP topics
Connect purchasing, receiving, supplier invoices and AP in one controlled workflow.
Request pilot access to evaluate how Gruvero connects purchase orders, goods receipts, supplier invoices, three-way matching, AP open items and settlement in one traceable process.
Check pilot fit