How Education Works | Education Accounts Payable, Invoice Verification & Payment Controls — How Delivered Goods Become Valid, Timely Public Payments

HEW-NODE-0193 · How Education Works · Education accounts payable, invoice verification and payment controls

A school system can approve a budget, run a fair procurement, sign a valid contract and receive the correct goods—and still fail at the last metre.

The textbooks arrive, but the invoice sits in an inbox. A contractor completes work, but nobody records the acceptance certificate. A school receives fifty laptops while the invoice says sixty. A supplier changes its bank account and sends new details by email. An invoice is paid twice because two offices process copies. A payment is held so long that a small supplier cannot meet payroll. A year-end rush pushes invoices through without checking whether the goods were actually delivered.

This is where public money stops being an abstract budget and becomes a specific transfer to a specific supplier for a specific obligation.

This is the job of education accounts payable, invoice verification and payment controls: proving that an amount is genuinely owed, that the claim matches what was ordered and received, that the right authority approves it, that bank and supplier details are trustworthy, that payment happens once, and that valid obligations do not quietly turn into arrears.

This node has a deliberate boundary. Education Procurement owns the purchasing lifecycle and formation of the obligation. Education Budget Execution, Commitment Controls & Virements owns authorisation and reservation of budget before expenditure. Education Treasury & Cash Management owns system-wide cash availability and payment liquidity. Education Contract Management, Service Levels & Vendor Exit Planning owns supplier performance after award. This page owns the payable between receipt and settlement: invoice capture, validation, matching, approval, payment preparation, duplicate prevention, supplier-master controls, ageing and arrears visibility.

Quick Answer

Valid purchase or contract → commitment exists → goods or services are delivered → receipt is evidenced → invoice is captured once → supplier and banking identity are verified → invoice is checked against order, contract and receipt → discrepancies are resolved → authorised officer approves the claim → payable is recorded → payment is scheduled according to terms and cash rules → treasury or bank executes → remittance is issued → ledger is updated → exceptions and overdue items are reviewed → records remain auditable.

A mature accounts-payable system protects two things at once: public money from invalid payment and legitimate suppliers from avoidable non-payment.

Accounts Payable Begins After Somebody Has Earned a Claim

A purchase order is not yet an invoice. A commitment is not yet a delivered service. A signed contract is not yet proof that the supplier has performed.

The payable arises because a third party has provided goods, services or another valid consideration under the applicable arrangement and the organisation now has an obligation to settle that claim.

The IMF’s technical guidance on government expenditure arrears describes payables as liabilities for goods or services that have been provided but not yet paid. That distinction is important because it separates an intention to spend from an amount actually owed.

The Expenditure Chain Has Distinct States

A strong financial system does not compress every stage into “spent.” It distinguishes budget, commitment, receipt, invoice, payable, payment and, where relevant, arrears.

Those states answer different questions. Was money authorised? Was it reserved? Was the item delivered? Was the claim verified? Is it now owed? Has it been paid? Is it overdue?

When the states are visible, managers can locate where money is stuck instead of discovering the problem only when suppliers complain.

An Invoice Is a Claim, Not Proof

An invoice can be accurate, mistaken, duplicated, fraudulent, premature or unrelated to an authorised purchase.

The accounts-payable process should therefore treat the invoice as a claim requiring validation. The organisation pays because underlying evidence supports the obligation, not because a document titled “invoice” arrived.

Invoice Capture Should Create One Official Record

Invoices may arrive by supplier portal, structured e-invoice, email, paper or through a contract-management system. Whatever the channel, the organisation needs one authoritative record containing the supplier, invoice number, invoice date, receipt date, amount, currency, tax treatment where applicable, purchase-order or contract reference and payment due date.

The capture date matters because it starts the organisation’s internal clock and supports later analysis of processing delays.

A Central Intake Point Reduces Duplicate Payment Risk

If the same invoice can be sent to a school, a district office and central finance, three teams may believe they are looking at separate claims.

A central electronic intake route, or at least a shared register, makes duplicate detection much easier. Paper can still be accepted where necessary, but it should become part of the same record rather than a parallel accounting world.

The Supplier Master Is a High-Risk Control Point

Before an invoice can be paid, the system needs to know who the supplier is and where payment should go.

