Why Your New Finance System Is a Finance Project, Not an IT One
Every integration works. Every login holds. Then someone asks one simple question about the numbers, and nobody can answer it.
Here's a scene that plays out more often than anyone admits. A growing business invests serious money in a new finance system. Someone capable sets it up, an IT consultant, the software provider's onboarding team, or the most tech-savvy person in the office. Everything connects. Data flows in from the bank, invoices go out, nothing crashes. By every measure the setup was judged on, the project is a success.
Then, about six months in, you ask a simple question. Which of my services actually makes money once I account for the time they take? Or: which clients are genuinely profitable, and which ones just feel busy? And the answer takes three days, two exports and a manual spreadsheet, because the system was never set up to answer it.
The software isn't broken. It's doing precisely what it was built to do. The problem is that nobody told it what it was for.
1. Installing the system and designing it are different jobs
This is the distinction that costs businesses the most, and it's the one most often missed. Setting up a finance system is not a technology project with finance implications. It is a finance project with technology implications.
The technical side, connecting the bank feed, setting up users, linking your till or booking software can be done by anyone competent, and usually is. But making the software run and deciding what it needs to do are entirely different questions. The second one belongs to whoever understands your numbers.
Take a salon owner moving onto a cloud accounting platform like Xero. The booking system connects, payments flow through, the bank reconciles. Technically flawless. But if nobody decided up front to separate treatment income from retail product sales, or to track each stylist's chair as its own income stream, the system can't tell you which parts of the business actually pay the rent. All the data arrived. None of the meaning did.
2. The decisions that matter are finance decisions
The chart of accounts, the underlying list of categories that determines what you can and can't report on is a finance decision. So is the tagging and tracking structure that lets you slice income by service, location, client type or project. So is the order things happen in: when a sale is raised, when the income is recognised, when the invoice goes out, when the cash is chased. Get that sequence wrong and the numbers stop meaning what you think they mean.
None of this appears on a technical setup checklist. It can't, because it depends entirely on how you run your business and what you'll want to know about it. A photographer who shoots weddings and sells prints needs a different structure from a café that also does outside catering. The software's default template fits neither of them well, it fits an imaginary average business that doesn't exist.
A finance system that merely works is not the same as a finance system that earns its cost.
3. The trap is that a badly set-up system still works
Get the foundations wrong and nothing visibly breaks. Invoices still send. VAT returns still file. That's exactly what makes it dangerous, the wrong structure gets quietly baked in, and you don't discover it until you try to lean on the numbers.
Usually that moment arrives with the stakes at their highest. A bank asks for management accounts to support a loan. A potential investor or buyer wants profitability by service line. You're deciding whether to take on premises or a second member of staff, and you need to know which part of the business would fund it. The question is simple. The system can't answer it, because it was never asked to.
4. The real cost isn't the software, it's the rebuild
When a system is configured without finance thinking in the room, the bill arrives later, and it's bigger. Rebuilding a chart of accounts retrospectively. Re-categorising months, sometimes years of historic transactions so this year's figures can actually be compared with last year's. Paying for reporting that still can't answer the questions that matter, right when they matter most.
You paid once to set it up. Now you're paying again to unpick it. The second invoice is always larger than the first, partly in fees, but mostly in the decisions you made in the meantime on numbers that couldn't be trusted.
5. Five things to decide before anyone touches the setup
Before the technical work starts, or before you accept the software's defaults, these should be decided by someone who understands both your business and your numbers:
The chart of accounts. Built around how you actually run and report on the business, not the software's default template.
Tracking and tagging. Every way you'll ever want to slice the numbers, by service, location, stylist, project, client type agreed up front, because retrofitting them is brutal.
The order of operations. From quote or booking, to invoice, to recognising the income, to collecting the cash, sequenced so the data stays clean end to end.
Reporting requirements. The questions you, your bank and any future investor or buyer will ask, designed in from day one rather than bolted on later.
Who owns the data going forward. Someone has to maintain the structure, or it quietly degrades with every new starter and every workaround.
Save that list. It's the difference between a system that runs and a system that earns its cost.
Where to start
If you're about to move onto new software, pause the technical setup for a week and get the five decisions above made first. It will feel like a delay. It's the fastest week you'll ever spend on your finances.
If your system is already live and can't answer the questions you actually care about, don't assume you're stuck with it. A structured review, what the system currently captures, what you need it to tell you, and the shortest path between the two, usually costs far less than living with numbers you can't use.
Owl Accounting helps small businesses design and rebuild their finance systems so the numbers answer real questions if that sounds familiar, get in touch.