Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

The German charts of accounts SKR03 and SKR04 need improvements #22363

Closed
3 of 8 tasks
priojk opened this issue Sep 22, 2022 · 2 comments
Closed
3 of 8 tasks

The German charts of accounts SKR03 and SKR04 need improvements #22363

priojk opened this issue Sep 22, 2022 · 2 comments
Labels
Bug This is a bug (something does not work as expected) Issue Stale (automatic label) This issue is stale because it has been open 1 year with no activity. Remove this label to keep open

Comments

@priojk
Copy link
Contributor

priojk commented Sep 22, 2022

Bug

There are several issues with the current German charts of accounts SKR03 and SKR04. Mainly, the pcg_types are all unset and the parent accounts are not usable in the current state (currently there is no functionality in Dolibarr making use of them, but for reporting purposes the parent accounts will be required in the future).

  • SKR03 Account numbers according to DATEV documentation shall have a length of 4 digits with leading zeros, like 0038 instead of 38. This helps also with sorting in drop down lists, like currently there is the order 38, 380, 3800, 39, ... which should probably rather be sequential: 0038, 0039, 0040, ...

  • SKR03 Parent accounts as they are defined currently don't make much sense, some are faulty (in the sql file, there needs to be given the row ID of the parent, not the account number of the parent, this is not always handled correctly).

  • SKR03 Parent accounts make sense in terms of the HGB structure for the balance sheet and the P&L. The respective items need to be created as additional accounting accounts and linked as parent accounts to the individual accounting accounts.

  • SKR03 pcg_type is not set

  • SKR04 Account numbers shall also have a length of four digits with leading zeros (see aboce).

  • SKR04 Lots of accounts are disabled/commented out, since they have an incorrect parent account. In this state, the SKR04 does not seem to be usable. Parent accounts could be removed/unset and the lines re-enabled in a first step.

  • SKR04 Parent accounts make sense in terms of the HGB structure for the balance sheet and the P&L. The respective items need to be created as accounting accounts and linked as parent accounts to the individual accounting accounts.

  • SKR04 pcg_type is not set

Will try to provide pull requests for the issues.

Would be happy, if some accounting experts could chime in, in particular regarding the pcg_types and balance/P&L items as parent accounts.

@priojk priojk added the Bug This is a bug (something does not work as expected) label Sep 22, 2022
@priojk
Copy link
Contributor Author

priojk commented Sep 26, 2022

pcg_type is actually set to the leftmost value of the account numbers, reflecting the major groups (e.g. account 8200 is in group '8'), so will keep it for the time being.

@github-actions
Copy link

This issue is stale because it has been open 1 year with no activity. If this is a bug, please comment to confirm it is still present on latest stable version. if this is a feature request, please comment to notify the request is still relevant and not yet covered by latest stable version. This issue may be closed automatically by stale bot in 10 days (you should still be able to re-open it if required).

@github-actions github-actions bot added the Issue Stale (automatic label) This issue is stale because it has been open 1 year with no activity. Remove this label to keep open label Sep 26, 2023
@github-actions github-actions bot closed this as completed Oct 6, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug This is a bug (something does not work as expected) Issue Stale (automatic label) This issue is stale because it has been open 1 year with no activity. Remove this label to keep open
Projects
None yet
Development

No branches or pull requests

1 participant