#jeff-sexton_invoices-delayed-finalization
stable tulipBOT
👋 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/1486804118163951759
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
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.
- jeff-sexton_unexpected, 15 hours ago, 40 messages
grave zinc
Hi 👋
Do you have an example of an Invoice that had a delay of 3 days (72 hours) before finalizing?
marble solstice
See any (and every) draft invoice in https://dashboard.stripe.com/acct_1Cf8ReCx65IjJG44/invoices
grave zinc
That's a dashboard link and useless to me, since it's not my dashboard. Please provide a specific Invoice ID
grave zinc
Aha! Great. Looking now
This invoice was created today. I asked for an example of one that took 3 days before it transitioned from draft to open status
marble solstice
FYI, I opened a Stripe Support case at the end of yesterdays issue to get a follow up. Saniya from Stripe support has the case and I've emailed them that the issue re-occured.
Yes. All invoices that are being created today are being set with a "automatically_finalizes_at": value that is 3 days in the future despite the fact that our API call is 1) not setting that value at all and 2) this account is configured for a 1 hour invoice grace period
,
The problem is that these draft invoices will not automatically charge for 3 days instead of 1 hour as expected.
Our support team can manually finalize and charge these invoices but we're talking having to manually action thousands of invoices because Stripe is not behaving as we expect and have it configured.
grave zinc
So you don't have an example of an Invoice ID where the invoice waited 3 days to finalize?
marble solstice
No. but these invoice are waiting for longer than 1 hour. which they shouldn't be
grave zinc
I can see what you mean in this event: https://dashboard.stripe.com/acct_1Cf8ReCx65IjJG44/events/evt_1TFJISCx65IjJG44vZkOveb3
I'm just looking for as much data as I can gather
marble solstice
No problem! Of course
Here's an example of an invoice that was created over an hour ago but is not scheduled to finalize and charge for 3 days. https://dashboard.stripe.com/acct_1Cf8ReCx65IjJG44/invoices/in_1TFI9eCx65IjJG44oqxO5taE
We should already have collected payment for this invoice but will not do so for days unless we manually intervene
stable tulipBOT
winged fjord
Hi there, taking over for @grave zinc as they had to step away. I'll need a moment to get caught up on the context of this thread. I believe you mentioned that you opened a case yesterday - do you have a reference number to that case?
marble solstice
I was not given a case number. I only received this email response.
winged fjord
Got it, I should be able to look it up with your account ID. It sounds like from the previous thread that there may have been an issue on Stripe's side that was resolved, but now it appears not completely. I'll look for any similar reports or incidents on our side to start with
marble solstice
Perfect. Thank you!
winged fjord
My understanding on this issue is that when an invoice is first created, it is set to finalize 3 days in the future. Once the invoice.created webhook event is delivered to all endpoints, we update it to finalize in 1 hour. From what I can see, your webhooks are functioning properly, so it looks like there's something wrong with the update on our end.
I did find the case you filed, and there I see we filed an ticket for an internal investigation with the team that owns this feature which is open. I'll try and do some more digging myself, but your best bet may be to wait for the updates from the investigation in your case
It would be helpful if you respond to the case with the context of this thread to make sure they know it's still an issue
marble solstice
I did respond to the email right away that the issue is happening again but I will also add a link to this thread.
winged fjord
Ah yes, I see your response
grave zinc
Hi 👋
I just wanted to reiterate what my colleague stated that this issue will be followed up on internally and we will get back to you through the email. I realize the delay can be frustrating but this requires more internal investigation that we can offer here.
marble solstice
Ok. Thanks for confirming