Bug 328575 - Create transaction to move an investment from one investment account to another
Summary: Create transaction to move an investment from one investment account to another
Status: REPORTED
Alias: None
Product: kmymoney
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: unspecified All
: NOR wishlist
Target Milestone: ---
Assignee: KMyMoney Devel Mailing List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-12-09 14:36 UTC by Jack
Modified: 2022-02-17 15:40 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jack 2013-12-09 14:36:37 UTC
If you have multiple accounts with a Broker, you sometimes move stock from on account to another.   To do this in KMM now, you have to remove the shares in one account and then add them to the other account.  It would be easier to allow a transfer, in the same way you can transfer cash from one account (such as checking or savings) to another.  There should not be any restrictions on the receiving account, since it is possible to transfer stocks to an account with a different broker/institution.
Comment 1 allan 2013-12-10 10:59:32 UTC
On 09/12/13 14:36, Jack wrote:
> https://bugs.kde.org/show_bug.cgi?id=328575
>
>              Bug ID: 328575
>             Summary: Create transaction to move an investment from one
>                      investment account to another
>      Classification: Unclassified
>             Product: kmymoney4
>             Version: unspecified
>            Platform: unspecified
>                  OS: All
>              Status: UNCONFIRMED
>            Severity: wishlist
>            Priority: NOR
>           Component: general
>            Assignee: kmymoney-devel@kde.org
>            Reporter: ostroffjh@users.sourceforge.net
>
> If you have multiple accounts with a Broker, you sometimes move stock from on
> account to another.   To do this in KMM now, you have to remove the shares in
> one account and then add them to the other account.  It would be easier to
> allow a transfer, in the same way you can transfer cash from one account (such
> as checking or savings) to another.  There should not be any restrictions on
> the receiving account, since it is possible to transfer stocks to an account
> with a different broker/institution.
>

You say "Create transaction to move....".  If I understand what you are 
thinking, that would involve inventing a new, non-standard, activity 
type.  Might it not be better to have a context menu option to do the 
transfer, as with checking accounts - 'Move transaction to...'?

Allan
Comment 2 Jack 2013-12-10 14:47:07 UTC
No.  I don't want to move the transaction to another account, I want a transaction to move the shares to another account in the same way you can already move cash between accounts with a "transfer".  Moving the transaction is already possible via the context menu.  (As I said in the mailing list, I can  now fake this type of transaction by creating a "remove shares" transaction, duplicating that transaction, moving the duplicate transaction to the other account, and then reversing that to "add shares."  This new transaction would not only save lots of steps, but it would keep a proper record of what happened to the shares.
Comment 3 allan 2013-12-10 17:45:42 UTC
On 10/12/13 14:47, Jack wrote:
> https://bugs.kde.org/show_bug.cgi?id=328575
>
> --- Comment #2 from Jack <ostroffjh@users.sourceforge.net> ---
> No.  I don't want to move the transaction to another account, I want a
> transaction to move the shares to another account in the same way you can
> already move cash between accounts with a "transfer".  Moving the transaction
> is already possible via the context menu.  (As I said in the mailing list, I
> can  now fake this type of transaction by creating a "remove shares"
> transaction, duplicating that transaction, moving the duplicate transaction to
> the other account, and then reversing that to "add shares."  This new
> transaction would not only save lots of steps, but it would keep a proper
> record of what happened to the shares.
>

The thing is, Are you not putting yourself out on a limb?  You would be 
using a transaction type that no other software would recognise.  Heaven 
forbid, but if KMM ceased to exist for whatever reason, and you 
wanted/needed to export everything, you would run into self-inflicted 
difficulties on top of the usual crop of difficulties on a new app.
Comment 4 Jack 2022-02-17 15:40:47 UTC
There is an additional reason for KMM to handle this transaction type natively.  Currently, if you move shares with a "remove shares" and an "add shares" transaction pair, investment income reporting is messed up - showing a total loss of those shares in the first account, and an absurdly large gain in the second.