Supplier-master records typically contain legal name, registration or tax identifiers, address, contact details, bank account information, payment terms and status. Because changing these fields can redirect public money, creation and amendment deserve stronger controls than ordinary data entry.

Bank-Account Changes Need Independent Verification

A familiar fraud pattern begins with a believable message: “Our bank details have changed. Please use the attached account for all future payments.”

A strong process does not validate a bank change by replying to the same message. It uses a trusted independent channel, known contact or established supplier portal, with appropriate segregation of duties and an audit trail.

The payment destination is part of the financial control environment, not just a clerical field.

Segregation of Duties Makes One-Person Fraud Harder

The person who creates a supplier should not normally be able to create an invoice, approve it and release payment alone. The exact division depends on organisational size, but incompatible powers should be separated or independently reviewed.

Small schools may not have enough staff for perfect separation. Compensating controls—central approval, periodic review, dual bank authorisation, exception reporting or rotation—can reduce the risk.

Three-Way Matching Tests Three Different Claims

For many routine purchases, one of the most useful controls is a three-way match:

• Purchase order or contract: what the organisation authorised.
• Goods receipt or service acceptance: what the organisation actually received.
• Invoice: what the supplier is asking to be paid.

When quantity, price, item and terms align within permitted tolerances, the invoice can progress. When they do not, the mismatch becomes an explicit exception instead of being hidden inside payment.

Two-Way Matching Can Be Appropriate for Some Expenditure

Not every transaction has a conventional goods receipt. Rent, utilities, subscriptions, statutory fees or some professional services may require a different evidence model.

The principle is not that every payment must use the same workflow. The principle is that the organisation defines what evidence proves the obligation for each expenditure type.

Receipt Evidence Is More Than a Signature

“Received” should mean the organisation has evidence that the goods or services arrived in the required state.

For textbooks, this may be counted quantities and condition. For construction, it may be certified milestones. For professional services, it may be an accepted deliverable. For software, it may be activated licences or service availability. For catering, it may be verified service periods and quantities under the contract.

The evidence should match the nature of what was bought.

The Person Who Orders Should Not Automatically Certify Receipt

Where feasible, independent receipt confirmation reduces the ability of one person to create an order and falsely confirm that it was fulfilled.

The appropriate control can vary by value and risk. A small stationery delivery and a major capital milestone do not need identical ceremony.

Quantity Differences Need Rules

A purchase order may specify one hundred units while ninety-eight arrive because two are back-ordered. The supplier may invoice the full hundred. The accounts-payable system should not guess whether that difference is acceptable.

Rules should specify whether partial receipts are allowed, whether partial invoices can be paid, how back-orders are tracked and when the remaining commitment is released.

Price Differences Need Tolerances

Minor rounding or freight differences can create disproportionate manual work if every variance requires senior intervention. Unlimited tolerance, however, defeats the point of matching.

Organisations can define monetary and percentage tolerances by transaction type, with higher-value or unusual exceptions routed for approval.

Tax and Currency Are Part of the Claim

Where relevant, invoices may involve sales tax, withholding tax, value-added tax, foreign currency or exchange-rate rules. These affect the amount payable and the accounting record.

Automated validation can reduce clerical error, but unusual transactions still need knowledgeable review.

Contract Milestones Need Objective Acceptance

Complex education projects often pay against milestones: design approved, equipment installed, training completed, system accepted or construction stage certified.

A milestone invoice should be supported by the evidence defined in the contract. Paying because the calendar date arrived turns a performance-based milestone into a scheduled advance.

Retentions and Holdbacks Must Remain Visible

Construction and other contracts may retain part of a payment until defects are corrected or conditions are met.

The retained amount should remain traceable with a clear release condition and date. Otherwise it can become forgotten money, disputed liability or an unexplained balance years later.

Credit Notes Must Be Linked to the Original Claim

Returns, price corrections and rebates can generate credit notes. If they are processed separately from the original invoice, the organisation can lose sight of the net obligation.

Linking credits to the supplier and original transaction helps prevent overpayment and supports reconciliation.

Duplicate Detection Should Use More Than Invoice Number

A supplier may accidentally resend an invoice with a slightly different number, spacing or date. Scanned documents may introduce recognition errors.

Duplicate checks can consider supplier, amount, invoice number, date, purchase-order reference and other patterns. Exact-match rules catch simple duplicates; near-match analytics can flag suspicious similarities for review.

