Core HR
Three Structures, Three Functional Areas, and Where Each Setting Lives
Legal, managerial and functional are three axes rather than one nesting — and their setup tasks are split across three functional areas, with one record that is created in one work area and revised in another.
Learning objectives
- 1.Name the three fundamental structures and the records each is implemented with
- 2.State the responsibilities a legal entity takes on by being registered
- 3.Name the implementation decision factors the structures are shaped by
- 4.Locate the setup tasks for each structure, and the one record whose revision lives elsewhere from its creation
Why this matters
An enterprise is not one tree, and the moment a design treats it as one, two questions become unanswerable: which legal entity employs this worker, and which business unit manages this work. Those are different axes that only sometimes coincide, and the application models them separately on purpose — one structure for the law, one for management reporting, one for what people actually do.
If you skip this: A structure designed as a single nesting answers every reporting question the same way, and the first statutory report that needs a different grouping cannot be produced without rework.
What it is, why it exists, what breaks
What it is
Every enterprise has three fundamental structures — legal, managerial and functional — implemented using the chart of accounts and organization hierarchies rather than as a single nested hierarchy. The management structure is implemented with divisions and business units and reflected in the chart of accounts; the functional structure is implemented with departments and organizations, including sales, marketing, project, cost and inventory organizations.
Why it exists
Three structures because three questions are asked of the same workforce: what does the law see, what does management measure, and what work do people actually perform. One record set cannot answer all three without distorting at least one of them.
What breaks without it
The shapes do not have to line up. One business can be operated by legal entities in several countries, and one legal entity can run several businesses — so a hierarchy that assumes one parent per node is wrong in both directions at once.
Source: COREHR-ORDER-001, COREHR-ENT-025
Three structures, three axes
Legal, managerial and functional are three separate axes with different records, not one nested hierarchy — one business can span several legal entities and one legal entity can run several businesses. Listed in order: Legal structure, then Management structure, then Functional structure, then Legal Structures functional area, then Organization Structures functional area, then Workforce Structures functional area and work area.
An enterprise is modelled with three fundamental structures — legal, managerial and functional — and they are axes rather than layers. The legal structure is implemented with legal entities: registered in their jurisdictions, able to own and trade assets and to employ people there, and carrying the responsibilities that registration assigns — statutory and external reporting, compliance with legislation and regulations, income and transaction taxes, and VAT collection on behalf of the taxing authority. The management structure is implemented with divisions and business units and is reflected in the chart of accounts. The functional structure is implemented with departments and organizations, including sales, marketing, project, cost and inventory organizations, and its expenses land directly on the income statement. The axes deliberately do not line up: one business can be operated by legal entities in several countries, and one legal entity can run several businesses, which is why a single tree cannot answer all three questions and the first statutory report that wants a different grouping exposes the difference. The configuration is split to match the structures: legal entity setup tasks sit in the Legal Structures functional area, business unit setup in Organization Structures, and department, division, trees, jobs, positions and other organizations in Workforce Structures. One exception is worth memorising on its own: payroll statutory units, legal employers and tax reporting units are created from the Manage Legal Entity task in Setup and Maintenance, but revised with Manage Legal Entity HCM Information in the Workforce Structures work area — a record whose creation and revision live in different work areas.
What to take from this: Read the diagram as axes rather than layers. The legal axis says who employs; the management axis says what is measured; the functional axis says what people do. The example worth pausing on is the business that appears in three legal entities — a single row on the management axis, three columns on the legal one.
Source: COREHR-ORDER-001, COREHR-ENT-025
The statutory report that wanted a grouping the tree did not have
An enterprise is configured with departments reporting up to business units, and the business units up to a single parent — one tree, used for everything. A statutory body then asks for reporting by legal entity, and several departments turn out to span two.
- 1.The reporting request is read as "add a level to the tree", which is not what it is.
- 2.The legal structure was never modelled separately, because the single tree absorbed every question into one shape.
- 3.Re-grouping the departments by legal entity cannot be done by rearranging the management tree without destroying the management reporting that already exists.
- 4.The fix is modelling the legal axis explicitly, not editing the management one until it coincidentally answers both.
Takeaway: The three structures exist so that one reporting question never has to distort another. A model that answers them all with one tree has not simplified anything; it has deferred the collision.
Source: COREHR-ORDER-001, COREHR-ENT-025
Configuration model
Navigation paths
Setup and Maintenance > Legal Structures functional area > legal entity setupCOREHR-ENT-026Setup and Maintenance > Organization Structures functional area > business unit setupCOREHR-ENT-026Setup and Maintenance > Workforce Structures functional area > departments, divisions, trees, jobs, positions and other organizationsCOREHR-ENT-026
Objects
Legal entities
The legal structure. A registered entity can own and trade assets and employ people in its jurisdiction.
Risk if wrong: The legal employer designation that payroll pays through is made on the legal entity, and an enterprise without a modelled legal axis cannot answer statutory questions at all.
Divisions and business units
The management structure, also reflected in the chart of accounts.
Risk if wrong: Management reporting inherits whatever grouping the business units carry, including the autonomy decisions the implementation made for other reasons.
Departments and organizations
The functional structure: sales, marketing, project, cost and inventory organizations, plus the department tree that cost centres track through.
Risk if wrong: Functional reporting reflects a structure that describes the law or the org chart rather than the work, and functional expenses land on the wrong income statement lines.
Manage Legal Entity HCM Information
Revises payroll statutory units, legal employers and tax reporting units in the Workforce Structures work area.
Risk if wrong: A change searched for in Setup and Maintenance, where the record was created, and not found there.
Constraints
- Every enterprise has three fundamental structures: legal, managerial and functional.
- The legal structure is implemented using legal entities; the management structure using divisions and business units, reflected in the chart of accounts; the functional structure using departments and organizations.
- A legally recognized entity can own and trade assets and employ people in the jurisdiction in which it is registered, and is assigned the responsibilities of statutory and external reporting, compliance with legislation and regulations, paying income and transaction taxes, and processing VAT collection on behalf of the taxing authority.
- Legal entity setup tasks sit in the Legal Structures functional area, business unit setup in the Organization Structures functional area, and department, division, trees, jobs, positions and other organizations setup in the Workforce Structures functional area.
- Payroll statutory units, legal employers and tax reporting units are created from the Manage Legal Entity task in Setup and Maintenance, and revised using the Manage Legal Entity HCM Information task in the Workforce Structures work area.
- The Workforce Structures work area is where departments, divisions, disability organizations, organization trees, department trees, position trees, locations, jobs, positions, grades, grade rates and grade ladders are added and edited.
Source: COREHR-ORDER-001, COREHR-ENT-024, COREHR-ENT-026, COREHR-ENT-027, COREHR-ENT-028
Common mistakes
Wrong: Modelling the enterprise as one tree with the enterprise at the top.
Symptom: Statutory or management reporting that needs a different grouping cannot be produced without rearranging the whole structure.
Fix: Legal, managerial and functional are three structures with different records. Model each one; do not make one tree answer all three.
Wrong: Looking for legal entity setup tasks in the same functional area as department setup.
Symptom: Tasks appear to be missing from the list, and the conclusion is that the environment differs from the documentation.
Fix: Legal entity setup is in the Legal Structures functional area, business units in Organization Structures, and departments, trees, jobs and positions in Workforce Structures.
Wrong: Revising a legal employer from the task it was created by.
Symptom: The change is looked for under Manage Legal Entity in Setup and Maintenance, and the revision task is not there.
Fix: Create from Manage Legal Entity; revise with Manage Legal Entity HCM Information in the Workforce Structures work area.
Wrong: Deciding the structure by org chart alone.
Symptom: The structure answers who reports to whom fluently and every other question not at all.
Fix: The documented decision factors are the industry, business unit autonomy, business and accounting policies, business functions and whether they centralize in shared service centers, and facility locations.
Diagnosing it
Symptom: A required structure object cannot be created, or a required change cannot be found in the task list it is being looked for in.
Category: configuration
- 1.
Which of the three structures does the object belong to — legal, managerial or functional?
If no: Naming the structure names the functional area, and the functional area names the task list. Most "missing task" reports are a structure question in disguise.
Evidence to capture: The object being created against the three structures
- 2.
Is the object one whose revision lives in a different work area from its creation?
If no: Payroll statutory units, legal employers and tax reporting units are created in Setup and Maintenance and revised in the Workforce Structures work area.
Evidence to capture: The task being searched for against where that object type is revised
- 3.
Was the structure shaped by all five documented decision factors, or only the org chart?
If no: A structure decided by reporting lines alone will satisfy reporting-line questions and distort industry, policy, shared-service and location questions.
Evidence to capture: The recorded structure decisions against the five factors
Confirm: Confirm the structure the object belongs to, then the functional area that owns its setup, then — for the legal entity HCM records — whether this is a creation or a revision.
Recall
Name the three fundamental structures and the records each is implemented with, and say which functional area each one’s setup tasks sit in.
Answer shape: Legal, managerial and functional. Legal is implemented with legal entities; managerial with divisions and business units, reflected in the chart of accounts; functional with departments and organizations including sales, marketing, project, cost and inventory organizations. Legal entity setup is in the Legal Structures functional area, business unit setup in Organization Structures, and departments, divisions, trees, jobs and positions in Workforce Structures. Payroll statutory units, legal employers and tax reporting units are created from Manage Legal Entity and revised with Manage Legal Entity HCM Information in the Workforce Structures work area.
Memory hook: Law, management, work — three axes, never one tree. Legal Structures, Organization Structures, Workforce Structures — three areas. Created in Setup, revised in Workforce.
Source evidence
The three-structures model with its implementation records, the legal entity privileges and responsibilities, the functional-area split for setup, the legal entity HCM revision task, and the workforce structures work area list were read on 2026-10-09 from the enterprise structures overview, the legal entities overview, the workforce structures overview and the workforce structures enterprise-level configuration page.
Release scope: FA Latest
Recorded gaps
- The enterprise-level configuration page describes job and position code generation methods, defaults for effective start dates and evaluation systems, and minimum search characters per structure type. COREHR-WS-015 already carries the code generation methods; the remaining options are named here and not taught as behaviour, because the page describes the options and not their consequences.
- The enterprise structures overview illustrates the model with an example enterprise of registered companies and divisions. The example is descriptive and no specific enterprise shape is asserted as recommended.
Related concepts
- The enterprisedepends on
The enterprise is the boundary all three structures are defined within, and the configuration-order lesson teaches the sequence they are built in.
- Legal entity and legal employerteaches
The legal entity is the record the legal axis is implemented with, and the one whose registration carries the statutory responsibilities.
- Departmentextends
Departments implement the functional axis, and the department lesson’s cost-centre tracking is the functional structure meeting the chart of accounts.
Self-check
An auto-graded assessment is attached to this lesson: assessment-core-hr-enterprise-structures
Lesson progress
Checking your progress…