Home › Guides

How to preserve local statutory accounts inside group reporting

Keep an identifiable local reporting result even when the group uses one chart of accounts and one close calendar. The subsidiary must still be able to explain its accounts, supporting records and filings independently of the group's latest dashboard.

This guide pilots an established UK private limited subsidiary. It shows how to preserve local numbers, map them into a group package, detect a balanced but incomplete import and assign the final filing work. The method can be adapted elsewhere after checking that jurisdiction's requirements.

Use the statutory-to-group mapping and filing worksheet. The worked example is synthetic, and its journal and mapping controls are recommendations rather than additional legal requirements.

Define which output is being prepared

Statutory accounts are the entity's annual financial reporting package. They include statements and supporting disclosures. They are different from a tax computation, a Company Tax Return, a group consolidation package and a transaction-level audit extract.

UK government guidance describes statutory accounts prepared from financial records, their recipients and their components, including a balance sheet, profit and loss account and notes. Director and audit-report requirements depend on the applicable circumstances; do not assume an exemption merely because the subsidiary is operationally small. GOV.UK, preparing annual accounts.

For this pilot, assume the accounting adviser has determined that FRS 102 is the appropriate local basis. The FRC describes FRS 102 as applying to entities not using adopted IFRS, FRS 101 or FRS 105, and identifies the principal 1 January 2026 effective date of its Periodic Review 2024 amendments. Identify the actual applicable edition before accounts preparation begins. FRC, FRS 102 and current amendments.

The group package serves the parent's reporting. Consolidated accounts combine the appropriate entities with accounting adjustments, translation and eliminations. A mapped subsidiary trial balance is one input to that process, not the complete consolidated statements or a replacement for the subsidiary's own accounts.

Similarly, an audit file supplies specified records for a particular request or reporting obligation. Its format and legal trigger require separate verification. Do not treat a UK statutory-accounts process as requiring a French FEC or another country's audit export.

Establish the local close and mapping boundary

Choose a local close snapshot and preserve its entity, period, currency, accounting basis and revision. Give later journals an explicit route into a revised snapshot. Avoid exporting a moving ledger while the accounts preparer and group team work from different versions.

Separate account mapping from accounting adjustments. Mapping determines where an existing balance is presented. An adjustment changes recognition, measurement or another accounting result. Group eliminations remove applicable intra-group amounts at consolidation; they do not generally justify deleting a subsidiary's genuine receivable or revenue from its own books.

Business Central's consolidation documentation permits different business-unit and consolidation-company charts and describes account mappings, business units and translation methods. That establishes a documented Dynamics 365 Business Central mechanism, not production evidence for a particular tenant or an automatic UK statutory-accounts filing service. Microsoft, Business Central consolidation setup.

In the mapping record, identify the source account, reporting destination, sign, currency treatment, effective period and approving owner. Include accounts with zero closing balances but movements relevant to the year's disclosures. Version the mapping used for the final package.

Work a complete local-to-group example

Assume the subsidiary has a full calendar financial year ending 31 December 2026. All amounts below are GBP thousands. There are no currency differences, dividends, basis adjustments or consolidation eliminations in this exercise. Its ordinary local accounting records are already reviewed and closed.

Closing assets are cash of 25, receivables of 40 and equipment costing 60 with accumulated depreciation of 12. Net equipment is 48, so total assets are 113.

Liabilities are trade payables of 18 and a current-tax provision of 5, totalling 23. Share capital is 20, opening retained earnings are 50 and current-year profit is 20. Equity therefore totals 90, and liabilities plus equity equal assets: 23 plus 90 equals 113.

Revenue is 150. Staff costs are 90, rent is 12, depreciation is 12 and other operating expenses are 11. Pretax profit is 25. The tax charge is the assumed accountant-approved provision of 5, leaving profit after tax of 20. The 5 is a synthetic provision, not an asserted UK tax rate or a tax computation.

Map cash and receivables to separate group asset lines. Map equipment cost and accumulated depreciation to their respective group accounts so both gross and net values remain visible. Map payables and tax liability separately, and retain distinct capital, opening reserves and current-profit movements.

For the income statement, the group wants rent included in its "premises and administration" category with other operating expenses. That category becomes 12 plus 11, or 23. Group reporting still shows revenue of 150, staff costs of 90, depreciation of 12 and premises/administration of 23. Pretax profit remains 25, tax remains 5 and profit remains 20.

This is a presentation bridge with no accounting difference. The local rent account stays available for local statements and notes. Do not create a second GAAP book simply to combine those expense lines.

Reconcile population and value before accepting the package

Account for every relevant source account before checking the grand totals. Record mapped, deliberately excluded and unresolved accounts separately. For an ordinary full trial-balance import, any non-zero unresolved balance needs investigation even if the imported totals balance.

The example's correct mapped result has assets of 113, liabilities of 23 and equity of 90. Its operating expenses before tax total 125, producing pretax profit of 25. Keep those controls alongside the account-level bridge and the retained-earnings movement.

