A demo ir_sequence record with 'standard' implementation was
assigned to the payment journal so that no concurrency errors arise
from using 'no gap' sequences when attempting to create multiple payments.
In case you want name your invoice YYYY-MM-SEQ (ie: 2022-07-00001)
where:
* YYYY: is the account move year
* MM: is the account move month
* SEQ: is a numerical sequence that is continue along the fiscal year
assuming fiscal year is over two years (ie: from july to june next year)
Before this commit the sequence prefix use now() to be compute but the
range is selected with the account move date.
This commit make consistency computing prefix with the account
move date as well.
So account move manage the first janunary for the last day of
the previous year will properly use the account move date.
Co-authored-by: Alexis de Lattre <alexis.delattre@akretion.com>
