Procurement request conversion

Purchase requisition to purchase order conversion audit

A purchase requisition records an internal need; a purchase order communicates an authorized commitment to a supplier. Between them, quantities can split, specifications can drift, approvals can expire and duplicate orders can be created when requesters chase a slow conversion through another channel.

Discuss requisition controls View buyer resources

By MINJI Wholesale DeskUpdated August 9, 2026

Direct answer

The short version

Audit purchase requisition to purchase order conversion by assigning the requisition, line and version, then preserving requester, need-by date, business purpose, item or service specification, quantity, unit, estimated value, currency, delivery location, accounting or budget reference under policy and approval history. Confirm the request is approved for conversion and has not been canceled, superseded or already converted. Link supplier selection, quotation, contract, catalog, sourcing event or approved exception without claiming one universal procurement method. Compare every PO line with the approved requisition: item or scope, specification version, quantity and unit, price basis, currency, destination, delivery date, tax or charges under qualified policy and required terms. When a requisition splits across suppliers, sites, schedules or POs, allocate quantities and values explicitly; when several requisitions consolidate, preserve each source line. Detect duplicate conversion, orphan PO lines, unconverted approved lines, over-conversion, changed specification, unauthorized price or supplier and stale requests. Separate system-created draft PO from approved and transmitted PO. Route differences through requisition amendment or PO approval rather than silently changing the source. Reconcile requested, canceled, converted, ordered and remaining quantity and value. Close only when every requisition line has a supported converted, canceled, rejected or remaining state and every resulting PO line traces back to approved need or an authorized order-only source.

Use this before requesting a quotation

Audit the handoff from internal demand to an external purchase commitment

Capture the requisition baseline

Record requisition and line IDs, version, status, requester, department or project, business purpose, item or service specification, quantity, unit, need-by date, delivery location, estimated value, currency, accounting or budget reference, attachments and created date. Preserve approval route, approvers, times, conditions and thresholds under company policy. Identify whether the request is standard, urgent, blanket-calloff, capital, service, sample or another type. Check for cancellation, replacement, duplicate request and prior conversion. Do not infer budget availability or legal authority from an approved-looking email. Acquisition.gov examples require authorization before specified U.S. federal purchase processes; they are public control examples, not a rule for a private wholesaler.

Confirm sourcing and supplier basis

Link approved supplier, contract, catalog, quote, bid, sourcing event or exception, with validity and scope. Compare supplier legal entity, site or remit-to relationship, product, price basis, currency, lead time, destination and terms. Separate supplier recommendation from final authorized selection. Check supplier master status and bank-change controls without exposing sensitive data. Document competition or exception only as required by the actual company, customer or legal process. A requisition approval may authorize the need but not a supplier or price. Conversely, a contract may set supplier and terms but not authorize this quantity. Preserve both decisions. Recheck quotes that expired or changed before PO creation.

Map requisition lines to PO lines

Create a cross-reference for every requisition line and resulting PO, line and schedule. Support one-to-one, one-to-many and many-to-one conversion with allocated quantity and value. Normalize units and verified pack factors. Compare item, description or specification version, quantity, unit, price, currency, delivery location, required date, buyer entity, supplier and relevant terms. UNECE ORDERS structures order parties, references, lines, quantities, prices, delivery and terms; use it as a data model, not proof of approval. Detect free-text substitutions, changed model, added fee, new destination and rounded quantity. An aggregate PO total can match while line allocation is wrong. Preserve source line identity in downstream receipt and invoice matching.

Control approval and transmission states

Keep draft PO, buyer-reviewed, approved, transmitted, supplier-acknowledged, rejected, changed, canceled and closed as separate states. Confirm the PO follows the approval required for actual supplier, value, currency, category and exception. A requisition approval does not automatically approve a materially changed PO. Prevent transmission before final approval and prevent repeated transmission from creating another order. Store PO version, transmission channel and supplier response. If the supplier proposes changes, use the order-change and acknowledgement process. Separate a system-generated PO number from an external commitment under the actual agreement. Restrict creation, approval and transmission roles proportionately and retain audit records.

Reconcile quantities, values and exceptions

For each requisition line, bridge requested quantity and value to canceled, rejected, converted and remaining. For each PO line, trace the authorized source quantity and value. Identify approved-unconverted backlog, partial conversion, over-conversion, duplicate PO, orphan PO, converted canceled request, wrong supplier, expired quote, price or currency variance, changed specification and interface failure. Record owner and action. Do not clear remaining requisition quantity by editing the original request. If a residual is no longer needed, cancel through authority. If the PO needs more quantity, amend the request or use an authorized order-only process. Review taxes, accounting, commitments and exchange rates with qualified finance owners. Keep estimated and ordered value distinct.

