#Nukesforbreakfast
1 messages · Page 1 of 1 (latest)
Hello! I think you want invoice.updated: https://stripe.com/docs/api/events/types#event_types-invoice.updated
Let me see.
Actually, now I'm not 100% certain that Event will fire when the Invoice becomes overdue. Let me check...
I was going to ask what field would indicate overdue. There's no "overdue" status.
Yep, you're right. The Invoice itself doesn't change when it becomes overdue. There is no Event that fires when that happens.
Hmmm
So is there a best practice for handling overdue invoices? I was hoping to be able to listen for an event and start triggering other workflows when that happened.
Using an automated subscription doesn't work for my case, so it was going to be manual invoices with "send invoice"
The best idea I can come up with is to cache the due date of an Invoice in your database and then trigger your workflows based on when that due date comes through.
Alternatively, you could listen for invoice.upcoming and webhooks and then schedule a check on the Invoice to see if it is paid by the date given in the event
Damn. I was hoping to be able to use stripe as the source of truth. If I have to set up timers to handle the due date, there's now a bunch of logic I have to write to handle when the invoice is paid or voided to ensure the timer is cancelled etc.
Does invoice.upcoming fire for invoices that are not driven by subscriptions?
Ah, I don't think it does unfortunately
Ok. I guess consider this a feature request to add a webhook event for when an invoice becomes overdue. And probably adding an overdue status, but I could be convinced to just use the due date attribute.
Are you just using Invoices? Or are you using Subscriptions too?
For the use case where I need the overdue events, it would just be invoices. I have a fine schedule that is graduated for X events in Y time where Y is generally a 365 day rotating period. Meaning if an event happens, I need to look back 365 days and count the number of events to index into the right fine amount. I checked some time ago and the Stripe usage based pricing tools can't model this, so I'll be creating invoices without subscriptions.
If I could use the subscription model, I bet there's some other event that would work.
Ahhh okay. We already submitted the feature request for the overdue event, though I'll add one to have something like status=past_due on Invoices
Yeah, the status could be optional since one could check the due date attribute. But the status change might be required if the implementation is to trigger a invoice.updated rather than have an entirely new event type.
Is there somewhere I can watch for status updates on feature requests like this? This one is actually a big one for me. It would save me a lot of work.
If you write into support and mention that you talked to us and need updates on a feature request, we can try to send them out, though this feature request has actually existed for a very long time (~2019) and we bump it every couple of months (including today where we referenced this thread), but it hasn't been selected for development yet. So I wouldn't hinge anything on it being created anytime soon
Is there a backlog item number or something I can give support to help them easily identify it?
Yeah, you can reference FEEDBACK-1380
Thanks for the help and the insight into how long this has been a feature request.
I've similarly asked before for a feature to be able to further customize the invoice PDF. We have cases where we have to mail a copy certified before we can send an overdue account to collections, for example. However, the existing invoice PDF doesn't work with normal window envelopes and we have to insert an additional page for the address manually. Is there a feedback ID you can find for that feature request as well?
The use case is moving the address blocks around on the page. Where the to address is right now doesn't line up in a window envelope when printed and folded.
Here is the other one you can reference FEEDBACK-24528 for the customizable Invoice pDFs