zenzen

[sage thorn]

Hi,
I see you are using a test clock here.
When creating the subscription, you set the billing_cycle_anchor to 1677589200 which is 28th of February,
That's why a first prorated invoice was generated for the period 24th Feb (trialing ends) to 1st of March (new billing_cycle)

What were your expectations regarding this test scenario ?

[delicate plover]

we're expecting that if you set the billing anchor to the 1st of the month (March 1st in this case) it will generate the invoice for the whole month of the subscription monthly (March 1st to March 31st) but it generates an invoice with the start / end period with a (March 1st to March 28th) which does not encompass the whole 31 days of the month.

[sage thorn]

I think the issue is that the billing cycle anchor was set at 2023-02-28 13:00:00 UTC try setting it to the 1st of March instead with another test

[delicate plover]

we're setting it on the dashboard, Australian time, there's no option to set the time of the anchor to accomodate utc changes

[delicate plover]

anyways, I want to confirm the behavior of the billing anchor, does it count the days of the month it was set in? like in this case it was set in February which has a 28 days month so it counts the monthly cycles as 28 days? if in another case the anchor was set in march it counts the monthly cycle as 31 days and so on?

[sage thorn]

Sorry, I was doing some tests

Just checking something else between

Sorry for the late reply, I was doing multiple tests between regading your use case, thanks for your passions.
Actually, the billing_cycle_andhor is the date which will determine the billing. In your case, you set the billing cycle to 28th of February, so each month, on the 28th, new billing period is considered.
If you set billing_cycle_anchhor to 4th of a month, then every month on the 4th a new billing period is considered and so one.

I hope I'm enough clear in my last message