The problem to investigate
Site totals can differ for valid operational reasons. The review needs to identify shared infrastructure and local requirements before using location comparisons to flag exceptions.
Common causes to check
- Carrier accounts covering several branches
- Closed sites retained under old addresses
- Shared circuits allocated wholly to one location
What your organization should review
- Map accounts and circuits to a stable site ID
- Separate shared and site-specific services
- Review opening and closure dates against billing periods
Verification and supporting evidence
Keep the location crosswalk, allocation method, and owner confirmations. Document operational differences that explain why apparently similar locations have different service costs.
Illustrative review example
Two branches show very different spend because one hosts the shared voice gateway. The reviewer separates that shared obligation before investigating the remaining difference.
How this fits the AuditRes workflow
Normalize carrier bills into a location-aware review, reconcile site inventory, and attach verified closure or rate evidence to Telecom findings that warrant recovery follow-up.
AuditRes Telecom supports secure carrier billing intake, invoice normalization, reconciliation against contracts and service inventory, human verification, evidence-backed findings, and recovery case management. A flagged difference remains a review candidate until the supporting records establish what happened.
Frequently asked questions
Should every branch be placed on the same plan?
Only if its requirements and contract options support that choice. A consistent review method is more useful than assuming identical service needs.
Does a finding guarantee a credit or refund?
No. A finding records a reviewed discrepancy and its evidence. The carrier response and the documented financial outcome determine whether a case produces a credit, refund, partial adjustment, or no recovery.