Law & Regulation
Codes of Good Practice on Broad-Based Black Economic Empowerment (Generic Codes)
The independently operative measurement layer beneath the B-BBEE Act, providing the general methodology for measuring an enterprise's B-BBEE status for entities not governed by a more specific applicable sector code: ownership, management control, skills development, enterprise and supplier development, and socio-economic development, plus entity categories, priority elements, subminimum requirements, discounting, recognition levels and evidence. A sector code may displace the generic framework for an entity within its defined scope — correct code selection is a threshold exercise before score calculation. Proposed 2026 amendments (Hold, ZA-L-058) were not verified as a final effective package by the research cut-off and do not displace the operative Codes.
Legal Significance
What This Instrument Does
Establishes the general methodology for measuring an enterprise's B-BBEE status, organising assessment around ownership, management control, skills development, enterprise and supplier development, and socio-economic development, and addressing entity categories, scorecard application, priority elements, subminimum requirements, discounting, recognition levels and evidence. Instrument boundary: not the B-BBEE Act, a procurement statute, a universal sector code, a tender specification or a project-specific local-content regime; does not guarantee contract award or licensing success, and does not convert ordinary CSR, supplier payments or nominal ownership into qualifying recognition without satisfaction of the applicable rules and evidence standards.
Why It Matters
The Codes affect bid competitiveness, supplier recognition, consortium strategy, ownership structuring and the ability of customers to claim procurement recognition from spend. In major infrastructure programmes they can shape EPC and O&M supply chains, subcontracting, enterprise-development initiatives and reporting systems throughout delivery. For investors and lenders, the principal risk is incorrect code selection, unsupported evidence, loss of priority-element compliance or supply-chain changes altering the represented status — a certificate should be tested against the legal category and underlying facts.
Key Provisions
- Statement 000 — General principles and framework
Establishes the generic measurement architecture, interpretation principles and overall scorecard operation. Practical consequence: confirm that no applicable sector code displaces the generic scorecard before measuring status.
- Statement 000 — Entity categorisation
Differentiates enterprise categories and applicable measurement treatment using the current code criteria. Practical consequence: use current thresholds and evidence, not historical figures hard-coded into long-term documents.
- Statement 000 — Priority elements and subminimums
Identifies priority elements and consequences where required subminimum performance is not achieved. Practical consequence: model priority-element compliance separately rather than relying only on aggregate score.
- Statement 000 — Recognition levels
Converts measured points and applicable adjustments into a B-BBEE recognition status and procurement-recognition outcome. Practical consequence: state status only for the applicable measurement period and evidence set — it is not permanent.
- Statement 100 — Ownership
Measures voting rights, economic interest and specified participation in ownership. Practical consequence: examine beneficial economics, governance rights, funding and exit mechanics together — nominal title alone is insufficient.
- Statement 100 — Net value and ownership substance
Tests the extent to which recognised ownership carries real accumulated economic value within the code methodology. Practical consequence: model debt, vesting and value realisation over time rather than measuring headline equity only.
- Statement 200 — Management control
Measures participation in board, executive, senior management and workforce structures. Practical consequence: ensure appointments carry real authority and responsibilities supported by organisational evidence.
- Statement 300 — Skills development
Measures eligible expenditure and participation in recognised learning and development activity. Practical consequence: build qualifying programmes, records and completion evidence into project workforce planning.
- Statement 400 — Enterprise and supplier development
Measures procurement from recognised suppliers and qualifying supplier/enterprise-development contributions. Practical consequence: establish supplier classification, spend traceability and beneficiary evidence before reporting deadlines.
- Statement 400 — Preferential procurement measurement
Recognises procurement spend according to supplier status and applicable code rules. Practical consequence: supplier status changes can affect the purchaser's measured performance — monitor key vendors throughout the period.
- Statement 400 — Supplier and enterprise development
Provides measurement treatment for qualifying support to beneficiary enterprises. Practical consequence: use documented, measurable and qualifying assistance rather than relabelling ordinary commercial payments.
- Statement 500 — Socio-economic development
Measures qualifying contributions supporting access to the economy under the code criteria. Practical consequence: distinguish qualifying measured contributions from general CSR or project mitigation obligations.
- Verification/evidence provisions — Substantiation and measurement period
Requires status to be supported by the evidence and period applicable under the Codes and verification framework. Practical consequence: preserve source data, ownership records, payroll, training and procurement evidence.
- Sector-code interface — Applicable-code hierarchy
Recognises that an applicable sector code may govern instead of the Generic Codes. Practical consequence: perform a documented sector-scope analysis for each material project participant.
- Transitional provisions in amending codes — Movement between code versions
Provides effective dates and transition treatment when final amendments alter the framework. Practical consequence: apply the version legally effective for the relevant measurement or decision date and retain the Gazette chain.
InfraLex Relevance
The operative measurement layer beneath the B-BBEE Act, retained as a standalone record because practitioners consult it independently to determine status and transaction consequences.
Legal Framework Position
- Local ContentImplementing Instrument
Primary / Parent Instrument
Instrument Overview
- Official Citation
- Gazette codes under section 9 of Act 53 of 2003; principal 2013 Generic Codes, as amended; Government Gazette 36928, 11 October 2013
- Instrument Type
- Code
- Source Language
- English
- Enactment Date
- 11 October 2013
- Last Verified
- 6 September 2026