Despite the apparent simplicity of the CSD registration system, a significant number of suppliers — particularly smaller businesses and first-time registrants — encounter persistent problems that prevent them from achieving or maintaining an active CSD status. This module covers the most frequently encountered CSD problems, their root causes, and the specific steps required to resolve each one.
Inactive CSD status is the most commonly reported CSD problem. An inactive status means that one or more of the live compliance checks has failed: either the tax compliance check, the CIPC registration check, or the bank account verification is returning a failure result. The first diagnostic step is to log into your eFiling account and check your tax compliance status — if you have outstanding returns or debts, resolve these with SARS first. The CSD status update after a SARS resolution is typically reflected within 2–5 business days of the compliance being corrected, not immediately. Next, check your CIPC status by logging into cipc.co.za and confirming that your annual returns are up to date and your registration status is 'In Business'. Finally, confirm your banking details by calling your bank and verifying that the account is active and in good standing.
Tax compliance failures are often more complex than they first appear. SARS may have an objection outstanding on your account, a payment arrangement that has lapsed, an assessed penalty that you were unaware of, or a VAT audit finding that has created a balance. Log into eFiling and review the 'My Compliance Profile' section, which shows the compliance status for each tax type separately. If you see red indicators for any tax type, click on the detail to understand the specific issue. For complex tax disputes, engaging a registered tax practitioner is advisable — they can access your account through eFiling and resolve issues more efficiently than self-service.
Banking verification failures occur when the bank account details on the CSD cannot be matched to an active, validly named account. Common causes include: the account is in a personal name when the CSD requires it to be in the company name, the account has been flagged by the bank for unusual activity, the account number was entered with a transposition error, or the branch code is the general clearing branch code rather than the specific branch code for your account. To resolve a banking verification failure, obtain a fresh bank confirmation letter on official bank letterhead confirming the account number, account holder name, branch code, and account type, then upload this to the CSD and request re-verification.
CIPC versus B-BBEE name mismatches are a particularly frustrating problem that arises when a company has changed its trading name, brand name, or legal name without updating all the relevant documents. The CSD requires that the company name on the B-BBEE certificate exactly matches the registered company name in the CIPC register. If your company rebranded and the B-BBEE certificate reflects the old name, procurement officials will flag this as a discrepancy and your B-BBEE preference claim may be disallowed. Resolution requires obtaining a new B-BBEE certificate in the correct legal name, which means going through a new verification process.
CSD support channels for unresolved problems include the National Treasury CSD helpdesk reachable at csd@treasury.gov.za and the telephone helpline (the number is published on the supplier.gov.za contact page). When logging a support query, always include your CSD supplier number, the specific error message or status issue, the steps you have already taken to resolve it, and copies of the relevant documents. Response times vary from 2 to 15 business days depending on the complexity of the issue. For urgent matters — particularly where a bid closing date is imminent — mention the urgency in your query and follow up by phone. In genuine emergencies, your TenderForce representative or procurement consultant may be able to escalate through official channels.