After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 473348 - SKR04 needs separate versions for every year
SKR04 needs separate versions for every year
Status: VERIFIED DUPLICATE of bug 538913
Product: GnuCash
Classification: Other
Component: Business
git-master
Other All
: Normal enhancement
: ---
Assigned To: Derek Atkins
Derek Atkins
Depends on: 473350
Blocks: 433428
 
 
Reported: 2007-09-03 22:23 UTC by Rolf Leggewie
Modified: 2018-06-29 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Rolf Leggewie 2007-09-03 22:23:56 UTC
our overly competent government makes changes every year and thus the chart of accounts for SKR04 will slightly changes every year.  Maybe it is possible to split SKR04 into modules as proposed in another bug report and make the year-specific changes one module.
Comment 1 Josh Sled 2007-09-04 13:47:47 UTC
It's unclear to me exactly what the year-to-year changes look like, but the code processing those XML files doesn't have any notion of "merging" or "overlaying" one file's contents on top of another, which would seem to make isolating the year-to-year changes into a "module" difficult.  It's probably better to just copy -and-tweak the previous year's templates/modules/files.
Comment 2 Rolf Leggewie 2007-09-05 07:10:41 UTC
(In reply to comment #1)
> It's unclear to me exactly what the year-to-year changes look like, but the
> code processing those XML files doesn't have any notion of "merging" or
> "overlaying" one file's contents on top of another, which would seem to make
> isolating the year-to-year changes into a "module" difficult.  It's probably
> better to just copy -and-tweak the previous year's templates/modules/files.

Josh, thank you for your comment.  It helps me understand the inner workings of gnucash a bit better.  There is still a lot I need to get my head wrapped around, though.

It is possible to add several chart of accounts to a single gnucash file.  Thus, I was wondering if it might be a solution to have skr04-base and skr04-2005, skr04-2006 and skr04-2007, for example, to provide the modularization.  I will need to study the changes and the way those accountants usually deal with them more closely myself before I can make a judgment on this question.
Comment 3 Frank H. Ellenberger 2008-06-16 22:16:17 UTC
#1: I think the german private account templates have a modular design?

If the user keeps the data from more than one year in a file, and also in the template, one possibility would be, to introduce slots <valid from> <valid until>. But this would introduce the question, could there be:
2006: Erlöse 16% 4400
2007: Erlöse 16% 4340
2007: Erlöse 19% 4400
(example from DATEV: SKR04-2007)

In other words: must account names or account numbers unique?
Comment 4 Rolf Leggewie 2008-06-16 22:48:57 UTC
For the German context, account names and account numbers should probably be unique.  I am not yet sure how gnucash should deal with updates to SKR accounts and having the same gnucash file span more than one year.
Comment 5 Rolf Leggewie 2008-06-18 08:03:42 UTC
My current take on this subject is described in bug 473350 comment 2
Comment 6 Rolf Leggewie 2008-06-18 08:15:37 UTC
It seems as if accounts get added but apparently there is no need to delete older accounts
Comment 7 Frank H. Ellenberger 2008-06-18 17:15:04 UTC
As you can see in the spreadsheets at https://lists.berlios.de/pipermail/kontenrahmen-devel/ there is much confusion under the german opensource maintainers of the systems of accounts, when DATEV dropped which account.

It seems to me, that nearly every year they declare a few for invalid. 2008 they dropped the accounts, which were necessary, to have the old and the new VAT taxrate in the system.
Comment 8 Rolf Leggewie 2008-07-07 00:06:47 UTC
I believe bug 538913 has the problem formulated more to the point.  A user should keep all transactions for all years in a single file.  Updates should be made to that file instead of creating a new file for every year.

*** This bug has been marked as a duplicate of 538913 ***
Comment 9 John Ralls 2018-06-29 21:47:53 UTC
GnuCash bug tracking has moved to a new Bugzilla host. This bug has been copied to https://bugs.gnucash.org/show_bug.cgi?id=473348. Please update any external references or bookmarks.