Purchase Requisition Process: From Request to PO

Purchase Requisition Process: From Request to PO

A purchase requisition is the internal request that starts a purchase. Someone says what they need, a manager checks it against budget and authority, and only then does a purchase order go to the supplier. The process works when every request is complete, routed to the right approver and turned into a PO before anyone commits to a supplier. For an equipment dealership that means parts, workshop consumables, tooling and stock purchases all follow one path, not a mix of emails, texts and verbal orders.

This guide walks through each step, the approval checks that matter, the difference between a requisition and a PO, and how AI inside a dealer management system (DMS) or ERP can take the repetitive work out of the loop.

TL;DR

• A requisition is an internal request to buy. A purchase order is the external document sent to the supplier. The PO should always come first, before the commitment, not when the invoice arrives.
• A good requisition names the requester, item, quantity, price, budget code, justification and delivery date. Missing fields cause most of the delays.
• Approval is one control. The receiving and three-way match stage, where PO, receipt and invoice are compared, is the control that protects payment.
• AI in a DMS or ERP is most useful on the repetitive parts: drafting requisitions from low stock, routing, and flagging mismatches before payment.
• MDMS AI is priced at $449 AUD per month, with AI-enabled users at $29 AUD per month per seat.

Table of Contents

• What a purchase requisition is
• The purchase requisition process, step by step
• Requisition vs purchase order
• Who approves a requisition, and what they check
• From approved requisition to purchase order
• After the PO: receiving and three-way matching
• Where the process stalls, and how to fix it
• How AI fits into requisitions in a DMS or ERP
• A worked example: a hydraulic hose for a customer job
• Setting up your own process: a short checklist
• Our perspective
• Put the process into your DMS
• FAQ
• Sources

What a purchase requisition is

A purchase requisition is a formal internal request by an employee to buy goods or services, raised before a purchase order exists. Yale’s purchasing procedure describes it as an internal, department-generated source document required to initiate a PO, carrying the purchase details and the required approvals.

People also call it a purchase request, a PR or a requisition. In everyday dealership language it is the note from the service lead saying the workshop is out of hydraulic filters, or the request from the rental manager for a replacement coupler on a hire attachment. The label matters less than the discipline: the request is written down, approved and traceable.

What every requisition should include

A requisition that gets approved on the first pass is a complete one. At minimum, capture:

• Requester and department, so the approver knows who is asking and which budget is affected.
• Item description and specification, including part numbers where they exist.
• Quantity, unit price and total cost, even if the price is an estimate.
• Preferred supplier, or a note that any approved supplier will do.
• Budget or cost centre, for example workshop consumables or rental fleet maintenance.
• Justification, in one line: replacing stock, a customer job, a warranty repair.
• Required delivery date, so urgency is visible and not argued about later.
• Supporting documents, such as a supplier quote or the work order the purchase relates to.

For dealerships, linking the requisition to a work order, a build order or a customer deal is what separates a useful record from a loose request. It tells the approver why the spend exists and tells accounts which job the cost belongs to.

The purchase requisition process, step by step

The steps are the same whether you run a paper form, a spreadsheet or software. What changes is how much chasing the process needs.

1. Identify the need. A technician, parts counter or manager notices a shortage or a job requirement.
2. Raise the requisition. The requester completes the form with the fields above. Government and university systems typically let you build it from a catalogue or shopping cart, and the requisition is the output at checkout. The NSW Government purchasing guide describes it exactly that way.
3. Submit for approval. The request goes to the relevant manager or approver, who receives it as a task in the workflow system. Flinders University’s finance guide lays out this create, submit, approve sequence.
4. Review and validate. Someone checks budget, supplier, price and whether the need is genuine. Incomplete requests are returned for changes, not quietly fixed.
5. Approve, reject or return. The approver makes a clear decision, and the requester sees the status.
6. Convert to a purchase order. The approved requisition becomes a PO sent to the supplier.
7. Receive and match. Goods arrive, are checked, and the PO, receipt and invoice are compared before payment.
8. Close and record. Documents are kept against the job, supplier and budget.

The NSW guide shows requisitions tracked through states including Incomplete, Pending, Approved, Declined and Cancelled. You do not need those exact labels, but you do need every request to sit in one visible state at any moment. A request nobody can find is the most common reason a process quietly stalls.

Requisition vs purchase order

The two documents are often confused, and the difference is who sees them and what they commit you to.

Yale’s procedure states that a PO is the document sent to the supplier as an offer, and once accepted it forms a legally binding document. The Australian National University makes the same point in its guidance: purchase orders are legally binding, ensure delegate approval happens before ordering, and make future commitments visible as encumbrances. That visibility is the real prize for a dealer. You can see what you have committed to before the invoices land.

In plain terms: the requisition is the question, the PO is the order. MYOB’s procurement guide puts it the same way: an internal purchase request seeks authorisation and, once approved, the company creates the PO detailing the goods and services required.

