patr0la

[main rover]

Hmm generally speaking having multiple separate subscriptions on a single invoice is not possible with our Billing product

Otherwise you could have multiple items on a single subscription (and thus invoice), but the billing periods and intervals would have to be the same

[strong briar]

I have kind of managed to use SubscriptionSchedule to get this to work..

But I am having multiple issues with generated prorations, canceling and renewing specific SaaS/Module subscriptions.

Do you think that this would be the way to go?

[main rover]

Not sure how it works with a schedule but ok. What specific issues?

[strong briar]

First one is good - that is a free trial ending, but next 2 items are showing a price change even when no price change is happening

Then I am getting complicated invoice

And I can't figure out if this is because minor time difference and prorations or something else
As I can't find exact time by which prorations are calculated at best it gives me a date "after 17 Feb 2024"

[main rover]

You're going to need to share object ID(s) – hard for me to understand anything from that

[strong briar]

https://dashboard.stripe.com/test/subscriptions/sub_1OZtJdG8ueyEKTmSD9wZRPD6

sub_1OZtJdG8ueyEKTmSD9wZRPD6

[main rover]

You'd need to check the API for specific timestamps really

But yes this is likely a consequence of what I described re: the same billing anchor

[strong briar]

Is there an easy way to get changes to line up with billing cycle?

[main rover]

Well that is what is happening on that invoice hence the proration

[strong briar]

hmm, ok

[strong briar]

how about this?

its not a major concern, but would still like to show only real changes for easier debugging

[main rover]

Depends what you define as 'real changes'

(looking at the sub/schedule to try and understand)

[strong briar]

changes that actually affect price. I am getting this "price changed from 3.0 to 3.0"
should I re-use Price Object from previous phase to prevent this from showing?

[main rover]

What I'm seeing seems unexpected looking at the sub_sched_xxxx object:
On Feb 18th the scehdule will transition the sub from these items:

• price_1Obib4G8ueyEKTmSoqorsBcY
• price_1Obib4G8ueyEKTmSkQWtuIiL
• price_1Obib4G8ueyEKTmSSC6JWaSH
  To:
• price_1Obib4G8ueyEKTmSjJ5P3lJ2
• price_1Obib4G8ueyEKTmS5oA904eV
• price_1Obib4G8ueyEKTmS0fimli7S

Note the IDs are all completely different, so you're essentially migrating all the items to new prices which will trigger proration as you're seeing. Not sure if that's your intention or not, but unless they're switching plans you'd re-use the same price_xxx IDs

[strong briar]

Ok ok thank you

I have few more errors, But will create new thread when #dev-help reopens

tnx