Cross-validation and segment value security

Two halves, and both are about stopping something rather than enabling it. Cross-validation rules. Dynamic insertion allows any combination, including nonsense — a revenue account against a balance-sheet-only cost centre. Build a rule with a condition filter and a validation filter, then test it by deliberately entering a blocked combination and reading the error. Write rules as exclusions of what is forbidden, not enumerations of what is allowed, or maintenance eats you. And rules only apply to combinations created after the rule exists, so run the validation report against the combinations you already have. Segment value security. Restricting which values a user can see or use. Build a rule limiting a user to one company value, assign it to a role, then sign in as that user and demonstrate the restriction. These are a data-security mechanism and they interact with data access sets, which is why the two are easy…

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