#dennis_de - subscriptions
1 messages ยท Page 1 of 1 (latest)
I would need to update an existing one.
With new ones I can control the behavior with "billing_cycle_anchor" and "proration_behavior".
With new ones I can control the behavior with "billing_cycle_anchor" and "proration_behavior".
For new subscriptions you could also usebackdate_start_date: https://stripe.com/docs/billing/subscriptions/backdating
As far as known, but unfortunately it is about an already existing subscription.
Yes. For existing subscription you could move the next billing cycle by adding a free trial as mentioned here: https://stripe.com/docs/billing/subscriptions/billing-cycle#changing
This wouldn't backdate the subscription, but change the next billing cycle anchor.
Sure. So what exactly would you like to change about this subscription?
The current billing period is 07/10/2022 - 08/10/2022 and the next bill would be on 08/10/2022. I would like to backdate this to 07/01/2022 so that I can still deposit Usage for that month.
I have just no possibility to deposit Metered Usage to 07/02/2022 as an example.
I don't think that's possible. For this you would need to update the backdate_start_date of the subscription, but this can only be set when creating the subscription (and not when you update it).
But the "backdate_start_date" is on 05/01/2022 which is correct. But I understand what you mean....
What do you think would be the best course of action now?
I have just no possibility to deposit Metered Usage to 07/02/2022 as an example.
The simplest option is to add the metered usage to the current billing period.
Okay, retroactive to 07/01/2022 is problematic, got it. What about an adjustment to 08/01/2022? Or also not possible since the current billing period goes to 08/10/2022? So only 09/01/2022 would be possible?
๐ I'm stepping in for my colleague who has to step away
What about an adjustment to 08/01/2022?
since it's within the current billing cycle you can do as much adjustments as you see fit
But not via the dashboard?
the only constraint for you is the timestamp
https://stripe.com/docs/api/usage_records/create#usage_record_create-timestamp
Complete reference documentation for the Stripe API. Includes code snippets and examples for our Python, Java, PHP, Node.js, Go, Ruby, and .NET libraries.
so the usage event shouldn't be in the future
it should be between the start of the cycle and now
I can only reset the cycle but not change it easily.
Or should I "schedule an update" to 08/01/2022 with "reset cycle"?
you want to change the cycle dates? or just the usage within the cycle itself?
I would like to customize this subscription so that it is always calculated on the 1st of the month, so that usage can of course always be recorded from the 1st of the month until the end of the month.
And now the question is how do we get this solved? So either back to 07/01/2022, as I understand that is not possible. Would be the next option in the future 08/01/2022.
I already know the excerpt from the documentary. But that has nothing to do with what I want to achieve? If I do "billing_cycle_anchor=now", I don't achieve the desired effect and the test period doesn't seem to be a solution either?
actually you can do that but on the 1st of August
if you reset the billing cycle anchor on the 1st of August, you would 1- bill the customer on the last period (07/10/2022 -> 07/31/2022) and start a new billing cycle on the 1st that would be recurring on each month accordingly
I see, that's almost what I thought. Can I schedule this as an update via Scheduler?
yes if you already have a scheduler in your infrastructure why not
Or via dashboard?
not via Stripe though
It's German... I know, but can it be that the option ignores the scheduler? The text is irritating.
"Subsequent bills will be set to today's date."
if you're using a scheduler you will have to do it via the API
Complete reference documentation for the Stripe API. Includes code snippets and examples for our Python, Java, PHP, Node.js, Go, Ruby, and .NET libraries.
no I'm not referring to this
honestly it would be an overkill to use subscription schedules just to change the billing cycle anchor
This would have to be executed on 01.08.2022 - correct?
yes
And then it is recognized that the customer had paid until 08/10/2022 and gets that proportionally charged on the new bill?
Is it possible to preview what the effect is via an endpoint?
if you want you can test this using test clocks https://site-admin.stripe.com/docs/billing/testing/test-clocks
you can reproduce the same steps and advance through time to see what the results would be
e.g. set the frozen_time of the test_clock as 07/10/2022
create a customer and add the test_clock id to them
create a subscription (the same one as you have now)
advance in time till August 1st
do the update
and then you would have a full replica of what would happen