Some country has a balance sheet for which the type of account change depending on the balance sign.
I think the best is to add a second type Many2One on account that will be used for negative balance. This new field can stay empty to have the same behavior than now.
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Child items
...
Show closed items
Linked items
0
Link issues together to show that they're related.
Learn more.
I'm curious as to whether the 'type' should not simply limited to:
- Balance sheet accounts
- Profit and loss accounts
and perhaps
- Special Accounts
Individual accounting plans can then break these types down
into classes for their particular account heirarchy (whether
developed or simplified)
Perhaps it is best left to the various reports to be able to
then select the accounts into the various sections and eventually
detailed by specific account balance criteria such as:
* debitor balance (only take if balance is debitor)
* creditor balance (" " creditor)
* both debitor or creditor (which is probably the general case)
there may be need for some reports to access as well:
* debit moves (only take the sum of the debit moves)
* credit moves (" " credit moves)
this is because the 'type' doesn't change, at least not without
perhaps somewhat radical consequences.
risto42added 1 deleted label and removed 1 deleted label
If you do not make required to put all accounts in the report tree, you will miss some. So the current design ensure that every account is places somewhere in the report tree. Your proposal does not ensure that.
? I made no compete proposal for reports, only to try to alleviate the misrepresentation of the account type (at least as noticed in the French plan) and a suggestion for a filter to simplify a reporting need.
The reports themselves will need to be revisited, naturally, and they *should* be conformant to national standards.
If for example a bank account is 'creditor' (or overdrawn) then the report should have it under liabilities as its current value implies a debt. Otherwise it is a liquid 'asset'. Similar for third-party or auxilliary (partner) accounts.
This doesn't appear to be the case for at least the French plan
and as such presents inexact reports.
I tried creating a new base with a company using simply the minimal account plan and I noticed similar difficulties as with the French plan, hence my suggestion/observation.
Noticing now in the account plan that 'kind' is already there (which is more or less a superset of what I suggested earlier). The difficulty seems to stem from the required secondary 'type' which simply cannot be static for all account types (or rather, 'kinds').
Trial balance and GL *are* static reports and naturally don't normally even refer to these 'types'. (pm: view accounts are still problematic)
From the initial issue problem statement, I believe I read that you maintain that this is an exceptionnal case in a some country (France).
Can you cite perhaps at least one country where the issue is *not* exhibited? As is logical, it does seems rather pervasive from my limited research.
Account type is used balance sheet and profit and Loss. Both report agregateall information about all parties into a single type. So it does not affect the party_required flag.
In the French plan, although for many accounts with parties have a movement needed to treat correctly the balance, unfortunately there are others that are not(such as for class 45).
42x means here in the subaccounts, notably 421, 425 and 427 (not to mention others).
That Tryton doesn't set party_required forces either that one closes the account in order to create subaccounts (which is rarely done these days, at least for those using more modern accounting packages and more than an single employee or two) or override the model in order to set party_required and get on with it.
I don't believe this to be off topic as creditor/debitor status is on a party basis, by definition... in tryton, party_required simplifies the treatment of these cases.