ESD Reporting for Funders: What to Include and How Often to Report

02 Jun ESD Reporting for Funders: What to Include and How Often to Report

Most ESD programmes don’t fall apart because the money wasn’t spent well. They fall apart at reporting time, when a funder asks “show me the impact” and the answer is a folder of invoices with no story attached. Good reporting is what turns a compliance spend into a programme a corporate is willing to keep funding — and it’s also what a verification agency needs to award you the points in the first place.

The confusion usually comes from treating these as one audience. They’re not. Your corporate funder wants to know the programme is working and their money is safe. Your B-BBEE verification agency wants documented, auditable evidence that a specific contribution meets the Codes’ definition of enterprise or supplier development. Build a reporting rhythm that serves both, and neither one catches you scrambling.

Two Audiences, Two Different Reports

A funder relationship report and a verification evidence file look similar on the surface — both reference the same beneficiaries, the same spend, the same milestones — but they’re read differently and they’re due on different clocks.

Your funder (the corporate whose ESD or supplier development budget you’re implementing) wants a narrative: who’s being supported, what’s changing for them, whether the programme is on track against the plan you agreed, and any risks worth flagging early. They’re reading for relationship management and budget justification, and they typically want this more often than once a year — a programme they only hear about at certification time feels unmanaged, whatever the actual quality of the work.

Your verification agency wants something narrower and more exacting: proof that the contribution qualifies for points under the B-BBEE Codes. That means agreements, proof of payment or in-kind support, evidence the beneficiary meets the qualifying criteria (black ownership percentage, EME or QSE status, annual turnover), and evidence of outcomes where the Codes require it. This report is produced once a year, timed to your scorecard verification cycle, and it needs to survive an auditor who has never met your beneficiaries and has no reason to take your word for anything.

What Verification Agencies Actually Require

SANAS-accredited verification agencies work from the substance of the B-BBEE Codes, not from goodwill. For an ESD contribution to count, the evidence file generally needs to show four things: the agreement establishing the relationship and its terms, proof the support was actually delivered (payment records, delivery notes, signed attendance registers for training or mentorship), the beneficiary’s qualifying status at the time of the contribution, and — increasingly — evidence of outcome, not just activity.

That last point matters more than it used to. Draft Statement 400 of 2026, the proposed amendment to the B-BBEE Codes published for comment by the dtic, moves ESD toward what the amendment calls a more structured approach: formal needs analyses before a programme starts, defined performance indicators, ongoing monitoring and evaluation, and verified outcome reporting before points are recognised. In plain terms, the direction of travel is that simply proving you paid out the money is no longer treated as sufficient — you need to show what that money did.

The amendment also proposes an alternative compliance route: measured entities could contribute 3% of Net Profit After Tax to a centrally administered Transformation Fund in place of the current 2% Supplier Development and 1% Enterprise Development targets. If it’s finalised as drafted, that gives corporates a simpler compliance pathway for the contribution itself — but it doesn’t remove the reporting obligation from implementing agents running programmes outside the fund, and if anything it raises the bar for programmes that want to keep the direct-spend route rather than defaulting to the fund.

Where Section 13G Fits — and Who It Actually Applies To

It’s worth being precise here, because this requirement gets misapplied more often than it should. Section 13G of the B-BBEE Act requires an annual compliance report, but only from three categories of entity: government departments and organs of state, companies listed on the JSE, and Sector Education and Training Authorities. Private companies — including most of the corporates funding ESD programmes — are not legally required to submit a 13G report to the B-BBEE Commission.

Where 13G does apply, the report must be submitted within 30 days of the annual financial statements being approved, or within 90 days of financial year-end, and it has to include a full list of B-BBEE-compliant suppliers with total expenditure per supplier, each supplier’s B-BBEE status and ownership detail (including black women ownership), and — specific to ESD — the identity of every beneficiary receiving development support, the value of that support, and the beneficiary’s level of black ownership.

Even where a corporate isn’t legally obliged to file a 13G report, most well-run ESD programmes end up producing something structurally similar anyway, because it’s the same information a verification agency will ask for and the same information a funder’s own board wants to see. Building your annual report to 13G’s level of detail from the start means you’re never rebuilding it under pressure.

A Practical Reporting Calendar

The programmes that never scramble at verification time run on a simple rhythm: continuous internal tracking, quarterly funder reporting, and an annual evidence pack built from material that’s already been collected rather than reconstructed.

Monthly or continuously — log every disbursement, delivery, training session, and beneficiary interaction as it happens, with the underlying proof (invoice, attendance register, delivery note) filed against it immediately. This is the single habit that makes everything downstream easier; it’s far cheaper to file a signed register the week it happens than to chase a beneficiary for a signature eleven months later.

Quarterly — send your funder a short report: beneficiaries supported this quarter, spend against the annual plan, milestones achieved versus planned, and anything at risk. Keep it readable — a one-to-two-page narrative with a simple table beats a data dump, and it’s this cadence that builds the relationship a funder needs to keep renewing the budget.

Annually, ahead of verification — assemble the full evidence file: agreements, consolidated proof of support, beneficiary qualifying documentation, and outcome evidence mapped to the specific element of the scorecard it supports. If you’ve kept the monthly log current, this becomes an assembly exercise rather than a research project.

What Belongs in the Core Report Template

Whether you’re writing for a funder or preparing a verification file, the underlying data set is largely the same — it’s the framing and level of detail that changes. At minimum, build your template around:

• A beneficiary register: name, B-BBEE status, ownership percentage (including black ownership and black women ownership), enterprise size classification, and the date the relationship started.
• Value of support per beneficiary, broken down by type — cash grant, loan, mentorship hours, market access facilitated, or in-kind contribution — because verification agencies weight these differently.
• Milestones achieved against the plan agreed at the start of the relationship, not just spend to date.
• Outcome evidence — revenue growth, jobs created or sustained, contracts won, or capability gained — with a source for each figure rather than an unsupported claim.
• Sign-off documentation — the beneficiary’s own confirmation that support was received, dated and signed, which is one of the first things a verification agency will ask to see.

Keep the same beneficiary IDs and the same categories across every quarterly report and the annual file. Consistency across periods is what lets a funder — or an auditor — trust the trend line rather than re-verifying every number from scratch each time.

Frequently Asked Questions

Do private companies have to submit ESD compliance reports to the B-BBEE Commission?

No. Section 13G’s mandatory annual compliance report applies only to organs of state, JSE-listed companies, and SETAs. A private company funding an ESD programme still needs a verification-ready evidence file for its own scorecard, but that file goes to its accredited verification agency, not to the Commission.

How often should I report to my ESD funder if there’s no formal requirement in the agreement?

Quarterly is the practical standard across well-run programmes, even where the funding agreement doesn’t specify a cadence. It’s frequent enough to catch problems early and keep the relationship visible, without turning reporting into a full-time job. Confirm the cadence explicitly in writing with your funder at the start of the relationship so expectations are shared rather than assumed.

What changes for ESD reporting under the 2026 draft B-BBEE amendments?

Draft Statement 400 of 2026 proposes moving ESD toward a more structured, outcomes-based approach: a documented needs analysis before a programme starts, defined performance indicators, ongoing monitoring and evaluation, and verified outcome reporting before points are recognised. It’s still in draft and open to comment, but the direction is clear — proof of activity alone is becoming less sufficient, and proof of outcome is becoming the expectation.

If your reporting currently starts and stops at “here’s what we spent,” this is worth building out before it becomes mandatory rather than after. A reporting structure that satisfies a demanding funder today will satisfy a stricter Code tomorrow — the reverse is rarely true.