# 1. Revenue Leak Screen **Status: MULTIPLE LEAKAGE HYPOTHESES — evidence is sufficient to prioritize reconciliation, but not to quantify loss.** # 2. Leakage Hypothesis Map - **Entitlement drift:** 300-seat commercial state vs. 420 active users. - **Unpriced support:** weekend support may be outside the supplied plan terms. - **Usage billing dispute:** two invoices require event-to-lineage reconciliation. # 3. Evidence Available - plan notes - entitlement snapshots - sample invoices # 4. Evidence Missing - effective downgrade date and grace rules - user activation/deactivation timestamps - support exception approvals - usage-event definitions and invoice lineage # 5. Priority Reconciliation Checks 1. Align contract effective date with entitlement snapshots. 2. Separate licensed seats, enabled users, and billable users. 3. Trace disputed invoice lines to usage definitions and source events. 4. Confirm whether weekend support is an approved exception. # 6. Customer and Control Risks Quantifying loss before these records reconcile could overstate or understate the issue. No billing change should be made from the current evidence. # 7. Specialist Handoff Map - **Repair Subscription Entitlement Drift** if entitlement state remains inconsistent. - **Repair Usage Metering Drift** or **Resolve SaaS Usage Billing Disputes** if usage lineage is the confirmed gap. - **Audit SaaS Support Entitlements** if support delivery is not supported by plan or exception evidence.