If an item fails to publish from Dext to QuickBooks Online, an error message will appear on the item. This article covers the most common errors, what causes them, and how to resolve them.

Common causes of publishing errors include issues with tax settings, missing fields, or integration configurations.

When an item fails to publish, a yellow status badge appears on the item row. Hover over the badge to see the error message, or open the item to see it in the Please resolve these issues panel on the Details page.

If your account uses approval workflows, items go through approval before publishing. A failed item will appear in the Approvals tab rather than the Inbox. If editing is not allowed in the approval workflow, the item details are read-only in this state - to edit the item, select Cancel request to return it to the Inbox, make your changes, request approval again, and then publish.

These errors appear when your QuickBooks Online account is inactive or restricted because of a billing issue.

See How to reconnect or change your accounting software in Dext.

QuickBooks Online allows only one currency per transaction. All of the following must use the same currency: the transaction, the supplier, the payment account, and the category.

To resolve it, create the relevant entity - for example, a category or supplier - in the correct currency in QuickBooks Online. Then refresh your integration data in Dext to sync the change, assign the correct entity to the item, and publish again.

See How to refresh your accounting software data in Dext.

This error appears because QuickBooks Online requires a 0% (exempt) tax code to publish documents with no tax amount, and no default exempt tax code has been configured in Dext.

There are 2 ways to resolve it:

Option 1 - Set a default exempt tax code in Dext:

Ensure that a default tax rate is selected in the dropdown to avoid errors related to missing tax rates.

Option 2 - Apply a tax rate manually to the item:

This error means the document number already exists in QuickBooks Online. This is common when publishing directly as Cheque or Credit card, where duplicate references aren't allowed.

To resolve it, either change the document number on the item in Dext, or update the duplicate warning settings in QuickBooks Online:

Alternatively, change the Publish to destination on the item to Bill, which doesn't enforce unique reference numbers in the same way.

This error means a customer, supplier, or employee already exists in QuickBooks Online with the same name as the supplier on the item. QuickBooks Online won't accept a supplier and customer with the same name.

To resolve it, either change the supplier name on the item in Dext or change the matching customer name in QuickBooks Online. If you have multiple supplier entries with similar names in Dext, merge them first before making changes in QuickBooks Online.

See How to manage suppliers in Dext.

This error has 2 common causes:

This error appears because QuickBooks Online requires a default tax rate to be configured before publishing any tax information. Go to Business settings > Connections, select Manage next to QuickBooks Online, then select Settings. Turn on Publish tax data and complete the tax rate fields. Then publish the item again.

This error means the QuickBooks Online user account used for the integration doesn't have sufficient permissions. Reconnect the integration using a QuickBooks Online Admin user account.

This error usually means the QuickBooks Online integration has expired. Integrations expire periodically and need to be refreshed.

To resolve it, reconnect Dext to QuickBooks Online, then publish the item again. See How to reconnect or change your accounting software in Dext.

This error appears when there's a conflict with a previously published item in QuickBooks Online. Clear the item's publishing data in Dext and republish. Before doing so, check for duplicates in QuickBooks Online and delete or void any that exist to keep your records clean.

See How to republish an item.

This error appears when attempting to publish a credit note to ApprovalMax. ApprovalMax doesn't support credit notes published from Dext.

To resolve it, open the item and change the Integration field to QuickBooks Online or Xero, then update the Publish to destination to a supported credit note destination.