# Explaining Reclassified Transactions to Clients

- Author: AutoBankConvert (https://www.autobankconvert.com)
- Published: 2026-02-22
- Updated: 2026-02-22
- Category: Client communication
- Canonical: https://www.autobankconvert.com/blog/explaining-reclassified-transactions-to-clients

> Explaining reclassified transactions to clients when last month's report changes: what moved, why the books are better for it and how to show the change.
Explaining reclassified transactions to clients comes down to three points made before they spot the change themselves: which lines moved between accounts, why the new account is more accurate, and what the change does to the figures they saw last month. A short before-and-after table shows it faster than any paragraph can.

## Why did last month's report change after reclassified transactions?

Last month's report changes when a transaction is reclassified, meaning moved from one account to another after it was first recorded. The money and the bank balance stay exactly the same. What changes is where the line sits, so a category total or the profit figure on an earlier report can go up or down.

Clients see a changed number and assume something was lost or added. Start by saying what did not change: "The bank balance and the total you spent are the same. Three charges moved to a better category." That one sentence removes most of the worry.

Then give the reason in the client's terms. Typical reasons are a receipt that arrived late and showed a purchase was equipment, a vendor whose charges were split across two accounts by mistake, or an answer from the client that changed how a charge should be read. Reclassifications are a normal part of keeping books accurate, not a sign that the books were wrong in a careless way.

## A before-and-after table for reclassified transactions

A before-and-after table lists each reclassified transaction with its date, payee, amount, old account and new account, and ends with the effect on the report. Clients can read it in under a minute, and it doubles as a record of what changed and why.

Here is an example for a small retail client. The payees and amounts are made up.

| Date | Payee | Amount | Was in | Now in | Reason |
| --- | --- | --- | --- | --- | --- |
| Mar 6 | OFFICE DEPOT | 1,240.00 | Office supplies | Equipment | Receipt showed a register terminal |
| Mar 14 | ADOBE | 59.99 | Advertising | Software subscriptions | Same vendor as other software lines |
| Mar 22 | HOME CENTER | 180.00 | Repairs | Owner draws | Client confirmed it was personal |

Then state the effect in one or two lines: "March expenses fall by 1,420.00, so March profit rises by the same amount. Your equipment balance rises by 1,240.00." The Adobe line moved between two expense accounts, so it does not change profit at all. Point that out, because clients often assume every change moves the bottom line.

When several months are affected, add a month column instead of sending one table per month. If the move covers dozens of lines, such as a vendor coded wrongly all year, summarize it as one row with a count and a total, and keep the full list in your workpapers in case the client or their preparer asks.

## Which reclassifications deserve a note to the client?

A reclassification deserves a note when it changes a figure the client has already seen and might rely on, such as profit for a reported month, a category they track, or a balance they quoted to a lender. Moves inside the current open month, before any report went out, usually need no separate explanation.

A rough guide to sorting them:

- **Tell the client:** changes to a closed month's profit, moves into or out of owner draws, anything a lender, partner or tax preparer has already seen.
- **Mention in the monthly report:** small moves between two expense accounts in a closed month.
- **No note needed:** corrections made during the month before the report went out.

A regular client update can carry the low-stakes ones. If you send a [bookkeeping client newsletter](/blog/bookkeeping-client-newsletter), a line about why categories sometimes move after month end helps clients expect it.

## Reclassified personal spending from a business account

Personal spending paid from a business account is the most sensitive reclassification, because moving it out of expenses can look like an accusation. Treat it as a routine correction: say the charge looks personal, ask the client to confirm, and once they do, record it as an owner draw or the equivalent account for their business structure.

Word it neutrally. "This charge at a home store on March 22 looks like it might be personal. Should it be a business repair, or should I move it to your draws?" The client answers a question instead of defending themselves.

If personal charges keep appearing, the fix is a separate account rather than repeated questions every month. A [client guide to separate business accounts](/blog/client-guide-to-separate-business-accounts) is something you can send so the owner hears the reasons from a page, not as a complaint from you.

## Stopping the same reclassification from recurring next month

The mistake that turns reclassifications into a monthly chore is fixing the line and not the cause. When a vendor is coded wrongly, update the rule or the vendor default that coded it, so next month's statements land in the right account the first time and there is nothing to explain.

Each time you reclassify, ask why the first coding was wrong. Most causes fall into a few groups: a vendor rule that was too broad, a missing rule for a new payee, a client who did not answer a question before the close, or a statement that went into the wrong client's books. Fix the group, not only the line.

In [AutoBankConvert](/), approving a transaction in the review queue teaches that client's rules, so the same vendor is categorized automatically next month. Checking the files before a run matters as well. A [pre-batch checklist for bank statements](/blog/pre-batch-checklist-for-bank-statements) catches the wrong-client and wrong-period problems that would otherwise surface later as reclassifications.

Keep a short running log of reclassifications per client: date, line, old account, new account, cause. After a few months the log shows whether the corrections are shrinking. If they are not, the conversation with the client may need to be about how they answer questions, not about any one charge.