At Lookout Bookkeeping, we pride ourselves on putting order to your chaos when it comes to your books!
bookkeeping tips
financial reporting
lookout outlook archives
small business tips
CLIENT CASE STUDIES
FREEBIE!
CLIENT CASE STUDIES
GET IT NOWSeptember 30, 2026

I hate journal entries.
Not “prefer to avoid them.” Hate them. I tell my staff all the time: we do not do journal entries unless we have to.
That sentence gets me some looks in bookkeeping circles. Especially from anyone who came up through a CPA-backed firm, where journal entries aren’t a last resort—they’re the default setting. Loan payment comes in? Journal entry. Owner draw? Journal entry. Something doesn’t reconcile cleanly? Journal entry to force it closed.
I get why. That’s the training. But it’s not the only way to do this work, and I’d argue it’s not the better way.
CPA-backed firms think in year-end terms. Their whole world is built around producing a clean set of financials for a tax return, once a year. Journal entries are fast for that. You don’t have to touch the bank feed, you don’t have to match anything to a transaction, you just move numbers where they need to go and move on.
That works fine if the only person who ever needs to understand those books is another accountant, at tax time, with a spreadsheet open next to them.
It falls apart the second a business owner actually wants to look at their own numbers.
Here’s what I do instead: split the bank feed transaction.
A loan payment isn’t one number. It’s principal, and it’s interest, and maybe it’s a fee. So I split it, right there in the transaction, tied to the actual deposit or withdrawal that happened in real life. No detached entry floating in the general ledger with a vague memo and zero context.
Same logic for owner draws, for reimbursements, for anything that touches more than one account. If it happened in the bank, it gets handled in the bank feed. Journal entries are for the handful of things that genuinely can’t be handled any other way—depreciation, accruals, the occasional correction. Not the default. The exception.
Here’s the part that doesn’t get talked about enough: the journal-entry-heavy approach costs the client something, even when the numbers are technically correct.
It costs them clarity. Open a bank-feed-split transaction and you can see exactly what happened—the actual deposit, the actual split, tied to the actual bank activity. Open a mystery journal entry from six months ago and you’re staring at a debit and a credit with no story attached. You have to go find someone who remembers why it’s there. Sometimes that someone doesn’t work there anymore.
It costs time, too. Every journal entry someone else made is now something you have to investigate before you trust it. I’ve opened client files where every single loan was journaled monthly for years, no documentation, no notes. That’s not clean bookkeeping. That’s clean-looking bookkeeping, which is a very different thing.
Every journal entry needs a receipt. If I can’t attach documentation explaining why it exists, it doesn’t go in. That rule alone eliminates most of the journal entries a CPA-backed workflow would have made without blinking.
It’s a small operational choice. But it changes what the client’s books actually communicate—to them, to their CPA, to the next bookkeeper who opens the file after me.
If you’re a bookkeeper reading this and journal entries have become your default move for anything remotely complicated, try one thing this month: pick a recurring entry you make out of habit—a loan payment, a draw, whatever it is—and ask if it could live in the bank feed instead. Split it. Document it. See what changes when you open that file three months from now.
You’ll probably hate journal entries a little more after that. Good. That means it’s working.