MiGL Integrator Error Messages and Resolutions

The most common error messages received in the Integrator app relate to GL mapping in SwiftPOS BO and the accounting software settings. Generally a new media or sales item has been used in SwiftPOS BO and the relevant GL account has not been assigned to it. This prevents the journals posting from the Integrator to the general ledger.

Outlined below are common error messages and their resolutions. If you are still unable to post journals or invoices to your GL on completing the resolution please contact support@miclub.com.au and include details and images of any errors and messages received.

No GL code mapped

The media type, or accountpurchase assignment Master Group has not been assigned a GL Code.

Resolution: Follow the steps in this link How to map GL codes in SwiftPOS BO

Supplier Terms Not Set

The DUE DATE has not been set on the supplier record in Xero. Note: SwiftPOS does not have an option to set terms for a supplier.

Resolution: Login to Xero and navigate to the supplier details. Find the fields Bills Due Date and Invoices Due Date and enter the required Due Day and Month for each option.

New Supplier Invoices Not Posting to Xero (no error message returned)

The supplier records in SwiftPOS BO and Xero do not match.

Resolution: Check the supplier Account Number in Xero matches the Supplier ID number in SwiftPOS BO.

Sales Sales Total is $0.00 and No COS GL Code is mapped (no error message returned)

The STK Wastage media is likely to be missing the GL code in SwiftPOS BO 

Resolution: Follow the steps in this link How to map GL codes in SwiftPOS BO

Unhandled exception has occurred in your application.....Execution Timeout Expired

This error generally relates to an interruption in the connection between the database, internet and the accounting software, causing the process to timeout and cancel. You may need to wait 5 - 30 minutes before connection is reestablished.

Resolution: Close the application, reopen and repost the transactions or invoices