Understand your organization structure

Read this before you create a single department. The structure you build in the first week is the skeleton the rest of HCM hangs on. Leave, attendance, payroll, expenses, hiring, approvals and reports all read it. A structure that matches how your business really runs makes every later module easier. One that does not match makes every later module awkward, and it is slow to fix once people and payslips depend on it.

This page explains the ideas. For the clicks, follow Onboard your organization: step by step and the how-to tasks.

What the structure is used for

Part of the business	What it reads from the structure
Payroll	Which legal entity a payroll run is for, and which group of people it covers (by department, employment type, pay group or one employee). Country rules come from the country pack for the person's country.
Expenses and travel	The cost center a claim, advance or travel request is charged to.
Hiring	The legal entity, department, location, cost center and position a requisition is for; a job opening carries a cost center too.
Leave, holidays and attendance	The location and country decide which holiday calendar applies to a person: a calendar can be assigned to an organization unit or a country, with a tenant default behind it.
Approvals	The reporting line and the approval hierarchies (Administration) decide who approves.
Onboarding and documents	Checklists, document requirements and orientation programs can be set per legal entity.
Reports and dashboards	Headcount, span of control, open positions and exits are counted by department and by manager.

The building blocks

The structure has two separate trees. People mix them up, so keep them apart in your head.

1. Where the money and the law sit. Legal entities, then business units, divisions, departments and teams, with cost centers and profit centers for finance.
2. What jobs exist. Job families, job levels, job grades, designations and job positions. This is the job architecture.

Every employee is placed in both: they belong to a department (tree 1) and hold a position with a designation and a grade (tree 2).

Tree 1: the organization

Legal entity. A company that is registered with a government and can employ people. It has its own tax and registration numbers and its own payroll and statutory obligations. If two companies in your group each file their own tax returns, they are two legal entities. Create one legal entity per registered employer. This is the most important decision in the whole setup, because payroll runs, statutory registrations, bank accounts and compliance contacts are kept per legal entity.

A tenant can have several legal entities (a holding company and its subsidiaries, or the same company in several countries). A single small company has just one.

Business unit. A major part of the business: a product line, a market segment, a region or a shared-service function. It sits between the legal entity and the departments. Use business units when leaders run parts of the business as separate profit-and-loss units. If your company does not, skip them.

Division. A further grouping inside a business unit. Many companies do not need it. Add it only when departments naturally group under it and someone is accountable for the group.

Department. A functional group of people who do similar work: Finance, Engineering, Customer Success. Departments are the unit you will report on most. A department can have a parent department, a head, a type (functional, operational, corporate, support, regional, project, shared service or other) and an effective date range. Keep departments stable: people, budgets and approvals attach to them.

Team. A small working group inside or across departments. Teams are lighter than departments and are for day-to-day grouping, not for finance.

Branch and location. A location is a place (an office, a plant, a warehouse) with its address, country and working hours. A branch is a distinct operating unit or physical office, which can have its own head and details. The country on a location matters: it decides which holiday calendar and country rules apply, so enter it correctly.

Cost center. A finance bucket that costs are charged to. A cost center is not a department: one department can be spread over several cost centers, and one cost center can serve several departments. Employees, expense claims, advances, travel requests and job openings carry a cost center. Allocation lines can split an employee's cost across more than one cost center, and a cost center can have a yearly budget split over twelve months (the months must add up to the annual amount).

Profit center. A finance bucket for revenue and result, used where leaders are judged on profit. Optional.

Tree 2: the job architecture

Think of it as a vocabulary for jobs, from general to specific.

Term	What it answers	Example
Job family	What kind of work is this?	Engineering, Finance, Sales
Job level	How senior is the work? One standard ladder of seniority and responsibility that every family shares.	Level 1 (entry) to Level 7 (executive)
Job grade	Which pay grade does the work sit in? A grade can carry a salary band.	Grade G5
Designation	What is the person's title?	Senior Software Engineer
Job position	A specific seat in the structure that one person fills.	"Senior Software Engineer, Payments team, Bengaluru"

A designation is a title that many people can hold. A position is one seat, with its own department, reporting line, approved headcount and budget. Companies that control headcount seat by seat use positions; companies that do not can run on designations alone. Positions can be assigned to an employee, released, transferred, reserved, frozen or closed, and a position can have more than one reporting line.

A worked example

Acme Industries has a head office in Mumbai, a factory in Pune and a small sales office in London.

• Legal entities: Acme Industries Private Limited (India) and Acme UK Limited. Two employers, two countries, two statutory regimes, so two legal entities.
• Business units: Consumer Products and Industrial Products. Leaders run each as a separate business.
• Departments: Finance, Human Resources and IT sit directly under the legal entity as shared functions. Manufacturing and Quality sit under Industrial Products. Sales sits under both business units.
• Locations: Mumbai Head Office, Pune Factory, London Sales Office. Each gets its country and time zone, so Pune and Mumbai follow the Indian holiday calendar and London follows the UK one.
• Cost centers: one per department, plus a separate one for the Pune factory overhead because finance tracks it on its own.
• Job architecture: four job families (Operations, Sales, Finance and Support, Technology), seven levels, grades G1 to G9, and about forty designations. Positions are created only for manufacturing, where headcount is approved seat by seat.

When Acme hires a Quality Engineer in Pune, the requisition names the Quality department, the Pune location, the cost center and the position. The new employee is paid by Acme India, takes Indian holidays, charges expenses to the Quality cost center, and asks their manager for approvals.

Decisions to make before you start

Write these down; they are hard to change later.

1. How many legal entities? One per registered employer. Count each country separately.
2. Do you need business units and divisions? Only if leaders run them as separate units. Fewer layers are easier to keep right.
3. What are your departments? Use your real functions, not your current project names. Aim for departments that will still exist in two years.
4. How do cost centers map to your finance system? Reuse the codes your finance team already uses, so reports reconcile.
5. Seats or titles? Decide whether you control headcount by position or only by designation.
6. What is your grade structure? Align it with the pay bands in your compensation policy before you create grades.
7. Who is the head of each department? Heads and reporting managers drive approvals; an empty head is the most common reason approvals stall.

Good practice

• Create top-down. Legal entities and locations first, then departments, then designations and grades, then cost centers and positions. Lists in later windows pick from earlier ones, so a missing earlier record shows as an empty pick-list.
• Use codes that will not change. A code identifies the record in lists, files and reports. Rename the name if the business changes; keep the code.
• Use effective dates. Give a new structure an Effective from date. When a department is reorganized, close the old one and start the new one instead of overwriting history.
• Do not model people in the structure. A person belongs to a department; the department does not become a person. Do not create a department per manager.
• Keep one source of truth. If finance owns cost center codes, copy them from finance, do not invent them in HR.

Mistakes we see most

• One legal entity for everything. It works until the first subsidiary or foreign office, then payroll and statutory reports cannot be separated. Create the entities you need now.
• Departments that mirror people. "John's team" becomes obsolete the day John moves. Use teams for that.
• Cost center = department, always. Fine for a small company; it breaks as soon as finance splits a department or shares a cost center.
• No department head. Approvals and the "without head" count on the Departments screen both depend on it.
• Wrong country on a location. The holiday calendar and the country rules follow the country.

Related

• Onboard your organization: step by step
• How-to tasks: add a department, legal entity, location, position and more
• Reporting Structure & Organization Structure
• Positions