For now, there is a single active check box which is only usable if no moves have ever been made on this account or its children.
But some countries (like Germany) have a highly evolving charts for almost every fiscal year. The 'active' field is not good enough as account should deactivated from a specific fiscal year.
Here is my proposal:
- Add a from/to date on the account (and template) (and enforce on children)
- Add a function field that convert the dates into valid fiscal years
- Enforce move creation inside the dates/fiscal year
- Compute active field using the dates/fiscal year/periods from the context
- Ensure that date/fiscal year/period are set in the search context for all document storing account
- Add a forward account field on account that have an end date. The property "account*used" must follow such forward until a valid account for the date is found.
The same design should be added also on the tax code and line (but not the forward).
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Child items
0
Show closed items
No child items are currently assigned. Use child items to break down this issue into smaller parts.
Linked items
0
Link issues together to show that they're related.
Learn more.
Here is review58301002
It does not yet contain the "forward" feature because I'm not yet sure about the design. Having reference to other account on the account will complicate a lot the template creation/synchronization. So I'm thinking of using a different Model to store this information which will be synchronized after. This design will also allow to make more complex replacement rules (a little bit like the tax rules).
Indeed I found that I could reuse the update_account_taxes which is a second update loop to synchronize the "forward" field. So I will go this way because it will be simpler to understand for the user.