neart.ai
EcosystemStoryHow We BuildPricingBlog
Try Inspected →
neart.ai
EcosystemStoryHow We BuildBlog

Ní neart go cur le chéile

A SaltCore Group Limited company

© 2026 neart.ai · SaltCore Group Limited. All rights reserved.

HR & Payroll

How Do I Make Sure a New Starter's First Payslip Is Correct?

3 October 20254 min read

## The short answer


To make sure a new starter's first payslip is correct, collect their bank details and a starter declaration before the first pay run, apply the right tax code based on that declaration and any P45 they provide, set up pension auto-enrolment correctly, and run a pre-payroll check that compares their record against their contract. Most first-payslip errors come from missing information or a default tax code being left in place, and both are avoidable with a short pre-run checklist.


## Why the first payslip matters more than any other


The first payslip is the moment a new employee finds out whether they can trust the organisation with the thing they care about most: being paid correctly and on time. An error here is remembered long after it is fixed. It also tends to be the payslip most likely to be wrong, because the person is new to the system and several pieces of information are being entered for the first time.


## Collect the right information first


You cannot run accurate payroll without complete data, so gather it before the cut-off, not on the deadline.


- **Full legal name, date of birth and National Insurance number.**

- **Bank account details** for the payment itself.

- **A starter declaration** indicating their employment situation, which drives the initial tax code.

- **A P45 from a previous employer**, if they have one, which gives you their existing tax code and pay-to-date figures.

- **Start date and agreed salary or hourly rate**, matched exactly to the signed contract.


If any of these is missing, flag it immediately rather than guessing, because a guess becomes an error that has to be corrected later.


## Get the tax code right


The single most common first-payslip problem is an incorrect tax code. Use the starter declaration and any P45 to apply the correct code from the outset. Where the correct code is genuinely unclear, follow the standard process for new starters rather than defaulting in a way that over- or under-deducts. Make a note of the basis you used, so that if a coding notice arrives later you can reconcile it.


## Handle pension auto-enrolment


Workplace pension obligations apply from the start of employment, so assess the new starter for auto-enrolment as part of setup rather than as an afterthought. Record their assessment, enrol them if eligible, and make sure both employee and employer contributions are configured before the run. Missing this on the first payslip creates a backlog of corrections and member communications.


## Account for partial periods and one-offs


New starters rarely begin on the first day of a pay period, so the first payslip often covers a partial period and needs pro-rata calculation. Check whether:


- The salary should be pro-rated for a mid-period start.

- Any sign-on payment, expenses or allowances are due.

- Salary-sacrifice or benefit deductions should already apply.

- Holiday or other entitlements affect the first period.


## Run a pre-payroll check


Before you commit the run, reconcile the new starter's record against their contract and the information you collected. A short check catches most errors while they are still cheap to fix.


1. Does the gross pay match the contract, allowing for any pro-rata?

2. Is the tax code the one the declaration or P45 supports?

3. Are National Insurance and pension deductions present and sensible?

4. Are the bank details entered correctly?

5. Does the net pay look reasonable for the role and period?


## Reduce the chance of human error


Manual re-keying across multiple systems is where first-payslip errors are born. The fewer times a number is typed by hand, the fewer chances there are to fat-finger it. Connecting onboarding data directly to payroll, so that the start date, salary and personal details flow through once, removes a whole category of mistakes. neart.ai builds enterprise-grade HR and payroll products designed to keep starter data consistent from onboarding through to the first pay run, so the figures on the contract are the figures on the payslip.


## Practical takeaway


Treat the first payslip as a deliverable with a deadline that sits before payroll cut-off, not after it. Collect complete data early, apply the correct tax code from the declaration or P45, set up pension auto-enrolment, account for the partial first period, and run a five-point pre-payroll check. The goal is simple: the new starter opens their first payslip, sees the number they expected, and never has to think about it again.

Related posts

HR & Payroll

What Is Multi-Country Payroll and How Does It Actually Work?

HR & Payroll

Why One Employee Record (a Single Source of Truth) Matters for Global HR

HR & Payroll

UK vs Ireland Payroll: Key Differences Employers Should Understand