A Duplicate Flag Is Not Proof of Fraud

Two legitimate monthly invoices can have the same amount. The purpose of duplicate detection is to stop automatic payment long enough for a human or validated rule to determine whether the second claim is real.

Invoice Approval Should Confirm More Than Arithmetic

The approving officer is usually confirming that the expenditure belongs to the organisation, the goods or services were received, the amount is correct, the account coding is appropriate, contractual conditions have been met and the person has authority to certify the claim.

Approval is a statement of responsibility.

Approval Limits Should Scale With Value and Risk

A routine low-value payment should not need the same approval chain as a multimillion-dollar construction milestone. Excessive approval layers slow payment without necessarily improving control.

Delegations can scale by value, transaction type, project, funding source and exception status.

Emergency Payment Paths Need Rules Before the Emergency

A school may need urgent repairs after a storm, immediate transport after a safety event or emergency supplies during disruption.

The process can be faster without becoming undocumented. Emergency authority, evidence, retrospective review and thresholds should be defined in advance so urgency does not become a general bypass.

Payment Terms Are Operational Commitments

Contracts and law may specify how many days the buyer has to pay a valid invoice. The due date should be recorded when the claim enters the system.

Without a due date, the organisation cannot distinguish an ordinary payable from an overdue obligation.

Accounts Payable and Arrears Are Not the Same Thing

A valid invoice awaiting payment within agreed terms is a payable. Once it remains unpaid beyond the applicable due date, it can become an expenditure arrear under the relevant rules.

PEFA treats expenditure arrears as a significant public-finance issue because overdue obligations can become a form of non-transparent financing. Suppliers are effectively lending to government without that financing appearing like normal borrowing.

Ageing Makes Delay Visible

A payable ageing report groups outstanding claims by how long they have been waiting: current, approaching due date, overdue by 1–30 days, 31–60 days, and so on.

The precise bands vary. The essential function is to show not only the total amount outstanding but how long obligations have been unresolved.

Ageing Should Distinguish “Waiting for Cash” From “Waiting for Evidence”

A delayed invoice can be blocked because the treasury lacks cash, because the supplier has not corrected a discrepancy, because receipt has not been certified, because approval is missing or because a legal dispute exists.

One overdue total is not enough. Managers need reason codes and owners so they can intervene at the correct point.

An Invalid Invoice Should Not Age Silently

If a claim is incomplete or disputed, the supplier should be told promptly. PEFA guidance notes that even defective claims can create arrears problems if recipients are not notified before the payment deadline under applicable rules.

The system needs a formal status for rejected or suspended invoices, with the reason and date communicated.

Payment Runs Convert Approved Payables Into Cash Movement

Many organisations group approved invoices into scheduled payment runs. The run selects due items, applies holds, verifies bank details, produces a payment file and sends it for authorised release.

The payment run is another control boundary. A claim that was approved should not be altered casually while it is being converted into a bank instruction.

The Payment File Needs Integrity Controls

The list of approved payables can be correct while the bank file is manipulated afterward.

Controls can include restricted access, file hashing or secure interfaces, dual release, totals reconciliation, independent review and direct system-to-bank transmission. The design should fit transaction volume and risk.

Positive Pay and Bank Validation Can Add Another Barrier

Banking arrangements may support validation of payee or payment information before funds leave. Where available and appropriate, these controls supplement—not replace—internal supplier and approval controls.

Remittance Advice Helps Suppliers Reconcile

A supplier receiving one transfer for several invoices needs to know what was paid. Clear remittance information reduces queries and helps both sides reconcile balances.

Good payment communication is a small operational control that prevents large amounts of avoidable follow-up.

The Ledger Must Reflect Settlement

After payment, the payable should be cleared against the correct invoice and the cash movement recorded. Unapplied or misapplied payments leave supplier accounts unreliable.

The accounting record should allow an auditor to trace from budget and purchase through receipt, invoice, approval and payment without reconstructing the story from emails.

Supplier Statements Are a Powerful Reconciliation Tool

A supplier’s statement may show invoices the organisation never captured, credits not applied or payments the supplier cannot identify.

Regular reconciliation with high-volume or high-risk suppliers can detect missing claims and duplicate records before year-end.

Unmatched Receipts Need Attention Too

Goods may arrive before an invoice. If receipt records sit unmatched for months, the organisation can understate what it owes or lose track of commitments.

