Compliance Monitoring
Vendor Master Data Integrity
Integrity checks on the supplier master file, flagging duplicates, CSD mismatches and bank-detail changes.
Why supplier master integrity is a fraud and SCM control
The vendor master file drives every payment, so duplicates, CSD mismatches and unauthorised bank-detail changes are direct enablers of duplicate payments, irregular expenditure and supplier fraud that the AGSA and PRECCA-aligned investigations routinely uncover. Continuous integrity checking is a core SCM and financial control. AuditPro Core tests the supplier master for these defects so they are corrected before they cause loss.
The Numbers
AuditPro Core renders this view from your tenant's live, tamper-evident records. The figures below are illustrative sample data.
Active vendors
6,210
Duplicate suspects
187
3% of file
CSD mismatches
94
tax / banking
Bank changes (90d)
312
review pending
Master data exceptions by type
High-risk vendor exceptions
| Vendor | Issue | Spend (12m) | Risk |
|---|---|---|---|
| Sizwe Trading | Bank detail change x3 | R 8.4 m | High |
| Khanya Supplies | Duplicate of KS Pty | R 2.1 m | Medium |
| Bopha Projects | Director = employee | R 5.7 m | High |
| Velo Services | Invalid VAT number | R 0.9 m | Medium |
Figures shown are illustrative sample data for demonstration. AuditPro Core renders these views from your own tenant's live, tamper-evident records.
Duplicates enable double payment
The same supplier created twice allows the same invoice to be paid twice and obscures spend analysis. Detecting near-duplicates requires fuzzy matching on name, registration and banking, not exact matches alone.
CSD alignment is mandatory
Suppliers must be registered and current on the Central Supplier Database, and master records should match CSD particulars. Mismatches signal either stale data or vendors transacting outside the prescribed process.
Bank-detail changes are the prime fraud vector
Unauthorised changes to supplier banking divert legitimate payments to fraudsters. Every change should be independently verified and logged before it takes effect.
How AuditPro Core Bridges the Gap
- Duplicate detection: AuditPro Core applies fuzzy matching across name, registration and banking to surface duplicate vendors.
- CSD reconciliation: master records are compared to CSD particulars to flag mismatches and lapsed registrations.
- Change monitoring: bank-detail changes are flagged for verification with the change history retained.
- Audit-ready export: integrity exceptions and resolutions feed the SCM and AGSA files.
Key Takeaways
- Fuzzy matching, not exact matching, finds real duplicates.
- Master records should reconcile to current CSD data.
- Bank-detail changes are the leading payment-fraud vector.
- Continuous checking prevents loss rather than detecting it late.
See This on Your Own Data
AuditPro Core renders this dashboard from your tenant's live, tamper-evident records — every figure traceable to source.