Most of what determines a verification outcome happens long before the verification begins. By the time an auditor walks into the data room, the score is mostly already on the page. The audit reads what is there. The work of the months before is to make sure what is there is correct, complete, and defensible.
The pattern across healthcare clients is consistent. Organisations engage advisors at the wrong time (the month of the audit, instead of the year before it), present evidence in the wrong shape (raw exports instead of reconciled summaries), and discover gaps once they are uncloseable. These mistakes are routinely costly and entirely avoidable.
What follows is a working view of what a B-BBEE verification actually inspects, in the order it inspects it, and where healthcare organisations most often leak the points they came in to claim.
What the auditor opens first
The opening session is short and almost always the same. Auditors confirm the entity scope, the measurement period, and the priority elements. They ask for the affidavit or audited financials, the empowerment shareholder register where an ownership claim exists, and the trial balance for the period.
If the entity scope is wrong (a holding-company structure being verified instead of the operating company, or a permanent establishment that has been improperly delineated), every subsequent number is anchored to the wrong base. We have seen verifications restart from this point often enough to take it seriously.
Where healthcare organisations leak points
Three patterns recur, in roughly this order.
- Skills spend reported but not credentialed. The biggest and most common leak. Spend appears on the books while the supporting documents (attendance registers, accredited training-provider proofs, certificates of completion) are missing or inconsistent. Auditors disallow what they cannot evidence. We have seen organisations forfeit four to six points here on a single audit, almost always recoverable with a half-day of pre-audit reconciliation.
- Preferential procurement spend with thin substantiation. BEE certificate copies are old, supplier categorisations are inferred rather than documented, or the recognised spend calculation is run on the wrong base. Procurement teams report a spend number; the audit derates it because the substantiation falls short. The fix is unglamorous (a quarterly supplier-certificate refresh and a written calculation methodology) and it lifts the procurement pillar more than any other intervention.
- SED programmes that exist on paper, with thin field evidence. The contributions cleared bank reconciliations. The recipient organisations are real. The narrative tying the spend to a beneficiary outcome is missing, along with photographic or third-party evidence. Auditors increasingly want a story alongside a transfer. The score may hold; the trust the CSR conversation should have built does not arrive.
What audit-ready actually means
Audit readiness is a state maintained over time. In our practice, it rests on three habits.
The first habit is reconciliation. For each scoring element, one page summarises: the population of items, the recognised value, the calculation methodology, and the supporting evidence list. The auditor reads the one-pager first and the raw data second. Audits that begin with reconciliations close in a fraction of the time of audits that begin with spreadsheets.
The second habit is source-by-claim. For each line of recognised spend, a single source document can be produced within minutes of the same conversation. This is a discipline. Organisations that get it right tend to keep evidence in a single shared folder structured by pillar.
The third habit is narrative alignment. The scorecard is a quantitative document. The submission packet is a narrative one. The two should agree. When management-control percentages are improving, the appointment history should show it. When skills spend is concentrated in a single training provider, the narrative should explain why. Auditors use the narrative to interpret the numbers, and a well-written submission shortens every subsequent question.
What audit support looks like in practice
In a real engagement we work backwards from the verification date. Three months out, we run a desktop audit against the same codes the verifier will use, and produce a gap list. Two months out, we close the gaps that can be closed and document the ones that cannot. The month before, we assemble the pillar reconciliations and the supporting-evidence folders, and walk the leadership team through what an auditor will ask and how to answer.
The verification itself is then short. The score is rarely a surprise, and when it surprises, it surprises in the right direction.
