CSD Registration Errors That Can Cost You a Tender

Your Central Supplier Database (CSD) profile is the single record every organ of state checks before it can legally award you a tender or pay you. It is also where quiet, easily-missed data mismatches accumulate over time — and unlike a missing document, a CSD error often isn't obvious until a bid evaluator pulls your report and finds something doesn't reconcile.

This article covers the specific CSD registration errors that most often cost South African suppliers a tender, and how to check for each one before it matters.

CIPC Mismatch

The CSD verifies your company and director details directly against CIPC records. If your registered company name, director details, or registration number on CSD don't match CIPC exactly — including small differences like an abbreviated trading name — verification fails silently, and your CSD status can show as unverified without a clear explanation in the interface. Check that your CSD profile mirrors your CIPC records character-for-character, not just approximately.

Tax Compliance Sync Delays

CSD pulls your tax compliance status from SARS, but the two systems don't always update in real time. It's possible to be fully tax compliant according to SARS while CSD still displays an old, non-compliant status because your Tax Compliance Status PIN wasn't refreshed on the CSD side, or the sync simply lags. Our guide on the SARS Tax Compliance Status PIN covers how to keep this current; on CSD specifically, re-verify your tax status directly on the platform rather than assuming a SARS update will reflect automatically.

Bank Verification Failures

CSD generates your supplier number (MAAA) immediately on registration, but you are not marked 'Verified' until your banking details clear a separate check — which typically takes around four working days. Verification commonly fails when the bank confirmation letter is outdated, or when the account holder name doesn't match your registered company name exactly. An unverified banking status can be enough for a procuring institution to treat your profile as incomplete.

B-BBEE Level Not Reflecting Correctly

B-BBEE status is not automatically verified on CSD — your certificate or sworn affidavit has to be uploaded manually, and if it isn't, or if an old certificate is still attached after a renewal, CSD can show an incorrect level or a 'non-compliant' status even though your actual B-BBEE standing is current. This is one of the most common CSD errors because it requires an active upload every time your certificate renews, rather than a one-time setup step.

Quick CSD Health Check

Why These Errors Are Easy to Miss

None of these four errors produce a hard rejection message when they occur — CSD generally still lets you save a profile with a mismatch, a pending bank verification, or a stale B-BBEE upload. The interface tells you your profile exists; it doesn't proactively tell you it's wrong in a way a procuring institution will flag. That's what makes CSD errors different from a missing SBD form: nothing forces you to notice until an evaluator pulls your report and something doesn't reconcile against CIPC, SARS, or your bank.

This is also why CSD errors tend to persist for months rather than getting caught on the first tender they affect. A business that registered correctly two years ago, then changed its trading name, switched banks, or let a B-BBEE certificate lapse without re-uploading the renewal, can carry a silent mismatch through several tender cycles before it actually causes a disqualification — at which point it isn't obvious that CSD, rather than the bid itself, is the point of failure.

Because CSD sits upstream of almost every other compliance check a procuring institution runs, an error here can quietly undermine a bid that is otherwise fully compliant. Treat a CSD health check as a standing item before every tender submission, not a once-off registration task — pull your own CSD report periodically and read it the way an evaluator would, rather than assuming that because the profile was correct once, it still is.

For the registration process itself, see our guides on how to register on the CSD and CSD document requirements.