Payroll for One Employee: A Guide for Small UK Employers

Hiring one person can feel like a small administrative step. In payroll terms, it can be the moment a business becomes an employer with formal HMRC obligations, payroll records, reporting deadlines, pension duties and a more disciplined approach to bookkeeping.

That is why payroll for one employee often causes more uncertainty than larger payrolls. The amounts may be modest, but the compliance framework is broadly the same. A sole director taking a salary, a shop hiring its first assistant, a contractor bringing in office support, or a consultant employing an administrator may all face the same basic question: do I need payroll for one employee?

The short answer is: sometimes yes, sometimes not immediately. The practical answer depends on pay level, employment status, benefits, pensions, tax code issues, and whether the worker is genuinely an employee rather than self-employed. Getting that judgement right matters because PAYE is not simply a payslip exercise. It connects payroll, tax, National Insurance, workplace pensions, bookkeeping, employment records and HMRC reporting.

Why one-person payroll is not as small as it looks

A common misunderstanding is that PAYE only becomes relevant once a business has several employees. In reality, PAYE for one employee may be required as soon as the employer pays someone at or above the relevant threshold, provides taxable benefits, operates pension deductions, or needs to report pay and deductions to HMRC.

For a small employer, the difficulty is not usually technical complexity in the payroll calculation itself. The difficulty is knowing what should happen before and after the payment is made. Payroll has a sequence: registration, employee setup, tax code handling, pay calculation, Real Time Information submission, payment to HMRC, payslip issue, records, pension assessment and year-end reporting. Missing one part can create problems even if the wage amount is correct.

This is why questions such as how to do payroll for one employee or how to run a payroll for one employee are really operational questions. The employer is asking how to build a compliant process without creating unnecessary cost or administration. For employers who find that even a single payslip brings more administration than expected, specific guidance on payroll for one employee can be a useful next step.

Do you need payroll for one employee?

You may need to register as an employer and operate PAYE if you pay an employee at or above the PAYE threshold, if they have another job or receive a pension, if you provide benefits or expenses that need reporting, or if you need to make deductions through payroll. HMRC rules should always be checked against the current tax year because thresholds and reporting requirements can change.

There are situations where a very small employer may not need to register immediately. For example, if the employee is paid below the relevant threshold, has no other job, receives no benefits and no deductions apply, PAYE registration may not be required at that point. Even then, records should still be kept properly. If circumstances change, the employer may need to set up payroll later.

The mistake is treating “only one employee” as the deciding factor. It is not. The deciding factors are what is paid, how the worker is engaged, what else affects their tax position, and whether HMRC reporting obligations arise.

Employee, director, contractor or casual worker: the starting point

Before thinking about payroll software for one employee or the cheapest way to do payroll for one employee, the business needs to be clear about the status of the person being paid. Payroll is for employees and office holders such as directors. It is not normally used for genuinely self-employed suppliers, although status can be a sensitive area and should not be judged only by the wording on an invoice.

For a limited company, the first payroll is often for a director. Director payroll has its own National Insurance treatment and may be linked with dividend planning, Corporation Tax, bookkeeping and director loan account records. For an unincorporated business hiring a first member of staff, the concern may be more practical: hours, hourly rate, holiday pay, payslips, pension eligibility and payment dates.

For construction businesses, there may also be CIS considerations. A subcontractor paid under CIS is not automatically an employee, but the boundary between employment, self-employment and subcontracting should be considered carefully. A wrong assumption can affect tax, National Insurance, CIS deductions, payroll reporting and employment rights.

How to set up payroll for one employee

To set up payroll for one employee, the employer usually needs to work through several practical steps. The exact sequence can vary, but the underlying logic is consistent. Employers moving from informal payment arrangements to a structured process may also need to think about payroll setup and implementation before the first payday.

• Confirm worker status. Decide whether the person is an employee, director, office holder, casual worker or self-employed supplier.
• Register as an employer if required. HMRC registration should be completed before the first payday where PAYE reporting is needed. Employers receive PAYE and Accounts Office references after registration. Guidance on registering for PAYE is especially relevant at this stage.
• Collect employee details. This normally includes full name, address, date of birth, National Insurance number, start date and starter declaration information, often from a starter checklist or P45.
• Choose a payroll method. This may be HMRC-recognised software, commercial payroll software, online payroll, an accountant-managed payroll system, or outsourced payroll processing.
• Set the pay frequency. Monthly payroll is common for small employers, but weekly or fortnightly payroll may be appropriate in some sectors.
• Assess pension duties. Even with one employee, automatic enrolment duties can apply, depending on age and earnings.
• Run the payroll before payment. Calculate gross pay, tax, employee National Insurance, employer National Insurance, pension contributions and any other deductions.
• Submit RTI reports. A Full Payment Submission is normally sent to HMRC on or before the employee is paid.
• Pay HMRC where deductions are due. PAYE tax and National Insurance must be paid by the relevant deadline.
• Keep payroll records. Records should support payslips, submissions, payments, deductions, leave, pension assessments and year-end reporting.

