Routine bank matching is not usually where a staffed medical practice needs the most owner attention. The difficult work starts when a payer deposit combines several receipts, a card settlement arrives net of fees, or a transfer appears in one entity’s books but not the other’s.

AI-assisted suggestions may help a bookkeeper identify possible combinations, spot repeated imports, or organize an investigation. But a suggested match is a hypothesis—not proof that the accounting is correct. Equal amounts and nearby dates do not establish that two records represent the same transaction.

This article focuses on the exceptions left after routine matching: how to triage them, document evidence, obtain independent approval, and escalate differences that remain unexplained. It is not a walkthrough of the entire monthly reconciliation process.

What Makes an Exception Worth Investigating?

An exception is a transaction or difference that cannot be confidently explained by the available bank and accounting records. Some are legitimate timing items. Others reveal missing entries, duplicate postings, incorrect account assignments, or payments requiring further investigation.

For a private practice, the distinction matters. An incorrect match can hide an overstated payer receipt, misstate a location’s expenses, or make money moved between accounts look like new revenue.

The IRS guidance on business recordkeeping supports maintaining complete business records, separating business and personal accounts, and reconciling bank records. Exception review puts those principles into a practical workflow: every unresolved item needs an explanation supported by records, not just a balanced total.

What AI assistance can—and cannot—establish

Depending on the tools and records available, AI-assisted analysis may help:

  • Identify combinations of receipts that could explain a grouped deposit.
  • Compare settlement totals with gross collections, fees, and refunds.
  • Flag similar entries for possible duplication.
  • Suggest that an unmatched withdrawal may be a transfer or reversal.
  • Draft a summary of missing evidence for a reviewer.

None of these suggestions establishes authorization, confirms that a payment reached the intended recipient, or determines the correct accounting treatment. Those conclusions require source evidence and human judgment.

Triage Exceptions by Risk, Not Just Dollar Amount

Start by separating known timing differences from items that could affect cash control or financial reporting. A smaller unfamiliar withdrawal may deserve more immediate attention than a larger deposit already supported by a settlement report.

Exception Evidence to obtain Main risk Appropriate next step
Grouped payer deposit Aggregate receipt batch, bank deposit detail, payer or clearinghouse settlement reference Wrong receipts combined to force a match Verify the full batch composition and references
Net card settlement Processor settlement report showing collections, refunds, fees, and adjustments Fees omitted or revenue counted twice Build a gross-to-net bridge and check existing postings
Suspected duplicate import Bank statement, imported transaction identifiers, ledger entries Duplicate income or expense Distinguish duplicate feed data from duplicate accounting entries
Missing transfer side Statements for both accounts, transfer confirmation, entity ownership Transfer recorded as revenue or expense Trace both sides and confirm the entities involved
Reversal or returned payment Original transaction, reversal reference, bank or processor notice Original posting left incorrectly outstanding Link the reversal to the original and investigate the cause
Uncleared payment Payment register, issue date, authorization, bank status Duplicate payment, failed delivery, or unsupported write-off Confirm status before reissuing, voiding, or adjusting

An unfamiliar withdrawal, changed payment destination, or unexplained reversal should receive prompt owner or controller attention. Repeated differences and exceptions involving multiple entities also warrant escalation, even when individual amounts appear modest.

Use an Exception Register Instead of Informal Notes

A central register makes it clear what is unresolved, who is investigating, and what must happen before an item can be closed. Keep it tied to the relevant bank account, legal entity, location where applicable, and accounting period.

At minimum, record:

  • Exception ID, discovery date, transaction date, and amount.
  • Bank account and entity; location if relevant to reporting.
  • The observed difference and any AI-suggested explanation.
  • Supporting evidence and evidence still missing.
  • Proposed treatment, preparer, and independent reviewer.
  • Resolution status, next action, and follow-up date.
  • Final approval and reference to any posted correction.

Illustrative example: The following register entries are invented to demonstrate the workflow; they are not practice results or benchmarks.

ID / item Supporting evidence Proposed treatment Independent reviewer Resolution status
EX-A: grouped payer deposit Bank deposit reference and aggregate receipt batch; settlement confirmation pending Match to existing receipt batch only if confirmed; no new revenue entry Controller Waiting for settlement evidence
EX-B: net card settlement Processor report and bank credit; ledger comparison complete Clear recorded gross receipts and record documented fees not already posted CPA reviewer Awaiting approval
EX-C: possible duplicate Statement shows one withdrawal; import and ledger detail under review Remove redundant feed item or correct duplicate posting, depending on findings Finance manager Investigating
EX-D: transfer mismatch Originating statement and transfer confirmation; destination statement missing Verify receiving account and determine same-entity or intercompany treatment Controller Escalated

Keep “investigating,” “awaiting approval,” “posted,” and “closed” distinct. A proposed explanation should not become a resolved item simply because someone added a comment.

Close an exception only when the evidence supports the explanation, an independent reviewer has approved any correction, and the resulting ledger and reconciliation have been checked.

Worked Example: A Grouped Payer Deposit

Illustrative example: A private practice receives a bank deposit of $24,680. Its accounting records contain three aggregate payer receipt batches awaiting settlement:

Aggregate record Amount Available reference
Batch A $10,240 Settlement group R
Batch B $8,915 Settlement group R
Batch C $5,525 Settlement group R
Total $24,680

An AI-assisted suggestion identifies the three batches as a possible match because their amounts total the bank deposit and their expected settlement dates are close.

That is a useful lead, but not enough to approve the match. Another combination could produce the same amount, or one batch could already have been matched elsewhere.

Build the evidence chain

