Version: 0.8.5 (using KDE KDE 3.5.4) Installed from: Gentoo Packages OS: Linux Suppose one moves money from an account in one bank to another account in another bank. The money is removed from the first account at one point in time and added to the other account at another point in time. The money is said to be floating during that timespan. To model this in the program, one has to manually create a float account and add 2 transactions. But it is very inconvenient to enter several transactions for the same logical transaction. And it is harder to follow the flow of money, because the program does not keep track of which pair of transactions to/from the float account belong together. I think it should be possible to set different dates in transactions. The program would then be able implicitly connect this to a float account. The float account is virtual. The user can see how much he has floating on it, but can not enter transactions directly to/from it. He can only implicitly add transactions to the float account by making transactions between other accounts, where the times differ. The user should probably be able to create several float accounts if he wishes, and choose which float account a certain transaction should use if it's times differ. Float accounts would of course not be stored in file, but recalculated from the transaction data. The transaction would then have the following data: * Source account * Time that the money leaves the source account { * Target account * Time that the money enters the target account * Float account (where the money is if the times differ) } The part between { and } is repeated for split transactions. Someone will say that one should do accrual accounting instead of cash accounting, but the bank accounts are cash accounts and therefore needs to be modeled with cash accounting. Accrual accounting can still be used for other accounts in the user's dataset. This functionality is a requirement for adding more advanced functionality to the program, like interest calculation for bank accounts. This request is also registered for gnucash: http://bugzilla.gnome.org/show_bug.cgi?id=353602 The relevant discussion is at: https://lists.gnucash.org/pipermail/gnucash-user/2002-October/004391.html
Created attachment 18045 [details] Tiny start for a patch. This is just a tiny start of a patch. It makes it possible to edit, save and load the information, but it is not used yet.
Created attachment 18050 [details] Tiny start for a patch. This patch enforces validity when entering the information. See table (attached soon) for explanation of the validity enforcement.
Created attachment 18051 [details] Table that describes the validity enforcement of the float data.
(In reply to comment #2) > Created an attachment (id=18050) [details] > Tiny start for a patch. > > This patch enforces validity when entering the information. See table (attached > soon) for explanation of the validity enforcement. Is this patch still valid or has it bitrotted? I think this would be useful functionality for those that want it - perhaps pref controlled?
I did not test the patch recently so it is probably bitrotted. It was never complete anyway.
Moving this wish to kmymoney4.
*** Bug 342989 has been marked as a duplicate of this bug. ***
*** Bug 434871 has been marked as a duplicate of this bug. ***
*** This bug has been confirmed by popular vote. ***