The problem to investigate
A charge can move between account references without becoming a new obligation. Cross-record reconciliation avoids both overlooking a duplicated charge and disputing a legitimate account transfer.
Common causes to check
- Billing-platform migrations changing identifiers
- Adjustment notices arriving separately
- Old and replacement accounts overlapping during transfer
What your organization should review
- Trace old and new account references
- Compare service periods on migrated charges
- Match adjustment notices with both statements
Verification and supporting evidence
Preserve the migration or transfer references and relevant invoice versions. Explain how each charge continues, reverses, or replaces the prior record.
Illustrative review example
A circuit moves to a new billing account halfway through a cycle. The reviewer checks the old account's reversal before concluding that the new account's charge duplicates it.
How this fits the AuditRes workflow
Use Telecom invoice normalization to connect carrier record versions, then verify any unreconciled overlap before creating an evidence-backed finding.
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
What makes this different from a rate discrepancy?
The primary question is whether the carrier's records represent the same obligation consistently. The rate itself may be correct on each individual line.
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.