Payroll software contracts should settle who does what before anyone is paid

A payroll software contract should describe the operational relationship before something goes wrong. A generic software licence rarely explains who approves data, submits reports, releases payments, handles pension files and corrects errors. Obtain English legal advice for the actual parties, service and exposure.

Identify the parties and service

Use full legal names and distinguish the software supplier, reseller, implementation partner, managed-service operator and customer. Define the product edition, employer and employee limits, PAYE schemes, tax-year support, integrations, service tasks and exclusions.

The Office of the Small Business Commissioner's Contract Guide recommends recording who is involved, what is provided, quality or conditions, duration, payment and how the arrangement ends. Its guidance is a practical prompt, not tailored legal drafting.

Allocate payroll responsibilities

State who supplies and validates inputs, approves calculations, submits to HMRC, checks acknowledgements, sends pension data, authorises payments and communicates with employees. Set deadlines for customer information and a process for late or changed data.

Do not imply that software transfers the employer's legal obligations. HMRC's running payroll guidance describes employer tasks around payday and the following tax month. A managed service can perform agreed steps while responsibility still requires careful legal allocation.

Describe service and change

Set availability measurements around critical payroll functions, scheduled maintenance, support hours, severity, escalation and recovery. Explain how tax-year releases, legal changes, integrations and unsupported operating environments are handled.

Avoid a broad right to change any term or function without notice. Define material change, customer communication, acceptance and any termination option. Record the order of precedence between order form, service terms, data-processing agreement and service levels.

Address personal data

Where a controller appoints a processor, the ICO's contracts and liabilities guidance lists required processing details and minimum terms. Cover instructions, confidentiality, security, sub-processors, rights assistance, incidents, return or deletion and audits.

Commercial confidentiality is not a replacement for data-protection terms. Test whether operational practice can deliver what the contract says.

Price, liability and payment

Define the chargeable unit, active-employee rules, extra runs, migration, support, VAT, invoices, renewal and late payment. Separate software fees from managed work.

Liability clauses need advice. The Unfair Contract Terms Act 1977 contains controls relevant to exclusions and restrictions in stated circumstances, including a reasonableness test for some terms. Applicability depends on facts and cannot be resolved by copying another supplier's cap.

Plan exit before entry

Specify termination triggers, suspension safeguards, notice, transition help, export content and format, retention, deletion and outstanding payroll responsibilities. Test a complete export with safe data.

Maintain a contract-to-control matrix linking each promise to an owner and evidence. Review it at renewal, tax-year change and every significant product update. The agreement is useful only when sales, engineering and support can perform it consistently.

Link the order form to qualification

Record the customer's employee range, pay frequencies, PAYE schemes, pension provider, integrations and planned start date. Make assumptions and exclusions visible beside the purchased service. If discovery reveals an unsupported case, change the scope or decline the order before migration.

Avoid allowing marketing copy to expand the signed service. Incorporate only identified documents and preserve the version accepted by both parties. Train sales and onboarding staff on which promises need specialist approval.

Set a dispute and correction process

Describe how a customer reports a suspected error, what information is needed, who investigates and how urgent payroll issues are escalated. Separate correction of software, customer data, HMRC reporting, pension records and payments because authority can differ.

Provide a proportionate route for complaints and disputes, including governing law and jurisdiction after legal review. Keep operational evidence such as approvals, submission responses and support records under a defensible retention schedule. A contract cannot prevent every disagreement, but it can make the facts and next action much easier to establish.