FORMAL PURCHASE AUTHORIZATION
Purchase requisition form with the detail reviewers need
Turn an accepted buying need into a complete internal authorization record with quantities, specifications, coding, budget, supplier path, approvers, and a visible outcome.
Unlike a short request form, this template is designed for the formal record reviewers authorize. Line items and decision history stay connected rather than being flattened into one long spreadsheet row.
Free for up to five users. No credit card required.
Adapt fields, workflows, and dashboards without code. Explore 1,000+ app templates and use cases
Inspect the requisition, its line items and every decision
The populated example keeps coding, budget, supplier context, approval history and the PO-ready outcome connected to the same requisition.
Give every reviewer the same facts without one unreadable form
Keep the requisition header, line detail, supporting evidence, and decision log connected but purposeful.
- 01
Header and business justification
Identify the requester, department, original request, required date, urgency, total, category, and outcome the purchase supports.
- 02
Line-item detail
Record item or service, specification, quantity, unit, estimated price, cost center, delivery location, required date, and line status for each requested component.
- 03
Budget and supplier path
Expose available budget, budget owner, existing or new supplier, quote requirements, and any single-source or terms exception.
- 04
Approval and next action
Show the current stage, named approvers, outcome, decision note, due date, next owner, and whether the record is approved, returned, declined, or PO-ready.
Match each field group to its real owner
Ownership makes the form shorter for each role and reduces accidental edits.
| Field group | Who provides it | Who relies on it |
|---|---|---|
| Need and timing | Requester | Department and procurement reviewers |
| Line items and specification | Requester with buyer support | Buyer, approvers, and receiving team |
| Cost center and budget | Department and budget owner | Finance and amount approver |
| Supplier and commercial path | Procurement or buyer | Supplier reviewer and PO approver |
| Outcome and rationale | Assigned approver | Requester, buyer, audit, and downstream teams |
Define completion before the requisition enters approval
Approval time is wasted when the reviewer is asked to discover missing information.
Specification is actionable
A buyer can identify what is being purchased, how much, by when, and which acceptance or service outcome matters.
Value is internally consistent
The line totals support the requisition total and the estimate is current enough for the decision being requested.
Budget owner can decide
The cost center, category, available amount, amount at risk, and exception path are visible before budget approval.
Supplier path is explicit
The requisition says whether the team will use an approved supplier, review a new supplier, compare quotes, or approve a justified exception.
Use this form for formal authorization, not every purchasing record
The requisition is one controlled record in a longer buying process.
Start here when requesters know the required detail
The formal template works well for trained department coordinators or when a short upstream request has already been accepted.
Use the shorter request for casual employee intake
Do not force every employee to choose cost centers, supplier paths, or approval stages merely because the back-office process needs them.
Hand approved data to the authoritative order system
A PO or ERP system may remain responsible for legal order issuance, receipt, accounting, tax, invoice match, and payment.
Preserve the correction without destroying the decision trail
Returned is a controlled state, not a vague rejection or a new email thread.
State the exact correction
Record what is missing or inconsistent, who owns the correction, and when it is due.
Protect reviewer-owned fields
Ordinary request entry should not let the submitter select Approved, rewrite the reviewer rationale, or make the record PO-ready.
Resubmit to the correct stage
The corrected record returns to the decision that failed rather than bypassing budget, department, amount, or procurement review.
Keep previous evidence visible
The team can see the original request, prior outcome, corrected values, resubmission date, and final decision without comparing attachments manually.
Fit the requisition to category, department, and threshold
Jodoo lets administrators change the formal record and approval experience together.
- Show service scope fields for services and quantity fields for goods.
- Require quotes or exception rationale only above the relevant threshold.
- Add department, budget, procurement, or executive approval without duplicating the form.
- Create line-item, returned-work, budget, and PO-ready views from the same records.
Questions about purchase requisition form
Use these answers to decide what belongs on the formal requisition, how line items should be stored, and how returned work should be corrected.
What is a purchase requisition form?
It is the formal internal record used to describe a proposed purchase, document line items and justification, identify coding and budget ownership, route authorization, and preserve the outcome before a purchase order or commitment is created.
What is the difference between a requisition and a purchase order?
A requisition asks the organization for authorization to buy. A purchase order is normally the external or system-of-record order issued to a supplier after internal approval and commercial checks.
Should line items be in a subtable or separate records?
Either can work. Separate connected line-item records improve searching, reporting, ownership, and later reconciliation; a subtable can be simpler for small requests. Choose based on what users need to review and report.
How should returned requisitions be handled?
Record one clear correction, the owner and due date, protect prior decisions, and route the corrected record back to the stage that returned it. Do not make the requester create a disconnected replacement.
Can different categories use different fields and approvals?
Yes. Jodoo can show conditional fields and route workflows by category, department, amount, urgency, supplier path, or exception. Test every supported branch and its permissions before launch.
Inspect a formal requisition, its lines, and its decision history
Open the populated example to see returned, pending, approved, PO-ready, and closed requisitions. Copy the App and adapt coding, line detail, thresholds, reviewer permissions, and downstream handoff.
Open the requisition form