Purchase requisitions: explaining the need before committing money

A requisition explains what the business needs before it commits to a supplier. It gives the approver enough information to judge necessity, specification, urgency and budget. A requisition is an internal request, not a promise to pay an outside party.

DNA requisitions support products, services and custom requests, requester and department, required date, preferred suppliers and cost allocation. Cost-center selection enables budget checking. Specifications are especially important for a custom item that does not yet have an established item record.

An internal request with a business purpose

A requisition gives the organisation an opportunity to evaluate the need before promising money to a supplier. It should explain the intended use, required specification, quantity, timing, and responsible business area.

The level of detail depends on the purchase. A standard replenishment item can rely on established item information. A custom service or special component needs enough description for a buyer and supplier to understand what a satisfactory result looks like.

DNA supports products, services, and custom requests in this process. The distinction is useful because not every legitimate requirement begins with a fully established stock item.

A practical maintenance requirement

Maintenance requests a replacement motor. “Motor, quantity 1” is insufficient: power, mounting, compatibility and needed-by date influence the purchase. The department explains whether the request restores a stopped line or replenishes a spare, helping the approver judge urgency.

Urgency has a cause. A motor needed to restart a stopped line has a different priority from a spare intended for future resilience. The approver needs that explanation to compare the request with other demands on money and purchasing capacity.

Quantity, timing, and cost responsibility

A quantity should have a clear unit and a reason. Ten boxes can mean a very different commitment from ten pieces. A required date should reflect the operational need rather than an arbitrary default.

Cost allocation identifies where the expenditure belongs. DNA's cost-centre relationship can support budget checking and responsibility. A missing or failed budget-check result is not proof that the request is within budget. A budget result helps assess funding, but it does not independently establish whether the specification is correct or the purchase is necessary.

Request and supplier decision

A preferred supplier can provide useful context, especially for compatibility or continuity. It should be distinguished from an already authorised award. Purchasing may still need to compare availability, terms, and alternatives.

The requisition also remains separate from the purchase order. Approval of the internal need allows the procurement process to advance under company policy; it does not by itself prove that an outside supplier has accepted a commitment.

A useful requisition reduces later ambiguity

A well-explained request helps the approver judge necessity, the buyer obtain comparable offers, and the receiving team recognise the intended supply. It reduces the risk of discovering after delivery that everybody interpreted the requirement differently.