What is Purchase Requisition vs Purchase Order?
Purchase requisition vs purchase order — what's the difference? Learn how these two procurement documents relate to each other and when each is used in the B2B purchasing process.
Purchase Requisition vs. Purchase Order
These two documents are easy to confuse because they both relate to purchasing — but they operate at completely different stages of the procurement process and involve different parties entirely. The key distinction: a purchase requisition is an internal document; a purchase order is an external document.
At a Glance
| | Purchase Requisition | Purchase Order | |---|---|---| | Direction | Internal (employee → organization) | External (buyer organization → vendor) | | Who prepares it | An employee or department needing something | The buying organization's procurement/AP team | | Who receives it | Internal manager, budget approver, or procurement dept | The external seller or vendor | | Legal effect? | None outside the organization | Binding on both buyer and seller once accepted | | Purpose | Request internal approval to purchase | Formally authorize and obligate the purchase | | Seen by freelancer/vendor? | Never | Yes — directly |
The Internal Procurement Workflow
Most medium-to-large organizations have a formal procurement process that goes roughly like this: 1. An employee or department identifies a need — they need a contractor, equipment, software, or services 2. A purchase requisition is submitted — this is the internal ask, typically including: what is needed, why it's needed, expected cost, and budget code 3. The requisition is reviewed and approved — by a manager, budget holder, or procurement team 4. A purchase order is created — once approved, the procurement or AP team issues a PO to the external vendor 5. The vendor receives the PO and accepts it — at this point a legal contract is formed 6. Goods or services are delivered — and the vendor invoices against the PO
Why Freelancers Only See POs
If you're a freelancer or independent contractor, you operate on the outside of your client's procurement process. The purchase requisition is their internal mechanism — you won't see it and it has nothing to do with you directly. What you will see is the purchase order — which is the output of that internal process, translated into an external commitment directed at you. This is actually good news: when a client sends you a PO, it means their internal process has cleared. Someone with budget authority has said yes, allocated funds, and authorized the purchase. Your job at that point is to: - Review the PO carefully - Confirm acceptance - Deliver per the scope and timeline - Invoice with the PO number referenced
Common Scenarios
Scenario 1: The enterprise client A Fortune 500 company's marketing department wants to hire you for a campaign. Their process requires a requisition → approval → PO. You receive a PO with a PO number, line items, and payment terms. You deliver and invoice against that PO. Scenario 2: The small business client A local design studio wants to hire you for a logo project. They don't have a formal procurement process. They send you a quote or contract directly — no requisition, no PO. In this case, the contract itself serves as the authorization. Scenario 3: The nonprofit with grant funding A nonprofit receives a grant specifically earmarked for a consulting engagement. Their grant management policy requires a requisition to draw down grant funds, which converts to a PO once the grant is approved for the specific expenditure. You receive the PO referencing the grant.
The Bottom Line
Purchase requisitions and purchase orders are sequential steps in a formal procurement process — but only the PO crosses the line to the external vendor. As a freelancer, understanding this distinction helps you read client signals: when a PO arrives, it means the client's internal machinery has processed your engagement and authorized payment. Key Takeaways: 1. A requisition is internal — employees use it to request purchase approval 2. A PO is external — sent to vendors to authorize and obligate purchases 3. Only the PO creates legal obligations between buyer and seller 4. Freelancers never see requisitions; they only see POs 5. Receiving a PO means the client's internal approval process has cleared Professional invoicing with PO tracking built in — Try Eonebill Free View Pricing → | Glossary Home → | Home →