Procurement process

Purchase requisition: the start of every purchase

A purchase requisition is the first formal step in buying anything — the internal request that says 'we need this, here's why, and here's the budget it comes from.' It is not an order to a supplier; it is a request for permission to buy. Getting requisitions right is what keeps spend controlled, budgets protected and the rest of the procure-to-pay cycle clean. This guide explains what a purchase requisition is, how it differs from a purchase order, and how to run the requisition process well.

9 min read · Last updated 11 July 2026 · By Lapasar Procurement Technology

In short

A purchase requisition is an internal document a staff member raises to request approval to buy goods or services. It captures what is needed, the quantity, the reason, the budget line and a suggested supplier, then routes for sign-off. It is an internal request — not a commitment to a supplier — and once approved it becomes a purchase order.

What is a purchase requisition?

A purchase requisition is an internal request for approval to purchase something. When a team member identifies a need — new equipment, consumables, a service — they complete a requisition describing what is needed, how much, why, and which budget it should come from. That request then goes to the people authorised to approve spend of that type and size.

The key distinction is that a requisition is internal and a purchase order is external. A requisition asks 'may we buy this?'; a purchase order tells a supplier 'we are buying this.' Nothing is committed to a supplier until the requisition is approved and converted into a purchase order. This separation is what gives the organisation a checkpoint to control spend before money is committed.

A good requisition captures enough detail for an approver to make a decision without chasing information: a clear description, quantity, estimated cost, the budget or cost centre, the business justification, and often a preferred or contracted supplier.

How the requisition process works

The requisition process is the front end of procure-to-pay. Done well, it captures the right information once and routes it cleanly, so approval and ordering are fast.

  • Identify the need: the requester determines what is required and confirms it is not already available internally.
  • Complete the requisition: capture description, quantity, estimated cost, budget line, justification and preferred supplier.
  • Check budget: confirm the spend fits the available budget for that cost centre before routing.
  • Route for approval: the requisition goes to the approver(s) set by the approval matrix and spend thresholds.
  • Approve or query: the approver signs off, rejects, or returns it for more information.
  • Convert to a purchase order: once approved, the requisition becomes a PO issued to the supplier.

Why purchase requisitions matter

The requisition is the control point before money is committed. It is far easier to question, redirect or reject a purchase at the requisition stage than after a supplier has been told to proceed. A disciplined requisition process is how organisations enforce budgets, keep buying on-contract and prevent maverick spend before it happens.

It also creates the record everything else depends on. A clean requisition — with the right budget line, justification and supplier — flows straight into an accurate purchase order and, later, a clean three-way match. Weak or skipped requisitions are a common root cause of downstream problems: budget overruns, off-contract buying and invoices that cannot be matched. Standardising the requisition, ideally through a self-service catalogue where items and prices are pre-approved, removes most of that friction.

Benefits

Spend control before commitment

Approving at the requisition stage stops unwanted spend before any supplier is committed.

Budget enforcement

Tying each requisition to a budget line keeps purchases within the funds available for that cost centre.

A clean downstream record

Accurate requisitions flow into accurate purchase orders and clean invoice matching later.

Less maverick buying

A required requisition step channels purchases through the approved process and on-contract suppliers.

Clear accountability

Every purchase has a named requester, justification and approver, creating a traceable audit trail.

Common challenges

Incomplete requisitions

Missing detail forces approvers to chase information, delaying the whole cycle.

Slow manual routing

Email and paper approvals stall on desks and are hard to track or escalate.

Requisitions that bypass budget

Without a budget check, requisitions can commit spend the cost centre cannot fund.

Being skipped entirely

When the process is cumbersome, staff buy first and paperwork later — defeating the control.

Purchase requisition in practice

A site supervisor needs safety consumables. Rather than calling a supplier directly, they raise a requisition specifying the items, quantities, estimated cost and the maintenance budget line, with a short justification. Because the amount is within the supervisor's manager's authority, it routes to that manager, who approves it the same day. The approved requisition converts into a purchase order automatically.

The difference a good process makes is speed with control. If the items sit in a pre-approved catalogue with contract pricing, the requisition is a few clicks, the cost is already known and correct, and the budget check is automatic — so approval is quick and the resulting purchase order is accurate. Malaysian organisations that move requisitions onto a managed catalogue in this way remove most of the back-and-forth while keeping every purchase inside budget and on-contract. Use the requisition template linked below to standardise the form if you are still on spreadsheets.

Best practices

Standardise the form

Use one requisition format that always captures description, quantity, cost, budget line, justification and supplier.

Check budget before routing

Confirm the spend fits the available budget so approvers are not approving unfunded purchases.

Use catalogue items

Requisitioning from a pre-approved catalogue makes cost and supplier correct by default and speeds approval.

Automate the routing

Route by value and category to the right approver automatically, with reminders and escalation.

Keep it easy

