> ## Documentation Index
> Fetch the complete documentation index at: https://human-resource-docs.ha-consultancy.com/llms.txt
> Use this file to discover all available pages before exploring further.

# First-Time Configuration

> The minimum BC Human Resource configuration — general setup, master data, shifts, leave, and payroll inputs — required before hiring your first employee.

This guide walks the minimum configuration you need before you can hire your first real employee and run a payroll-adjacent process end-to-end.

The walk-through assumes a fresh BC company. If you ran the [demo seeder](/getting-started/seed-demo-data), most of these lists already have starter records you can rename or extend.

## 1. HR General Setup

Search for **HR General Setup** and pick your overtime calculation method.

| Field                               | What it controls                                                                                                                                                                                      |
| ----------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Overtime Hour Rate Calculation Type | How the hourly rate for overtime is derived: *Uniform Month Length (30 Days Each)*, *Use Actual Days in Month*, or *Hourly Rate Based on Annual Working Hours*. Affects every overtime journal entry. |

See **[HR General Setup](/configuration/hr-general-setup)** for the full formula behind each option.

## 2. Master data

Populate these lists once — they back the dropdowns on every employee card, document, and request. Open **Tell Me** and search for each:

| List                    | Why you need it                                                                        |
| ----------------------- | -------------------------------------------------------------------------------------- |
| Departments             | Tagged on each employee; targets announcements; filters reports                        |
| Branches                | Multi-site organisations only                                                          |
| Work Types              | Full-time / part-time / contractor — drives EOS and accrual eligibility                |
| Positions               | Title rendered on the employee card                                                    |
| Nationalities           | Required for HR documents (visas, work permits) and air-ticket policy                  |
| Religions               | Optional — used for compliance reporting in some jurisdictions                         |
| Genders                 | Required for HR documents                                                              |
| Employee Document Types | Drives the *Doc Type* dropdown when uploading documents                                |
| HR Document Type List   | Catalog of letters employees can request (employment letter, salary certificate, etc.) |

See **[Master data](/features/master-data)** for fuller coverage.

## 3. Shifts

For every distinct work pattern in your company, create a Shift Config:

1. Search for **Shift Config List** → **New**.
2. Fill code, name, total working hours, weekend days, workdays count.
3. Tick **Add to Roster** if this shift should appear on the Visual Roster Board.
4. Add **Shift Config Lines** for each time block — alternate Work / Break Time rows covering the day. The Roster Board uses these to render bars; payroll uses them to compute hourly rates.

See **[Scheduling & roster](/features/scheduling)**.

## 4. Leave

Two-level setup:

1. **Leave Type Config List** — define the *type* (Annual, Sick, Unpaid…). Tick **Has Deduction Rules** on the type to expose a deduction-rules subform on each plan; see **[Leave deduction rules](/configuration/deduction-setup)**.
2. **Leave Config List** — define a *plan* per type: how many days, accrual cadence, probation rules, min/max consecutive days, contract type, hourly-leave equivalent, etc.

Assign each employee to one Leave Config row per leave type via the **Employee Leave Card**.

See **[Leave management](/features/leave-management)**.

## 5. Payroll-adjacent setup

Configure the following before posting any salary breakdown. None of these are mandatory; each adds a payroll module.

| Setup                        | Why                                                                                                        |
| ---------------------------- | ---------------------------------------------------------------------------------------------------------- |
| **Salary Type List**         | Lists every component (Basic, Allowances, Deductions). The install codeunit seeds Basic + four allowances. |
| **Compensation Allowances**  | Map allowances to salary types and rules                                                                   |
| **EOS Config List**          | End-of-service indemnity rules per work-type / nationality                                                 |
| **Soc. Insur. Setting List** | Employer + employee contribution percentages                                                               |
| **Vacation Time Setup**      | Vacation accrual rules per work-type                                                                       |
| **Air Ticket Policy**        | Per-position / per-nationality air-ticket entitlement                                                      |
| **Overtime Config List**     | Multiplier per overtime band                                                                               |

See **[Payroll setup](/features/payroll-setup)**.

## 6. Employee posting groups

To post HR journals to the G/L, every employee needs an **Employee Posting Group** with a **Payables Account** set — that is the standard BC field the posting engine reads. Open **Employee Posting Groups**, pick (or create) the group you'll assign to most employees, and set its **Payables Account**.

The extension also adds ten *reference* G/L account fields on the same page (Salary, Leave, Overtime, EOS, Loans, Loan Installment, Advance, Bonus, Deductions, Warnings). They are **not** read by the posting engine — they exist as a place to document which G/L account each HR transaction type should hit. You can fill them or leave them blank; the posting flow doesn't care.

See **[Employee Posting Groups](/configuration/posting-groups)** for the full posting flow and the meaning of each reference field.

## 7. Your first employee

1. Search for **Employees** → **New**.
2. Fill the standard BC fields (No., First Name, Last Name).
3. Switch to the **HR** FastTab (added by this extension) and pick Branch, Department, Work Type, Position, Direct Manager, End of Probation date, Religion, Nationality.
4. Save. From the employee card's ribbon you can now open **Documents**, **Family Members**, **Competencies**, **Contract**, **Salary Package**, **Shift**, **Leaves**, **Loans**.

## Verifying the setup

Quick smoke test once you've completed the steps above:

1. Open the Employee Card → Documents → upload a passport scan. The file is stored on the BC table.
2. Open the Employee Card → Shift → assign the day shift for the rest of the month.
3. Open **Visual Roster Board** — the employee should appear with their shift coloured in.
4. Submit an annual-leave request via the leave card. The leave journal records the balance change.

<Note>If any of these fail, the relevant feature page (linked in steps 2–7 above) has a troubleshooting section.</Note>