An expenditure-control evidence pack is an advisory documentation workflow that traces public funds from initial transaction to management review.
Public Finance Management Act 1 of 1999 (PFMA) governance requires national and provincial departments, trading entities, constitutional institutions, and Schedule 2 and 3 public entities to operate effective financial control systems. National Treasury Instruction No. 4 of 2022/2023 sets a national compliance and reporting framework for specified expenditure categories, tracking supplier invoice payments, and reporting contract variations.
In contrast, Western Cape Treasury Circular 7 of 2026 (issued 16 April 2026) provides provincial treasury guidance prescribing quarterly reporting schedules and register formats (Appendices A, B, and C) for Western Cape provincial bodies, serving as provincial procedure rather than universal national law. Implementation recommendations in this article represent advisory methodology rather than statutory rules.
Tracing original transactions across procurement and payment records
safeguard assets and manage revenue, expenditure and liabilities of the public entity
— National Treasury Instruction No. 4 of 2022/2023, paragraph 2.4, p. 2
Establishing expenditure control requires maintaining an unbroken evidentiary trail from initial procurement requisition to final bank settlement. Under Section 38(1)(f) of the PFMA, departmental accounting officers must settle contractual obligations within the prescribed or agreed period; Treasury Regulation 8.2.3 addresses the payment period, subject to contractual or other agreed arrangements, as reinforced by Treasury Regulation 8.2.3. For public entities listed in Schedules 2 and 3, Section 51(1)(c) of the PFMA mandates accounting authorities to "safeguard assets and manage revenue, expenditure and liabilities of the public entity" (National Treasury Instruction No. 4 of 2022/2023, page 2 of 4).
Tracing expenditure begins with matching purchase requisitions, tender approvals, contracts, official orders, goods receipt notes, and tax invoices. Finance teams must cross-reference sub-ledger payment entries against main general ledger accounts during monthly financial closing. Reconciling payment vouchers against primary bank statements helps reviewers identify missing records, posting differences or unsupported payments; reconciliation does not itself prove compliance or service delivery.
Structuring the evidence pack and preserving transaction status
An annotated transaction-level evidence pack provides a structured repository for documenting expenditure reviews, tracking exceptions, and supporting management oversight. The evidence pack must maintain separate fields for gross expenditure, identified financial loss, recovered amounts, and authorised write-offs. Conflating these fields obscures transaction status and distorts financial reporting. An initial exception finding represents a diagnostic indicator for review, not an automatic financial loss, criminal misconduct, unrecoverable debt, or guaranteed audit outcome.
To maintain evidentiary integrity, the proposed pack should use controlled access and retain an auditable history of records and changes. Keep unresolved cases visible, with their current status and the evidence needed for the authorised next step. A complete expenditure-control evidence pack comprises five practical components:
- Primary transaction records, including approved requisitions, purchase orders, delivery notes, tax invoices, and payment vouchers.
- Bank statements, sub-ledger posting logs, and general ledger reconciliation working papers.
- Exception case reference files logging transaction descriptions, dates, and preliminary assessment details.
- Determination and investigation evidence records detailing root causes, control breakdowns, and financial loss calculations.
- Authorised management decision records, consequence management logs, and corrective-control re-testing sign-offs.
Differentiating departmental and public entity expenditure categories
Financial compliance frameworks establish clear distinctions between departmental expenditure categories and public entity reporting requirements. The framework distinguishes unauthorised expenditure applicable to departments from irregular and fruitless and wasteful expenditure reporting. Reviewers should establish the institution type and applicable legal definition before classifying a transaction. For public entities, the Instruction refers to irregular and fruitless and wasteful expenditure; a departmental category should not simply be copied into an entity register.
However, both departments and public entities must track irregular expenditure and fruitless and wasteful expenditure under Sections 38 and 51 of the PFMA. An irregular-expenditure assessment needs an identified applicable legal requirement and supporting facts. An internal policy or delegation exception should not automatically be treated as irregular expenditure without establishing the relevant legal basis. Fruitless and wasteful expenditure represents expenditure made in vain that could have been avoided had reasonable care been exercised.
Western Cape Treasury Circular 7 of 2026 establishes specific provincial quarterly submission dates (such as 31 July for Quarter 1) and reporting registers for Western Cape provincial institutions, providing provincial monitoring protocols.
Advisory four-column transaction evidence pack matrix
To assist finance leads in structuring transaction reviews, institutions can implement a transaction-level evidence matrix. The table below presents an advisory design framework outlining required primary evidence, advisory review assessments, and retained management control responsibilities across the transaction lifecycle.
| Transaction lifecycle stage | Required primary evidence | Advisory review assessment | Retained management control |
|---|---|---|---|
| Procurement & Approval | Approved requisition, tender approval, and purchase order | Verify delegation limits and competitive bidding compliance | Approval under the institution’s delegations |
| Goods Receipt & Invoicing | Signed goods receipt note, delivery slip, and tax invoice | Verify receipt date, applicable payment terms and delivery evidence | Receiving Manager sign-off on goods receipt note |
| Sub-Ledger Payment | Payment voucher, bank statement, and ledger journal | Reconcile sub-ledger disbursement to general ledger | Finance Manager authorisation of payment run |
| Exception Determination | Exception log, assessment file, and investigation report | Evaluate root cause, gross expenditure, and potential loss | Accounting Officer or Authority determination sign-off |
What good looks like
A well-governed public institution demonstrates expenditure control through complete data provenance, unbroken evidence chains, and clear management oversight. By maintaining an annotated transaction-level evidence pack, separating gross expenditure from loss calculations, distinguishing departmental unauthorised expenditure from public entity categories, and conducting regular management reviews, accounting officers and accounting authorities build a resilient foundation for financial governance and public accountability.
Sources
- National Treasury Instruction No. 4 of 2022/2023, pp. 1–2 — National Treasury
- Western Cape Treasury Circular 7 of 2026, sections 3–5 and Appendices A–C — Western Cape
Frequently Asked Questions
Which records should an expenditure-control evidence pack link together?
Link the original requisition, approval, order, receipt or service evidence, invoice, payment and ledger posting. Add the reconciliation, exception case reference, assessment status and authorised management response so reviewers can follow the transaction without treating a missing record as a proven loss.
What is the distinction between unauthorised expenditure in departments and irregular expenditure in public entities?
The Instruction treats unauthorised expenditure as a departmental category and identifies irregular and fruitless and wasteful expenditure for public entities. Confirm the applicable institution type and legal requirement before making a classification.
Why must gross expenditure, identified loss, recovery, and write-off fields be kept separate in the evidence pack?
Keeping gross expenditure, identified financial loss, recovered amounts, and written-off values in distinct fields prevents financial conflation and ensures accurate reporting . Gross expenditure represents total transaction value, whereas identified loss is a separate assessment from the amount of expenditure, and cannot be inferred solely from the transaction value or a procedural exception .
Does logging an expenditure exception automatically indicate financial misconduct or loss?
No, logging an exception in an evidence register is a diagnostic control action indicating that a transaction requires formal review . An exception finding does not imply automatic financial loss, official misconduct, or immediate debt write-off until formal assessment and determination workflows are completed .
How should invoice payment terms be documented in the pack?
Record the invoice receipt date, relevant contract or agreement, applicable payment requirement, delivery evidence and actual settlement date. Test the transaction against the requirement that applies; do not assume every institution and invoice has an identical payment timetable.
Read the wider context in expenditure accountability and control.