Bug 379695

Summary: Loan to a friend. I entered the debt sum twice
Product: [Applications] kmymoney Reporter: Victor Porton <porton>
Component: generalAssignee: KMyMoney Devel Mailing List <kmymoney-devel>
Status: RESOLVED WORKSFORME    
Severity: normal CC: jeffjl.kde
Priority: NOR    
Version: 4.8.0   
Target Milestone: ---   
Platform: Other   
OS: Linux   
Latest Commit: Version Fixed In:

Description Victor Porton 2017-05-10 13:08:51 UTC 
My friend owes me some money as I paid for his assets using my credit card.

I created a "Loan" account and then entered the sum of the debt along with other data of the account.

But to see the credit card payment withdrawn from my main savings account, I entered the same sum again in Ledgers.

So, why I was forced to enter this number twice? For me it looks like a misdesign of KMyMoney. Or at least it is hard to understand how to use it properly.

Please make it easy not to enter the same number more than once, when giving a loan to a friend.
Comment 1 Jeff 2017-05-11 13:34:36 UTC 
KMM supports transfers between accounts. In one of the accounts in question, click on "New", then "Transfer", then select the direction of transfer using "From" or "Pay To", then select the from or to account on the "Transfer To" or "Transfer From" line. The transaction will be entered in both accounts.
Comment 2 Thomas Baumgart 2017-05-14 11:17:17 UTC 
There is no need to enter amounts twice. It's just a matter of the right collection of accounts and understanding of the mechanics of accounting. The following steps should help you:

1.) Create an asset account called 'Loan to friend'
2.) Change the credit card payment in your savings account to a transfer into this asset account
3.) When you friend pays you back (even in multiple installations) enter a transfer transaction from the 'Loan to friend' account to the account that he transferred the money to.
4.) Once the asset is payed back, you can close the 'Loan to friend' account.
Comment 3 Thomas Baumgart 2017-05-14 11:18:11 UTC 
*** Bug 379696 has been marked as a duplicate of this bug. ***