Month-End Renewals: Handling the 29th, 30th and 31st

WayaDesk / PPPoE and renewals

Month-end renewals reveal whether a billing rule is clearly defined. A subscriber whose anniversary falls on the 31st cannot always receive the same numbered day in the following month. Operators need consistent behaviour and a customer explanation that matches it.

Understand the documented anniversary rule

LinkDesk’s calendar-month implementation preserves the local time and anniversary day across the sequence. An anniversary on January 31 moves to February 28 or 29 as appropriate, then returns to March 31 while that sequence continues. An expired account that pays later starts a new anniversary from the payment time.

Demonstrate the boundary before launch

Use test records for the dates that are difficult to explain, not only a purchase on the 15th. Inspect the start and end of each paid period. If staff disagree about the result, resolve the rule before the customer sees it.

• Check a short month and a leap-year scenario in the test plan.
• Confirm the Africa/Nairobi date and local time shown to the operator.
• Keep an example of a late renewal separate from an uninterrupted sequence.

Preserve the purchased record

Do not rewrite an older paid period simply because the next month has more days. The service-period history should explain what the customer bought at the time. If an operator grants an additional adjustment, document that as an intentional business action.

Use plain customer wording

Explain the exact next expiry instead of saying that the software has “taken away days”. A clear account view and a consistent staff script can prevent a normal calendar result from becoming a payment dispute.