Implemented
0
Recurring invoice next_send_date is incorrect across DST boundaries
Source: invoiceninja/invoiceninja#12158 · opened by @nbolender
<!-- Before posting please check our "Troubleshooting" category in the docs: --> Setup • Version: v5.13.26 • Environment: ZIP / CLI / LAravel Forge Checklist • Can you replicate the issue on our v5 demo site or Yes • Have you searched existing issues? Yes • Have you reported this to Slack/forum before posting? No • Have you inspected the logs in storage/logs/laravel.log for any errors? Yes Describe the bug When a company or client is set to a timezone that observes daylight savings time, recurring invoices may receive the incorrect send time. For example, if a company is set to America/New_York, and the email send time is set to 6am, upon sending a quarterly recurring invoice on August 5, 2026 6am, Invoice Ninja will update the next send time to be November 5, 2026 5am. This is because timezone_offset() for both company and client only returns the offset for the current date, not the next send date in question. Steps To Repr…
No pledges yet. Be the first to back this.
Comments
Similar requests
Enable recurring invoices/expenses auto-updates based on composing entities (group, client, product, tax, etc.) settings
0 votes · 0 comments
Feature Request: Mass-edit (or import possibility) of recurring invoices
0 votes · 0 comments
Recurring invoice, email now, like in v4
0 votes · 0 comments
About Recurring Invoice status
0 votes · 0 comments
Import invoices with several items into InvoiceNinja
0 votes · 0 comments
No comments yet.