only if a fiscal year of same code exists for the same company. The exclusion
must be executed on the basis of the company and not without it.

On call of the 'find' methods of fiscal years and accounting periods, ensure
that only one object is returned.

to specify a keyword argument, which will define the codes of the periods to
create.

a recordset, and not only one record at once.

This would happen when running tests on a DB where ``account_period`` is
already installed.

Follow-up on rev e9cc0fe9ab5f.

obsoleted by accounting date this module adds.

Also update tests in this module to use them instead of creating them anew.

To be reworked.

or an accounting document.
Updated the translations.

Specifics to play better with accounting changes:

* No longer change the base ``date`` field; add ``accounting_date`` instead.
* Build periods when loading accounting data for a new company.

The copy of a transaction_date should be disabled by default.

Updated the translations.
Updated the unit tests.

Note that when the account move date is empty an exception:
constraint null value is raised during execution of action_move_create() method.

Add force_period_on_date context to always make the period be around the current date.

Note that we send a accounting date in reverse_moves func and
the fill_acocunting_date should use it instead of today date.

Remove a "special" field & rename an action.

Updated the translations.
Executed "black" and "isort".

it existed in previous versions

Those fields are similar to old odoo fiscalyear fields
Also added tests

(taken from the related account.move object)