Home → Problems →

FIX: NON-HIERARCHICAL SECURITY ACCT TXNS

• Edit

Tom Goodhart

Jun 28, 2023 @ 12:19 AM

I ran TOOLBOX - 'FIX: Non-Hierarchical Security Acct Txns (& detect Orphans)' and got the following results:

I don't understand how to fix these 2 txns. There are 51 transactions in Category "Initial Holdings", it is an Expense category
______________________________________________________________________________________________________
FIX Investment Transactions where Security's Account is not linked properly to the Parent Txn's Acct:
 =====================================================================================================

Scanning for Security Orphans...:

>> No investment txn(s) with Orphaned securities were detected!

Scanning txns for non-hierarchical accounts:
 -------------------------------------------

Must fix txn BUY_XFER
ParentTxn(276196a3-87fc-4808-9326-04e205a62a47): val=6953;
 date=20161003;
 chk=ShrsIn;
 desc=Purchase: DOLLAR GENERAL CORP EXECUTED 100% AGENCY PRI;
 stat= ;
 acct=13 Invest.:Initial Holdings;
 
   SplitTxn: val=-6953;
 amt=6953;
 desc=Purchase: DOLLAR GENERAL CORP EXECUTED 100% AGENCY PRI;
 stat=x;
 cat=13 Invest.:Initial Holdings;
 tags=[(samt:-6953)(stat:x)(acctid:580f17bd-8808-470a-a9e9-69fa1c12785b)(invest.splittype:xfr)(obj_type:)(id:541fca51-7f21-49b3-a2b5-a1b828c40aa8)(pamt:6953)(oldid:-1)(desc:Purchase: DOLLAR GENERAL CORP EXECUTED 100% AGENCY PRI)];
 ]
 > in '13 Invest.:Initial Holdings' with sec acct 'None'
** CANNOT FIX Txn where the Parent is sitting within an NON INVESTMENT(EXPENSE) account and the SECURITY is NONE - SKIPPING **Must fix txn BUY_XFER
ParentTxn(8d2dc6a6-895c-4780-aa9a-bd4a1b37910a): val=2965;
 date=20161011;
 chk=ShrsIn;
 desc=Purchase: KROGER CO EXECUTED 100% AGENCY PRICE SHOWN I;
 stat= ;
 acct=13 Invest.:Initial Holdings;
 
   SplitTxn: val=-2965;
 amt=2965;
 desc=Purchase: KROGER CO EXECUTED 100% AGENCY PRICE SHOWN I;
 stat=x;
 cat=13 Invest.:Initial Holdings;
 tags=[(samt:-2965)(stat:x)(acctid:580f17bd-8808-470a-a9e9-69fa1c12785b)(invest.splittype:xfr)(obj_type:)(id:75237166-4941-4364-9eb7-1b778a639cf5)(pamt:2965)(oldid:-1)(desc:Purchase: KROGER CO EXECUTED 100% AGENCY PRICE SHOWN I)];
 ]
 > in '13 Invest.:Initial Holdings' with sec acct 'None'
** CANNOT FIX Txn where the Parent is sitting within an NON INVESTMENT(EXPENSE) account and the SECURITY is NONE - SKIPPING **

You have 2 non-hierarchical txn errors...

RUNNING FIX ON SECURITY TXNS TO RE-LINK PARENT ACCOUNTS
------------------------------------------------------------

Must fix txn BUY_XFER
ParentTxn(276196a3-87fc-4808-9326-04e205a62a47): val=6953;
 date=20161003;
 chk=ShrsIn;
 desc=Purchase: DOLLAR GENERAL CORP EXECUTED 100% AGENCY PRI;
 stat= ;
 acct=13 Invest.:Initial Holdings;
 
   SplitTxn: val=-6953;
 amt=6953;
 desc=Purchase: DOLLAR GENERAL CORP EXECUTED 100% AGENCY PRI;
 stat=x;
 cat=13 Invest.:Initial Holdings;
 tags=[(samt:-6953)(stat:x)(acctid:580f17bd-8808-470a-a9e9-69fa1c12785b)(invest.splittype:xfr)(obj_type:)(id:541fca51-7f21-49b3-a2b5-a1b828c40aa8)(pamt:6953)(oldid:-1)(desc:Purchase: DOLLAR GENERAL CORP EXECUTED 100% AGENCY PRI)];
 ]
 > in '13 Invest.:Initial Holdings' with sec acct 'None'
** CANNOT FIX Txn where the Parent is sitting within an NON INVESTMENT(EXPENSE) account and the SECURITY is NONE - SKIPPING **Must fix txn BUY_XFER
ParentTxn(8d2dc6a6-895c-4780-aa9a-bd4a1b37910a): val=2965;
 date=20161011;
 chk=ShrsIn;
 desc=Purchase: KROGER CO EXECUTED 100% AGENCY PRICE SHOWN I;
 stat= ;
 acct=13 Invest.:Initial Holdings;
 
   SplitTxn: val=-2965;
 amt=2965;
 desc=Purchase: KROGER CO EXECUTED 100% AGENCY PRICE SHOWN I;
 stat=x;
 cat=13 Invest.:Initial Holdings;
 tags=[(samt:-2965)(stat:x)(acctid:580f17bd-8808-470a-a9e9-69fa1c12785b)(invest.splittype:xfr)(obj_type:)(id:75237166-4941-4364-9eb7-1b778a639cf5)(pamt:2965)(oldid:-1)(desc:Purchase: KROGER CO EXECUTED 100% AGENCY PRICE SHOWN I)];
 ]
 > in '13 Invest.:Initial Holdings' with sec acct 'None'
