How Education Works | Education Purchase Requisitions, Purchase Orders & Receiving Controls — How a Need Becomes an Authorised Commitment Before It Becomes a Bill

HEW-NODE-0206 · How Education Works · Purchase requisitions, purchase orders and receiving controls

A school needs twenty laptops.

That sentence sounds like the beginning of procurement. In a well-controlled education system, it is still only the beginning of a question.

Who decided twenty? What problem are the laptops solving? Is money available? Is there already a contract? Which specification applies? Does the person requesting them have authority? Has demand been split to avoid a threshold? Is the supplier legitimate? When the boxes arrive, who confirms there are twenty rather than eighteen? Are they the model ordered? Were two damaged? Did the school receive them before the invoice arrived? Which record tells accounts payable that the invoice represents something actually authorised and delivered?

This is the job of the purchase requisition → purchase order → receiving control chain.

This node has a deliberate boundary. Education Procurement Bid Evaluation, Conflict-of-Interest & Award Governance owns formal tender evaluation and award. Education Procurement Framework Agreements & Dynamic Purchasing Systems owns repeated competitive purchasing vehicles. Education Contract Management, Service Levels & Vendor Exit Planning owns post-award contract performance. Education Accounts Payable, Invoice Verification & Payment Controls owns the invoice-to-payment end of the chain. Education Budget Execution, Commitment Controls & Virements owns budget authority and commitment control at system level. This page owns the operational bridge in between: how a school need becomes an authorised order and how physical or service receipt becomes trustworthy evidence before payment.

Quick Answer

Identify the genuine need → check whether stock, contract or shared service already satisfies it → define quantity and specification → create a requisition → confirm budget and coding → route approval under delegated authority → select the lawful procurement route → verify supplier master data → issue a uniquely numbered purchase order or equivalent commitment → send the order to the supplier → monitor delivery → inspect quantity, quality and condition → record goods or service receipt → quarantine discrepancies → return, reject or accept partial delivery as appropriate → update inventory or asset records → make receiving evidence available for invoice matching → close residual commitments when the order is complete → analyse exceptions, late orders and retrospective purchases to improve the process.

The central principle is simple: the system should know what it authorised before the supplier acts, and know what it received before the supplier is paid.

The Requisition Is the Internal Request to Buy

A requisition is not normally the supplier’s order. It is the organisation’s internal statement that a need exists and permission is requested to commit resources.

A useful requisition identifies:

• requesting school or department;
• requester;
• purpose;
• item or service description;
• quantity;
• required date;
• delivery location;
• estimated cost;
• budget or cost centre;
• suggested supplier where allowed;
• existing contract or framework reference;
• technical specification;
• approvals;
• and any conflict, safety, data or accessibility considerations.

The requisition turns “we need this” into something reviewable.

The First Question Is Often: Do We Need to Buy Anything?

Before going to market, the system can check:

• is the item already in central or school stock?
• can another school transfer surplus?
• is the requirement covered by an existing contract?
• is there a shared service?
• can existing equipment be repaired?
• does standardisation make another specification preferable?
• is rental or service provision better than ownership?

Good procurement begins by validating the need, not merely processing a request faster.

Specification Determines What the System Will Actually Receive

“Buy twenty laptops” is not a specification.

Processor, memory, storage, screen, accessibility, warranty, operating system, security, charging, repair support, delivery and imaging can all matter.

For textbooks, the edition matters. For laboratory chemicals, grade, quantity and safety documentation matter. For cleaning services, service frequency and quality standards matter. For training, learning outcomes and participant numbers matter.

Weak specification creates disputes later because the supplier can deliver something that technically satisfies a vague order but does not solve the educational problem.

Do Not Over-Specify Around One Brand Without a Valid Reason

A specification can become disguised supplier selection if it contains unnecessary features only one product can meet.

Public procurement principles emphasise competition, value for money and integrity. Where a brand, compatibility requirement or single-source justification is genuinely necessary, the reason should be documented.

Accessibility Belongs in the Specification

Accessibility should not be tested only after a digital platform, textbook format or physical device has been bought.

If learners or staff need accessible interfaces, captions, keyboard navigation, screen-reader compatibility, adjustable furniture or other features, those requirements belong in the purchasing definition.

Safety Belongs in the Specification Too

Laboratory equipment, playground equipment, electrical devices, furniture and chemicals can introduce hazards.

