Telecom Mediation and Rating Software: Custom Build or Buy
Buy JeraSoft if you are a wholesale voice operator with conventional rating at moderate volume, and buy MATRIXX or Optiva if you need real time online charging for prepaid. Keep Oracle Billing and Revenue Management if you already run it and it works.
On this page
Buy JeraSoft if you are a wholesale voice operator with conventional rating at moderate volume, and buy MATRIXX or Optiva if you need real time online charging for prepaid. Keep Oracle Billing and Revenue Management if you already run it and it works. Build when back dated re rating is routine rather than exceptional, because that requirement shapes the architecture and cannot be bolted on afterwards.
What MediationZone, Oracle BRM, MATRIXX and JeraSoft actually do well
This is one of the few telecom categories where the products are genuinely mature and a custom build is a real competitor rather than an obvious one. Start with what the incumbents already solve.
DigitalRoute MediationZone is the strongest dedicated product in the space and it handles enormous complexity: collection from heterogeneous sources, normalisation, deduplication, enrichment and distribution, configured in its own toolkit. Oracle Communications Billing and Revenue Management is deeply capable across rating, billing and receivables, with decades of telecom accounting correctness inside it. MATRIXX and Optiva are built for real time converged charging over the Diameter interfaces, which is the right answer if you need balance checks and reservations during a session, and considerable overkill if you rate files after the fact. JeraSoft is far more accessible and aimed squarely at wholesale voice and internet telephony, and at moderate complexity it is a sensible answer at a fraction of a build. Hansen and Comarch bring rating inside a broader business support suite, which suits you if you are replacing the suite anyway.
Replacing a functioning billing platform is one of the higher risk projects a telecom operator can undertake, and the trigger for it should be a business change rather than dissatisfaction with a screen. If your rating logic is conventional, your sources are few, and your invoices are correct, buy and put the money into your network. Most readers are in that position.
Where they stop: back dated re rating and the path to raw
The failure mode that defines this category is not an outage. It is quiet incorrectness. Records that arrived and were silently dropped because a file carried an unexpected trailer. Duplicates counted twice because the deduplication window was an hour and the switch retransmitted after ninety minutes. A tariff change applied from the wrong effective date so three weeks of traffic rated at the old price. None of those page anyone, and the ones that undercharge are never reported by the customer.
So the requirement is not throughput. It is that for any number on any invoice you can produce the raw records behind it, the rate applied, why that rate applied, and proof nothing else was dropped.
Two capabilities follow from that and they are where configured products get uncomfortable. The first is back dated reprocessing. A partner rate was loaded incorrectly on the fourth and it is now the nineteenth. You need to re rate that partner between those dates, produce the delta against what was already invoiced, and issue an adjustment, without touching anything else and without losing the record of what was originally billed. That needs raw retained immutably, rating as a pure function of raw plus a versioned rule set, and every rating run identified so re rating produces a new run rather than mutating the old one.
The second is the drill path. A customer's controller says the invoice reads eleven thousand for international termination in March and they expected eight. In a healthy system an account manager reaches the underlying detail in minutes with no structured query language involved. In an unhealthy one it takes a week, ends in a credit because nobody could prove the charge, and your commercial team quietly learns to concede. That behavioural change costs more than the credits.
The arithmetic: cost per million rated records versus a build
Rating platforms are priced per subscriber, per rated event volume, or per named user with a volume tier, and configuration is usually a separate professional services line that recurs every time a tariff construct changes. Restate your contract as one annual number including that services line before comparing.
Now the build. A first release covering collection from your main sources, declarative parsing with suspense handling, persistent deduplication and a rating engine with versioned effective dated tariffs for your primary usage type runs $120,000 to $260,000 in our delivery experience. Amortise the midpoint over five years, add year two support at the rate below, and you carry roughly $53,000 to $65,000 a year.
At 200 million rated records a month that is about $0.023 per thousand records. At 20 million a month it is $0.23 per thousand. Set that against a per event licence: at $0.05 per thousand rated events the crossover sits near 90 to 110 million records a month, and at $0.20 per thousand it falls to roughly 22 to 27 million.
Volume matters less than people expect, because the architectural jump happens at a threshold rather than continuously. Source diversity is the real multiplier. Every new format is a parser, a set of undocumented quirks and a discovery period, so count your distinct sources and multiply. Then add the line nobody quotes: if every tariff change requires a consultant, your commercial agility now runs on somebody else's calendar, and that delay has a revenue number attached that your product manager can estimate.
What a custom build actually costs
A first release covering collection, declarative versioned parsers with suspense handling, a persisted deduplication index and a rating engine with effective dated tariffs for one usage type end to end runs $120,000 to $260,000 across 16 to 24 weeks. Rate one usage type completely rather than three partially.
A full platform adding enrichment against routing and customer data, back dated re rating with adjustment computation, settlement and partner outputs, roaming file handling where relevant, and the traceability interface for commercial users runs $350,000 to $900,000 phased over 10 to 20 months.
Data migration lands at 10 to 25 percent of build cost, and here it is dominated by history rather than configuration. You need enough historical raw records to support disputes and re rating for the period your contracts require, plus the tariff versions in force across that period, which frequently exist only as a table someone edited in place. Reconstructing effective dates for tariffs that were never versioned is the part that overruns.
Year two runs 15 to 20 percent of build cost annually. The drivers are new sources, new tariff constructs your commercial team sells, and the steady discovery that a field documented as mandatory is empty on a slice of records from one node. Budget for that as normal operations rather than as defects.
The four situations where building wins
- Standards and format fit. Your sources will include binary records encoded to the abstract syntax notation used by network elements, fixed width text described in a vendor document from a decade ago, and roaming settlement files following the Transferred Account Procedure with their own rejection process. If you are a communications platform provider, your message and voice application events look nothing like a call detail record and still have to be rated like one. Declarative versioned parsers per source with a schema contract validated on every file are the only design that survives that.
- Scale economics. Past roughly 25 to 100 million rated records a month depending on your per event rate, the arithmetic above turns in favour of ownership.
- A workflow that is your advantage. If your rating logic is a commercial differentiator rather than a standard construct, which is common at communications platform providers and wholesale operators with unusual settlement arrangements, the tariff model is your product. Committed volume tiers with true up, grandfathered plans that must never be touched, contracted floors and partner specific rounding are not features you should be waiting on a release for.
- Integration sprawl across three or more systems. Count them: the softswitch and session border controllers, packet gateways, application platforms, partner feeds, the routing data used for jurisdiction determination, and the invoicing system downstream. Once three or more must agree on one usage event, the pipeline is the product.
How to decide in a week
Take one month of real production traffic and rate it in parallel against your current system. Then investigate every difference, not the aggregate. This is the single most useful exercise in the category and it defines scope better than any requirements workshop, because it surfaces undocumented source behaviour, tariff constructs nobody remembered, and records your current pipeline has been silently dropping.
Three counts come out of it. Records in, records rated, and records suspended with a reason. If the first two do not reconcile and nobody can explain the gap, you have a completeness problem rather than a rating problem, and that is a different project with a faster payback.
Run the second test on people. Give an account manager one invoice line and ask them to reach the underlying rated records without asking an engineer. Time it. If the answer is that they cannot, the drill path does not exist in any way that matters to your business, and it should be a first release requirement rather than a later enhancement.
Third, ask your incumbent supplier one question in writing: what it takes to re rate three weeks of one partner's traffic after a rate correction, and whether the original rated output is preserved. If the proposal involves updating rated records in place, you now know why your finance team does not trust adjustments.
If those tests point to building, take a paid discovery phase rather than a proposal. Digital Heroes runs discovery to a signed product requirements document covering the source inventory, the tariff model, the re rating design and acceptance criteria. The specification is yours to take to any other firm on your shortlist. We are the wrong partner if you need real time online charging with credit control, because that is a different system with genuine safety requirements and should not be scoped as an extension of file based mediation. We are an India LLP with US LLC and UK LTD entities so intellectual property assigns under your own law, with more than fifty specialists, over 2,000 projects delivered, a named team you meet before signing, and a public record on Clutch, Trustpilot, Fiverr Vetted Pro and D-U-N-S.
Book a 30-minute call with Digital Heroes and get a written plan and a fixed quote within 48 hours.
The evidence behind this guide
Independent findings on why this investment pays off. Every link goes to the primary source.
- 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) →
- Deloitte reports that modern ERP implementations aim to deliver reduced manual effort, greater transparency, a single source of truth, and increased productivity, but many organizations do not capture the full expected benefits (a significantly lower ROI) without disciplined strategy, change management, and data readiness. Source: Deloitte (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 October 2025 survey of 530 small-business employers (conducted by TechnoMetrica, October 3-9, 2025), 88% reported using AI tools and 73% said those tools had been important to their competitiveness and growth over the past year, with 60% citing efficiency and productivity as the primary motivation for adoption (42% cited improving customer service). Source: Small Business & Entrepreneurship Council (SBE Council) (2025) →
Frequently asked questions
What is the difference between mediation, rating and charging?
Mediation collects, normalises, deduplicates and enriches usage records from network and application sources. Rating applies tariffs to those records to produce monetary amounts. Charging usually implies real time control, meaning checking and reserving balance before or during a session, which is a fundamentally different system with genuine safety requirements. Do not scope real time charging as an extension of a file based mediation build.
How do you re rate back dated traffic after a rate is loaded incorrectly?
Retain raw records immutably, treat rating as a pure function of raw records plus a versioned rule set, and make every rating run identifiable so any output traces to the run and rule version that produced it. Re rating then produces a new run rather than mutating the old one, and the adjustment is the difference between runs, which finance can reconcile without taking anyone's word for it.
Why does deduplication go wrong in telecom mediation?
Two reasons. Hashing the whole record breaks on high volume short duration routes where two genuinely distinct calls carry identical field values, so you need the source's own unique identifier plus a composite key where none exists. The second is retention: an index kept for a convenient window rather than for how long your worst source might take to retransmit will miss late duplicates, which is how systems double bill and cannot explain why.
How long does a mediation and rating build take?
Sixteen to twenty four weeks for a first release covering collection, parsing with suspense, deduplication and rating for one usage type end to end. The full platform with enrichment, re rating, settlement outputs and the commercial drill path runs ten to twenty months. Rating one usage type completely and invoicing from it beats rating three partially, and it gives you a reconciled baseline before scope grows.
Who owns the code and the tariff configuration if an agency builds this?
You should own the repository, the cloud infrastructure accounts and the unrestricted right to hire another firm, written into the contract before kickoff. At Digital Heroes the client owns the code from the first commit. The tariff model matters as much as the code, because it encodes every commercial construct your business has sold, and losing access to it means reconstructing your own pricing history from invoices.
What happens if a source sends a malformed file at two in the morning?
The correct behaviour is that the offending records go to suspense with the specific violation attached, an alert fires naming the source, and the pipeline keeps processing everything else. A partial failure must never become a total failure, and it must never silently become a success with missing data. If a prospective developer answers that the job fails and gets rerun, you will spend every month end doing manual recovery.
Can we keep our billing system and build only mediation?
Yes, and it is a common and sensible split. Mediation collects, validates, deduplicates and enriches, then hands rated or unrated records to the billing platform you already run. It removes the source diversity problem, which is usually where the pain actually is, without touching invoicing, receivables or the general ledger. Scope the interface contract carefully, because that boundary is where a phased approach either works or does not.
How much history do we need to keep and why?
Long enough to support disputes and re rating for whatever period your contracts and local record keeping obligations require, which is normally longer than your operations team assumes. Storage of raw records is the cheap part. The expensive part is retaining the tariff versions in force across that period, because you cannot reproduce a historical invoice without the rules that produced it and most systems overwrite rates in place.
Is JeraSoft enough for a wholesale voice operator?
For conventional wholesale rating at moderate volume, often yes, and it will cost a fraction of a build. It gets constrained when enrichment is complex, when back dated reprocessing is routine rather than exceptional, or when your commercial team has sold constructs that do not map to its model. The clearest tell is a spreadsheet maintained alongside the system to explain what the invoices should have said.
How do we know whether records are being silently dropped today?
Count three numbers per source per day: records received, records rated, and records suspended with a reason. If the first does not equal the sum of the other two, the difference is being lost somewhere and nobody is watching. Add sequence number continuity where the source provides it. This check is unglamorous plumbing and it finds more money than any analytics layer built on top of the same data.
What happens to my software if the agency shuts down or we stop working together?
Nothing dramatic, if the engagement was set up correctly: the code sits in your repository, hosting runs on your cloud account, and a handover document explains how to deploy and operate the system. Any competent replacement team can then take over in days rather than months. If the agency controls the repo, the servers, or the domain, fix that now, because renegotiating access during a dispute is the most expensive place to discover the problem.
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.
How much should a small business budget for its first custom app or website?
For a focused first build, most small businesses land between $8,000 and $60,000: roughly $8,000 to $45,000 for a custom website and $25,000 to $60,000 for an internal tool or simple web app, based on Digital Heroes delivery across 2,000+ projects. Customer-facing products with payments, logins, or a mobile app start around $40,000. Quotes far below these bands usually mean a template with your logo on it, not software shaped around your workflow.
What can custom accounting software do that QuickBooks, Xero, and FreshBooks can't?
It encodes your actual business rules: progress billing tied to project milestones, revenue recognition for your specific contract types, landed cost tracking, or approval chains that match your org chart. Off-the-shelf tools handle generic bookkeeping well but force every business into the same chart of accounts and workflow. FreshBooks, for example, is built around freelancer-style invoicing, so inventory or multi-entity accounting means leaving the product entirely.
Can custom accounting software connect to my bank, payment processor, and payroll provider?
Yes, and it should be treated as standard scope rather than an add-on. Bank feeds typically come through aggregators like Plaid, payments through Stripe or your existing processor's API, and payroll providers such as Gusto and ADP publish APIs for pulling journal entries. The real constraint is smaller regional banks without feed coverage, which is worth verifying during scoping instead of discovering after launch.
How much does custom accounting software cost for a small business?
Most small business accounting builds land between $25,000 and $75,000 for a working first version, while a full double-entry platform with invoicing, payroll, and reporting runs $100,000 to $250,000. Across 2,000+ projects at Digital Heroes, the biggest cost driver is how many external systems the software must connect to, not the accounting logic itself. A tool that automates a single painful workflow, like reconciliation or job costing, can come in under $20,000.
Can we migrate years of data out of our current system into new custom software?
Almost always yes, through CSV exports or the vendor's API, and migration should be scoped as its own workstream with field mapping, a dry run, and a planned cutover window rather than an afterthought. The real time sink is rarely moving the data; it is cleaning it, since years of duplicates, free-text fields, and inconsistent formats surface all at once. Pull a full export from your current vendor before committing to anything new, because some SaaS plans restrict exports on lower tiers.
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.
What happens to my accounting software if the agency shuts down?
If you own the repository, the hosting accounts, and the documentation, another team can take over within weeks, usually before a missed closing cycle does real damage; if the agency owns any of those, you have a hostage situation. Before signing, confirm the code sits in your GitHub or GitLab organization, hosting bills to your card, and a written deployment runbook exists. A competent agency agrees to all three without friction, and hesitation is itself the answer.
How do I vet a software development agency before signing a contract?
Ask to speak with two past clients whose projects resemble yours in size and industry, and ask exactly who will write your code, since some agencies sell senior faces and deliver junior or subcontracted hands. Demand a written specification with acceptance criteria before any fixed price, and check that their portfolio links to products that are actually live. An instant quote given without questions about your workflows is the clearest warning sign there is.
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
Published · Last updated .