spencersr - back-dated subscription | Stripe Developers | Page 1

minor kestrel Mar 15, 2022, 11:45 PM

#

shell marsh Mar 15, 2022, 11:46 PM

#

If we attempt to set the subscription anchor to the start date (same date as Jan 15th 2022) it will attempt to do some prorations we aren't entirely sure of as seen from today.

minor kestrel Mar 15, 2022, 11:48 PM

#

I would think a subscription that started in the past and was anchored in the future would be pretty strange. Let me take a look

#

So the attempt is to avoid proration?

shell marsh Mar 15, 2022, 11:50 PM

#

Hah yeh.. it is. I've got a feeling we should just build out invoices for annual subscriptions for the current year that have already started and set up future subscriptions for these clients we are migrating into stripe.

#

Yeh.. I'm happy to share a screen and discuss. Won't be free for a few hours however.

minor kestrel Mar 15, 2022, 11:51 PM

#

Yeah we aren't set up to handle that, just a basic chat server for now.

shell marsh Mar 15, 2022, 11:52 PM

#

I haven't taken the time to attempt to figure out the math involved with the total we are seeing quite yet.

minor kestrel Mar 15, 2022, 11:52 PM

#

This would probably be too easy but you haven't tried just disabling prorations, have you?
https://stripe.com/docs/billing/subscriptions/prorations#disable-prorations

shell marsh Mar 15, 2022, 11:55 PM

#

I can test it. We actually have some other products that require that feature - but I have a sandbox that I can use to check this out. This is one of the reasons I wanted to use two different stripe accounts for our product 😉

minor kestrel Mar 15, 2022, 11:56 PM

#

Sandbox environments are definitely recommended! Between all the options and products offered, you can build some pretty intricate workflows that can only be verified by testing.

#

Also are you using test clocks to verify future subscription behavior? It's a pretty new feature.

#

https://stripe.com/docs/billing/testing/test-clocks

#spencersr - back-dated subscription