That list can look disproportionate for payroll for only one employee, but most tasks become routine once the system is built properly. The first setup is where mistakes tend to occur.

Running payroll for one employee each month

After setup, running payroll for one employee is usually a short monthly process, provided the underlying data is accurate. The employer confirms the pay period, gross pay, hours if relevant, any statutory payments, pension deductions, tax code updates, benefits processed through payroll and any adjustments from previous periods.

The payroll is then calculated and the payslip is issued. The RTI submission is sent to HMRC, usually through payroll software. A Full Payment Submission, often called an FPS, reports the employee’s pay and deductions. An Employer Payment Summary, or EPS, may be needed in some situations, such as reporting certain recoveries or periods where no employees were paid. Employers who are unsure about the reporting process may need to review the practical requirements around filing for PAYE.

If PAYE tax, National Insurance or student loan deductions are due, these are paid to HMRC by the correct deadline. The payroll journal should be reflected in the bookkeeping system so wages, employer National Insurance, pension costs and liabilities are properly recorded.

This bookkeeping point is easy to overlook. Payroll processing for one employee is not complete just because the employee has been paid. The business accounts also need to show the cost and any amounts owed to HMRC or the pension provider. If the payroll figures do not reconcile with bank payments and bookkeeping records, the problem often surfaces later during accounts preparation, VAT reviews, management accounts or tax work.

The payroll decision is rarely just payroll

One-person payroll affects several parts of a UK small business. For a limited company, salary costs influence Corporation Tax calculations because properly incurred employment costs are usually recorded as business expenses. For a director-shareholder, the interaction between salary, dividends, PAYE, National Insurance and company profits needs careful handling.

For VAT-registered businesses, wages themselves are outside the scope of VAT, but payroll still affects management information and cash flow. For CIS businesses, the distinction between employees, subcontractors and office staff can influence how labour costs are reported and reviewed. For Self Assessment taxpayers, payroll income, dividends and business profits may all feed into personal tax reporting in different ways.

Companies House is not directly involved in monthly payroll submissions, but payroll records can still matter in the broader company compliance picture. Director remuneration, staff costs, liabilities and year-end balances may be reflected in statutory accounts. Poor payroll records can make the accounts process slower and increase the risk of unexplained balances.

What small employers often get wrong

The most common errors are rarely dramatic. They are ordinary administrative gaps that build up quietly.

Some employers pay the employee first and think about payroll afterwards. This can create late RTI submissions because payroll information is usually expected on or before payday. Others register for PAYE too late, misunderstand tax codes, forget pension assessment, or assume that no PAYE is due because the salary is “small”.

Another frequent issue is confusing net pay with gross pay. An employer agrees to pay someone “£1,800 a month” without clarifying whether that is before or after deductions. If the figure is intended as take-home pay, the gross payroll cost may be higher than expected once tax, National Insurance and pension deductions are calculated.

Record keeping also causes problems. A payslip may be produced, but the employer does not retain starter information, pension communications, leave records, payroll reports or evidence of HMRC payments. That makes later queries harder to answer. HMRC does not usually ask whether the payroll was small; it asks whether records support the figures submitted.

Payroll software for one employee: useful, but not a substitute for judgement

There are several ways to manage payroll for one employee UK employers can choose from. The right route depends on confidence, complexity and tolerance for administration.

Some employers look for free payroll software for one employee or search for payroll for one employee free. Free or low-cost tools may be adequate for a straightforward payroll with one employee, no complications, no benefits, simple tax code treatment and basic pension requirements. The limitation is that software follows the information entered into it. It cannot always identify whether the worker should have been treated differently, whether the payroll setup is strategically appropriate, or whether the accounting records are being posted correctly.

Commercial software may be more convenient, especially where the employer wants automatic updates, online payslips, pension integration, HMRC submissions and bookkeeping links. For some employers, the best payroll software for one employee is not the platform with the longest feature list, but the one that reduces avoidable errors and fits the business’s actual workflow. Reviewing practical payroll software options can help employers compare functionality without assuming that every small payroll needs the most advanced system.

