We would like to use it to create invoices for VAT purposes for payments made on credit card - so dates have to do with tax periods and historical records.

It seems that the current date is always used - rather than allowing the user to enter a date and then let the system work out whether any recurrent invoices are due. Furthermore the current date is used as the invoiced date - so one can't set the date to the taxpoint (e.g. for invoices relating to subscriptions).

More seriously if say a monthly recurrent invoice set was last created in January - and it is end March when the user next operates the functionality the system deduces that the recurrent invoices are overdue - but will only create 1 set ( dated March ) before saying that no invoices are due.

I believe the system should work along the following lines:
Enter taxpoint date...
Work out whether recurrent invoices are due - and if so how many sets according to the frequency set.
Use the day of the month set with the appropriate month to calculate the date for the invoices in each set.
Loop until the number of sets required have been created.

What do people think ?

Thanks in anticipation....

Vernon