Home About Case Studies Hire Me Contact
Currently available for select engagements

Hire Software Developer for Energy Companies
Senior, direct, no layers

Software Developer for energy companies: cleaner meter-to-cash, fewer billing exceptions, and reporting that stands up to scrutiny.

15+
Years Experience
100+
Projects Delivered
6
Countries Served
$25M+
Revenue Enabled
Energy Companies — Development & Engineering

A senior software developer for energy companies

An energy company, in the retail supply sense, is really a billing and metering operation with a customer service desk attached. Meters are read, estimated, or missed; tariffs change; customers move, query bills, and fall behind; and field crews visit properties that may or may not match the address on file. When meter data, tariff rules, and customer accounts live in separate systems, a bill becomes an argument, and the argument is settled by whoever kept the better spreadsheet.

This is a build for one energy supplier's own operational system: customer accounts, meter readings, tariff rules, billing, and field visits for that supplier alone. It is not a solar installation system and not a trading platform; its centre is the account, the meter, and the bill, with readings, estimates, and corrections recorded as a history rather than overwritten. Generation, trading, and network operations sit outside this scope and connect only where they already feed account data.

The sharpest first slice is usually meter-to-bill reconciliation, because that is where queries and write-offs start. Book a free discovery call and the fit is tested on a set of real accounts with disputed or estimated bills, not on a generic demo.

Meters, tariffs, and accounts

What an energy supplier's own system has to get right

  • Customer accounts with their meter history — Each account holds its meters, readings, estimates, and corrections in sequence, so a bill can be explained from the readings behind it.
  • Tariff rules held as versioned data — Tariff rates, standing charges, and change dates are stored as rules with effective dates, so a bill from last quarter can be reproduced from the rules that applied then.
  • Billing runs with exceptions listed — Each billing run produces its bills plus a short list of exceptions, such as missing reads or unusual usage, for staff to resolve before bills go out.
  • Corrections that preserve the original — A corrected reading or bill is recorded as a new entry linked to the original, so the account history shows what changed and why, instead of silently rewriting it.
  • Field visits tied to accounts and meters — Meter exchanges, inspections, and access attempts are scheduled and recorded against the account and meter they concern, with outcomes visible to the service desk.
  • Payment plans and arrears in one view — Balances, payment plans, and promises to pay sit on the account, so a service conversation starts from the full position rather than the latest letter.
How it fits energy work

Built for billing cycles and field crews together

Billing systems earn trust by being reproducible. Any bill the system produces must be explainable from readings and tariff rules, and any correction must leave a trail a second person can follow. That discipline shapes the whole build: no hidden adjustments, no figures that only appear at print time, and no billing run that cannot be re-run and compared. The service desk view is built around the same principle, showing the account history in the order a customer would ask about it.

The pilot runs on a subset of accounts, with new bills compared against the old method line by line before any wider switch. The supplier owns the code, the data, and the hosting, and account histories export in a form that survives a future change of billing provider.

The order of work

From meter chaos to accounts that reconcile

  1. Reproduce a set of disputed bills

    Real accounts with queries or estimates are worked through by hand, and every place the current tools force a guess or a manual adjustment is noted.

  2. Define accounts, meters, and tariff versions

    The account, meter, reading, and tariff records are defined with their rules, including how estimates and corrections are handled, before building.

  3. Pilot meter-to-bill on a subset of accounts

    The billing path goes live for a pilot set of accounts, with new bills checked against the old method, and exceptions resolved before widening.

  4. Add field visits and arrears, then hand over

    Visit scheduling and payment-plan views follow once billing is trusted, and handover leaves documented code, data, and tariff-rule documentation.

Why Omer

Why hire Omer

  • Bills that can be explained: Every bill traces to readings and the tariff version in force at the time, so a query gets an answer from the record.
  • Corrections with a visible trail: Originals are never overwritten; corrections link to them, which is what auditors and customers both need.
  • Exceptions before bills go out: Missing reads and unusual usage surface in the billing run, not in the complaint queue afterwards.
  • Service desk and billing on one record: The desk sees the same account history as billing, so customers stop hearing different stories from different teams.
  • Supplier-owned account data: Code, data, and hosting belong to the supplier, and account histories export without the builder's help.
FAQ

Questions, answered

How are estimated readings handled?
Estimates are recorded as estimates, clearly marked, with the basis for the estimate visible, and they are replaced by actual readings when those arrive, with the bill corrected as a linked entry. Nothing is presented as a reading when it was not one.
Can tariff changes apply from a past date?
Tariff rules carry effective dates, so a change can be applied from its real start date and earlier bills can be reproduced under the rules that applied then. Retroactive changes still need the supplier's own policy decision; the system records and applies it cleanly.
Does this handle smart meter data?
It ingests reading feeds where the supplier already receives them and treats each reading as a dated record on the meter, with gaps and anomalies flagged as exceptions. It does not replace the meter data platform; it turns its output into billable account history.
What about customers who move property?
A move closes one account position and opens another with its own meter history, while the customer's identity links the two, so final bills and new accounts do not contaminate each other.
Is this a full billing platform replacement?
It can become the supplier's billing record, but the engagement is scoped to the supplier's actual operation: accounts, meters, tariffs, and field visits. Trading, network operations, and wholesale settlement are outside it unless the supplier's own data already feeds them in.
Currently available for select engagements

Ready to get started?

The best way to explore working together is a quick conversation. Reach out through your preferred channel and let us discuss your project.