tymm

[icy badger]

hello! can you elaborate more on what you mean by automatic collection starts 1 month late?

[hushed inlet]

my billing cycle anchor was set to 1st of month 0600
i created the previously mentioned subscription and set the anchor
and then after the first payment was collected, i update the subscription to pause collection and set resumesat = 1st of nov 0600

however, the expected invoice on 1/11 got voided and the next un-voided invoice comes at 1/12

and also, why is the 1/11 invoice comes on 31/10?

with the upcoming invoice coming on the correct date

[icy badger]

so to confirm, you created the subscription, on Sep 27, you want it to pause payment for Oct 1, and resume on Nov 1 - is this correct?

[hushed inlet]

correct

[icy badger]

you need to unpause the subscription earlier

not exactly on the next time the collection is supposed to occur

[hushed inlet]

so to be exact i would need to set the resume time latest at 0559 1/11? since my billing cycle anchor is at 0600 1/11 ?

and i should be fine setting the resumesat to 0600 1/10 and the october invoice will still be voided and nov invoice will get collected, right?

[icy badger]

you would need to test it out, but i would set it earlier i.e. maybe a day after the time to collect it has passed (for the collection date you want it to skip)

[hushed inlet]

right ok

[hushed inlet]

any idea on this tho? why is the nov invoice coming on oct 31?

[blissful fractal]

Hey, taking over here. Can you share the in_xxx ID?

[hushed inlet]

hi, i've created a new subscription and this time i set the resumesat = 31/10 0600, the november invoice is being charged however it's still on oct 31 for some reason
sub_1LmYrtLK0bfo5HSb13mIZDOe
in_1LmYvCLK0bfo5HSbCMFEMg6p

[blissful fractal]

I think this is an issue with timezones. You're in UTC+8, right?

Yet our timestamps are all UTC

[hushed inlet]

i dont think so

im always giving UTC epoch timestamps

[blissful fractal]

Yes, and the timestamps on the Invoice object reflect that. It's only in the Dashboard that you see the localised time

[hushed inlet]

my time is 6am, if its problem with time zone and mine is +8, it would be on oct 31 2200 instead, since im setting nov 1 0600

ok let me try creating another subscription

[blissful fractal]

What are you actually trying to achieve?

[blissful fractal]

The invoice would be generated immediately after resuming, this is expected

[hushed inlet]

this is the new subscription that i have created

notice it says collection pause until nov 1
but the next invoice is coming on oct 31

in this case, which i have tested prior, the invoice on oct 31 will get canceled and i wouldnt get invoice on nov 1 and the next invoice will be on dec 1 instead

[blissful fractal]

The screenshot is no use to me really, I need the sub_xxx ID

[hushed inlet]

sub_1LmZJdLK0bfo5HSbMjBzBdl6

resumesat was set to 1667253600

local time nov 1 0600, same as my billing cycle anchor actually, which is 1st of month, 0600

[blissful fractal]

• You're setting resumes_at to 2022-10-31 22:00:00 here: https://dashboard.stripe.com/test/logs/req_OYTD9lgvhj6u4i
• The next invoice in_1LmZKrLK0bfo5HSb9dBpkfB4 (https://dashboard.stripe.com/test/invoices/in_1LmZKrLK0bfo5HSb9dBpkfB4) for billing period 2022-09-30 22:00:00 - 2022-10-30 22:00:00 is automatically voided because of the paused collection state.

The labelling in the Dashboard is I assume confusion between timezones as I explained

It's set to resume 2022-10-31 22:00:00 UTC which is actually 2022-11-01 06:00:00 in your timezone

I guess the Dashboard isn't localising one of those timestamps

[hushed inlet]

hmmm, if thats the case shouldnt the invoice on oct 31 comes in at 2200 instead of 0600 here?

in_1LmZgpLK0bfo5HSbRNOv0w7K

i notice that the billingcycle seems affected by this pausecollection api...
now i have advanced the time of this customer and the billing date seems to change

[blissful fractal]

I'm really unsure what you're asking me at this point or what the underlying issue is

[hushed inlet]

im expecting the invoice to come in on the anchordate that i have set the first time i created the subscription, which on on the first day of month

as u can see here the dates of the invoice is not consistently on the first day of month, how do i make all them subsequent invoices coming in at the first day of month?

sub_1Lma4oLK0bfo5HSbloWyOkIs subid incase u neeed it

do i need to update the subscription manually every month to achieve that?

i think i know what the problem is, stripe is using 30 days month and thats why the invoice is coming in at times that im not expecting, correct?

[teal plaza]

Hey! Taking over for my colleague. Let me catch up.

[hushed inlet]

i guess it's due to this doc right here that i would expect that the billing date for every month to be consistent

[hushed inlet]

hi again 🥲

[teal plaza]

May I ask you please resume your last followup question?

[hushed inlet]

basically i was trying to use PauseCollection api on subscription

eg:
i create subscription now and immediately charge customer for 27/9 to 30/9, and i want to pause collection for 1/10 to 31/10, and continue on 1/11
and then i found out that even though i have set the billing cycle anchor to 1st of month, and i have set the pausecollection resumesat to be on 1/11, the invoice comes in on 31/10 instead and since the resumesat was set to 1/11 so the invoice got canceled

[hushed inlet]

and based on the doc it seems like when i set the billing cycle anchor to 1/10 the first time, the subsequent months will be using day of month "1" as the billing day?

if so it's not happening~

[hushed inlet]

as u can see here~

i am actually using this approach to simulate upfront payment (my question to u yesterday)... i will be backdating to the same day of previous month eg 27/8
so when i first charge the customer it would be from 27/8 to 30/9, and then im gonna pause collection for october
and since im not using stripe generated invoice to show the customer so i thought im all good....
and now i faced another problem which is the inconsistent billing date 🤣

[teal plaza]

Ok let me check all of this, is this subscription Id sub_1Lma4oLK0bfo5HSbloWyOkIs reflect this issue ?

[hushed inlet]

yes

[teal plaza]

give me couple of minutes while doing some tests 🙂

[teal plaza]

Probably I'll ask for another opinion on this case

[bleak quail]

this is pretty complicated and beyond the scope of Discord and handing between multiple people, I'd suggest writing into https://support.stripe.com/?contact=true so you can have a single point of contact and we can let you know the results of async investigations

[hushed inlet]

can i have a reference to this issue? a ticket number or something?