Account hierarchies and why reporting needs them

A flat list of nine hundred natural accounts cannot produce a balance sheet. Something has to say that these forty accounts are current assets. That something is a hierarchy, and the lesson builds one on screen beside the balance sheet it produces, line by line. Trees and tree versions, and why versioning exists at all: reorganisations happen, and last year's report must still run against last year's structure. Parent values live in the value set alongside detail values, flagged as summary. Three steps, and what each does: audit, activate, publish. Publishing is what pushes the hierarchy into the balances cubes that reporting reads — which is why a hierarchy that exists and was never published produces reports that look wrong for no visible reason. Build the hierarchy from the report backwards. Take the client's balance sheet: every subtotal line on it is a parent node. And keep some depth discipline.…

In this module: Module 4 · Chart of Accounts and Ledger Design

1. 1What we're building
2. 2The decision you can't undo
3. 3Anatomy of a chart of accounts
4. 4Segment labels and qualifiers
5. 5Running the design workshop
6. 6Sizing segments: the arithmetic
7. 7Building value sets
8. 8Structure, instance, deployment
9. 9Loading account values
10. 10Account hierarchies and why reporting needs them
11. 11Building and publishing a hierarchy
12. 12Accounting calendars
13. 13Currency and conversion rate types
14. 14Primary, secondary, reporting: the decision tree
15. 15Building the primary ledger
16. 16Ledger options and completing the definition
17. 17Cross-validation and segment value security
18. 18What breaks
19. 19Lab briefing: Meridian Trading