The requisition should identify safety standards, certifications, material restrictions or installation requirements before purchase rather than expecting facilities staff to repair a bad specification later.

Budget Check Comes Before Commitment

An approved annual budget does not mean every individual purchase is affordable at every moment.

The requisition should check available budget, existing commitments and the correct account code before an order becomes binding.

This links directly to Education Budget Execution, Commitment Controls & Virements: a purchase order often becomes one of the operational records showing that part of the approved budget is already committed.

Approval Is About Authority, Not Seniority Theatre

Organisations often use delegated financial authority: different roles can approve different values or categories.

A good approval matrix defines:

• value thresholds;
• category restrictions;
• capital versus operating expenditure;
• emergency authority;
• conflict-of-interest rules;
• who may approve for whom;
• and whether technical approval is separate from financial approval.

The goal is not to make every pencil purchase reach the director-general. It is to place decisions at the lowest level consistent with risk and accountability.

The Requester Should Not Approve Their Own High-Risk Purchase

The 2025 U.S. GAO Green Book emphasises effective internal control and preventive controls over public resources. A long-standing internal-control principle is segregation of duties: no one person should control all key aspects of a transaction.

In practical school purchasing, this often means separating at least some of these roles:

• request;
• approve;
• select supplier;
• receive goods;
• record inventory;
• approve invoice;
• release payment.

Small schools may not have enough staff for perfect separation. Compensating review can reduce risk.

Thresholds Create Behaviour

If purchases above $10,000 require competition, there is a temptation to split one $18,000 need into two $9,000 orders.

Policies should prohibit artificial splitting and systems can flag repeated same-supplier purchases, same-day orders or related requests just below thresholds.

Aggregation Can Improve Value and Reduce Work

Ten schools independently buying the same paper, laptops or cleaning supplies may create ten procurement processes and weaker pricing.

Demand aggregation can support central contracts or framework agreements when needs are sufficiently common. Local flexibility may still be appropriate for specialised requirements.

The Purchase Order Is the Authorised Instruction to the Supplier

Once the need, budget, approvals and procurement route are satisfied, the purchase order—or equivalent contract document—states what the organisation is actually ordering.

A strong PO typically includes:

• unique order number;
• supplier legal name and identifier;
• delivery address;
• invoice address or portal;
• item or service lines;
• quantity and unit price;
• tax treatment;
• total authorised amount;
• contract or framework reference;
• delivery date;
• payment terms;
• shipping terms where relevant;
• contact details;
• and applicable standard terms.

The PO is both an operational instruction and an internal commitment record.

Unique PO Numbers Create Traceability

The same number can connect requisition, approval, supplier correspondence, receiving note, invoice and payment.

Without a stable identifier, staff spend time reconstructing which invoice belongs to which order and which delivery completed which request.

“No PO, No Pay” Can Strengthen Control—If the Organisation Makes Ordering Usable

Some organisations refuse invoices without a valid PO except defined exceptions.

This discourages staff from making unauthorised commitments and asking finance to regularise them later.

But if the requisition process is painfully slow, operational staff may bypass it to keep schools running. Control design has to be both strong and usable.

Retrospective Purchase Orders Are a Warning Signal

A retrospective PO is created after goods or services were already ordered or delivered.

Sometimes an emergency justifies it. Repeated retrospective orders suggest that staff are committing public money before approval, turning the control into paperwork after the fact.

Supplier Master Data Is a Financial Control

The purchase order must point to the correct legal supplier and payment record.

Supplier setup should verify identity, tax or registration information as applicable, bank details, contact information and duplicate records. Changes to bank accounts are particularly sensitive to fraud and should use independent verification.

The Requester Should Not Be Able to Invent a Supplier and Pay It Alone

Supplier creation, order approval and payment are high-value controls. Combining all three in one user account creates avoidable fraud risk.

Purchase Orders Can Be Standard, Blanket or Call-Off

A one-off order may specify exact quantity and delivery.

A blanket or call-off order can cover repeated purchases from an existing contract up to a value or period. This reduces administrative work but needs quantity, price and duration limits.

The procurement vehicle should match purchasing frequency and risk.

Open Purchase Orders Need Management

An order for $50,000 remains a commitment even if only $20,000 has been delivered so far.

Systems should show open quantity, open value, expected delivery and aged commitments. Old orders may need closure so budgets are not artificially blocked by commitments that will never materialise.

Change Orders Need the Same Discipline as Original Orders

A supplier may propose more quantity, changed specification or increased price.

