#NoahBundeling-invoices
covert jetty
Would be great if it's possible!
old nacelle
I didn't quite get the whole scenario
let me try to summarize, please correct me if I'm wrong
so you start a subscription with plugin A, and in the middle of the cycle you want to switch to plugin B
and remove plugin A and you want the user to be charged for each plugin the time that they used
old nacelle
but you don't want to generate a new invoice mid-cycle?
covert jetty
Another scenario:
Client gets a subscription for the main product and adds (during the month) plugins A and B. Client receives a separate invoice for that which says (i.e.):
'Remaining time on plugin A after 4 August'
'Remaining time on plugin B after 4 August'.
First of all, is there any possibility to make this just:
'Plugin A'
'Plugin B'?
Next, if you for example change the quantity, you'll receive another invoice which says:
'Remaining time on 3x plugin A'
'Remaining time on 3x plugin B'
'Unused time on 4x plugin A'
'Unused time on 4x plugin B'
Is there a way to short that?
And I don't want to change the billing cycle.
old nacelle
and you want that to be postpaid right?
I don't think the template you are waiting for is doable in Stripe
we have a fixed template
what I'm trying to figure out is whether it's possible to model your scenario using Stripe Subscription but in all cases you'd have to generate your own invoice using your template
covert jetty
I want to invoice the client immediately after they make the change.
And then for the rest of the month, I suppose yeah. But only like the difference amount.
old nacelle
proration_behavior : always_invoice would do it for you but I'm talking about this format
'Remaining time on 3x plugin A'
'Remaining time on 3x plugin B'
'Unused time on 4x plugin A'
'Unused time on 4x plugin B'
it would be easier if you try to test this
so the best way of doing that is to use test clocks https://stripe.com/docs/billing/testing/test-clocks
you'd create a subscription and try your different scenarios and advance the clock accordingly
and you could see the results by yourself
this is also a guide for changing the price mid-cycle
exotic ferry
Hia, Sorry for the bother.

We’re basically trying to set up the following billing structure, Which we’ve got working except for the problems with the weird invoices.
- Customer create their account and adds their plugins & users
- After a couple hours, these changes are gathered up and billed to the customer

3. Changes afterwards repeat the same process of being gathered up and billed after couple hours.
This allows the customer to add users & plugins without A invoice being generated for every change but still require them to pay for the changes quickly after making them.


I think the confusion here lies that we want it to work prepaid not postpaid?
old nacelle
@exotic ferry please send your message on the main channel
covert jetty
It's my colleague. That's why he attended.
old nacelle
Oh my bad
exotic ferry
yeah, sorry should've clarified
old nacelle
what I'm not following is how would it work prepaid if you don't want to invoice the user upon change?
exotic ferry
Well not instantly, we collect changes over a few hours and then try to bill those all at once
for example if you add a user and then delete them, it'd be a waste to generate 2 invoices for that
old nacelle
If you want to charge for an upgrade immediately, pass proration_behavior as always_invoice to create prorations, automatically invoice the customer for those proration adjustments, and attempt to collect payment. If you pass create_prorations, the prorations are created but not automatically invoiced. If you want to bill the customer for the prorations before the subscription's renewal date, you need to manually invoice the customer or use pending_invoice_item_interval.
from https://stripe.com/docs/api/subscriptions/update
exotic ferry
If we set pending_invoice_item_interval on the subscription it will automatically generate the invoice for non-billed changes every defined time?
Would this make seperate items every time the count changes or consolidate it into a single change?
For example:
- 1 user gets added at 1pm and another at 3pm
Will it show up as 1 line on a invoice the next day?
old nacelle
we prorate per day if I'm not mistaken
I stand corrected, it's accurate to the second
then yes what you can do is update the subscription each time there's a change and pass proration_behavior as create_prorations
and you can set the pending_invoice_item_interval to a day
which means that the next day the customer will get billed the changes that happened on the eve
exotic ferry
Alright, that sounds promising!
We'll have to go try that out real quick.
old nacelle
yes, and as mentioned before feel free to use test clocks, that would help tons with the testing
manic moss
Hey, taking over here. Let me know if there's any follow-up Qs I can answer!
exotic ferry
Alright, so if we update the quantity multiple times in a day it looks like it still gonna do this mess.
In this example I changed the quantities like this:
5 > 4 > 6
We want to squash this into something that's easier to read since they all happen on the same day.
and just display 2 lines
5x old amount (unused time in cycle)
6x new amount (remaining time in cycle)
manic moss
Let me check on something
So we do have a setting that will unify proration items into 1. So in your example you'd go from 4 line items, to 2
exotic ferry
that'd be perfect
manic moss
Cool! You'd need to speak to support specifically to have that enabled (I can't do it unfortunately)
Just mention that you're interested in unifying proration line items
exotic ferry
Just start a chat?
manic moss
Yep
manic moss
Any specific topic?
Don't know the topics off the top of my head, anything integration/API related
manic moss
And are there costs ascociated with that?
With?
exotic ferry
enabling that setting
manic moss
Nope! It's just a flag that we enable on a per account basis
exotic ferry
coolio, thanks i'll go start a chat.