Reports should identify goods received but not yet invoiced, especially where accounting rules require recognition of the obligation.

Invoices Without Purchase Orders Are a Diagnostic Signal

Some expenditure legitimately does not use a purchase order. But a recurring pattern of invoices arriving without prior authorisation can indicate weak procurement discipline, retrospective purchasing or an overly difficult ordering process.

The accounts-payable system should classify and analyse these exceptions rather than normalise them.

Accounts Payable Is Where Procurement and Finance Meet

Procurement knows what was contracted. The school knows what arrived. Finance knows what is recorded. Treasury knows when cash can move. A payable sits at the intersection.

Weak handoffs create delays even when every individual department believes it has done its job.

Small Suppliers Feel Late Payment More Severely

A global technology provider may tolerate a delayed invoice. A local transport operator, maintenance firm, translator or learning-support provider may depend on predictable cash to pay wages and purchase supplies.

Timely payment is therefore not merely courtesy. It can affect supplier diversity, market participation and the resilience of services schools depend on.

Late Payment Can Raise Future Prices

Suppliers who expect long delays may build financing costs and risk premiums into future bids or avoid public-sector work altogether.

Payment discipline can therefore influence procurement value beyond the current invoice.

A Year-End Rush Is a Predictable Control Hazard

As the financial year closes, spending units may rush to process invoices, clear commitments and use remaining appropriations. Volume rises at the same time staff are reconciling accounts.

Year-end procedures should define cut-off dates, treatment of goods received, open purchase orders, accruals or payables, rejected claims and the authority needed for late transactions.

Cut-Off Is About Which Period Owns the Transaction

An invoice dated after year-end may relate to goods received before year-end. A payment made before year-end may relate to a service not yet delivered.

Correct cut-off protects both financial reporting and budget control by aligning the transaction with the period in which the underlying economic event occurred under the applicable accounting basis.

Prepayments Need Separate Treatment

Sometimes education organisations legitimately pay before delivery—for annual licences, subscriptions, deposits or mobilisation under contract.

A prepayment is not the same as an ordinary payable for goods already received. It carries different risks and should be authorised and tracked accordingly.

Recurring Invoices Can Be Automated Carefully

Rent, approved subscriptions and standard utilities can often use recurring controls. Automation should still test supplier status, account coding, unusual amount changes and contract validity.

Predictability is useful. Blind repetition is not.

Utilities Need Consumption Reasonableness Checks

Electricity, water and telecommunications invoices may not have a fixed quantity. Schools can compare consumption with prior periods, meter data, building use and known tariff changes.

A sudden doubling of consumption can be a billing error, leak, equipment fault or real operational change. Accounts payable can be an early sensor.

Capital Projects Need Stronger Certification

Large construction or infrastructure payments often depend on engineer, architect or project-manager certification. Variations, retentions, defects and cumulative progress can make the amount difficult to verify.

The payment workflow should preserve the technical certificate, contract reference, approved variations and previous amounts paid so finance does not have to infer construction progress from an invoice alone.

Grant Payments Are Not Supplier Invoices

Education systems also transfer funds to schools, NGOs, scholarship recipients or programme partners. These can be governed by grant agreements rather than procurement contracts.

The adjacent Education Grant Administration, Recipient Monitoring & Acquittal node owns the grant lifecycle. Accounts payable can execute an authorised transfer, but should not pretend a grant is a commercial invoice.

Employee Reimbursements Need Their Own Evidence Model

Travel, approved purchases and other reimbursements can look like supplier payments but involve staff claims. Policy limits, receipts, business purpose, approval and conflict checks may differ.

Separating transaction types helps controls remain specific rather than forcing every payment through one inappropriate workflow.

Fraud Detection Should Look for Patterns

Useful signals can include duplicate amounts, repeated invoices just below approval thresholds, rapid bank-detail changes, weekend approvals, unusual supplier concentration, invoices without purchase orders, split invoices and payments to bank accounts shared by unrelated suppliers.

A flag is not proof. It is a reason for review.

Threshold Splitting Can Defeat Delegations

If an approval threshold is $10,000, two invoices of $9,900 for what is really one obligation may deserve attention.

Systems can look for clusters of invoices by supplier, order and time period rather than checking each document in isolation.

Related-Party and Conflict Information Should Reach Payment Controls

