Syncing issues between BuildOps and QuickBooks can occur due to data mismatches, duplicate records, deleted entries, account mapping differences, character limits, or manual edits. This article walks through the most common syncing errors and how to resolve each one.
Additional causes of syncing issues include closed accounting periods and mismatched reference IDs, which can also lead to failures during the syncing process.
How syncing works: Post vs. Export
Syncing in BuildOps is a two-step process. A record that shows as Posted has not yet synced to QuickBooks — you must also trigger the export step.
Post — saves the record and marks it ready for export. This does not send data to QuickBooks.
Export/Sync — sends the posted record to QuickBooks. Always click the export action after posting to trigger the sync.
If a record shows as Posted but has not appeared in QuickBooks, check whether the export step was completed.
Fields or actions greyed out? If a record is in Approved or Posted status, some fields and the Edit button may be locked. Unapprove or unpost the record first (if your permissions allow), or contact BuildOps Support to request a status reset before re-triggering the sync.
1. Invoice Syncing Issues
Invoice sync failures typically happen when an invoice is deleted or moved in QuickBooks after it was already synced from BuildOps.
If the invoice was deleted in QuickBooks:
Contact the BuildOps Support Team to request a Reference ID (RefID) reset for the affected invoice.
Once the RefID is reset, retry the sync.
If the invoice was moved in QuickBooks:
Open QuickBooks and locate the invoice.
Verify that the invoice is assigned to the same job/project, property, and customer as it appears in BuildOps.
If it was moved to a different entity, move it back to the original job/project, property, and customer.
Retry the sync from BuildOps.
2. Property Syncing Issues
If a property record fails to export to QuickBooks, the issue is often caused by a duplicate property name in BuildOps or a stalled record export.
Navigate to the affected property record in BuildOps.
Check for any other property records with the exact same name. Duplicate names will prevent a successful sync — rename or remove the duplicate if one exists.
Open the property record and select Edit, make no changes, then click Save. This retriggers the record export to QuickBooks.
If the sync still fails after completing the steps above, contact BuildOps Support for further assistance.
3. Pre-Existing Payments in QuickBooks
When a payment already exists in QuickBooks, syncing the same record from BuildOps will fail to prevent duplicate entries.
To resolve this:
Locate the payment record in BuildOps that is failing to sync.
Use the Bypass option on the payment. The payment status will update to Bypassed.
The record will no longer attempt to sync, preventing duplicate entries in QuickBooks.
Note: The Bypass option is intended for records that already exist in QuickBooks and do not need to be re-created. Use it only when you have confirmed the payment exists on the QuickBooks side.
4. Vendor Document Number Errors
QuickBooks Online requires a unique Vendor Document Number for each receipt per vendor. If a receipt shares a document number with an existing entry for the same vendor, the sync will fail.
To resolve this:
Open the affected receipt in BuildOps.
Locate the Vendor Document Number field.
Update the number to a unique value that has not been used for that vendor in QuickBooks.
Save the changes and retry the sync.
Tip: Use a consistent naming convention (e.g., adding a date suffix) to avoid duplicate document numbers going forward.
5. Expense GL Account Mismatches
If the Expense GL accounts assigned to items in BuildOps do not match the corresponding accounts in QuickBooks, invoice syncing will fail.
To resolve this:
In QuickBooks, review the Expense GL account settings for the affected items.
In BuildOps, update the corresponding items to match the Expense GL accounts found in QuickBooks.
If you need to make changes in QuickBooks, switch to single-user mode first to avoid conflicts with other users.
Once the account mappings are aligned, retry the sync.
Note: GL account mismatches are one of the more common causes of ongoing sync failures. If you experience repeated invoice sync errors, check GL mapping first before escalating.
6. Deleted Receipts That Won't Re-Sync
When a receipt that was previously synced to QuickBooks is deleted in BuildOps and then re-created, the backend accounting Reference ID (RefID) from the original sync is often retained. This prevents the new receipt from syncing until the RefID is cleared.
To resolve this:
Identify the receipt that is failing to re-sync.
Contact the BuildOps Support Team and request a RefID reset for the affected receipt.
Once the RefID has been reset, retry the sync.
Additional Steps for Correcting and Re-Exporting Receipts
Set the receipt status to "Pending" and "Not Synced" if it is blocking further actions.
Delete the incorrect receipt from BuildOps.
Create a new receipt with the correct details.
Re-export the corrected receipt to your accounting system. If the receipt was already exported, delete the existing version in your accounting system before re-exporting.
7. Payment Syncing Issues
Invoice Already Marked as Paid in QuickBooks: Payments may fail to sync if the invoice is already marked as paid in QuickBooks. To resolve this, either bypass the payment in BuildOps or delete the payment in QuickBooks and re-sync it.
Mismatched Customer Records: Payments may not sync if the customer names differ between BuildOps and QuickBooks. Ensure that the invoice and payment are associated with the same customer in both systems.
Unposted Payments: Payments saved but not posted in BuildOps will not sync. Always use the 'Save & Post Payment' option to trigger the sync.
8. Character Limit Violations
QuickBooks Online has character limits for fields like payment numbers, customer names, or property names. If these fields exceed the limits, the sync will fail. Shorten these fields to comply with QuickBooks' requirements. For example, product codes must not exceed 30 characters. Ensure all fields meet these specific limits before retrying the sync.
9. Inactive Classes or Items in QuickBooks
Errors may arise if a class or item associated with a transaction is inactive in QuickBooks. Reactivate the class or item to resolve the issue.
10. Web Connector Not Running
Confirm QuickBooks is open and the correct company file is active on the designated sync computer
Open the Web Connector and check for authentication errors or stale credentials — sign out and back in if prompted
Click Update Selected in the Web Connector to manually trigger a sync attempt
If QuickBooks is open in multi-user mode, switch to single-user mode, run the sync, then switch back
Restart both QuickBooks and the Web Connector if the issue persists
If the Web Connector still fails to connect after restarting, contact BuildOps Support to review the connection configuration
11. Closed Accounting Period in QuickBooks
If the date on an invoice or PO falls within a period that has been closed in QuickBooks, the sync will be rejected. This is one of the most common causes of repeated invoice sync failures.
To resolve this:
In QuickBooks Desktop, go to Edit > Preferences > Accounting > Company Preferences and check the Closing Date. In QuickBooks Online, go to Settings > Advanced > Accounting.
If your invoice or PO date falls on or before the closing date, the sync will be blocked.
Update the date on the affected record in BuildOps to fall within an open period, then retry the sync.
Alternatively, contact your QuickBooks admin to temporarily open the period for the affected date range.
If you experience repeated invoice sync failures and GL account mapping appears correct, check the closing date in QuickBooks — a closed period is often the underlying cause.