Supplier Risk
CSD Status & Self-Service Mismatch
Reconciles vendor master records against Central Supplier Database registration status.
Why vendor records must reconcile to the Central Supplier Database
The Central Supplier Database is the single source of truth for supplier registration with the state, and a vendor master that diverges from CSD status risks transacting with unregistered, restricted or de-registered suppliers contrary to National Treasury requirements. Mismatches also conceal tax, banking and ownership changes captured at CSD. AuditPro Core reconciles vendor records against CSD so SCM works from registration data that is current and authoritative.
The Numbers
AuditPro Core renders this view from your tenant's live, tamper-evident records. The figures below are illustrative sample data.
Vendors Matched
3,460
Not on CSD
142
4.1%
CSD Restricted
37
R 11.9m paid
Detail Mismatch
208
Vendors by CSD Reconciliation Outcome
Spend to Non-Active CSD Suppliers
| Supplier | CSD Status | Spend (R'm) | Action |
|---|---|---|---|
| Vendor 3510 | Restricted | 4.2 | Hold payments |
| Vendor 3622 | Not registered | 2.8 | Investigate |
| Vendor 3733 | Restricted | 1.9 | Hold payments |
| Vendor 3844 | Deregistered | 1.1 | Recover |
Figures shown are illustrative sample data for demonstration. AuditPro Core renders these views from your own tenant's live, tamper-evident records.
CSD as the authoritative register
Suppliers to the state must be registered on the CSD, which verifies identity, tax, banking and ownership against source authorities. The local vendor master should mirror, not contradict, that record.
Status and restriction flags
CSD reflects whether a supplier is active, restricted or tax-non-compliant. Transacting against a vendor master that ignores a CSD restriction exposes the institution to dealing with a barred supplier.
Drift between systems
Banking changes, name changes and de-registrations recorded at CSD must propagate to the vendor master. Drift between the two is where stale or fraudulent details survive.
How AuditPro Core Bridges the Gap
- Reconciliation: matches each vendor record to its CSD entry and reports status and detail mismatches.
- Restriction screening: flags payments or awards to suppliers carrying a CSD restriction or non-compliance.
- Exception workflow: routes mismatched records for correction against the authoritative CSD data.
- Continuous monitoring: re-runs the reconciliation as CSD and the master refresh.
Key Takeaways
- The CSD, not the local master, is the authoritative supplier register.
- A vendor master that ignores a CSD restriction can transact with a barred supplier.
- Banking and ownership changes at CSD must propagate to the master.
- Reconcile continuously so drift never accumulates.
See This on Your Own Data
AuditPro Core renders this dashboard from your tenant's live, tamper-evident records — every figure traceable to source.