Multi-Company Financial Consolidation: From Chart of Accounts to Management Report

Finance teams of groups with multiple companies always ask the same question at month-end: "What is the situation across the group as a whole?" Each company has its own accounting software, its own chart of accounts, and sometimes its own currency. Consolidation is the task of transforming this fragmented picture into a single comparable and reliable view. In this article, we explain the technical steps of consolidation for management reporting purposes; the preparation of statutory (official) consolidated financial statements is the responsibility of the accountant and auditor.

1. Common chart of accounts: mapping table

The foundation of consolidation is mapping each company's chart of accounts to a common structure at the group level. Although the Uniform Chart of Accounts is widespread in Turkey, sub-account breakdowns vary from company to company, and companies in Northern Cyprus may use different structures. Therefore, the "source account → group account" mapping table must be manageable data within the software and should not be hardcoded.

-- Example: group chart of accounts mapping (simplified)
create table account_mapping (
  company_id   uuid not null,
  source_code  text not null,   -- company's own account code
  group_code   text not null,   -- group account code
  valid_from   date not null,
  valid_to     date,
  primary key (company_id, source_code, valid_from)
);

It is important for the mapping to carry a date range: historical period reports should not be broken when the chart of accounts changes.

2. Currency conversion: which rate, which date?

When consolidating companies operating in different currencies, there are three exchange rate approaches: period-end rate (for balance sheet items), period-average rate (for income statement items), and transaction-date rate (for specific items). The most important point in management reporting is consistency: make the rule you use for which item visible on the report and record the exchange rate source (e.g., central bank daily rate) in the system.

3. Elimination of intercompany transactions

If companies within the group sell to each other, these amounts are counted twice in consolidated turnover. For elimination, intercompany current accounts must be matched on both sides. Practical method: each company marks the counterpart within the group as a "group company" in its current account card; the consolidation engine automatically matches these marked transactions and displays unmatched ones in a warning list.

An unmatched intercompany balance is the most valuable output of consolidation: either a record is missing or one party's record is wrong. Make these differences visible instead of rounding them away silently.

4. Data transfer and validation rules

Trial balances or transaction exports (Excel, CSV, or API) obtained from accounting software must not enter consolidation without passing through validation rules. Minimum controls we recommend:

• Equality of total debits and credits (trial balance equilibrium).
• Rejection of account codes that do not have a counterpart in the mapping table.
• Period lock: tying the reloading of data into a closed period to authorization.
• Recording who made each upload, when, and with which file.

5. Management screen: which indicators?

Once the consolidated data is ready, the management screen should be simple. An example executive view might include: income-expense, cash and bank balances on a company-by-company and total basis, receivables and payables nearing maturity, planned versus actual budget variances, and period-over-period comparisons. Being able to click on any figure to drill down to source transactions increases the reliability of the report.

6. Authorization: not everyone should see every company

The consolidated view is for group management; company managers should mostly see only their own companies. Implementing this distinction at the database level (such as PostgreSQL Row Level Security) ensures that the rule remains valid even if the reporting tool changes.

Where to start?

Our recommendation is to build consolidation gradually rather than as an "all-encompassing" project in one go: first, trial-balance-based monthly summary, then cash flow and budget comparison, and lastly intercompany elimination. Comparing the results with the finance team's existing Excel work at each stage increases both confidence and data quality.

Period-end closing workflow: an example calendar

The workflow below is a fictional example; it varies depending on the size of the group. The important thing is that each step has a responsible person and a control point.

1. First business days of the month: Each company exports the trial balance from the accounting software and uploads it to the system. Trial balance equilibrium is automatically checked.
2. Mapping control: New account codes without mapping are listed; the finance team completes the mapping.
3. Rate application: Conversion is made with the defined exchange rate policy; used rates appear in the report appendix.
4. Intragroup matching: Unmatched balances drop as warnings to the relevant companies.
5. Locking: Once controls are completed, the period is locked; subsequent changes require justification and authorization.
6. Management report: The consolidated screen is updated; executives can drill down to source transactions.

Cash flow: as important as the balance sheet

A group that appears profitable can fall into difficulty due to cash crunches. The consolidated cash flow view brings together bank and cash balances on a company basis, receivables and payables nearing maturity, and planned payments. The most valuable feature here is the "warning": if planned payments within a specific date range exceed expected collections, management should see this without waiting for a report. The warning thresholds are set by the finance team, not the system, and changed when necessary.

Budget: planned versus actual

Budget consolidation must be done with the same chart of accounts and the same cost centers as the actual consolidation; otherwise, the comparison will be between apples and oranges. The variance report should include not only the amount but also the percentage and an explanation field; the responsibility for explaining the variance belongs to the relevant company, and the system can assign this as a task.

Common pitfalls

• Manually corrected Excel: Manual corrections made in the file before uploading leave no trace. Corrections must be made in the system and with justification.
• Showing exchange rate differences in the wrong place: Conversion differences should appear on a separate line and not interfere with operating results.
• Applying chart of accounts changes retroactively: Historical reports change silently without date-ranged mapping.
• Dependency on a single person: If only one person knows the consolidation, the process is undocumented.

AI-assisted summarization: careful use

Once the consolidated report is ready, summarizing period-over-period changes in natural language can save executives time. However, these summaries must be linked to source figures and marked as a "model interpretation"; financial decisions are made from source data, not the summary. This approach is the financial equivalent of the validation and human approval principle we apply in our AI and automation service.

Cy Logic's finance and accounting systems service follows precisely this gradual path; building a management layer on top of your existing accounting software without changing it is the most realistic starting point for most groups.