How to Hire a Submetering and Utility Billing Software Development Company
Judge every firm on one test: can it rebuild a single resident's bill, line by line, in front of somebody who is not on your side.
On this page
Judge every firm on one test: can it rebuild a single resident's bill, line by line, in front of somebody who is not on your side. Expect $60,000 to $130,000 for a first release covering read ingestion, allocation, prorations and master bill reconciliation, and $150,000 to $380,000 for multi state rules, a resident portal and posting into Yardi.
Utility recovery software is a bookkeeping system wearing a billing system's uniform. It will not be judged on the statements it prints. It gets judged the day a master water bill arrives at $19,840 for a 312 unit property, the run produces $18,410 of resident charges, and nobody can say where the other $1,430 went because no report compares the two. Then three residents call, and the coordinator needs forty minutes in three systems to produce a paragraph rather than evidence.
What makes this hard to buy is that the compliance surface is jurisdictional and invisible in a demo. A firm can show you a tidy allocation screen with no concept of which formula your state permits, what administrative fee is capped where, or what disclosure has to sit in the lease addendum. Every vendor's screens look the same. The difference shows up in a demand letter.
What a utility billing development company actually does
The statement generator is the easy part and the part everyone demos. The rest is the engagement.
Read ingestion per meter vendor, each with its own file shape and its own failure signals, plus gap detection with an age, so a unit missing from the file raises an alert rather than quietly becoming an estimate. Estimates marked as estimates, carrying the method used and an obligation to true up when the real read lands. Register rollover and meter changeout handled explicitly with old and new register values, which is the single most common cause of a wildly wrong bill after a renovation cycle. Tiered and block rates applied at the master level and then distributed, because applying a tier per unit and summing gives a different number and a poor position to defend.
Then the controls. Jurisdiction as a first class object with an effective dated rule set covering permitted methods, fee caps, disclosure text and billing windows, so a property cannot be configured with a method its jurisdiction does not allow. Proration by actual days against the read interval rather than the calendar month, with vacant cost posted to the property as a reportable number instead of vanishing. And reconciliation as the primary object, not a report: resident charges plus owner absorbed plus vacant must equal the master invoice, or the run does not release without a recorded reason and an approver.
What it really costs in 2026
| Scope | Cost | Timeline |
|---|---|---|
| Read ingestion, submeter billing, prorations, master bill reconciliation, per unit audit trail, one state | $60,000 to $130,000 | 12 to 18 weeks |
| Adding allocation methods, multi jurisdiction rule sets, resident portal and dispute workflow | $140,000 to $250,000 | 6 to 10 months |
| Full platform with property accounting posting, utility bill capture, billing service provider model | $250,000 to $380,000 | 7 to 12 months |
| Support plus jurisdiction rule maintenance | 15 to 20 percent of build per year | Retainer |
Two costs are almost never in the quote and always in the project.
The parallel run. You cannot cut over utility billing in a single cycle. Two full cycles billed twice, old process and new, reconciled line by line before you send anything to a resident, is the only honest test. That is staff time on your side and delivery time on theirs, and it is the phase that catches the proration rounding and the period boundary mismatch. A quote without it is quoting a demo, not a billing system.
Utility bill capture. Reading master invoices automatically sounds like a checkbox. Every utility formats differently, several produce documents from decades old systems, and a few still post paper to the property office. Price capture as its own workstream or decide openly that you will keep keying master bills. What you should not accept is a line saying invoice capture with no discussion of how many utilities you deal with.
Signals of a strong partner
- They draw the model before they discuss screens. 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, charge line with derivation.
- They mention register rollover unprompted. A firm that raises meter changeouts in the first hour has billed through a renovation cycle before.
- They treat reconciliation as a gate. A run that can release while it does not balance is an invoicing tool, not a recovery system.
- They ask how many states you operate in. Each distinct regime is configuration plus verification plus test cases, and they should price it that way.
- They ask about your lease addendum. Disclosure language is part of the compliance record, and the system should evidence that the resident was shown it.
- They separate reading from writing in Yardi or RealPage. Posting charges is one problem and posting reversals is a harder one.
- They will tell you to stay with Conservice. Under roughly 3,000 units in one or two states, outsourcing carries the compliance burden for less than a build costs.
Red flags
- A model built from units and invoices. Without the meter, the read and the derivation, your audit trail does not exist and neither does your defence.
- Estimates treated as final numbers. If an estimate never creates a true up obligation, you are storing a future catch up bill nobody can justify.
- Allocation methods offered as a dropdown with no jurisdiction attached. That design puts the legal decision in an untracked setup screen.
- Recalculations that overwrite. A rebill you cannot explain is worse than no rebill, so prior versions must remain retrievable with a reason and an operator.
- A fixed price before seeing a real read file. Meter vendor formats differ enough that scoping unseen is guesswork.
Questions to ask on the first call
- Draw me the data model, including register history and charge line derivation.
- A meter is replaced mid period during a renovation. What happens to the register, and what does the resident see?
- The utility billed 34 days and our cycle is 30. How do you map that, and where is the method recorded?
- Fifteen units have no read this month. What happens now, and what happens in March when the real reads arrive?
- A resident moves out on the 14th and the next moves in on the 22nd. Who carries the eight days, and where does that number surface?
- Water is on a tiered rate. Do you apply the tier per unit or at the master and distribute?
- We operate in six states. Where does a rule live, and what happens when one of them changes?
- Show me the single screen you would hand to a state agency for one resident's bill.
- Can you write charges and reversals into Yardi, and who owns the historical derivations if we end the engagement?
A simple way to decide
Pay for a short discovery before you commit to a build. Two to three weeks, paid, ending in a written specification you own: the data model, your jurisdiction list with the rule set each carries, the meter vendors and their file formats, the reconciliation control expressed as an acceptance test, the posting path into your property management system, and a first release limited to one state and your directly submetered properties. Send it to three firms and the numbers finally compare.
Digital Heroes writes a product requirements document before any code and gives the client the repository from the first commit, which matters here more than in most categories: your historical charge derivations are your legal defence, so they should never live behind a licence you might want to end. We are the wrong firm if you hold under 3,000 units in one or two states, because Conservice carries the compliance burden as part of the service and doing it yourself would cost more than it recovers. We are the right firm when jurisdiction rules have become a compliance surface, or when the platform is your product.
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.
- Inventory carrying cost commonly runs about 20% to 30% of inventory value, covering capital cost, storage/warehousing, insurance, taxes, handling, shrinkage, and obsolescence - a recurring cost that better inventory and warehouse software aims to reduce. Source: APQC (2023) →
- McKinsey found that currently demonstrated technologies can fully automate about 42% of finance activities and mostly automate a further 19%, indicating roughly 60% of finance work is technically automatable. Source: McKinsey & Company (2018) →
- In the Flexera 2025 State of ITAM report, respondents reported roughly 33% of SaaS spend is wasted, underscoring how paying for off-the-shelf seats and tiers that go unused erodes the supposed cost advantage of generic SaaS. Source: Flexera (2025) →
- SaaS spend averaged $4,830 per employee (up 21.9% year over year), with large enterprises (10,000+ employees) spending roughly $284M annually and running about 660 apps, while organizations wasted an average of $21M annually on unused licenses. Source: Zylo (2025) →
Frequently asked questions
How much does it cost to add a new state to an existing utility billing system?
Budget roughly $10,000 to $25,000 per additional jurisdiction once the effective dated rule engine exists. The work is capturing permitted allocation methods, fee caps, disclosure requirements, billing windows and dispute response rules, then writing test cases that prove a property in that state cannot be configured with a method it does not permit. The first state costs far more because it forces the rule engine into existence.
Who owns the billing history if an agency builds our system?
You should, unconditionally. Every charge line, its inputs, and every recalculation version is evidence you may need years later in front of a regulator or a plaintiff's firm. Insist on the repository in your account from the first commit, infrastructure in your name, and a contractual right to export the full derivation history in a documented format. A vendor holding your billing derivations holds your legal defence.
What happens if a resident disputes a bill from eighteen months ago?
A properly built system reproduces it: the master bill and its period, the allocation method with the jurisdiction rule that permitted it, the unit's read pair with dates and source, the proration days, the fee, and every recalculation with its reason and operator. If assembling that takes forty minutes across three systems, the dispute is answered with a paragraph instead of evidence, which is exactly the position that turns a phone call into a filing.
Can we keep Yardi or RealPage and still build a custom billing engine?
Yes, and most portfolios should. Leases, ledgers and resident records stay where they are, and the billing platform reads occupancy intervals and posts charges back. Ask specifically about the write path, because posting a charge is straightforward and posting a reversal against a closed period is not. Settle which system owns the charge record before development starts, or you will reconcile two of them forever.
Should we bring utility billing in house or keep outsourcing it?
Keep outsourcing under roughly 3,000 units in one or two states. Bring it in house when you operate across enough jurisdictions that the rules are a compliance surface, when your recovery rate has drifted and nobody can explain the gap, or when the per unit outsourcing fee would fund an internal system within about three years. Being a billing service provider for other owners is a separate and stronger case.
How do you handle a submeter that has not reported for four months?
Never by quietly estimating and moving on. Expect a read for every active meter, raise a gap with an age when one does not arrive, and escalate it as a maintenance item rather than a billing one. Estimates should be flagged, carry the method used, and create an obligation to true up once the real read lands. Four months of silent estimates produces a catch up bill you cannot defend.
What is the difference between submetering and ratio utility billing?
Submetering measures a unit's actual consumption through a meter serving only that unit. Ratio billing allocates a shared master cost by a formula, usually occupants, square footage or a weighted blend, when no submeter exists. The legal treatment differs sharply: some jurisdictions restrict ratio billing for water entirely and some require submeters in new construction. A system should model both and enforce which one a given property is allowed to use.
How long before we can run production billing on a new platform?
Twelve to eighteen weeks to a first release, then two full billing cycles running in parallel with your current process before you send a resident anything from the new system. That parallel period is where proration rounding, period boundary mismatches and vacant cost handling get caught. Anybody proposing a single cycle cutover on a portfolio has not been through a month where the numbers disagreed.
Will the system tell us where we are losing recovery?
It should, and that is often the strongest argument for the build. Once reconciliation is a gate, the variance between what the utility charged and what you billed becomes a measured number per property per period rather than an unnoticed gap. Vacant cost becomes a reportable metric, and high vacant consumption usually means a running toilet or a unit left heated, which is a maintenance ticket rather than a billing mystery.
Do we need a resident portal in the first release?
Not for correctness, but it pays back quickly. A portal showing consumption history alongside the charge deflects a meaningful share of calls without a human, and it creates a timestamped record that the resident was shown the disclosure. Most portfolios ship the billing engine and reconciliation first, then add the portal and dispute workflow in the following phase once the numbers are trusted internally.
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.
I'm outgrowing FreshBooks. Is custom software the logical next step?
Usually not directly, because FreshBooks is an invoicing tool more than a full accounting platform, and the natural next step is QuickBooks or Xero for proper double-entry books. Custom development makes sense when those do not fit either, typically because of a billing model none of them handle, like usage-based or milestone billing. In that case a custom billing engine that feeds a standard ledger is often smarter than replacing everything.
What are the biggest mistakes companies make when building accounting software?
The three we see most across Digital Heroes rescue projects: replacing everything at once instead of automating the most painful workflow first, skipping the parallel run so errors surface in live books, and letting developers design the ledger without an accountant reviewing the data model. A fourth is quietly expensive: no assigned owner for tax rate and compliance updates after launch. Every one of these is cheap to prevent and costly to unwind.
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.
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 .
