Skip to main content

QuickBooks Online publishing error messages

A guide to common QuickBooks Online publishing errors in Dext what causes them and how to fix them.

Written by Alexander
Updated today

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

How to find the error message

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.

Note: After resolving an error, the message will still appear on the item. This is expected - the error is returned by QBO's API on each publishing attempt and only clears once a successful publish goes through. Publish the item regardless of the error still showing.


Your QuickBooks Online subscription appears to be inactive / restricted due to a payment failure

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

  1. Log in to QBO and resolve any outstanding billing issues.

  2. Confirm your account status is active.

  3. Reconnect Dext to QBO.

Note: It may take 24–48 hours for QBO to update the account status after payment is resolved.


Business validation error: you can only use one foreign currency per transaction

QBO 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 QBO. Then refresh your integration data in Dext to sync the change, assign the correct entity to the item, and publish again.


Dext is unable to find a 0% tax rate in order to publish this item

This error appears because QBO 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:

  1. Go to Business settings > Connections.

  2. Select Manage next to QuickBooks Online, then select Settings.

  3. In the Tax section, set a default exempt tax code.

  4. Publish the item again.

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

  1. Open the item from the Inbox.

  2. In the Tax field, select a compatible tax rate instead of Extracted amount.

  3. Publish the item again.


Duplicate document number error: this number has already been used

This error means the document number already exists in QBO. 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 QBO:

  1. In QBO, go to Settings > Account and settings > Sales and turn off Custom transaction numbers.

  2. Go to Advanced and turn off Warn if duplicate check/bill number is used.

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


Duplicate supplier name exists

This error means a customer, supplier, or employee already exists in QBO with the same name as the supplier on the item. QBO 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 QBO. If you have multiple supplier entries with similar names in Dext, merge them first before making changes in QBO.


Object not found

This error has 2 common causes:

  • A supplier or category was deleted in QBO while items were publishing - refresh your integration data in Dext to resync your lists. See How to refresh your accounting software data in Dext.

  • The QBO integration was disabled and re-enabled - refreshing lists will resync categories and suppliers, but payment method links are lost when an integration is disabled. You'll need to relink your payment methods to bank accounts in Dext after reconnecting.


One or more charge lines do not have a tax code associated with it

This error appears because QBO 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.


Sorry, the credentials used to authenticate your integration do not have the correct permissions

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


Something went wrong

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

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


Stale object error

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


We don't currently support publishing credit note/refund to invoice

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.

Did this answer your question?