#eman8519-billing
1 messages · Page 1 of 1 (latest)
Hi
are you a software developer who built the integration?
Yes...me and my team did. I'm the Head of Engineering for my company.
We have customers on annual plans being billed monthly
mind sharing the Subscription ID and monthly Invoices (just 1 or 2 are fine)
and I can have a look
Here is one: si_LABxVp2536NbVy
Their customerID is: cus_KUAkFNQqx16ky8
You'll notice that their next invoice should be Feb 26th of 2023, but they recieved this invoice on March 26th:
in_1KhZvXCTlW8ESIfRZnnNNUoY
This could very well be related to a price increase that we did in February, but I can't figure out how/why nor how to correct the behavior. I can give you more details if that helps, just let me know I appreciate you taking the time to look.
what you shared is sufficient! looking
Hi there! Taking over here since @scarlet trout has to step away. Give me a moment to catch up
Looks like the pending_invoice_item_interval is set to monthly which is generating the invoices.
Hi @final swift thank you.
You can see it was set on Sub creation here: req_pF5AgKLsmb1Tj3
Info on that param: https://stripe.com/docs/api/subscriptions/create#create_subscription-pending_invoice_item_interval
Complete reference documentation for the Stripe API. Includes code snippets and examples for our Python, Java, PHP, Node.js, Go, Ruby, and .NET libraries.
I'm not sure how that happened. This could be affecting several of our customers. What is the best way you would recommend reconciling that?
All we were trying to accomplish was updating our pricing which meant generating new plans etc.
Looks like that Subscription was created via the API so you will want to check your integration for why that was set.
You likely either want to recreate the Subs or update that interval to yearly
I think what initially happen is our production Annual plan got configured with a monthly cycle, and we went back to reconcile that by creating yet another plan with the proper configuration. We updated all the annual users effected and put their billing_anchor into the future to prevent billing them out of cycle due to the update.
Do you guys have any technical solutions architects that we could interface with to help clean this up with us? The biggest fear I have is that all the steps we've taken so far have resulted in something not quite being right resulting in customers being billed improperly.
I've researched and researched how to correct this, but still we have this issue remaining.
My recommendation would be to contact our Support team (https://support.stripe.com/contact/login) with full details about what you have done so far and what you want to accomplish. You can mention that you talked to us on discord as well. That will help route you to my team. Then someone can take the proper time to look into the situation fully and help guide you to the best resolution/setup.
Great. Thank you @final swift I appreciate your help.