Other employers prefer payroll services for one employee because they do not want to manage filings, deadlines, tax codes or pension administration themselves. This can be sensible where the owner’s time is more valuable elsewhere, where the employee is a director, where payroll interacts with tax planning, or where the business expects to grow.

Free, cheap or outsourced: comparing the real trade-offs

Searches for the cheapest payroll for one employee, cheap payroll for one employee or the cheapest way to do payroll for one employee are understandable. A small employer does not want a large administrative cost for one wage. But the cheapest option is only cheap if it is used correctly.

A free payroll route can work for a simple case, but it may demand more time from the employer. The owner must understand payroll deadlines, submit reports, deal with tax codes, keep records, monitor pension duties and reconcile the bookkeeping. If the employer is organised and the payroll is uncomplicated, that may be a fair trade-off.

Low-cost software can make the process easier, especially if it provides online payroll for one employee with HMRC submissions and payslips. The employer still needs to know what to enter and when to act.

Outsourced payroll usually costs more than doing it yourself, but it can reduce administrative risk and save time. The payroll service for one employee cost varies depending on frequency, pension work, director payroll, reporting requirements and whether bookkeeping support is included. A simple monthly payroll may be inexpensive; a payroll involving corrections, late setup, irregular pay, pension duties or benefits may cost more.

The better question is not simply how much does payroll cost for one employee. It is what the business is buying: software access, calculation support, filing responsibility, payroll advice, pension administration, bookkeeping integration, or a fully managed process.

A simple payroll can still become complicated

A one-person payroll may begin simply and become less straightforward over time. The employee may receive a pay rise, switch hours, receive statutory sick pay, go on maternity or paternity leave, join or opt out of a pension scheme, receive benefits, have a student loan deduction, change tax code, or leave part-way through the tax year.

Each event has a payroll consequence. Some also have employment record or bookkeeping consequences. A final salary payment may require a leaving date and P45. A pension opt-out must be handled in line with scheme rules. A tax code notice from HMRC must be applied correctly. A late correction may require an amended payroll submission.

This is where the phrase simple payroll for one employee can be misleading. The payroll is simple only while the facts remain simple. A robust process should be able to cope when the first exception appears.

PAYE registration and timing

If PAYE registration is required, timing matters. Employers should allow enough time to register before the first payroll submission is due. HMRC references are needed to submit PAYE information and pay liabilities correctly.

Leaving registration until after the employee has already been paid can create unnecessary pressure. It may still be possible to regularise matters, but the employer can end up dealing with late submissions, unclear payment references, or a mismatch between payroll dates and HMRC records.

For a new limited company, payroll setup should also be considered alongside company formation, bookkeeping setup and director remuneration planning. For an existing business, the first employee should prompt a review of processes that may previously have been informal: approving payments, storing records, tracking working hours, and separating wages from drawings or personal transfers.

Pensions are not optional just because there is one employee

Automatic enrolment duties can apply even where there is only one employee. The employer must assess the worker, understand whether they are an eligible jobholder, non-eligible jobholder or entitled worker, and deal with communications and enrolment where required.

Some one-person payrolls do not result in pension contributions because of age, earnings or director-only arrangements. But that conclusion should come from assessment, not assumption. Pension duties are often missed by small employers because they think of pensions as a larger workforce issue. The Pensions Regulator expects employers to understand their duties regardless of size. Where pension duties are likely to apply, pension scheme setup and management should be considered alongside payroll configuration.

Pension administration also affects payroll calculations and cash flow. Employee contributions, employer contributions and pension provider payments need to be processed and recorded accurately.

The hidden link between payroll and bookkeeping

Payroll errors often appear as bookkeeping problems before they are recognised as payroll problems. For example, the bank shows a payment to the employee, but the payroll report shows a different net pay figure. HMRC payments are made, but the PAYE liability account does not clear. Pension deductions are taken, but no matching pension payment is recorded. A director’s salary is processed, but payments are posted to the director’s loan account instead of wages.

These issues matter because they affect the accounts. They can distort profit, liabilities, staff costs and cash flow reporting. They may also complicate VAT reviews, management accounts, Corporation Tax computations and year-end reconciliations.

For a payroll for small business with one employee, the cleanest approach is usually to decide from the start how payroll reports will be posted into the bookkeeping system. That does not need to be elaborate, but it should be consistent.

Choosing the best way to do payroll for one employee

The best way to do payroll for one employee depends on the employer’s situation. A straightforward case might be handled internally with suitable software. A director payroll may benefit from professional input because payroll interacts with dividends, company tax, personal tax and year-end accounts. A growing business may prefer an outsourced payroll model from the beginning to avoid rebuilding the process later.

It helps to ask practical questions before choosing a payroll system for one employee:

