anthonyg-schedules-backdate | Stripe Developers | Page 1

sturdy venture Nov 2, 2021, 10:27 PM

#

Is there a way to get this to display differently so that it's clear to customers that this is a back dated bill for the previous period
No you can't control further what appears on the invoice. Does it behave differently from what Subscriptions do today? Can you test quickly?

elfin laurel Nov 2, 2021, 10:32 PM

#

Hmm, I don't have anything setup to create a subscription instead of a schedule.

sturdy venture Nov 2, 2021, 10:33 PM

#

should only take a few minutes in code to do the same thing with subs and backdate_start_date right?

elfin laurel Nov 2, 2021, 10:33 PM

#

Yeah, not too much work.

sturdy venture Nov 2, 2021, 10:35 PM

#

once you do, if you can share the 2 invoice ids I can look at each one. Either it's consistent (and then just confusing) or it's not (and then it's likely a bug)

elfin laurel Nov 2, 2021, 11:05 PM

#

It's not quite a 1 to 1 comparison as you don't really set the billing cycle anchor in the same way. With schedules it's either phase_start or automatic and with subs it's just a date. So when I set the sub billing_anchor to the same date as the second phase start of the schedule it doesn't produce a first paid invoice for the period from the start date. The api docs say that sub billing cycle anchor dates set the date of the first full invoice, and since I'm setting proration to none then maybe that's why it's not running a first initial invoice, but waiting until the later anchor date? Here are the sub ids, first one is from the one created with the schedule and the other is just straight sub setup:
sub_1JrVJwK4OwuAC0l7IrzmbOKY
sub_1JrVz1K4OwuAC0l7uMHwz4Bv

sturdy venture Nov 2, 2021, 11:11 PM

#

but did you use backdate_start_date on subscription creation?

elfin laurel Nov 2, 2021, 11:12 PM

#

Yes

#

So it says started on Oct 3

sturdy venture Nov 2, 2021, 11:12 PM

#

ack let me have a look (channel got busy again but looking)

#

Okay so both invoices behave the same in that case and treat the "now" (sub/schedule creation) as the beginning of the period, even if you backdate which is expected behaviour in the way it's designed, but not expected behaviour in the way people hope/expect it to work 😦

#

My understanding is that if you also use billing_cycle_anchor and keep proration enabled, it'd do the right thing for you automatically for Subs, but not for schedules

#

I can't think of a way to do this at this point unfortunately I'm sorry

#anthonyg-schedules-backdate