When master data breaks your signals
Apimanagementhub is candid about a hard limit: anomaly detection cannot rescue broken vendor masters, duplicated customers, or drifting account maps. It will advertise the mess loudly.
Symptoms
- Hit rates spike after every ERP patch with no process change.
- The same “anomaly” repeats with different IDs for the same counterparty.
- Reviewers spend more time reconciling dimensions than reading evidence.
What to do instead of more rules
Pause net-new thresholds. Escalate a data-quality workstream with named owners. Keep a thin detection set for cash and related-party patterns that still matter while the foundation is fixed.
We teach recognition of this condition in the flagship FAQ and Module 1. We do not sell master-data remediation as a course outcome.