#knolleary_best-practices
lavish coralBOT
đ Welcome to your new thread!
â˛ď¸ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.
âąď¸ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.
đ This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1364238103916843018
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
sonic briar
Looking for tips on how to manage a combined monthly/yearly subscription(s)
Can you share more about how monthly/yearly comes into play here? Are these add-ons not also billed annually?
brittle zephyr
@sonic briar with our current model, a user can add/remove additional Things from their team. A user may add/remove Things multiple times a week. When they do, we update the quantity of a corresponding item on their subscription. Effectively, its usage-based pricing without using the metered billing feature. With monthly billing, they get invoiced at the end of the month based on their usage. With the shift to annual for the base team subscription, I'm trying to work out how we can handle these addition items being added/removed through the week.
lavish coralBOT
jagged schooner
Hello, my colleague has to step out but I can help. Have you considered billing immediately when adding the yearly add ons?
brittle zephyr
As in trigger an invoice for any pending item?
jagged schooner
Can you tell me what you mean by pending item here? Do you not consider the item to be part of the subscription until after it has been paid or something else?
brittle zephyr
Was using the term from the stripe docs here: https://docs.stripe.com/billing/invoices/subscription#pending-items-frequently
jagged schooner
Ah gotcha, apologies I was unaware of that specific functionality but I do think that that can offer a good solution for you here. When you make your subscription update you can pass us the proration behavior create_prorations which will tell us to calculate prorations and create invoice items for them, but to not actually create an invoice and charge for them yet
So if you also set that interval, you can have us charge for any outstanding prorations at a monthly interval or something similar
brittle zephyr
ok - I hadn't seen the pending_invoice_item_interval property before (or read it properly)