What should I do when my CSD bank verification remains unresolved?

Read the result before trying another entry

“Unresolved” can describe a request still awaiting a response, a failed match or a case requiring further attention. Start by recording the wording currently shown, the affected account and when the last action occurred. The reason matters because a pending response and a confirmed mismatch need different next steps.

The official CSD registration guidance identifies bank information as part of the supplier record and directs users to banking guidance. Use the current portal and official support information for the actual case. Older screenshots or instructions may not match the screen now displayed.

Do not replace the existing details repeatedly simply because there is no immediate success message. First establish whether the request was saved, sent for verification or returned with a reason that can be investigated. Keep evidence of the current position.

Compare identity details held by the bank

A bank account can be active and usable while a verification request still fails to match its recorded holder details. Compare the supplier’s legal identity with the identifying information the bank has on its system. Check the registered name, registration or identity number and the account holder information requested by the current process.

An Eastern Cape Provincial Treasury banking notice illustrates how differences in the recorded company name can cause a failed verification. It is historical guidance, so use it to understand the matching issue rather than as a promise about today’s screens or turnaround.

Ask the bank to confirm the information relevant to verification where the documents and system appear inconsistent. Do not invent a different legal identity to force the result through. Resolve the underlying record appropriately.

Keep the status history when a result changes from pending to failed. The new reason may make an earlier support request incomplete. Update the same case with the latest result, identify any action taken in between and ask which discrepancy remains. This preserves a coherent investigation rather than leaving separate messages that describe different stages as though they were simultaneous.

Check the account fields as one complete record

Review the account number, account type, branch information and holder details together. A correction to the name will not fix an incorrect account number. Equally, changing an account type without evidence may add a new problem to an existing identity mismatch.

Compare the entered data with a current record obtained through the bank’s authorised channel. Be careful when copying from a scanned page, where similar characters or cropped digits can cause errors. Confirm that the account belongs to the supplier relevant to the profile.

Keep a short record of each confirmed correction and its reason. The purpose is to create a traceable sequence, not to preserve every exploratory guess. If no mismatch can be established, stop changing values and prepare a focused support query using the current result.

A focused investigation checklist

Keep the full evidence private. A public discussion about the error should not contain an unredacted bank statement, identity document or account credentials. Use the relevant official channel for documents needed to investigate the case.

Illustrative example: a company name has changed

A fictional supplier changes its company name and updates its working documents. Its bank still holds the old legal name, while the CSD entry uses the new one. The supplier can still make ordinary bank transactions, which leads the owner to assume the verification problem must be a broken website.

The useful investigation compares the current company record, the bank’s holder record and the data supplied for verification. The bank may need the appropriate company-change evidence before updating its record. The supplier should establish what the bank actually requires rather than altering the CSD name blindly.

After the confirmed correction, the administrator follows the current verification process and checks the resulting status. The case is complete only when the relevant record demonstrates the outcome. A submitted bank-change request is progress, but it is not the same as a successful verification.

What to include in an official support enquiry

Describe one clear issue: the supplier reference, affected verification function, current status or error and the date of the last relevant action. Explain what has already been checked and identify any source-record correction completed by the bank or another authority.

Attach only the evidence requested through the proper channel. Keep the case reference and the exact response. If the support team asks for a particular document, respond to that request rather than sending an unrelated folder containing all company information.

A good enquiry lets the recipient distinguish a capture error from a source-data mismatch or an unresolved system response. Avoid claims such as “everything is correct” without identifying the records compared. If the response does not resolve the issue, follow up under the same case with the remaining discrepancy clearly stated.

Do not use another account as an unexplained workaround

A payment deadline can tempt a supplier to insert someone else’s bank account or create a fresh profile. That does not resolve the original identity and verification issue. It can also make the records supplied to buyers inconsistent and introduce a new question about the intended payee.

If the business genuinely changes bank accounts, follow the appropriate change process and provide accurate supporting information. Keep the old and new account records distinct, record the effective change and verify the buyer’s payment-update procedure separately where relevant.

Do not describe a bank-account change as completed merely because a new row is saved. Check the verification result and any buyer-side requirement that applies to the actual transaction. The CSD record and a buyer’s invoice or payment process are related records, not interchangeable confirmations.

Handle a closing tender or payment query honestly

If the unresolved result affects an imminent bid, read the tender’s actual requirements and use the stated clarification route. Explain the current status accurately if asked. Do not change a downloaded report or claim that pending verification has passed.

For an existing payment query, identify which institution is asking for information and what its process requires. Keep the purchase order, invoice and supplier identity aligned. A support ticket may help explain the issue, but do not assume it automatically substitutes for a required verification outcome.

Record the answer and the next action. Where the buyer’s requirement cannot be established, preserve the uncertainty rather than promising the owner that payment or acceptance will occur on a particular date. The relevant institution controls its own decision.

Check the final result and preserve the handover

Once the issue appears resolved, review the current supplier record and report rather than relying only on an email saying a change was made. Confirm the correct account and supplier identity, the verification outcome and any remaining warning needing attention.

Save the relevant completion evidence with the support case and the approved bank records. Tell the responsible administrator what was corrected so that an old document is not copied back into the profile later. Update the internal checklist for future company or bank changes.

Also review who can maintain the profile. Changes in staff or advisers should leave the business with authorised access and a clear record of responsibility. Sharing a former administrator’s password is not a useful long-term handover method.

Get help with the specific mismatch

For assistance reviewing the supplier record, enquire about Vatco’s CSD service and describe the status, dates and checks already completed. The useful starting point is the actual mismatch or unresolved result, not a request to “make the account compliant” without context.

If the underlying company details are wrong, the company amendments service may be relevant to a separate correction. Keep each authority’s update and evidence distinct.

This troubleshooting process aims to establish a reliable record and a documented outcome. It cannot promise a verification time or override the bank, CSD or procuring institution’s requirements.