Key takeaways
- Reconcile transaction activity every business day instead of waiting for the bank statement.
- Match the patient account, processor transaction, batch, and deposit as separate records.
- Use an exception queue for unmatched payments, partial settlements, refunds, and chargebacks.
- Preserve transaction identifiers and timestamps so staff can trace a payment without storing card data.
Understand the four records
A patient payment can appear in at least four places: the practice-management or billing account, the payment processor transaction list, the terminal or online batch, and the bank deposit. Reconciliation confirms that the records agree or explains why they do not.
Treat authorization and settlement as different events. A payment can be approved at checkout and still appear in a later deposit, be reversed, or require investigation.
Create a daily close process
Assign one owner and one backup for daily payment close. Use a standard cutoff time and record who completed the review. Separate duties where practical so the same person is not solely responsible for collecting, posting, refunding, and reconciling payments.
- Confirm each terminal and online channel completed the expected batch.
- Compare transaction count and gross amount by channel.
- Match payments to patient, invoice, or plan records.
- Record refunds, voids, chargebacks, and adjustments separately.
- Move unresolved items into an exception queue with an owner and due date.
Reconcile deposits without losing fee visibility
Some processors deposit net of fees while others separate fees from settlement. Maintain a bridge from gross patient payments to refunds, chargebacks, processing fees, reserves, and the final bank amount.
The merchant statement and settlement report should support this bridge. If staff cannot explain the difference, document the question for the processor rather than forcing the amount into a miscellaneous adjustment.
Work exceptions from oldest to newest
Common exceptions include duplicate payments, payments posted to the wrong account, partial approvals, missing batches, refund timing differences, expired payment methods, and chargebacks. Each type should have a defined investigation path.
Use transaction IDs, batch IDs, dates, amounts, and approved internal account references. Do not copy full card numbers or sensitive authentication data into spreadsheets or notes.
Review trends monthly
Summarize unresolved exceptions, average time to resolve, refund volume, chargebacks, duplicate transactions, manual adjustments, and deposits that did not match on first review. Recurring exceptions often reveal a training, integration, or configuration problem.
A strong reconciliation process protects both the patient experience and the practice's financial reporting. It also makes merchant-statement audits and processor comparisons substantially easier.
