Implementing Cloud Financials: From Empty Pod to Go-Live · Module 4 · Chart of Accounts and Ledger Design
Loading account values
Lesson 37 of 153 · 8 min
Add values to the company value set by hand first, so you see the account type field appear on the natural account segment and understand why it appears only there. Set summary versus detail, the enabled flag, and start and end dates. Then switch to bulk: file-based upload for around 120 natural account values, verify the load, and look at the rejections from a deliberately malformed row. Account type on natural account values drives year-end close behaviour. Get it wrong and retained earnings is wrong — and you will not find out until the year closes. Never delete a value that has been used. End-date it. A deleted value takes its history with it; an end-dated one stops being selectable and leaves the past intact. Above about fifty values the bulk path is the only sane approach, and it is worth learning here rather than at cutover.
The full lesson is part of the course
The video, the complete written lesson and the module quiz are included in Implementing Cloud Financials: From Empty Pod to Go-Live, with a certificate on completion and a fourteen-day refund window.
In this module: Module 4 · Chart of Accounts and Ledger Design
- 1What we're building
- 2The decision you can't undo
- 3Anatomy of a chart of accounts
- 4Segment labels and qualifiers
- 5Running the design workshop
- 6Sizing segments: the arithmetic
- 7Building value sets
- 8Structure, instance, deployment
- 9Loading account values
- 10Account hierarchies and why reporting needs them
- 11Building and publishing a hierarchy
- 12Accounting calendars
- 13Currency and conversion rate types
- 14Primary, secondary, reporting: the decision tree
- 15Building the primary ledger
- 16Ledger options and completing the definition
- 17Cross-validation and segment value security
- 18What breaks
- 19Lab briefing: Meridian Trading