> For the complete documentation index, see [llms.txt](https://help.allwage.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.allwage.com/modules/payroll/recurring-pay-runs.md).

# Recurring Pay Runs

Create multiple recurring pay runs to make sure each group of employees gets paid on time

A recurring pay run is a payroll procedure designed to simplify and streamline the remuneration of employees with consistent pay structures and schedules. It offers several key advantages:

**Customisable Pay Periods**: Each recurring pay run can be individually configured with its own payment frequency, whether it's on a monthly, fortnightly, or weekly basis. This flexibility allows businesses to align payment cycles with their unique operational needs.

**Employee Grouping**: Recurring pay runs enable the grouping of employees who share similar job roles or payment structures. For instance, all packhouse employees or harvesting workers can be categorised within their respective pay runs, making it easier to manage and process payments efficiently.

**Leave**: Employees linked to a specific recurring pay run will accrue leave based on the configuration set for that pay run.

**Payment structure**: Avoid mixing different payment types (e.g., fixed salary and hourly wage) within the same pay run.

**Multiple Companies**: Pay runs are grouped per company. Easily separate employees between multiple legal entities

In summary, recurring pay runs are a versatile tool for managing payroll operations by tailoring payment schedules and grouping employees according to their roles, whether they are permanent or seasonal staff. This aids in achieving greater efficiency and accuracy in the payroll process.

Move on to the next section to create a new recurring pay run.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.allwage.com/modules/payroll/recurring-pay-runs.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