** CANNOT FIX Txn where the Parent is sitting within an NON INVESTMENT(EXPENSE) account and the SECURITY is NONE - SKIPPING **

You had 2 non-hierarchical txn errors... FIXED 0

<END>

1. 1 Posted by dwg on Jun 28, 2023 @ 01:41 AM

   

   I'm a fellow user.

   Ok so Toolbox is finding a problem, I understand you are using a category to draw the initial purchase funds from, which is fine.

   So what is throwing Toolbox off. I think I would be checking the basics to start with. so I would look at:

   1. Are the securities defined in Tools --> Securities

   2. Have the securities been associated with the correct Investment account

   3. Does the transaction have the correct security selected.

   • Edit

2. 2 Posted by Stuart Beesley ... on Jun 28, 2023 @ 07:04 AM

   

   OK, this implies that "13 Invest.:Initial Holdings" is NOT an investment account.... How did these txns get there (perhaps misuse of batch change)? Can you send Screenshot of the txns in question and also the Tools/accounts edit screen of the "13 Invest.:Initial Holdings" account?

   • Edit

3. 3 Posted by Stuart Beesley ... on Jun 28, 2023 @ 07:05 AM

   

   Also, within "13 Invest.:Initial Holdings", how many txns are in that account?

   • Edit

4. 4 Posted by Stuart Beesley ... on Jun 28, 2023 @ 11:44 AM

   

   Assuming the parent account is a non investment account. I think I would.

   • BACKUP

   • use toolbox. Edit account type. To investment.

   • run the toolbox fix

   • then select the two txns; run toolbox move investment txns. Move them to a real investment account.

   • toolbox. Edit the account type back to what it was.

   —- really depends what else is in that account?

   • Edit

5. 5 Posted by Tom G. on Jun 28, 2023 @ 03:32 PM

   

   1) Yes.

   2) Yes.

   3) Yes.

   Tom Goodhart

   • Edit

6. 6 Posted by Tom G. on Jun 28, 2023 @ 03:42 PM

   

   * 13 Invest.:Initial Holdings is an expense category.

   * These were part of an initial load of transactions from a QIF File. These discrepancies, just showed up. I had not seen this error before, now.

   

   Tom Goodhart

   • Transactions.png 75.3 KB
   • Initial_Holdings_Category.png 119 KB
   • Edit

7. 7 Posted by Tom G. on Jun 28, 2023 @ 03:46 PM

   

   355

   Here are the tens related to the error:

   
   Tom Goodhart

   • Initial_Holdings_Txns.png 89 KB
   • Edit

8. 8 Posted by Tom G. on Jun 28, 2023 @ 03:48 PM

   

   These 2 transactions are in an IRA Investment Account

   Part of setting up initial holdings of the IRA

   Tom Goodhart

   • Edit

9. 9 Posted by Stuart Beesley ... on Jun 28, 2023 @ 07:32 PM

   

   Simplest solution. Delete them and recreate them properly.

   • Edit

10. 10 Posted by Tom G. on Jun 28, 2023 @ 07:50 PM

    

    I think I found a problem, if not THE problem.

    I went back and reread the thread about using an “Initial Holdings” category.

    I had it as an Expense Category instead of Income per the thread.

    I couldn’t see how to change it from Expense to Income, so I did this:
    1. Renamed 13 Invest:Initial Holdings to Begin Holdings
    2. Changed Begin Holdings to be a standalone category (no Parent)
    3. Created a NEW Income category called “Initial Holdings”.
    4. Went into each IRA account and manually changed the category from "Begin Holdings” to the new “Initial Holdings”.
    5. Open Tools -> Categories - Begin Holdings
    6. Did Open new window and deleted the bad transactions.
    7. Deleted the category “Begin Holdings”

    Opened Toolbox. No red message saying to run "FIX: NON-HIERARCHICAL SECURITY ACCT TXNS. Woohoo!.

    Finally, I can back to reconciling these IRA accounts.

    Everything looks good now.

    Thanks for all your help.

    Tom Goodhart

    • Edit

11. 11 Posted by Stuart Beesley ... on Jun 28, 2023 @ 08:24 PM

    

    Well done!

    Toolbox 🧰 +1 😃

    • Edit

12. 12 Posted by dwg on Jun 28, 2023 @ 10:00 PM

    

    I doubt if the type of of category would be the problem. If you have an expense category and it is an income item it ends up with a negative number. This is how I use categories when I have expenses I get some reimbursement for to get a net figure.

    Now there being something wrong in the category itself is another matter. QIF imports relax a lot of rules in Moneydance i.e. you can do things that manually are not allowed. So I suspect that recreating the category and moving the transactions to the new category is what really solved your problem.

    • Edit

13. System closed this discussion on Sep 27, 2023 @ 10:00 PM.