Who approves a requisition, and what they check

Approval is not a signature for its own sake. The University of Wollongong’s purchasing policy says approvers certify compliance with financial policies and procedures, while purchasing officers confirm sufficient funds, assess preferred suppliers, obtain price and availability information, and apply probity, transparency and fairness.

For a dealership, a workable approval ladder usually looks like this:

• Low value, routine items: the department manager approves, for example the service manager for workshop consumables.
• Mid value or non-routine items: the general manager or operations manager approves, with a quote attached.
• High value, stock commitments or capital items: the owner or finance lead approves.

The exact dollar limits are your decision. Set them in writing, review them as the business grows, and make sure each limit has a named backup so a manager’s leave does not freeze the queue. The NSW guide recommends using the platform’s approval chain and out-of-office feature to avoid approval delays, and the same logic applies in any system.

Checks before approval

• Budget: is there room in the cost centre or job?
• Need: is this stock already on the shelf, or available at another branch?
• Supplier: is it an approved supplier with agreed terms?
• Price: does it match the price list or quote?
• Splitting: has a larger purchase been broken into smaller ones to dodge a limit? The State Library of NSW policy says procurement value is the total cost over the contract term and prohibits splitting purchases into components or successive orders to reduce procurement requirements. Private dealers are not bound by that policy, but the principle is a sound internal rule.

If you want a deeper look at limits and workflow design, our guide to purchase order approvals covers approval tiers and AI checks in detail.

From approved requisition to purchase order

Once approved, the requisition should convert to a PO without retyping. In the Flinders guide, the approved requisition is found under My Purchase Orders, opened as a PO and then sent by print, email or export depending on supplier settings. In the NSW on-account process, approval triggers a PO that is sent electronically to the supplier and copied to the buyer.

The rule that matters most here is timing. Yarra Ranges Council’s procurement policy requires an official PO documenting items, quantities and agreed price, and requires it to be raised and approved before the commitment is made, not when the invoice arrives. A PO raised after the invoice is a record, not a control. Budget and authorisation checks have already been bypassed.

Dealerships have a few special cases to design for:

• Urgent breakdown parts: allow a verbal or phone order only if a PO is raised the same day and the exception is visible.
• Dropship orders: the supplier ships direct to the customer, so the PO needs the customer’s delivery details and the link to the sales order. See our guide to dropship purchase orders.
• Stock replenishment: requisitions can be raised from reorder points, not from someone remembering. Our article on reorder points for parts shows how to set them.

After the PO: receiving and three-way matching

Many teams treat approval as the finish line. It is not. MYOB’s procurement guidance recommends inspecting received goods and comparing the PO, supplier invoice and receipt or packing list in a three-way match, checking quantities, unit costs and total order cost before payment. The practical control point is the receiving and matching stage, because payment should reflect goods actually received at the agreed price.

Australian construction accounts payable guidance applies the same idea to hired equipment, where receipt quantities such as hire days can be verified, and recommends holding invoices that do not align with the PO and goods receipt. The University of Wollongong policy adds that the requisition initiator must confirm goods arrived in good working order or that services were satisfactory, and that POs are receipted in the purchasing system.

A simple receiving routine for a parts counter:

1. Match the delivery docket to the PO line by line.
2. Count and inspect. Note shortages and damage on the docket.
3. Receipt the goods in the system the same day.
4. Let the invoice match automatically where quantity and price agree, and route differences to a person.

If the paperwork vocabulary trips up newer staff, a glossary of procurement acronyms explained is a handy reference to share. For the full matching routine, read our three-way matching guide.

Keep the records. MYOB advises retaining invoices and payment details, including payment date and method, as part of procurement record-keeping. Attach them to the PO so one search finds the full trail.

Where the process stalls, and how to fix it

Most requisition delays come from a handful of causes.

The NSW guide specifically suggests reusing shopping lists for frequently ordered products and tracking requisition status online. Dealer workshops order the same filters, belts, fluids and fasteners again and again, so templates remove a large share of the typing.

How AI fits into requisitions in a DMS or ERP

AI does not replace the approver. It handles the work around the decision, so the approver sees a clean, checked request and decides in seconds. In a DMS or ERP that holds your parts, work orders, suppliers and ledger in one place, there are four natural places for it.

1. Drafting the request. When stock falls below a reorder point, or a work order needs a part you do not hold, AI can assemble a draft requisition: part, quantity, preferred supplier and last price. The requester confirms instead of typing.

2. Pre-approval checks. Before a manager sees the request, AI can compare the price with the last purchase or the supplier’s price list, flag a possible duplicate, check the budget code, and spot a pattern that looks like splitting a purchase to stay under a limit.

3. Routing and nudging. The system can route to the right approver by value and department, remind approvers of waiting requests and use the delegate when someone is away.

4. Matching and exceptions. At receipt and invoice, AI can compare quantities, unit prices and totals, pass clean matches and send only the exceptions to a person. That is where the real money protection sits.

