I have the problem that when I schedule a recurring invoice that is not due to start until 2026, I have to create a real invoice that exists alongside the recurring invoice.
So I have the normal invoice as a draft (which always remains a draft and will no longer be billed in 2025) and the recurring invoice, which does not start until 2026.
The problem is that I cannot delete the draft invoice (even though I no longer need it) because then I automatically delete the recurring invoice.
My suggestion would be (similar to InvoiceNinja) to simply allow recurring invoices to be created as individual separate invoices. This means I can create a recurring invoice individually (which, for example, only starts in 2026) without having to create a normal invoice first. Then I only have the recurring invoice listed as a “draft” and when it starts in 2026, the recurring invoice creates a normal invoice which can then be paid.
We won’t change anything until version 2 of InvoicePlane is tackled.
With InvoicePlane v2 we’ll re-think the recurring invoices thing, but until then you’re stuck with what we have.
How about creating a draft invoice and complete it when you want to make it recurring? Will that help?
Yep, this will help. It was my hope that we can adjust that to a lil bit comfortable solution. But I will create alerts to create invoices and following recurring invoices.
There are 2 issues and they seem to be similar.
Of you want you can focus on that issue (number 52 in the InvoicePlane V2 project)
Add especially the context, just like if it was an issue using a Template.
If number 52 is too cluttered, grab that gray issue (draft) and make it your own.
Convert it to a real issue and add things you want in V2 for Recurring Invoices
