The current Generate Vendor Recurring Invoices process in Dynamics 365 Finance requires users to provide both a Generation Date and an Invoice Date when running the batch job. In practice, the Invoice Date is almost always expected to be the same as the Generation Date, making the additional field redundant. Requiring users to manually enter an Invoice Date increases the risk of errors, creates unnecessary maintenance, and complicates what should be a highly automated process. The system should automatically default the Invoice Date to the Generation Date and either make the field optional or remove it altogether from the batch dialog.

In addition, the current design requires users to actively schedule and manage the generation process, even though recurring invoices already contain the information needed to determine when the next invoice should be created. Ideally, the batch job should only require selection of the relevant template, if filtering is needed, and then automatically identify all recurring invoice records whose Next Generation Date is due on the current processing date. The process should generate invoices for all eligible records and automatically advance the next generation date based on the configured recurrence pattern. This would allow organizations to run a truly unattended recurring batch process without needing to specify dates each time.

Another challenge is that invoices created through the recurring invoice framework do not seamlessly integrate with Invoice Automation. Organizations that have invested in automated vendor invoice processing expect recurring invoices to follow the same downstream automation path as other vendor invoices. Currently, the generated invoices often require additional manual intervention, reducing the value of automation. The solution should either provide an option to automatically submit generated recurring invoices to Invoice Automation and any associated workflow processes, or clearly separate recurring invoices from the vendor invoice workflow paradigm if that is the intended design.

Overall, the recurring invoice feature would be significantly more effective if it functioned as a true recurring engine: running on a scheduled basis, automatically identifying due invoices based on their next generation date, defaulting invoice dates appropriately, updating future generation dates, and integrating seamlessly with Invoice Automation. This would reduce manual effort, eliminate user confusion, improve data consistency, and deliver the level of automation that organizations expect from a recurring invoicing solution.