Earned-wage access without a payroll migration

Most earned-wage access (EWA) projects stall in the same place: the moment someone asks what it does to payroll. The fear is reasonable. Payroll is the one process no employer can afford to break, and swapping providers or rebuilding a working setup to bolt on a benefit is rarely worth it.

The good news is that adding EWA does not have to touch your payroll provider at all. Done properly, it sits on top of the payroll and rota systems you already run, reads from them, and writes a single recovery back at the next run. This guide walks through how that works, what UK law and HMRC rules require at each step, and how to plan a rollout your payroll team will actually sign off. If you are still at the stage of establishing what earned-wage access is and where UK regulators stand on it, start there instead.

The quick answer

UK employers can add earned-wage access without changing payroll provider. A layered EWA product reads earned hours from the existing rota or payroll systems, pays capped advances by Faster Payments, and recovers each advance at the normal payroll run. Since 6 April 2024, HMRC rules (SI 2024/305) let a qualifying advance be reported on the normal payday Full Payment Submission rather than in a separate submission, and recovery of a genuine, documented wage advance does not reduce pay for National Minimum Wage purposes. The realistic work is integration testing, written deduction consent, staff communications and a legal review, not a systems migration.

Why rollouts stall: migration versus layering

The usual blocker is migration. Some EWA products only work if you move onto their payroll or HR stack, which turns a benefit decision into a systems-replacement project. That is worth discovering in the first call rather than the last.

There are three broad ways an EWA product attaches to an employer. It can be built natively into a payroll platform, which means a payroll migration unless you are already on it. It can integrate with your existing payroll and rota systems by API, SFTP or CSV file exchange. Or it can route net pay through a provider-arranged account, an “intercept” model where the provider holds the wages and forwards the balance after deducting advances. Only the first forces you to change payroll. But “no payroll migration” never means “no implementation work”: identifiers, earnings feeds, cut-offs, leaver handling and reconciliation still have to be configured and tested. The way to avoid the migration without kidding yourself about the diligence is to choose a model that layers rather than replaces, and to know which of the three you are buying. To see the employer-side picture in full, read how Wagecrew works for employers.

HMRC already supports this: the April 2024 RTI rule

The single most important thing to know is that HMRC changed the rules in your favour. Since 6 April 2024, under the Income Tax (PAYE) (Amendment) Regulations 2024 (SI 2024/305, inserting regulation 67BD), a qualifying salary advance and the reduced regular payment that follows are treated as a single payment, reported on one Full Payment Submission on the normal payday. No extra FPS per advance. The National Insurance mirror is SI 2024/306, and HMRC’s manual (NIM11521, updated 22 July 2026) confirms the rule remains current.

The easement applies only where three conditions hold: salary is ordinarily paid at regular intervals of between a week and a month; the advance reasonably represents work already undertaken, with no other payment made for that work; and the next regular payment is reduced by the amount of the advance (HMRC PAYE72053). Two consequences follow for a buyer. Even where a third-party provider makes the advance on the employer’s behalf, the RTI reporting obligation stays with the employer, so the incumbent payroll or bureau keeps producing and sending the FPS. And HMRC has said the operation of commercial salary-advance schemes falls outside its remit, so the reporting easement is not an endorsement of any model. It removes a reporting headache; it does not vouch for a provider.

Lawful recovery: consent before the first advance

Recovery is a deduction from wages, and UK law is specific about deductions. Under section 13 of the Employment Rights Act 1996, an employer may only deduct from a worker’s wages where the deduction is required or authorised by statute, authorised by a relevant provision of the worker’s contract, or the worker has previously agreed to it in writing. For a contractual term to authorise an EWA recovery, the employer must, before making the deduction, have given the worker a written copy of the term or notified them of its existence and effect, and consent cannot authorise a deduction for something that happened before the consent was signified. In practice the deduction wording and written consent should be in place before any advance is made.

Do not lean on the overpayment exception. Section 14 takes overpayments of wages outside the section 13 protections, but an EWA advance is a planned advance rather than an overpayment, so recovery should rest on an express contract term or prior written consent, and shortfalls should not be relabelled “overpayments”. And the recovery has to show up properly: section 8 gives workers the right to an itemised pay statement showing the amount and purpose of each deduction, and (where pay varies by time worked) the total hours worked, the hours requirement added by SI 2018/147 and the extension of payslip rights to all workers by SI 2018/529, both from 6 April 2019. In a deduction-model EWA the recovery appears as a labelled deduction line on the payslip.

The National Minimum Wage check payroll must run

This is the compliance point most likely to bite a wage-floor employer. Regulation 12(2) of the National Minimum Wage Regulations 2015 expressly excepts “deductions, or payments, on account of an advance under an agreement for a loan or an advance of wages”, so a properly structured, documented EWA recovery does not reduce pay for NMW purposes. HMRC’s manual backs this up: an advance is not counted towards NMW pay when paid (NMWM09210), and its recovery does not reduce NMW pay (NMWM11150), but only where the arrangement is genuine and documented, the money must be cash the worker is free to spend, the worker must not be required to take it, and pay records must show they received it.

