If I have interpreted the Swedish bookkeeping regulations correctly, all transactions (verifikat) should be numbered consecutively. Currently I do this manually with the "check number" field, making sure that I get a global numbering of transactions in all accounts. This is of course quite error prone and seems like unnescessary work, so if KMyMoney could do this (semi-)automatically instead, it would be really great. In detail: a setting whether to force numbering of all transactions or not; each new transaction is given the next higher number in a global sequence, with the possibility to override the number if need be. Thanks! Reproducible: Always Steps to Reproduce: N/A Actual Results: N/A Expected Results: N/A
This would also require inhibiting the deletion of transactions. Otherwise, the numbers are not consecutive anymore, right? BTW: Internally KMyMoney has such a number. It is called "Transaction-ID" but not visible at the UI and not changeable at all.
(In reply to comment #1) > This would also require inhibiting the deletion of transactions. Otherwise, > the numbers are not consecutive anymore, right? > > BTW: Internally KMyMoney has such a number. It is called "Transaction-ID" > but not visible at the UI and not changeable at all. Presumably, though, the ID could be copied into the check number field, optionally, with no on-going relationship to the "Transaction-ID"?
(In reply to comment #1) > This would also require inhibiting the deletion of transactions. Otherwise, > the numbers are not consecutive anymore, right? Inhibiting or at least warning about it. My dream scenario would be: for already reconciled transactions, do not allow deletion or leave a "deleted marker" upon deletion, so that the numbers do not change. For not yet reconciled transactions, allow re-number transactions if one is removed. Thanks for your showed interest in this!
Actually deleting a transaction (probably considered appropriate if it was entered in error, for example) changes account balances. I suppose only marking a transaction as deleted, but not actually removing it, could do the same thing, but keep the information for future reference. There would then also need to be a date-deleted field added to transactions. Should this then be changed to a wishlist? Perhaps some of this might be controlled by some configuration setting, as I don't think all countries require this. Separately - do the Sweeding regulations apply to personal finance software, or only software used for commercial users?