Anatomy of a chart of accounts

Six objects, bottom to top, and the lesson builds them twice — upward and then downward — because the indirection in the middle does not land the first time. Value set: the list of allowed values for one segment. Independent validation, character data type, a maximum length. This is the vocabulary. Segment: one position in the account combination, backed by exactly one value set. Structure: the ordered set of segments — it defines shape: how many, in what order, of what lengths, with what labels. Structure instance: a deployed copy of a structure, and what a ledger actually points at. The indirection exists because multiple instances can share one structure. Deployment: nothing works until you deploy. It is the step that turns metadata into a usable flexfield, and it is the single most common "why can I not see my segment" support question in the product. Account combination: one concrete…

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