Close-up of two red lever arch files on a wooden desk in a modern office setting.
Back to insights

A procurement audit evidence matrix and exception-resolution workflow

A procurement audit evidence matrix and exception-resolution workflow. Practical institutional guidance on evidence, ownership and review boundaries.

By Justin Kettle · Founder & Managing Director

Published · Updated

Illustrative photograph: Pixabay · Photo source

A procurement audit evidence matrix is an index connecting review assertions, source records, unresolved gaps and accountable review decisions.

Structural design of an audit evidence matrix

An evidence matrix provides a rigorous, standardised structure for testing whether public procurement transactions satisfy constitutional and institutional requirements. Under Section 217(1) of the Constitution of the Republic of South Africa, 1996, organs of state in the national, provincial, or local spheres of government, and other institutions identified in national legislation, must contract for goods or services in accordance with a system that is fair, equitable, transparent, competitive, and cost-effective.

fair, equitable, transparent, competitive and cost-effective

— Constitution of South Africa, section217(1), procurement system requirements

To evaluate whether a transaction meets these broad principles, reviewers must break down the procurement lifecycle into specific, testable assertions. Rather than making generalized assumptions about file completeness, the matrix pairs each review assertion directly with the relevant records and the scope of the conclusion they support. This analytical discipline prevents subjective interpretations and ensures that review findings remain strictly grounded in verified facts.

The National Treasury SCM Guide of February 2004 highlights that integrated supply chain management spans demand, acquisition, logistics, disposal, and performance monitoring. Designing a matrix around these operational stages ensures that governance checks cover the entire transaction journey. Accounting officers should note that historical Treasury guidance reflects foundational framework principles rather than operative monetary thresholds, which must always be confirmed against current institutional delegations.

Linking review assertions to primary procurement records

Every assertion in a procurement review must be anchored to specific primary records created during the transaction lifecycle. For instance, testing whether demand was validly established requires examining approved strategic plans, procurement plans, and user requisitions. Similarly, verifying market competitiveness depends on inspecting tender advertisements, bidding registers, and submitted bid response files.

The historical February 2004 SCM guide emphasises that proper contract documentation defines the legal rights, risks, and obligations of contracting parties. Reviewers must cross-reference evaluation scorecards, committee minutes, and signed award notices against the original bid conditions. Mapping each claim to a specific file reference creates a traceable index; it does not itself make the underlying evidence immutable or complete that supports objective review conclusions.

Public institutions must ensure that the evidence mapping process accounts for both physical and electronic record repositories. Where records are stored across decentralized departmental files or digital procurement portals, the evidence matrix functions as a centralised index. This index enables internal audit teams, oversight committees, and external reviewers to locate specific decision records rapidly during formal compliance assessments.

Distinguishing evidentiary gaps from statutory non-compliance

A critical requirement of professional procurement review is maintaining a clear distinction between an evidentiary gap, an administrative policy deviation, and a formal legal conclusion of non-compliance. An evidentiary gap occurs when a required document is absent from the file, whereas a policy deviation involves an operational departure from internal procedural rules. Assess each against its actual requirement. Missing documentation can itself breach a record-keeping duty, while a policy deviation may also have statutory significance; the matrix should identify the question requiring assessment rather than presume the outcome.

Reviewers must avoid making automatic determinations of irregular expenditure solely because a document cannot be located during an initial file check. Labeling a missing file as an immediate statutory violation without thorough investigation creates misleading audit outcomes and damages institutional credibility. Instead, the review workflow must classify missing records as factual information gaps that require systematic resolution.

Preserving original records in their unalterable state is essential throughout the exception-resolution process. Reviewers and institutional officials must never attempt to manufacture backdated approvals, alter historical scorecards, or retrofit missing signatures. Retroactive documentation distorts the historical record and undermines forensic integrity, turning a simple administrative record gap into a potential integrity failure.

Accountable resolution and reviewer disposition workflows

Resolving identified evidence gaps requires a structured, accountable workflow that assigns clear responsibility to designated file owners. When an evidence matrix flags a missing record, the assigned owner must conduct targeted searches across secondary archives, financial system logs, and departmental registries. Every resolution attempt must be documented to explain how missing information was retrieved or why it remains unverified.

Once the file owner completes the retrieval process, the reviewer records a formal disposition within the matrix. Reviewer dispositions should categorise findings into clear operational states, such as verified compliant, administrative record gap resolved, policy exception noted, or potential statutory non-compliance flagged for legal review. This clear categorization ensures that executive leadership receives actionable, objective oversight reports.

Operationalising matrix mapping in institutional reviews

