Raise need without rebuilding the PO later.
Purchase requisitions with the fields buyers fill in — catalogue lines, justification, deliver-to, charge dimensions — then convert to RFQ or PO without retyping, carrying detail procurement still needs after the first click.
PR-1042 · 6 lines
Yard bolt restock · Apr
→ PO-1182
PR-1041 · 3 lines
MEP sealant call-off
—
PR-1040 · 2 lines
Filter packs · Plant 2
→ RFQ-088
PR-1038 · 1 lines
Crane hire · structural lift
—
Raising need should not mean starting over.
Procurement fails when the requisition is a disposable form. Continuity — into RFQ, PO, receipt, and bill — is the product.
Need as an email thread
Requests live in inboxes. Quantities, UoMs, and deliver-to get retyped into the PO — and quietly change along the way.
Rebuild at every step
Approved need becomes a blank order form. Line continuity dies; RFQ and bill never know where the ask started.
Converted into nowhere
Status says “converted” with no visible PO or RFQ. The commonest complaint about procurement software — the loop never closes for whoever raised it.
Catalogue lines buyers actually fill.
Lines against governed items and UoMs — plus justification, required-by, and deliver-to — so the ask matches the language stock and the PO already use.
PR-1042 · lines
- 10
MTR-Culvert bolt M16
400 EA · needed Apr 18
- 20
CNV-Sealant 5L
24 CAN · needed Apr 18
- 30
SPA-Filter pack A
12 SET · needed Apr 25
Know what the need is charged to.
Cost center, business unit, region, and account assignments sit on the requisition — so finance and buyers share the charge story before anyone commits a vendor.
Cost center
Who owns the spend — visible on the PR and carried into the PO.
Business unit / region
Org dimensions when cost center isn’t the only charge story.
Account assignment
Line-level charge detail for services, value limits, and project cost.
Clear the ask before spend commits.
Submit for approval, approve or reject with a comment — rejection reasons stay on the record. Governance without a side spreadsheet of who said yes.
Approve
Decision with optional comment — ready to convert to RFQ or PO.
Reject
Reason required — the requester sees why, not a silent status flip.
Approved need becomes the next document.
Convert to PO or seed an RFQ without retyping lines. The requisition keeps a visible outcome so whoever raised it can close the loop.
Convert to purchase order
Open lines become a draft PO — pick the vendor, keep quantities and charge dimensions. No rebuild from scratch.
Derive an RFQ
When you need competition first, the requisition seeds the RFQ so invites start from the same governed lines.
See what it became
Derived POs and RFQs stay linked on the requisition — converted never means “vanished into nowhere.”
Where need started stays visible.
The requisition identity rides forward. RFQ, PO, receipt, and bill still know the ask — so audits and the person who raised it share one path.
PR-1042
Approved need
RFQ-088
Optional compete
PO-1182
Committed order
GR / Bill
Receive & AP
Raise need that survives conversion
Catalogue lines, charge dimensions, approvals, and convert to RFQ or PO — with a visible outcome for whoever asked.