Sync error:
Error processing Customer: String length is either shorter or longer than supported by specification - String length specified does not match the supported length. Min:0 Max:30 supported. Supplied length:39
Category: Customer
Cause: The customer’s name or phone number has more than 30 characters, which exceeds QuickBooks’ maximum length for that field.
Resolution: In BuildOps, edit the customer’s phone number so it is 30 characters or fewer, save, then re-sync to QuickBooks.
Sync error (examples):
CustomerProperty 'xxxxx xxxxxxx xxxxxx' companyName exceeds 41 charactersCustomer 'xxxxx xxxxxxx xxxxxx' customerName exceeds 41 charactersThe string "Client Name: xxxxxxxxx xxxxx xxxx" in the field "Addr1" is too longCategory: Invoice
Cause: QuickBooks enforces character limits on name and address fields, and the customer name or address coming from BuildOps is longer than the allowed limit.
Resolution:
In BuildOps, shorten the customer name or address line mentioned in the error so that it fits within QuickBooks’ character limit (for many fields, 41 characters or fewer).
Save the record and re-sync.
You can reference Intuit’s limits here: Character limitations for fields in QuickBooks.
Sync error:
A related transaction object specified by the ID xxxxxxx-xxxxxx is already in use, or failed to acquire the lock for this object.
Category: Invoice
Cause: A related record (typically a customer or vendor) is currently open in QuickBooks, so the integration can’t acquire the lock it needs to update the transaction.
Resolution:
Try re-syncing; if the record was closed in the meantime, the sync may succeed.
If not, in QuickBooks close any open customer windows (for invoices or payments) or vendor windows (for receipts), then re-sync from BuildOps.
Sync error:
Product 'xxxxxxx': GL Expense Account is required! Please correct the error above and try syncing againCategory: Invoice
Cause: The item used on the invoice in BuildOps is missing the GL Expense Account from the item list. All items must have both income and expense GL accounts to sync successfully.
Resolution: Check all items used on the invoice and make sure they have GL Expense Account at the item level from the item list, editing the item will resync it to QB, then re-sync the transaction that was failing.
Sync error:
Product 'xxxxxxx': GL Income Account is required! Please correct the error above and try syncing again
Category: Invoice / Item
Cause: The item used on the invoice in BuildOps is missing the GL Expense Account from the item list. All items must have both income and expense GL accounts to sync successfully.
Resolution: Check all items used on the invoice and make sure they have GL Expense Account at the item level from the item list, editing the item will resync it to QB, then re-sync the transaction that was failing.
Sync error: 6000: A business validation error has occurred… Please make the parent customer active first. Then you can make this sub-customer active.
Category: Invoice / Customer
Cause: The invoice is linked to a sub-customer or property whose parent customer is inactive or not correctly set up in QuickBooks Online.
Resolution:
In QuickBooks Online, open the parent customer and make sure it is active.
Ensure the property or sub-customer in BuildOps is linked to the correct billing (parent) customer in QuickBooks.
Save your changes in QuickBooks, then re-sync the invoice from BuildOps.
Sync error:
6000: A business validation error has occurred… Make sure all your transactions have a GST/HST rate before you save.
Category: Receipt / Bill (Canadian accounts)
Cause: For Canadian companies, QuickBooks Online requires a tax rate on every taxable line, and the tax-exempt / default tax setup isn’t fully configured for the items or transactions coming from BuildOps.
Resolution:
In QuickBooks Online, review your tax codes and tax-exempt settings and ensure a valid GST/HST rate is available for taxable items.
If taxes should apply, assign the appropriate tax code to the affected items/lines and save.
If you’re unsure how your tax-exempt code is configured, contact BuildOps Support so we can confirm the integration settings, then re-sync the transaction.
Sync error:
Bad Request - 6210 - Account Period Closed, Cannot update through services API. The account period has closed and the account books cannot be updated through the QBO service API. Please use the QBO website to make these changes.
Category: Invoice / Receipt / Item
Cause: Cause: The transaction is trying to sync to a date that is in a closed accounting period in QuickBooks (the bill date is on or before the company’s closing date).
Resolution:
In BuildOps, change the transaction date to a date after the closing date, then sync again; or
Bypass this transaction in BuildOps and enter it directly in QBO with the desired historical date.
Sync error:
Object already exists(when syncing a receipt or bill)
Category: Receipt / Vendor
Cause: The vendor in QuickBooks Online is missing the name in one of the two key fields—Vendor Display Name and Company Name—which QBO expects to match for that vendor.
Resolution:
In QuickBooks Online, open the vendor record mentioned in the error.
Enter the vendor name in both the Vendor Display Name and Company Name fields, then save.
Return to BuildOps and re-sync the receipt or bill.
Sync error:
Validation Error BOE00040501001 - Product 'XXXX': GL Income Account is required! Please correct the error above and try syncing again.
Category: Item / Invoice / Receipt
Cause: The product or service item in BuildOps is missing a GL Income Account, which QuickBooks Online requires for items used on transactions.
Resolution:
In BuildOps, open the item named in the error.
Add a valid GL Income Account that exists in your QuickBooks Online chart of accounts.
Save the item in BuildOps, let it sync to QBO, then re-sync the invoice or receipt that was failing.
Sync error:
There is a discrepancy in GL accounts between the BuildOps item and the QuickBooks item. Please confirm both items are the same and correct if they misaligned before syncing the invoice.
Category: Item / Invoice / Receipt
Cause: The Income and/or Expense accounts on an item in BuildOps don’t match the accounts on the corresponding item in QuickBooks Online. QBO rejects the transaction because the configuration is inconsistent.
Resolution:
In both BuildOps and QuickBooks Online, open the same item referenced in the error.
Decide which system has the correct GL mapping, then update the other system so the Income and Expense accounts match.
Save your changes and re-sync the invoice or receipt from BuildOps.
Sync error:
Bad request - 6070 - Amount calculation incorrect in the request. Amount is not equal to unit price * qty supplied…
Category: Invoice
Cause: There is a rounding or calculation mismatch on one or more lines— the line amount sent from BuildOps does not exactly match unit price × quantity the way QuickBooks Online expects.
Resolution:
In BuildOps, open the invoice and review the affected line(s).
Check that quantity × unit price = line amount with no extra rounding or manual overrides.
Correct any discrepancies, save the invoice, and re-sync to QuickBooks Online.
Sync error:
There was an error when syncing with your QuickBooks Online instance. 620: TxnID Cannot Be Linked - TxnID Cannot Be Linked: xxxx
Category: Payment / Invoice
Cause: The payment is trying to link to a QuickBooks transaction that cannot accept the link—for example, a payment applied to a sub-customer that isn’t set to “bill parent,” or the target invoice is in a state that QBO won’t allow further linking.
Resolution:
In QuickBooks Online, open the sub-customer (or child job/property) record and ensure “Bill with parent” (or equivalent “bill parent customer”) is enabled where appropriate.
Confirm the target invoice or bill is still open and in a valid state to receive the payment.
Save any changes, then re-sync the payment from BuildOps.
Sync error:
“Duplicate Document Number” (often on receipts with Vendor Document Number)
Category: Receipt / Vendor
Cause: QuickBooks Online requires a unique document number per vendor. If the same Vendor Document Number already exists on another receipt or bill for that vendor in QBO, the new receipt from BuildOps will fail to sync.
Resolution:
In QuickBooks Online, search for the Vendor Document Number shown in the error for that vendor to confirm the existing record.
In BuildOps, edit the receipt and change the Vendor Document Number to a unique value that isn’t already used for that vendor.
Save the receipt in BuildOps and re-sync to QuickBooks Online.
Sync error (customer records):
Messages likeA business validation error has occurred… Unexpected user errorwhen creating or updating a customer, often tied to name mismatches
Category: Customer
Cause: The Company Name and Customer Display Name in QuickBooks Online don’t match or conflict with how the customer is set up in BuildOps, or there are duplicate customer records between the two systems.
Resolution:
In QuickBooks Online, open the customer profile mentioned in the error.
Make sure the Company Name and Customer Display Name are consistent and match how the customer is named in BuildOps.
Check for duplicate customer records in QBO with the same or very similar names and merge or clean them up as needed.
Save your changes and re-sync the customer or related transaction from BuildOps.