If the change is material, it may require new approval or even a new procurement process depending on rules. Purchase-order amendment should preserve version history rather than silently overwrite the original commitment.

Emergency Purchasing Needs a Fast Legal Lane

A burst water pipe, urgent safety repair or disaster response may not allow ordinary lead times.

Emergency procedures can allow accelerated approval, limited competition or retrospective documentation where law permits. They should define what qualifies as an emergency, who can authorise, spending caps and what post-event review is required.

Emergency is a condition, not a procurement style.

World Bank Procurement Rules Emphasise Value, Integrity and Fit-for-Purpose Process

The World Bank’s seventh edition of the Procurement Regulations for IPF Borrowers, issued in September 2025, continues the framework’s focus on value for money, integrity and procurement approaches suited to risk and need. The Bank’s current Procurement Framework page also lists a July 2026 procedure update.

School systems do not need to copy World Bank project rules into routine local purchasing. The useful principle is broader: controls should match value, complexity and risk rather than force every purchase through the same method.

OECD’s 2025 Public Procurement Review Emphasises Risk Across the Full Cycle

OECD’s 2025 report on implementation of its Recommendation on Public Procurement highlights risk management throughout the procurement cycle, including administrative mistakes, deliberate transgressions, supply-chain risks, IT risks and other threats to procurement outcomes.

That is important for schools: the risk does not disappear after supplier selection. Requisition, ordering, delivery, receipt and payment are all part of the cycle.

Receiving Is an Independent Control Point

The supplier says twenty laptops were delivered.

The invoice says twenty.

The school still needs to count.

Receiving confirms what physically or operationally arrived. It protects against short delivery, wrong items, damaged goods and invoicing for something never received.

The Receiver Needs the Purchase Order

Without the order, the receiver does not know what to inspect.

Receiving staff should be able to compare delivery against ordered item, quantity, model, packaging, condition and required documents.

Blind Receiving Can Reduce Confirmation Bias

Some control systems hide the expected quantity from the receiver, requiring an independent count before comparison.

This can reduce the tendency to see what the PO says rather than what physically arrived. It is more useful for some categories than others.

Goods Receipt Should Be Recorded Promptly

If goods arrived on Monday but receiving is entered Friday, an invoice may be blocked unnecessarily or an item can disappear before it reaches inventory.

Prompt receipt records improve accounts payable, inventory and supplier-performance data.

Partial Delivery Is Normal and Needs Good Records

The school orders 500 textbooks. Three hundred arrive today and two hundred next week.

The system should record 300 received, 200 open, and only permit invoice matching according to the contractual terms. Closing the whole PO on the first shipment creates either missing books or payment errors.

Over-Delivery Needs a Decision

A supplier sends 520 textbooks against an order for 500.

The school should not simply keep them and pay. Policy may permit a small tolerance; otherwise the extra quantity may require rejection, PO amendment or authorised acceptance.

Damaged Goods Need Quarantine

If five laptops arrive with crushed screens, they should not be recorded as fully usable inventory.

The receiving note can record accepted quantity, rejected quantity, damage evidence and return instructions.

Returns Need Reverse Traceability

A returned item should remain connected to the original PO and receipt so accounts payable knows whether a credit note, replacement or reduced invoice is expected.

Service Receipt Is Harder Than Goods Receipt

You can count chairs. How do you receive a consultancy report, cleaning month, teacher-training session or software subscription?

Service receipt should reference deliverables:

• session delivered;
• participants served;
• milestone completed;
• report accepted;
• uptime achieved;
• cleaning inspection passed;
• licensed users activated;
• or another measurable service condition.

“Invoice received” is not evidence the service was delivered.

The Technical Receiver May Differ From the Physical Receiver

A warehouse clerk can confirm that twenty boxes arrived. An ICT specialist may need to confirm that the devices match the technical specification and power on correctly.

For complex goods, acceptance can be staged: physical receipt first, technical acceptance second.

Installation Can Be Part of Acceptance

A laboratory machine may be delivered but not yet installed, calibrated or trained for use.

If contract payment depends on commissioning, goods receipt should not accidentally signal full contractual acceptance before installation is complete.

Asset Registration Should Follow Receiving

Durable equipment may need asset tags, serial numbers, assigned location and custodian.

The separate Education Fixed Asset Registers, Inventory Verification & Disposal Controls page owns the asset lifecycle. Receiving should hand over clean acquisition data so that lifecycle can begin.

