Use the table below to troubleshoot common errors that may be encountered when posting data via AroFlo's cloud-based and desktop accounting integration links. Further information can be accessed by clicking the blue error message link.
To search for keywords on this page, press Ctrl + F on your keyboard.
The client in MYOB is set to On Credit Hold status which prevents invoices from being created against their account.
The client will need to remove the On Credit Hold status (if no longer applicable) to be able to push the invoice across.
MYOB is expecting a "Category" to be defined for the Invoice that is being posted.
This is a enforcement that can be turned off within MYOB or if it needs to be used, the integration link needs to be configured to pass the appropriate Category details to via the Manage -> Integration -> Integration Entities -> "Invoice Category" section.
MYOB is expecting a "Job" to be defined for the Invoice line items that are being posted.
This is a enforcement that can be turned off within MYOB or if it needs to be used, the integration link needs to be configured to pass the appropriate Job details to via the Manage -> Integration -> Integration Entities -> "Invoice Job" section.
When trying to send an invoice across and receiving this error, it's due to the client having a payment block enabled for that period, typically around financial year.
Also check that the Due date isn't set prior to Date invoiced.
Client must remove their payment block within MYOB to be capable of sending new invoices across.
Posting Purchase Orders or COGs to 630-Inventory account
XERO reserves the account 630-Inventory for it's own uses and cannot be used for integration. In order to track cost of inventory in XERO you will need an independant Asset account code setup, imported into AroFlo and configured correctly in the Map Account Codes area.
Once the new account is setup, adjust the PO line items to the new account and re-post. COGs entries will need to be updated by AroFlo Customer Service.