The exception does not cover fees. Deductions for the employer’s own use and benefit reduce NMW pay regardless of profit or worker agreement (NMWM11020), and HMRC says an administration charge for handling a transaction always reduces NMW pay (NMWM11050). CWG2 tells employers to account for NMW obligations where advances involve fees. The safe pattern, and the one to insist a provider supports, is to recover only the advance principal through payroll; any worker-paid fee should be kept out of the payroll run and assessed on its own NMW merits rather than assumed to be neutral. This is also why the FCA has pointed to models where the employee pays no fees and the employer bears the cost. It is worth getting right: NMW underpayment penalties run up to 200% of arrears, capped at £20,000 per worker (halved if paid within 14 days), and arrears must be repaid at current minimum-wage rates where higher (DBT guidance, updated 6 January 2026), so a late-discovered shortfall grows with each April uprating.

The rails: Faster Payments out, Bacs back

Two payment systems do different jobs here, and it helps to keep them straight. Faster Payments is the rail for on-demand disbursement: payments can be initiated 24 hours a day, funds are usually available almost immediately though a payment can sometimes take up to two hours, the scheme limit is £1 million per payment (raised from £250,000, announced by Pay.UK on 10 February 2022, with individual banks free to set lower limits), and a Faster Payment cannot normally be cancelled once sent. Bacs is the bulk payroll rail: it runs on a fixed three-working-day cycle, uses the Bacs Standard 18 file format, and on input day files transmit between 07:00 and 22:00 with the session closing around 22:30, though cut-offs vary by submission route and sponsor bank. Bacs typically carries the normal payday run and any bulk settlement back to the provider; it cannot do real-time EWA disbursement. Wagecrew pays each draw by Faster Payments, typically within seconds, to the worker’s own bank account, and recovers through the normal payroll run.

For that to work, the EWA layer needs two feeds and one write-back: a source of earned hours, a way to move money to the worker, and a recovery line that reconciles against the payslip. Do not simply hand over an FPS-shaped dataset: the FPS carries extensive per-employee data (taxable pay, tax, NI, student loan, tax code, payroll ID, an hours band), and data minimisation applies, so the provider should receive only the narrow fields, or a pre-computed available amount, it actually needs. Wagecrew connects to Ubeya timesheets for earned-hours data, FreshPay FPS payroll, Bacs Standard 18, and Xero; the full connector list sits on our payroll and rota integrations page.

What happens on payday: deduction order and edge cases

On payday the EWA recovery sits last in the queue. PAYE, NI and pension come first, then statutory attachments: a DWP Direct Earnings Attachment is calculated on net earnings and must leave the worker with at least 60% of them, and a priority attachment must leave the protected earnings rate in the order. A contractual EWA recovery cannot displace any of these and is taken from whatever net pay remains.

Three edge cases decide whether the model is safe or a liability, and they are contract-level because no statute or code settles them. First, insufficient net pay: if the recovery cannot be taken and rolls to a later period, the next regular payment was not “reduced by the amount of the advance”, so on a strict reading the single-FPS condition fails for that advance and per-advance reporting revives, which is why providers cap advances at a share of accrued earned pay and freeze drawdowns before cut-off so the payday payment can always absorb the recovery. Second, statutory-pay periods: deductions can be made from Statutory Sick Pay and family payments (HMRC SPM182400), but a prudent availability engine treats statutory leave, unpaid leave and irregular final-pay periods carefully because no new worked earnings accrue; and keep the codes separate from the retail-worker 10%-of-gross cap on cash-shortage deductions, which is a different rule. Third, leavers: the standard mechanism is recovering the outstanding balance from final pay where there is a contractual basis (Acas says final pay should normally be paid on the usual payday with each deduction explained), but the scheme should freeze access on a leaver signal and not assume final pay will always cover the balance. Wagecrew handles the recovery side with the Payroll Verifier, a pre-approval check that reads the payroll bureau’s FPS file and scores every worker before any advance is approved, so nothing is paid out that cannot be cleanly recovered.

Where the wages sit, and why it matters

If a provider uses the intercept model, it holds workers’ net wages in transit, and that changes your risk. Money held at a non-bank payment or e-money firm is not protected by the Financial Services Compensation Scheme. Such firms must safeguard customer money by segregation or insurance, but small payment institutions do not have to safeguard at all, so check the provider’s exact permission on the FCA’s Financial Services Register. FCA analysis in CP24/20 (September 2024) found that payments and e-money firms which failed between 2018 and 2023 left an average shortfall of 65% in client funds owed; the FCA’s PS25/12 (August 2025) brings tighter safeguarding rules from 7 May 2026. And the wage obligation does not disappear when wages are routed through a provider: under ERA 1996 section 13(3), where wages paid on any occasion fall short of what is properly payable, the deficiency is treated as a deduction made by the employer, so if an intercept provider fails while holding a pay run, the shortfall can leave the employer exposed as if it had made an unauthorised deduction, whatever it had funded. With an employer-funded layered model, there is no third party holding the wages in the first place, which is the cleanest answer to this whole class of risk.