Two cautions keep AI useful. First, it works from your data, so clean supplier records, part numbers and cost centres come first. Second, keep a human decision on anything above your approval thresholds. AI recommends; people with delegated authority approve.

What MDMS AI costs

MDMS publishes its AI pricing. MDMS AI is $449 AUD per month, and each AI-enabled user is $29 AUD per month per seat. That means a dealership can switch AI on for the people who raise and approve requisitions, such as the parts manager, service manager and finance lead, without paying for every seat. Module pricing is separate; see the MDMS pricing page for the current list.

A worked example: a hydraulic hose for a customer job

Here is how the process reads for a mid-sized equipment dealer.

A technician finds a failed hydraulic hose on a customer’s excavator during a service. The work order needs a hose the parts counter does not hold. The parts clerk raises a requisition from the work order, so the part, quantity, customer job and required date are pre-filled. The preferred supplier and last price come from the supplier record.

The service manager gets the request, sees it is within their limit and tied to a booked job, and approves. The system converts it into a PO and sends it to the supplier. When the hose arrives, the clerk receipts it against the PO, the cost lands on the work order, and the supplier’s invoice matches on quantity and price. If the invoice showed a higher unit price, it would be held for a person to review.

No one retyped anything. The cost sits on the right job. The customer can be quoted and invoiced accurately. This is the idea behind our purchase order and supplier management software, where requisitions, POs, receipting and supplier records live alongside parts and service. For the supplier side, see our supplier management operating guide.

Setting up your own process: a short checklist

• Write down approval limits by role and name a delegate for each.
• Make the required fields mandatory: cost centre, justification, delivery date.
• Decide what counts as an urgent exception and how it is recorded the same day.
• Require a PO before supplier commitment, and hold payment on invoices without one.
• Receipt goods on the day they arrive.
• Review exceptions monthly: late approvals, price variances, after-the-fact POs.
• Keep records together: requisition, PO, receipt, invoice and payment.

Our perspective

We built MDMS around a simple idea: data should travel once. A part number entered on a work order should not be typed again on a requisition, again on a PO and again on an invoice. Every retype is a chance for a wrong cost code or a missing approval.

In our experience, dealerships rarely struggle because they lack an approval rule. They struggle because the request lives in one place, the approval in an inbox, the PO in another tool and the invoice in the accounts package. Nobody can see the whole chain, so people chase it by phone.

That is why we think AI belongs inside the DMS and ERP, not beside it. When the system already knows your stock levels, work orders, suppliers and ledger, AI can draft the requisition, check it and route it using the same records your team trusts. We design MDMS AI to take on that repetitive checking so your managers spend their time on decisions.

You can start small. MDMS is modular, with purchasing and parts modules adopted alongside the workflows you already run, and you keep ownership of your data.

ModernDMS

Put the process into your DMS

If your requisitions still travel by email and spreadsheet, start with the module that matches your biggest pain. Purchasing and supplier management, Parts and Warehouse are each listed at published module prices, and you can add MDMS AI when your team is ready for automated checks on requests and invoices. Setup is designed to take under an hour, and you can try it before committing to a monthly rolling plan.

See how it fits your dealership on the MDMS pricing page, or review the full feature list first.

FAQ

What is the difference between a purchase requisition and a purchase order?

A requisition is an internal request asking permission to buy. A purchase order is the external document sent to the supplier, and once accepted it becomes legally binding. The requisition comes first and carries the approvals; the PO carries the agreed items, quantities and price.

Who should approve a purchase requisition?

The person with delegated authority for that budget and value. In a dealership that is usually the department manager for routine items, a general manager for larger ones and the owner or finance lead for stock commitments and capital items. Set limits in writing and name a delegate for each approver.

What information goes on a purchase request?

Include the requester and department, item description, quantity, unit price and total, supplier, cost centre, justification, delivery date and any supporting quote. Linking it to a work order, build order or customer deal gives the approver the context they need.

Can AI approve purchase requisitions?

AI is best used to draft requests, check prices and budgets, flag duplicates and route to the right approver. The approval decision should stay with a person who holds delegated authority, especially above your thresholds. This keeps the speed of automation and the accountability of a named approver.

Sources

• Yale University: Purchase Order Process
• NSW Government Purchasing Guide, October 2025
• Flinders University: Raising Purchase Orders in Tech One
• ANU: Transactional Services Overview
• University of Wollongong: Purchasing and Procurement Policy
• State Library of NSW: Procurement and Contract Management Policy
• Yarra Ranges Council: Procurement Policy
• MYOB: How to Implement Procurement Processes
• Three-way matching in construction AP, Australia
• Procurement acronyms explained

Recommended

• Purchase Order Approvals: Workflow, Limits and AI Checks
• Purchase Order & Supplier Management Software
• Close Returns in 6 Steps: Supplier RMA Process for Procurement Teams
• Dropship Purchase Orders: A Practical Guide for Dealers