How Much Does Submetering and Utility Billing Software Cost?
A custom submetering and utility billing platform runs $60,000 to $380,000, with a focused first release covering meter read ingestion, submeter and allocation billing, prorations, master bill reconciliation and a per unit audit trail landing at $60,000 to $130,000 in 12 to 18 weeks.
On this page
A custom submetering and utility billing platform runs $60,000 to $380,000, with a focused first release covering meter read ingestion, submeter and allocation billing, prorations, master bill reconciliation and a per unit audit trail landing at $60,000 to $130,000 in 12 to 18 weeks. The decision that moves the number most is how many distinct legal jurisdictions you bill in, because permitted allocation methods, fee caps, disclosure requirements and billing windows are set by state statute or municipal ordinance and each regime is configuration plus verification plus its own test cases, so a single state portfolio sits near the bottom of the band and a national one sits at the top.
The bands a utility billing build falls into
Three bands, and unit count matters less than jurisdiction count.
The focused first release, at $60,000 to $130,000 over 12 to 18 weeks, buys the control layer: read ingestion that expects a read for every active meter and raises an aged gap when one does not arrive, submeter and ratio allocation billing, prorations by actual days against the read interval with vacant cost posted rather than absorbed, administrative fee handling, master bill reconciliation as a hard gate on release, and a per unit audit trail where every charge line is derived and reproducible.
The full platform, at $150,000 to $380,000 phased over 7 to 12 months, adds jurisdiction rules as effective dated objects across states and municipalities, a resident portal with dispute workflow, posting into Yardi or RealPage ledgers, utility bill capture so master invoices are read rather than keyed, and client separation and reporting if you operate as a billing service provider.
Below both, outsource. Under roughly 3,000 units in one or two states with conventional submetering, a provider carries the compliance burden as part of the service and doing it yourself costs more than it recovers.
What drives a utility billing build up
Jurisdiction count first. Each distinct regime is a configuration set, a verification exercise with counsel and a body of test cases, and the verification is the part you cannot compress. Confirm the specifics for your states with counsel rather than with a vendor.
Meter hardware diversity. Each submetering vendor's read format is separate work, and more importantly each network fails differently. A radio module that dies silently and a repeater that drops after a power event produce different gaps that the system has to detect in different ways.
Utility bill capture, if you want master invoices read automatically rather than keyed. This is genuinely useful at scale and it is a distinct piece of work per utility format.
Posting into Yardi or RealPage. The read path is straightforward. Writing charges, and particularly writing reversals and rebills cleanly so a recalculated run does not orphan or duplicate a ledger entry, is the harder half.
The service provider model roughly doubles the domain, because client separation, per client fee schedules and client reporting are a second system wearing the same interface.
What keeps the number down
Start with one state and your directly submetered properties. Submetering has a cleaner evidence chain than ratio allocation, so it is the right place to prove the reconciliation control before you add allocation and multi jurisdiction rules.
Key master bills by hand in release one. It is a few minutes per invoice and it removes a per utility parsing effort from the critical path while you are still proving the core.
Post to your property management system manually at first, or by file, and add the write integration once billing runs are reconciling reliably. A duplicated charge in a resident ledger creates exactly the dispute the system exists to prevent.
Build the resident portal in phase two. It deflects a large share of calls, which is real value, but only once the underlying derivations are trustworthy enough to show a resident.
Audit your meter register before the project starts. Confirming which meters are active and resolving units whose meters were replaced without a recorded rollover is your work, not the developer's, and it is the usual reason these projects run long.
A worked example that adds up
An owner operator with 14,000 units across three states, mixed submetered and ratio allocated, keying master bills manually in release one and posting to Yardi by file.
- Domain model: master account, master bill with service period, meter with register and changeout history, read with source and quality, occupancy interval, charge line with derivation: $30,000
- Read ingestion for two meter vendors with gap detection, estimate marking and true up obligations: $24,000
- Submeter and ratio allocation billing with tiered rates applied at master level then distributed: $23,000
- Prorations by actual days with vacant cost computed and posted to the property: $14,000
- Master bill reconciliation as a release gate with approved variance reasons: $17,000
- Per unit audit trail with versioned recalculations and retrievable prior versions: $13,000
- Meter register cleanup support, training, parallel billing cycle: $11,000
That totals $132,000, marginally above the first release band, and the two meter vendors plus the mixed submetered and allocated model are what put it there. One state and submetered properties only takes the same scope to around $88,000. Jurisdiction rules across three states, the resident portal, dispute workflow and Yardi posting move you into the second band.
How the spend phases
Discovery runs three to four weeks and 10 to 15 percent of release one. The deliverable is the domain model drawn out, and you should see master account, master bill with service period, meter with register and changeout history, read with source and quality, occupancy interval, allocation rule with jurisdiction and effective date, and charge line with derivation. If a developer draws units and invoices, your reconciliation control will not exist.
Release one runs 12 to 18 weeks. Sensible milestones are a billing run that will not release until it balances against the master invoice, a mid period meter changeout handled correctly with register rollover, and a full period billed in parallel matching your existing output within an explained variance.
Parallel billing takes at least two full cycles. Utility billing is monthly, so this is the constraint on go live rather than development speed.
Phase two follows two or three clean cycles, when the reconciliation control has proven itself and you know which variances are real.
The ongoing costs nobody quotes
Rule maintenance. Statutes and ordinances change, and someone has to enter the change with an effective date and check which properties it affects. If jurisdiction was built as a first class object this is a small internal job. If it was built into screens with no version history, it is a development request every time and you find out through a demand letter.
Support and continued development at 15 to 25 percent of build cost annually, which on the example is roughly $20,000 to $33,000. Utility billing runs monthly and a defect discovered on billing day needs a response that day.
Meter vendor changes. Read formats and network behaviour shift when hardware is replaced across a property, and each replacement programme is a small integration exercise.
Hosting is modest, typically low hundreds to low thousands per month, but retention is not optional. Historical charge derivations are your legal defence, so plan to keep them for as long as claims can be brought against them.
And someone has to work the reconciliation exception queue every cycle. A variance nobody investigates is the same leakage as before, now with an audit trail confirming it.
Comparing a build against your current renewal
If you outsource, this arithmetic is straightforward and you already have the inputs. Take your provider's per unit per month fee, multiply by units and twelve, and compare against the build amortised with its retainer. On the example above, $132,000 plus a $27,000 annual retainer is roughly $71,000 a year over three years. Put your own fee against 14,000 units and see where it lands.
If you run billing in house on spreadsheets, the comparison is labour plus leakage. Take the coordinator hours per cycle and multiply by cycles and properties. Then take the leakage, which is the part nobody measures: reads that failed silently, estimates never trued up, prorations rounded the wrong way and vacant consumption absorbed rather than allocated. In the utility billing projects we have delivered, unreconciled leakage rather than fraud is the recurring finding, small per unit and material across a portfolio.
Measure it directly. For three master accounts, compare the invoice total against the sum of what you billed plus what you knowingly absorbed. The gap is your annual number once you scale it, and it is usually the figure that funds the project.
Then add the dispute cost. If answering one resident takes forty minutes across three spreadsheets, price that per call at your own rate and multiply by your call volume.
When buying beats building
If you hold under roughly 3,000 units in one or two states with conventional submetering, outsource to Conservice or an equivalent provider. They exist for exactly this, they carry the compliance knowledge as part of the service, and running it yourself will cost more than it recovers.
If your portfolio sits inside one property management platform and you are content inside that ecosystem, Yardi or RealPage utility billing is a reasonable buy and the integration is already done for you. That saves the hardest half of the write path, which is worth real money.
Build when two or more of these are true. You operate across enough states that jurisdiction rules are a compliance surface rather than a setup detail. You are a billing service provider, so the platform is your product rather than an overhead. Your recovery rate, meaning billed against master, has drifted and nobody can explain the gap. A regulatory inquiry or a demand letter arrived and assembling the evidence was painful. Or the outsourced fee across your unit count would fund an internal system in under three years.
If you want that decision made properly rather than quickly, Digital Heroes contracts through India LLP, US LLC and UK LTD entities, so the agreement and the intellectual property assignment sit under law your own advisers already read. 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.
- APQC's Open Standards Benchmarking data on the monthly financial close found median performers take about 6.4 calendar days to close the books, while top performers (top 25%) do it in 4.8 days or fewer and bottom performers (bottom 25%) take 10 or more days. Source: APQC (2018) →
- Independent reporting of Gartner's 2025 survey confirms 59% of finance leaders use AI, up from 37% in 2023, with error and anomaly detection (34%) and accounts payable automation (37%) among the leading use cases. Source: CPA Practice Advisor (reporting Gartner) (2025) →
- Senior executives report the highest average compensation among developer roles (e.g., $225K median in the US), and reported salary bands shifted downward year-over-year ($60-75K vs. $70-85K in 2023), underscoring how compensation varies sharply by role and location. Source: Stack Overflow (2024) →
- The share of tasks performed mainly by humans is projected to fall from 47% to 33% by 2030 as human-machine collaboration expands, with 170 million jobs created and 92 million displaced (a net gain of 78 million). Source: World Economic Forum (2025) →
Frequently asked questions
How much does custom submetering and utility billing software cost?
A focused first release covering read ingestion, submeter and allocation billing, prorations, fees, master bill reconciliation and a per unit audit trail runs $60,000 to $130,000 over 12 to 18 weeks in Digital Heroes delivery experience. A full platform adding multi state rule configuration, a resident portal with disputes and posting into Yardi or RealPage runs $150,000 to $380,000 over 7 to 12 months.
The number of distinct legal jurisdictions is the biggest single cost driver, well ahead of unit count.
What does it cost to run each year?
Budget 15 to 25 percent of build cost annually for support and continued development, roughly $20,000 to $33,000 on the $132,000 example. Utility billing runs monthly and a defect found on billing day needs a same day response, so negotiate that window explicitly.
Add rule maintenance, which is a small internal job if jurisdiction was built as an effective dated object, plus the cost of retaining historical charge derivations for as long as claims can be brought.
Is Conservice cheaper than building our own platform?
Under roughly 3,000 units in one or two states, almost certainly, and outsourcing is the right call because the provider carries the compliance burden as part of the service. Run the comparison directly: per unit per month fee times units times twelve, against the build amortised with its retainer.
The calculation flips when you operate across many states, when your unit count means the fee would fund an internal system in under three years, or when you are a billing service provider yourself and the platform is the product.
How long before we can run production billing on it?
A first release generally ships in 12 to 18 weeks, then plan at least two full parallel billing cycles before cutover. Because billing is monthly, parallel running rather than development speed is what sets your go live date.
The usual schedule risk is meter data rather than engineering. Confirming which meters are active and resolving units whose meters were replaced without a recorded rollover takes real time, and portfolios with a clean register move noticeably faster.
Why does each additional state cost so much?
Because permitted allocation methods, fee caps, disclosure text and billing windows are set by statute or ordinance, and each regime needs configuration, verification with counsel and its own test cases. The verification is a legal exercise on your side, not a development task, which is why it takes calendar time.
Build jurisdiction as a first class object with effective dated rules so a property cannot be configured with a method its market does not permit, and so a rule change lists every affected property rather than being discovered later.
What does posting into Yardi or RealPage add?
Typically $20,000 to $40,000 depending on the platform and how much of the write path you need. Reading leases and occupancy is straightforward. Writing charges, and handling reversals and rebills so a recalculated run does not orphan or duplicate a ledger entry, is the harder half.
Post by file in release one and add the write integration once billing runs reconcile reliably, because a duplicated charge in a resident ledger creates exactly the dispute the system exists to prevent.
How much is the reconciliation control worth building properly?
In the worked example it is $17,000 of a $132,000 release, and it is the line we would defend hardest. For every master bill and period, resident charges plus owner absorbed cost plus vacant cost must equal the invoice, and the run should not release until it balances or an operator records an approved variance reason.
Without it you have an invoicing tool. Measure your own gap first: for three master accounts, compare the invoice total against what you billed plus what you knowingly absorbed.
What does a resident portal with disputes add?
Typically $30,000 to $60,000 depending on whether residents see consumption history alongside the charge and can raise a dispute that routes into a workflow. It belongs in phase two.
The return is call deflection plus a timestamped record that the resident was shown the disclosure, which matters in a dispute. Build it after the derivations are trustworthy enough to show a resident, not before.
Who owns the billing history and the code if an agency builds this?
You should own the repository, the cloud infrastructure accounts, the database and the right to appoint another firm, agreed in writing before kickoff. At Digital Heroes the client owns the code and the data from the first commit and it does not change the price.
This matters more in utility billing than in most categories, because your stored charge derivations are the evidence you would rely on in a regulatory inquiry or a resident claim, and they should not sit behind a licence you might one day want to end.
How many developers does it take to build accounting software?
The standard Digital Heroes team is 4 to 6 people: a backend developer, a frontend developer, a QA engineer, a part-time designer, and a project lead who owns the accounting logic. A single-workflow automation can ship with two people, while multi-entity platforms with payroll can need eight. Headcount matters less than having one named person accountable for the books balancing.
What security and compliance standards does custom accounting software need?
At minimum: encryption at rest and in transit, role-based access control, and immutable audit logs recording every change to the ledger. If outside parties rely on your numbers you will want SOC 2 style controls, and storing card data pulls you into PCI DSS, which most builds avoid by tokenizing payments through Stripe or a similar processor. Your industry adds its own rules, so compliance requirements belong in the written spec, not in a post-launch retrofit.
Who owns the code when an agency builds my software?
You should, completely, through a written intellectual property assignment that transfers everything on final payment; without that clause, copyright stays with whoever wrote the code by default. Insist that the repository lives in your own GitHub organization from day one and that hosting, domains, and third-party accounts are registered to you. Also check for licenses to the agency's proprietary frameworks buried in the contract, because those can make switching vendors practically impossible even when you own your own code.
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.
How do I calculate whether custom software will pay for itself?
Divide the build cost by the monthly benefit, where benefit is hours saved times loaded hourly cost, plus subscription fees replaced, plus any revenue the software unlocks. Three staff saving 10 hours a week each at a $40 loaded rate is about $62,000 a year, which pays back a $60,000 build in roughly 12 months. Across Digital Heroes internal-tool projects, 12 to 24 months is the normal payback range, and anything projecting under 6 months usually means the spreadsheet is hiding costs.
How do I vet a development agency for an accounting software project?
Ask to see a live accounting or fintech system they built, then ask how they handle double-entry integrity, period closing, and audit trails; a team that has never built a ledger will learn on your budget. Check whether they bring an accountant or finance-literate analyst into scoping sessions. A portfolio proves design skill, but a walkthrough of how their system blocks an unbalanced journal entry proves domain skill.
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.
How many SaaS seats do we need before building custom becomes cheaper?
The crossover usually shows up between 20 and 50 seats on premium tiers. Salesforce Enterprise lists at $165 per user per month, so 40 users cost about $79,000 a year in subscriptions, which is real money against a custom system you would own outright. Run the comparison over three years: if subscription spend beats the build cost plus 15-20% annual maintenance, custom wins on price before you even count workflow fit.
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.
How do I migrate years of QuickBooks data into a custom system?
Use a staged migration: export full history through the QuickBooks API or backup files, load it into the new system, then run both systems in parallel for at least one full closing cycle before cutting over. Expect cleanup work, because books older than three years almost always contain miscategorized transactions that surface during import. Digital Heroes schedules migration as its own project phase with its own sign-off, never as a launch-week task.
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.
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 Saanvi.
Senior Shopify Engineer · B2B · Delhi · 1 post on the site
Published · Last updated .
