Most telco margin conversations focus on the retail side — churn, upsell, the cost of a truck roll. Those numbers are visible, the metrics are well-instrumented, and the executive dashboards have been chasing them for years. The wholesale side of the business is a different story. Carrier-to-carrier settlement, interconnect billing, partner reconciliation, dispute management — it sits in a quiet corner of the finance org, gets a fraction of the tooling investment, and somehow still accounts for an enormous slice of the P&L.
The numbers aren't subtle once you look. iCONX's analysis of wholesale reconciliation notes that interconnect costs can represent up to 30% of a telco's total business, with charging variances between operators and their wholesale partners typically running 0.5% to 5%. On a base that large, even a half-percent variance translates to tens of millions of dollars sitting in dispute at any given moment — money the operator has either overpaid, can't yet collect, or hasn't reconciled because the spreadsheet ran out of rows.
And the gap is widening, not closing. The same analysis describes the operational reality bluntly: legacy systems can't keep up with the pace at which interconnect agreements are changing, partner formats are mutating, and traffic types are diversifying. Voice, SMS, data, IoT, and increasingly OTT settlement all flow through the same finance team, and most of them are still running on email threads, attached spreadsheets, and a CDR drop folder.
Wholesale settlement is not retail billing — and your retail BSS knows it
The first instinct of every telco CFO is to ask why the existing billing system can't handle this. The answer is structural. Retail billing is one-to-many: one operator, millions of subscribers, predictable rate plans, and reasonably consistent inputs. Wholesale settlement is many-to-many, with each peer carrier sending Call Detail Records in a different format, on a different cadence, with different rounding conventions, different timestamping, and different dispute SLAs.
Equinox's primer on the CDR as telecom's working currency describes how each interconnect partner can effectively define its own data dialect. Some carriers reconcile monthly; others want weekly true-ups; a handful are pushing toward near-real-time settlement. When discrepancies appear, finance teams routinely cross-reference seven or more systems — the switch, the mediation platform, the partner's invoice, the contract repository, the rating engine, the GL, and whatever shared drive the original agreement was filed in — to resolve a single line item.
That correlation work is what eats the team. Days disappear chasing a $4,000 variance because nobody automated the comparison between the partner's CDR file and the operator's own switch records. Working capital sits locked in disputed settlements while the dispute desk drafts another email.
What automated wholesale reconciliation actually looks like
Modernizing this isn't about ripping and replacing the BSS. The work is process orchestration across the systems that already exist. Five workflows have to run in parallel, and each one is a candidate for automation that pays back fast.
1. CDR ingestion and normalization. Partner files arrive in a dozen formats. Some are EDI, some are flat-file CSV, some are vendor-specific binary, and some show up as a PDF attachment because that's what the carrier's finance system exports. The normalization layer needs to read all of them, map them to a canonical model, and flag schema changes before they break downstream rating. Symphona Migrate is built for exactly this kind of multi-source data normalization — its no-code rule-based mapping editor and AI-assisted Mapping generation let a wholesale finance team onboard a new partner format in days rather than the quarters most BSS modifications require.
2. Variance detection. Once records are normalized, the partner's view and the operator's view need to be compared at the line level. Variance over a defined threshold becomes a candidate dispute. This is process automation territory — high-volume, deterministic, perfectly suited to running on a schedule rather than waiting for a finance analyst to notice a number looks off.
3. Dispute case creation and tracking. A flagged variance has to become a tracked case with an assigned owner, an SLA clock, a contractual reference, and an audit trail. Symphona Resolve handles this directly — disputes flow into a managed exception queue, get prioritized by financial impact, and route to the right human or workflow without anyone copying line items into a spreadsheet first. Industry research on wholesale interconnect billing consistently finds that automated validation cuts manual reconciliation effort by 80–90%, with the bulk of the saving coming from this stage.
4. Multi-party resolution workflow. Resolving a dispute usually requires the operator's finance team, the partner's finance team, and sometimes a third-party clearinghouse. The supporting evidence has to be packaged and sent, the response tracked, and the outcome reflected back into the GL. Symphona Flow orchestrates that conversation — generating the evidence package, sending it to the right counterparty, parsing the inbound response, and triggering the credit memo or supplemental invoice when both sides agree.
5. Settlement closure and posting. The final step is updating the GL, releasing the held cash, and feeding the outcome back into the rating engine so the same variance pattern doesn't keep firing. This is the step most operators skip because the manual version is exhausting; once the rest of the workflow is automated, it becomes the easy part.
The standards angle is finally catching up — but standards alone don't ship the workflow
TM Forum's coverage of wholesale standardization describes the industry push toward Open APIs and standardized lead-to-cash interfaces between buyer and seller carriers. The direction is right, and the pilots are real. But standards close the protocol gap, not the operational gap. Even with a TM Forum-compliant interface to every partner, somebody still has to ingest, reconcile, dispute, and resolve. The carriers that win on wholesale margin over the next three years won't be the ones with the cleanest API spec — they'll be the ones who orchestrate the full settlement lifecycle around it.
The math is the part most operators underestimate. If interconnect represents 30% of business and reconciliation variance runs at 1–2% of that, an operator doing $10 billion in revenue is carrying $30–60 million annually in variance that should be either recovered or properly accrued. Pulling even half of that back through automated dispute management is a faster ROI than nearly any retail initiative the same team is being asked to chase.
If you're a telecom operator looking to compress wholesale settlement cycles and recover the margin currently parked in disputes, explore how Symphona works for telecom and media or book a consultation . We can walk through your specific interconnect partner mix and identify where unified reconciliation, dispute, and credit-memo automation closes the gap fastest.
.svg)
.svg)
.avif)
.avif)
.avif)
.avif)
.svg){kind=icon}
.svg){kind=icon}
.svg)
.svg)
.svg)
.svg)
.svg)