A simple, fast requisition is one people actually use — the surest defence against buy-first-paperwork-later.

Summary

A purchase requisition is the internal request for approval to buy — the control point before any commitment is made to a supplier. It captures the need, cost, budget line, justification and preferred supplier, then routes for sign-off, and once approved becomes a purchase order.

A disciplined requisition process enforces budgets, curbs maverick spend and produces the clean record the rest of procure-to-pay depends on. Standardising the form, checking budget up front, requisitioning from a catalogue and automating routing keep it fast enough that people actually use it.

Key takeaways

  • A requisition is an internal request to buy; a PO is the external commitment.
  • It is the control point before money is committed to a supplier.
  • Good requisitions capture cost, budget line, justification and supplier.
  • Catalogue-based requisitions make cost and supplier correct by default.
  • Keep the process simple or staff will bypass it.

Frequently asked questions

What is a purchase requisition?
A purchase requisition is an internal document raised to request approval to buy goods or services. It records what is needed, the quantity, the estimated cost, the budget line, a business justification and often a preferred supplier, then routes to the people authorised to approve that spend. It is an internal request, not an order to a supplier.
What is the difference between a purchase requisition and a purchase order?
A purchase requisition is internal — it asks for approval to buy. A purchase order is external — it is the formal commitment sent to a supplier once the requisition has been approved. In sequence, an approved requisition is converted into a purchase order; the requisition controls spend before commitment, the PO makes the commitment.
What should a purchase requisition include?
A good requisition includes a clear description of the item or service, the quantity, the estimated cost, the budget or cost centre it draws on, a business justification, the required date, and a preferred or contracted supplier where relevant. Enough detail for the approver to decide without having to chase for more information.
Why is the purchase requisition step important?
It is the checkpoint before money is committed. Reviewing a purchase at the requisition stage lets the organisation enforce budgets, keep buying on-contract and stop unnecessary spend before a supplier is engaged. It also creates the accurate record that downstream steps — the purchase order and three-way matching — rely on.
How can Lapasar simplify purchase requisitions?
With Lapasar, buyers raise requisitions from a pre-approved catalogue where items and contract prices are already set, so cost and supplier are correct by default, budget checks and approval routing are automated, and the approved requisition flows straight into a purchase order. That keeps every purchase inside budget and on-contract across Peninsular Malaysia. A free requisition template is linked below to get started.

Explore related across the knowledge graph

GuideERP integrationConnecting the procurement channel to the ERP so requisitions, orders and invoices flow between systems without manual re-keying.GuideOracle integrationConnecting a supplier catalogue to Oracle procurement and NetSuite through PunchOut so buyers requisition without leaving their system.GuideProcure-to-payThe operational cycle that turns an approved need into a purchase order, a delivery, a matched invoice and a payment.SolutionMicrosoft Dynamics 365 PunchOut in MalaysiaConnect Microsoft Dynamics 365 to the Lapasar marketplace as an external punchout catalog — requisition live items at contract pricing inside D365.SolutionNetSuite PunchOut Integration in MalaysiaConnect NetSuite procurement to the Lapasar B2B marketplace via punchout — requisition live catalogue items at contract pricing inside NetSuite.SolutionPunchout & ERP Integration in MalaysiaConnect Lapasar's B2B marketplace to your ERP via punchout — SAP, Oracle and Coupa. Requisition in your existing workflow with no rekeying.ToolFree Procurement Tools & TemplatesEvery Lapasar procurement calculator plus editable RFQ, purchase order, policy and evaluation templates.TemplateBudget Request FormAn editable Excel and PDF form to itemise, justify and route a budget request for approval.TemplateProcurement SOP TemplateAn editable Word and PDF standard operating procedure covering the buying process from requisition to payment.TemplatePurchase Order Tracker TemplateAn Excel tracker to follow every purchase order from raised to delivered and paid, with automatic status.GlossaryAccounts Payable (AP)Accounts payable (AP) is the money an organisation owes its suppliers for goods and services received but not yet paid for, and the team that manages those payments.GlossaryAccrualsAccruals are accounting entries that recognise expenses which have been incurred but not yet invoiced, so costs appear in the correct period.GlossaryApproval WorkflowAn approval workflow is the defined sequence of authorisations a purchase must pass through before it can proceed, based on rules such as value or category.GuidePunchOut catalogThe catalogue mechanism that lets a buyer shop a supplier's live catalogue from inside their ERP and return a populated requisition.GuideSAP integrationConnecting a supplier catalogue to SAP and SAP Ariba through cXML PunchOut so buyers requisition without leaving SAP.

Put these ideas to work

Talk to our team about consolidating spend, wholesale pricing, credit terms and delivery across Peninsular Malaysia — or request a walkthrough of the marketplace.

Prefer to talk to a real person?

Our team replies fast on WhatsApp and email — no forms, no waiting.