UK employers must report every payment to HMRC in real time, on or before the day staff are paid, through a Full Payment Submission, and the cost of employing people rose sharply when employer National Insurance moved to 15% on 6 April 2026 [1]. Those two facts shape every payroll decision a business makes, including how its payroll data reaches its accounts. For the many SMEs and accountants who keep their books in Xero, the practical question is not how to run payroll and accounting as separate chores, but how to make the figures flow cleanly from one into the other.
Payroll produces numbers the accounts need: gross wages, tax and National Insurance owed to HMRC, pension contributions owed to a provider, and the net pay leaving the bank. Accounting software needs those same numbers posted as a journal so the ledger balances. The connection between the two is where time is won or lost each month.
This article explains what UK payroll has to calculate and report, how the resulting payroll journal posts into Xero as the accounting ledger, and what separates a clean payroll-to-Xero integration from a messy one. It is written for employers and bookkeepers who run payroll and keep their accounts in Xero, not for payroll specialists.
Key takeaways
- Payroll and accounting are separate jobs: payroll calculates and reports pay, Xero records the resulting figures in the ledger.
- Every payrun must be reported to HMRC in real time through a Full Payment Submission on or before payday.
- The payroll journal is the bridge: it posts wages, tax, National Insurance and pension liabilities into the accounts.
- A clean integration maps each payroll figure to the correct nominal account automatically, rather than by manual entry.
- HMRC recognition is the baseline for payroll; what differs between products is how well the data flows onward.
Payroll and accounting are two different jobs
It helps to separate two tasks that are often spoken of as one. Payroll is the process of calculating what each worker is paid, deducting the right tax and National Insurance, and reporting it to HMRC [2]. Accounting is the process of recording what the business owns and owes, including the liabilities that payroll creates [3]. Xero is an accounting platform: it holds the ledger that those payroll figures have to land in.
The reason the distinction matters is that the two jobs answer to different masters. Payroll answers to HMRC and to The Pensions Regulator, with statutory deadlines and submission formats [1]. Accounting answers to the business and its accountant, producing the profit-and-loss and balance sheet. A good integration lets each do its job while keeping the numbers in step, so that what payroll reports to HMRC is exactly what the accounts record.
Where the payroll journal fits
The payroll journal is the accounting entry that captures a completed payrun. After payroll has calculated the payrun, the journal posts the gross wage cost, the amounts owed to HMRC and pension providers, and the net pay due to staff, into the correct nominal accounts in Xero [3]. Done well, this is a single automated posting; done badly, it is a monthly re-keying exercise that invites error.
Because the journal has to reconcile to the penny against the bank payments that follow, the figures posted into Xero must match the figures reported to HMRC exactly [1]. This is why the quality of the payroll calculation, not just the accounting, determines whether the month-end reconciles. Most modern UK payroll software produces the journal automatically from the payrun it has just calculated.
What UK payroll has to calculate
Before any figure reaches Xero, payroll has to work out a set of statutory amounts for every worker. These are the numbers the journal is built from, and because there are several of them they are best set out together.
| Payroll figure | What it is | Where it goes |
|---|---|---|
| Gross pay | Total earnings before deductions | Wage cost in the profit-and-loss |
| Income Tax (PAYE) | Tax deducted under the worker's code | Liability owed to HMRC |
| National Insurance | Employee and employer contributions | Liability owed to HMRC |
| Pension contributions | Employee and employer shares | Liability owed to the provider |
| Net pay | Pay after deductions | Cash leaving the bank |
Income Tax is worked out by applying each worker's tax code to their taxable pay, with the basic rate at 20%, the higher rate at 40% and the additional rate at 45% in England and Northern Ireland for the 2026-27 tax year [4]. National Insurance is charged on the employee at 8% in the main band and on the employer at 15% above the Secondary Threshold of £5,000 a year [5]. The employer's National Insurance is a real cost that the journal must post as an expense, not merely a deduction from the worker [5].
The deductions that create liabilities
Beyond tax and National Insurance, payroll may calculate student loan repayments at 9% above the plan threshold, pension contributions on qualifying earnings, and, for larger employers, the Apprenticeship Levy at 0.5% of the pay bill [6]. Each of these becomes a liability the business owes to a third party, so each needs its own line in the journal that posts to Xero [7].
Pension contributions deserve particular care, because the employer owes both its own share and the amount deducted from the worker to the pension provider, and both must be remitted on time [8]. Posting these correctly to the ledger keeps the pension liability visible until it is paid, which is exactly what an accountant reconciling the accounts needs to see [3].
Reporting to HMRC in real time
Running payroll is not complete when the wages are calculated; the figures have to be reported to HMRC through Real Time Information. On or before every payday the employer sends a Full Payment Submission, which reports each worker's gross pay, taxable pay, tax, National Insurance, student loan and pension figures [1]. This is the submission that tells HMRC what the business owes for the period.
Alongside the Full Payment Submission, an Employer Payment Summary is sent where the employer is reclaiming statutory payments, claiming the Employment Allowance, or reporting no payments in a period, and it is due by the 19th of the following tax month [9]. The Employment Allowance can reduce an employer's National Insurance bill, which changes the liability the journal posts, so the two processes are linked [10].
Why HMRC recognition is the floor, not the differentiator
Any payroll software that submits Real Time Information at scale has to be recognised by HMRC, so recognition is the entry ticket every serious product holds rather than a feature that sets one apart [11]. The Moonworkers payroll engine carries the HMRC Recognised status and files the Full Payment Submission automatically as part of each payrun [1].
What actually separates one payroll product from another is everything that happens around the submission: how cleanly the data flows into the accounts, how little manual entry is required, and whether the same engine can serve a single business and a multi-client bureau. For teams building their own products, that capability is exposed through an HMRC-recognised payroll API rather than locked inside a single interface, with the full endpoint set documented in the API reference.
Posting the payroll journal into Xero
Once the payrun is calculated and reported, the journal posts the figures into Xero. A well-formed payroll journal maps each payroll figure to a nominal account: gross wages to a staff-costs expense account, employer National Insurance and employer pension to their own expense accounts, and the amounts owed to HMRC and the pension provider to liability accounts that clear when the payments are made [3].
The net pay line matches the cash that leaves the business bank account, so when the bank feed in Xero shows the salary payments, they reconcile against the journal [2]. The payment to HMRC, due by the 22nd of the month electronically, clears the HMRC liability account, and the pension remittance clears the pension liability [1]. Done correctly, the ledger tells the whole story of the payrun without a single manual adjustment.
A worked payroll journal
A simple monthly payrun shows how the journal balances. Suppose total gross pay is £10,000, the tax and National Insurance deducted from staff come to £2,400, the worker pension share is £400, the employer's National Insurance is £750 and the employer pension is £400 [5]. The journal debits the expense accounts and credits the liability and bank accounts, so the entry nets to zero [3].
| Account | Debit | Credit |
|---|---|---|
| Gross wages (expense) | £10,000 | |
| Employer National Insurance (expense) | £750 | |
| Employer pension (expense) | £400 | |
| HMRC liability (tax and National Insurance) | £3,150 | |
| Pension provider liability | £800 | |
| Net pay (bank) | £7,200 |
The net pay of £7,200 is the gross figure less the £2,800 of employee deductions, and it matches the salary payments the bank feed in Xero will show [2]. When the business later pays HMRC by the 22nd of the month and remits the pension, those payments clear the liability accounts, leaving nothing stranded in the ledger [1]. The £3,150 owed to HMRC combines the tax and National Insurance covered in the Moonworkers guide to paying PAYE to HMRC.
The single most valuable part of the integration is that this mapping, from each payroll figure to the right nominal account, is defined once and then applied automatically to every payrun. An employer never has to decide afresh which account the employer National Insurance belongs in, and the same structure applies whether the payrun covers one worker or fifty [3].
What a clean integration removes
The value of a proper payroll-to-Xero integration is measured in what it removes: the re-keying of totals, the guesswork over which nominal account a figure belongs in, and the month-end hunt for the few pounds that will not reconcile. When the payroll engine generates the journal and maps it to the accounting structure automatically, the figures posted to Xero are the figures reported to HMRC, with no opportunity for a transcription error to creep in between them [3].
For accountants running payroll across many clients, this matters at scale. A multi-client payroll platform that posts a correct journal for each client turns a recurring reconciliation problem into a routine one, which is the difference between a bureau that scales and one that is capped by manual effort [2].
Payroll, accounting and Making Tax Digital
The direction of travel in UK compliance is towards digital record-keeping and submission, under HMRC's Making Tax Digital programme [12]. Payroll has reported in real time since Real Time Information went live, and the wider move to digital tax reinforces the case for payroll data that flows into the accounts automatically rather than being copied across by hand [1].
An employer keeping accounts in Xero is already working digitally, so the sensible completion of that picture is a payroll process that posts straight into the same digital ledger [3]. The year-end tasks, including sending the final payroll report and issuing P60s to staff still employed on 5 April, also depend on accurate records throughout the year, which a clean integration keeps intact [9].
Conclusion
The phrase that brings most people to this topic is really a question about connection: how to run UK payroll and have the figures appear, correctly, in the Xero accounts. The answer is that payroll and accounting remain two jobs, bridged by the payroll journal. Payroll calculates and reports pay to HMRC in real time; the journal posts the resulting wage costs and liabilities into the ledger; and a good integration makes that posting automatic and exact, so what the accounts record matches what HMRC was told.
The lesson for an employer or a bookkeeper is to judge a payroll setup not by the submission alone, which every recognised product handles, but by how little manual work sits between the payrun and a reconciled ledger. As digital tax requirements tighten, the gap between payroll and accounts is exactly the place where errors and wasted hours accumulate, and closing it with a clean, automatic journal is the most practical improvement most businesses can make to their monthly routine.
Frequently asked questions
Does payroll data post automatically into Xero?
It can, when the payroll software is set up to generate a payroll journal and map it to the accounting ledger. The journal posts gross wages, the tax and National Insurance owed to HMRC, pension liabilities and net pay to the correct nominal accounts, so the figures appear in the accounts without manual entry. The quality of the integration determines how much, if any, re-keying is left to do each month.
What is a payroll journal?
A payroll journal is the accounting entry that records a completed payrun. It posts the wage cost as an expense, the amounts owed to HMRC and pension providers as liabilities, and the net pay as the cash leaving the bank. Because the journal must reconcile against the actual payments, the figures it contains have to match the figures reported to HMRC on the Full Payment Submission exactly.
What does an employer have to report to HMRC each payday?
On or before each payday an employer sends a Full Payment Submission reporting each worker's gross pay, taxable pay, tax, National Insurance, and any student loan and pension figures. Where relevant, an Employer Payment Summary is also sent, by the 19th of the following tax month, to reclaim statutory payments or claim the Employment Allowance. These submissions tell HMRC what the business owes for the period.
Is HMRC recognition enough when choosing payroll software?
HMRC recognition is essential but not distinguishing, because every serious UK payroll product that files Real Time Information holds it. What separates products is how cleanly their data flows into accounting software, how much manual work the month-end requires, and whether the same engine can serve both a single business and a bureau managing many clients. Recognition is the floor to look past, not the feature to choose on.
Image prompt
Documentary photograph, the side profile of a UK bookkeeper at a tidy desk in a small office, two monitors softly out of focus showing a ledger and a spreadsheet, hands resting near a keyboard and a printed payroll summary, soft daylight from a large window on the right, mid-morning, palette of cool grey, navy, warm timber, an exposed brick wall behind, asymmetric composition with the subject in the right two-thirds, shot on a Sony A7 IV at 35mm f/2.8, photojournalism, gentle film grain, no AI artefacts, no warped hands, no warped text on screens (screens blurred), landscape orientation 16:9.