Handle changes, cancellations and failures

When need, specification, quantity, supplier, date, destination or funding changes, record whether requisition amendment, new approval, PO change or cancellation is required. Link old and new versions and prevent both from converting. Cancel open workflow tasks and supplier transmissions deliberately. For interface failure, identify whether the transaction was accepted before retrying. Use idempotency keys or duplicate searches where supported. If one split PO is canceled, return only its supported residual to requisition demand. Do not reopen fully satisfied demand without a new business decision. Preserve urgent manual orders and reconcile them back to a requisition or authorized exception. Test downstream receipt, invoice, commitment and reporting after correction.

Close the audit and improve conversion

Close when every requisition line has a converted, canceled, rejected or valid remaining state; every PO line has an approved source; and quantity and value totals reconcile. Confirm no duplicate supplier order or draft remains. Monitor approval time, approved-to-converted time, unconverted age, partial conversion, duplicate conversion, orphan PO, over-conversion, specification change, supplier change and rejected transmission. Compare by request type and workload before judging performance. Sample POs back to requisitions and approved requisitions forward to POs. Use recurring causes to improve intake fields, specification quality, supplier master, quote validity, approval design, interface idempotency or buyer workload. Never improve cycle time by bypassing authorization or hiding residual requests.

Reusable buyer brief

Requisition-to-PO conversion audit record

Requisition/line/version, requester, purpose, status and need date:
Item/service specification, quantity/unit, destination and attachments:
Estimated value/currency, accounting/budget reference and approval:
Supplier/contract/quote/catalog/sourcing basis and validity:
PO/line/schedule/version and source-line cross-reference:
Requested/canceled/converted/ordered/remaining quantity bridge:
Estimated/approved/ordered/canceled/remaining value bridge:
Item/spec/unit/price/currency/date/destination comparison:
Draft/approved/transmitted/acknowledged/rejected/change state:
Duplicate/orphan/over-conversion/expired quote exception and owner:
Amend/cancel/retry/manual-order action, authority and dependency test:
Bidirectional trace, timing, root cause and closure:

Fill only the details relevant to your request

Before you send the request

Questions buyers often ask

What is checked when converting a requisition to a PO

Check approved need, specification, quantity, unit, supplier basis, price and currency, destination, date, line allocation, approval and duplicate status.

Can one requisition create several purchase orders

Yes when authorized, but allocate each source line's quantity and value across the POs and preserve the remaining balance.

Does an approved requisition authorize every PO change

No. A material supplier, price, quantity, specification, date or destination change may require new approval under the actual policy.

How are duplicate PO conversions prevented

Check existing source-line mappings and transmissions, use controlled idempotent conversion, and reconcile every PO back to one approved source or exception.

Keep the request specific

A requisition approval and a supplier purchase commitment are different control events

Procurement authority, competition, budget, tax, contract formation and approval requirements depend on the organization and jurisdiction. Acquisition.gov sources are U.S. federal examples and do not impose private-company rules. Use qualified procurement, finance and legal review. UNECE ORDERS structures order data but does not prove internal approval or supplier acceptance. Preserve source versions and never convert canceled demand, invent specifications or duplicate an order to solve a workflow delay.

Send this checklist on WhatsApp

Editorial method

How this guide was prepared

MINJI freezes the approved requisition and sourcing basis, maps each source line to PO lines and schedules, then reconciles quantity and value in both directions. UNECE ORDERS supplies external order structure; Acquisition.gov sources supply limited public examples of documented authorization; NIST supports separated access and audit. The workflow retains draft, approval, transmission and supplier response as distinct events.

UNECE UN/EDIFACT — Purchase Order MessagePrimary external order structure covering parties, references, lines, quantities, prices, dates, delivery and terms.
Acquisition.gov — Purchase Request and Approval Sample TemplatePrimary U.S. federal example requiring a documented, routed and signed purchase request before the covered purchase-card process.
NIST — Security and Privacy Controls SP 800-53 Rev. 5Primary control catalog supporting least privilege, separation of duties, audit records and controlled changes.

Ready with the key details

Discuss a wholesale request

Send the product reference, estimated quantity and destination so the conversation starts with useful context.

Continue on WhatsApp