Part of Baseload, the utility enterprise platform
Baseload Revenue is the customer information system (CIS) and billing engine inside Baseload — the customer register, tariff engine, vending, payments and debt management an electricity distributor’s commercial directorate runs on, deployable first, ahead of the rest of the platform.
CUSTOMER INFORMATION AND BILLING FOR ELECTRICITY DISTRIBUTORS
IN DEVELOPMENT
Request a briefing →THE PROBLEM
CAPABILITIES
One record per customer, one per service connection, with the full history of applications, agreements, meters and tariffs attached. The register the rest of the module — and the rest of Baseload — reads from.
From application through inspection, quotation, payment and energisation — tracked end to visible end, with service-level clocks the commercial directorate can hold teams to.
Every meter tied to a connection point and a customer, from procurement through installation, recertification and retirement. The linkage that makes losses attributable rather than mysterious.
Lifeline blocks, tiered energy charges, time-of-use, maximum demand and statutory levies expressed as configuration, not code — so the tariff in the system is the tariff the regulator approved.
One customer, one account, whether the meter vends tokens or receives a bill. Migration between modes is a change of state, not a re-registration.
Mobile money, banks, agents and aggregators reconciled to the customer account automatically — with the unmatched-payment queue worked down inside the system, not in a spreadsheet.
Ageing, instalment plans, disconnection queues generated by rule, reconnection on payment — with the audit trail the regulator and the customer both see.
Consumption anomalies, bypass indicators and zero-usage accounts surfaced for inspection, with case tracking from flag to field visit to resolution.
Complaints, faults and service requests logged against the customer record, routed by category, and measured against the service standards the regulator publishes.
Balance, bills, vending, payments and service requests in the customer’s hands — reducing the queue at the district office without changing the record system behind it.
DEPLOYMENT
Baseload Revenue goes live in phase one, ahead of the rest of the platform, for utilities replacing a billing system before anything else. It deploys first — on the same foundation the rest of Baseload builds on.
Baseload Revenue works with what the utility already runs: existing finance systems, AMI head-ends, meter data management and GIS connect over open interfaces. It interoperates with the estate around it — replacement of any of those systems is a separate decision, on the utility’s timetable.
HOW IT CONNECTS
The customer record in Baseload Revenue is the same connection point AMPERE monitors, and the same record the rest of Baseload draws on. Fixing billing and fixing the network stop being separate projects.
AMPERE — NETWORK INTELLIGENCE →BASELOAD — THE UTILITY ENTERPRISE PLATFORM →
REQUEST A BRIEFING
A briefing covers the customer and billing capabilities, the phase-one deployment path, and how Baseload Revenue sits alongside the metering and finance systems you run today.