A bill is a number someone else sets
Electricity, water, health insurance and internet follow one pattern: enter an ID, ask the biller, pay what comes back. Where the four differ, why due dates shape the month, and why fees come per bill.
Figures come from public sources and are typical, not guaranteed. The biller’s own app shows the current rules.
You do not choose the amount
A prepaid product lets the customer pick the amount. A monthly bill does not. The biller decides what is owed, and the customer can only pay that number.
- Prepaid: you choose
The customer picks the amount and the product.
Airtime, PLN token, game top-up
- Monthly bill: they choose
The biller calculates what is owed, per customer and per month.
Postpaid electricity, water, health insurance, internet
Read the full section
Think of a PLN token: you choose Rp50,000 or Rp100,000. Now think of a postpaid electricity bill, a water bill, a health insurance contribution or a home internet bill. The amount was calculated by someone else, for a specific customer and a specific month.
That one difference changes how the product is built. The platform cannot let the customer type a number. It has to ask the biller first.
Four bills, one pattern
Postpaid electricity, water, health insurance and internet all follow the same pattern: enter a customer ID, run an inquiry, see the amount, pay. What differs is who sets the amount and what happens if you are late.
Pick a bill to compare how the same pattern plays out.
- You enter
- Customer number or meter number
- Who sets the amount
- PLN, from your metered use
- Typically due
- The 20th of the month
- If you are late
- A late fee that depends on power class; service can be disconnected temporarily.
- What varies
- Power class and the later stages of disconnection.
Read the full section
The customer enters an identifier: a customer number, a meter number or a membership number. The platform sends an *inquiry* to the tier above, which comes back with the name, the period and the amount owed. Only then does the customer confirm and pay.
In my experience the flow for regional water bills is almost the same as for electricity. What changes is the biller behind it, and with it the due date, the late rules and the fees.
Pick a bill below to compare. Everything shown is from public sources and is typical, not guaranteed. The biller's own app shows the current rules.
The month has a rhythm
Bills do not arrive evenly. Due dates cluster in the month, so payment traffic does too. The platform feels this as a calendar.
Read the full section
Electricity and home internet are both commonly due on the 20th. Health insurance contributions are due by the 10th. Water bills depend on the local utility, so there is no single date.
For a platform, that rhythm means that volume, support questions and the risk of pending transactions peak in the days before a deadline, not on an average day. A customer who pays on the last day has no room for a delay.
Fees come per bill
The amount belongs to the biller. The platform earns through fees, and the fee is charged for each bill, not for each payment.
Read the full section
In my experience the admin fee is set by the provider, and the markup on top of it depends on the market price. This is the same logic as the PLN token note.
Admin fees for water bills differ by region. In August 2026, BCA published adjustments for several districts, for example Rp3,000 for Cianjur (down from Rp3,500) and Rp2,500 for West Halmahera. A customer who settles two months at once is paying two bills, so the fee applies twice.
When something goes wrong
Bills add a few failure cases that prepaid products do not have. The bill may already be paid elsewhere, the customer ID may be wrong, or the inquiry may find nothing at all.
Read the full section
A bill can be paid through another channel between the moment a customer looks at it and the moment they confirm. The inquiry is how the platform avoids charging for something that is already settled, which is why it comes first.
A wrong customer ID is a clear failure: the inquiry returns nothing. A slow answer from the biller is the hard case, and it follows the same logic as any other product. It is not a failure until the answer says so. The details are in the note on the anatomy of a failed transaction.
Being late has consequences that are set by the biller, not by the platform. Those consequences are why customers pay near the deadline, and why a delay at the wrong moment matters.
What to take from it
Pay a few days before the due date, and check the amount in the biller's own app if it looks unusual.
If you build the product, treat the inquiry as part of it rather than a technical step. Show the period and the name that came back, so customers can see it is the right bill before they pay.
If you run operations, expect the calendar, and plan capacity and support for the days before the 10th and the 20th.
Sources and notes
Public information and typical practice from my own experience, not any company's internal process. Public figures can change, so check the biller's own channel.
- PLN postpaid: commonly cited due date is the 20th of the month, and late fees depend on power class under the energy ministry's Regulation 27 of 2017. Sources disagree on the later stages of disconnection, so they are not described here.
- BPJS Kesehatan: contributions are reported as due by the 10th; late payment makes membership inactive in the following month until arrears are paid. Reports differ on penalties, so check Mobile JKN.
- Home internet (IndiHome, per Telkomsel's published terms): due on the 20th, a late fee of 5% of the outstanding charge or at least Rp5,000, and service blocked from the 21st. Other providers differ.
- Water (PDAM): admin fees vary by region. Source: BCA notice on PDAM admin fees, August 2026.
- The full chain, tier by tier, is in the deep explainer. The prepaid electricity side is in the PLN token note.