Setting Up a PAYE Scheme as a New Employer: The Bookkeeping View

The moment a Harrow business takes on its first employee, a new compliance cycle starts that did not exist when the founder worked alone. Real-Time Information has to reach HMRC every payday, deducted tax and National Insurance have to be remitted every month, and each of those movements leaves a footprint in the books that has to reconcile back to the payroll software. Setting up the PAYE scheme correctly at the start is what keeps that footprint clean for the rest of the scheme's life.

This is the bookkeeping view of becoming an employer rather than a step-by-step on payroll software. It covers when registration is required, the timing constraints HMRC imposes, what the first payroll run actually submits, when the money is due, and how the whole cycle is reconciled in a Xero or QuickBooks ledger so the year-end accounts tie to the figures HMRC already holds.

When you actually need a PAYE scheme

You do not need a PAYE scheme simply because you have hired someone. According to HMRC, registration is required once any employee is paid £96 or more a week, gets expenses or company benefits, has another job, is receiving a pension, or has previously received certain benefits such as Jobseeker's Allowance. Below the £96 weekly threshold, with none of those other conditions present, a scheme is not mandatory, though payroll records still have to be kept either way.

For most owner-managed businesses one of those conditions is met immediately. A director paying themselves a salary, or a first part-time employee on more than £96 a week, both trigger the requirement. The practical answer is that almost any business deliberately running a salary needs to register, and the few that genuinely sit below the threshold should still keep the records that would be needed if they cross it mid-year.

The registration timing trap

Two HMRC timing rules catch new employers out. You must register before the first payday, and the PAYE reference number is sent by post rather than issued instantly, so the registration cannot be left to the day before payroll runs. At the same time, you cannot register more than two months before you start paying people. That leaves a window: register inside the two months before the first payday, but with enough lead time for the reference to arrive by letter.

The reference that arrives is two numbers a bookkeeper needs from day one: the employer PAYE reference and the Accounts Office reference. The first identifies the scheme on every Real-Time Information submission; the second is the reference money is paid against. Recording both in the payroll software and the accounting platform at setup avoids the scramble when the first payment to HMRC falls due.

What the first Full Payment Submission carries

Payroll under PAYE is reported through Real-Time Information, and the core filing is the Full Payment Submission, or FPS. The FPS tells HMRC about every payment made to employees and every deduction taken from their pay. HMRC is explicit that it must be sent on or before payday, and that it must include everyone paid, even an employee earning less than £96 a week. The "on or before" rule is the one most often broken by businesses that run payroll late and file after staff have already been paid.

Where the business is reclaiming money from HMRC rather than just reporting deductions, a second filing comes into play. The Employer Payment Summary, or EPS, is used to claim reductions on what is owed, such as the recovery of statutory pay. The EPS is sent by the 19th of the following tax month, separately from the FPS. A first-time employer reclaiming Statutory Maternity Pay or Statutory Sick Pay learns the EPS quickly; most others meet it later. The reconciliation patterns for statutory pay are covered in the wider payroll bookkeeping hub.

When the money is due to HMRC

Reporting and paying are two separate obligations. The FPS reports the figures on payday; the cash follows on a monthly cycle. HMRC requires the tax and National Insurance owed to be paid by the 22nd of the following month for electronic payments, or the 19th if paying by post. For a business running monthly payroll, that means the deductions from, say, a 28 March payroll are remitted by 22 April.

Smaller employers have an easing. HMRC allows employers who usually pay less than £1,500 a month to pay quarterly instead of monthly, by arrangement. A first employee on a modest salary often sits inside that limit, which reduces the remittance to four payments a year rather than twelve. The reporting cadence does not change, though: the FPS is still filed on or before every payday regardless of how often HMRC is actually paid.

The monthly PAYE timeline

How the payroll run lands in the ledger

Every payroll run produces a set of figures that have to be posted to the books, whether the software does it automatically through an integration or the bookkeeper journals it manually. The gross pay is an expense, employer National Insurance is a further expense, and the deductions create liabilities that sit on the balance sheet until paid. A clean payroll journal separates these so the profit and loss shows the true cost of employment and the balance sheet shows exactly what is owed to whom.

• Gross pay and employer National Insurance post to wages expense accounts in the profit and loss.
• PAYE and employee National Insurance deducted post to a PAYE/NIC liability account on the balance sheet.
• Net pay posts as a reduction in the bank account when staff are actually paid.
• Pension contributions deducted post to a pension liability account until the provider takes them.
• When HMRC is paid, the PAYE/NIC liability clears against the bank, and should reconcile to zero each month.

The test of a correctly posted payroll is that the PAYE/NIC liability account returns to nil each month once HMRC has been paid. A residual balance means either a payment was missed or the journal does not match what was filed. Catching that drift early is part of the discipline of monthly bookkeeping, and it is far easier than unpicking eleven months of mismatched payroll at year-end.

Why this matters for the year-end accounts

If the payroll figures in the ledger do not tie to the Real-Time Information already filed, the year-end accounts will show a payroll cost that disagrees with HMRC's own records. That mismatch is exactly the kind of inconsistency that slows a year-end down, because the accountant has to reconcile two sets of numbers that should have agreed all along. A limited company carries the added layer of director payroll interacting with dividend planning, which is why clean payroll posting matters as much for a one-director company as for one with staff, a point covered in the guide to bookkeeping for limited companies.

The same digital-record-keeping direction of travel that reshaped VAT and is now reshaping income tax under Making Tax Digital applies to the evidence behind payroll too: HMRC increasingly expects the numbers in the software, the numbers filed, and the numbers in the accounts to be one continuous, reconcilable trail rather than three separate workings that happen to roughly agree.

Getting the scheme set up cleanly

The cost of getting PAYE setup wrong is rarely a single large error; it is a slow accumulation of small ones. A reference recorded late, an FPS filed after payday, a payroll journal that never quite reconciles, a quarterly payment option not taken when it was available. None of them is fatal on its own, but together they produce a year-end where the payroll cannot be tied out, the liability account carries an unexplained balance, and the accountant bills for the time spent unpicking it. Setting the scheme up properly at the start, with the references recorded, the filing cadence understood, and the journal posting clean from the first run, is what keeps the whole cycle quiet for the years that follow.

Frequently asked questions

Do I need a PAYE scheme to pay myself as a director?

If the director's salary is £96 or more a week, or the director has another job or pension, then yes, the scheme is required. Most owner-managers deliberately run a salary at or near the personal allowance, which is well above the threshold, so a scheme is needed. The director's salary level itself interacts with corporation tax and dividend planning and is a decision worth taking deliberately rather than by default.

How long does PAYE registration take?

HMRC sends the PAYE reference number by post, so registration is not instant. Allow time for the letter to arrive before the first payday, and remember you cannot register more than two months ahead. The practical window is to register within those two months but with enough lead time that the reference is in hand before payroll runs.

What happens if I file the FPS after payday?

The FPS is required on or before payday. Filing late can trigger penalties and flags the scheme for HMRC attention. There are limited reasons HMRC accepts for a late FPS, but routine lateness because payroll was run after staff were paid is not one of them. Running payroll a day or two ahead of payday, so the FPS goes in on time, is the simplest way to stay compliant.

Can I pay HMRC quarterly instead of monthly?

If your average monthly PAYE and NI bill is usually less than £1,500, HMRC allows quarterly payment by arrangement. This suits a business with one or two employees on modest salaries. The reporting does not change: the FPS is still filed on or before every payday. Only the remittance of the cash moves to a quarterly cycle.