St. Lucia Payslip Requirements: What to Include

A payslip looks like the simplest document in the whole payroll cycle — a number in, a number out, done. In practice it's the record that everything else gets built from. The monthly PAYE remittance, the AU-1 registration, the P45 when someone leaves, the TD5/P11 annual return: all of them ultimately trace back to what was recorded on each employee's payslip, pay period after pay period.

Get the payslip right, consistently, and the rest of the compliance calendar is just arithmetic on clean data. Get it inconsistent — a missing deduction here, a rounding difference there — and every downstream document inherits the error. This guide walks through what a proper St. Lucia payslip should show and where employers most often leave gaps.

Why the payslip is the foundation, not just a courtesy

It's tempting to treat the payslip as something you hand an employee out of courtesy — proof they were paid. But it's really the source document for the whole PAYE relationship. The income tax withheld each period is what gets remitted to the Inland Revenue Department by the 15th of the following month. The year-to-date totals on the payslip are what eventually populate the TD5/P11 annual return. And if the employee leaves, their P45 is built from the same running totals.

That means a payslip isn't just about paying someone correctly today — it's the first link in a chain that has to stay unbroken for a full tax year, from 1 April to 31 March.

What a proper payslip should show

1. Employer and employee identification

The business issuing the payslip and the employee receiving it should both be clearly identified, so the document stands on its own as a record — not just a number that only makes sense in context.

2. The pay period

Every payslip should state exactly which pay period it covers. Given St. Lucia's April-to-March tax year, it should be obvious which period within that year the figures belong to, so year-to-date totals can be checked against it.

3. Gross pay, broken down

Basic salary or wages, plus any additional pay components for that period — overtime, allowances, bonuses — should be itemised rather than folded into a single lump figure. An employee (and, later, an auditor) should be able to see how gross pay was arrived at, not just what it totalled.

4. Deductions, itemised

Income tax withheld under PAYE and any social-security contributions should appear as their own line items, not netted away. If there are other deductions — a loan repayment, a benefit contribution — those should be visible too. The point is that nothing between gross and net pay should be a mystery.

5. Net pay

The amount actually paid out, after deductions — the figure the employee is really watching, and the one that should match what actually lands in their account.

6. Year-to-date totals

This is the piece employers most often skip, and it's arguably the most important for compliance. Running totals of earnings and tax withheld since the start of the tax year are what make the annual TD5/P11 return a simple summary rather than a reconstruction project. They're also exactly what a P45 draws on if the employee leaves partway through the year.

Where employers slip up

The most common payslip problems aren't dramatic — they're small inconsistencies that compound over a year:

• ✦Lumping pay components together. A single "gross pay" number with no breakdown makes it hard to spot an error later, and harder still to explain if an employee questions their pay.
• ✦Netting deductions away instead of itemising them. Employees can't verify what was withheld, and neither can you when it's time to reconcile the annual return.
• ✦Skipping year-to-date figures. Without them, every payslip is an island — accurate for the period, disconnected from the running story the tax year needs.
• ✦Inconsistent formats month to month. When payslips are built by hand or from an ad-hoc spreadsheet, small formatting drift between months makes it painful to compare periods when something doesn't add up.

Individually, each of these is minor. Together, across twelve months and a growing headcount, they're exactly the kind of gaps that turn a routine annual return or a departing employee's P45 into a scramble to reconstruct numbers that should have been sitting there all along.

How unStatute keeps payslips consistent

unStatute is built natively on the St. Lucia Income Tax Act (Chap. 15.02), and it generates payslips with gross pay, itemised deductions, net pay, and running year-to-date totals built in from the first pay run — not bolted on later. Because every payslip draws from the same underlying employee record, the figures that feed your monthly PAYE remittance, your TD5/P11 annual return, and any P45 you issue are always the same figures your employees already saw on their payslips. Nothing gets re-keyed, and nothing quietly drifts apart.

For a growing team, or a bureau running payroll for several clients, that consistency is the difference between year-end being a formality and year-end being a forensic exercise.

If your payslips are still living in a spreadsheet template someone tweaks by hand each month, start a free 14-day trial at unstatute.com — no card required — and give every pay period a payslip that's already doing the compliance work for you.