Carry the same controlled accounting record into mapping, disclosures, statutory presentation and finalisation without rebuilding the year end in another package.
Balansix is designed so the final accounts remain connected to the figures produced in the Accounting Workspace. The year-end process therefore starts from a known source rather than a new file that has to be reconciled back to the bookkeeping system.
Balansix supports accounts-production workflows for eligible micro-entities under FRS 105 and eligible small entities using FRS 102 Section 1A. The accounts engine is designed to select the relevant rules according to the accounting period so presentation and disclosure logic can follow the standard applicable to that period.
That period-awareness matters as UK GAAP changes. The accounting standards are not treated as one permanently frozen template; the workflow is structured around controlled rule packs that can distinguish periods before and after material changes in the reporting framework.
Figures are not designed to become casually editable copies inside accounts production. When the underlying accounting is wrong, the controlled response is to correct the accounting record and carry the effect through.
Accounts production should help the preparer understand how the trial balance becomes the statutory presentation, not hide that transformation behind an opaque final PDF.
Confirm entity, reporting framework, period and the key presentation settings that determine the accounts workflow.
Map accounting balances into the statutory structure and keep the relationship between ledger and financial statements visible.
Prepare relevant notes and narrative disclosures with professional review over the content that accompanies the figures.
Statutory compliance is only one part of accounts production. The presentation also represents the practice. Balansix is designed to produce clean, professional accounts with consistent typography, spacing, notes and supporting reports rather than treating the final PDF as an afterthought.
An accountancy practice handles more than one company type. Balansix is designed so the underlying workflow can support the relevant entity and presentation variants configured for the engagement rather than forcing every client through an identical front end.
Balansix keeps arithmetic and compliance-oriented diagnostics inside the accounts workflow. Review is focused on the conditions that affect a reliable output rather than adding generic warning noise that trains staff to click through everything.
Transaction → reconciliation → adjustment → trial balance → mapping → disclosure → statutory output. Balansix keeps those stages connected so the reviewer can move backwards when a figure needs explanation.
The finalised accounts can feed the supported digital-output and Companies House filing workflow from the same controlled figures. iXBRL output and filing data should remain another representation of the approved accounts, not a separate set of numbers maintained by hand.
Generate digital accounts output from the finalised accounts structure for supported downstream workflows.
Prepare supported Companies House accounts submissions from the controlled final-accounts position.
Keep filing output tied to the same figures that were reviewed and approved inside Accounts Production.
Finalisation should change how the system behaves. Balansix is designed so controlled areas such as setup, mapping and disclosure become read-only after finalisation, protecting the completed output from unintended changes.
When the accounts are finalised, the workflow should preserve the position that was reviewed and approved. If a correction is genuinely required, it should happen through a controlled route rather than by quietly editing a note or mapping after the fact.
Bring a real client workflow to the demonstration and compare how many handoffs, re-keying points and separate systems Balansix can remove.