Stripe Payments and QuickBooks for Plumbing: Reconcile the Records

Map the records before relying on a connection

Start with a list of identifiers: job, invoice, customer, payment, processor balance transaction, payout, and accounting record. Not every screen displays every identifier, but the relationship needs to be traceable somewhere in the process.

This guide does not certify that GoPlumber automatically synchronizes every Stripe and QuickBooks event. Confirm the supported integration behavior for invoices, partial payments, refunds, fees, and retries in a controlled test. Official source

Understand the payout boundary

Stripe's payout-reconciliation report connects automatic payout batches to their underlying transactions. Its documentation distinguishes manual and instant payout reconciliation, which can require a different approach. Use the official report guidance appropriate to the account's payout setup.

That means a bank deposit should not automatically be treated as one customer's invoice payment. The deposit can represent a batch with fees or other adjustments.

Use a fictional batch example

Suppose three verified payments total $600. An illustrative $12 in fees and a $40 refund are included in the same batch. Ignoring other adjustments for this example, the net payout is $548.

The $548 bank deposit is not a new $548 sale on top of the original invoices. The accountant needs the relationship among the charges, fees, refund, and payout to apply the correct treatment.

These figures are not Stripe's actual fees or a recommended accounting entry.

Reconcile in two passes

First, verify each customer payment and its invoice allocation. Check the amount, customer identity, transaction status, and any partial-payment balance.

Second, reconcile the processor batch to the bank payout. Identify fees, refunds, disputes, reserves, or other adjustments that actually appear in the relevant records. Do not assume a missing amount is always a fee.

Intuit's matching guidance helps distinguish an existing record from a new transaction. Use that distinction to avoid duplicating a sale or payment already created by the workflow. Official source

Keep an exception log

Stripe / QuickBooks exception
Invoice reference: [ID]
Payment reference: [ID]
Payout or balance reference: [ID]
Accounting reference: [ID]
Expected relationship: [description]
Observed difference: [amount/status/reference]
Evidence reviewed: [records]
Owner and next action: [details]
Resolution reference: [record]

A missing reference should remain an investigation item. Do not force a match based only on an equal amount or a nearby date.

Test the edge cases that affect real jobs

Check one partial payment, one refund, one payment covering multiple invoices where supported, and one repeated event. Verify whether the connection updates an existing record or creates a new one.

Document manual steps honestly. A workflow can still be useful when some cases require review, but staff need to know which cases those are.

The goal is not simply to “connect Stripe to QuickBooks.” It is to preserve an explainable chain from authorized work to payment, settlement, and accounting reconciliation without counting the same money twice.