Consumable Inventory Follows a Different Route

Paper, cleaning products, laboratory consumables and teaching materials may enter stock rather than the fixed-asset register.

The receiving event should update the appropriate inventory system so stock is visible before further requisitions are raised.

Three-Way Match Connects Order, Receipt and Invoice

The classic control compares three records:

1. purchase order — what was authorised;
2. goods or service receipt — what was received;
3. invoice — what the supplier wants to be paid.

If quantity, price and terms agree within authorised tolerances, accounts payable can process efficiently. If not, the transaction becomes an exception.

This is where the process hands off to Education Accounts Payable, Invoice Verification & Payment Controls.

Two-Way Match Can Be Appropriate for Some Transactions

Not every purchase requires physical receipt. Certain rent, utilities or subscription invoices may be matched against contract or PO and other service evidence rather than a traditional goods receipt.

Control design should reflect what constitutes evidence of delivery.

Tolerances Reduce Pointless Exceptions

A supplier invoice may differ by a few cents due to rounding or an approved minor quantity variation.

Systems can define tolerances by category and value. Tolerances should be small enough to protect control and visible enough not to become hidden authority for price changes.

Exceptions Need Ownership

If the invoice price is higher than the PO, who resolves it? If fewer goods arrived, who contacts the supplier? If the receiver entered the wrong quantity, who corrects the receipt?

An exception queue should route by cause rather than leave invoices stranded between procurement, school and finance.

Duplicate Purchase Orders and Duplicate Invoices Are Different Risks

Duplicate POs can overcommit budget or result in duplicate delivery. Duplicate invoices can create duplicate payment.

System checks should address both but not confuse them.

Catalogues Can Standardise Routine Purchasing

Approved e-catalogues let schools select common goods from pre-negotiated suppliers and prices.

This reduces specification work and off-contract buying while preserving requisition, approval and receiving controls.

But Catalogues Can Freeze Bad Standards

If approved products are inaccessible, obsolete or poor quality, catalogues can scale the wrong choice.

Usage data, returns, incident reports and user feedback should inform catalogue review.

Procurement Cards Need Separate Rules

Low-value purchasing cards can reduce transaction cost but bypass traditional POs.

Controls may include spending limits, approved merchant categories, receipts, monthly review, prohibited purchases and segregation from card administration.

The point is not to force every low-value purchase through a PO. It is to ensure the alternative route has controls of its own.

Purchase-to-Pay Systems Can Automate Preventive Controls

Modern systems can prevent submission without a budget code, block self-approval, enforce thresholds, validate suppliers, reserve budget, generate POs, record receipts and perform automatic matching.

Automation is strongest when the underlying authority rules are clear.

Workflow Configuration Is Policy

If the software lets a $100,000 order bypass procurement because a user selected the wrong category, the configured workflow has silently rewritten policy.

System rules should be tested against the delegation matrix and reviewed after organisational changes.

Access Rights Need Periodic Review

A former principal should not retain purchase approval. A transferred employee should not continue receiving goods for a school they left.

Role changes and departures should update procurement permissions promptly.

Audit Logs Should Show the Decision Chain

A reviewer should be able to reconstruct:

• who requested;
• who approved;
• which budget was checked;
• which supplier was used;
• which PO was issued;
• who changed it;
• who received;
• what discrepancies occurred;
• and how the order closed.

This is essential when questions arise months later.

Analytics Can Find Control Weaknesses

• retrospective PO rate;
• requisitions just below approval thresholds;
• same requester and approver combinations;
• high-volume emergency purchases;
• orders to new suppliers;
• unusually frequent supplier bank-detail changes;
• open POs older than expected;
• receipt entered after invoice;
• excessive match exceptions;
• repeated over-delivery or short delivery;
• returns by supplier;
• off-contract spend.

Red flags are reasons to examine transactions, not automatic proof of wrongdoing.

Supplier Performance Begins at Delivery

Late delivery, repeated damage, wrong specifications and incomplete documentation should feed contract and supplier-performance records.

The same supplier should not be evaluated as “successful” merely because an invoice was eventually paid.

Receiving Data Can Improve Future Specifications

If a particular chair is repeatedly returned, the problem may be the supplier—or the specification that allowed that chair.

Purchasing should learn from what actually arrives.

Sustainability Claims Need Verification

Procurement may specify energy efficiency, recycled content, repairability or environmental certifications.

