ProAdvisor Prep: Module 6 — Closing the Books Without Burying Them

Look at us.

Module fucking six.

We have navigated QBO.

Built clients.

Imported data.

Managed bank feeds.

Matched transactions.

Reconciled accounts.

Run reports.

Wallace and Gertrude are wearing party hats.

Something significant has clearly happened.

But before anybody starts firing confetti cannons and declaring themselves Lord High Accountant of QuickBooks, we have one more Level 1 topic to cover:

Closing the books.

We’re trying to protect historical accounting data from being casually changed after we’ve finished working with that period.

Because there’s nothing quite like spending hours getting historical books correct only for somebody to wander backward six months and casually edit something.

What Does “Closing the Books” Actually Mean?

Closing the books establishes a closing date in QBO.

Transactions dated on or before that date receive additional protection against changes.

Why?

Because once you’ve reviewed a period, reconciled the accounts, prepared reports, made necessary adjustments, and otherwise established that the books are correct, changes to historical transactions can have consequences.

Remember Module 4?

We respected the R.

Same philosophy.

History matters.

Changing an old transaction can affect balances, reports, reconciliations, tax information, and everything built on top of that transaction.

Closing the books creates a boundary that basically says:

We’re done with this period. Don’t casually fuck with it.

I approve of this feature.

Setting the Closing Date

In current QBO, closing-date settings live under:

Settings → Account and settings → Advanced → Accounting

From there, authorized admins can establish or change the closing date and manage the closing-date password.

And here’s another perfect example of why we’re learning concepts rather than tattooing menu paths onto our bodies:

Intuit changes shit.

Know what a closing date does.

Know why you would use one.

Know what happens afterward.

If Intuit moves the setting six months from now, you can find the damn thing again.

Warning or Password?

QBO provides protection around changes to closed periods.

Depending on the configuration, users attempting to change transactions dated before the closing date can encounter a warning, and closing-date protection can include a password.

Now, some may tell you:

ALWAYS USE THE PASSWORD. GOLD STANDARD. MAXIMUM SECURITY.

I’m not doing that.

Because we’re learning how the feature works, not pretending every business has identical internal controls.

The important concept is:

A closing date creates protection around historical transactions.

A password adds another level of control.

Which level is appropriate depends on the business, its users, responsibilities, workflows, and accounting procedures.

Look at that.

Nuance.

Gertrude hates it, but accounting apparently requires some.

Can Closed Books Ever Be Changed?

Yes.

And that’s important.

Closing does not mean freezing financial history in carbonite for eternity.

Sometimes legitimate corrections need to happen.

An accountant may discover an error.

A tax professional may provide an adjustment.

Something may need correcting after the period was originally considered complete.

Authorized admins can change the closing date or password when necessary.

The goal isn’t:

NEVER CHANGE HISTORY.

It’s:

DON’T CHANGE HISTORY WITHOUT KNOWING YOU’RE CHANGING HISTORY.

That is a much better control.

So How Do We Know If Somebody Changed Something?

QuickBooks provides an Exceptions to Closing Date report.

Current Intuit instructions place it under Reports → Standard reports, where you can search for Exceptions to Closing Date. It shows changes made after the books were closed.

This is extremely useful.

Because imagine this:

You reconciled December.

Everything balanced.

Reports looked correct.

Books were closed.

Three months later, something from December has changed.

Instead of immediately accusing the office manager, the client’s cousin, Mercury retrograde, or the dog—

check the evidence.

That’s why audit trails and exception reporting matter.

Accounting loves receipts.

Sometimes literally.

Before You Close Anything: Is the Period Actually Ready?

Common Thought Process:

Apparently:

ALL A/R AND A/P MUST BE ENTIRELY CLEAN.

No.

A business can legitimately have unpaid customer invoices and unpaid vendor bills crossing reporting periods.

That’s literally why Accounts Receivable and Accounts Payable exist.

The question isn’t:

Does every open balance equal zero?

The question is:

Are the balances accurate?

Before closing a period, you want confidence that the accounting work appropriate to that period has been completed and reviewed.

That may include things such as:

• reconciling relevant accounts,
• reviewing outstanding A/R and A/P,
• correcting known errors,
• recording necessary adjustments,
• reviewing financial reports,
• and coordinating with the appropriate accounting or tax professionals when needed.

Notice the difference?

Review open items.

Don’t magically delete legitimate ones to make the ledger aesthetically pleasing.

And No, December 31 Isn’t a Magical Universal Closing Date

Some will say:

“Usually December 31st of the prior year.”

Maybe.

For a calendar-year business closing an annual period, December 31 makes perfect sense.

But not every business operates on the same fiscal year, and books can also be closed through other completed periods depending on the organization’s workflow.

The important thing is understanding which completed period you’re protecting and why.

Again:

Concept.

Not memorized ritual.

Module 6 Scavenger Hunt

Last scavenger hunt of Level 1.

For now.

Open your training/practice environment and see if you can find:

• Account and settings.
• The Advanced accounting settings.
• The option related to closing the books.
• Where a closing date would be entered.
• The available protection/password options.
• The Exceptions to Closing Date report.
• Information showing what happens when somebody tries to modify a closed-period transaction.
• The permissions required to manage closing information.

Bonus Mission

Explain this without looking:

Why would changing a transaction from a previously completed period potentially matter?

If your answer includes some combination of:

reports, reconciliations, balances, historical accuracy, taxes, or downstream accounting