Embedding an evidence matrix into routine oversight activities strengthens institutional governance and audit readiness across public entities. Accounting officers and accounting authorities, who bear statutory responsibility for internal financial controls under public finance legislation, can utilise matrix mapping to monitor procurement integrity continuously. Regular matrix reviews highlight systemic record-keeping weaknesses before formal external audits occur.

To maximise operational effectiveness, public institutions should adopt standardised matrix templates across all procurement units. Training supply chain practitioners and internal auditors to use identical assertion structures ensures consistency in file reviews. Furthermore, institutional leaders should verify that review frameworks reflect operative delegation schedules, actual transaction dates, and specific organisational policies rather than outdated national guidelines.

A structured evidence matrix ultimately transforms procurement auditing from a disruptive, reactive search into an orderly, evidence-based quality assurance process. By systematically linking assertions, file references, gaps, and dispositions, public institutions maintain defensible decision trails that demonstrate commitment to constitutional procurement principles.

Key practical principles for implementing an evidence matrix include:

  • Establish standardised assertion templates that cover the full procurement lifecycle from demand to contract closure.
  • Maintain strict separation between factual file indexing, administrative gap resolution, and formal legal analysis.
  • Ensure all worked examples and matrix entries are treated as qualitative, illustrative frameworks tailored to operative delegations.
  • Verify operative institutional frameworks, transaction dates, and commencement provisions before concluding on statutory compliance.
AssertionFile referenceMissing or conflicting evidenceAccountable resolution and reviewer disposition
The demand decision relates to an institutional needActual requisition and procurement-plan referencesThe requisition is available, but its link to the approved plan is missing from the indexFile owner locates the relevant plan extract; reviewer records the reference and what it supports, retaining any remaining question about authority.
The competitive process followed the applicable procedureActual notice, bid-receipt register and procedure referencesA notice is available, but opening or receipt evidence is incompleteSeek genuine contemporaneous records and check the actual applicable requirement; do not infer transparency or non-compliance from one document alone.
Evaluation used the approved criteria and authorised panelActual evaluation report, scorecards and attendance referencesSome evaluation records are missing or conflict with attendance informationCheck actual panel authority, composition, participation and quorum requirements. An absence record alone does not establish a valid evaluation.
The award decision fell within the decision-maker's authorityActual award minute and operative delegation referencesThe minute exists, but the relevant delegation is not linkedRetrieve the delegation in effect on the decision date and assess its scope. Record uncertainty until the authority question is resolved.
Delivery acceptance is supported by the contract and evidenceActual contract, delivery record and inspection referencesA delivery note is present, but technical acceptance evidence is incompleteSeek contemporaneous inspection evidence. Date any later explanation honestly and distinguish it from the original acceptance record.

Sources

Frequently Asked Questions

How does an evidence matrix differ from a financial expenditure pack?

An evidence matrix focuses specifically on reconstructing and testing the decision-making logic, statutory compliance, and contractual documentation of a procurement process. In contrast, a financial expenditure pack focuses on accounting disbursements, payment vouchers, tax invoices, and bank settlement proofs. While financial packs verify that funds were paid out, an evidence matrix verifies whether the underlying purchasing decision met constitutional standards.

Why must institutions preserve original records when resolving evidence gaps?

Preserving original records in their authentic state is essential to maintain the evidentiary integrity of public files. Attempting to alter, backdate, or recreate missing documents distorts the historical record and may constitute improper record manipulation. When an evidence gap is identified, institutions must document the missing record through secondary archival retrieval or explanatory memos rather than retrofitting original files.

What is the distinction between an evidentiary gap and a legal conclusion of irregularity?

An evidentiary gap refers strictly to the absence of a physical or digital record from a file, whereas an administrative policy deviation involves a failure to follow an internal procedural rule. A conclusion about statutory irregularity requires assessment against applicable legislation and the relevant framework by the responsible authorised function, with specialist input where needed. An evidence gap or procedural deviation should never be automatically equated with unlawful expenditure.

How should reviewers handle missing delegation certificates or committee minutes?

When key administrative records such as delegation schedules or committee minutes are missing from a transaction folder, reviewers should request the file owner to conduct a search in centralized institutional archives. If official copies are retrieved from primary governance registries, the evidence matrix is updated to reflect the verified document location. If records remain unlocated, the reviewer flags the gap without fabricating conclusions.

Can missing procurement approvals be retroactively granted during an audit review?

Do not backdate or present a new approval as if it existed earlier. Record the actual decision history and assess any lawful remedial route under the applicable framework through the responsible authority. A later explanation or remedy must retain its real date and must not overwrite the original evidence gap.

For wider context, read the procurement audit readiness overview.

Discuss your organisation’s priorities

Contact Kettle Consulting