TEOCO Alternatives for Carriers: Settlement and Cost Management, Bought or Built

Why teams start looking for a TEOCO alternative

Wholesale and cost teams tend to arrive here through frustration with the last mile of the process rather than the calculation itself. The system rates the traffic, produces the settlement position, and then a human opens a spreadsheet anyway, because the partner sent a rate sheet in an unexpected format, or a dispute needs a workpaper the platform cannot produce, or finance wants margin by route by month in a shape the standard reports do not offer. When the tool ends at the point where the actual negotiating happens, its value looks smaller than its price.

The second driver is estate change. Voice minutes shrink, messaging shifts to application to person traffic with different economics, data and roaming dominate, and network cost structures move to cloud and to different transport arrangements. A platform bought for a traffic mix that no longer exists carries modules configured for yesterday, and the cost of reconfiguring it invites the question of whether to reconfigure something else instead.

The third is ownership of the numbers. Carriers now run data platforms for their own reasons, and usage records, network cost data and billing extracts are frequently already there. Once your data is centralised, a separate system holding a copy of the same records and computing on it privately starts to feel like a duplicate rather than a specialism.

What TEOCO genuinely does well

The company grew up in telecom cost management and invoice reconciliation, which is unglamorous work with an immediate financial return: comparing what a supplier or partner invoiced against what your own records say the traffic and circuits should have cost, and disputing the difference. Done well, this pays for itself, and it requires a deep, tedious understanding of how carrier invoices and usage records are actually structured. That knowledge is the asset.

Interconnect billing and settlement is the second area, and the difficulty is not the rating engine. It is holding thousands of rate elements, effective dates, destination breakouts, minimum commitments and negotiated exceptions in a state where every party can agree on the answer. Add international currency, withholding tax and regulated termination rates and you have a maintenance problem that a specialist vendor amortises across many customers. TEOCO also brings network planning and analytics capability alongside, which is a genuine adjacency for a wholesale team that wants cost and network performance in the same conversation.

Where it actually strains

• Rate sheet ingestion stays partly manual whatever you buy. Partners send commercial terms in whatever format they use, and turning those into structured rate data with correct effective dates is a human process at the edges. No platform in this category has eliminated it, and buyers should expect that rather than be surprised by it.
• Reporting rigidity at the analytical edge. Standard settlement and cost reports are solid. Margin by route by partner by month against a forecast, joined to network cost, is usually an export.
• Configuration is specialist. Modelling agreements and cost structures inside the platform is skilled work, often delivered as professional services, which puts your change velocity on somebody else's calendar.
• Deployment weight. Systems in this class are frequently installed or managed rather than lightly consumed, which brings upgrade cycles, environments and an operational footprint that a small wholesale team feels disproportionately.
• Data model gravity. Everything is expressed in the platform's structures, so getting agreements, rates and historic settlements out in a form another system can use is a project and defines your real switching cost.
• Licence economics tied to volume. Pricing generally scales with traffic or estate size, which is uncomfortable in a business where voice volumes decline while the administrative complexity of the agreements does not.

Your realistic options

• Stay and re scope. Cut modules that served a traffic mix you no longer have, and push the vendor on the two things that matter: dispute workpapers and analytical export. Both are reasonable asks at renewal.
• Switch specialists. Subex, Amdocs and Comarch all address interconnect and wholesale settlement, and Mobileum sits nearby on the assurance and roaming side. A swap resets commercials but you re model every agreement, so treat it as a reimplementation.
• Keep settlement, build the analysis. Leave rating and settlement where they are, export everything nightly, and build margin, route profitability, dispute tracking and forecasting on your own data platform. This is the cheapest meaningful improvement available to most wholesale teams.
• Build the whole thing, for a bounded estate. If your agreement count is modest and your traffic types are few, settlement is deterministic arithmetic over records you already own.

When a custom build pays back

Interconnect settlement is unusual among telecom systems because the logic is knowable and stable. A rate applies to a destination for a period, traffic is counted in defined units, tiers and commitments adjust the result, taxes and currency are applied, and a statement is produced. There is no probabilistic model and no real time constraint. What makes it hard at scale is volume and change: thousands of rate elements moving constantly. What makes it tractable at smaller scale is that same determinism.

So the honest test is arithmetic on your own estate. If you manage a few dozen agreements whose rates change occasionally, a purpose built system that ingests your usage records, applies your agreements, produces statements, tracks disputes and feeds finance is a contained build. It will fit your traffic mix exactly, including the application to person messaging and data arrangements that older platforms model awkwardly, and it puts settlement output in the same place as the rest of your numbers.

The dispute layer is where a build most reliably pays for itself, and it is chronically underserved. Partner claims arrive, someone assembles evidence, the argument runs for months, and the workpapers live in email. A system that captures the claim, generates the reconciliation evidence automatically, tracks the position and ages the exposure recovers real money by making disputes fast to answer rather than by rating anything differently.

Do not build when the agreement estate itself is the workload. Hundreds of bilateral relationships, international rate decks changing monthly, hubbing arrangements and regulated rate transitions add up to a maintenance function, and a vendor spreads that cost across every carrier it serves. In that situation your build would be a full time team pretending to be a project.

Migration reality

Settlement migrations are judged by one question from your partners: does your statement still match theirs? Everything else is secondary.

Agreements come first, and they are rarely fully documented in the system. Contracts, side letters, verbally agreed exceptions and the effective dates that govern each: extract all of it, and expect the archaeology to take longer than the software work. Rate history matters as much as current rates, because disputes reach backwards and you must be able to recompute a period from two years ago exactly as it was computed then.

Run parallel settlement for at least two full cycles across every active partner, comparing statements line by line rather than in total. Offsetting errors across destinations can produce a matching grand total while individual routes are wrong, and your partner will find that before you do. Test the difficult categories deliberately: transit versus termination, mobile termination rate changes mid period, minimum commitment shortfalls, currency conversion, withholding tax and credit notes.

Carry the open items across: unresolved disputes with their evidence, credit notes issued, netting positions and accrual entries that finance depends on. Keep a read only archive of historic settlements for the retention period your regulators and contracts require, and brief your partners before the change so a formatting difference in the first statement does not become a dispute of its own.

Cost bands

Cost management and settlement platforms are quoted rather than published, generally scaled to traffic volume or estate size, with configuration and agreement modelling delivered as professional services and an annual maintenance component. On the custom side, using what Digital Heroes typically delivers as the frame: a settlement and reconciliation build covering usage ingestion, agreement modelling, statement production, dispute workflow and finance reporting runs roughly $80k to $200k over 12 to 20 weeks. A full cost management and settlement platform adding supplier invoice reconciliation, route profitability analytics and forecasting runs roughly $220k to $480k. In either model, budget for the human work of maintaining rate data, because that cost belongs to the estate rather than to the software.

The honest recommendation

Stay if your agreement estate is large, international and constantly moving, because rate maintenance is the real product and a vendor carries it across many customers. Stay too if your usage records are not yet trustworthy, since no settlement system, bought or built, is better than the data beneath it. Build when your estate is bounded, your traffic mix has moved on from what the platform models comfortably, and you want settlement output living beside margin and forecast in your own analytics. And whichever you choose, build the dispute and evidence layer yourself. It is the part that recovers money, the part vendors serve least well, and the part your team will use every week.