A rollout sequence payroll will sign off

A layered rollout is a defined piece of work: integration checks, staff communications and a legal review, not a systems migration. In rough order:

1. Confirm the earned-hours source. Point the EWA layer at your existing rota or timesheet system and check the earned figures match.
2. Get the deduction basis right first. Put the written consent or contract term in place before any advance is made, and decide the withdrawal cap, the minimum draw and eligibility (both the cap and the minimum are yours to configure).
3. Confirm the payout route. Each draw is paid by Faster Payments to the worker’s own bank account.
4. Wire up recovery and test it. Run the reconciliation step against a real FPS file so recovery is validated before go-live, and check the payslip shows a clean, labelled deduction line.
5. Pilot with a comparison group, not just an adoption number. Watch reconciliation and query rates, not take-up alone.
6. Communicate to staff. Give workers a plain explanation of the cap, the minimum, how recovery appears on their payslip, and that it is their own earned pay with no fee.

None of these changes your payroll provider or your pay calendar. The heaviest lift is the first-time integration check; after that the layer runs alongside payroll rather than inside it.

Choosing a provider without a migration

The due-diligence that makes a no-migration model real is the same checklist you would run on any payroll-adjacent vendor: how each advance is funded and who bears the loss if a worker leaves mid-cycle; the provider’s exact FCA register entry and safeguarding status if it holds money; whether it has signed the CIPP Earned Wage Access Code of Practice and when it was last independently assessed; and the categorical fee question, is there any cost to the worker on any path. We set those out in full in questions to ask an earned-wage access provider, and the no-worker-fee model that addresses the FCA’s fee warning is explained on free earned-wage access. For a like-for-like view of the field, see the UK earned-wage access provider comparison.

Frequently asked questions

Do we have to change payroll provider to add earned-wage access?

No, if you choose a layered model. The EWA product should read earned pay from your existing rota and payroll systems, send capped advances to workers, and recover them at your normal run. Wagecrew connects to systems including Ubeya, FreshPay FPS, Bacs Standard 18 and Xero, so payroll stays where it is. A payroll-native product, by contrast, can require you to move onto its stack, which is a migration and belongs in the comparison.

How are salary advances reported to HMRC under RTI?

Since 6 April 2024 (SI 2024/305), a qualifying advance and the reduced regular payment are reported on one Full Payment Submission on the normal payday, not one FPS per advance, provided pay is at regular weekly-to-monthly intervals, the advance represents work already done, and the payday payment is reduced by the advance. The National Insurance rule mirrors it (SI 2024/306). The reporting duty stays with the employer even where a third party makes the advance.

Does recovering an advance on payday breach National Minimum Wage rules?

Not if it is done properly. Regulation 12 of the National Minimum Wage Regulations 2015 excepts a genuine, documented advance of wages from the deductions that reduce NMW pay, and HMRC’s manual confirms it, provided the worker was free to spend the money, was not required to take it, and the records show it. Fees are different: a charge for the employer’s own use and benefit does reduce NMW pay, so recover only the advance principal through payroll and check the NMW treatment of any worker-paid fee separately rather than assuming it is neutral.

What written agreement do we need before deducting an advance from wages?

Under section 13 of the Employment Rights Act 1996, either a relevant contractual term the worker has been given in writing before the deduction, or the worker’s prior written consent. Consent cannot authorise a deduction for something that already happened, so put the deduction basis in place before the first advance. The recovery must then appear as an itemised deduction line on the payslip under section 8.

What happens if a worker leaves with an advance outstanding?

The scheme should freeze access on the leaver signal and recover the outstanding balance from final pay where there is a contractual basis, with the payslip explaining the deduction. Because final pay does not always cover the balance, a well-designed model caps advances against accrued earned pay so exposure stays small, and who absorbs any unrecovered amount is a contract point to settle in writing before you sign.

Is earned-wage access regulated by the FCA?

Usually not, but the position is structure-dependent. Where the advance is provided by the employer, the scheme does not usually involve the provision of credit and so generally falls outside FCA credit regulation, which means consumer-credit protections and the Financial Ombudsman route do not apply. It is not a permanent carve-out, and no employer-funded EWA scheme should be described as “FCA regulated” or “FCA approved”.

Further reading and sources

• Income Tax (PAYE) (Amendment) Regulations 2024 (SI 2024/305) and HMRC PAYE Manual PAYE72053: the single-FPS reporting rule and its conditions.
• Employment Rights Act 1996, s13 and Acas guidance on deductions from wages: lawful recovery.
• HMRC NMW Manual NMWM11150 and NMW Regulations 2015, reg 12: the advance-recovery exception.
• Pay.UK, how Faster Payments work and Bacs glossary (Standard 18): the payment rails.

To see the full connector list, read our payroll and rota integrations page, and for the wider case read earned-wage access for employers.