📊 a journal entry
ProAdvisor Prep: Level 2 — Banking, Rules & Finding the Bodies
September 22, 2026
A Quick Credit Where It’s Due
This module is a little different from the others because I didn’t compile the source material for it. My fellow Resistance Accountant and dear reader, Taissa, did. 🌸
She worked through this material, organized the concepts, and built the original scavenger hunt you’ll find below after she completed the module herself.
I did approximately fuck all of that this time. Had you all waited on me, this would have published on Friday as usual and might not have been nearly as good as this.
I did my usual verification pass against current Intuit documentation, corrections, and general Resistance Accountant fuckery—and what you’re reading is what came out the other side. She did amazing.
So if this module helps you understand advanced banking cleanup a little better, give Taissa her flowers. This one’s hers. 🌸
Well here we go! Hi, I’m Taissa and I’m happy to be here today supporting the Resistance Accountants!
Level 1 taught us how to work with bank transactions, match what belongs together, reconcile an account, and—ideally—reach that glorious $0.00 without committing accounting crimes along the way.
Level 2 asks a slightly different question:
What the hell do you do when somebody has already been doing this for a while and the books are weird?
Because eventually you inherit the client with seventeen bank rules, eight-month-old checks floating around like financial ghosts, transactions somebody excluded because they didn’t know what else to do with them, and a reconciliation that suddenly doesn’t work even though “it was fine last month.”
This is where knowing which buttons to press stops being enough.
You need to understand what QuickBooks did, what the human did, and what actually happened at the bank.
Those are three different things.
And if they disagree?
Welcome to Level 2.
Bank Rules Are Automation, Not Accounting Judgment
Bank rules can save an enormous amount of repetitive work. They can also reproduce a bad decision at remarkable speed.
QuickBooks lets you build rules around information such as bank text, description, and amount. A rule can contain multiple conditions, and those conditions can use All or Any logic. Current QuickBooks supports up to five conditions within a rule.
But here’s the Level 2 part:
Rule order matters.
QuickBooks can apply only one bank rule per transaction, so it evaluates rules according to their priority. The highest-priority matching rule gets there first. You can reorder rules by dragging them within the Rules area.
That means your rule list is effectively a logic hierarchy.
Imagine Resistance Coffee & Books has these two rules:
Rule 1:
Bank text contains GLOBAL
→ Categorize as Other Income
Rule 2:
Bank text contains GLOBAL BOOK DISTRIBUTORS
→ Categorize as Inventory Purchases
Guess which rule you don’t want sitting above the other one?
The broad rule can catch a transaction before the specific rule ever gets the opportunity.
Specific first. Broad later.
That’s a much better mental model than memorizing some arbitrary rule number.
And don’t automatically switch every broad rule from Any to All, either.
All means every specified condition must be satisfied.
Any means one of the specified conditions can satisfy the rule.
Neither setting is inherently better.
The question is:
What transaction was this rule designed to identify?
Build the logic around that answer.
Auto-Post Deserves Respect
Rules can do more than suggest categorization. QuickBooks can also automatically post transactions when a rule matches.
That’s convenient.
It’s also exactly why you should understand the rule before giving it that much authority.
Intuit currently warns that when auto-post is enabled, matching downloaded transactions can be posted immediately without waiting for your review.
So this:
Automation should follow understanding, not replace it.
is still very much our rule around here.
A beautifully automated mistake remains a mistake.
It just arrives faster.
The Ghost Hunt: Old Uncleared Transactions
Now we get to the fun shit.
You open a client’s checking account and discover checks from eight months ago that are still sitting there with no cleared or reconciled status.
Do not immediately delete them.
Do not immediately reconcile them.
Do not immediately create a journal entry.
And please, for the love of Gertrude, do not start clicking the little status box until the numbers become aesthetically pleasing.
First:
Find out what happened.
QuickBooks lets you identify outstanding checks by running a report and filtering or sorting by cleared status. That’s useful precisely because old uncleared checks deserve investigation.
An eight-month-old check could mean:
- the vendor never cashed it;
- it was lost;
- it was replaced;
- it was entered twice;
- it was entered but never actually issued;
- something happened at the bank that hasn’t been properly reflected in the books;
- or somebody simply made a bookkeeping mistake.
Those situations do not all have the same correction.
That’s why the investigation comes first.
Blank, C and R: Don’t Make Them Say More Than They Do
In the register, QuickBooks uses reconciliation status indicators.
The current progression is:
R = Reconciled
C = Cleared
Blank = Uncleared
That’s it.
A blank status tells you the transaction is currently uncleared in QuickBooks.
It does not, by itself, prove:
“This transaction never appeared in the bank feed.”
Those are different systems/concepts.
A downloaded bank transaction appears for review before it affects the books; matching connects downloaded bank information with an existing QuickBooks record.
So when you see an ancient blank status, don’t invent a biography for it.
Investigate.
That word is becoming suspiciously important around here.
The Excluded Tab Is Not a Trash Can
Remember Excluded?
We met it back in Level 1.
Now we’re going to stop treating it like QuickBooks’s junk drawer.
When you exclude a downloaded bank transaction, QuickBooks moves it to the Excluded area. The excluded transaction does not appear in the account register or financial reports. If it was excluded accidentally, you can undo the exclusion and return it for review.
That means the original draft’s idea that excluded transactions somehow remain inside the financial books and secretly alter the Balance Sheet was wrong.
They don’t.
But exclusions still matter during an investigation because they tell you something about what happened to downloaded banking data.
Maybe the exclusion was appropriate.
Maybe it was a duplicate.
Maybe somebody excluded a legitimate business transaction because they didn’t know what to do with it.
Intuit specifically notes that even something like a personal transaction may need to be recorded appropriately rather than simply excluded if the QuickBooks account needs to reconcile to the bank statement.
So again:
Excluded does not mean irrelevant.
It means somebody made a decision.
Level 2 asks whether it was the right one.
Suggested Matches Are Suggestions
QuickBooks has gotten considerably more sophisticated about banking suggestions.
As of August 2026, Intuit’s AI-powered banking features can suggest matches and categories based on transaction details and prior activity, including potential partial and combined matches. Suggested matches can also display confidence information.
Useful?
Absolutely.
Authority?
Nope.
Before accepting a suggested match, verify that it represents the same actual transaction.
QuickBooks itself tells users to make sure they select the correct match.
So we’re retiring the original dramatic Delta Airlines versus Delta Tools example as though QuickBooks necessarily behaves exactly that way.
The real lesson is better anyway:
A suggestion is evidence to examine, not permission to stop thinking.
Very Resistance Accountant.
When Last Month Suddenly Doesn’t Reconcile Anymore
Here’s a particularly unpleasant client sentence:
“It reconciled perfectly last month.”
And now the beginning balance is wrong.
That doesn’t automatically tell you why it’s wrong.
QuickBooks provides tools for investigating changes affecting previously reconciled periods. Current Intuit guidance tells users to review reconciliation discrepancies and, if necessary, the Audit Log for deleted or voided transactions and other changes.
This is why randomly deleting things until the difference disappears is such a spectacularly bad troubleshooting method.
You’re destroying clues.
Instead ask:
What changed?
Was a reconciled transaction edited?
Deleted?
Voided?
Was its reconciliation status changed?
Was an entire reconciliation undone?
The Audit Log exists because historical changes matter. QuickBooks records account activity there, including transaction changes and user activity, and current Audit Log events remain available for two years.
Find the cause before manufacturing the cure.
There’s our Level 2 theme again.
About That Magical $0.00
We established this in Level 1, but apparently Level 2 requires me to say it louder:
A reconciliation difference of $0.00 is only useful when it’s legitimate.
QuickBooks does allow an adjusting entry when a small discrepancy remains after you’ve reviewed everything and cannot find the source.
But Intuit describes that as a last resort and specifically warns that adjustments for larger discrepancies can create accounting problems.
So if you’re staring at an $8,500 discrepancy:
No.
Put the adjustment button down.
Gertrude is approaching.
Journal Entries: Powerful, Not Magical
Journal entries aren’t “deep database overrides.”
They’re accounting entries.
QuickBooks uses them when you need to record activity without one of the normal transactional forms such as an invoice or bill. Total debits and credits must balance.
That makes them powerful.
It doesn’t make them the universal answer to every weird thing you find.
And Accounts Receivable and Accounts Payable deserve particular care.
For specific A/R journal-entry corrections, QuickBooks requires the appropriate customer on the A/R line. For A/P corrections, the corresponding vendor is used. Intuit also explicitly warns users to consult an accountant before correcting these accounts with journal entries when they’re uncertain.
So instead of teaching:
“Something is wrong → make a journal entry.”
We’re teaching:
What happened?
↓
What transaction should represent it?
↓
Does an existing QuickBooks form represent that activity correctly?
↓
If a journal entry really is appropriate, what accounts and names must it affect?
That is a very different thought process.
🚨 Three Level 2 Banking Sabotages
Sabotage #1: Letting Automation Become Authority
Rules and AI suggestions are useful.
Neither knows your client’s business the way a human reviewing the actual records should.
If something looks strange, inspect the bank information, existing QuickBooks record, payee, date, amount and business purpose before approving it.
QuickBooks can suggest. You still decide.
Sabotage #2: Editing History to Make Today Look Better
If a previously reconciled account suddenly develops a beginning-balance discrepancy, don’t start deleting old transactions because one of them looks inconvenient.
Use the reconciliation information and Audit Log to determine what changed.
A current discrepancy may be evidence of a historical change.
Don’t destroy the evidence.
Sabotage #3: Assuming Bank Description and Bank Text Are the Same Thing
This one from the original draft actually pointed toward something useful, but the explanation needed fixing.
QuickBooks distinguishes between bank text—information received from the bank—and description, which may be a simplified version of that information. Intuit specifically recommends checking which one a bank rule uses when troubleshooting rules that aren’t behaving as expected.
That matters.
A rule built around a simplified description may behave differently from one built around the underlying bank text.
So when a rule suddenly seems possessed:
Look at what it’s actually reading.
Don’t immediately blame the robot.
Gertrude hates when we falsely accuse robots.
Apparently she has developed professional ethics.
🕵️ The Resistance Accountants Scavenger Hunt
Time to break something.
The Scenario
You inherit a new client’s books.
Their actual bank balance is:
$50,000
But their QuickBooks Balance Sheet shows:
$58,500
You begin investigating and discover two things:
1. There’s a broad bank rule sitting at the highest priority. It looks for the word GLOBAL and categorizes matching downloaded money-in transactions as Income.
2. Three checks written to an overseas supplier eight months ago still appear in the register with a blank reconciliation status.
Your mission is not to force QuickBooks to equal the bank.
Your mission is to determine why they don’t agree.
Task 1
What should you investigate or change about that broad GLOBAL bank rule before allowing it to continue processing transactions?
Task 2
What does the blank status on those three old checks actually tell you, and what does it not tell you?
Task 3
You investigate one check and determine that it is genuinely a duplicate entry. The check was never issued and never represented a real payment.
What are your options for correcting it, and why might you choose Void rather than Delete?
Bonus Mission
Before changing anything, name at least three places or records you would inspect to understand how the $8,500 difference developed.
Don’t scroll yet.
Gertrude is watching you.
And she has been moisturizing.
🛑 SCAVENGER HUNT ANSWERS BELOW
Seriously.
Go investigate first.
The answers aren’t going anywhere.
🕵️ Scavenger Hunt Solved: The Banking & Accounting Tactical Brief
Task 1 — Get the Broad Rule Out of Everybody Else’s Fucking Way
First, inspect the rule itself.
If GLOBAL is a broad catch-all rule and more specific rules should handle some of those transactions, move the specific rules above it in the priority hierarchy.
QuickBooks applies only one rule to a transaction, and the highest-priority matching rule is applied first.
Then inspect the rule’s conditions.
Should it use Any?
Should it use All?
Should it contain additional criteria?
Should it use bank text rather than description?
Don’t automatically flip Any to All because somebody on the internet told you that’s more advanced.
Build the rule around the transaction you’re actually trying to identify.
Resistance Answer:
Specific rules first. Broad rules later. Logic based on purpose.
Task 2 — Blank Means Uncleared
Those blank statuses tell you that the checks are currently Uncleared in QuickBooks.
They do not prove that the checks never appeared in the bank feed.
Now investigate each check.
Was it issued?
Did the supplier receive it?
Was it cashed?
Was it replaced?
Is there a corresponding downloaded bank transaction?
Was it entered twice?
Does the bank statement contain anything corresponding to it?
Resistance Answer:
Blank is a status, not a fucking biography.
I would actually like that embroidered on something.
Task 3 — Void or Delete?
You’ve established that one check is genuinely a duplicate/error and never represented a real payment.
QuickBooks permits both voiding and deleting unnecessary transactions.
The difference matters.
When you void an eligible transaction such as a check, QuickBooks keeps the transaction in the books but changes its value to zero.
When you delete a transaction, QuickBooks removes it everywhere except the Audit Log.
So if you deliberately want the check number and transaction record to remain visible while eliminating its financial effect, Void makes sense.
If you’re certain the entry is simply a duplicate or erroneous transaction that shouldn’t remain in the books, deletion can also be appropriate; QuickBooks guidance explicitly allows deletion of obvious duplicates when you’re certain that’s what they are.
Resistance Answer:
Don’t memorize VOID GOOD / DELETE BAD.
Ask:
What happened, and what record should remain after I correct it?
⭐ Bonus Mission — Where Would You Investigate?
There isn’t only one valid answer here.
Good places to start include:
The bank statement — because that’s our external evidence of what actually cleared.
The QuickBooks account register — to inspect the recorded transactions and their statuses.
Bank Transactions — to examine downloaded activity, suggested matches, posted transactions and exclusions.
The Rules area — because we’ve already identified automation capable of misclassifying transactions.
Reconciliation reports/history — because reconciliation reports identify what was cleared and what remained uncleared during that reconciliation.
The Audit Log — particularly if previously reconciled information appears to have changed.
The goal isn’t to visit every screen because a checklist told you to.
The goal is to assemble enough evidence to answer:
What actually happened?
And only then:
What should QuickBooks show?
The Level 2 Rule I Want You to Keep
If you remember nothing else from this module, remember this:
Do not make QuickBooks agree with the answer you expected. Find out what happened and make QuickBooks accurately represent it.
That’s the difference between troubleshooting and number decoration.
A rule can be wrong.
A suggested match can be wrong.
A human can be wrong.
A transaction can be duplicated.
A reconciliation can be altered after it was completed.
And, yes, AI can confidently hand you an answer key claiming that a blank reconciliation status proves something about the bank feed that it absolutely does not prove.
The software gives us evidence.
The records give us evidence.
The bank gives us evidence.
The human evaluates the evidence.
That’s what we’re training.
Not somebody who can make a screen say $0.00.
Somebody who understands why it should say $0.00.
Wallace & Gertrude’s Final Assessment
Wallace remains confident in you because Wallace is a good boy and apparently has no concept of professional skepticism.
Gertrude has considerably more conditions.
She would like it formally documented that:
- automation is not authority;
- blank means uncleared;
- excluded does not mean posted;
$0.00is not inherently proof of correctness;- journal entries are not accounting duct tape;
- and investigate before you alter history.
She has also requested that nobody ask why she knows so much about Audit Logs.
HR has declined to comment.
Use the machine. Train the human.
And for fuck’s sake:
Don’t manufacture zero. Prove it.
✦ enjoyed this entry?