If the billing period ends on the 28th, are the 29th, 30th, and 31st (when exists) included in the next cycle? Right now NMU will set the billing period to begin on the first.
The actual billing period is from the 29th through the 28th. So the new cycle does include the 29th, 30th, and the 31st. Cycle is always a period consisting of 30days. NMU allows you to choose your billing period start date; but only between the 1st and the 28th.
It might not include the 29th due to leap year. In Leap year would your billing period shift to the 28th through the 28th and then return to the 29th? Just trying to validate the flow for the team.
Okay, Erik, I not meaning to come off as condescending, but your statement seems a bit slighting. You’re the employee so only you would know if that’s the case. And, in general, that is not the case- save for those robust calendar software utilities. Even those self adjust. And to answer your second question, “yes” my billing period is the same- even during leap year. And this is not a leap year.
Hi Marcus,
I have never known Eric to be condescending. I believe that all he was trying to do was to check with you that if the 29th were included as a start date then you would be content to accept the logic that, in a normal February the start date would be treated as 28th and then returned to 29th on subsequent months. This however does not seem a sensible logic, to me.
I have a different suggestion which I think might work. The option that is currently given is for the billing start day -which I take to be 29th in your case and which causes an oddity in most Februaries, If instead we were given the option of a monthly bill end date, then you could select 28th and all would be fine. Should anyone have an end date of 29, 30 or even 31 then the obvious logic (to me) is to end on the selected day or before the next month whichever is the earlier. I assume this is the logic that charging companies would use.
Hope that made sense!
Thank you Andmike. Your solution is the same that I've been using- setting the end date to the 28th. But that gives me a bit of a staggered data reading total. Considering how smart phone work, I try to stay up on my usage for security reasons. But, again, u made perfect sense and how do I go about apologizing to Erik? Should I do a post of reply? The reason he came off as condescending tome when he brought leap year. Because we aren't in a leap year, I took it as a slight. I apologize to Erick, you, and the forum/community as a whole because that small attitude isn't proper when you're seeking help.
I made a typo in my response. Only in leap year would February have a 29th to start the billing period on, so every other year would need to be handled as an exception within the product. Mike's suggesting of the end date being on the 28th would work as long as in your case that then there are only 28 days in February that the Feb billing period ends on the 28th and the next period begins March 1. Could you confirm this just so I can communicate the need to the team correctly? When a feature or option is designed in a product we need to clearly outline the use cases for that feature. It looks like we missed one in your instance, but we just need to make sure that it's clearly outlined.
Also, there's no need to apologize. I made a mistake in my response that was confusing.
Erik,
I’ve called my provider and they informed me that though my cycle ends the 28th month-to-month, on Feb. 28th it still ends, but it would start over on the 1st of the following month- which would be March. This in spite of my cycle ending normally on the 28th and starting on the 29th. But of course during a leap year, the cycle would be normal- being that then there would be 29days. Hope this helps.
Thanks for confirming Marcus. We will try to fix this n the next release.