Purchase Requisition Record

This record is one step in a larger programme. Using it for work that belongs to a neighbouring template produces records that are hard to report on later.

The template is built against ISO 9001's control of externally provided processes, products and services, which is broader than procurement paperwork — it asks the organisation to prove the control is proportionate to the risk, not just present.

The template itself is generic, but the control it implements sits inside frameworks that treat a weak or bypassed approval step as evidence of a control failure, not just an administrative gap.

Filling in every field is the easy part. The judgement calls below are what decide whether the record would hold up if someone challenged the approval later.

Patterns that turn up repeatedly when purchase requisition records are reviewed after the fact, usually during an audit or once an invoice dispute forces someone to look back.

A site had an approved supplier for packaging on its preferred supplier list, priced and vetted the previous year. A requester short on time raised a requisition against a different, unvetted supplier they had used before at a previous employer, marked Preferred Supplier Used as No, and left the field beside it blank. Business Justification Stated was answered Yes with a single line: 'urgent need'. The requisition was approved within the hour by a manager who did not query either answer.

Three months and several repeat orders later, the invoice arrived at a rate roughly 20% above the preferred supplier's price, and the new supplier had never been through onboarding or a bank detail check. Nothing on the requisition record was individually false — No really was No, and the need really was urgent — but nothing on it forced anyone to ask why an approved, cheaper option was skipped, which is precisely the gap the field exists to close.

The form is the easy part. Keeping the authority matrix current, routing each requisition to the right approver and holding the evidence together is the work that actually slips.

KnowLogistics

Holds the purchase requisition register alongside Supplier Onboarding and the Contract Register, and flags requisitions that name a supplier who was never actually onboarded.

KnowComply

Tracks the delegated authority matrix, conflict-of-interest declarations and anti-bribery risk assessments the fraud-control programme depends on, and checks each approval against the current version rather than a stale copy.

KnowOps

Routes each requisition to the correct approver by value and category, and chases the ones stalled waiting on a chemical or capital sign-off before spend gets committed anyway.

Ella

Coordinates the crew, rolls completion and exceptions into one view, and holds every write for your approval before it touches a record.

Delegated authority matrix

A table, maintained outside this template, mapping who may approve spend up to what value or in which category. This record checks against it but does not define it.

Committed spend

Money the organisation becomes obligated to pay once a purchase order is placed with a supplier, as distinct from spend that has merely been requested and not yet approved.

Preferred supplier

A supplier already vetted, approved and typically priced for a category, used instead of sourcing and onboarding a new one for every purchase.

Capital approval threshold

The estimated value or category above which a purchase is treated as capital expenditure and routed through a separate capital sign-off rather than routine requisition approval.

Conflict of interest declaration

A statement by the requester or approver of any personal, financial or relationship interest in the supplier being used, made before the requisition is approved rather than discovered afterwards.