Legislative data groups

The most important lesson in the module, and possibly in the phase. An LDG is a hard partition, not a filter. Payroll definitions, elements, rates, balances and the related setup live inside one and are not visible outside it. That word is the whole lesson: a filter hides things that are still there; a partition means they genuinely are not, and there is no permission you can grant that reaches across it. The default rule: one LDG per country you employ people in. Start there, and deviate only with a reason. When do you need more than one in a country? Genuinely rare. Reasons that sometimes qualify: legally separate payroll operations that must not share element definitions, or an acquired entity kept fully separate during a transition. Reasons that do not: "different divisions", "different pay frequencies", "it feels tidier". Pay frequency is the one that catches people — it is…

In this module: Module 4 · Legal Entities, LDGs, PSUs, TRUs and Business Units

1. 1What we are building
2. 2The decisions you cannot undo
3. 3The object map
4. 4Legislative data groupsFree preview
5. 5Legal employers, PSUs and TRUs
6. 6Running the structure design workshop
7. 7Four worked country models
8. 8Legal jurisdictions and authorities
9. 9Creating legal entities
10. 10Designating legal employers, PSUs and TRUs
11. 11Creating legislative data groups
12. 12Business units
13. 13Reference data sets
14. 14Associating business units with legal employers
15. 15Deduction levels and calculation cards
16. 16Proving the structure works
17. 17What breaksFree preview
18. 18Lab briefing: the Northwind structure
19. 19Lab solution walkthrough