Multi-Facility Consolidation for Growing Manufacturers

What Changes When the Second Plant Opens

Five things that stop working the way they used to.

1. Intercompany transfers become their own accounting stream

The moment plant A ships work-in-process to plant B for a finishing operation, you have intercompany accounting. Every transfer needs a document trail, a valuation method, and a cutoff. Without it, the same inventory shows up as WIP at plant A and as raw material at plant B, and your consolidated balance sheet is double-counting until someone reconciles.

The mechanics that need to exist: an intercompany transfer document (physical or system), a transfer price that's applied consistently, an intercompany AR/AP posting at both entities, and a period-end elimination entry that removes the intercompany transaction from the consolidated view. QuickBooks Enterprise can do some of this with class tracking and a lot of manual JE discipline. Sage 300cloud, NetSuite, and Acumatica handle it natively.

2. Transfer pricing becomes a real question, not a theoretical one

How do you price intercompany transfers? The three common approaches, each with its tradeoff:

• At standard cost. Simplest. Doesn't reveal the true economics of either plant — the sending plant shows no margin on the transfer, the receiving plant gets the full margin on the finished sale. Fine for a wholly-owned single-entity view; misleading if plants are separately managed or have separate P&L accountability.
• Standard cost plus a markup. Attempts to allocate margin between plants. Better for management reporting. Requires everyone to accept the markup rate as reasonable, which becomes political when a plant manager's bonus depends on it.
• Market-comparable pricing. Priced as if the transfer were an arm's-length sale to a third party. Most accurate for management insight; most work to maintain. Required if either entity is in a jurisdiction with transfer-pricing tax exposure (Canada, Mexico, EU) or if the entities have different ownership.

The right answer depends on what you need the numbers for. If it's a single-owner group and you're just consolidating for the bank, standard cost is fine. If plant managers have P&L accountability, markup. If you have any international entity involvement, market-comparable and get a transfer-pricing study done.

3. Shared services need an allocation method — and someone has to defend it

Corporate finance, HR, IT, marketing, and executive salaries have to be allocated across plants somehow. The four most common bases:

• Revenue. Simple, defensible in most situations, but overweights plants with high-revenue low-margin work.
• Headcount. Fair when the service supported (HR, IT) is truly headcount-driven.
• Direct labor hours. Reasonable when overhead is labor-intensive.
• Contribution margin. Best for allocating corporate profit-generating services (like marketing) but complicates the accounting.

The mistake we see most often: no allocation, so all corporate cost sits at HQ and every plant looks profitable. Then a plant manager makes an operating decision based on that unallocated P&L and the business as a whole loses money. Allocation isn't optional at two-plus locations — it just has to be defensible and consistent.

4. The consolidation itself takes real time now

Single-entity closes typically wrap in 5–10 business days. Two-entity closes with intercompany, transfer pricing, and shared services allocation typically wrap in 10–15. Three-entity closes push toward 20 unless the process is automated. If your Controller is doing consolidation manually in Excel — pulling trial balances, keying intercompany eliminations by hand, allocating shared services with a spreadsheet — the close will keep slipping as the business grows.

The tools that solve this scale up in cost. Sage Intacct, NetSuite, and Acumatica handle intercompany and multi-entity consolidation natively. QuickBooks Enterprise + Excel works up to about $30–40M with one added entity; past that, it's the biggest single time sink in the finance function.

5. Bank and covenant reporting fragments

Most banks want a consolidated financial package, but many also want entity-level detail — especially if different entities are collateral for different facilities. Covenant calculations (fixed charge coverage, funded debt to EBITDA, current ratio) sometimes apply at the consolidated level and sometimes at the entity level, depending on how the credit agreement was written.

The finance function needs to be able to produce both views without manual reconstruction each quarter. When you can't, the bank meeting turns into a scramble and covenant certifications get filed late.