3rd Party: QuickBooks connections failing due to TAX_RATE and TAX_CODE with QueryValidationError
View the provider incident record →Current answer
Fivetran experienced a minor incident: 3rd Party: QuickBooks connections failing due to TAX_RATE and TAX_CODE with QueryValidationError. Resolved on Sep 23, 2026.
The notice publication date does not establish the outage start. Provider resolved: .
Looking for an update now? Check the current status, or follow Fivetran for future changes.
Provider notice timeline
Affected Components
QuickBooks
Incident Timeline
Resolved
This incident has been resolved. We have observed that instance rates are returning to normal levels and affected connectors are syncing successfully.
Incident Summary
Description:
We identified an issue for QuickBooks connectors, which resulted in syncs failing with a "Failed to sync 2 endpoints: TAX_RATE: The request cannot be fulfilled due to bad syntax; TAX_CODE: The request cannot be fulfilled due to bad syntax" error.
Timeline:
This issue began on September 23, 2026 at 00:10 UTC and was resolved on September 23, 2026 at 07:25 UTC.
Cause:
QuickBooks (the source) stopped returning the Active field in its TaxRate and TaxCode API responses. Without that field, QuickBooks rejected Fivetran's query as invalid (QueryValidationError: value true is not valid for property 'Active'), causing syncs to fail for the TAX_RATE and TAX_CODE tables.
Resolution:
We deployed a hotfix that skips the TAX_RATE and TAX_CODE tables when this error occurs and surfaces a warning in the connector dashboard instead of failing the sync. The fix was rolled out to all affected QuickBooks connectors, and no further failures were observed after rollout. We have opened a support case with QuickBooks to address the underlying API issue on their end.
Incident Summary
Description:
We identified an issue for QuickBooks connectors, which resulted in syncs failing with a "Failed to sync 2 endpoints: TAX_RATE: The request cannot be fulfilled due to bad syntax; TAX_CODE: The request cannot be fulfilled due to bad syntax" error.
Timeline:
This issue began on September 23, 2026 at 00:10 UTC and was resolved on September 23, 2026 at 07:25 UTC.
Cause:
QuickBooks (the source) stopped returning the Active field in its TaxRate and TaxCode API responses. Without that field, QuickBooks rejected Fivetran's query as invalid (QueryValidationError: value true is not valid for property 'Active'), causing syncs to fail for the TAX_RATE and TAX_CODE tables.
Resolution:
We deployed a hotfix that skips the TAX_RATE and TAX_CODE tables when this error occurs and surfaces a warning in the connector dashboard instead of failing the sync. The fix was rolled out to all affected QuickBooks connectors, and no further failures were observed after rollout. We have opened a support case with QuickBooks to address the underlying API issue on their end.
Sep 23, 2026 at 8:43 AM UTC
Monitoring
We have deployed a workaround for this issue: the TAX_RATE and TAX_CODE tables are now skipped, and a warning is shown in the UI.
We will continue to monitor all affected connectors until they resume their normal sync functionality.
Next Expected Update: 3 hours
We will continue to monitor all affected connectors until they resume their normal sync functionality.
Next Expected Update: 3 hours
Sep 23, 2026 at 7:29 AM UTC
Identified
We have identified that this issue was caused by the source not returning the Active object for the TaxRate and TaxCode objects, resulting in an invalid query response. As a workaround, these tables will be skipped, and a dashboard warning will be surfaced. We have also reached out to QuickBooks support, as this issue is not currently listed on their status page: https://status.quickbooks.intuit.com/ .
Sep 23, 2026 at 4:55 AM UTC
Identified
We have identified an issue where QuickBooks connectors are failing with a "Failed to sync 2 endpoints: TAX_RATE: The request cannot be fulfilled due to bad syntax; TAX_CODE: The request cannot be fulfilled due to bad syntax" exception. We are currently investigating in more detail.
Next Expected Update: 1 hour
Next Expected Update: 1 hour
Sep 23, 2026 at 4:53 AM UTC
Identified
The issue has been identified and we are working to resolve it.
Sep 23, 2026 at 4:40 AM UTC
Was your business affected by this Fivetran outage?
Follow Fivetran and route available status alerts to email or a team channel.