Three Entities, One Job: Why Construction CFOs Outgrow QuickBooks Enterprise
Four entities. One project. The general contractor holds the job. A related equipment company owns the loader. A self-perform concrete company uses it on site.
Now the CFO has a simple question: What did this project cost the group?
In QuickBooks Enterprise, those companies may sit in separate company files. Equipment charges move between entities, while project costs need to stay tied to the job. Across dozens of projects, month-end can become a reconciliation exercise before the CFO sees the full job cost.
QuickBooks Enterprise can combine certain reports across company files. But Intuit’s documentation limits that feature to standard statements and trial balance reports, with matching account names and Excel as the output. Job cost reports aren’t included in Enterprise’s built-in Combine Reports feature.
That’s the real issue. Multi-entity job costing isn’t a month-end consolidation task. The cost needs to stay connected to the job as transactions move across entities.
In short
Multi-entity job costing tracks project costs across several legal entities with shared cost codes and automated intercompany entries. QuickBooks Enterprise keeps each entity in a separate file and combines only summary financial reports, so group-level job costs are usually rebuilt in spreadsheets.
Why Contractors Run Multiple Entities
Few mid-size contractors operate as a single company for long. Common reasons include:
- Liability separation: keeping risky work or regions in their own entity.
- Equipment companies: owning fleets separately and renting internally.
- Self-perform or specialty subsidiaries: concrete, electrical, or site work under their own license.
- Real estate and development: holding property apart from operations.
Each reason makes sense. Together, they turn one project into several sets of books.
Where QuickBooks Enterprise Runs Out
QuickBooks Enterprise can handle accounting within each company. The challenge comes when you need to connect those companies around the same construction project:
- Separate company files: each entity maintains its own company file, with its own jobs and cost codes.
- Limited combined reporting: selected financial reports can be combined across company files, subject to matching account structures and Excel output.
- Intercompany transactions: Platinum and Diamond support intercompany transactions between related company files, but each entity still maintains its own company records.
- No unified cross-entity job view: the key question is not simply whether transactions can move between companies. It is whether the CFO can see the true cost and profitability of a project across the group.
One Loader, Three Sets of Books
Here’s how a single internal rental plays out when each entity keeps its own books (figures are illustrative):
Each company’s books can be correct, but the group-level job view can still be distorted. The equipment company records rental revenue, while the concrete company records the rental as a project cost. Without a clear intercompany trail and elimination process, those internal charges can inflate the group’s apparent job cost and distort project profitability.
What Multi-Entity Job Costing Actually Requires
Before evaluating any system, construction CFOs should check for these five capabilities:
| What you need | Why it matters to a construction CFO |
|---|---|
| Intercompany that posts once | An equipment rental or labor charge between entities is entered one time and balances both sets of books. |
| One cost code structure across entities | A concrete cost code means the same thing in every company, so job costs roll up cleanly. |
| A group-level view of each job | You can see what a project costs the whole group, not just the entity that holds the contract. |
| Committed costs and WIP by entity | Subcontracts, POs, and WIP are tracked where they belong, ready for lenders and sureties. |
| Consolidation with traceable intercompany | Every intercompany entry is tagged to a partner, so eliminations are easy to find and review. |
Modern ERP platforms handle much of the accounting side. In Microsoft Dynamics 365 Business Central, for example, intercompany partners enter information once, and “a corresponding document is created at the other partner.” Microsoft is also candid that consolidation eliminations remain a manual step, which is why tagging every intercompany entry matters.
The Netsmartz View: Design Entities Around the Job
Most multi-entity pain comes from setting up entities for legal reasons and hoping job costing follows. Flip it:
Where ProjectPro Comes In
ProjectPro is Netsmartz’s all-in-one, AI-powered construction ERP built on Microsoft Dynamics 365 Business Central. It brings construction job costing and financial management into one platform, with Microsoft 365 Copilot as the intelligence layer.
For multi-entity contractors, ProjectPro brings these requirements into one construction ERP environment. It combines construction job costing by project, phase, and cost code with intercompany accounting, labor and equipment resource management, subcontracts, retention, progress billing, and WIP.
Each company can maintain its own books while finance and project teams work from connected project and financial data across the group. That gives CFOs a clearer view of what each entity owns, what it owes, and what each project actually costs across the organization
The Bottom Line
QuickBooks Enterprise can tell you how each company did. A growing contractor also needs to know how each job did across all of them. When that answer lives in a spreadsheet, the structure has outgrown the software.
See how multi-entity job costing works in ProjectPro. Take the product tour.
Frequently asked questions
Multi-entity job costing tracks construction project costs across two or more legal entities, such as a general contractor, self-perform subsidiary, and equipment company. A shared cost code structure helps finance teams see project costs and profitability across each entity and the group.
QuickBooks Enterprise can combine selected financial reports from multiple company files into Excel, including balance sheet, profit and loss, cash flow, and trial balance reports. The company files must use matching account names, types, and levels. Its built-in Combine Reports feature does not include job-cost reports or provide a project-level view of costs across entities.
In Microsoft Dynamics 365 Business Central, you can assign intercompany partners to customers and vendors. When one company sends an intercompany transaction, the corresponding document can be created in the partner company, reducing duplicate entry across entities.
The terms are often used interchangeably. Multi-company construction accounting generally refers to managing multiple companies or sets of books within an accounting system. Multi-entity job costing goes further by connecting project costs, commitments, and WIP across those companies, so finance teams can see each job’s cost across the group.
A common trigger is when multiple entities share jobs, equipment, or labor and group-level job costs, intercompany balances, or WIP have to be rebuilt in spreadsheets each month. That is a sign to evaluate whether the accounting system can support the way the business operates.
ProjectPro brings construction job costing, intercompany accounting, commitments, WIP, and project financials into the same ERP environment. Built on Microsoft Dynamics 365 Business Central, it helps construction companies track costs by project, phase, and cost code while maintaining separate company books.
