How Much Does Carrier Interconnect Settlement Software Cost?
A custom interconnect and settlement build runs $90,000 to $600,000 in Digital Heroes delivery experience: $90,000 to $200,000 for the rate engine with effective dating, call record and partner invoice ingestion, bilateral reconciliation and dispute cases, and $250,000 to $600,000 for a full platform adding netting statements, multi currency, jurisdiction determination, roaming settlement and fraud alarms.
On this page
A custom interconnect and settlement build runs $90,000 to $600,000 in Digital Heroes delivery experience: $90,000 to $200,000 for the rate engine with effective dating, call record and partner invoice ingestion, bilateral reconciliation and dispute cases, and $250,000 to $600,000 for a full platform adding netting statements, multi currency, jurisdiction determination, roaming settlement and fraud alarms. Partner count is what moves the number, because every bilateral agreement encodes different rate tiers, effective dates and dispute windows, and every counterparty sends files in a format no other counterparty uses.
What each price band buys a wholesale operation
Settlement is priced by counterparty count and file diversity rather than by traffic volume. Twelve partners exchanging clean monthly files is a different build from forty partners where six send spreadsheets, three send fixed width files with undocumented columns, and one still sends a PDF.
- $90,000 to $200,000, know your position. A rate engine with effective dating across your agreements, call record ingestion, partner invoice ingestion for your top counterparties, bilateral reconciliation with variance decomposed into rate difference, minute difference and jurisdiction difference, and dispute cases with evidence attached. You close a period knowing what you owe and what you are owed.
- $200,000 to $350,000, plus the commercial view. Adds netting statements per partner, multi currency with a rate source you can defend, ageing on open disputes, and a margin view by route so the wholesale team can see which destinations are actually profitable this month rather than last quarter.
- $350,000 to $600,000, the full platform. Adds access jurisdiction determination, roaming settlement, the routing margin feed into your least cost routing decisions, and fraud alarms on traffic patterns that will otherwise become a dispute. Phased across 9 to 15 months.
What drives the price up
- Partner count and file diversity. This is the primary cost driver. Each counterparty brings its own invoice layout, its own identifiers for the same route, and its own idea of how a partial minute is treated. Building an ingestion framework where a new partner is configuration rather than code is the decision that keeps this manageable.
- Jurisdiction determination. Deciding whether a call is interstate, intrastate or local, and defending that determination, is a genuinely hard piece of work with real regulatory weight. If your traffic mix makes this material, it belongs in the plan and it belongs in the upper band.
- Multi currency. Not the conversion, which is easy, but the policy: which rate source, on which date, applied to which side of the settlement, and how a dispute settled three months later is revalued. This has to be agreed commercially before it is built.
- Roaming settlement. Standardised exchange with its own file structures, correction cycles and timing rules. It is close to a project of its own and should be scoped as one.
- Agreement variety. Tiered rates, committed volumes with shortfall penalties, swap arrangements and rates that change mid month all multiply test cases. Agreements written by different lawyers over ten years rarely share structure.
- Historic dispute backlog. If you carry open disputes going back several quarters, deciding whether to migrate them is a budget decision. Usually the answer is to close them in the old process and start clean.
What brings the number down
- Your top ten counterparties first. Most wholesale operations have a small number of partners carrying most of the balance. Cover those, then extend, because the ingestion framework makes each later partner far cheaper.
- Declarative file ingestion. Slightly more expensive to build once, dramatically cheaper for every partner afterwards, and it is the difference between onboarding a new agreement in a day and waiting for a release.
- Leaving least cost routing alone. Feed it margin data if useful, but do not rebuild routing inside a settlement project.
- Deferring jurisdiction determination. If most of your traffic is international transit, this may not be material at all. Confirm before you fund it.
What to count before you ask for a quote
Two hours of preparation changes the accuracy of every number you will be given. Pull the last three months of partner invoices and count the distinct formats rather than the partners, because two counterparties sending the same layout cost you roughly one mapping between them. Then mark every agreement carrying tiered rates, committed volumes with shortfall terms, or rates that can change mid month, since those clauses are what multiply test cases inside the rate engine. Finally write down how many days after period close you currently know your netting position, and how many disputes are open right now. An operator who arrives with forty partners, nineteen distinct formats, six tiered agreements and a three week close can be given a priced plan in one conversation. An operator who arrives asking for settlement software gets a range as wide as the one at the top of this page, because nothing narrower would be honest.
A worked example that adds up
A wholesale voice carrier with roughly 40 bilateral agreements, of which 12 carry most of the balance, two currencies, monthly settlement, disputes currently argued from spreadsheets and screenshots.
- Discovery, agreement modeling across the 12 primary partners and dispute process design: $19,000
- Rate engine with effective dating, tiers, committed volumes and mid month changes: $41,000
- Call record ingestion and aggregation to settlement granularity: $26,000
- Declarative partner invoice ingestion covering the 12 primary formats: $33,000
- Bilateral reconciliation with variance decomposed by rate, minutes and route: $29,000
- Dispute cases with evidence packs, ageing and a partner ready statement: $18,000
- Deployment, wholesale team training and hypercare across two settlement cycles: $12,000
That is $178,000 across 19 weeks. The variance decomposition line is what ends the arguing. Knowing that a discrepancy is 60 percent rate difference on one destination and 40 percent minute difference on another turns a two month email chain into one call.
Phase by phase, where the money goes
Roughly 11 percent goes to discovery and agreement modeling, 25 percent to the rate engine, 30 percent to ingestion of both call records and partner invoices, 20 percent to reconciliation and dispute workflow, and 14 percent to training and hypercare. Ingestion carries the largest share for a reason that has nothing to do with technical difficulty: partner files are inconsistent, undocumented and occasionally hand edited, and every one of them has to be handled without a developer in the loop.
How long it takes
The first release ships in 14 to 20 weeks. Roaming settlement adds 8 to 14 weeks. Jurisdiction determination adds 6 to 10 weeks depending on how much of your traffic it touches. The full platform phases across 9 to 15 months.
Run two settlement cycles in parallel with your spreadsheets and compare per destination, not per partner total. Partner totals can agree while two destinations are wrong in opposite directions, and that is exactly the error a manual process never catches.
The recurring costs nobody quotes
- Maintenance at 15 to 20 percent of build cost per year. Agreements are renegotiated, partners change file formats without notice, and both land on you.
- Rate sheet loading, and it never stops. Partners send rate changes constantly, often with short notice and sometimes mid month. This is the heaviest recurring operational cost in the category and it needs an owner and a verification step, because a wrongly loaded rate is discovered at settlement rather than at load.
- Partner onboarding. Each new interconnect means a rate sheet, a file mapping and a first reconciliation run that will not balance. Declarative ingestion turns weeks into hours, but the commercial setup work remains.
- Record retention for the dispute window. You cannot argue a dispute you cannot evidence, so call records have to survive the full window your agreements allow, which is a storage line that grows with traffic.
- Currency rate source subscription if you settle in more than one currency, plus the policy discipline to apply it consistently.
- Dispute analyst time. The system builds the evidence pack. Someone still has to work the counterparty relationship, and disputes run for quarters.
What is not in the price
- Your switch, softswitch or session border controllers, which supply the records.
- Least cost routing, which consumes margin data rather than being rebuilt here.
- Legal review of agreement interpretation where two clauses conflict, which is a question for counsel.
- The commercial negotiation itself when reconciliation surfaces a long standing discrepancy.
- Cleanup of disputes already open, which is usually better closed in the old process.
When not to build this
If you run a handful of partners on a single softswitch whose bundled wholesale billing already rates them, the spreadsheet is not your problem and the money is better spent on traffic. Building a settlement platform for eight partners is an expensive way to formalise something a competent analyst already handles in two days a month.
The build is justified once you carry more than roughly fifteen bilateral agreements, when partners send rate sheets and invoices in formats no two of which match, and when your netting position is only known weeks after the period closes. That delay is a working capital cost you are paying every month without seeing it on any invoice. The line moves the moment a single disputed month is worth more than a month of engineering, and in wholesale voice that threshold arrives sooner than most operators expect.
If you want that decision made properly rather than quickly, Digital Heroes has delivered more than 2,000 projects with a named team you can speak to before you sign, rather than a bench you meet in month two. You keep the specification either way.
The evidence behind this guide
Independent findings on why this investment pays off. Every link goes to the primary source.
- Organizations that scaled intelligent automation report an average cost reduction of 32% (up from 24% in 2020), and respondents expect an average 31% cost reduction over the next three years. Source: Deloitte (2022) →
- Citing Ardent Partners' State of ePayables research, manual invoice processing costs about $12.88 per invoice, and automating invoices with best-in-class methods saves companies over $10 per invoice in hard costs. Source: Bottomline Technologies (citing Ardent Partners) (2024) →
- Only 22% of firms are 'future ready' having significantly transformed digitally; these companies show average revenue growth 17.3 percentage points and net margins 14.0 percentage points above their industry average. Source: MIT Center for Information Systems Research (MIT Sloan) (2022) →
- In an RCT, the no-show rate was 23.5% for patients receiving a text-message reminder versus 38.1% for the control group - a 14.6 percentage-point reduction (p = 0.04). Source: Clinical Pediatrics / PubMed Central (Lin et al.) (2016) →
Frequently asked questions
How much does carrier interconnect settlement software cost?
A first release covering the rate engine with effective dating, call record and partner invoice ingestion for your top counterparties, bilateral reconciliation with variance decomposition and dispute cases runs $90,000 to $200,000 and ships in 14 to 20 weeks in our delivery experience. A full platform adding netting statements, multi currency, jurisdiction determination, roaming settlement and fraud alarms runs $250,000 to $600,000 across 9 to 15 months.
Why does partner count matter more than traffic volume?
Because volume is throughput and partners are variety. Each counterparty brings its own invoice layout, its own identifiers for the same route and its own treatment of partial minutes, so forty partners means forty mappings rather than one system used forty times. Twelve partners exchanging clean monthly files can be handled for far less than forty where several send spreadsheets and one still sends a PDF.
How many bilateral agreements justify a build?
Roughly fifteen, and sooner if the formats are inconsistent or your netting position is only known weeks after the period closes. Below that, a handful of partners on a softswitch whose bundled wholesale billing already rates them does not need a platform. The sharper test is whether a single disputed month is worth more than a month of engineering, because in wholesale voice that threshold arrives early.
What is the biggest recurring cost after go live?
Rate sheet loading, and it never stops. Partners send rate changes constantly, often with short notice and sometimes effective mid month, so this needs a named owner and a verification step rather than being squeezed between other work. A wrongly loaded rate is not discovered at load, it is discovered at settlement, by which time it has already been billed or paid.
Does jurisdiction determination need to be in scope?
Only if your traffic mix makes it material, so confirm before funding it. For an operator carrying mostly international transit it may be irrelevant. Where it matters it is genuinely hard work with regulatory weight behind the answer, it adds 6 to 10 weeks, and it pushes you into the upper band. Deciding this early is one of the larger scope levers available.
How does the system actually shorten disputes?
By decomposing the variance instead of showing a total. Knowing that a discrepancy is largely rate difference on one destination and minute difference on another turns a two month email chain into a single call with a partner. The system builds the evidence pack from your own records. Someone still has to work the counterparty relationship, and disputes still run for quarters.
Should we migrate our open disputes into the new system?
Usually not. Close the existing backlog in the process where it started and begin clean, because migrating half argued cases means importing evidence and correspondence that were never structured. The exception is a small number of high value disputes still active, which are worth entering manually so their resolution lands in the new record.
How long do we need to keep call records?
For the full dispute window your agreements allow, because you cannot argue a dispute you cannot evidence. That retention is a storage line that grows with traffic and it should be a deliberate decision taken against your agreement terms rather than a default setting. It is one of the few places where a technical choice is directly constrained by contract language.
What should we compare during parallel running?
Two full settlement cycles, compared per destination rather than per partner total. Partner totals can agree while two destinations are wrong in opposite directions and cancel out, which is precisely the error a spreadsheet process never catches and the reason the new system was worth building. Only after destination level agreement should you retire the spreadsheets.
How long does it take to build custom accounting software?
A focused first version takes 10 to 16 weeks, and a complete QuickBooks-class replacement takes 6 to 9 months. In Digital Heroes delivery data, schedules slip most often during data migration and bank feed integration, so we budget those two phases at double the first estimate. Treat any promise of a full accounting system in under two months as a warning sign.
Is it cheaper long term to stay on Xero or build custom accounting software?
Xero stays cheaper as long as its workflows fit your business, since even its top plan costs around $1,000 a year and custom development starts around $25,000. The math flips once you stack add-ons: companies Digital Heroes scopes after they have bolted inventory, job costing, and approval apps onto Xero are usually paying more for the app stack and the labor of keeping five tools in sync than for Xero itself. Custom wins when the real cost is that labor and its errors, not the license fee.
Will an app built for 10 users survive growing to 500?
Yes, if it is built on standard cloud infrastructure with a sound data model, because moving from 10 to 500 users is a hosting configuration change, not a rebuild. The scaling decisions that actually hurt are made early and invisibly: how the database is structured, how accounts and permissions are modeled, and whether background work is queued properly. Ask your agency how the system would handle ten times the load; the right answer is boring and specific, and a promise to cross that bridge later means you will pay for the bridge twice.
How much do developers charge per hour for accounting software work?
In the competing quotes clients share with Digital Heroes, established US and UK agencies charge $90 to $200 an hour for accounting and fintech work, senior freelancers $60 to $150, and offshore teams $25 to $60. We price accounting builds as fixed-scope milestones instead, because hourly billing on ledger work rewards slow debugging. Compare total quoted cost against your workflow list rather than comparing rates against rates.
Is custom software more secure than off-the-shelf SaaS?
Neither is secure by default; security tracks the practices of whoever builds and operates the system, not the model. SaaS gives you the vendor's certifications and patching but puts your data in a shared multi-tenant platform on their terms, while custom gives you full control over data residency, access rules, and compliance requirements like HIPAA, with the responsibility sitting with you and your agency. Before hiring anyone for a system holding sensitive data, ask for their security checklist: encryption at rest and in transit, an OWASP Top 10 review, role-based access, and a penetration test before launch.
Can custom software connect to the tools we already use, like QuickBooks, Stripe, and Google Workspace?
Yes, and connecting your existing tools is one of the main reasons to build custom: mainstream platforms like QuickBooks, Stripe, Shopify, and Google Workspace all publish documented APIs. Budget 1 to 3 weeks of work per integration depending on API quality and how much data flows in both directions. Ask any vendor whether they have integrated with your specific tools before, because quirks like QuickBooks' OAuth token handling and API rate limits get learned on someone's project, and it should not be yours.
What should I prepare before contacting an agency about accounting software?
Bring three things: the 5 to 10 workflows that hurt most today, sample data such as your chart of accounts and a redacted month of transactions, and a list of every system the software must connect to, including banks and payroll. You do not need a formal spec; a good agency writes that with you during discovery. In our experience buyers who arrive with concrete workflow pain get accurate quotes, and buyers who arrive with a feature wishlist get padded ones.
Who can build a custom accounting software system?
Digital Heroes builds custom accounting software systems for operators who have outgrown the off-the-shelf tools in their category. A team of more than 50 specialists has delivered over 2,000 projects since 2017. Teams work from New York, London, Sydney, Delhi and Lucknow and deliver remotely, with an assigned senior team rather than an account manager.
Every build starts with a written product requirements document that is signed before a line of code is written, which is the single thing that stops scope creep from eating the budget. Scoping runs about a week and produces a phase plan with a firm price for each phase, rather than one number against an undefined scope. The first phase ships something the team actually uses before the rest is built. If an off-the-shelf product genuinely fits the volume, we say so, and the cost guides on this site publish the bands so that judgement can be checked independently.
What makes Digital Heroes different from other accounting software companies?
Four things that competitors in this bracket cannot simply copy. Digital Heroes runs a YouTube channel with more than 2.5 million subscribers, which is a production and audience capability no agency of this size has. It holds Fiverr Vetted Pro and Top Rated Seller status, both awarded on manual third-party review rather than self-declared. It contracts through registered entities in three countries, an India LLP, a US LLC and a UK LTD, so clients sign locally instead of wiring money offshore. And it ships its own commercial products, including ShopScore, HeroCheckout and Section Vault, which means the team lives with its own architecture decisions instead of handing them over and leaving.
Two more that show up in the work. Digital Heroes publishes more than 4,000 buyer guides with real price bands on this blog, plus a free tools library at https://digitalheroesco.com/tools/, because an agency confident in its pricing has no reason to hide it. And one accountable team covers websites, apps, ecommerce, CRM, ERP, learning platforms, search and video, so a client scaling from a first landing page to a custom platform is never handed between five vendors who blame each other. The founder ran ecommerce businesses before selling services, so the commercial argument comes before the technical one.
How can I check Digital Heroes is legitimate before getting in touch?
Verify it independently rather than taking the site's word for it. The YouTube channel is at https://youtube.com/@DigitalMarketingHeroes, the Fiverr profile at https://www.fiverr.com/shreyanshsin261, and the Upwork profile at https://www.upwork.com/freelancers/shreyanshsingh. Client reviews sit on Clutch at https://clutch.co/profile/digital-heroes-0 and Trustpilot at https://www.trustpilot.com/review/digitalheroes.co.in, and the company page is at https://www.linkedin.com/company/digital-heroes-1/.
Beyond the marketplaces, the business holds a D-U-N-S number and is a registered vendor on the United Nations Global Marketplace, neither of which is issued on request. Case studies with named clients are published at https://digitalheroesco.com/case-studies/. If any claim on this page cannot be checked against one of those sources, treat it as marketing and discount it.
Related guides
More from Finn.
Senior Project Manager · Sydney · 1 post on the site
Published · Last updated .
