There are some scenarios, where the users are creating the invoice proposals, but they only post them a few days later. In that case, the invoice journal invoice date gets the invoice proposal creation date (invoicing date on the invoice proposal) as invoicing date. This is incorrect, because the actual invoicing to the customer happened a few days later. This is affecting due date calculatation as well. Let's say there is an invoice proposal created on 2021.08.31, it has a terms of payment, that calculates due date for the 4th of next month. In that scenario if the invoice proposal is posted on 2021.09.05. for example, the invoice date on the invoice will be 2021.08.31 and the due date is 2021.09.04. Therefore customers may receive invoices where the due date is already passed. If the invoice date on the invoice would be the current system date, then the due date would be 2021.10.04 in that scenario.
There are workarounds for this, but none of them are the most efficient:
Workaround 1: Delete invoice proposal on the date of actual invoicing, recreate the invoice proposal, and post it on the same date -> this generates double work for the users
Workaround 2: Change the invoicing date on the post invoice proposal form -> this could work, however when recurring batch jobs are used to post the invoice proposals, this cannot be modified.