MYOB Common Errors
Start with your current app
For Shopify and Neto, inspect Logs and the affected Orders, Payments or Products record. For WooCommerce and BigCommerce, inspect Sync jobs, Activity and the affected record. Importing, transferring and scheduling are separate actions.
Follow the current troubleshooting guide before repeating a financial export. For a timeout, check whether the document already exists in MYOB.
- MYOB Sync for Shopify — Install MYOB Sync through the Shopify App Store, then open it from your store admin.
- MYOB Sync for Neto / Maropost — Add MYOB Sync through your Neto add-on workflow. Contact MySync if you need help finding or enabling the connection.
- MYOB Sync for WooCommerce — Open the WooCommerce app in MySync, sign in or create an account, then approve the connection from your own WordPress store.
- MYOB Sync for BigCommerce — Contact MySync for installation access while the public BigCommerce Marketplace listing is being prepared. Existing approved stores can open the app from BigCommerce Apps.
App specific errors can be found here.
This article lists errors returned by MYOB and their solutions.
If you cannot find the error on this page MYOB has a more extensive list that can be found here.
| Error | Cause | Solution |
| [####] CardId:(SalesEvent) | 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. |
| [4227] CategoryId:(SaleEvent) | 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. |
| [4245] JobId:(SaleEventLine) | 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. |
| [50] Error converting value "" to type 'System.Guid'. Path 'lines[X].Account.uid', line 1, position YYY. | The Account Code (Account.uid) for the item at line number X (lines[X]) does not have a matching identifier (uid) that MYOB understands. | Remap the account code and update the line item to select the new account code and retry the post. |
| [50] Error converting value "" to type 'System.Guid'. Path 'invoices[X].uid', line 1, position YYY | The invoice (invoices[X].uid) from this payment has not been transferred to MYOB and does not have an identifier (uid) that MYOB understands | Ensure the invoice has been posted across via the integration link and then try posting the payment again. |
| [50] Error converting value "" to type 'System.Guid'. Path 'SellingDetails.FreightTaxCode.UID' | Purchase order line item tax code (FreightTaxCode.UID) does not have an identifier (UID) that MYOB understands. | Ensure all tax codes have been properly imported from MYOB and mapped accordingly in the Map Account Codes area. Update the PO line items with the correct tax codes and retry the post. |
| [2530] Number:(ABNVO) | The ABN details in AroFlo do not align with the expected format "12 345 678 901". The ABN needs to include all spaces to be valid. |
Locate the client card and ensure the ABN format is correct. |
| BusinessLine_AccountHeaderNotAllowed | Attempting to post data with an 'Header' Account Code mapped. |
Ensure a 'Header' Account Code is not being used when posting Data. Use an Account Code under a Header. Example - How it looks in MYOB Name - Account Code 1234 <--- This is a header level (Can't Use) Name - Account Code 5678 (Can Use) Name - Account Code 9012 (Can Use) |
| Error 100 Required: Account is required Account | The payment cannot find which account it should be applied to. | Payment method should be mapped to correct Account from MYOB Live |
| Error 111 IncorrectRowVersionSupplied: An Update operation requires the latest RowVersion for each of the existing entities being modified. | The order has not been exported correctly. | Mark the invoice for re-export. Open the invoice in Maropost Commerce and tick the box Re-export order to 3rd party app at the bottom of the page, then save. The invoice can then be re-exported manually from the Export log or wait for the next schedule export to run. |
| Error 4237 ValidationError: BusinessLine_AccountRequired AccountId:(SaleEventItemLine) | This is related to incorrect/incompatible tax code with regards to Cost Of Sales Account / Income Account. | Update the tax code for the cost of sales or income account and re-export the order. |
| Error 4340 ValidationError: SaleEventLine_ItemSoldRequired ItemId:(SaleEventItemLine) | This is related to Buying Details / Selling Details. | Items on these orders need to be marked as “Sold” and assigned to the relevant Cost Of Sales Account / Income Account. |
| Error 12101 UnitPriceNotValid: UnitPrice must be a positive number Lines[2].UnitPrice | These invoices have a negative amount on them for Rounding. | Adjust the orders with the negative rounding to bring the line to positive. |
| Warning 4327 ValidationWarning: SaleEvent_DuplicateSale EventId:(SaleEvent) | This usually occurs if the order has been manually added in MYOB. | If the invoice exist in MYOB, mark this error as successfully export or delete the MYOB record and re-export. |
| Error 25002 InsufficientItemQuantity: Insufficient item quantity to complete transaction Lines[0].Item | Stock for the product is 0 or less. | You can remove the “I Inventory This Item” mark on these items in MYOB or adjust the QTY on hand to be greater than 0. |
| Error 4226 ValidationError: BusinessEvent_CategoryRequired CategoryId:(SaleEvent) | Category tracking required setting needs to be updated. |
The company file preference “Turn on Category Tracking: Categories
are [Required/Not Required]” on all transactions MUST be set to
Not required. In MYOB, go to Setup > Preferences
> System to change. |
| Product “XXX” does not exist in MYOB | A matching product cannot be found in MYOB. | Ensure that the product is in MYOB. |
| Error 4237 ValidationError: BusinessLine_AccountRequired AccountId:(SaleEventItemLine) Error 4340 ValidationError: SaleEventLine_ItemSoldRequired ItemId:(SaleEventItemLine) | Income/Asset/Cost of Sales Accounts on product is not linked in MYOB. |
In MYOB go to Accounts > Accounts List find the Asset, Income
and Cost of Sales accounts being used on Maropost Commerce’s product
and ensure the accounts are linked in MYOB. To check account linking,
click on the account in the accounts list, go to Details tab. This
page tells you if the account is linked or not. If it’s not, it needs
to be linked to a MYOB account. If the error is not cleared after linking your accounts in MYOB, please request for your product import temp data to be cleared by our integrations support team and try re-exporting the failed orders. |
| Error 4238 ValidationError: BusinessLine_AccountRequired Error 4342 ValidationError: SaleEventLine_ItemSoldRequired | Item on the invoice is missing its account mapping (usually sales account) and it is also not marked as sold. | Map the account on the product and mark it as Is Sold to rectify the error. |
| Error 100 Required: Lines[0].Location.UID Lines[0].location must be specified for inventoried item | Maropost Commerce does not support MYOB’s multiple warehouses. | Disable this setting in MYOB and the orders will export correctly during the next sync. |
|
"Name": "ValidationError", "Message": "ReceivePaymentEvent_LineSaleEventDoesNotBelongToCard", "AdditionalDetails": "Lines:(ReceivePaymentEvent)" |
The MYOB customer for the order does not match the original customer on the order |
MYOB requires that the customer on the payment is the same as on the order. Change the customer on the order in MYOB back to the original customer. To prevent this dont change the customer until the payment has been applied.
|
|
"Name": "ValidationWarning", "Message": "ReceivePaymentEvent_PaymentDetailsBlank", "AdditionalDetails": "PaymentBankingDetails:(ReceivePaymentEvent)"
|
This usually means the order or invoice does not yet exist in MYOB for the payment to be added to. |
Fix any order export errors to ensure order has been processed successfully to MYOB. The payment will retry once order is exported. |
|
"Name": "SerializationError", "Message": null, "AdditionalDetails": "Error converting value \"\" to type 'System.Guid'. Path 'Customer.UID'
|
This error occurs when the customer does not exist in MYOB and an order or invoice cannot be created as a result. |
Check you are creating customer cards on app settings page and if not add the missing customer with identical email to MYOB. After adding to MYOB click Sync button on app settings page. MYOB also does not allow special characters on customer cards. If the phone number on Shopify contains a # this will prevent it from being created on MYOB. You can create the customer manually on MYOB or contact us to remove hashes from what we have captured on Shopify. |
|
"Name": "ValidationError", "Message": "BusinessLine_AccountRequired", "AdditionalDetails": "AccountId:(SaleOrderFreightLine)"
|
This error relates the tax code used for freight. |
Check in your MYOB account you have freight tax code set up: https://www.myob.com/au/support/myob-business/sales/entering-freight-costs-in-myob-business |
|
"Name": "ValidationError", "Message", "SaleOrderLine_ItemSoldRequired", "AdditionalDetails", "ItemId:(SaleOrderItemLine)"
|
This error relates to an item in MYOB that is on and order line. |
Check the item in MYOB that it has the Item Sold checkbox selected as otherwise we cannot add it as an order line in MYOB. |