Prepaid or Postpaid ISP Billing: Choose by Risk and Workflow
Compare prepaid and postpaid broadband models through entitlement, collections, accounting and customer operations.
Compare prepaid and postpaid broadband models through entitlement, collections, accounting and customer operations.
The billing model changes the service state machine
Prepaid and postpaid are not merely different invoice dates. Prepaid makes verified value a condition of future access; postpaid extends service before collection and creates receivable risk. Product design, suspension, refunds, revenue recognition, customer communication and support must agree with that choice.
Entitlement
Define the event that starts, extends, restricts and ends service.
Money
Separate invoice, payment, wallet, credit and revenue states.
Customer promise
State validity, due date, grace and restoration timing plainly.
Control
Make every automatic restriction reversible and auditable.
Use prepaid when value and access move together
Prepaid can reduce receivables and make household spending predictable, but gateway delays and wallet errors directly affect access. Never activate from an unverified return page.
Validity extension needs one rule for early recharge, late recharge, package change and partial payment. Preserve the transaction reference and before-after entitlement.
Use postpaid when credit supports the relationship
Postpaid fits contracts, institutions and customers needing uninterrupted service through a billing cycle. It requires credit policy, aging, reminders, disputes, adjustments and collection ownership.
Grace should be an explicit commercial rule, not an undocumented scheduler delay. Suspension must distinguish disputed, promised, partially paid and technically unavailable accounts.
Offer hybrid products carefully
Deposits, wallets, usage add-ons and advance payments can combine models, but each balance needs a defined liability and application order.
Compare collection cost, bad debt, gateway cost, support contacts and involuntary suspension—not only headline revenue.
Evidence before rollout
| Signal | Required proof |
|---|---|
| State map | Invoice, payment, entitlement and session transitions are documented. |
| Gateway proof | Activation follows verified, deduplicated settlement evidence. |
| Correction | Refund and adjustment preserve the original audit trail. |
| Communication | Due, validity, grace and restoration messages are unambiguous. |
| Reconciliation | Cash, gateway, ledger and subscriber state agree. |
Put the plan into operation
- Segment. Identify customer credit, continuity and collection needs.
- Model. Write both state machines and exceptions.
- Configure. Set pricing, grace, notices and permissions.
- Simulate. Test delays, duplicates, partials, refunds and migration.
- Pilot. Compare support and collection outcomes.
- Review. Adjust policy from reconciled evidence.
The decision standard
Select prepaid, postpaid or hybrid per segment only when finance, entitlement and communication can describe the same state and recover safely from late callbacks, corrections and disputes.
Research basis: IFRS revenue principles; TM Forum billing concepts; consumer protection guidance. Validate implementation details against the releases, contracts, and local regulations governing your network.