The preparer should establish that:

  1. The bank statement confirms the deposit amount, date, and available reference.
  2. An aggregate payer or clearinghouse settlement record links settlement group R to all three batches.
  3. The batches belong to the entity receiving the deposit.
  4. None of the batches has already been matched, reversed, or duplicated.
  5. The total contains no unexplained fee, offset, or missing component.

This investigation uses aggregate financial records. Patient names, dates of birth, and clinical details are unnecessary for the example.

Separate matching from posting

Assume the gross receipts are already recorded in a receipts-clearing account under the practice’s established accounting workflow. The proposed treatment is to match the bank deposit to those existing receipts and clear the corresponding balance—not create another revenue entry.

If the batches exist only in a billing report and have not been recorded in the general ledger, the treatment is different. The CPA or responsible accountant should determine the entry consistent with the practice’s accounting method and existing posting workflow.

An independent reviewer should inspect the bank evidence, settlement record, and ledger status before any correction is posted. After approval, the preparer records the resolution and confirms that the match leaves no unexplained remainder.

If the evidence does not identify all three batches, leave the exception open. Do not select unrelated receipts merely to make the deposit total work.

Investigate the Other Ambiguous Matches

Net settlements: explain every component

A patient-payment processor may deposit collections after deducting refunds, fees, or other adjustments. The investigation should bridge gross collections to the bank amount using the processor’s settlement report.

Do not assume the difference is a processing fee. It may include a refund, chargeback, reserve adjustment, or correction. Check what has already been posted before proposing an entry; otherwise, the practice could record the same fee or refund twice.

For location-level reporting, verify the supporting allocation rather than assigning the entire settlement to whichever location owns the receiving bank account.

Duplicate imports: distinguish data from accounting

Two identical bank-feed lines do not necessarily mean two ledger postings. Conversely, a single statement withdrawal may have been recorded once through an accounts-payable workflow and again as a bank-feed expense.

Compare the bank statement, import identifiers, and posted ledger detail. Removing a redundant feed item and reversing a duplicate accounting entry are different actions. The reviewer should approve the action that addresses the actual problem without disturbing a valid transaction.

Missing transfers: verify both accounts and entities

Trace a suspected transfer to both bank statements. Confirm the originating and receiving accounts, amounts, dates, and account ownership.

A transfer between accounts of the same entity is not new operating revenue. A movement between separate entities may require intercompany accounting and CPA review. A shared owner or similar bank description is not enough to determine treatment.

Reversals: trace the original transaction

A reversal can relate to a returned payer receipt, failed payment, duplicate settlement correction, or other event. Link it to the original transaction using bank or processor evidence.

Do not automatically net a reversal against an unrelated receipt or expense. Determine whether an outstanding receivable, payable, or clearing balance needs attention and whether the underlying operational issue remains unresolved.

Uncleared payments: investigate before reissuing

For an outstanding vendor check or provider/admin payroll payment, confirm issuance, authorization, bank status, and whether a replacement already exists. Coordinate payroll exceptions with the payroll administrator so a bank correction does not create a second payment or an inconsistent payroll record.

Age alone does not justify deleting a liability or recognizing income. Escalate long-outstanding items to the CPA, including any questions about unclaimed-property obligations, rather than applying an assumed write-off rule.

Require Independent Verification Before Corrections

The preparer should gather evidence and propose treatment. A different person should verify that evidence and approve corrections before posting. In a smaller practice, the owner may provide this review with CPA support when internal finance staffing is limited.

The reviewer should answer four questions:

  • Does the external evidence support the proposed explanation?
  • Has the preparer checked for existing postings and prior matches?
  • Are the entity, account, period, and location assignments appropriate?
  • Will the correction resolve the actual issue without creating another one?

After posting, check the affected ledger accounts and reconciliation again. Retain the approval and correction reference with the exception record.

Never use an unexplained adjustment to force agreement. If a temporary clearing treatment is appropriate under the CPA’s direction, keep the underlying exception open with an owner and follow-up date.

Protect Information and Escalate Unresolved Differences

Use aggregate amounts, settlement identifiers, and masked account references wherever they are sufficient. Do not put patient-identifiable records into ordinary Slack messages or a general-purpose AI tool.

HHS explains that accounting services can involve business-associate responsibilities when protected health information is involved. Its minimum necessary guidance also provides context for limiting information in applicable circumstances. These sources do not establish that a particular tool or service is approved for patient information.

Owners should review unresolved exceptions by age, risk, entity, and recurring cause—not just total dollars. Escalate unexplained differences, suspected unauthorized transactions, missing source records, and items that repeatedly return after correction. If an item affects period-end reporting, ask the CPA how it should affect the close rather than silently carrying it forward.

Lucid Financials provides CPA-led bookkeeping, tax, and CFO services for staffed US private medical practices, combining AI-assisted financial work with a human finance team. Exception review is a useful place to define responsibilities with that team: who gathers evidence, who approves treatment, and which unresolved items reach the owner. Slack can support status coordination without sharing patient-identifiable details.

FAQs

Can AI approve a bank reconciliation exception?

An AI-generated match should not serve as approval. It may identify a plausible explanation, but an independent human reviewer should verify source evidence and approve corrections before posting.

Should a practice record every unmatched deposit as revenue?

No. The deposit may represent receipts already recorded, an account transfer, a loan, or another type of transaction. Determine its source and existing ledger treatment before creating an entry.

What if an exact amount match has no supporting reference?

Keep it as a candidate match, not a confirmed resolution. Seek settlement details, bank documentation, or other independent evidence. Matching amounts alone cannot rule out coincidence or duplicate use of an existing receipt.

What should the owner see at month-end?

A concise exception report showing unresolved items, supporting evidence, assigned owners, aging, proposed treatment, and escalation decisions. Posted corrections should have documented approval; unexplained differences should remain visible rather than disappearing into miscellaneous adjustments.