Enterprise AI Administration

Governance & Lineage — Revenue leakage

How this KPI is sourced, calculated, governed, predicted and acted on — one traceable chain.

Current value

USD 0.8M

No stored target

Mission area

Fraud & Revenue Assurance

Decision journey

Fraud & Revenue Assurance

Source systems

Revenue Assurance · Fraud Monitoring

Lineage path

From source system to value realization — counts of governed records linked to this KPI

Governed calculation for this KPI

No governed formula recorded.

Source system, object and field feeding this KPI, and how each is transformed

Role	Source	Transformation	Target	Grain / refresh
Leakage cases	Revenue Assurance `ra_leakage_cases.estimated_amount`	Sum of open and confirmed case amounts per period	`fraud_assurance_mart.leakage_amount`	Fraud-case · Daily
Fraud loss estimates	Fraud Monitoring `fraud_alert.loss_estimate`	Confirm and classify fraud type	`fraud_cases.fraud_loss_zar`	Fraud-case · Daily
Fraud risk scores	Fraud Monitoring `fraud_cases.risk_score`	Latest risk score per subscriber	`fraud_assurance_mart.fraud_anomaly_score`	Fraud-case · Daily

Thresholds that escalate this KPI and the alert each raises

Rule	Severity	Alert raised
Revenue Leakage Escalation Leakage rate 1.2% of billable revenue	HIGH	SIM-box activity detected in 2 border regions

Predictive and simulation models used for this KPI

AI model	Validation	Simulation model
Revenue Leakage Detection Model Isolation Forest + Business Rules · v1.4	VALIDATION REQUIRED	Revenue Leakage Impact Model

Model features derived from the source fields above

Stored scenarios for the Fraud & Revenue Assurance journey

Governed actions and value records for the same journey