Clean Up Operations, 101

Finance Operations - Strategy - 12 min read

Clean, organized accounting, all one one easy to read screen.

The problem we solve most often? Messy books. 

It's no secret that messy books are one of the most common corporate finance issues for businesses of all shapes and sizes (and it is the number one reason for booking discovery calls at Level). And while companies know that keeping clear, correct bookkeeping is important, not enough of them consider it an essential. If that’s you, we hope you’ll change your tune. “Clean books are not optional, says Sarah Jordan, Level Managing Partner and Fractional CFO, "they are the foundation for accurate reporting and strategic planning." This article shows you how to do it.

Books get disorganized because teams lack the capacity or know-how to set up the rigorous systems needed to keep books tidy and bookkeeping streamlined. In our opinion, an unconsidered tech stack—or no fintech stack at all—is a fundamental root cause of messy books. It's also why many teams need a perspective different from an accountant's or a bookkeeper's to sort things out. A CFO's fluency across both business operations, financial operations, and technology is essential in overseeing the work of making books compliant and strategically informative. 

Our goal for client clean-ups? To set up a complete, simple, and streamlined system that your team can keep clean month and month, year after year. Because nobody wants to go through the process a second time. Read on to learn: 

  • What clean books really look like, and the red flags that signal a clean-up operation

  • How to set up your tech stack to keep books compliant and strategically informative 

  • How to prepare for a clean-up operation, even before you make the call to a fractional CFO

What does it mean to have 'clean' books? 

Not all of us are accountants, but all of us should have an accountant's understanding of what clean books look like. We define cleanliness by two standards: compliance and operations. 

Compliance or statutory cleanliness is entirely focused on accuracy of the financials. Companies are legally required to share accurate financials with shareholders and investors, typically through filings with regulators like the SEC, so those stakeholders can make informed decisions. It's also required in order to properly file business taxes. In other words: it's not optional. 

To achieve this level of cleanliness, you need your accountant and bookkeeper to understand GAAP accounting and revenue recognition rules. In e-commerce, for example, revenue can't be recognized until an item has been shipped; customer payments must be categorized as liability until orders are fulfilled. Typically, that's a 36 hour window, but backorders and preorders also apply by this rule. You also need to ensure that the team is reconciling back to the bank every month—-if there is a difference between your ERP and bank statements, that difference needs to be accounted for.  

Operational cleanliness is more variable, and organizations do interpret it differently. Our standard looks something like this: all of the transactions live in one place, and it's easy to see how transactions are properly categorized per budget line. And teams can make quality strategic decisions based on real-time (or close to it) financials. 

For example, instead of all of the travel expenses for the annual conference being categorized under "General Travel," these expenses might more usefully be categorized under the budget travel line for the annual conference itself, so that they show up properly in the P&L of that event. That enables your team to make the appropriate decisions about how to allocate funds to next year's event, or even to attend at all. The point here is to make smart strategic decisions based on real performance rather than speculation. 

Pro-tip: To get to this level of cleanliness, all teams need to understand how to properly log expenses under budget categories, so that the finance team isn't constantly following up individual transactions. And the line of communication between departments and finance needs to stay open. That looks like a monthly finance meeting with department heads to reconcile expenses. 

Bookkeeping redflags 

When nobody knows where the money is, or how much money has been made or spent, or tax time is a scramble, it's time to attend to your books, no question. 

But sometimes, clients come to us with a vague sense that something is off—because we don't know what we don't know—and our team needs to do more sleuthing. In these cases, our first question is always, "how many finance platforms and systems are you using?" It's a red flag when an organization has multiple finance platforms that do similar work or don't talk to each other, because every new tool introduces operational complexity into the bookkeeping process.

So, yes, a retailer using a 3PL will have a WMS in addition to an ERP, and perhaps an e-commerce site like Shopify. But more systems mean that data has to show up reliably across all of them; if those systems aren't reliably integrated, your books won't be accurate. That's a more common problem than many companies think, and it leads to inaccurate reporting, noncompliance, and poor strategic decisions. 

Using several banks is another red flag. Four or five accounts at one bank isn't an issue—that's a very normal treasury security setup, no qualms there—but unless you have a very specific need for an account at both Wells Fargo and Bank of America, using multiple banks makes it almost impossible for teams to transparently understand the finances. (The exception: if an investor exclusively uses one bank as a repository mechanism, and thus your organization needs an account there to receive funds through that investor). 

The second you add more systems or accounts into the mix, you have to establish a process for reconciling across the stack, and ensure that all data is formatted in the same way. That can be tricky across different interfaces. And if the data integrity of those secondary and tertiary tools aren't maintained, the books won't be accurate. 

Pro-tip: Core products like Netsuite and Quickbooks have so many functionalities that teams should understand and trial out before adding another fintech product to the stack. We love many of the new solutions in the market for ease of use and design interface, but the fact is that integrating another product into your stack requires yet more data integration—and it's not just as easy as programming a Zap. 

Tighten up tech procurement to keep books cleaner.

