Common Sync Errors: QuickBooks Online

Prev Next

Below, you will find a list of the most common errors that we receive when trying to sync bills to QuickBooks Online as well as instructions in the dropdown detailing how to resolve them.


Type: ValidationFault. Code: 6140. Detail: Duplicate Document Number Error : You must specify a different number. This number has already been used. DocNumber=XXXXXX is assigned to TxnType=Bill with TxnId=XXX.

A duplicate Invoice Number already exists within QuickBooks Online.

Solution: Remove the duplicate transaction from Quickbooks or change the Invoice Number within MakersHub.

Type: ValidationFault. Code: 6210. Detail: The account period has closed and the account books cannot be updated through through the QBO Services API. Please use the QBO website to make these changes..

The accounting period has been closed in QuickBooks.

Solution: Re-open the accounting period  or adjust the date of the invoice to be within an open period.

Type: ValidationFault. Code: 2500. Detail: Invalid Reference Id : Account assigned to this transaction has been deleted. Before you can modify this transaction, you must restore XXXXXXXX (deleted)..

The account in Quickbooks has been deleted or marked as inactive.

Solution: Reactivate/recreate Account within QuickBooks or change the account on the transaction within MakersHub.

Type: ValidationFault. Code: 2500. Detail: Invalid Reference Id : Vendor assigned to this transaction has been deleted. Before you can modify this transaction, you must restore XXXXXXX(deleted-1)..

Vendor has deleted or made inactive within QuickBooks.

Solution: Reactivate/readd vendor to QuickBooks or update vendor name on transaction to new vendor.

HTTP Error: Timeout was reached (CURLE_OPERATION_TIMEOUTED): Operation timed out after 30001 milliseconds with 0 bytes received

Server has timed out.

Solution: QuickBooks Server may be experiencing technical difficulties please try again after a few minutes.

Type: ValidationFault. Code: 2500. Detail: Invalid Reference Id : Customer assigned to this transaction has been deleted. Before you can modify this transaction, you must restore XXXXXX (deleted)..

Customer/Job has deleted or made inactive within QuickBooks.

Solution: Reactivate/readd Customer/Job to QuickBooks or update Customer/Job name on transaction to new Customer/Job.

Type: ValidationFault. Code: 6000. Detail: Business Validation Error: You can't use an Accounts Payable account on the detail portion of a Bill..

There is an Account Receivable or Account Payable Account selected at line level.

Solution: Update the account at line level to be another type of account that is not AR or AP.

Unable to Establish Supplier Link

This error usually occurs when a bill is assigned to a vendor that MakersHub was not able to create and thus does not exist in your QuickBooks.

Solution: First check if this Vendor already exists in your QuickBooks as an active or inactive vendor. Then check your Customer list as well as QuickBooks does not allow for vendor name and customer names to be the same.  

HTTP Error: HTTP/2 401#Gpi2022!

HTTP error’s stem from one of two causes, either MakersHub sent the update to QuickBooks and did not receive a response that the bill was able to sync. In this scenario, you can click on the Blue Button and MakersHub will try once more to sync the bill.

If the bill does not sync, you most likely have an Authentication Error. This typically happens if the Admin that authorized the connection is removed from the QuickBooks account or their permissioning was changed. To fix this, we need to disconnect MakersHub from your QuickBooks and reconnect. This is a quick process and only takes a few minutes.

Unable to Obtain Access Token

This error indicates that the previous user who authorized the connection between MakersHub and QuickBooks has been removed or their permissions reconfigured. The authorization between MakersHub and QuickBooks would then need to be re-configured by a new user with Admin access. This only takes 1 minute and instructions on how to resolve this issue can be found in the link provided.