At a glance
- A consolidated view needs three things per unit: a mapping to one reporting chart, a rule for balances between related entities, and a close calendar all units can meet.
- Three approaches exist: migrate every unit to one ERP, add a reporting layer over the existing ledgers, or add an agent that normalizes and maps the ledgers and drafts the consolidation for review.
- The hard part is rarely the roll-up itself. It is the account mapping, because two units can book the same cost under different names, numbers and levels.
- A mapping, an elimination or a close adjustment is approved by your own finance staff. The agent prepares it and logs it.
- If every unit already sits in one system that consolidates natively, you do not need any of this.
Why do separate accounting files for each unit resist a single franchise group roll-up?
Every unit's books are their own set of ledgers: a chart of accounts, a transaction history and a close date. A consolidated view has to line those sets up. Two situations look alike but are not:
- Operator group: owns many franchise units in separate companies and consolidates its own entities.
- Franchisor: collects numbers from independent franchisees and aggregates them for comparison, which raises separate questions about access and permission.
Intuit's help center shows the problem in miniature. For QuickBooks Online Advanced companies, Spreadsheet Sync can combine multiple-period Profit and Loss and Balance Sheet reports from several company files. Accounts combine only if they share the same name, type and hierarchical level; spelling differences or different account numbers keep them apart[1]. Two units that book the same cost under two labels stay on two lines.
Inside one ERP the mechanics are built in. If company-owned units are set up as subsidiaries, NetSuite OneWorld documents consolidated data across them[5], and Sage Intacct documents consolidation entries, including eliminations, posted to an elimination account[4]. Both assume the entities already live in that system, which is the migration this article is about avoiding.
Which consolidation approach fits a group that cannot move every unit at once?
Consolidating franchisee financials means turning many separate ledgers into one reporting view. The table compares three ways to do that. The last column is the test that matters: can the approach start while most units stay on their current software?
| Approach | What it fixes | What it does not fix | Fit when units cannot migrate together |
|---|---|---|---|
| Full ERP migration, one multi-entity system for every unit | Puts every unit in one system with consolidation built in. NetSuite documents consolidated data for related subsidiaries [5]. Sage Intacct documents elimination entries for inter-entity balances [4]. | The cutover itself: historical data conversion, retraining each unit's bookkeeper and running two systems during transition. Independent franchisees may not agree to switch. | Fits units you control, such as company-owned locations or a roll-up with a fixed integration plan. Poor fit when the units are many and move at different speeds. |
| BI or reporting aggregation layer over existing ledgers | Connects to units on different platforms. Fathom's FAQ says it consolidates between Xero, QuickBooks, MYOB or Excel and supports inter-company eliminations [2]. | It reports on the books as they are kept. Fathom's FAQ says a consistent chart is not necessary but recommended, and that it is a management, not statutory, tool [2]. Coding differences between units remain someone's job. | Fits when units sit on a few supported platforms and the need is management reporting. Test it on the units whose charts differ most. |
| Agent-assisted chart-of-accounts normalization, with the ledgers left in place | Reads each unit's export, proposes a mapping to one reporting chart, flags unmapped and inconsistent accounts, drafts eliminations, and assembles the roll-up. New units are added as another mapping, not another project. | It does not replace a system of record, correct bookkeeping errors at the source, or approve anything. A person on your finance staff approves the mapping table and each adjustment. In a pilot, measure the share of proposed mappings your staff accept unchanged. | Fits groups with many units on mixed systems that need account-level normalization before reporting. Less useful if the units are already few and similar. |
The approaches combine. One sequence is to normalize and consolidate first, then migrate only the units that earn a move for their own reasons. The mapping carries over, because the reporting chart stays the same. Docyt is a different case: its page describes an AI-native ERP for franchisees on one AI-native ledger, and lists switching from QuickBooks, NetSuite or Sage [3]. That is a migration to a franchise-specific platform, not a layer over existing ledgers.
Can you get one P&L across all locations without migrating everyone?
Yes, provided the mapping step is done explicitly. A consolidated P&L is a sum of mapped accounts, and the system each unit keeps its books in matters less than whether each account has an agreed reporting line. The three steps are mapping, eliminating related-entity balances, and reviewing before release.
Franchise groups have a few lines that deserve a named mapping row and an owner, not a footnote. We state no rates or amounts here; those come from your own agreements.
- Royalty and brand-fund expense
- Management fees charged between entities
- Owner distributions
- Costs the parent pays on behalf of a unit
How do you map and normalize disparate charts of accounts?
Normalizing means translating each unit's accounts into one reporting chart, one row at a time, and recording who approved each row. The mapping table has these columns: unit, source system, source account, reporting account, rule, approver and effective date. An agent can propose rows and flag the ones it is unsure about. Your staff accept, change or reject each proposal.
If your units keep separate QuickBooks files, Spreadsheet Sync is the first thing to try, for companies on QuickBooks Online Advanced[1]. It combines only accounts that already match, so charts that differ still need a reviewed mapping.
| Unit and system | Source account label | Reporting account | Review note |
|---|---|---|---|
| Unit A, desktop ledger | 6120 Brand Fund Fee | Marketing and brand fund contributions | Accept: label and purpose match the reporting definition. |
| Unit B, cloud ledger | Adv. Contribution | Marketing and brand fund contributions | Agent flags: abbreviation. Approver confirms against the franchise agreement. |
| Unit C, spreadsheet | Misc - marketing | Needs review | Held: the account mixes brand fund fees with local advertising. Split by period or leave as a reconciling item. |
Rules that keep the mapping stable
- Map at the lowest level you can defend. Map to the reporting account, not to a subtotal, so a later change in the reporting chart is a one-row edit.
- Never merge on name alone. Similar names can hide different meanings, which is why the third row above is held, not guessed.
- Version the table. Record the effective date so a restated month can be re-run with the mapping that applied at the time.
- Keep unmapped accounts visible. An unmapped balance stays on its own line in the roll-up until someone assigns it.
How do multi-unit franchise groups run month-end close across dozens of entities?
With dozens of entities, the close is a coordination problem first. Units finish on different days, and the consolidation is only as final as its latest input. NetSuite's OneWorld documentation notes that default reporting periods may not correspond to fiscal periods used by all subsidiaries[5], so check each unit's calendar before you fix a cutoff. The sequence below is the method we recommend.
- Fix one cutoff and publish a close calendar
Name the date each unit's books must be final, who submits them and who chases a late unit. List the units that run on a different fiscal calendar.
- Collect each unit's export in a standard layout
Ask each unit for the same reports in the same format. An agent can read an export, a PDF or a spreadsheet and flag missing pages or periods.
- Apply the mapping and list exceptions
Apply the approved mapping table. New or changed accounts, unmapped balances and sign changes go to a review queue, not into the roll-up.
- Match and eliminate related-entity balances
Match what one entity records as owed to or by another, draft the elimination entries, and list differences for a person to resolve or carry.
- Review the consolidated package
Compare each unit's contribution with its prior month, review flagged variances, and approve any close adjustment. The finance lead releases the package.
Keep a one-page status board by unit: received, mapped, exceptions open, approved. It shows which unit is holding the close. For the wider workflow, see financial close automation.
What transfers from private-equity multi-entity consolidation?
Portfolio finance teams meet a similar problem when add-on acquisitions arrive on different ERPs. The pattern transfers to franchise groups with changes. Leave the ledgers where they are, build one reporting chart, add each entity as a mapping, and gate the output on human review. Our article on multi-ERP consolidation for private equity covers the keep-or-convert decision for entities on full ERPs.
- Scale of entities. Franchise units are many and small, so a mapping that is reusable across units matters more than a bespoke integration per unit.
- Quality of source books. A unit on a small-business ledger may have an informal chart, so the review column in the mapping table carries real weight.
- Who controls the ledger. In a roll-up you can set a required format. With independent franchisees, any data request depends on your agreements, which is a question for counsel.
For the wider franchise operations picture, including royalty reporting and unit-level workflows, see our franchise operations industry page. This article stays on the consolidated financial statements.
When this approach does not apply
- Every unit is already in one system. If your ERP or accounting platform consolidates those entities natively, use it. An agent adds little.
- A reporting layer is enough. If your units are on supported platforms, the charts are close, and management reporting is the goal, a BI layer alone may do the job. Test it on your two most different units first.
- Units are very few. A spreadsheet roll-up with a reviewed mapping can be the right tool.
- You need statutory or audited statements. Fathom's FAQ describes its output as management reporting rather than statutory reporting[2]. Confirm with your auditors what any tool's output can support.
- The books themselves are unreliable. Normalization cannot fix a unit whose books are months behind or whose transactions are miscoded. Fix the source first.
Frequently asked questions
How do I consolidate financials when my franchisees use different accounting software?
Keep each unit's ledger and consolidate on top of it. Define one reporting chart, map each unit's accounts to it, eliminate balances between related entities, and roll the mapped results into one P&L and balance sheet. Your finance staff approve the mapping table and every adjustment before the package is released.
Can I get one P&L view across all locations without migrating everyone to the same system?
Yes, if the account mapping is done explicitly. A consolidated P&L is a sum of mapped accounts, so each unit can stay on its current software as long as every account has an approved reporting line. Related-entity balances are removed, and a person reviews the result before release.
What's the easiest way to combine QuickBooks files from multiple franchise locations?
Start with the tools you already have. Intuit documents Spreadsheet Sync for combining reports across QuickBooks Online Advanced company files, merging accounts only when names, types and levels match. If charts differ, add a reviewed mapping table first, kept in a spreadsheet, a reporting tool or an agent.
How do multi-unit franchise groups handle month-end close across dozens of entities?
They fix one cutoff and publish a close calendar, collect each unit's exports in a standard layout, apply the mapping, eliminate related-entity balances, and review the package. A status board by unit shows which entity is holding the close. The finance lead approves adjustments and releases the final package.
Is there a way to automate consolidated reporting without a full ERP implementation?
Yes. A reporting layer can aggregate units on supported platforms, and an agent can read exports, propose account mappings, draft eliminations and assemble the roll-up while the ledgers stay in place. Neither replaces a system of record, and a person on your finance staff approves the mapping and adjustments.
Related reading
- Financial close automation covers the close workflow this article applies to franchise units.
- Financial reconciliation automation covers the account matching behind related-entity eliminations.
- AI agent implementation covers building an agent with review controls and a named approver.
- Multi-ERP consolidation automation for private equity covers the pattern this article adapts.
- AI agents for franchise operations covers the wider franchise workflow picture.
Sources
- Intuit QuickBooks, "Combine reports from multiple companies using Spreadsheet Sync" (accessed 2026-10-29)
- Fathom, "Financial Consolidation software" (FAQ) (accessed 2026-10-29)
- Docyt, "Franchise reporting" (accessed 2026-10-29)
- Sage Intacct, "Consolidation Elimination Accounts" (accessed 2026-10-29)
- Oracle NetSuite, "OneWorld Financial Statements" (accessed 2026-10-29)
More in Finance operations
Deal Jacket and Title/Registration Automation for Multi-Rooftop Dealer Groups
Deal jacket and title/registration automation for multi-rooftop dealer groups: a completeness checklist table, audit-gap handling and cross-store standards.
Auto DealershipsFranchise Brand-Standards Audit Documentation: Automating the Paper Trail Behind the Inspection
Franchise brand-standards audit documentation: how an agent turns photos, PDFs, forms and emailed fixes into one packet per location, ready when asked.
Multi-Unit Franchise OperatorsGroup and Folio Billing Audit: Catching the Leak Types a Normal Error Check Misses
A group and folio billing audit for hotel management companies: a leak-type table of rate code mismatches, missing closes, adjustments, orphaned charges.
Hotel Management Companies