#nukesforbreakfast_sub-schedule-prorations
mossy salmonBOT
👋 Welcome to your new thread!
⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.
⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.
🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1423081458393677914
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.
- nukesforbreakfast_docs, 4 hours ago, 8 messages
- nukesforbreakfast_best-practices, 6 days ago, 12 messages
quaint turret
Hi 👋
Taking a look at the request
The underling Subscription sub_1SDYulB9W1Dc6ymv0qJr6CpZ doesn't have an Invoice associated with it
quaint turret
You are using a non-GA'd API version but I don't think we introduced anything that would cause this...
cold hare
huh?
whatdya mean non-GA'd API version?
clover was released, I was able to upgrade from my dashboard: https://docs.stripe.com/changelog/clover
quaint turret
Oh right, yeah that was yesterday
quaint turret
No I don't think that should be necessary
Hmmm... okay I tried to repro but I got an Invoice created
I was wondering if the days until due might have something to do with it but that wasn't it.
cold hare
I had it happen twice in a row.
Is it something to do with a freshly created Connected account perhaps?
quaint turret
Oh, I noticed you are specifying a timestamp for start_date
cold hare
yes, but I tried this before with that same setup and it was creating invoices.
so IDK why it isn't today.
quaint turret
1st - can you try without providing the start date? It looks like it's pretty much the current time so the default "now" will get the same result
I am wondering if the proration_behavior: "none" + a start date is causing the Subscription to not charge for the first year
2nd - can you share a working API request ID?
cold hare
do you think it's a specific thing with the date being October 1?
because last time I tried this was middle through end of september, which backdated to September 1`
and those all created invoices.
give me a second to re run the test
quaint turret
I think the problem is that you are starting the Subscripton 10 seconds in the past, which would normally generate prorations for the first phase but you have proration_behavior: "none" so we aren't.
- Timestamp on the API request:
2025-10-01 22:54:26 - What your
start_datemaps to:2025-10-01 22:54:16
cold hare
yeah, the behavior I'm trying to achieve is to force align the subscription to the start of the month, so I can align the pending invoice items cycle to the start of the month.
quaint turret
In that case it would make more sense to create the Subscription Schedule in the previous month with a future start date so you don't run into this situation.
The prorated amount would be almost the entire unit_amount but we calculate prorations down to the second so even if your start date is 1s in the past, we consider that a proration.
If you tell us not generate the prorations, we won't charge the customer
cold hare
Sometimes I need an invoice to be billed for immediately depending on if a end user created the object in our DB that generates the subscription, or not if an admin created said object. I'm guessing setting the start date in the future would also not immediately generate an invoice.
Unfortunately something is wrong with my code and it's not allowing me to change the date as I expected. I need to debug some more, but I have to step away to handle something else. I'll re-open a thread based on what I find if I come back and this one is locked.
quaint turret
Okay sounds good. I recommend either allowing prorations (if you need to bill with a backdated start date) or use the start_date: "now"
mossy salmonBOT