Run the Batch

Click “Run Export”. This will start the export process.

Once started, a screen will appear that provides the status of the export process. When the export process completes, you will have a description of the results in the lower part of the screen. At this point, you can save a log of the results:

  • Click “Save List of Errors” to create a file that contains the list of errors that occurred. You might have to fix issues with various transactions and then rerun. Having this list of errors is helpful for listing those errors.

  • Click “Save Full Log” to create a file that contains much more information on the errors and the cause of those errors. This log is useful if you have a question on a specific error message and would like to send it to a Mobius Works support technician, as it provides us a great deal of information that helps us discover what happened.


When the export finishes, you will be left in one of three states. You should read the text in the output screen to determine the results of your batch. In general, you will experience one of three results:

  1. The batch failed

In this case, an error occurred before any transactions started to be imported into Sage 50 Accounts. These errors might be as simple as not being able to connect to either Manage or Sage 50 Accounts.

Additionally, this integration performs a number of validation checks before starting to push transactions to Sage 50 Accounts. An example validation is to check to make sure that a Vendor has been mapped successfully and the Vendor ID it was mapped to exists in the Sage 50 Accounts system. If any such validations fail, the batch will fail entirely.

You should fix whatever the error messages indicate and try to run the batch again. Because no transactions were exported, just as if you had never run the batch.

  1. The batch completed successfully

In this case, the batch was run successfully. All selected transactions were exported to Sage 50 Accounts and no errors occurred. Additionally, Manage was updated with the information of all the transactions, creating a new “Batch” with the Batch ID provided, that stores the list of transactions that were selected. These transactions will no longer show in the integration screen since they are considered to have been transferred to Sage 50 Accounts.

  1. The batch completed, but some transactions contained errors

In this case, all the validations passed, and at least one transaction was successfully imported into Sage 50 Accounts. However, there were some transactions that failed. In this case, a batch is still created with the transactions that did successfully transfer. Since a batch was created for the successful transactions, another batch will need to be created once the unsuccessful transactions are corrected based on the suggestion(s) in the error message.

For example, assume that John Doe ran batch “20130101JD-I”, which pushed 25 successful invoices to Sage 50 Accounts, but failed on three invoices. John should correct the issues described by the error messages, and then create another batch for these last three. This new batch number could be called “20130101JD-I-1”


Did you find it helpful? Yes No

Send feedback
Sorry we couldn't be helpful. Help us improve this article with your feedback.