IXL CORE
All guides
HR & PayrollGuide ยท v1.0

Configure pay components

Create a payroll component master with a typed calculation rule, accounting mapping, statutory flags, display order and visibility that every payroll run consumes.

Everything on a payslip is a payroll component: earnings, deductions, employer contributions, statutory items and informational lines. Each component carries a typed calculation rule and settings that every run reads. This guide covers creating and editing a component.

Before you start

  • You need permission to manage payroll components.
  • Decide the component type and how it should calculate (fixed amount, percentage of something, a rate table, or a registered formula).
  • Editing an active component cuts a new draft version from your changes rather than altering the live one.

Steps

  1. Open the Payroll workspace and go to the Components panel.
  2. Enter a Code (required, uppercase letters, digits and underscores only, up to 60 characters).
  3. Enter a Name (required, up to 180 characters).
  4. Choose the Component type (required): Earning, Deduction, Employer contribution, Statutory or Informational.
  5. Set the Calculation rule (required) by choosing a type:
    • Fixed โ€” a flat amount.
    • Percentage โ€” set what it is a percentage of and the rate (0โ€“100).
    • Rate table โ€” set the table reference.
    • Formula โ€” set the registered formula expression reference (a labelled reference, not free-form code).
  6. Optionally set the Accounting mapping: GL account reference and cost centre reference.
  7. Optionally set the Statutory flags: Taxable, Pensionable and Leviable.
  8. Optionally set the Display order (0โ€“100000) to control ordering on the payslip.
  9. Optionally set Visibility: Payslip visible and ESS visible.
  10. Save. Status is managed by the system, not entered here.

[screenshot: Component form showing code, type and the calculation-rule selector]

Result

The component is saved as a master with a working version. Active components publish; edits create a new draft version so live runs stay stable until you publish the change.

Put this into practice