When a tech stack is cobbled together, it's been sourced by varying teams purchasing solutions independently for their work, without the oversight of a CFO or CTO (ideally, working in tandem). Those entities question how a solution fits within the total tech stack, or if the solution might create complexity or deliver redundancy.

Payment processing tools are the most likely culprits. No one team is going to have the authority to choose a WMS, for example, but we do see companies use multiple payment processing platforms all the time. It's easy to see how an organization can use ten different ways to get paid, from check to card to Stripe to ACH. 

We get it, especially from a merchandiser's point of view: it's not a wrong decision to enable customers to pay you however they want to do so. But if you don't have an accounting system into which all of those systems feed—and if you don't have a very tight process for month-end reconciliation—those systems will get out of sync. The result is misrepresentation across every number: income, fees and charges, discounts, and ultimately, margin. 

Importantly, we see teams struggle to write effective systems RFPs all the time. Doing it right can be time consuming, but a good RFP is invaluable in ensuring that every new solution actually serves your teams' needs. Booking a demo isn't enough: in fact, "It's the exact wrong way to do an RFP," says Level CFO Sarah Jordan. "Sales teams will always show you the features and benefits they think will work for you, and of course it looks fabulous. But without a specific grounding in your existing workflows and systems, you'll be less likely to see real ROI on that purchase." 

We released our Level Guide to SaaS RFP Best Practices alongside this piece for those of you seeking  a deep dive into tech procurement. RFPs get more detailed as tools need to be integrated into existing systems, or if the organization is planning to switch to a different system: this requires detailed event logging across affected workflows to truly understand the specs you're looking for. In your demo, ask the sales team to show you how the tool handles those specific tasks and workflows from start to finish. 

Be aware of the fact that no one solution will do everything you need. And be wary of bolting on new solutions just because they cover 1 or 2 annoying small holes in the existing tech stack. 100% automated efficiency is unrealistic, and costly. Ideally, your senior IT leader will help every team determine where to hold the line against bolted on solutions, and where to invest in more flexibility. 

Pro-tip: Always, always ask if a tool can be connected to your existing systems at the outset. If it can't, it's an automatic no-go. 

Make the most of the features your products do have.

One common reason for disorderly books is that teams simply haven't taken the time to automate processes that can be covered by their software, or they may not yet understand all of the ways that their systems can work for them. 

Products roll out new features all the time, and it can be hard to stay on top of those changes. But there are a few key finance practices that should always be automated today; doing so helps make reconciliation much more streamlined. We regularly help businesses automate simple processes like bill pay, uploading bank statements to EOPs, and reconciling income and outflows across bank accounts. 

Pro-tip: If you haven't yet transitioned your bookkeeping from QuickBooks Desktop to QuickBooks Online, we'd highly suggest that you do. QuickBooks Online makes it easier for you, your bookkeeper, and your accountant to work in the same file without emailing backups back and forth. You can log in from any computer with an internet connection, and bank transactions can be imported automatically instead of entered by hand. You also no longer have to install updates or manage your own backups. The tradeoff is an ongoing subscription fee rather than a one-time license, so compare the costs for your situation.

How to get your books sorted.

It's evident that your books need a clean-up. You know things aren't working as they should. How do you get started? 

The first step is to task a finance person with both technical expertise and a total operations understanding with the project. At the end of the day, tech supports the operation. If that person doesn't have an understanding of how different units operate within the system of the business, they won't be equipped to make determinations about how different technologies work together. 

Realistically, that person is a CFO, perhaps working quite closely with the COO and CTO. The CFO perspective is needed to get all of the pieces working properly, even if there are other more junior finance staff on board, because a broader, holistic perspective is needed. 

Once you have the right person in place, you should expect the work to take months, not weeks, depending on the depth and complexity of the issues at hand. Expect the CFO to spend time with every team asking hard questions about each system currently in use—and prepare to have a strong rationale for each purchase. In fact, this is great prep work, even before bringing in a clean-up lead: 

  • Compile a complete list of your FinTech stack, and any other tools that talk to it

  • Understand how and if those tools currently speak to each other

  • Map duplication of workflows across the stack, and eliminate those you know you don't need now

Bringing that list to a first call with a CFO can speed up their initial discovery work and help them hit the ground running faster. 

Projects like catching up on a few months of unreconciled bank and credit card accounts, recategorizing misclassified transactions, and organizing missing receipts and documentation are less complex and take a few days to a few weeks; something like a systems migration is a much more demanding project and can take months to prepare and complete.


Honestly, we love clean-up projects. There is tedium involved, to be sure. But the relief on our clients' faces when they can finally see the real chassis of their business is priceless. And then we can get to the exciting work of building an engine for the journey ahead. 

Our team has conducted countless clean up operations in our years of experience for businesses of varying size and complexity, and across industries. From retailers to nonprofits to brick and mortar SMBs to SaaS companies, we've seen time and again how working through the process of cleaning up the books gives companies the clarity and confidence to dream bigger and scale better. 

Let us help you get it done, for good. Book a call with a Level Pro today.

Next
Next

Conscious Consumerism Is No Longer Niche. Here's How Retailers Can Respond In Kind.