B-BBEE Verification Supplier Invoice Evidence Pack

A B-BBEE verification supplier invoice evidence pack should turn a full year of AP data into three things: a verification-ready Excel supplier ledger, the largest invoice per sampled supplier, and matching B-BBEE certificate or affidavit evidence. The pack should reconcile invoice totals to the AP ledger, flag supplier classification and recognition multipliers, and preserve source-file paths so evidence queries can be answered without re-opening months of supplier folders.

That is a different job from learning the preferential procurement rules. The rules explain what a measured entity can claim. The evidence pack proves where the spend came from, which supplier status evidence supported it, and how a verification analyst can trace a figure in the workbook back to the actual invoice file.

The dtic B-BBEE Verification Manual provides guidelines for the authentication and substantiation of B-BBEE reporting, as well as minimum norms and procedures for verifying the B-BBEE Codes of Good Practice. That is why the pack should be built around traceability rather than presentation. A neat supplier list is not enough if the underlying invoice totals, source files, and certificate references cannot be followed.

For a procurement officer, transformation manager, B-BBEE coordinator, or QSE finance officer, the practical output is a workbook that answers predictable verification questions. Which suppliers made up procurement spend for the measured year? Which invoice files support those totals? Which invoice is the largest for each sampled supplier? Which certificate, affidavit, ownership flag, recognition level, and effective period was used when the spend was classified?

Keep the scope tight. Code 400, ESD mechanics, and procurement recognition rules matter, but this workflow is not a scorecard tutorial. It is the AP-to-evidence-pack assembly step that sits before formal scoring, consultant review, or verification agency sampling.

Start with the AP exports and source invoice folder

Start from the full AP supplier ledger for the measured financial year, not from the suppliers you expect the verification agency to sample. The population matters because the sample is drawn after submission, and the largest invoice per supplier cannot be identified reliably from a partial folder.

For each entity or branch included in the measured entity's procurement spend, export supplier transactions for the period under review. Keep the accounting system supplier code if one exists, but do not rely on it as the only identifier. Supplier names, trading names, VAT numbers, and company registration numbers are often less tidy than the master data suggests.

The invoice extract should be prepared as a row-level workbook. At minimum, include supplier name as shown on the invoice, VAT number, company registration number where present, invoice date, invoice number, excluding-VAT amount, VAT amount, gross amount, entity, and source filename. Those fields overlap strongly with the supplier-invoice fields to capture for bookkeeping and AP, and they also support a separate VAT201 supplier-invoice working file, but the B-BBEE pack adds a verification concern: every spend row should still point back to the document that supports it.

Keep the source path or file reference with each row. A filename such as ACME-Inv-10482.pdf is useful only if the team can locate the file quickly inside the evidence folder. A better extract has a stable folder reference, document name, and, where possible, a page number or batch reference.

Do not mix B-BBEE status evidence into the invoice extract too early. The first workbook tab should answer: what supplier invoices exist in the year, what amounts do they carry, and where are the source files? Certificate, affidavit, ownership, classification, and recognition fields can be joined once the transaction population is clean.

Extract invoice rows before calculating supplier spend

Extraction is not the same as B-BBEE calculation. At this stage the task is to convert supplier PDFs, scans, and images into consistent evidence rows so the workbook can be reconciled and classified later.

For a B-BBEE annual verification pack, extract the full invoice population for the measured year. One row per supplier invoice is usually the cleanest starting point. Capture the supplier legal or trading name as shown, VAT number if present, company registration number where present, invoice date, invoice number, excluding-VAT amount, VAT amount, gross total, entity, and source file reference. If the supplier has line items that affect classification, keep a separate line-item extract rather than crowding the main supplier-ledger tab.

Manual keying creates two verification risks. First, teams tend to type the invoices already requested by the consultant, which means the workbook no longer proves the full spend population. Second, the largest invoice per supplier can be missed if supplier documents are sitting across email attachments, scanned batches, and accounting exports. The evidence pack should be built from the whole AP source set before the sample is selected.

This is where invoice extraction to Excel fits the workflow. With Invoice Data Extraction, users upload PDF, JPG, or PNG invoices, describe the fields they need in a prompt, and download structured Excel, CSV, or JSON output. The same interface handles annual batches: up to 6,000 files at a time, or a single PDF of up to 5,000 pages.

The extraction prompt should be practical rather than clever. Ask for the fields needed by the workbook and require the output to keep the source filename with each row. Do not ask the extraction tool to decide B-BBEE recognition levels, verify certificates, or score preferential procurement. Those decisions depend on supplier-status evidence and verification judgement, not on the invoice image alone.

Reconcile the evidence workbook before the verification sample is selected

Before recognition levels or ownership flags are applied, reconcile the extracted invoice workbook back to the AP ledger. The control is simple in principle: supplier spend in the evidence pack should tie back to the accounting records for the measured year, with explained differences rather than silent adjustments.

