Skip to main content
Skip table of contents

Error: "MYOB.Sbr.Desktop.Lodgement.LodgementEngine Run MoveNext ... " when lodging via PLS

This support note applies to:

  • AE Tax (AU)

These instructions require technical expertise

Make sure you know what you're doing and are using one of the products listed. If you're not sure, ask your IT professional or MYOB.

Article ID: 38687

What you need to know:

The ATO is decommissioning AUSkey on 27 March 2020. See AUSkey decommissioning on the ATO website for more details.
  • If you’re using Lodgment Manager to lodge, you don’t need to do anything.
  • If you're using AUSkey Authentication to lodge, you can’t lodge after 27 March 2020. Talk to your client manager about how to upgrade your practice.

    If you have any questions, contact us.

In MYOB Accountants Enterprise (AE) Tax version 2016.4, you may experience the error "MYOB.Sbr.Desktop.LodgementEngine Run MoveNext Object reference not set to an instance of an object" when attempting to lodge using PLS (AUSkey).

This error can occur after a previous AUSkey Lodgment has failed.

To resolve this error you need to navigate to your AESQL\TAX\IPSbr or SOL64\IPSbr folder and ensure that the following folders are empty:

  • SbrWorking
  • SbrOutput
  • SbrStaging
How to locate and delete the contents of the IPSBr folders
  1. Open Windows Explorer and navigate to X:\MYOBAE\AESQL\TAX\IPSbr where X:\MYOBAE is your installed location. The IPSbr folder appears.

    For information on how to find your installed location refer to Finding the SOL64 or Tax directory
  2. Double click on the SbrWorking folder.
  3. Highlight all files within the SbrWorking folder and right-click on the highlighted area then select Delete.
  4. Repeat steps 2 and 3 to delete the contents of the SbrOutput and SbrStaging folders.
  5. Close Windows Explorer. The Windows Desktop appears. You can now lodge via PLS.



MYOB Internal Note:

PR# 144717836907

JavaScript errors detected

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

If this problem persists, please contact our support.