Procurement may identify conflicts or beneficial ownership concerns at tender stage. If that information is not available to finance, later payments can proceed without awareness of conditions or restrictions.

The control environment works when relevant integrity information travels with the supplier relationship.

Payment Holds Need Reasons and Owners

A payment may be held for a contract dispute, sanctions check, tax issue, missing evidence, suspected fraud or litigation. The hold should state why, who imposed it, when it should be reviewed and what clears it.

Indefinite unexplained holds create hidden arrears and unfairness.

Disputed Invoices Need a Resolution Clock

A school may genuinely disagree with a supplier over quantity, quality or price. That dispute should not disappear into an email chain.

A controlled dispute record can show the amount challenged, undisputed amount, evidence requested, responsible contract manager, next review date and whether partial payment is allowed.

Pay the Undisputed Amount Where Rules Permit

If only one part of an invoice is contested, withholding the entire payment can unnecessarily harm the supplier. Some systems allow the uncontested portion to proceed while the disputed amount remains on hold.

The governing contract and financial rules should determine the treatment.

Creditors Should Not Finance Education by Accident

When an education system delays valid supplier payments because its cash planning is weak, it effectively borrows from those suppliers. That financing can be opaque, uneven and expensive.

This is why accounts-payable ageing is not merely an accounting report. It is a signal about budget credibility, cash planning and operational trust.

The Treasury Boundary Must Be Clear

Accounts payable proves and prepares the obligation. Treasury decides how approved payments fit the system’s cash position and executes cash movement under its authority.

If accounts payable holds invoices because it is informally rationing cash, managers cannot tell whether delays are caused by invalid claims or liquidity constraints. The adjacent Education Treasury & Cash Management node owns that cash layer.

The Chart of Accounts Gives Every Payable a Financial Address

A valid invoice must usually be classified to the correct organisation, programme, economic category, project, fund or other dimensions required by the financial system.

If coding is inconsistent, the payment may still reach the supplier while management reports become misleading. The sibling Education Chart of Accounts, Financial Coding & Reporting node owns that classification architecture.

Coding Should Happen as Early as Practical

If the purchase order already contains the correct financial coding, the invoice can inherit it rather than forcing accounts-payable staff to guess the educational purpose after delivery.

Exceptions still need review when circumstances change, but earlier coding reduces rework.

Automation Can Match High-Volume Invoices

Where purchase orders, receipts and invoices are structured electronically, systems can automatically match clean transactions and route only exceptions to staff.

This allows humans to focus on discrepancies, unusual patterns and judgement rather than repeatedly confirming perfect matches.

Optical Character Recognition Is Not Verification

Document-reading tools can extract supplier name, amount and invoice number from a PDF. They can also misread decimal points, dates and account numbers.

Extraction can reduce data entry, but controls still need to validate critical fields against source evidence and system records.

Electronic Invoicing Can Improve Control at Source

Structured e-invoices can enforce required fields, standard identifiers and machine-readable references before a claim enters the workflow.

This can reduce transcription errors and speed matching, provided supplier onboarding, authentication and system integration are well governed.

Artificial Intelligence Should Not Invent Evidence

Automated tools can identify anomalies, suggest coding or summarise supporting documents. They should not fabricate missing receipt evidence or approve a claim because a pattern “looks normal.”

Payment remains a consequential public decision. The evidence chain must be inspectable.

Accounts-Payable Metrics Should Measure Both Control and Flow

Useful measures can include invoice volume, time from receipt to capture, time to approval, percentage matched automatically, exception rate, duplicate blocks, overdue payables, value in dispute, supplier queries, payment-on-time rate and invoices without purchase orders.

A good dashboard asks both “Are we paying safely?” and “Are we paying valid claims on time?”

Cycle Time Should Be Split by Stage

A thirty-day invoice cycle tells managers little if they cannot see whether twenty-seven days were spent waiting for a school to certify receipt, waiting for finance approval or waiting for cash.

Stage-level timing turns delay into something actionable.

Exception Rates Reveal Process Design

If most invoices fail matching because purchase orders contain poor descriptions or receipts are not entered promptly, the accounts-payable team is experiencing an upstream design problem.

The queue can tell procurement and schools where earlier processes need repair.

Straight-Through Processing Is Not the Goal for Every Invoice

