Suspension Log
Overview
The Suspension Log records every automatic customer suspension triggered by the ISPBills billing system. When the billing automation suspends a customer's service — for example, because an invoice is overdue — the event is written to this log. It is your primary tool for diagnosing billing automation issues and verifying that suspensions are firing correctly.
What Is Recorded
Each entry in the Suspension Log represents a single automated suspension event:
| Column | Description |
|---|---|
| Timestamp | The date and time the suspension was applied. |
| Customer Username | The PPPoE or hotspot username of the affected customer. |
| Reason | The reason the system triggered the suspension (e.g. Invoice overdue, Subscription expired). |
Common Use Cases
- Diagnosing billing automation issues — If a customer complains their service was cut unexpectedly, search for their username in this log to confirm whether and why an automated suspension was applied.
- Verifying suspension timing — Check that suspensions are firing on the expected date according to your billing cycle configuration.
- Auditing mass suspension events — After a billing run, review the log to see how many customers were suspended and confirm the automation is working as intended.
- Resolving disputes — Use the timestamp and reason fields as evidence when discussing a suspension with a customer.
Searching and Filtering
Use the search bar to search by customer username or reason text. Use the date range filter to focus on a specific billing cycle or incident period.
Exporting to CSV
Click Download CSV to export the filtered suspension records. This is useful for reconciliation during billing audits or for sharing data with your finance team.
Adding Reviewer Notes
Click on any log entry to add a Reviewer Note. Use notes to record whether the suspension was correct, whether it was manually reversed, or any other context relevant to the event.