#nachofranco14-invoices
1 messages · Page 1 of 1 (latest)
Hi @graceful patrol , thanks for helping me out
Hi @pale oasis! Could you clarify where you see this due date exactly? Maybe share a dashboard screenshot or an Invoice ID (in_xxx).
it's a invoice from the test environment
maybe a screenshot?
and I'm referring to the pdf invoice
maybe that wasn't clear enough
Yes a screenshot would be great.
Thanks! Could you also share the Invoice ID (in_xxx)?
Thanks, I'm having a look now.
awesome
Sorry for the delay, I'm still looking at this.
Sorry again for the delay!
Actually there should not be a due date on invoices that have collection_method: charge_automatically. So it looks like a bug. I'll open an investigation internally.
Sorry for the confusion, and thanks for letting us know!
hmm okay but going back to the open questions
and regardless the possible bug
could you please answer me to this?
- where does the Due date comes from?
- how is it calculated?
- is it possible to disable the field?
maybe we could set the payment due date to 0 or 1 days at https://dashboard.stripe.com/settings/billing/invoice
30 days is simply the default value, but it shouldn't matter in this case. And unfortunately there's no way to disable that field.
This setting is only applied to invoices that are sent to customers to be paid manually, so it won't work in your case.
I understand that the due date only applies to manually paid invoices but since it's shown I was just wondering whether the information used was the config I shared with you. For us it wouldn't be a problem to change it to 0 or 1 day if that's the information used to calculate until you fix the bug and hide the field, because we only have charge_automatically as collection method config
I just did some tests, and it seems to work! However I would't recommend that temporary workaround. Instead it's better to wait for Stripe to fix that issue, it should be pretty fast.
thank you
Hey @graceful patrol , is there a place in which I could check the status of the issue?
Unfortunately no, this is only tracked internally.