Payroll setup overview
Configure schedules, employees, statutory rules and transactions before preparing a pay run.
What this is6 sections
Payroll setup joins named pay schedules, effective-dated employee assignments, compensation, a compatible statutory pack and the transactions that belong in a run. The regular run’s statutory effective date is its service-period end. Payment routing matters to an optional payment-file export, separately from payroll calculation.
What this is
The setup is split across the app rather than a single “Payroll Setup” page:
- Payroll → Schedules creates named schedules, previews occurrences, manages assignments and provides actions to add rule versions, rename or retire schedules.
- Payroll → Overview and Payroll → Runs create, continue and review regular or off-cycle pay runs.
- Transactions contains the controlled catalogue, organisation custom transactions and generated statutory outputs.
- Employees contains employee facts, status, statutory information, and recurring transaction assignments.
- Statutory Packs shows the date-scoped workspace default and retained pack history. Compliance is for Rules and detached Tax Preview.
- My Organisation records employer statutory facts and readiness; Employees supplies each worker’s payment route. Organisation payment methods and the Banks directory have separate roles in optional payment exports.
Before you begin
Select the organisation, schedule and service period. Confirm effective employee assignments, compensation units, close-by date, service-period-end statutory effective date and signed compatible pack.
Set up schedules and employees
Use Set up pay periods to create a schedule, then Assign employees to pay schedules for primary regular service-date coverage. Use Add a pay schedule rule version for a future rule change and Retire a pay schedule when the schedule should stop accepting new assignments. Understand schedule changes and payroll drafts explains what must be refreshed after a change.
Choosing an employee for one run is a separate action. See Choose employees for a pay run.
Understand transaction ownership
On Transactions, use “Controlled catalogue” for pack-managed items. It is read only; each item states its interaction, information source, and available action, such as “Assign to employee”, “Enter in pay run”, “Record controlled event”, “Manage employee information”, or “View generated result”.
Use Custom transactions only for organisation-authored definitions. New custom transaction opens a builder whose tax-category choices come from the approved archetype catalogue; its payroll treatment follows the selected archetype. Generated statutory outputs are calculator results, not definitions to publish or assign.
What to check
Open Payroll → Overview or Runs, select an available schedule occurrence, and check the explicit employee set and calculation-readiness messages. Several regular runs may be available in a month. In the draft, review time off, transactions and a current backend preview before finalisation.
Important boundaries
Paydae calculates and prepares payroll results and approved output files. It does not debit or pay employees. Review totals, output status, and evidence, then use the applicable external channel. The desktop workflow does not make controlled catalogue items or generated statutory results editable.