Receiving or technical acceptance should verify required evidence rather than assume the supplier’s marketing claim satisfies the contract.

Data and Software Purchases Need Security Acceptance

A subscription can be “delivered” while privacy terms, security configuration or data-processing requirements remain incomplete.

Digital service acceptance may require technical and governance checks before full payment or rollout.

Worked Case: Twenty Laptops

A school requests twenty laptops for a new computing class. The requisition identifies the student group, required software, accessibility needs and delivery deadline. Budget control confirms funds. An existing framework contract is available, so no new tender is needed.

The authorised PO specifies model, memory, warranty and imaging requirements. Eighteen devices arrive correctly; two have damaged screens. Receiving records eighteen accepted and two rejected. The supplier replaces the damaged units. Only then does the order reach full receipt.

Accounts payable matches invoices to accepted quantities rather than paying for boxes the school did not successfully receive.

Worked Case: The Retrospective Repair

A pipe bursts on Sunday. The principal calls an emergency plumber who begins work before an ordinary requisition can be processed.

Emergency authority permits the commitment within a defined cap. On Monday, the principal records the emergency basis, supplier, scope and cost. Facilities verifies work performed and finance creates the authorised emergency record rather than pretending an ordinary pre-approved PO existed.

The exception is transparent because the system has an emergency lane.

Worked Case: Threshold Splitting

A department raises three $9,500 requisitions to the same supplier for related laboratory equipment when the competitive threshold is $25,000.

Analytics flags the pattern. Review confirms the requirements were one foreseeable purchase. The requisitions are consolidated and the proper procurement route is applied.

Worked Case: Cleaning Service Receipt

A monthly cleaning invoice arrives for the full contracted amount.

The system does not “receive” the service merely because the calendar month ended. The facilities manager reviews scheduled service, missed shifts, inspection scores and approved deductions before confirming the month’s service receipt.

Worked Case: Old Purchase Orders Block Budget

A school appears to have no remaining equipment budget. Review shows many POs from the previous term still open even though suppliers confirmed they will not deliver the remaining quantities.

Procurement closes the obsolete lines under controlled authority, releasing unused commitments. The school did not receive new money; it recovered visibility of money that was no longer truly committed.

Worked Case: Wrong Bank Details

An email asks the school to change a supplier’s bank account shortly before payment.

The supplier-master team verifies the change through an independent known contact rather than replying to the same email. The request is fraudulent and is blocked before any invoice is paid.

Supplier data is part of procurement control, not simple clerical maintenance.

Failure Mode: Requisition Means “Please Approve the Supplier I Already Chose”

The repair is need validation and procurement-route selection before an unofficial commitment is made.

Failure Mode: Specification Is Vague

The repair is outcome, quality, safety, accessibility and acceptance criteria clear enough to inspect on receipt.

Failure Mode: One Person Requests, Approves, Receives and Pays

The repair is segregation of duties or compensating review where staffing is too small for full separation.

Failure Mode: Purchase Is Split to Avoid Competition

The repair is aggregation rules and analytics across related purchases and time periods.

Failure Mode: PO Is Created After Delivery

The repair is usable pre-approval for ordinary purchases and a transparent emergency exception route for genuine emergencies.

Failure Mode: Supplier Master Changes Are Weakly Controlled

The repair is independent verification, restricted access and audit logs for legal and banking changes.

Failure Mode: Receiver Signs Without Counting

The repair is independent quantity and condition checks linked to the PO.

Failure Mode: Service Receipt Means Invoice Arrived

The repair is evidence of deliverables, milestones or service levels before confirming receipt.

Failure Mode: Partial Delivery Closes the Whole Order

The repair is line-level open quantities and values until all accepted delivery is complete or formally cancelled.

Failure Mode: Old POs Remain Open Forever

The repair is aged-commitment review and controlled closure of orders no longer expected to be fulfilled.

Failure Mode: Procurement Data Is Used Only for Audit

The repair is operational analytics that improves specifications, supplier performance, contract design and demand planning.

What a Strong Requisition-to-Receipt System Should Be Able to Answer

