Page 1 of 1

Asset Account Closing to Equity in Error

Posted: Sat Oct 09, 2004 2:05 pm
by Matt
This question is for Jeff. When I run the "Account Close To" report in Fund Accounting for Fund 02, somehow account 02-1120-000 on my Chart of Accounts got set up so that it is closing into account 02-3110-000. I can't figure out how this happened because when you are in Maintain Chart of Account the option to select the account to close to (when you click on details) does not appear if the account is an asset, liability, or equity account. But nevertheless it's there on the report. As a result, my balance sheet for fund 02 won't balance.

How can I fix this? I can't fix it through Maintain Chart of Accounts. I assume I will have to use the Database Manager in Utilities to fix this. I took a look and it looks like the Close to field I need to fix is in the FaAccts.DBF file. I viewed the record for account 02-1110-000 and it looks like I just need to change the "Close To" field from 023110000 to 02 on this record. Is this all I need to do to fix my problem?

Posted: Sun Oct 10, 2004 2:40 pm
by Matt
I think I found out what caused this problem to occur. I found out that every time I have added a detail asset, liability, or equity account to my chart of accounts in V.9 the program is automatically setting the account up to close to account 3110 (Unrestricted Net Assets) for the fund I set it up in. This is happening even though the option to specify what equity account the new account will close to does not come up on the "Specify Fund Level Options For Each Account" screen when adding detail asset, liability, and equity accounts. I just tested adding detail asset, liability, and equity accounts to my chart of accounts a bit ago and confirmed that all 3 accounts automatically got set up to close to the 3110 account.

Looks like there's a bug in the program that needs to be corrected. In the meantime, what should I do to correct the asset, liability, and equity accounts that I have already set up?

Posted: Mon Oct 11, 2004 9:40 am
by Zoe
This issue has been fixed in a maintenance release. Make sure you're on the latest program date (09/29/04 for version 9). Once the latest maintenance release is installed, reindexing the data files will fix the issue.