There is a particular kind of business that looks perfectly normal from the outside. It has customers, employees and revenue. It pays its bills. It has a bookkeeper, a bank account, a credit card, QuickBooks, Google Drive, and approximately 47 spreadsheets that nobody is entirely sure are still being used.
The company is functioning. The finance function is not.
Let’s call the company Harcourt Trades Inc. Harcourt is a growing Canadian services business with roughly 40 employees and about $8 million in annual revenue. Nothing is catastrophically wrong. There is no obvious fraud, no missing $500,000 cheque, no accountant running for the hills. There is simply entropy.
The Google Drive has folders called:
- Finance
- Finance 2023
- New Finance
- Invoices
- Invoices FINAL
- Invoices FINAL 2
- Old Stuff
- Taxes
- Tax Stuff
- DO NOT DELETE
Vendor names are inconsistent. One employee enters ABC Mechanical. Another enters ABC Mechanical Ltd. A third enters A.B.C. Mechanical Services.
The company has never established a consistent purchase-order process, so some vendors send invoices against POs, some don’t, and some apparently believe a PO is something the customer produces when they feel like it.
The chart of accounts has evolved organically. “Software,” “Computer Software” and “Subscriptions” are all in use. Someone created “Miscellaneous Expenses” several years ago, and it has become less of a category than a cry for help.
The owner occasionally puts personal expenses on the corporate card. Nobody has ever quite defined what counts as an owner expense, a reimbursable employee expense, a shareholder draw or a legitimate business expense.
And the bookkeeper? They’re doing what they’ve been asked to do. Mostly. They reconcile the bank, enter the obvious bills and post the obvious transactions to approximately reasonable accounts. They don’t always attach supporting documents. They don’t necessarily know which transactions deserve investigation, because nobody has given them a framework for deciding.
Last month, $175,000 of financing proceeds were deposited into the bank account. They were recorded as sales.
Not because anyone intended to misstate revenue, but because the bookkeeping process was effectively: “This money came into the bank. Where should I put it?” And there wasn’t a strong enough process sitting behind the question.
This is where the month-end close becomes interesting.
The close is not just accounting housekeeping
A month-end close is often described as the process of getting the books “done” at the end of the month. That’s true, but it’s incomplete. A meaningful close is a repeatable investigation into the state of the business. It asks:
- Did we capture everything?
- Is the balance sheet real?
- Does the P&L make sense?
- Are unusual transactions understood?
- Are revenues and expenses in the right period?
- Do the supporting documents exist?
- Are liabilities recorded?
- Are there transactions we cannot explain?
- What changed, and what needs somebody’s attention?
And, critically: what did we discover this month that we should prevent from happening next month? That last question is where a close stops being bookkeeping and starts becoming a management system.
Harcourt’s first close is going to be ugly
Imagine we take over Harcourt’s finance function on March 1. Our first instinct might be to “clean everything up.” That’s an admirable instinct. It’s also dangerous.
There are 1,400 transactions sitting in the accounting system. The vendor list is messy. The chart of accounts needs work. There are unexplained balance-sheet items, missing invoices, and old accounts nobody recognizes. We could spend six weeks cleaning everything.
Or we could establish a March close. Not a perfect March close. A real one.
We set a deadline. We define what “closed” means. We identify the accounts that must be reconciled and the transactions that require investigation. We create an exception list. And then we discover things. A lot of things:
- The $175,000 financing deposit is not revenue.
- Three credit-card transactions have no supporting documentation.
- There are two versions of the same vendor.
- A large consulting invoice relates to February but was posted in March.
- A recurring software subscription has been coded inconsistently for nine months.
- An employee has been paying a business expense personally and hasn’t submitted the reimbursement.
- An old prepaid-expense account carries a balance nobody can explain.
- The owner’s credit card has several transactions that need to be classified.
None of these discoveries means the close has failed. The discoveries are the close.
The exception list becomes the company’s to-do list
This is one of the most powerful ideas in a messy finance function. Instead of pretending the accounting system is clean, the close creates a controlled place for uncertainty to live. Harcourt’s March close might produce something like this:
| Issue | Owner | Action | Due |
|---|---|---|---|
| Financing proceeds coded as revenue | Controller | Reclassify | Apr 3 |
| Duplicate ABC Mechanical vendors | Bookkeeper | Merge and standardize | Apr 4 |
| Missing consulting invoice | Bookkeeper | Obtain invoice | Apr 5 |
| Owner card transactions | CEO | Identify personal vs business | Apr 8 |
| Old prepaid balance | Controller | Investigate | Apr 12 |
| Missing PO for major vendor | Operations | Establish PO process | Apr 12 |
Suddenly, “our books are messy” becomes six specific problems. And six specific problems can be solved. This is the beginning of operational discipline.
A close creates a forcing function
Harcourt could have discovered the $175,000 financing error at any point. But without a close, there was no particular moment when somebody had to ask: does this month’s revenue actually make sense?
The close creates that moment. It forces the organization to stop accumulating uncertainty. Every month, somebody has to say “these numbers are ready,” and somebody else has to be able to ask “how do you know?” That is an enormously useful organizational habit.
Businesses don’t generally become messy in one dramatic event. They become messy through hundreds of tiny exceptions that nobody resolves. A vendor sends an invoice without a PO. Someone doesn’t attach the receipt. A new software subscription gets coded differently. An owner puts something on the corporate card. A customer pays an unexpected amount. Someone creates a new Google Drive folder. A new employee doesn’t know where to put something.
Nobody thinks much of any individual event. Six months later, the finance function has become archaeology.
The close doesn’t fix the mess. It makes the mess fixable.
This distinction matters. A month-end close is not going to solve Harcourt’s Google Drive. It won’t teach vendors to submit proper invoices, redesign the chart of accounts, or decide whether the owner’s $3,400 dinner was a legitimate business expense. It certainly won’t turn an inexperienced bookkeeper into a controller. Those are different problems.
What the close provides is a recurring control point from which those problems can be identified, assigned and progressively eliminated.
Think of it less like cleaning a house once a year and more like weekly garbage collection. The garbage doesn’t stop being produced. You just stop letting it pile up.
Problems are rarely one-dimensional
Take the misclassified financing transaction. It would be easy to say “the bookkeeper made a mistake.” Maybe. But that’s not the useful diagnosis. Consider the chain of events:
- The company receives financing, and the transaction hits the bank.
- The bookkeeper sees a large inflow.
- There is no documented procedure for financing transactions, and the chart of accounts isn’t designed for them.
- Nobody reviews unusual cash movements during the month, and the close doesn’t include that review either.
- The bookkeeper doesn’t have access to the financing agreement.
- The CEO assumes the accounting team knows what the transaction represents. The bookkeeper assumes the CEO would say if something needed special treatment.
Nobody is behaving irrationally. The system is under-specified. That’s a very different diagnosis, and a far more useful one.
Give people information, and give them a way to use it
Even an excellent bookkeeper can only do excellent work with the information available to them. Without the loan agreement, card statements, vendor invoices, purchase orders, payroll information, expense policies, bank access, visibility into contracts, and someone available to answer questions, “do better bookkeeping” isn’t much of a strategy.
Equally, giving someone access to everything doesn’t solve the problem. If nobody has established what should be reviewed, when, by whom, what counts as an exception, how exceptions get resolved and where documentation belongs, you have simply handed someone a bigger pile of information.
Good finance requires both information and operating discipline. The close sits right in the middle of that relationship.
The second close should be slightly better
This is where it starts to compound. Harcourt finishes March, but the team doesn’t just close the month and move on. They ask: what did March teach us? The answers become April’s improvements.
| March finding | April change |
|---|---|
| Financing coded as revenue | All financing transactions identified and supported before close |
| Duplicate vendors | One vendor naming convention and a controlled vendor-creation process |
| Missing invoices | AP cutoff procedures and one standard place to submit invoices |
| Owner card confusion | A defined owner-expense policy, reviewed monthly |
| Messy chart of accounts | A chart-of-accounts redesign |
| Missing documentation | Material transactions must have support attached in the accounting system |
| Google Drive chaos | A documented finance folder structure and naming convention |
None of this happened because somebody had an inspired accounting moment. It happened because the close exposed the same friction often enough that the organization could fix it.
By June, the close looks completely different
Three months later, Harcourt isn’t a different company. It’s still growing. Receipts still go missing occasionally. Someone still puts the odd questionable lunch on the corporate card. A vendor will inevitably send an invoice with the wrong PO. That’s normal.
But now there is a system:
- The close has a calendar, and each account has an owner.
- There is a standard reconciliation package and an exceptions log.
- Material transactions have supporting documentation.
- The vendor list is controlled, and the chart of accounts makes sense.
- The bookkeeper knows what they are expected to review, and the controller knows where the risks are.
- The CEO isn’t being asked to explain 47 transactions at year-end.
Perhaps most importantly, everyone now shares an understanding of what “the books are closed” actually means.
The month-end close is only one-fifth of the solution
A strong close is powerful. It is also not magic. For a company like Harcourt, it helps to think of the finance function as five interconnected layers:
- The close. Did we capture, classify, reconcile and review what happened?
- The accounting architecture. Are the chart of accounts, entity structure, vendor and customer setup, and reporting model designed properly?
- The operating processes. How do invoices, POs, expenses, payroll, purchasing, approvals and payments actually flow through the business?
- The information environment. Can the people doing the work find the contracts, invoices, receipts and statements they need?
- The people and accountability. Does everyone know what they own, what good looks like, and when to escalate?
The close is perhaps one-fifth of the solution. But it’s a particularly useful fifth, because it touches all the others.
A good close is a feedback loop
That is ultimately what makes it so valuable:
Business activity → accounting → close → exceptions → investigation → process improvement → better business activity → better close.
The system improves because every month is another chance to find where it broke down. That’s very different from the traditional model: book everything, reconcile everything, produce statements, send them to the CEO, start over.
A modern finance function should instead be asking: what did we learn about the business this month, and what should be different next month because of it? That’s a much more interesting definition of a close.
The goal isn’t perfect books
This may be the most important point. A messy company doesn’t need a perfect finance function on day one. It needs a repeatable mechanism for becoming less messy.
That is what a good close provides. It establishes a cadence, creates accountability, surfaces exceptions, forces decisions, builds documentation and exposes missing information. It gives finance professionals a framework in which they can actually do good work.
Over time, the exceptions start disappearing. The vendor list gets cleaner. The chart of accounts gets better. The documentation improves and the processes become clearer. The bookkeeper gets better information, the controller spends less time hunting and more time analyzing, and the CEO gains confidence in the numbers.
Eventually the monthly close stops feeling like an archaeological expedition and becomes what it was supposed to be all along: a reliable monthly reset button for the finance function.
The Tuulyp perspective
At Tuulyp, we think about the finance function as more than the production of financial statements. Accounting tells you what happened. Controllership makes the numbers trustworthy. CFO advisory helps you decide what to do about them. Technology makes the system repeatable. Business intelligence makes the information useful. People and processes make the whole thing sustainable.
The month-end close sits at the intersection of all of it. It isn’t the whole solution. It’s the recurring mechanism that helps the rest of the solution take hold, and for a growing company with a messy finance function, that’s a surprisingly powerful place to start.
Harcourt Trades Inc. is a composite example. Names, figures and details are illustrative.