PR, PO, and purchase invoice: what each document does, when it matters, and how automating the handoffs between them improves control and cash flow.
|
Quick Summary A purchase requisition (PR) is an internal request for approval to buy something. A purchase order (PO) is the formal, legally binding document sent to the vendor once that request is approved. A purchase invoice is what the vendor sends back after delivering the goods or services, requesting payment. The three documents represent consecutive stages in one workflow: request, commit, pay. |
Introduction
Most finance teams know what these documents are. The confusion tends to surface in practice: who creates which one, at what point, and what happens when a stage is skipped.
This article lays out what each document does, why the sequence matters, and how automating the handoffs reduces errors and keeps finance in control throughout the procure-to-pay cycle.
What Is a Purchase Requisition?
A purchase requisition is an internal document. It does not go to the vendor. An employee or department fills it out with the item needed, estimated cost, vendor preference, and business justification, then submits it for review. The relevant manager, budget holder, or finance team approves or rejects it. Only after approval does the process advance to a purchase order.
The requisition is the control gate. In organisations without it, two problems appear repeatedly: budget overruns nobody saw coming, and invoices arriving for goods finance never knew were ordered.
What a Purchase Requisition Typically Contains
|
Field |
Purpose |
|---|---|
|
Requester name and department |
Establishes accountability and the cost centre |
|
Item or service description |
Tells procurement what is actually needed |
|
Estimated unit cost and quantity |
Allows budget validation before any commitment |
|
Suggested vendor |
Starting point for sourcing; procurement may substitute |
|
Requested delivery date |
Allows lead time to be factored into vendor selection |
|
Business justification |
Required for approval and audit trail completeness |
|
Budget code or cost centre |
Links spend to the correct budget line from the start |
What Is a Purchase Order?
A purchase order is an external document. Once the requisition is approved, procurement issues a PO to the chosen vendor. It locks in agreed pricing, quantities, delivery timelines, and payment terms, and assigns a unique PO number linking the transaction from issuance through to invoice matching and payment. It is a legally binding commitment once the vendor accepts.
That PO number is what makes the rest of the workflow function. When the vendor's invoice arrives referencing it, your AP team can match them automatically. Without it, every invoice requires manual investigation.
What a Purchase Order Typically Contains
|
Field |
Purpose |
|---|---|
|
PO number |
Unique identifier linking the order to the requisition and future invoice |
|
Buyer and vendor details |
Legal names, addresses, contact information for both parties |
|
Line-item descriptions and SKUs |
Precise specification of what is being ordered |
|
Quantities and agreed unit prices |
Locks in commercial terms to prevent billing disputes |
|
Delivery date and address |
Defines fulfilment expectations |
|
Payment terms (e.g. Net 30) |
Establishes when payment is due after invoice receipt |
|
Terms and conditions |
Covers returns, warranties, liability, and dispute resolution |
What Is a Purchase Invoice?
A purchase invoice is the payment request the vendor sends after delivering goods or completing a service. The AP team's job is to verify it before releasing payment: checking that the amount, quantities, and line items match the original PO and the goods receipt. This is three-way matching. Where the documents align, payment is authorised. Where they do not, the discrepancy needs to be resolved first.
In manual AP processes, this verification step is where most of the friction and errors accumulate.
PO Invoice vs. Non-PO Invoice
Not every invoice references a PO. Utility bills, subscriptions, emergency purchases, and low-value one-offs often arrive without one. These non-PO invoices need more manual handling because there is no pre-approved document to match against, which is where duplicate and erroneous payments tend to slip through.
|
Worth noting Summit’s Vendor Invoice Management handles both PO-matched and non-PO invoices in a single workflow. AI-native extraction captures line-item data from PDFs, email attachments, and scanned documents, while automated matching flags discrepancies before they reach the approver. |
Purchase Requisition vs Purchase Order vs Purchase Invoice: Side by Side
|
Purchase Requisition |
Purchase Order |
Purchase Invoice |
|
|---|---|---|---|
|
Who creates it |
Requesting employee or department |
Buyer (procurement or finance) |
Vendor or supplier |
|
Who receives it |
Internal approvers (manager, finance) |
External vendor |
Buyer’s AP team |
|
Legal status |
Internal document, not binding |
Legally binding once vendor accepts |
Legally binding payment obligation |
|
Stage in P2P cycle |
Step 1: Request |
Step 2: Commit |
Step 3: Pay |
|
Key purpose |
Authorise spending internally |
Formalise order with vendor |
Request payment for goods/services delivered |
|
Goes to vendor? |
No |
Yes |
Comes from vendor |
|
Contains PO number? |
No (generates one if approved) |
Yes (origin of PO number) |
Yes (references original PO) |
How the Three Documents Work Together: The Procure-to-Pay Flow
These are consecutive stages in one workflow. Each document triggers the next, with approval checkpoints at each handoff.
|
Stage |
Document |
What Happens |
|---|---|---|
|
1. Need identified |
Purchase Requisition |
Employee submits internal request with justification and estimated cost |
|
2. Internal approval |
Purchase Requisition |
Manager or finance reviews against budget and policy; approves or rejects |
|
3. Vendor engagement |
Purchase Order |
Procurement issues PO to selected vendor with full commercial terms |
|
4. Vendor acceptance |
Purchase Order |
Vendor confirms and begins fulfilment; PO becomes binding contract |
|
5. Goods or services delivered |
Goods Received Note |
Receiving team logs delivery; GRN created for matching |
|
6. Invoice received |
Purchase Invoice |
Vendor submits invoice referencing PO number |
|
7. Three-way match |
PO + GRN + Invoice |
AP verifies alignment; discrepancies flagged for resolution |
|
8. Payment authorised |
Approved invoice |
Finance releases payment per agreed terms |
Where This Process Breaks Down in Practice
The common failure points tend to be the same across organisations.
Skipping the Requisition
When employees go directly to a purchase order, or worse, directly to a purchase, the approval gate is bypassed. Spend that was never budgeted for gets committed. Finance discovers this when the invoice arrives, by which point the obligation already exists. Budget visibility suffers, and the month-end close becomes a cleanup exercise rather than a controlled process.
Manual Three-Way Matching
Manually matching purchase orders, goods receipts, and invoices line by line is time-consuming and error-prone. At scale, it becomes a full-time job. A single high-volume vendor sending 50 invoices a month means 50 separate matching exercises, each with potential for human error. The ACFE reports that billing fraud accounts for around 22% of all occupational fraud schemes, and robust three-way matching is one of the primary controls against it.
Duplicate Invoices
Without automated duplicate detection, the same invoice can be processed and paid twice. A vendor resubmitting an invoice with a slightly different invoice number, or the same invoice arriving through two channels, are both common scenarios. Recovering a duplicate payment typically costs between $1,000 and $1,500 in staff time and bank reversal processes, per incident.
No PO Reference on Invoices
When vendors do not include a PO number on their invoices, every incoming document requires manual investigation. Which PO does this relate to? Was this ever approved? Has it been received? Each question takes time. Across a team processing hundreds of invoices a month, the cumulative overhead is significant.
|
Summit’s Vendor Invoice Management automatically links incoming invoices to the corresponding purchase order, flags line-item discrepancies, and routes exceptions to the right approver. See how it works. |
How Automation Closes the Gaps
AI-powered AP platforms address the handoff failures that create friction at volume.
|
Workflow Step |
Manual Approach |
Automated Approach |
|---|---|---|
|
PR creation and routing |
Email to manager; often informal or inconsistent |
Structured form, auto-routed by department and spend threshold |
|
PO generation |
Finance manually creates PO from approved PR |
System auto-generates PO from approved requisition |
|
Invoice capture |
Email forwarding, manual data entry |
AI extraction from PDF, email, or scanned document |
|
Three-way matching |
Manual line-by-line comparison |
Automated matching against PO and GRN; exceptions flagged |
|
Duplicate detection |
Manual check or missed entirely |
Automated cross-reference by invoice number, amount, and vendor |
|
Approval routing |
Email chains, manual follow-up |
Rules-based routing with escalation for unavailable approvers |
|
ERP posting |
Manual data re-entry |
Direct sync to Xero, QuickBooks, NetSuite, or Microsoft Dynamics |
The benchmark difference is meaningful. Best-in-class AP teams using full automation process invoices for under $3 each. Manual processing costs between $15 and $40 per invoice. For a team handling 500 invoices a month, that gap compounds into a significant annual cost.
A Note for Singapore and APAC Finance Teams
The procure-to-pay flow described above is universal. The compliance layer on top varies by market.
For Singapore-registered businesses, vendor invoices above S$1,000 require a valid tax invoice with the vendor's GST registration number to support an input tax claim. An AP platform that validates tax invoice completeness at the point of capture catches these gaps before they become a GST recovery problem.
For further reading on how invoice management intersects with cash flow, see Summit’s guide on why vendor invoice management is key to cash flow optimisation.
Frequently Asked Questions
What is the difference between a purchase order and a purchase invoice?
A purchase order is issued by the buyer to the vendor before goods or services are delivered. It is a commitment to purchase under agreed terms. A purchase invoice is issued by the vendor to the buyer after delivery, requesting payment. The PO sets the terms; the invoice closes the transaction.
Is a purchase order legally binding?
Once the vendor accepts a purchase order, it becomes a legally binding contract. Before acceptance, it is an offer to buy. The binding nature of a PO is one reason that internal approval via a purchase requisition matters: the financial commitment exists as soon as the vendor accepts.
Can you have an invoice without a purchase order?
Yes. Non-PO invoices are common for utility bills, subscriptions, low-value purchases, and emergency spend. They require more manual handling because there is no pre-approved document to match against. AP teams managing high volumes of non-PO invoices tend to see higher error rates and processing costs unless they have a system that handles them in a structured workflow.
What is three-way matching in accounts payable?
Three-way matching compares three documents before authorising payment: the purchase order, the goods received note (confirming delivery), and the vendor invoice. All three must align on quantities, prices, and terms. Where they do not, the discrepancy is flagged for resolution. Automating this process eliminates the manual line-by-line comparison that consumes significant AP team time at volume.
Do small businesses need a purchase requisition process?
Not always. For organisations where a single decision-maker handles all purchasing, a formal requisition adds little value. Once a business has multiple departments making independent purchasing decisions, the requisition becomes a necessary control. Without it, spend commitments are made without budget validation, and finance loses visibility until the invoice arrives.