Key takeaways
- Reconciliation means proving that payments taken, payments recorded and money deposited all agree.
- Automation works when every payment carries consistent identifiers across systems.
- Gateway fees, refunds, chargebacks and batch deposits are the usual sources of mismatches.
- Automate the matching and route only exceptions to finance.
A business taking payments through a gateway, tracking them in a CRM and keeping books in QuickBooks has three versions of the truth. Someone in finance spends hours each week ticking them off against each other. Most of that work can be automated.
The three records that must agree
| System | What it shows |
|---|---|
| Payment gateway | Transactions, fees, refunds, chargebacks and settlement batches |
| CRM | Which customer, invoice or service each payment relates to |
| Accounting (QuickBooks) | Payments applied to invoices and deposits to the bank account |
Why reconciliation is hard
- Batch deposits: the bank shows one deposit for many transactions, minus fees.
- Fees: gateways deduct fees that must be recorded as expenses.
- Refunds and chargebacks: money leaves after the original payment was recorded.
- Timing: settlement happens days after payment.
- Missing links: payments recorded without the invoice or customer reference.
Making automation possible
- Store the gateway transaction ID on the CRM payment record and on the QuickBooks payment.
- Include the invoice number or customer ID in the payment request so every payment is linked from the start.
- Record fees separately rather than netting them invisibly.
- Import or fetch settlement batch reports from the gateway.
An automated flow
- A customer pays through a payment link sent from the CRM; the CRM records the payment with the gateway transaction ID.
- The integration creates the payment in QuickBooks, applied to the right invoice.
- When the gateway settles a batch, the integration groups the included payments, records fees and creates the matching bank deposit in QuickBooks.
- Refunds and chargebacks update both systems with the original transaction reference.
- Anything that does not match, such as an unknown transaction or amount difference, goes to an exception list for finance.
Exception handling
The goal is not zero human involvement but zero routine work. Finance should see a short list of exceptions with all the information needed to resolve each one, rather than a spreadsheet of every transaction.
Reports that help
- Daily payments by method, facility or entity.
- Unapplied payments and unpaid invoices.
- Fees as a percentage of revenue by payment method.
- Refunds and chargebacks by reason.
Our Payment Gateway for Salesforce logs every transaction with gateway references, and our integration team connects payments to QuickBooks and other accounting systems.
Common mismatches and fixes
| Mismatch | Usual cause | Fix |
|---|---|---|
| Deposit lower than payments | Fees deducted at settlement | Record fees as expenses when the batch is imported |
| Payment missing in QuickBooks | Integration error or missing customer | Retry with alert; create customer mapping |
| Duplicate payment | Webhook received twice | De-duplicate using the gateway transaction ID |
| Refund not reflected | Refund made directly in the gateway | Sync refunds by original transaction reference |
Frequently asked questions
Can QuickBooks reconcile gateway deposits automatically?
Bank feeds help, but batch deposits net of fees need matching to individual payments. Integration with gateway settlement data makes this automatic.
How should gateway fees be recorded?
Typically as a separate expense, so revenue stays at the gross amount. Confirm the treatment with your accountant.
What is the most important step for automated reconciliation?
Carrying a consistent transaction ID and invoice reference through every system from the moment a payment is requested.
