geordi-proration-tax | Stripe Developers | Page 1

calm vine Aug 1, 2022, 2:01 PM

#

Hi there 👋 taking a look

cloud sundial Aug 1, 2022, 2:05 PM

#

Thanks!

calm vine Aug 1, 2022, 2:06 PM

#

Can you share the IDs of these invoices? Additionally I'm seeing that there is a verbiage difference in the line between subtotal and total excluding tax, can you tell me a bit more about the steps that were taken which led up to each of these scenarios?

cloud sundial Aug 1, 2022, 2:12 PM

#

Absolutely.

Real:
First invoice on upgrade to higher tier: in_1LQq4LLLAsLlRiDeNz81iW4o

Adding another license on same day:
in_1LQqTNLLAsLlRiDeoJxknRI0

Test Invoice: in_1LRxRhLLAsLlRiDeGnVY9yAN

Sure. In the real case the customer was recently migrated into Stripe on one product, and upgraded to a higher tier product and on the same day added an additional seat to the subscription.

calm vine Aug 1, 2022, 2:24 PM

#

Oh, okay, multiple changes in a single day may make this look a bit confusing, taking a closer look.

cloud sundial Aug 1, 2022, 2:24 PM

#

Great, thank you!

rocky stump Aug 1, 2022, 4:24 PM

#

Sorry about that, didn't realize there was an ongoing thread not actioned, let me have a look

#

Okay so tax isn't "prorated" sadly it's one of the limitations of the API in that case and you would end up with "no tax" on those one-off items unfortunately but there are ways around it. I don't really understand your screenshots since they aren't about proration right?

#

(the Real does but not the Test)

#

you also gave 3 invoices, which one is problematic?

#

cc @cloud sundial

cloud sundial Aug 1, 2022, 4:37 PM

#

Hey thanks! The problematic are the first two - an upgrade plan (first) with additional seat add on (second) - the tax calculation with unused time credited is tricky to understand - if you could help understand the calculation between those invoices

rocky stump Aug 1, 2022, 4:38 PM

#

Okay so the problem is when you invoice the "proration" on its own?

#

like which of the 3 is wrong?

#

because you gave 3 invoice ids, but 2 screenshots

cloud sundial Aug 1, 2022, 4:38 PM

#

The second linked “adding another license”

rocky stump Aug 1, 2022, 4:39 PM

#

perfect let me look

cloud sundial Aug 1, 2022, 4:39 PM

#

Yes the screenshot “real” is the second linked invoice

#

The first was to understand the original upgrade amount/tax 🙂

#

Cheers!

rocky stump Aug 1, 2022, 4:41 PM

#

hmmm I don't really understand that invoice yet, it has absolutely no proration

#

also why are you passing billing_cycle_anchor: 'now'

#

Are you literally updating the quantity from 1 to 2 and backdating it?

#

I don't get why you're doing this, you should 1/ not pass proration_date and 2/ not pass billing_cycle_anchor

#

@cloud sundial

#

Are you still around?

cloud sundial Aug 1, 2022, 5:02 PM

#

Yes I am! The messages are a bit intermittent

rocky stump Aug 1, 2022, 5:03 PM

#

Can you reply to everything I mentioned above? I don't understand what you are trying to do unfortunately

cloud sundial Aug 1, 2022, 5:06 PM

#

This was a recently migrated customer from Braintree to Stripe so some subscription creation settings might be related to the use of the backdating and billing cycle anchor.

#

Are you seeing those incorrect parameters being passed on the subscription update event or on creation?

rocky stump Aug 1, 2022, 5:13 PM

#

I've only focused on that call and I don't understand what you're expecting unfortunately. The way you're making this call doesn't make sense to me, you should not be passing a proration_date in the past and billing_cycle_anchor

#

you should be passing proration_behavior: 'always_invoice'

cloud sundial Aug 1, 2022, 5:15 PM

#

“That call” being the subscription, invoice or other?

rocky stump Aug 1, 2022, 5:17 PM

#

That call being the invoice creation due to the Subscription update call your code is making

#geordi-proration-tax