Next, trace selected disclosures to their underlying records. Equipment notes need more than the closing net balance; staff, related-party, commitment and other disclosures may need data outside the mapped trial balance. Assign a preparer and reviewer to each required schedule rather than assuming the reporting tool can infer the missing information.

Compare the group's accepted package with the local snapshot. Where actual basis differences exist, add an approved adjustment bridge of the kind described in parallel books for local and group reporting. Keep the mapping bridge and accounting bridge separate so reviewers can identify which changed the result.

Recover from a balanced but incomplete import

Suppose the mapping accidentally omits both depreciation expense of 12 and accumulated depreciation of 12. The imported package still balances because a debit and a credit of equal size were dropped.

It now shows equipment of 60 instead of 48 and assets of 125 instead of 113. Profit becomes 32 instead of 20. Equity becomes 102, and liabilities plus equity still equal assets: 23 plus 102 equals 125. A "debits equal credits" check therefore passes a package that overstates both assets and profit by 12.

The reporting operator stops release when account coverage or the 113 asset control fails. The mapping owner identifies the two missing accounts and corrects the mapping revision. Replace the failed import through the system's controlled rerun process; do not add a plug to retained earnings.

The group reviewer then checks equipment at 48, profit at 20, assets at 113 and the account-level coverage report. The local controller confirms that the underlying statutory snapshot has not been altered to repair a group presentation error.

Prepare the UK filing calendar and delivery routes

Keep separate tasks for accounts approval, Companies House delivery, Corporation Tax payment and the Company Tax Return. For an established private company under the ordinary rules, GOV.UK gives nine months for annual accounts, nine months and one day for Corporation Tax payment and twelve months for the tax return. First accounts and other circumstances have different rules. GOV.UK, accounts and tax-return deadlines.

Assume the example qualifies for those ordinary deadlines, with its tax accounting period also ending 31 December 2026, no extension, no shortened period and no instalment-payment requirement. The illustrative dates are 30 September 2027 for Companies House accounts, 1 October 2027 for tax payment and 31 December 2027 for the Company Tax Return. Calculate the company's actual calendar from its circumstances rather than copying these dates.

The joint online accounts and Company Tax Return service closed on 31 March 2026. HMRC's updated guidance directs users to commercial software for their HMRC filing and distinguishes other Companies House routes. A former joint-service workflow must therefore be replaced explicitly. HMRC, filing after the joint service closed.

Companies House's current guidance states that mandatory commercial-software accounts filing starts on 1 April 2028. That is a separate future change from the already completed HMRC service closure. Check the permitted route and accounts type for the actual submission date, including any applicable specialised filing arrangements. Companies House, software filing requirements.

Treat iXBRL as a separate delivery and review step

Inline XBRL embeds machine-readable tags within a human-readable report. It is a reporting format, not an accounting framework or another ledger. HMRC explains the use of iXBRL accounts and computations in Company Tax Returns and the role of accounts-production, tax and conversion software. HMRC, Businesses XBRL guide, updated April 2026.

The accounts preparer should reconcile the final human-readable document and tagged values to the approved local result. Check entity identity, period, currency, units, comparative values and signs. In this example, reporting 113 as pounds instead of GBP thousands would create a substantial error even if the file passed a structural check.

Keep the tax computation separate from accounting profit. Its adjustments must be supported and reconciled before the tax preparer completes the return. Acceptance of a Companies House submission does not establish that the HMRC return, tax payment or parent package is complete.

Close the reporting assignment with named owners

The local controller owns the statutory result and supporting schedules. The group controller owns package mapping and consolidation adjustments. The accounts preparer assembles statements and disclosures; directors carry out the relevant approval responsibilities. The tax preparer owns the computation and return process, and a named filer monitors each recipient's acknowledgement.

Before completion, confirm:

• The correct entity, reporting period, basis and applicable standard edition are recorded.
• Every relevant account and movement is mapped or deliberately accounted for.
• Local statements, group package and supporting schedules reconcile.
• Mapping changes and accounting adjustments remain distinguishable.
• The balanced-but-incomplete failure test is detected.
• Filing dates and routes reflect the company's circumstances and submission date.
• Tagged and human-readable values agree with approved accounts.
• Companies House, HMRC, payment and group-delivery tasks have separate completion evidence.

Retain the source snapshot, mapping revision, reconciliations, approved accounts, tax package and acknowledgements. Use mapping reporting obligations for the wider register and preserving tax-reporting history when changing systems.

Source verification date: 17 October 2026. This pilot does not assume small-company filing relief, audit exemption or a parent's consolidation exemption; the applicable decisions remain part of the company's documented accounts preparation.

Worksheet: Statutory-to-group mapping and filing worksheet

Copy this worksheet for each case. It records decisions and evidence; it does not determine the tax or legal treatment.

Related on this site

• Country pages: key facts with sources
• E-invoicing matrix: country × ERP support
• All guides

Vendor documentation is cited only as an example of the level of evidence to ask for; it is not a recommendation or a ranking. This guide is general information, not tax or legal advice. Checked 2026-10-17.

Related: Glossary – abbreviations and terms used in these guides (SAF-T, Peppol, CTC, EN 16931, IFRS and more).

Page last updated: 2026-10-17 · Markdown version