#smitit1999-invoice-void-bug

1 messages ยท Page 1 of 1 (latest)

light sapphireBOT
#

Hello! We'll be with you shortly. Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.

atomic schooner
#

Hi, let me help you with this.

#

Yes, that's correct.

sonic tusk
#

Got it, so as per this request - https://dashboard.stripe.com/logs/req_Cuvpn4bCXEEQWl, the subscription's payment collection was paused with behavior set to void on 24th March 2023. However the invoice generated on Feb 1, 2023 was voided due to that. It shouldn't be the case right? in_1MWZa1A5BZ3mzPMys14YrXXk

atomic schooner
#

I see. It might actually affect all open Invoices. Since, the Subscription doesn't control the collection directly, Invoice objects take care of it themselves, and Subscription can only void them to stop the collection. So this might be what the Subscription is actually doing. Let me check.

#

Yes, this seems to be the case. It would be wrong if you paused the collection but the existing Invoice still charged the customer, right?
Sorry, I was wrong in the beginning, since it's an edge case: usually Invoices are created and charged in a short time window, so the situation like this doesn't happen often.

sonic tusk
atomic schooner
sonic tusk
#

This is the request ID - req_NMSmhkjDPCr86v and the invoice ID - in_1NwtTwA5BZ3mzPMyyQk2SXFb respectively

atomic schooner
#

This Invoice was finalized (2023-10-02) before you paused it (2023-10-23), so it is not affected by the pause. Only Invoices in draft state are voided. You will have to void this one yourself.

sonic tusk
#

aah okay, so the invoice in the previous example was in a draft state, which is why it got voided

#

actually, if you see this invoice - in_1MWZa1A5BZ3mzPMys14YrXXk, this was also in an open state. It was finalized on Feb 1, 2023

atomic schooner
#

Yes, I see. It's also weird that it was voided in August, even though the Subscription was paused in March.

#

Sorry for delay, I am still checking what's the expected behavior...

sonic tusk
#

No worries, please take your time and thanks for all your help ๐Ÿ™Œ

light sapphireBOT
charred sage
#

๐Ÿ‘‹ stepping in here

charred sage
#

Okay I think I may see what is happening here. We are attempting to reproduce from our end.

#

Give us a few more minutes.

sonic tusk
#

Thank you

charred sage
#

Alright unfortunately we haven't been able to pinpoint this. To me it seems like a bug -- that Invoice should not have been voided. However, we are not able to reproduce this so it feels like an edge case due to a very specific scenario with the state of that Invoice and the series of events. Have you seen this more than with that one example? Do you happen to have a more recent example (one within the last 30 days)?

light sapphireBOT