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 538911 - RFE: plausibility checks
RFE: plausibility checks
Status: RESOLVED WONTFIX
Product: GnuCash
Classification: Other
Component: General
git-master
Other All
: Normal enhancement
: ---
Assigned To: Andreas Köhler
Andreas Köhler
Depends on:
Blocks: 473506
 
 
Reported: 2008-06-18 09:09 UTC by Rolf Leggewie
Modified: 2018-06-29 22:05 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Rolf Leggewie 2008-06-18 09:09:20 UTC
Please describe the problem:
account charts for German businesses are standardized.  Gnucash does not prevent the user from recording transactions that go against the philosophy of these standardized account charts.  Gnucash should support the user better in avoiding entry mistakes here.  The best thing would be of course, if gnucash were to reject incorrect entries outright, but I think that will be very hard to get right.  A much easier thing would be to have plausibility checks (possibly even an external tool) that can be run periodically by the user and that list transactions that are likely incorrect.

Steps to reproduce:


Actual results:


Expected results:


Does this happen every time?


Other information:
Comment 1 Josh Sled 2008-06-19 19:54:21 UTC
Interesting … what's an example of an implausible transaction?  How would such a mechanism detect that transaction?
Comment 2 Rolf Leggewie 2008-06-19 21:35:19 UTC
I am learning about this myself.  To collect the list of such transactions would also be a work in progress once the structure is in place to deal with them.  

One stupid, but nonetheless important example is a transaction involving account 1405 "Abziehbare Vorsteuer 16%" after January 1st 2007, it would have to go to 1406 "Abziehbare Vorsteuer 19%" instead.
Comment 3 Christian Stimming 2008-11-08 13:56:23 UTC
I'm sorry, but this item is way too general and "wolkig" to be a useful bugzilla item. 
Comment 4 Rolf Leggewie 2008-11-08 14:32:37 UTC
Well, then think about this as an umbrella from which to spin off other tasks to fix one by one.

reopening.  Feel free to assign it to me if you want to get it off your radar.
Comment 5 Phil Longstaff 2009-06-18 18:37:43 UTC
In the spirit of a modular architecture, what I could see here is a hook that a module could tie into to be called back when a new transaction is going to be saved.  It could pop up whatever dialog it wants, and could then return a TRUE/FALSE indication whether to allow the transaction to be saved or not.  That is the best that Gnucash could provide.  It would be up to someone else to supply the specific German transaction validation module.
Comment 6 Rolf Leggewie 2009-07-10 17:11:23 UTC
sounds like it may be worth a try.
Comment 7 Christian Stimming 2011-01-16 19:53:58 UTC
Thank you for taking the time to explain your enhancement request.

The described enhancement is a good proposal and would be an advantage for the software. However, as a volunteer-driven project with limited resources, the GnuCash developers have their own priorities about the features which are most likely being worked on in the near future. In that sense, the current GnuCash developers decided not to work on your proposed feature in the next 4-6 months. In case you would like to have this feature implemented in any case, you have the following option: 1. Start to program in gnucash yourself - see http://wiki.gnucash.org/wiki/Development . 2. Convince someone who is not yet part of the GnuCash team to join the team and implement your feature. 3. Pay some of the GnuCash developers to implement your feature - ask on the mailing list gnucash-devel@gnucash.org in that case. Thank you very much.

Feel free to file other bugs or enhancement requests that you find, though.
Comment 8 John Ralls 2018-06-29 22:05:41 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=538911. Please update any external references or bookmarks.