Setup Considerations: pay elements

What this achieves

Your pay element catalogue is the vocabulary every payslip is written in, so the shape you choose now decides what your payslips and statutory reports can say later. Getting the granularity and the tax treatment right before your first run avoids reissuing payslips to correct them.

Decision 1: how granular to make the catalogue

An element is a line on a payslip. The question is how many distinct lines you want people to see.

Option	Description
Few, broad elements	Simpler to maintain. Payslips are shorter, but you cannot report on a component you did not separate.
Many, specific elements	More to maintain. Every component can be reported on, questioned, and given its own tax treatment.

Split an element whenever two things are taxed differently, reported separately, or need to be switched off independently. Keep them together when they always move as one.

Example: HC Corp UK Ltd keeps one London Travel Allowance rather than splitting travel into rail and bus, because both are taxed identically and are always granted together. It does keep a separate element for a pension deduction, because that has its own treatment and its own reporting.

Each element carries two independent switches — whether it is taxable, and whether it enters the social-insurance base. They are separate because real statutory rules treat them separately.

An element can be taxable but outside the social-insurance base, or inside the base but not taxable. Treating the two as one switch is the most common configuration error, and it produces figures that look nearly right.

Example: at HC Corp UK Ltd an element that is taxable but outside the social-insurance base affects PAYE without changing National Insurance. An element inside the base changes both.

Where you are unsure, get the treatment confirmed before your first run rather than after. A wrong flag understates or overstates a statutory deduction for every person the element reaches, in every period it has been in place.

Decision 3: what carries the amount

A pay element defines what is paid and how it is taxed, never how much. That leaves you a choice about where the amount lives.

Option	Description
An eligibility rule	The amount is set once on a rule and worked out at each run for everyone who matches its criteria. Best when many people get the same thing for the same reason.
A figure on the employee	The amount is specific to one person. Best when it genuinely varies individually.

Example: every HC Corp employee based in London gets the same travel allowance, so it belongs on a rule. A one-off retention arrangement for a single person does not.

Decision 4: codes

Codes appear in exports, imports, and bank files, and other systems key on them. Choose a scheme before you create the first element, because renaming a code after integrations depend on it means changing both sides at once.

Example: TRAVEL-LDN reads clearly in a statutory report and in a payment file. EL-004 does not.

What is expensive to change later

Decision	Cost of changing later
Taxable and social-insurance flags	High. Every payslip already produced used the old treatment, and correcting them means adjustments rather than an edit.
Element code	High once anything integrates against it. Exports, imports, and downstream systems key on the code.
Splitting one element into two	Medium. New elements apply going forward; history keeps the old shape, so reporting spans two structures.
Element name	Low. Employees see it on their payslip, so keep it readable, but changing it is safe.

What happens next

Once the catalogue exists, decide how each element reaches people. Elements granted to a group by criteria become eligibility rules, elements driven by law come from the statutory profile for the jurisdiction, and commission plans pay into an earning element you nominate.