The thesis: statutory filing is becoming an ERP workflow.
The important shift is operational. Software-only filing turns the annual accounts process into a designed workflow: closed ledgers, statutory adjustments, report assembly, taxonomy mapping, validation, director approval, agent collaboration, submission, acceptance, and corrections.
Companies House announced on 9 June 2026 that the accounts reforms will come into effect from April 2028, giving companies 21 months to prepare. The same announcement says the package includes all companies filing annual accounts via commercial software, small and micro-entity profit and loss filing, removal of abridged accounts, and a strengthened audit exemption statement.
That timeline is generous enough to build well. Finance teams can use the next reporting cycles to remove spreadsheet-only report assembly, align chart-of-accounts rollups to statutory lines, test iXBRL validation, and make the filed account package reproducible from controlled ERP evidence.
What changed, exactly.
The official Companies House guidance says that from 1 April 2028, all companies must file annual accounts using commercial software. The accounts must be in Inline XBRL, and the web and paper routes for accounts filings will close from that date. Web services remain available for other statutory filings.
The UK company law campaign page adds the practical shape of the reform: all accounts filings made on or after 1 April 2028 must be filed by commercial software in iXBRL format. Small and micro-entity companies will need to file a profit and loss account as part of their annual accounts, with details of the public-register opt-out still to be confirmed.
This also expands the reporting evidence surface. FRC guidance explains that XBRL tags are drawn from FRC taxonomies aligned to UK GAAP, IFRS, and other reporting rules. Its 2026 taxonomy guidance encourages filers to use the most up-to-date taxonomy where possible and emphasizes full tagging for HMRC requirements.
The opportunity is a cleaner reporting operating model.
The best finance teams will treat the change as a chance to reduce manual filing risk. Today, many close processes produce management accounts quickly, then rely on a separate statutory spreadsheet, an accountant handoff, or a final filing tool to create the Companies House artifact. The 2028 transition rewards a tighter pattern: one approved reporting package that is both human-readable and machine-readable.
The ERP does not need to become a full statutory filing product for every company. But it should own the source-of-truth workflow: entity profile, ledger close, statutory adjustments, report line mapping, approval state, taxonomy evidence, document versions, and final acceptance. Filing software and external accountants can then operate on a controlled package instead of rebuilding the numbers.
Control design for software-ready accounts filing.
| Workflow stage | Control pattern | Evidence to retain |
|---|---|---|
| Entity and filing scope | Confirm entity size, filing type, audit status, Companies House requirements, HMRC relationship, and whether an agent will file. | Entity filing profile, accounting reference period, size assessment, audit exemption basis, agent authorization. |
| Close and statutory adjustments | Lock the management close, then route statutory adjustments through controlled journals with source-document links and reviewer sign-off. | Closed period, statutory JE pack, preparer and reviewer trail, variance commentary, board-ready numbers. |
| Statement assembly | Generate the balance sheet, profit and loss account, notes, directors report where applicable, and package-account components from approved data. | Statement version, component inventory, director signatory fields, package checklist, source mapping. |
| Taxonomy mapping | Map each report line and disclosure to the correct FRC taxonomy concept, context, unit, sign, period, and dimension before filing season. | Mapping table, taxonomy version, extension rationale, prior-year comparison, mapping owner. |
| Validation and viewer review | Run technical validation and human-readable viewer checks before director approval, agent handoff, or submission. | Validation output, viewer screenshots or export, resolved exceptions, open items, final approval. |
| Submission and acceptance | Store the exact submitted iXBRL package, presenter details, timestamp, acknowledgement, rejection, and correction lifecycle. | Submitted package hash, presenter ID reference, Companies House response, correction record, final accepted version. |
| Disclosure privacy choice | When small or micro-entity publication opt-out rules are confirmed, treat the choice as a controlled disclosure decision. | Eligibility basis, director decision, filed P&L access setting, reviewer evidence, retained internal copy. |
This is a cross-functional control. The controller owns close readiness and statutory reporting integrity. The CFO owns disclosure posture and board confidence. The external accountant or agent may own the filing action. IT owns integrations, permissions, and retention. The ERP should make those roles visible in one workflow instead of spreading them across email, document storage, and filing portals.
The data contract matters more than the filing button.
A robust filing workflow needs a statutory report package object. That object links the closed period, company number, entity profile, report components, taxonomy version, report-line mappings, approvals, iXBRL package hash, and Companies House response. Without that object, the finance team can file successfully and still struggle to prove exactly what was filed and why.
Example statutory report package record
{
"statutory_report_package_id": "srp_uk_2028_000184",
"company_number": "12345678",
"entity_id": "uk_trading_ltd",
"accounting_period": {
"start": "2027-01-01",
"end": "2027-12-31"
},
"close_lock_id": "close_2027_12_final",
"filing_basis": "FRS_102_SMALL_COMPANY",
"taxonomy": {
"publisher": "FRC",
"suite": "2028",
"entry_point": "uk-gaap"
},
"components": [
"balance_sheet",
"profit_and_loss",
"notes_to_accounts",
"audit_exemption_statement"
],
"report_line_mappings": [
{
"line_id": "p_and_l_revenue",
"coa_rollup_id": "rev_total",
"taxonomy_concept": "Revenue",
"period_context": "current_year",
"sign_policy": "credit_positive",
"review_status": "approved"
}
],
"director_approval": {
"approved_by": "director_01",
"approved_at": "2028-06-20T10:14:02Z"
},
"ixbrl_file_hash": "sha256:8f21...",
"companies_house_response": {
"status": "accepted",
"received_at": "2028-06-21T09:03:44Z"
}
}The critical design decision is versioning. Taxonomies change. Entity eligibility can change. Close adjustments change. Agent responsibility can change. A filing package should remain reproducible after the fact, even if the current chart of accounts, accounting policy, taxonomy suite, or filing software has moved on.
Implementation checklist for 2026 and 2027.
Inventory every UK entity, filing route, accountant or agent relationship, accounting reference period, and current dependency on WebFiling or paper.
Create a statutory reporting calendar that starts at close lock and ends at Companies House acceptance, not at board approval.
Build one report-line mapping table that ties chart of accounts, consolidation mappings, statutory statement lines, and FRC taxonomy concepts together.
Version taxonomy mappings by year so a 2026, 2027, or 2028 filing can be reproduced without guessing which concept library was used.
Treat audit exemption and small-company filing choices as approval-controlled evidence, not free-text notes added at the end of the process.
Test iXBRL validation with a prior-year filing or mock filing pack before the first mandatory software-only deadline.
Define the handoff contract with external accountants: data owner, adjustment owner, taxonomy owner, filing owner, and correction owner.
Retain the human-readable accounts, the machine-readable iXBRL, validation output, approvals, submission acknowledgement, and any correction history together.
The order matters. Start with the entity and filing inventory, then fix the mapping between the ERP and statutory statements, then test validation. Buying or configuring filing software before the internal reporting package is clean can preserve the same manual weakness behind a more modern interface.
Audit evidence should follow the report package.
FRC guidance describes quality for a digital report as structured, machine-readable information that is accurate, complete, and usable for humans and systems. Its practical checks include correct accounting meaning for tags, mandatory tags, signs, calculation relationships, consistent duplicate facts, viewer display, and governance over judgemental tagging decisions.
That maps directly to ERP evidence. Every report line should explain which accounts, entities, periods, eliminations, journals, and statutory adjustments produced it. Every taxonomy tag should have an owner and review state. Every validation exception should have a disposition. Every filed package should be tied to the director-approved version and the Companies House response.
Constructive failure modes to design around.
A chart of accounts that can produce management reporting quickly but cannot explain statutory line mapping without manual spreadsheet work.
A late filing workflow where the accountant owns the submission but the company cannot retrieve the exact accepted iXBRL package and validation trail.
Taxonomy tags selected by wording similarity instead of accounting meaning, creating avoidable review and comparability issues.
Profit and loss data prepared for internal review but not controlled as part of the statutory filing package for small or micro-entity companies.
Package accounts assembled from multiple documents without a component inventory, version lock, or evidence that all parts were submitted together.
Director approval captured outside the reporting workflow, leaving no clear link between approved statements and the filed digital report.
These are solvable design issues. The practical fix is to move statutory reporting evidence earlier in the close process. Once report-line mapping, taxonomy mapping, and filing-package state live in the workflow, the final submission becomes a controlled release rather than a scramble to assemble documents.
What ERP buyers should ask vendors.
Can the system generate a statutory reporting pack from locked close data, with separate management-reporting and statutory-reporting mappings?
Does the product store FRC taxonomy version, concept, context, unit, sign, dimensions, and extension rationale at report-line level?
Can accountants or agents collaborate in the workflow without exporting uncontrolled spreadsheets or losing the audit trail?
Can the system validate iXBRL and preserve validation output, viewer checks, rejected submissions, and accepted submissions as evidence?
How does the product handle audit exemption statements, small-company filing options, package accounts, director approval, and amended accounts?
A credible answer should mention close locks, statutory mappings, taxonomy versioning, report package hashes, validation artifacts, role-based approvals, agent access, rejected filing handling, accepted filing retention, and reproducibility. A narrow answer centered only on document export leaves too much operational evidence outside the control layer.
Practical takeaway.
Companies House 2028 gives UK finance teams enough time to build a better statutory reporting workflow. The goal is simple: the same controlled close data that supports management confidence should also support the filed iXBRL account package. Build the entity inventory, report-line mapping, taxonomy evidence, validation trail, approval state, and accepted filing record now. The 2028 deadline then becomes a clean operating milestone, not a last-mile filing project.
Sources.
- GOV.UK: Companies House to bring in changes to accounts filing from April 2028
- Changes to UK company law: Changes to accounts
- GOV.UK: Using software to file your company's information
- GOV.UK: Preparing and filing Companies House accounts
- FRC: What is XBRL?
- FRC: 2026 FRC Taxonomy Suite
- FRC: Checking your report
- GOV.UK: XBRL guide for UK businesses