Lesson 2 of 6
Meter-to-cash in SAP S/4HANA Utilities
9 min
Listen to this lesson
Meter-to-cash is the utility's core process: install a device, read it, turn the reading into consumption, price the consumption by rate, create and print the bill, post it to the customer's contract account, collect the money and chase what is not paid. In SAP S/4HANA Utilities it runs on the same data model IS-U has always used, which is good news for a conversion: the objects testers know stay the same.
The data model
| Object | What it represents | Contoso Detroit example (illustrative) |
|---|---|---|
| Business partner | The customer | Contoso Motor Co. |
| Contract account | Where bills post and payments clear in FI-CA | Contoso Detroit plant account, payment by bank transfer |
| Contract | The supply agreement for one division (electricity, water) | Electricity contract and water contract |
| Installation | The billing-relevant unit: rate category, devices, billing data | Industrial electricity installation, large general service rate |
| Premise and connection object | The place and building served | Detroit plant, building A |
| Device and registers | The meter and what it measures | Interval meter: energy (kWh) and demand (kW) registers |
Meter-to-cash objects with Contoso as Northwind's customer.
The process
- ScheduleMeter reading units and billing portions set when each installation is read and billed
- Meter readingOrders created; results uploaded or entered (for example EL28) and validated
- BillingBilling documents calculated per contract: consumption, rates, operands (EA00 single, EA38 mass)
- InvoicingBilling documents combined into a print document with taxes and charges; posted to FI-CA
- Bill printBill created and sent by mail, email or portal
- CollectionPayments, returns, dunning, installment plans in FI-CA
Billing and invoicing are separate steps on purpose. Billing calculates what each contract owes for a period, using the rate category on the installation and the rates, operands and price levels behind it. Invoicing takes the billing documents of a contract account, adds taxes and other charges, applies budget billing amounts already paid, creates the print document and posts to FI-CA. A defect can sit in either, and the comparison method in lesson 4 must know which.
Rates and the worked bill
Contoso's June electricity bill (illustrative) combines an energy charge per kWh, a demand charge per kW of the month's peak, and a fixed customer charge. For 1,840,000 kWh at USD 0.072, a peak of 4,200 kW at USD 14.50 and a USD 350.00 customer charge, billing calculates USD 132,480.00 + USD 60,900.00 + USD 350.00 = USD 193,730.00 before taxes. Each line comes from a different operand and rate step, which is exactly what the comparison must check line by line.
| Line (illustrative) | Quantity | Price | Amount USD |
|---|---|---|---|
| Energy charge | 1,840,000 kWh | 0.072 per kWh | 132,480.00 |
| Demand charge | 4,200 kW | 14.50 per kW | 60,900.00 |
| Customer charge | 1 month | 350.00 | 350.00 |
| Total before taxes | 193,730.00 |
The Detroit plant's June electricity bill from Northwind.
Convergent Invoicing as an option
In SAP S/4HANA, IS-U billing results can also be passed to SAP Convergent Invoicing as billable items, where they are combined with non-commodity items, such as services or equipment rentals, into one invoice that posts to FI-CA. SAP describes this as an additional option beyond classic IS-U invoicing and bill print. A conversion usually keeps classic invoicing first and evaluates Convergent Invoicing separately, because changing the invoicing path changes every bill's structure at once.
What would you do?
In a test cycle, Contoso's simulated bill shows the right energy charge but a demand charge of zero. Other industrial customers are fine. Where do you look first?
What goes wrong in testing
| Symptom | Usual cause | Test |
|---|---|---|
| Estimated bills where actual reads exist | Results uploaded after the billing run, or failed plausibility | Check read status before billing in each cycle |
| Charges missing for a register | Register not billing-relevant after a device change | Test a device replacement mid-period |
| Bill does not post to FI-CA | Invoicing not run, or account determination error | Run invoicing and check the contract account |
Meter-to-cash defects seen in testing.
Budget billing and annual settlement
Many residential customers pay equal monthly budget billing amounts and receive one settlement bill a year. That creates two tests. Each month, FI-CA must request the right budget billing amount and clear it when paid. At the annual bill, invoicing must take the year's consumption charges, subtract the budget billing payments already made, show the balance, and propose new budget billing amounts for the next year. A converted customer whose budget billing plan started in ECC and settles in SAP S/4HANA is the most valuable test case, because it crosses the conversion.
| Item (illustrative residential customer) | Amount USD |
|---|---|
| Annual consumption charges and taxes | 1,488.40 |
| Budget billing paid (12 × 120.00) | 1,440.00 |
| Balance due on the annual bill | 48.40 |
| New monthly budget billing amount proposed | 124.00 |
An annual settlement with budget billing that started before conversion.
- The IS-U data model continues in S/4HANA Utilities: contract account, contract, installation, premise, device.
- Billing prices consumption by rate; invoicing creates the print document and posts to FI-CA.
- Convergent Invoicing is an added option, not a forced change.
- Keep hand-checked golden bills per rate category.
Check your understanding · not graded
Lesson check
1. Which object carries the rate category and is the billing-relevant unit?
2. What does invoicing do that billing does not?
3. 1,840,000 kWh at USD 0.072, 4,200 kW at USD 14.50, plus USD 350. What is the total before taxes?
4. How does SAP describe Convergent Invoicing for utilities in SAP S/4HANA?