#mounirmtl

1 messages · Page 1 of 1 (latest)

rugged sonnetBOT
supple coyote
#

Hello! Using pending_invoice_item_interval is useful if you want to bill for pending invoice items more frequently than your subscription renews. So for example - if you had a yearly invoice but wanted to charge for any pending invoice items more often you could use pending_invoice_item_interval

orchid lark
#

I'm sorry I'm not sure I understand.
Why would we have pending invoices more often than the subscription renewal cycle?

#

Unless it's a way to facilitate payment?
For example for a $99 per year subscription we could bill 8.25 every month?

supple coyote
#

Sorry let me give a clearer example - Some folks who do subscription updates choose to set proration_behavior: create_prorations , which generates pending invoices items for the prorations that will be pulled into the next invoice for the subscription. Normally, these will get pulled into the next renewal invoice but if you wanted those to be invoices sooner automatically, you'd use pending_invoice_item_interval.

So if you have a $99/year subcsription that started Jan 1st 2023. If you update it on Mar 1 5to increase the quantity w/ proration_behavior: create_prorations this will generate prorations + pending invoice items. If you don't change anything else about the subscription those prorations will be included on the Jan 1 2024 invoice. But if you were to set pending_invoice_item_interval[interval]: month, then we'd automatically generate a new Invoice that pulls in those prorations on April 1st

rugged sonnetBOT
orchid lark
#

Is there a way to bill the proration on March 15 when the subscription is updated?

supple coyote
#

Yes, you'd do that with proration_behavior: always_invoice which will immediately generate an Invoice to charge for the prorations

orchid lark
#

what's the default behavior?

supple coyote
orchid lark
#

Thanks I'll take a deeper look. I"m not sure I understand the impact very well to be honest

supple coyote
#

Yeah definitely try it out a bit in test mode - you likely don't want pending_invoice_item_interval at all

orchid lark
#

I tend to stick to the default. Unless I have a good reason not too.
But waiting the end of a cycle to bill a proration as default seems weird. At least from what I understand of it

#

For example my carrier would bill me whatever is left on the next bill if I upgrade/downgrade my mobile plan

supple coyote
#

Yeah it really depends on your use case - some integrations that do A LOT of updates all in a row may want to batch all their prorations in a single invoice so create_prorations is a good option for them

orchid lark
#

can we see a preview of a proration invoice?

#

Also, are you saying that ideally it should be the choice of the entity that subscribes to choose whether they'd like to be billed for the proration at the end of the initial cycle vs the next bill?

supple coyote
#

No, really it's your choice (as the company providing the service)

#

If you want to you could give your customer the option to choose, but ultimately it really depends on what you want