#iglutv_subscription-billingcycle
meager cosmosBOT
š 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/1303829146878742668
š 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.
- iglutv_code, 4 hours ago, 5 messages
lime widget
Backdate start date is the only way that I am aware of. Looking at the invoice that was created that way.
When testing myself now, the invoice does appear to list previous time periods with its invoice items
lime palm
Right, I would like to display a single item that starts on Nov 1st and ends on Nov 30th, without prorating, just a full month. Even though I create this on the 6th.
Also, I'm sending dates at 12 AM GTM, and it's doing it the day before in many cases, is there a trick to accurately create on that day? like +5 hours
lime widget
Interesting, that is what I am seeing when I specify a billing cycle anchor that is a month away from the backdated start date
Looking at your request again
lime palm
the invoice field that finance updates for backdating is Supply Date
couldn't figure how to access that upon subscription creation either
lime widget
the invoice field that finance updates for backdating is Supply Date
Not quite following what you are saying there. Can you explain this a bit more?
Ah I gotcha, unfortunately I am not seeing a way to set both of these properly through the dashboard either. I think this would have to be a feautre request
lime palm
Interesting, that is what I am seeing when I specify a billing cycle anchor that...
so this was achieved via a future billing cycle? a month from the start date?
lime widget
For that invoice I passed backdate_start_date=1730492340 and billing_cycle_anchor=1733087940. I do see that on the one subscription that you created you passed similar timestamps, still trying to figure out what the difference was
Actually when passing the same timestamps for the request ID you provided, I am seeing the same behavior where there is only one non-proration invoice item
Can you try again and let me know if you see something different?
lime palm
let me try again
meager cosmosBOT
gentle basalt
iglutv_subscription-billingcycle
lime palm
I see this upcoming invoice:
gentle basalt
Okay so can you share the exact Subscription id, the exact code, and clearly explaining what you expected that didn't happen?
lime palm
this is the subscription id sub_0QIHFgsSlifq3EcceSzQ9iPq
this is the code
{
"backdate_start_date": "1730419200",
"billing_cycle_anchor": "1733011200",
"customer": "cus_QNUHc8W9RK5rbR",
"items": {
"0": {
"price": "price_0QIHFfsSlifq3EccSRzRfmVg",
"quantity": "9"
}
},
"metadata": {
"SFDC Opportunity ID": "006U900000BeKEeIAN",
"organization_id": "TEST_FULCRUM_ID"
},
"payment_behavior": "default_incomplete",
"proration_behavior": "none"
}
I would like this to create a subscription that starts on Nov 1st 2024 and ends on Nov 30, and that gets billed on Nov 1st 2024
gentle basalt
Okay but Nov 1st was in the past right? So you want their first Invoice to charge for the full month of November, is that correct?
lime palm
yes
and then the invoice to match the start date, meaning following invoices will fall on the 1st, not the 6th
gentle basalt
Okay so what's the problem?
lime palm
I cannot backdate an invoice
and the dates on the subscription display starting a day before
gentle basalt
That is just impossible to fix. We don't backdate the Invoice so you can't fix it. I get your ask and I think it could make sense, but the Invoice was issued on November 6 and paid on November 6.
And for "a day before" that's not what's happening. You set December 1st 00:00:00 UTC as the billing_cycle_anchor so the Subscription's first Invoice is November 1st - November 30 right?
Like if you set billing_cycle_anchor to later in the day on Dec 1st what do you see?
lime palm
and how can I fix this? I want at least the subscription accurate
I think I have issues with UTC dates
gentle basalt
My guess is that you are using a different timezone in the Dashboard. You passed backdate_start_date: 1730419200 which is 2024-11-01 00:00:00 UTC. If you are based in the US that date is October 31st.
lime palm
so should I send 5 hours before I guess
lime palm
My guess is that you are using a different timezone in the Dashboard. You passed...
anyhow if I passed Oct 31, why it says Current Period starts on the 6th? where that date comes from?
gentle basalt
that's just the way backdate_start_date works. It basically does "past to now" + "now to billing_cycle_anchor"
I get what you want to do, it's just not possible
lime palm
ok, thanks for confirming that
is there any workaround like putting a trial_end in the past?
gentle basalt
no
lime palm
and what does the proration_behavior = none ? my intention was to avoid the calculation of prorated days between the 1 and the 6, but I'm not sure that's what is meant for
gentle basalt
I mean you do absolutely want the Nov 1-6 to be paid for right? You said you didn't but you seem to want to
It's a parameter that lets you tell us "don't prorate anything" so you could for example start a Subscription now, anchored to Dec 1st but nor charge anything, for example because you charge them on another processor before migrating to Stripe
lime palm
I want it to be paid, but I didn't want the proration item in the invoice, that was why
gentle basalt
Gotcha
lime palm
so, is it better if I get rid of the proration_behavior = none? I guess I must tell the business to invoice manually and just aim to provide accurate subscription dates, that's as far as I can go
else the billing date will be defined by the date the event is sent, always on today
gentle basalt
I don't really have a good answer for you. I think you need to decide what you really want to do here. But my read is you want to have the proration and it will reflect the relevant dates even if they are not matching exactly what you wanted and it will charge the end customer the proper amount
I hear you though. I have pushed for something like this for years. You don't want a proration for Nov1 - Nov6 and then Nov 6 - Dec 6. You want to make everything look as if that Subscription was created on Nov 1st and renewed on the 1st every month. We just don't support this š¦
lime palm
I'm glad you hear me, I don't think the business is asking for crazy things. Specially given that they can achieve this manually through the UI. I'm working with them on an integration to avoid manual work, and it seems that it won't be feasible, just halfway through.
So with realistic expectations I would try to get at least the subscription dates accurate. I think I got close and I have to adjust the UTC stuff.
Is there any page you can vote for future enhancements? š„²