Export or back up the relevant data first. Do not delete, void, unreconcile, or adjust historical transactions unless you understand the accounting impact.
Menu names can change. We link current first-party instructions so you can confirm product behavior before acting.
QuickBooks Payments can connect invoice collection and merchant processing with QuickBooks, but a connected button does not guarantee accurate books. Verify the current application, rates, funding, reserves, dispute, and termination terms; secure payment access; and reconcile gross sales, refunds, chargebacks, fees, and net deposits through a clearing account or equivalent controlled method.
Best for: businesses considering or using QuickBooks card, ACH, invoice-payment, or merchant services
What this guide covers—and what it does not
The page owns one search intent: evaluating and reconciling QuickBooks Payments merchant services. Related jobs have their own canonical guides so you can move between them without mixing product selection, setup, troubleshooting, and migration advice.
- This page owns merchant-service evaluation and settlement reconciliation.
- Invoice creation and customer-payment application belong to the invoicing guide.
- Bank-feed matching symptoms belong to the bank-transactions guide.
Evidence-first workflow
Reconcile gross activity to the net bank deposit
Follow the settlement statement so fees never silently reduce recorded sales.
- 1
Record
Create the sale or invoice and apply the customer payment once.
Evidence: Customer balance and revenue treatment are correct.
- 2
Settle
Collect the processor batch containing payments, refunds, disputes, and fees.
Evidence: Gross components explain the expected net funding.
- 3
Match
Match the net bank deposit to the settlement or clearing activity.
Evidence: No second sales receipt or income transaction is created.
- 4
Reconcile
Tie processor balance, bank funding, fees, and receivables at period end.
Evidence: Timing differences and disputes remain in an owned exception list.
Decision control
Choose from evidence, not a feature list
Use the same four gates for evaluating and reconciling QuickBooks Payments merchant services: define the job, surface constraints, choose the smallest workable option, then verify the records.
Evaluate payment processing beyond the headline rate
Use representative ticket sizes, channels, payment methods, and risk events.
| Your situation | Direction | Why |
|---|---|---|
| Most customers pay QBO invoices online | Integration may add value | Payment application and status can reduce manual work when mappings and duplicates are controlled. |
| Sales originate in ecommerce or point of sale | Compare native processor flow | Adding another payment system can complicate refunds, orders, tax, inventory, and deposit reconciliation. |
| Business has high volume or unusual ticket size | Model effective rate and reserves | Transaction mix, chargebacks, funding timing, and negotiated terms can dominate cost. |
| Only bank transfer is needed | Compare ACH and bill-pay options | Card features and pricing may not match the actual collection method. |
Model fees from the real transaction mix
Collect the current fee schedule and terms for card-present, keyed, invoiced, ACH, and any other channels used. Model percentage and fixed fees across actual ticket sizes; a fixed component affects small tickets differently from large ones.
Review funding windows, returned payments, chargebacks, retrieval requests, reserves, prohibited use, hardware, PCI or security obligations, support, data access, and termination. Retain the version accepted during onboarding.
Control links, refunds, and account access
Use individual identities, the strongest available authentication, least-privilege roles, and a documented bank-account change process. Restrict who can issue refunds, void payments, alter invoice payment settings, change deposit accounts, and respond to disputes.
Verify customer-facing business identity, invoice text, refund policy, and payment-link destination. Staff should know how to identify phishing and must never accept an unexpected request to change settlement banking without independent confirmation.
Reconcile processor, receivables, and bank together
For each batch, retain gross charges, refunds, chargebacks, fees, adjustments, and net funding. Post each component to the correct account or use a processor clearing account so the net bank deposit can be matched without understating revenue.
At month-end, reconcile unsettled batches, processor balances, customer receivables, bank deposits, fee expense, disputes, and refunds. Assign every aging difference to an owner and expected resolution date.
Rates, funding, holds, and service terms are time-sensitive and account-specific. Verify the current legal agreement and approved merchant offer before relying on any figure.
Completion checklist
Do not call the decision or setup complete until someone independent of the initial change can verify these items.
Frequently asked questions
How much does QuickBooks Payments cost?
Rates depend on the current offer, payment method, channel, and merchant terms. Check Intuit’s current pricing and legal documents, then calculate an effective cost using your ticket sizes, volume, refunds, and disputes.
Are QuickBooks merchant service deposits income?
The net bank deposit is cash funding, not necessarily the revenue amount. Preserve gross sales and record refunds, chargebacks, and processor fees separately, then reconcile the net settlement.
Should I add a bank deposit for a payment already recorded through QuickBooks Payments?
Usually the goal is to match the settlement to the payment activity already recorded, not create income again. Inspect the existing transaction chain before adding anything.
Still comparing adjacent tasks? Use the complete guide library to find the one page that owns your intent.
Optional free utilities
Tools that support this workflow
These run in your browser and can help prepare or inspect files. They do not replace reconciliation, source-document review, or an accountant’s approval.
Sources checked
First-party product documentation used to verify the workflow and risk notes in this guide.