A defensible invoice reconciliation process starts by comparing total spend per supplier between the AP export and the invoice extract. Investigate unmatched invoices, duplicate invoice numbers, supplier rows with missing VAT numbers, and suppliers split across trading names. Where a supplier appears under several codes, decide whether the evidence pack will group them under one supplier identity or keep them separate with a note.

Credit notes need explicit handling. If they reduce procurement spend, keep them visible in the workbook rather than deleting them from the extract. The same applies to foreign suppliers, intercompany suppliers, non-procurement spend, once-off adjustments, and other exclusions. A verification analyst is less concerned that an exception exists than that the measured entity can explain how it was treated.

Use an exceptions tab for items that do not fit the main supplier-ledger logic. It can record the supplier, invoice or credit note reference, amount, issue, treatment, and reviewer comment. That tab prevents undocumented changes from creeping into the working file and gives the consultant or verification agency a clean place to review judgement calls.

Only after the population reconciles should the workbook identify the largest invoice per supplier. Group the rows by normalised supplier identity, rank invoices by gross or excluding-VAT amount according to the evidence request, and preserve the source-file reference for the selected invoice. Lock the extraction date or version used for verification so the pack does not change after queries begin.

Join supplier certificates, affidavits, and recognition fields

Once the invoice population reconciles, add the supplier-status evidence that explains how each supplier's spend will be recognised. Keep the invoice evidence and the B-BBEE credential evidence distinct: the invoice proves the transaction and amount, while the certificate or affidavit supports the recognition treatment applied to that spend.

Add credential fields such as certificate or affidavit file reference, expiry date, EME, QSE, or Generic classification, recognition level, recognition-level multiplier, 51 percent black-owned flag, 30 percent black-women-owned flag, empowering-supplier status, and effective period. These fields turn the supplier ledger from a finance export into a B-BBEE preferential procurement evidence pack Excel file.

The joins deserve careful review. A supplier may trade under a name that differs from the registered name on the certificate. VAT numbers may be missing on older invoices or absent from the supplier master. Duplicate supplier records can split spend across several codes, while an expired affidavit can leave part of the year unsupported. Credentials collected after the invoice date should be reviewed against the effective period before they are used in the workbook.

Where the team needs the document-level checklist, use the existing South Africa B-BBEE procurement invoice requirements guide rather than rebuilding that material inside the evidence-pack file. This workbook has a narrower purpose: connect supplier invoice spend to the status evidence that supports the recognition level and multiplier used for verification.

For sampled suppliers, the file reference should lead to both sides of the evidence: the largest invoice or requested invoice set, and the valid certificate or affidavit used for that supplier. If either side is missing, flag it in the exceptions tab instead of letting the workbook imply that the evidence is complete.

Handle mid-year supplier status changes and sample queries

Supplier status is not always static for the full measured year. A supplier can move from EME to QSE, renew an affidavit, issue a new certificate, change ownership status, or provide evidence that covers only part of the period under review. The evidence pack should record effective dates so spend is not treated as if one credential applied to the whole year when the file does not support that treatment.

If spend must be split because supplier status changed during the year, make the split visible. Keep the invoice rows in the underlying extract, add the credential effective period, and show how the supplier summary allocates spend across the relevant recognition treatment. Avoid overwriting the original supplier row with a final scorecard conclusion; the workbook should preserve the trail from invoice to credential to recognition field.

For a sample query, the team should be able to answer from the pack without rebuilding the file. A selected supplier should have ledger rows, the largest invoice file or requested invoice files, the matching certificate or affidavit, and any exception note. If a VAT number is missing, a trading name does not match the certificate, or two supplier records conflict, record the issue and the treatment applied.

This is also the point where the roles separate. The evidence pack prepares clean invoice and supplier-status data. A B-BBEE platform, consultant, or verification agency may then handle scoring, interpretation, sample review, and formal verification. Keeping those jobs separate reduces confusion: invoice extraction supports the evidence base, while B-BBEE verification decides how that evidence is assessed.

Build the pack so the next evidence request is answerable

A ready B-BBEE supplier invoice evidence pack should have a workbook and a folder structure that mirror each other. The workbook should include tabs for the invoice extract, supplier summary, credential register, exclusions or exceptions, and sample index. The folder should hold source invoices, supplier certificates or affidavits, and any working papers needed to explain adjustments.

The invoice extract is the transaction population. The supplier summary groups spend by supplier identity and shows the totals that feed the preferential procurement analysis. The credential register records the B-BBEE evidence attached to each supplier. The exceptions tab explains exclusions, mismatches, missing fields, credit notes, foreign suppliers, and other judgement calls. The sample index points to the largest invoice per supplier or any specific invoice files requested by the consultant or verification agency.

Before submission, check that the AP reconciliation ties out, the largest invoice per supplier is retained, source-file paths open correctly, expired certificates are flagged, supplier status fields are complete, and exceptions are explained in plain language. A workbook that balances but cannot locate its source files will still slow the verification process.

The finished pack should make authentication and substantiation practical. Every supplier-spend number should lead back to invoice evidence, and every recognition treatment should lead back to supplier-status evidence. That is the difference between a spreadsheet that looks complete and an evidence pack that can survive the next verification query.