Routine low-risk transactions may be suitable for high automation. Complex construction, unusual professional services or high-risk supplier changes may deserve more human scrutiny.

Maturity means matching control effort to risk, not automating everything equally.

Worked Case: Fifty Laptops Arrive, Sixty Are Invoiced

The purchase order authorises sixty laptops. The receiving school records fifty delivered and ten back-ordered. The supplier invoices all sixty.

Three-way matching blocks the quantity variance. Finance does not manually change the receipt to make the invoice pass. The contract manager confirms that partial invoicing is permitted, the supplier issues a corrected invoice for fifty, and the remaining commitment stays open for the final ten.

The control protects both parties: the supplier is paid promptly for what was delivered, while the system does not prepay undelivered units by accident.

Worked Case: The Bank Account Changes Two Days Before Payment

A familiar supplier emails new bank details. The invoice is valid, and the request appears urgent.

Supplier-master control prevents the invoice processor from changing bank data directly. A separate authorised officer contacts the supplier using the phone number already held in the trusted master record, verifies the change and documents approval. The amended bank account then becomes active under the organisation’s change-control rule.

A plausible email never becomes the sole evidence for redirecting public money.

Worked Case: A School Forgets to Confirm Receipt

A local maintenance company completes urgent plumbing work. The invoice reaches central finance, but the school has not recorded service acceptance.

The payable enters an exception queue with an owner and due date. The school business manager confirms completion electronically. The invoice proceeds before the contractual payment deadline.

The system does not weaken receipt control, but it also does not let a valid local supplier disappear into an indefinite queue.

Worked Case: Two Offices Receive the Same Invoice

A supplier emails a school and central finance. Each copy has the same invoice number and amount.

Central capture identifies the duplicate against the supplier record. One transaction remains active; the second is attached as duplicate evidence and closed without payment.

The control is simple because both channels feed the same system of record.

Worked Case: A Valid Invoice Becomes an Arrear

A transport contractor submits a correct invoice, the school confirms the service and finance approves it. Payment is delayed because the spending unit has exhausted available cash for the month.

The invoice stays visible as an approved payable with a contractual due date. When that date passes, the system flags it as overdue rather than hiding it in a generic “pending” status. Management can now see that the problem is cash planning, not invoice validity.

Transparency prevents operational delay from becoming invisible financing.

Failure Mode: Paying From the Invoice Alone

The repair is evidence-based matching to the authorisation and receipt appropriate to the transaction.

Failure Mode: Supplier Bank Details Can Be Changed by the Invoice Processor

The repair is segregated supplier-master maintenance and independent verification of high-risk changes.

Failure Mode: Every Invoice Uses the Same Workflow

The repair is risk-based evidence models for goods, services, milestones, utilities, grants, reimbursements and prepayments.

Failure Mode: Invalid Claims Sit Quietly Until They Become Overdue

The repair is prompt exception notification, reason codes, named owners and resolution dates.

Failure Mode: Finance Does Not Know Whether Goods Arrived

The repair is timely receiving or service-acceptance records integrated with the payable workflow.

Failure Mode: Duplicate Prevention Relies Only on Invoice Number

The repair is multi-field duplicate checks and review of near matches.

Failure Mode: Year-End Clearing Becomes a Control Bypass

The repair is planned cut-off procedures, capacity for the volume surge and no relaxation of core evidence merely to empty the queue.

Failure Mode: Overdue Payables Are Mixed With Disputes

The repair is ageing by reason and ownership so managers can distinguish liquidity, missing evidence, supplier correction and formal dispute.

Failure Mode: Small Suppliers Carry the System’s Cash Shortage

The repair is credible cash planning, transparent prioritisation rules where legally necessary and early warning before valid obligations become arrears.

What a Strong Education Accounts-Payable System Should Be Able to Answer

• When did each invoice arrive?
• Which supplier submitted it?
• Is that supplier active and verified?
• When were bank details last changed, by whom and with what evidence?
• What purchase order, contract or authority supports the claim?
• What goods or services were received?
• Who certified receipt?
• Does quantity match?
• Does price match?
• Are taxes and currency handled correctly?
• Is the invoice a duplicate or near duplicate?
• What financial coding applies?
• Who approved payment?
• Did that person have authority for the amount and transaction type?
• What is the contractual or statutory due date?
• Is the invoice on hold?
• Why?
• Who owns the hold?
• Is any amount formally disputed?
• Can an undisputed amount be paid separately?
• When was the payable recorded?
• When was payment scheduled?
• Who authorised release?
• Which bank instruction settled it?
• Was remittance sent?
• Has the supplier account reconciled?
• Which invoices are approaching due date?
• Which are overdue?
• Why are they overdue?
• How old is the backlog?
• How many invoices arrive without prior purchase orders?
• What percentage match without manual intervention?
• Where do exceptions originate?
• Can an auditor trace the full transaction from authorisation to settlement?

