GL Posting Report Error - "Account not Found"

 

 

 

“Account not found” can indicate one of two possible situations has occurred and each each requires a slightly different approach to fixing:

 

1) The account number is showing on the error list report but not existing in your GL Chart of Account list, in which case you can just create an account with that number temporarily to allow your General Ledger Transactions to post, then after posting move the money out of the temporary account and into the preferred account number with a manual GL Transaction using the GL Transaction Entry program.  You may then delete this temporary account number when the balance is zero, as you do not need it anymore.

 

2) If No account number is shown on the error report (blank) or the number is garbled in such a way that AA won’t allow you to create it as a valid account number, then you need to take the direct approach.  Open your database in MS Access.  If this is an A/R transaction trying to post open the table named GLBTRAN.  If this is an A/P transaction trying to post open the table named APGLHOLD.  If this is a P/R transaction trying to post open the table named GLPRTRAN.  You will see the list of General Ledger transactions waiting to be posted from that particular module.  In the General Ledger Account number field key in the company number and correct General Ledger Account number.  Save and exit MS Access.  Restart AA and try posting AR to GL Again.  It will post now unless there just happens to be an additional error that also needs attention.

 

Having an Inquisitor report designed to allow you look at non-posted GL Transactions ahead of time can save you time later while in MS Access.  Also, before actually opening your database in MS Access, everyone must be out of that database, and the less amount of time spent with your database open in MS Access to fix this problem the less inconvenience to your other AA users.

 

Note:  It is a good idea to always have a good, current copy of your database before opening it in MS Access.  It is good insurance even if the likelihood of needing it is very small.