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

# Payroll periods

> A payroll period is one pay cycle — "May 2026", "Week 23", "First half June" — with a start date and an end date.

A payroll period is one pay cycle — "May 2026", "Week 23", "First half June" — with a start date and an end date. Every payroll run is created **for a period**, and the period also ties payroll to your accounting calendar: when you close a period, you lock both the payroll and the matching accounting period together so nobody can post into a cycle you've already finalised.

Periods are simple but important: they are the spine that runs, payslips and statutory remittances all hang off.

**You'll find this at:** `/settings/erp/finance/payroll-periods` — the old `/payroll/setup/periods` redirects here.

> 📷 *Screenshot: the Payroll Periods list with the "New Period" button and Open/Closed badges — to be added.*

> **Multi-business:** a period belongs to a business and posts to that business's default accounting book. Confirm the business switcher first.

***

## Creating a period

Choose **New Period**. The form asks for:

| Field          | Required | Notes                                        |
| -------------- | -------- | -------------------------------------------- |
| **Name**       | Yes      | A human label, e.g. "May 2026"               |
| **Start date** | Yes      | First day of the cycle                       |
| **End date**   | Yes      | Last day; must be on or after the start date |
| **Business**   | Yes      | Which business this period belongs to        |

The **accounting book** is resolved automatically from the business's default book — you don't pick it. If the business has no default book yet, creation is refused with a clear message; set up the book first.

> **No overlapping open periods.** A new period cannot overlap an existing **open** period in the same business — the system blocks it. (Overlaps with already-**closed** periods are allowed, so an off-cycle or separation run can target a closed window.)

***

## Period status: Open vs Closed

A period is either **Open** or **Closed**.

| Status     | Meaning     | What it allows                                                         |
| ---------- | ----------- | ---------------------------------------------------------------------- |
| **Open**   | The default | Payroll runs can be created and posted into this period                |
| **Closed** | Finalised   | No new payroll postings; the matching accounting period is also locked |

Actions on the list:

| Button         | When shown  | What it does                                                             | Permission              |
| -------------- | ----------- | ------------------------------------------------------------------------ | ----------------------- |
| **New Period** | Always      | Opens the create form                                                    | `payroll:config`        |
| **Close**      | When open   | Locks the period and cascades the lock to the matching accounting period | `payroll:write`         |
| **Reopen**     | When closed | Unlocks the period (and the accounting period)                           | `payroll:period-reopen` |

Closing is a paired action: it closes the accounting period first, then flags the payroll period. **Reopening** is the higher-risk action and needs the dedicated `payroll:period-reopen` permission — typically held only by HR managers and SuperAdmins.

***

## How a run scopes to a period

When you create a payroll run you pick a period. The run records the period (its `payrollPeriodId`) and copies down the period's **business**, **accounting book** and **currency** so the run is self-contained. The period's open/closed state decides whether new runs can post into it.

A run can only post into an **open** period. If you need to correct pay in a closed period you either reopen it (with the right permission) or use an off-cycle / correction route — see [Running payroll](/hr/user/payroll/running-payroll).

***

## Permissions

| Action          | Permission              |
| --------------- | ----------------------- |
| View periods    | `payroll:read`          |
| Create a period | `payroll:config`        |
| Close a period  | `payroll:write`         |
| Reopen a period | `payroll:period-reopen` |

***

## Behind the scenes — closing and the ledger

Closing a payroll period also closes the corresponding **accounting period** for the same book. That means once closed, no payroll journal entry — accrual, payment, or statutory — can post into those dates until the period is reopened. This keeps payroll and your financial statements in lockstep, so a "closed" month really is closed in both places.

***

## Related

* [Running payroll](/hr/user/payroll/running-payroll) — runs are created for a period
* [Income-tax slabs](/hr/user/payroll/income-tax-slabs) — slabs are resolved by the run date within the period
* [Payroll overview](/hr/user/payroll/overview) — the whole chain
* [Accounting periods](/accounting/user/periods-compliance/accounting-periods) — the accounting side of period close