One group, one view — multi-company accounting and reporting in Sage X3

A group may trade through several legal entities while its management team still needs one answer to a straightforward question: how is the whole organisation performing?

That answer is surprisingly difficult when each company runs a separate accounting system. Finance teams export trial balances, translate account codes, convert currencies, identify intercompany balances and assemble a management pack in Excel. By the time it is complete, the information is already out of date and much of the month-end effort has gone into moving numbers rather than understanding them.

Sage X3 is designed to hold multiple companies, sites, currencies, ledgers and legislations within the same system. Each legal entity keeps its own accounts and controls, but the group can share a reporting structure and produce a combined view from governed data.

Separate companies do not need separate information silos

Multi-company accounting does not mean putting every entity into one ledger. Each company still needs its own opening and closing periods, journals, tax rules, currency and statutory records.

The benefit of Sage X3 is that those separate companies can operate within a common finance model. Depending on the group, they may share:

• a chart of accounts and consolidation account structure
• analytical dimensions such as department, product, region or channel
• financial calendars and reporting periods
• customer, supplier and product data where appropriate
• consistent journal types, reporting rules and approval controls
• a group reporting currency and agreed exchange-rate policy

This consistency matters more than the final report layout. If one company records freight as a cost of sale, another treats it as an overhead and a third hides it within a local account, adding the three trial balances together will not produce a meaningful group figure.

The reporting model therefore needs to be designed before the report. Local differences can remain where legislation or operations require them, but every material account and dimension should have a defined route into the group view.

Intercompany journals without entering both sides twice

Shared costs are a common source of month-end work. A parent company may pay insurance, software, rent or professional fees on behalf of several subsidiaries. Finance then has to allocate the expense and create matching due-to and due-from balances.

Sage X3’s intercompany journal process allows the user to enter the transaction across the source and target companies. When it is posted, the system creates separate balanced journals in the relevant company ledgers using the accounts defined in the intercompany account mapping.

For example, Company A pays a £10,000 software bill and allocates £3,000 to Company B. The result can be:

The two legal ledgers remain separate, but the reciprocal balances come from the same controlled transaction. Sage X3 checks that the intercompany entry balances and uses the configured debit and credit accounts for the source and target companies.

This reduces duplicate keying and makes the relationship between both sides visible. It also removes a familiar month-end problem: one entity posting its half of a recharge while the other records a different value, period or account.

Intercompany journals are not the answer to every group transaction. Where one entity genuinely supplies goods or services to another, customer and supplier intercompany invoices may be the correct process. The design should reflect the commercial event, VAT treatment and accounting policy rather than routing everything through a journal for convenience.

From individual ledgers to one management report

Once the company structures are aligned, Sage X3 can extract accounting, analytical and budget data into a common management-reporting format. The report can show the group total alongside individual entities, periods, budgets and variances.

A useful monthly pack might include:

• a consolidated profit and loss account for the group
• an entity-by-entity comparison with a group total
• actual versus budget and prior year
• revenue and margin by product, region or channel
• operating costs by department
• group cash, receivables and payables
• intercompany balances and unmatched differences

The important change is that the report logic becomes repeatable. Account mappings, company scope, dimensions, currency treatment and calculation rules are defined once and applied consistently each period. Users can retain detail for analysis and trace a group figure back through the entity, account, site or dimension to the underlying entries.

Sage X3’s financial data extraction supports formula-driven reports using general, dimensional and budgetary accounting data. It can also calculate report groups and express amounts in a selected print currency. Cross-company inquiries depend on compatible structures, so shared charts of accounts, ledger currencies and period definitions need to be designed carefully.

Aggregation is not the same as consolidation

Adding the results of several companies produces an aggregated management view. A true consolidated result may also require:

• eliminating intercompany income, costs, receivables and payables
• translating companies with different base currencies
• recording exchange and cumulative translation adjustments
• aligning different local charts or accounting policies
• handling minority interests and changes in ownership
• posting group-only adjustments that do not belong in a local statutory ledger

This distinction is important. If Company A records £500,000 of sales to Company B, the amount is valid in both individual companies but it is not external group revenue. A group report that simply adds the companies together will overstate both revenue and costs unless the reciprocal entries are identified and eliminated.

Sage X3 can identify intra-group operations using partner and flow information and aggregate postings within a defined consolidation scope. The required process will depend on the complexity of the group and whether the output is an internal management pack, a statutory consolidation or data being passed to a specialist consolidation application.

The accounting policy should decide the treatment. The software should apply it consistently and preserve the audit trail.

What a good implementation needs

Installing Sage X3 will not repair an inconsistent group reporting model on its own. Before building the reports, agree:

1. The company and site structure. Define each legal entity, operational site and reporting group clearly.
2. The common reporting model. Map local accounts to group accounts and standardise the dimensions used for management analysis.
3. Intercompany relationships. Configure the permitted company pairs, due-to and due-from accounts, invoice flows and journal rules.
4. Currency rules. Decide which rates apply to profit and loss, balance-sheet and budget figures, and how translation differences will be reported.
5. Eliminations and adjustments. Define what is removed from the group result, who owns the process and where group-only postings are recorded.
6. The close timetable. Align periods, cut-off rules, approvals and the point at which each entity is ready for group reporting.
7. Reconciliation and access. Make it possible to trace every group number to its source while ensuring users only see the companies and detail they are authorised to access.

Test the model with real complications: an allocation across three entities, a late posting, a credit note in the following period, different base currencies, an unmatched intercompany balance and a new company joining the group. A report that works only when every transaction is perfect will not survive month end.

A faster close is useful; a trusted view is better

The immediate benefit of multi-company accounting in Sage X3 is less spreadsheet handling, less duplicate entry and a shorter route from entity close to group reporting.

The larger benefit is confidence. Management sees one version of the group’s performance, prepared using consistent definitions and supported by an audit trail back to each company. Finance can spend less time explaining why spreadsheets disagree and more time explaining what the results mean.

That is the real value of bringing separate companies into one Sage X3 reporting model: the legal entities remain distinct, but the organisation no longer has to manage them as separate islands of information.

For more detail on the underlying functionality, see Sage’s documentation for intercompany journal entries, financial data extraction and consolidation extraction.