The operating model to specify before a contract starts
Pearl Lemon Accountants contracts and coordinates the engagement; suitably approved payroll specialists carry out the processing activities assigned in the signed scope. We verify capacity, systems and service levels for each project before employee data is collected. A prospective engagement should convert each stage into a written scope, evidence checklist and named operational owner.
1. Qualification: understand the payroll you already have
The first discussion should establish employees paid each period, pay frequencies, PAYE entities, variable payments, pensions, HR/time-record systems, a current example of the output you need, major exceptions and target start date. No sensitive employee file is necessary for this first conversation.
Output: a short scope summary identifying supported payroll types, known exclusions and commercial assumptions. A fit decision at this stage is more valuable than an immediate sales promise.
2. A responsibility matrix and data-processing agreement
Every critical operation needs one accountable approver and one named processor. Separate data preparation from calculations; separate calculations from payment release. Confirm whether statutory filing, pension submissions, employee queries and payroll journal production are included.
Output: signed statement of work, pay calendar, contact/escalation matrix and appropriate data-processing agreement before any employee records are transferred. See ICO processor contract guidance.
3. Onboarding and first-run control
The process should include securely collected master data, validated payroll identifiers, agreed opening balances, pension configuration and—where appropriate—year-to-date reconciliation. Risk-based parallel checking is particularly useful mid-year or when there are multiple schedules.
Output: signed migration checklist, unresolved-issue log and a clear decision on whether to go live. Our switching guide covers the individual work items.
4. Routine cycle: prepare, process, check, approve
Rather than passing spreadsheets back and forth indefinitely, define a timetable for receiving approved changes, raising clarifications, preparing draft reports, employer review, final approval, filing and handoff. The employer should know what happens if a manager misses the cut-off.
Output: a review pack showing major variances, exceptions, payroll totals and confirmation of approved instructions. Keep evidence that the approval occurred before the relevant action.
5. Exceptions, incidents and continuity
Define scenarios before they happen: absent approver, late time records, disputed net pay, pension feed failure, software outage, incorrect employee details and data incident. Set the severity, escalation route, response windows and correction authority appropriate to the engagement.
Output: an issue log with ownership, actions, resolution and necessary statutory corrections. Do not describe a support mailbox as a business-continuity plan.
6. Monthly review and exit readiness
Compare the number of late changes, corrections, unresolved queries and service deviations, then improve the data handoff. Make sure historical payroll files can be returned securely in a documented format at contract end. A sticky relationship should come from service quality, not trapped records.
To discuss a scope, send a non-sensitive summary of your payroll including headcount, frequencies, timing and the most frustrating part of your current process.