—we’re getting somewhere.

Resistance Coffee & Books Attempts Time Travel

Our beloved fictional accounting disaster has returned for one final Level 1 incident.

The December books have been reviewed and completed.

A closing date has been established.

Then somebody realizes an old December expense was entered for:

$480

when the source documentation says:

$840.

Do we:

A.

Leave incorrect information forever because THE BOOKS ARE CLOSED AND THE VAULT MUST NEVER OPEN.

B.

Understand the reason for the correction, follow the appropriate process for making an authorized change, and verify its effects afterward.

C.

Delete December.

We’re going with B.

Closing the books isn’t supposed to preserve mistakes.

It’s supposed to prevent uncontrolled changes to information we’ve already established.

That’s an important distinction.

Module 6 Mini-Quiz

Question 1

What is the primary purpose of establishing a closing date?

A. Delete old transactions so QBO runs faster.
B. Add protection against changes to transactions in a completed historical period.
C. Prevent clients from ever opening QuickBooks again.

Question 2

Can a transaction from a closed period ever legitimately need correction?

A. Yes.
B. No. Financial history becomes sacred scripture at midnight.
C. Only if Wallace approves it.

Question 3

Where can you investigate changes made after books were closed?

A. Profit & Loss
B. Exceptions to Closing Date report
C. Gertrude’s notebook of suspicious activity

Question 4

A business has legitimate unpaid customer invoices at year-end.

Does that automatically mean the books cannot be closed?

A. Yes, A/R must always equal zero.
B. No. Outstanding receivables can be legitimate; what matters is that they’re accurate and appropriately reviewed.
C. Delete the customers.

Question 5

Why should historical transactions be changed carefully?

A. Changes can affect reports, reconciliations, balances, and other downstream accounting.
B. Old transactions become emotionally attached to their original amounts.
C. QBO charges them rent.

Answers: B, A, B, B, A.

Gertrude selected C for Question 3 because she has apparently been maintaining unauthorized documentation.

We’ll address that in Level 2.

Six Modules Down. And No, We’re Not Done.

Whoa there, Sparkles.

Completing training material and becoming certified are not the same thing.

Certification has its own enrollment and assessment requirements through the ProAdvisor Academy. Intuit specifically warns that simply completing courses without enrolling in the certification program does not grant the certification or badge.

But We Did Finish Something

We’ve reached the end of the six Level 1 modules I’m currently covering here.

And look at the process we’ve built:

Navigate → Build → Import → Review → Match → Reconcile → Report → Protect.

That’s a hell of a lot more useful than memorizing six sets of screenshots.

We’ve learned how information enters QBO.

How it moves.

How we review it.

How we compare it with reality.

How we turn it into reports.

And now how we protect completed historical periods from casual changes.

That’s the foundation.

Not mastery.

Foundation.

And I like that distinction.

What Comes Next?

We’re not stopping the blog series here because this is as far as I’ve personally gotten.

I’m also not going to race ahead, scrape together somebody else’s notes, and pretend I know shit I haven’t learned yet.

I’m doing this alongside you.

When I learn more, you get more.

And there is absolutely more.

Intuit currently calls the next QBO certification level QuickBooks Online Certification Level 2—what used to be called Advanced Certification. Intuit also offers additional certification paths, including Payroll.

I’m working on those next.

When I’ve gotten far enough into them to have something useful to teach instead of just something to repeat, Accounting Against the Machine will continue.

Because that was always the point of this category.

Not:

Watch me pretend to be an expert.

But:

Come learn this shit with me.

For Now…

Six modules.

A disturbing amount of QuickBooks.

Several fictional accounting emergencies.

One Resistance Coffee & Books.

One increasingly judgmental Sphynx.

One extremely patient German Shepherd.

And an entire series built around one idea:

The machine is useful.

Learn it.

Use it.

Automate the repetitive shit.

Let it make your work easier.

But understand what it’s doing.

Know why you’re clicking.

Know what the numbers mean.

Know when something looks wrong.

And know enough to question the machine when necessary.

Because the goal was never to become better button-pushers.

The goal is to become harder to replace.

So yes.

Celebrate this one.

Wallace and Gertrude have party hats.

That’s how you know it’s serious.

But we’re not graduating.

We’re not finished.

We’re just getting better.

I’ll see you when I’ve got enough Level 2 and Payroll under my belt to start causing trouble again.

Until then: use the machine. Train the human. ❤️

*For anyone pursuing this credential, here is Intuit’s current ProAdvisor Academy and certification guide. It explains enrollment, certification, badges, and training.

Update: And Yes, I Finally Took the Damn Exam

So there’s a mildly embarrassing epilogue to Level 1.

I finished the training. I wrote all of this as I diligently completed the sections myself. I moved on to Level 2.

And apparently forgot that at some point I should actually take the fucking certification exam.

I remembered this morning because my students are working on theirs and needed some help, which caused the spectacular realization that perhaps their sme trainer should stop wandering around with all the knowledge and none of the shiny paperwork.

So I took it.

I passed.

And now I have the shiny little Credly badge to prove that I eventually remembered how certification works.

View my Intuit QuickBooks Certification Level 1 badge on Credly

The badge is nice.

Knowing what the hell you’re doing is better.

And if anything perfectly summarizes this entire project, it’s probably me teaching other humans to become Certified ProAdvisors and then suddenly realizing:

Oh shit. I should probably go take mine.