Overview
This article outlines the most common MYOB AccountRight export errors and warnings you may encounter when exporting from Ocerra. Each error includes a brief explanation, possible causes, and clear steps to help you resolve the issue quickly.
Use this guide as a reference whenever an export fails or a warning appears in your workflow.
Error: API Timeouts / Gateway Errors
This occurs when MYOB’s API is temporarily overloaded or unresponsive, often resulting in a message like:
“Connection to the API has timed out” (typically after ~2 minutes).
This is a limitation on MYOB’s side and can affect both data and attachment exports.
How to resolve:
Retry the export later — early mornings or evenings tend to have lower API traffic and may yield better results.
If attachments fail to upload, check the export result in Ocerra. You can manually download the attachments from Ocerra and upload them directly into MYOB if needed.
Error: Line_JobHeaderNotAllowed (also applies to AccountHeaderNotAllowed)
This error occurs because MYOB does not allow transactions to be recorded against Header Jobs or Header Accounts.
How to resolve:
Update the Job or Account in Ocerra to a detailed (non-header) Job or Account, then try exporting again.
Error: Supplier has not supplied ABN number
This error appears when Ocerra has extracted an ABN from the invoice, but the supplier card in MYOB is missing an ABN.
How to resolve:
- Add the ABN number to the supplier card in MYOB.
- Re-import suppliers into Ocerra (sync vendors under MYOB AccountRight settings in Ocerra).
- Then, try exporting the invoice again.
If a supplier genuinely doesn’t have an ABN, Ocerra allows you to:
Remove the extracted ABN from the supplier card before exporting.
Export without triggering the error.
Error: Term_Out_Of_Range error
This error usually occurs when the Due Date is set earlier than the Invoice Date.
For example, if the Invoice Date is 1 March but the Due Date is 20 February, the export will fail. Most accounting systems, including MYOB, require the Due Date to be the same as or later than the Invoice Date.
How to resolve:
Check the invoice in Ocerra and update the dates accordingly. Then, try exporting again.
Error: ForeignCurrency is required
This error occurs when the invoice currency doesn't match the supplier’s currency in MYOB, and Foreign Currency is not enabled.
How to resolve:
Make sure that Foreign Currency is enabled in your MYOB company file.
Confirm that the currency of the invoice matches the currency set on the supplier card.
If the supplier’s currency differs from your company’s default currency, MYOB requires Foreign Currency to be enabled to process the transaction.
Error: BusinessEvent_DateOccured_InLockPeriod
This error occurs when the invoice date falls within or before a locked period in MYOB AccountRight. The MYOB ARL API prevents posting transactions on the same date as the lock period.
Important notes:
Ocerra stores dates in UTC format, which may cause a date shift depending on your local time zone.
Ensure the invoice is dated after the locked period in MYOB.
Assign a unique invoice number before exporting.
You can also refer to MYOB’s documentation for more context:
MYOB Community – Locking Error
Error: Cannot update or delete order converted to Bill
This error occurs when attempting to modify or delete a purchase order that has already been converted into a bill in MYOB. Once converted, the original PO becomes part of the financial records and is locked to preserve data integrity.
How to resolve:
Check the PO status – Confirm whether the purchase order has been converted to a bill.
Edit the bill instead – If updates are needed, make changes to the bill rather than the original purchase order.
Update in Ocerra if required – For example, remove the PO reference from the invoice in Ocerra and re-export.
Error: Purchase transaction will exceed supplier credit limit
This error is triggered by credit limit settings in MYOB for the supplier. It means the new transaction would exceed the defined credit limit.
This is a restriction from MYOB, and manually entering the same bill would result in the same message. Ocerra respects these limits and does not override them.
How to resolve:
Review the supplier’s credit limit settings in MYOB and adjust if necessary, or wait until the balance is cleared before retrying the export.
Error: Job/Account with UID "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx" cannot be found
This error indicates that the selected Job or Account either no longer exists, has been made inactive, or has a duplicate in MYOB.
How to resolve:
Check in MYOB if the Job or Account still exists and is active.
If the Job has been deleted or is inactive in MYOB, go to General Settings in Ocerra and mark it as inactive.
For Accounts, you can manage them directly from the Settings screen in Ocerra.
Error: UID/DisplayID not found
This error occurs when an invoice in Ocerra is linked to a supplier that has been deactivated in MYOB.
What happened:
The invoice was originally auto-matched to a supplier in Ocerra.
That supplier was later deactivated in MYOB, and a new supplier with the same name was created and synced back into Ocerra.
Since the invoice is still linked to the now-inactive supplier, the export fails.
How to resolve:
Rename the deactivated supplier in Ocerra to avoid confusion.
Re-match the invoice to the new, active supplier.
Try exporting the invoice again.
If the error persists:
MYOB may still be referencing the original supplier ID from the first export attempt. In this case, archive the invoice and re-upload it to Ocerra. This will reset the supplier link and ensure future invoices from this supplier are matched correctly.
Error: BusinessEvent_CategoryRequired
This error occurs when MYOB requires a category for the transaction, but the category in Ocerra is either missing or does not exactly match what exists in MYOB.
How to resolve:
Make sure a category is selected in Ocerra before exporting.
Double-check that the category name matches exactly what is set up in MYOB, including spaces and capitalisation.
Alternatively, if categories are not required, you can update your MYOB preferences under Setup → Preferences → System to disable the requirement.