How to know if your finance operations are ready for the next entity
- What actually breaks when you add another entity
- Five questions to ask before adding another entity
- What a fifty-location franchise learned about standardization
- Structuring approvals across multiple entities
- AI is accelerating multi-entity reporting, but only when the foundation is solid
- Technology amplifies whatever process you already have
- Where to start
There’s a moment in most growing businesses where someone raises the idea of adding another entity. A new jurisdiction, a subsidiary, a separate legal structure for a new product line. The commercial logic usually makes sense, and the legal and tax reasons are clear enough.
What tends to get less attention is whether the finance operations underneath can actually handle it. Adding an entity doesn’t just add another set of books. It exposes every gap, inconsistency, and informal workaround that was previously hidden inside a single-entity setup. The processes that felt manageable at one entity start to strain at two, and by three or four they can quietly fall apart.
A recent ApprovalMax webinar session brought together Aaron Patrick, Lara Manton, and James Goulsbra to unpack a question that comes up constantly in growing businesses: when is the right time to put AP controls in place, and what does a well-run process actually look like once you do?
• Adding a second entity doesn’t double the complexity. It exposes it. Every undocumented process, inconsistent naming convention, and informal approval becomes a problem that multiplies across entities.
• Half of finance teams take more than six days to close their books. If your close is already slow with one entity, a second will push it further.
• Most businesses can’t describe their own approval process. If the answer to “how does this get approved?” is “I send an email and someone gets back to me,” that process won’t survive a second entity.
• One construction company calculated $200,000 a year in time savings by structuring approvals across 10 to 15 entities. They were paying around $1,000 for the tools.
• Ask your team what the process actually is. If you get fifteen different answers, that tells you exactly where to focus before adding another entity.
What actually breaks when you add another entity
The most common assumption is that adding a second entity means copying the first one’s processes across. Sometimes that works, especially when the entities are similar in structure, team size, and approval needs. But the more interesting and more common scenario is when you can’t simply copy and paste.
A group with a startup café and an established restaurant will need different approval routing and different spend thresholds. A business expanding into a new jurisdiction faces different tax rules, reporting standards, and sometimes different currencies. The approval workflow that made sense for entity one may actively slow things down for entity two.
The biggest barrier tends to be documentation. Many businesses have never formally written down their approval process, and the gap only becomes visible once they try to replicate or adapt it for a new entity. If the current process lives in people’s heads rather than in a system, scaling it reliably becomes very difficult.
Half of finance teams take more than six days to close their books. Nearly everyone is struggling with poor data management. And half of CFOs say integration is their number one challenge. These pressures compound significantly with every entity you add.
Five questions to ask before adding another entity
During the session, a useful self-assessment framework was shared. These five questions reveal how ready your finance operations actually are, and answering honestly can save months of painful retrospective cleanup.
-
Can you state your committed spend across all entities this week, within five minutes, without opening a spreadsheet? If the answer requires pulling data from multiple systems and cross-referencing manually, that process will break under the weight of another entity.
-
Does your month-end close take four business days or fewer? A close that already stretches to six or ten days with one entity will only get longer with two. The manual reconciliation, chasing, and cleanup that drives slow closes multiplies with each additional set of books.
-
Do you have consistent, documented approval rules across all of your entities? This means all of them, with clear thresholds, defined approvers, and escalation paths that exist in a system rather than in someone’s memory.
-
Can you pull a consolidated P&L across all entities in under ten minutes without touching a spreadsheet? If consolidation currently involves exporting trial balances, running VLOOKUPs, and manually aligning chart of accounts entries, adding another entity will make that process significantly more painful.
-
Does your finance team receive operational data before it hits the accounting system? Knowing what’s been quoted, committed, or in progress before the invoice arrives gives finance teams the context they need to review and approve with confidence.
Most attendees in the session scored somewhere in the middle, with a few at zero or one and only one person in strong shape. The honest scores tend to reveal the gaps that matter most.
What a fifty-location franchise learned about standardization
One of the clearest examples from the session was Mobility City, a mobility equipment and repair franchise that had scaled to around fifty locations. Each location was running its own QuickBooks file, with custom reports, manual VLOOKUPs, and no standardized naming.
The result was predictable: a mobility scooter was called “blue scooter” in one location, “teal scooter” in another, and the brand name in a third. Individually, each file made sense to the person managing it. At group level, wrangling that data into a consolidated view was a nightmare.
The unlock came when they stopped thinking of themselves as fifty independent locations and started operating as a national company. That meant standardized naming conventions, consistent chart of accounts structure, and a repeatable process for onboarding new locations. The rollout took a year of test locations and stress testing, but they ended up with 95% adoption across all entities and a system that could scale to the next fifty locations without rebuilding from scratch.
Structuring approvals across multiple entities
Approval processes are one of the first things to strain in a multi-entity setup, because each entity may need different routing, different thresholds, and different approvers. A tool like ApprovalMax helps here by letting finance teams build flexible approval matrices tailored to each entity’s needs, while keeping everything visible in one place. Approvers can act from a mobile app, Slack, email, or the web app, including setting a substitute when they’re on holiday, and they don’t need access to the underlying accounting system to do it.
An Ontario construction company running 10 to 15 entities on QuickBooks Online calculated $200,000 a year in time savings after structuring their approvals this way. Their annual cost for the tooling was around $1,000. Even setting aside the reduction in risk, the return on that investment was difficult to argue with.
AI is accelerating multi-entity reporting, but only when the foundation is solid
One of the more forward-looking threads in the session covered how AI is starting to change multi-entity reporting. A VC-backed recruitment firm with fifteen entities across Xero and QuickBooks pulled everything into a single AI-powered model. Their CFO asked which software tools the company was paying for across all entities and instantly discovered five separate licenses for the same platform, with no collective bargaining. The renegotiation that followed saved thousands.
That kind of insight is powerful, but it only works when the underlying data is clean and consistently structured. AI-generated fake invoices are also a growing risk on the accounts payable side, because they can look remarkably similar to legitimate bills. The efficiency gains from AI in finance are real, and they’re accelerating, but the human in the loop remains essential, especially in a function where the stakes are high and a hallucinating model during a board presentation is something nobody wants to experience.
Technology amplifies whatever process you already have
One of the most grounded observations from the session was a simple one: technology amplifies whatever process you already have. If the process is well-mapped and clearly documented, layering in automation enforces it consistently across every entity. If the process is a mess, automation just creates more noise and people stop using the tools.
Processes also drift over time, especially in multi-entity environments. People leave, new people join, small tweaks get made informally, and before long ten people have ten different versions of how things are supposed to work. Auditing that regularly by asking the team directly what they actually do, rather than assuming the documented process reflects reality, is how you close that gap before it compounds across entities.
Where to start
If you’re considering adding another entity, or if you’ve already added one and things feel harder than they should, here’s where to focus:
- Run the five-question self-assessment honestly. The gaps it reveals are the exact areas that will cause problems at the next entity.
- Document your approval process by watching how it actually works today, because the version in people’s heads and the version that plays out in practice are often very different.
- Standardize naming conventions, chart of accounts structure, and reporting cycles across all entities before scaling further. Fixing these retroactively across ten entities is exponentially harder than getting them right across two.
- List the operational data that needs to be consistent across every entity, stack-rank it by importance, and use that list as the starting point for any implementation conversation.
- Build a feedback loop. Enable the team on the process, review it regularly, and refine it over time so that the system improves alongside the business rather than falling further behind it.
This article is based on a ApprovalMax webinar featuring Matt (ApprovalMax), Harry (Joiin), and Mattis (Method CRM). Watch the full recording here.
