Skip to main content
Skip table of contents

Ensuring journals post from Workpapers to AO Classic General Ledger

This support note applies to:

  • Workpapers (NZ)
  • AO Workpapers (AU)
  • AE Workpapers (AU)
Article ID: 37571

In MYOB Accountants Office (AO) Workpapers when you perform the Create Journal Export File process to post journals to an underlying AO Classic General Ledger (GL) data set, the transactions are posted automatically without any further process required in the AO GL application.

For this process to be successful, you need to ensure the User code in AO matches the Employee Code in AO Classic.

For more information regarding the posting process from Workpapers refer to the MYOB Help Centre topic Posting journals and exporting new accounts and follow the steps in the "To post journals to an AO Classic general ledger" heading.

 

To identify the employee code in AO Classic
  1. Open AO Classic and from the Tools menu, select Options. The Settings window opens.
  2. Click the Employees tab. The Employee details appear.
  3. Click the employee name which you use to log into AO Classic and note the Employee Code. The employee code is noted. 
To identify the user code in AO
  1. Open AO and click the drop-down arrow under Contacts and select Employees. The Find Employees window opens.
  2. Type your user name in the search for field and click Search. The search results appear.
  3. Open the relevant employee. The employee details appear.
  4. Review the Code field and ensure it matches the Employee Code from AO Classic and click OK. The Code field and the Employee Code fields match and journal transactions will now post from AO Workpapers.
     
 

 

If you have already attempted to process journals from Workpapers and they have failed to post, open the Workpaper Period and click Create Journal Export File. Select Include previously exported journals and continue the export process. 
JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.