• Is the employee paid a fixed salary or variable hours?
• Will pension assessment and contributions be needed?
• Is the employee a director or ordinary employee?
• Are benefits, expenses, bonuses, commissions or statutory payments likely?
• Will payroll data need to connect with bookkeeping software?
• Who will monitor HMRC notices and tax code changes?
• Who is responsible if an RTI submission is late or incorrect?
• Will the business hire more staff in the next 12 to 24 months?

These questions are more useful than searching only for the easiest way to do payroll for one employee. Ease depends on fit. A tool that is easy for one employer may create confusion for another if it does not match their records, pay frequency or accounting process.

What the monthly workflow should look like

A well-run one-person payroll usually follows a predictable rhythm. Before the pay date, the employer confirms the salary or hours, checks any changes, reviews tax code notices, calculates payroll and approves the payslip. On or before the payment date, the RTI submission is made. The employee is paid the net amount. HMRC and pension liabilities are then paid by their deadlines. The payroll records are filed and the bookkeeping entries are posted.

For a very small employer, this may take little time. The value is in consistency. A monthly payroll process that happens the same way each time is easier to review, easier to correct and easier to hand over if the business later appoints an accountant or payroll provider. Employers who want the cycle handled consistently may find that monthly payroll support fits better than ad hoc help after problems have already appeared.

Problems arise when payroll is treated as an afterthought. If the owner pays wages manually, updates the payroll later, forgets the pension assessment and leaves bookkeeping until year end, small discrepancies can turn into time-consuming clean-up work.

Cost of payroll for one employee: what affects the price

The payroll cost for one employee can range from no direct software fee to a monthly professional service fee. The difference usually reflects responsibility and support rather than the number of payslips alone.

Cost may be affected by:

• monthly, weekly or irregular pay frequency;
• director payroll treatment;
• pension scheme setup and ongoing pension submissions;
• tax code changes, student loans or attachment of earnings orders;
• statutory sick pay, maternity pay or other statutory payments;
• benefits processed through payroll;
• bookkeeping integration and payroll journals;
• corrections to previous payroll periods;
• year-end reporting and employee leaving processes.

If the payroll is genuinely simple, paying a large fee may be unnecessary. If the payroll touches wider tax planning, pension duties or messy bookkeeping, choosing purely on price can be false economy.

One employee today, a payroll system tomorrow

The first employee is often a signal that the business is becoming more structured. Even if the current payroll is small, the employer may later add staff, introduce bonuses, change working patterns, offer benefits or need clearer management accounts. A payroll process that works only because the owner remembers everything personally may not scale well.

That does not mean a small employer needs an enterprise payroll system. It means the payroll setup should be clean enough to grow. Employee records should be complete. Pay dates should be consistent. HMRC submissions should be traceable. Pension duties should be documented. Payroll reports should reconcile with accounts.

Good payroll habits formed at one employee usually prevent larger problems when the second or third employee joins.

Practical takeaways for small UK employers

Payroll for one employee is not about creating unnecessary administration. It is about recognising the point at which informal payments become formal employer responsibilities.

• One employee can still trigger PAYE. The number of employees is not the deciding factor; pay, status, benefits and reporting duties are.
• Payroll should be set up before payday where possible. RTI reporting normally happens on or before payment.
• FPS and EPS reporting should be understood. A Full Payment Submission is part of the normal payroll cycle, while an Employer Payment Summary may be relevant in specific situations.
• Software helps, but setup judgement matters. The employer still needs accurate worker details, tax treatment and pension assessment.
• Pension duties should be checked early. Automatic enrolment can apply even to a small employer.
• Bookkeeping should not be separate from payroll. Payroll costs, HMRC liabilities and pension deductions should reconcile with the accounts.
• Cheap is not always lowest-risk. The right payroll option depends on complexity, time, confidence and future growth.

A measured view on payroll for one employee

Doing payroll for one employee does not need to be burdensome, but it should be treated with the same discipline as any other employer obligation. The practical challenge is to avoid both extremes: overcomplicating a simple payroll, and underestimating the compliance framework because there is only one person on the payroll.

For some employers, a free or low-cost payroll option will be perfectly adequate. For others, especially directors, growing companies or businesses with pension and bookkeeping complexities, professional payroll processing may be the more reliable route. The right answer is not universal. It depends on the facts, the employer’s confidence and the importance of getting the surrounding tax and accounting records right from the beginning.

The first payroll often sets the tone for how a business handles employment administration. If it is built carefully, payroll for one employee can remain simple, compliant and easy to manage. If it is improvised, the smallest payroll in the business can become one of the most awkward records to untangle later.