Supplier Risk
Dormant Vendor Reactivation
Tracks suppliers reactivated after long dormancy and immediately transacting, a shell-vendor indicator.
Why reactivated vendors deserve a second look
A supplier dormant for years that suddenly reactivates and immediately transacts can be a legitimate returning vendor, or a shell account revived to move funds with a pre-existing, trusted record. Because the vendor already passed onboarding long ago, its reactivation can slip past the scrutiny a new vendor would attract. AuditPro Core tracks long-dormant suppliers that reactivate and transact at once so these are re-verified rather than trusted on history.
The Numbers
AuditPro Core renders this view from your tenant's live, tamper-evident records. The figures below are illustrative sample data.
Reactivations
76
this year
Spend Post-Reactivation
R 29.3m
▲ R 6m
Dormant 24+ Months
41
of reactivations
Re-vetted
33
of 76
Reactivations by Dormancy Length (count)
Highest Spend After Reactivation
| Vendor | Dormant (mo) | Orders Since | Spend (R'000) |
|---|---|---|---|
| Vendor 0223 | 41 | 22 | 6820 |
| Vendor 0588 | 33 | 18 | 4910 |
| Vendor 0941 | 52 | 14 | 3740 |
| Vendor 1304 | 27 | 11 | 2630 |
| Vendor 1655 | 38 | 9 | 1980 |
Figures shown are illustrative sample data for demonstration. AuditPro Core renders these views from your own tenant's live, tamper-evident records.
Dormancy and trust inheritance
An old vendor record carries inherited trust and may have stale verification. Fraud can exploit that trust by reviving a dormant account rather than creating a flagged new one.
Reactivate-then-transact pattern
Immediate transacting after long dormancy mirrors the velocity risk of new-vendor rush: the speed leaves no window for re-verification of banking, ownership or tax status.
Stale verification data
Banking, directors and tax status all change over years of dormancy. Transacting on outdated CSD data means paying against assurance that may no longer hold.
Ownership change on dormant shells
A dormant entity can be acquired and repurposed, so the directors transacting today may differ entirely from those originally verified.
How AuditPro Core Bridges the Gap
- Pattern detection: AuditPro Core measures dormancy length and flags suppliers transacting soon after reactivation.
- Reconciliation: Reactivated suppliers are re-checked against current CSD, banking and director data.
- Exception workflow: Reactivate-then-transact cases route for re-verification before payment.
- Continuous monitoring: Vendor-master activity is tracked so revivals are caught as they happen.
Key Takeaways
- Reactivated vendors inherit trust but may carry stale verification.
- Immediate transacting after dormancy mirrors new-vendor rush risk.
- Re-verify banking, directors and tax before paying a revived supplier.
- A dormant shell may have changed ownership since onboarding.
See This on Your Own Data
AuditPro Core renders this dashboard from your tenant's live, tamper-evident records — every figure traceable to source.