Recurring invoices - date fine tuning

[Pongrácz István <..hidden..>]

Hi,

I would like ask about the usage of the recurring invoices (sales invoice).

Do you use this feature? If yes, do you lack any fine tuning?

I ask this, because the recent recurring invoice workflow is not really useful/usable.

Here there are rules, how to fill an invoice, about continuous services: when one issue an invoice, there are several dates with conditions:

• creation date - crdate: the date the invoice created (reference date on the printed invoice)
• transaction date - transdate: this is the date which effects to the tax period
• due date - duedate: this is the payment deadline, when the customer must pay the amount of the invoice

Conditions:

• the transaction date must be creation date + X days (<=15 days)
• the duedate must be equal to transdate

How the recurring logic is working at this moment:

• there is no recurring invoice ID, which determine the recurring record itself, but an id, which is the base of the next invoice number (in fact, it seems it has a bug and not able to set any value to the reference, I will check it)
• when one creates a new recurring invoice, all the three days ar the actual date
• this is not good, because:
  • if I send the invoice immediately by email/regular mail, the customer will get later, 1-2 days
  • if the customer put the invoice into his queue, it takes time to start the paymen
  • the total time could take 1-8 days and this is quite normal, even everything goes smoothly

My proposal to rework the recurring invoice loginc in the following way:

• Using some new fields for adjusting the three dates, at least the transdate and duedate (like how many days must be added to the current date to get transdate and duedate)
• When one save an existing invoice as recurring invoice, there should set up offset days for transdate and duedate (if left empy, no offset will be set)

What do you think?

Cheers,

István