You could save up to 25% on transaction costs².
Speak with us now to see if you qualify.
Talk to sales 1-800-515-8366
Monday - Friday, 6 AM to 4 PM PT

Table of contents
Table of contents
Picture a familiar scene: a department orders new equipment. The delivery arrives at a different office than planned, and weeks later, an invoice lands in accounts payable with no record of who approved it or why. These disconnects can compound as you add more vendors, locations, or departments.
Manual processes can add to that friction. In Intuit’s 2026 Late Payments Report, nearly 3 in 4 small and mid-sized businesses surveyed stated they haven't fully automated the way they manage and pay bills. Manual work was also the leading internal reason for delayed outgoing payments.
A procure-to-pay process gives finance earlier visibility into spending and more control over purchasing decisions. Here’s how the process works and how to build a more effective approach.
Procure-to-pay (P2P) is the full sequence a business follows to buy and pay for goods or services. It connects purchasing, operations, and accounts payable. The process starts with a purchase request and approval, continues through ordering and receiving, and ends with invoice review and payment.
A well-managed procure-to-pay process can help businesses:
Businesses don't need a dedicated procurement department to establish a P2P process. The core stages are similar across businesses, but the number of people involved, approval layers, and degree of automation can vary as purchasing complexity grows.
Procure-to-pay (P2P) is the process a business uses to request and approve purchases, order and receive goods or services, verify supplier invoices, and complete payment.
The procure-to-pay process follows a series of steps that take a purchase from initial request through final payment. Below, we break down each step using a hypothetical example of a professional services firm buying 20 laptops at $1,200 each for a group of new hires.
Before an order is placed, the requester puts the basics in writing:
For the laptops, the request totals $24,000:
20 laptops × $1,200 = $24,000
That request enters the system before a single laptop is ordered.
A purchase request is different from a purchase order. The request is an internal document seeking approval to purchase. The purchase order is issued later and sent to the vendor.
Next, the request is checked against the available budget and routed to the appropriate approvers. Approval requirements may vary based on the purchase amount, department, location, or expense type.
For the $24,000 laptop purchase, approval could come from the department head and finance. Set approval thresholds and routing rules so finance can review spending commitments earlier in the purchasing process.
Create a purchase order (PO) with the approved purchase details and send it to the vendor. Include key information such as:
For the example purchase, the PO shows 20 laptops at $1,200 each, for a total of $24,000. Use the PO reference number to track the purchase through receiving, invoicing, and payment.
The PO documents the company's commitment to the purchase. The accounting entries that follow depend on when the goods are received, when the invoice is recorded, and the company's accounting setup.
When the order arrives, check the quantity and condition of the goods against the purchase order and record what was received. For services, this step might involve confirming that an agreed milestone or deliverable was completed.
In our example, only 18 of the 20 laptops arrive:
18 laptops × $1,200 = $21,600 received
2 laptops × $1,200 = $2,400 outstanding
The receiving employee records the shortfall and flags it to the purchase owner, documenting the discrepancy for invoice review.
Compare the purchase order, receiving record, and vendor invoice before approving the invoice for payment. This three-way match helps verify that the purchase was authorized, the goods or services were received, and the invoice reflects the agreed price and quantity.
For the laptop purchase, the records show:
The mismatch indicates that the vendor invoiced the business for two laptops that have not yet been recorded as received.
Accounts payable can investigate the discrepancy and determine the appropriate resolution. Depending on the agreement with the vendor, that might mean requesting a corrected invoice or credit, or confirming that the remaining two laptops are on a separate shipment.
In a mid-market business, purchase approval, goods receipt confirmation, invoice approval, and payment release may involve different people or teams. Keeping these responsibilities separate helps ensure that approving a purchase does not automatically result in an approved payment.
Schedule the approved invoice for payment based on the agreed payment terms and due date, allowing enough time for the payment to process.
Once payment is made, record and link it back to the invoice and supporting records. You now have a traceable record from the original purchase request through final payment to help keep accounts payable records accurate.

More purchasing activity can expose gaps in a procure-to-pay process, especially when requests, approvals, and invoices move between teams or locations. Watch for these common breakdowns:
Each of these breakdowns can create additional work for finance and slow down the purchasing process:

A stronger approval process gives finance oversight without slowing down routine purchases. The following practices can help keep requests moving while maintaining appropriate controls.
Set up one intake route for purchase requests and require a few key details:
Set approval thresholds by dollar amount, name backup approvers, and define an escalation path for urgent requests.
Give routine purchases and exceptions separate paths, too. Approvals can slow down across the business if every request lands on a senior leader’s desk, regardless of size.
Give each purchase a consistent reference number that follows it from the initial request through the PO, receiving confirmation, invoice, and payment. Assign ownership of supplier records and independently verify changes to payment details rather than relying on an email request alone.
With those records linked, reviewers can trace the full history of a purchase without piecing together information from different teams or systems.
Use accounts payable automation to handle repeatable work such as invoice data capture, approval routing, and payment reminders. Reserve manual review for issues that require judgment, including:
Assign a specific owner to each exception type so issues reach the right person and don't remain unresolved.
Track a few measures at key points in the procure-to-pay process to see where requests, invoices, or payments are slowing down. Establish an internal baseline first, then look for recurring patterns that may point to a process problem.
Use the results to focus improvements where they can have the most impact:
As purchasing volume increases, finance needs a reliable way to keep approvals, access, and spending visible. QuickBooks Online Advanced can support those controls by helping teams manage purchase orders, route purchase orders and bills for approval, set user permissions, and report on spending.
That can help businesses:
Stronger purchasing and payment controls can reduce the time finance spends chasing approvals and fixing issues later. Better visibility into spending also gives business owners and finance teams more useful information for managing cash flow, adjusting budgets, and planning ahead.
Accounts payable covers the invoice and payment portion of the process. Procure-to-pay starts earlier, at the point someone requests and approves a purchase, before an invoice even exists.
Procure-to-pay generally focuses on executing purchases and payments, while source-to-pay also includes broader sourcing activities, such as evaluating suppliers and negotiating contracts.
Yes. For service purchases, teams can compare the invoice with the approved scope of work, agreed rates, and confirmation that the work was completed. This might include confirming the completion of a consulting project or documenting a maintenance visit before approving the invoice for payment.