The problem we started with
Organisations running more than a handful of electricity connections spend every billing cycle doing the same thing: logging into a different portal for each DISCOM, solving a captcha, downloading a PDF, and typing numbers into a spreadsheet.
- Each utility has its own portal, its own login flow and its own bill layout.
- A PDF is a picture, not data — you cannot query it, trend it, or compare it.
- Accounts get skipped, numbers get mistyped, and nobody notices until much later.
- A cost spike is usually discovered after the payment has already cleared.
What we built instead
LiteBill turns that scramble into a pipeline. Scheduled workers handle the portal work, the bill is converted into structured fields, every critical value is checked against rules, the source document is archived, and a clean record lands in the systems you already use.
The parts that usually break — a portal changing its layout, a captcha changing shape, a credential expiring — are treated as normal operating conditions with defined recovery paths, not as outages.
What we hold to
Permission before access
No bill is retrieved without a documented authorization from the genuine account holder. It is the first rule, not a footnote.
Hold back bad data
A wrong number delivered confidently is worse than a gap. Records that fail validation stop for review instead of shipping.
Show your working
Every stage transition is logged. If someone asks why a bill was fetched or how a value was derived, there is an answer.
Start small, prove it
One DISCOM, your own sample bills, real output. Expansion should follow evidence, not a sales cycle.
Why consent sits at the centre
Electricity bills reveal where someone lives or operates, how much energy they use, when premises are occupied and what they owe. Automating access to that is only defensible if the person it belongs to has agreed.
So the authorization is the thing that switches a connection on. Without it, the connection stays inactive and no portal is ever touched — regardless of who is asking or how large the account is.
The mechanics are set out in our Bill Access & Consent Policy.
Who uses it
- Energy consultants advising from months of comparable data instead of a folder of PDFs.
- Facility and operations teams watching consumption across sites in one place.
- Multi-site enterprises normalising hundreds of connections across states and DISCOMs into one schema.
- Finance and audit teams who need every figure validated and traceable before it reaches the ledger.
Talk to us
The honest way to evaluate this is to run it on your own bills. Pick one DISCOM, give us a handful of connections you are authorized to access, and judge the output.
Questions about this page?
Our team answers policy and compliance questions directly.