QuickBooks Online Sync Conflicts

How to troubleshoot sync conflicts

Updated over a week ago

This article lists common QuickBooks Online conflicts with some steps to try and resolve the conflicts.

Split line

Business validation error: you must fill out at least one split line.

This QuickBooks Online conflict occurs when you try to sync a transaction with QuickBooks where the transaction has no line items.

In order to correct this conflict, ensure that a line item is added to the transaction, then save the transaction.

You should now be able to proceed with your sync as normal.

Stale object error

You and XXXX were working on this at the same time. XXX finished before you did, so your work was not saved.

This QuickBooks Online conflict occurs when the item you were working on in Method (Invoice, Estimate, Customer record, etc.) was updated in QuickBooks Online before you completed your work. If you encounter this conflict, this is what you'll see (click to enlarge):

In order to correct this conflict, manually initiate a Sync.

Note: In a full sync, sometimes the transaction will be updated with line items from both transactions (the one entered in QuickBooks and the one entered in Method). It is important for users to manually double check line items after the sync takes place to ensure there are no duplicates or incorrect information.

Duplicate document number error

Duplicate Document Number Error: You must specify a different number. This number has already been used.

This QuickBooks Online conflict occurs when "Custom transaction numbers" is checked in QuickBooks Online. QuickBooks Online requires each transaction to have a unique transaction number associated with it.

In order to correct this conflict:

  1. In your QuickBooks Online account, navigate to the Company menu and choose Preferences.

  2. Select from the following:

    1. Sales Form Entry > Custom Numbers, or

    2. Vendors & Purchases > Purchase Orders

  3. Uncheck the Custom transaction numbers checkbox.

  4. Click Save.

  5. Next, navigate to the transaction that did not sync.

  6. Delete the existing transaction number, then save the transaction.

NOTE: The next time you sync, QuickBooks Online will automatically assign that transaction a new, unique number.

You should now be able to proceed with your sync as normal!

Invalid reference ID

Invalid reference ID

This QuickBooks Online conflict occurs when a related transaction or item has been deleted.

For example, Bob has 4 items in his QuickBooks Online and Method accounts (which have been previously synced). Bob marks one of the items inactive in QuickBooks, and then creates an invoice in Method using all four items. When he clicks Save, the invoice is synced to QuickBooks, but the inactive item is not yet synced to Method. That's when Bob encounters this conflict.

To correct this conflict, do one of the following:

If these steps do not fix the conflict, please contact Method Support.

Account period closed

Account period closed

This QuickBooks Online conflict occurs when a transaction is edited in Method, but the accounting period has already closed in QuickBooks Online. When the transaction is synced, you will receive this conflict.

In order to clear this conflict you will need to take one of two steps:

  • Temporarily change your accounting period in QuickBooks Online so the transaction isn't in conflict with the closing date, then perform another sync. Once the conflict clears, change your accounting period back to its original settings. For more information on changing your accounting period in QuickBooks Online, please refer to this Intuit Help Article.

    NOTE: Changing closing dates in this way is not an accounting best practice, and as such anyone trying to make these changes will require administrative privileges in QuickBooks Online.

  • You can also use the refetch option to clear this conflict. This will undo any changes that were made to the transaction before the last sync.

NOTE: If the changes absolutely must be made, refer to the first possible solution.

Once one of these steps has been taken, you should be able to sync as normal.

QuickBooks International configuration issues

QuickBooks International configuration issues.

There are currently known configuration issues when working with a non-U.S. QuickBooks account, which can result in validations faults.


If you are attempting to add a shipping cost to an invoice, you must first ensure that shipping is enabled in your QuickBooks account.

  1. Go to your QuickBooks account

  2. Click Settings > Sales

  3. Ensure that Shipping is On


If you are attempting to add a discount to an Invoice, you must first ensure that discounts are enabled in your QuickBooks account.

  1. Go to your QuickBooks account

  2. Click Settings > Sales

  3. Ensure that Discounts are On

Line items with blank item name value

You have no items or one or more of your amounts is not associated with an item. Please enter an item.

This conflict references line items on a transaction grid that do not have item names or descriptions. Method does not alone a completely blank line on transaction grids. To resolve this, either:

  • Delete the blank line item.

  • Add an item name or description to the item. 

NOTE: If you only add a description to the line item, you will not be able to set an amount or tax value. Method will not sync a description-only line item if it has tax or an amount.

BillableStatus Invalid Enumeration - Detail: Invalid
Enumeration: HAS_BEEN_BILLED

Could not add/edit the TimeTracking '8748'. Error Code: 2170 - BillableStatus Invalid Enumeration - Detail: InvalidEnumeration: HAS_BEEN_BILLED

QuickBooks API does not allow third-party Apps to directly set the TimeActivity.BillableStatus attribute to HasBeenBilled.
QuickBooks automatically sets the TimeActivity’s billable status to HasBeenBilled (not by a user’s action) once the time tracking is applied to an invoice object via Invoice.LinkedTxn.

If someone tries to manually update the BillableStatus to “HasBeenBilled“ in Method, it results in the below conflict.

We should not manually set TimeActivity BillableStatus to HasBeenBilled.

Did this answer your question?