Use the dropdowns below to troubleshoot common errors that may be encountered when posting data via AroFlo's cloud-based and desktop accounting integration links.
Local Hosted Integration Users
Please contact AroFlo Customer Support for assistance.
Xero
The Ipayable cannot be applied
Cause |
Solution |
|---|---|
| Your AroFlo integration link is configured to post Invoices / Credit Notes to Xero as a 'DRAFT' or 'SUBMITTED' document. | Go to your AroFlo Integration Menu > Integration Entities and change the Invoice Status to 'AUTHORISED'. |
Invoice not valid state for modification
Cause |
Solution |
|---|---|
| The invoice already exists in Xero and the AroFlo integration link has not been configured to allow invoice updates. |
Go to your AroFlo Integration Menu > Integration Entities and change the Invoice Status to 'AUTHORISED'. If the invoice has been voided in Xero then attempting this process after adjusting the status will produce the same error. To check if the invoice has been voided in Xero: Go to the Sales Overview of the Purchases Overview under the Business tab, then click on 'See All' from here, click on the 'All' tab and tick the 'Include Deleted & Voided' tick box before searching for the invoice number. |
Document could not be found
Cause |
Solution |
|---|---|
| Posting payments to Xero but the invoice does not yet exist. | Post the invoice to Xero first, then post payments. |
The contact with the specified contact details has been archived
Cause |
Solution |
|---|---|
| Attempting to post data where the customer has been archived in Xero. |
To restore the applicable contact in Xero: Locate the customer or supplier assigned to this sale in Xero, and click the Restore Contact button. Attempt to re-post the data. If the requirement is to keep the contact Archived, then you will need to re-map the client or supplier via Manage > Integration > Client Setup or Manage > Integration > Supplier Setup. |
You cannot save this transaction using an inventory account type
Cause |
Solution |
|---|---|
| Posting Purchase Orders or COGs to 630-Inventory account |
XERO reserves the account 630-Inventory for its own uses and cannot be used for integration. In order to track cost of inventory in XERO you will need an independent 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. |
Xero Timesheet Integration - Post contains no data
Cause |
Solution |
|---|---|
| Posting Timesheets to Xero results in the error 'This post contains no data'. | Reauthorise the company token and authorise payroll access. |
Xero Timesheet Integration - TrackingItemID is required
Cause |
Solution |
|---|---|
| Posting Timesheets to Xero results in the error 'TrackingItemID is required' | In Xero, change the timesheet category to none. |
For more specific information regarding troubleshooting your Xero software directly, please see the help resources available on their webpage: Xero
MYOB
[####] CardId:(SalesEvent)
Cause |
Solution |
|---|---|
| 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)
Cause |
Solution |
|---|---|
| MYOB is expecting a "Category" to be defined for the Invoice that is being posted. | This is an 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)
Cause |
Solution |
|---|---|
| MYOB is expecting a "Job" to be defined for the Invoice line items that are being posted. | This is an 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.
Cause |
Solution |
|---|---|
| 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
Cause |
Solution |
|---|---|
| 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'
Cause |
Solution |
|---|---|
| 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)
Cause |
Solution |
|---|---|
| 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
Cause |
Solution |
|---|---|
| Attempting to post data with a '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) |
For more specific information regarding troubleshooting your MYOB software directly, please see the help resources available on their webpage: MYOB
QuickBooks Online
Code: 6000 Message: A business validation error has occurred while processing your request
Validation Error: We're sorry, QuickBooks encountered an error while calculating tax. Try reselecting the tax rate or re-entering the product/service item and saving the form again.
Cause |
Solution |
|---|---|
|
Attempting to post to an incorrect Tax Code, likely trying to post a Purchase against the ‘GST’ code or a Sale against the ‘GST on non-capital’ code. This error can also occur if the Tax Code is too long (Limit: 20 characters) or has been renamed such that the square bracketed component is no longer complete. EG GST [5, instead of GST [5,3] |
Ensure tax codes are correctly mapped and used in QuickBooks depending on the accounting method being used at the time. Invoices: Use Tax Code ‘GST’ Bills: Use Tax Code ‘GST on non-capital’ Ensure all Tax Codes contain their correct and complete square bracketed component. EG GST [5,3] |
For more specific information regarding troubleshooting your QuickBooks software directly, please see the help resources available on their webpage: Intuit QuickBooks