Connect HubSpot to QuickBooks

Sales runs in HubSpot. The books are in QuickBooks. Without a link, a rep pings finance every time a deal closes, finance re-keys the line items, and the "closed revenue" number in HubSpot and the invoiced total in QuickBooks slowly drift apart.

• A closed-won deal creates a QuickBooks invoice from the deal's line items, with products, quantities, and prices carried across
• Companies are matched on a stored QuickBooks ID, falling back to a normalized name and domain, so a repeat customer is never duplicated
• When QuickBooks records a payment, the deal shows paid, partially paid, or overdue, and the paid date is set
• An approval step can hold an invoice over a threshold or with a non-standard discount before it posts

The deal-to-invoice flow most teams turn on first.

A closed-won HubSpot deal becomes a QuickBooks invoice, payment status back

Started by the polled deal trigger, safe to repeat on the deal ID.

1. 1
   Trigger: HubSpot New or updated deal, polled on the schedule you set, with a Filter that continues only for a closed-won stage. The flow then reads the deal's company, primary contact, and line items with Get association and a batch read.
2. 2
   Resolve company: find the QuickBooks customer by the company's quickbooks_customer_id property. If empty, search by normalized name and domain, and write the ID back on a match.
3. 3
   Idempotency: query QuickBooks for an invoice whose private note holds the deal ID. If one exists, stop.
4. 4
   Map lines: for each HubSpot line item, resolve the QuickBooks item by SKU, carry quantity and price, and apply the tax code from a lookup on the company's region.
5. 5
   Approval: if amount is over the threshold or the discount exceeds the limit, a Wait for form step sends finance an approval task. Otherwise continue.
6. 6
   Create invoice: QuickBooks Create Invoice with the lines, the customer, the terms, and the deal ID in the private note.
7. 7
   Write back: set the deal properties invoice_number and invoice_status = sent. A second flow polls QuickBooks with the Change Data Capture operation and, when a payment lands, updates the status and sets invoice_paid_date.

The starting map for the HubSpot deal to QuickBooks Invoice step.

• Invoices. A closed-won deal creates an invoice from the line items, with mapped items, prices, terms, and tax. (HubSpot to QuickBooks)
• Customers. A new or changed company creates or updates the QuickBooks customer, matched on a stored ID. (HubSpot to QuickBooks)
• Payment status. Payments and credit memos, picked up by polling, update the deal's invoice status and paid date. (QuickBooks to HubSpot)
• AR aging (optional). A nightly roll-up writes open AR and days overdue onto the company for CS and collections. (QuickBooks to HubSpot)

The same controls apply to this sync as to every other Neblex workload.

• Run history. Every invoice is a run with the deal, the resolved customer, the mapped lines, and the QuickBooks response. A failed run can be replayed from the step that failed, and the invoice check stops a second posting.
• Approval steps. Invoices over a threshold or with a non-standard discount wait for a named approver before they are booked.
• Scoped access. HubSpot uses a private app scoped to deals, companies, contacts, and line items. QuickBooks uses an OAuth connection to one company file.
• Environments. Build against a HubSpot test account and a QuickBooks sandbox company, then promote the same flow to production.