I’ve spent the last few months auditing broken billing pipelines for agencies. If your native QBO or Xero integration is silently failing, rejecting invoices, or creating reconciliation nightmares, it almost always comes down to one of these 6 structural edge cases.
Here is exactly why they break, and how to bypass them using custom webhook middleware (like Make or Zapier).
1. Nested Discount Arrays Collapsing
The Problem: When sales reps apply custom discounts at the line-item level in HubSpot, the native connector often collapses the array, wiping out the line items completely in QBO/Xero.
The Fix: Catch the HubSpot Deal payload via webhook. Pass it through an Array Iterator to isolate the discount, then dynamically map the discount as its own distinct “negative” line item before pushing to the QBO/Xero REST API.
2. The Currency Rounding Mismatch ($0.01 failures)
The Problem: HubSpot and QBO calculate fractional taxes differently. A HubSpot invoice might total $1,000.00, but QBO calculates it as $1,000.01. QBO instantly rejects the sync due to unbalanced books.
The Fix: Insert a Math/Formatter step in your middleware. Isolate the subtotal and force a dynamic recalculation that matches QBO’s exact global rounding logic before sending the POST request.
3. Partial Refunds Not Syncing
The Problem: When a deal is partially refunded in HubSpot, the native sync does not automatically generate a corresponding Credit Memo in the accounting software.
The Fix: Set a webhook listener for a custom Deal property (e.g., “Refund Status”). When triggered, fetch the associated invoice ID and push a “CreditMemo” JSON payload directly to the ERP to balance the books.
4. Duplicate Customer Records
The Problem: The native bidirectional sync frequently creates duplicate contacts if there is a slight naming variation (e.g., “LLC” vs “Inc”).
The Fix: Disconnect the native two-way contact sync. Route the payload through a custom matching router that strictly searches QBO/Xero by domain name or verified email first. If matched, update; if null, create.
5. Deleted Deals Leaving Orphaned Invoices
The Problem: A sales rep deletes a closed-won deal in HubSpot by accident, but the invoice in QBO remains active and open, inflating projected revenue.
The Fix: Set a webhook to listen specifically for HubSpot “Deleted Object” events. Pass the Object ID to search your ERP for the linked invoice and automatically trigger a “Void” status update.
6. Token Expiry & Rate Limits
The Problem: Standard REST API connections drop payloads when OAuth tokens expire or API rate limits are hit, deleting the invoice data into the void.
The Fix: Build a dedicated error-handler (“Break” directive) in your middleware. If the QBO/Xero API throws a 429 or 401 error, the system stores the incomplete payload in an incomplete executions queue and automatically retries it 15 minutes later once the token refreshes.
Hope this saves someone an 11:00 PM headache. If anyone is currently stuck on the exact JSON mapping for any of these loops, drop a comment below and I’m happy to share the raw Make.com blueprints.