QuickBooks Integration for Custom Home Builders: Invoices, Payments and Payouts
A useful QuickBooks Online integration keeps three records distinct: the invoice for the work, the payment applied to that invoice and the bank deposit that groups settled receipts. For a custom home builder, that distinction matters when one Stripe payout contains payments from several invoices. Treating the payout as another sale can duplicate revenue instead of explaining how money moved.
Start with the connection and explicit mappings
An authorized operator should open Foundation's dedicated QuickBooks Settings page to review the company connection, sync status and accounting health. The accountant settings view depends on existing permissions and assigned projects. Opening or refreshing these pages does not itself connect accounts, export records or change settings. Review access and current status before choosing an action.
For invoice export, Foundation requires an explicit active QuickBooks customer/job and invoice product/service item mapping. An invoice-linked payment also needs its canonical Foundation invoice and a mapped QuickBooks Invoice. The receipt account must be a valid active bank or Undeposited Funds account. Follow the specific setup requirements rather than expecting the integration to guess a customer, item or ledger account.
Confirm payment settlement before accounting
A homeowner signature approves a draw or change order; it is not a settled payment. Foundation records settled payment principal after Stripe confirms settlement, subject to source, mapping and accounting-period checks. For invoice-linked receipts, the QuickBooks Payment applies to the mapped Invoice. If that Invoice mapping is missing, Foundation does not substitute an unrelated income Deposit. A lender funding event is a separate workflow and should not be assumed to be a Stripe receipt.
A canceled invoice, an inconsistent balance, a missing settlement date or conflicting source history can require review. Closed accounting periods also block automatic financial writes. Do not create a replacement transaction just to clear an error; first compare the original Foundation source with the existing QuickBooks record. Refunds and legacy accounting entries may need accountant-led reconciliation rather than an automatic reversal or historical repair.
Opt in separately to future payout deposits
Automatic Stripe payout deposits are off by default. For this feature, explicitly select an active USD Undeposited Funds receipt account, an active USD QuickBooks bank account and the connected USD Stripe bank destination. Select an active USD expense account for fees if the payout has explained fees. Although the fee selection is optional during setup, a fee-bearing payout cannot post without it. The bank and holding accounts must be distinct.
Review and confirm the future-only setup. The confirmation states that it records existing receipts, not new income, and sends no money. Only new eligible receipts may use the selected holding account; existing received Payments and receipt mappings are not rewritten. Older payouts are not replayed. Disable automation before changing an enabled selection, then review and re-enable with a new cutoff. Check delivery readiness as well as the saved configuration.
A hypothetical gross-to-net example
Suppose two already-recorded invoice Payments contain $25,000 and $15,000 of principal. Together they total $40,000. If verified source evidence explains $640 in fees and the paid automatic payout is $39,360, the grouped Deposit links the existing $40,000 of Payments and includes a negative $640 fee line. The net Deposit is $39,360. These invented figures are not a quoted Stripe fee schedule or a customer result.
That Deposit does not create a second $39,360 sale. Intuit's bank-deposit documentation explains grouping existing payments from Undeposited Funds and adding processing fees without editing the original transactions. Stripe's payout reconciliation guide explains how automatic payouts can contain multiple transactions; Foundation's automation additionally requires complete, supported evidence for its eligible invoice receipts.
Finish matching and handle exceptions deliberately
After the grouped Deposit posts, match it to the payout in the QuickBooks bank feed. Bank-feed matching is not available through Foundation's integration; it remains a separate QuickBooks review, not another income entry. Use Stripe's payout reconciliation report when reviewing batch details. Manual or instant payouts, refunds, unexplained fees and missing receipts should not be assumed eligible for Foundation's automatic grouping.
The company-wide pause blocks imports, exports, manual sync, retries and customer provisioning across all company projects. It preserves connections, mappings and existing records; requests already sent may finish. Resuming preserves individual settings and does not automatically repair history. Review Waiting for receipts or Needs review rather than forcing a duplicate. Compare Foundation features and pricing, or read the draw-request guide to plan the operational handoff.