• Who requested the purchase?
• What educational or operational need does it solve?
• Was existing stock or contract availability checked?
• Is the quantity justified?
• Is the specification clear?
• Are accessibility requirements included?
• Are safety requirements included?
• Which budget owns the cost?
• How much budget was available before commitment?
• Who has approval authority?
• Did anyone approve their own high-risk request?
• Was the proper procurement route used?
• Was demand split around a threshold?
• Was a framework or contract available?
• Is the supplier master verified?
• Who can change supplier bank details?
• What unique PO identifies the transaction?
• Was the PO sent before delivery?
• Were later changes version-controlled?
• How are emergency purchases authorised?
• What quantity was ordered?
• What quantity physically arrived?
• What was damaged or rejected?
• Who received it?
• Was technical acceptance required?
• Was installation or commissioning required?
• Were asset serial numbers captured?
• Was consumable inventory updated?
• What service evidence proves delivery?
• Are partial deliveries tracked correctly?
• How are returns linked to the original order?
• How much of the PO remains open?
• How old is the commitment?
• What invoice-match tolerance applies?
• Who resolves exceptions?
• Are retrospective POs monitored?
• Are emergency purchases overused?
• Are user access rights current?
• Does the audit trail reconstruct the full decision chain?
• Does receiving experience improve future procurement?

A Practical Requisition-to-Receipt Control Loop

Need arises → check stock and existing contract → define specification → raise requisition → verify budget → approve under delegation → choose procurement route → verify supplier → issue PO → supplier fulfils → count and inspect → record receipt → reject or return discrepancies → update inventory or assets → match order, receipt and invoice → resolve exceptions → close residual commitment → analyse patterns → improve the next specification and purchase.

How This Node Connects to the Wider Education System

Public education spends through thousands of ordinary decisions. The major tender attracts attention. The daily requisition, order and receipt determine whether approved budgets actually become the goods and services schools intended to buy.

Useful neighbouring routes include the main How Education Works hub; Education Budget Execution, Commitment Controls & Virements; Education Procurement Bid Evaluation, Conflict-of-Interest & Award Governance; Education Procurement Framework Agreements & Dynamic Purchasing Systems; Education Contract Management, Service Levels & Vendor Exit Planning; Education Accounts Payable, Invoice Verification & Payment Controls; Education Fixed Asset Registers, Inventory Verification & Disposal Controls; and Education Warehousing, Stock Control & Last-Mile Distribution.

Frequently Asked Questions

What is the difference between a requisition and a purchase order?

A requisition is usually an internal request for permission to buy. A purchase order is the authorised instruction or commitment sent to the supplier after budget, approval and procurement requirements are satisfied.

Why record goods receipt if an invoice has arrived?

Because an invoice proves only that a supplier is asking for payment. Goods or service receipt provides independent evidence that the organisation actually received what it authorised.

What is a three-way match?

It compares the purchase order, receiving record and supplier invoice. Agreement among the three gives stronger assurance that payment is authorised, delivered and correctly priced.

Can schools ever buy without a purchase order?

Some systems allow controlled alternatives such as procurement cards, direct-pay categories or emergency purchasing. The important point is that each alternative has its own authority, evidence and review controls.

Why are old open POs a problem?

They can tie up budget that is no longer genuinely committed, distort forecasts and create confusion about outstanding deliveries. Aged orders should be reviewed and closed when no further delivery is expected.

Sources and Further Reading

• World Bank — Project Procurement Framework. Current framework page listing mandatory procurement instruments, including the September 2025 Procurement Regulations and July 2026 procedure.
• World Bank — Procurement Regulations for IPF Borrowers, Seventh Edition, September 2025. Current rules for goods, works, non-consulting and consulting services in Bank-financed investment projects.
• OECD — Implementing the OECD Recommendation on Public Procurement in OECD and Partner Countries, 2025. Current comparative review of integrity, risk management, digitalisation and public-procurement system capability.
• U.S. Government Accountability Office — Standards for Internal Control in the Federal Government, 2025 Revision, published 15 May 2025 and effective for fiscal year 2026. Provides a modern public-sector internal-control framework focused on safeguarding resources and preventive controls.

Final Thought: The Invoice Is Too Late to Start Asking Whether the Purchase Made Sense

By the time an invoice reaches finance, much of the real decision has already happened.

Someone decided the need. Someone chose the quantity. Someone defined the specification. Someone committed the organisation to a supplier. Something was delivered—or was not.

Accounts payable can check the invoice. It cannot reconstruct good procurement if every earlier control was bypassed.

That is why requisitions, purchase orders and receiving matter. They put authorisation before commitment and evidence before payment.

In a public education system, that simple sequence is one of the quiet mechanisms that turns money into real classrooms, real books, real equipment and real services without losing accountability along the way.