A Practical Purchase-to-Pay Control Loop

Authorise need → procure correctly → reserve budget → create order or contract → receive goods or services → record receipt → capture invoice once → verify supplier → match claim to authority and receipt → resolve exceptions → approve within delegation → record payable → schedule by due date → execute securely → reconcile bank and supplier → age unresolved items → investigate arrears and patterns → improve upstream purchasing, receiving and cash planning.

The loop works when the same transaction remains identifiable from the first authorised commitment to the final cleared payment.

How This Node Connects to the Education System

Accounts payable is where educational plans meet commercial reality. Books, repairs, transport, technology, food, professional services and infrastructure remain promises until suppliers are paid correctly.

Useful neighbouring routes include the main How Education Works hub; Education Procurement; Education Procurement Bid Evaluation, Conflict-of-Interest & Award Governance; Education Budget Execution, Commitment Controls & Virements; Education Treasury & Cash Management; Education Contract Management, Service Levels & Vendor Exit Planning; Education Internal Controls & Fraud Risk Management; and Education Financial Audit & Assurance.

Frequently Asked Questions

What is accounts payable?

Accounts payable is the system for recording and settling valid obligations owed to suppliers and other parties after goods, services or another recognised obligation have been provided under the applicable rules.

Why not pay as soon as an invoice arrives?

Because the invoice is a claim. The organisation still needs evidence that the purchase was authorised, the supplier is legitimate, the goods or services were received, the amount is correct and the payment is approved by someone with authority.

What is three-way matching?

It compares the purchase order or contract, the receipt or service acceptance and the supplier invoice. Matching helps confirm that what is being billed is what was authorised and actually received.

What is the difference between a payable and an arrear?

A payable is an amount legitimately owed but not yet paid. An arrear is a payable that remains unpaid beyond the applicable payment due date.

Should every invoice be manually checked?

Not necessarily. Structured, low-risk invoices that match verified orders and receipts can often be processed automatically within defined tolerances. Higher-risk or exceptional transactions deserve human review.

Why are supplier bank changes risky?

Because redirecting bank details can redirect the payment itself. Changes should be independently verified using trusted contact information rather than accepted solely from the message requesting the change.

Why does timely payment matter to education?

Schools depend on supplier ecosystems. Persistent late payment can weaken smaller providers, reduce market participation, increase future prices and disrupt essential services even when the underlying education budget was properly approved.

Sources and Further Reading

• International Monetary Fund — Prevention and Management of Government Expenditure Arrears, describing commitments, liabilities, payables, payment and arrears.
• PEFA — Assessment Fieldguide, Indicator 22: Expenditure Arrears, on identifying, monitoring and reporting overdue obligations.
• PEFA — Fiji Public Financial Management Performance Report 2025, including contemporary examples of FMIS accounts-payable and arrears monitoring.
• World Bank — 2026 public-financial-management technical material, including payment-control examples linking budget, authorised requests and supporting evidence.
• International Monetary Fund — Governments’ Payment Discipline, on payment lags and the relationship between commitments, payment orders and accounts payable.

Final Thought: Payment Is the Last Test of the Promise

Education systems depend on promises made across institutional boundaries.

A supplier promises to deliver. A school promises to confirm receipt. A finance office promises to verify the claim. A treasury promises to settle valid obligations. A government promises that public money will be used for the purpose for which it was authorised.

Accounts payable is where those promises meet evidence.

Too little control and the system pays what it does not owe. Too much friction and it fails to pay what it genuinely owes. Both failures damage education.

The strongest system holds the middle: every payment has a reason, every reason has evidence, every valid claim has an owner and due date, every exception is visible, and every transfer can be traced from public purpose to settled obligation.

That is how a delivered textbook, a repaired roof, a completed training course or a functioning digital service becomes not merely purchased, but properly paid for.