In 2022 the Financial Conduct Authority concluded that giving employees access to wages they have already earned does not constitute consumer credit, which opened the door for platforms to build wage-access products on top of payroll data [1]. With around 30.3 million people paid through PAYE in June 2026, each producing a stream of verified earnings data on every pay run, payroll has become one of the richest foundations for embedded finance in the UK [2]. Payroll embedded finance is the term for financial services built directly into a payroll flow.
Embedded finance is the integration of financial services into non-financial platforms, so a business can offer payments, wallets, lending or wage access inside its own product without becoming a bank. Applied to payroll, it means an HR platform, a workforce app or a vertical software product can deliver pay, wage advances and pay-linked financial products natively, rather than sending users to a separate provider. Underneath all of it sits a compliant payroll engine that calculates accurate net pay and files with HMRC.
This article explains what payroll embedded finance is, the layers it is built from, the statutory foundation every layer depends on, and why an accurate, HMRC-recognised payroll engine is the component that makes the rest possible. It is written for product leaders, fintech builders and platform teams evaluating embedded payroll and pay-linked finance.
Key takeaways
- Payroll embedded finance builds financial services (wage payments, earned wage access, pay-linked products) into a platform's own product on top of payroll data [1].
- Every layer depends on an accurate payroll calculation, because net pay, deductions and earned-to-date figures are only trustworthy if the underlying engine is correct [3].
- The FCA found in 2022 that access to already-earned wages is generally not consumer credit, though how a scheme is structured can change that [1].
- A salary advance is a payment on account of earnings and remains fully taxable through PAYE, with simplified RTI reporting from 6 April 2024 [7][3].
- Only HMRC-recognised software can submit Real Time Information, so the payroll engine at the base of the stack must carry that recognition [4].
What payroll embedded finance means
Embedded finance moves financial services out of dedicated financial institutions and into the products people already use. A platform integrates payments, accounts, cards, lending or wage access through an API, and offers those capabilities to its users without holding a banking licence or building financial infrastructure from scratch. The user stays inside the host product; the financial plumbing runs behind the scenes.
Payroll is a natural home for this, because a pay run generates exactly the data that pay-linked finance needs: who is employed, what they earn, what they have earned so far in the period, and what reaches their bank account after tax. A platform that already runs or reads payroll can offer wage payments, wage advances and financial wellbeing products as native features. The key is that the numbers have to be right, because a wage-access product that advances money against an inaccurate net pay figure exposes both the platform and the employee to risk [3].
This is why payroll embedded finance is not simply a payments feature bolted onto an app. It is a stack, and the layers only work if the bottom one, the compliant payroll calculation, is accurate. An overview of what a payroll API is and how it works sets out how that base layer is exposed to the platforms built on top of it.
The layers of the stack
Payroll embedded finance is best understood as a set of layers, each depending on the one below. A platform can enter at any layer, but none of the upper layers is trustworthy without the base.
| Layer | What it delivers | What it depends on |
|---|---|---|
| Payroll engine | Compliant gross-to-net calculation and RTI filing | HMRC recognition |
| Wage payments | Paying net wages into employee accounts | Accurate net pay from the engine |
| Earned wage access | Advancing a portion of already-earned pay | Verified earned-to-date figures |
| Pay-linked products | Savings, benefits, financial wellbeing tools | Consented access to pay data |
The base layer is the payroll engine. Every layer above it consumes figures the engine produces, so the accuracy and compliance of that engine determine whether the whole stack can be trusted [4]. That trust is anchored in the Real Time Information submission, filed on or before payday, which is the point at which the pay data becomes official [3].
Why accurate pay data is the foundation
The value of embedded finance in payroll comes from the quality of the underlying data. An earned wage access product advances money against wages an employee has already earned, so it needs a reliable earned-to-date figure, which only a correct payroll calculation can provide [1]. A wage payment has to move the exact net figure after PAYE, National Insurance, student loans and pension deductions, which again comes from the engine [6].
If the base calculation is wrong, every product built on it inherits the error. An advance against an overstated earned figure can leave an employee with a shortfall at payday; a wage payment based on an incorrect net figure creates a reconciliation problem for the employer. This is the practical reason the payroll engine, not the payments rail, is the component that decides whether payroll embedded finance is safe to offer. The engine must apply the full statutory calculation correctly on every run, and that is a compliance task, not a payments one [3].
The statutory foundation every layer depends on
Because the whole stack rests on the payroll calculation, the platform building embedded finance has to understand what that calculation involves. The engine must apply the complete UK statutory surface, current for the 2026-27 tax year, before any figure it produces can be used to move money.
The core obligations are the same ones any UK payroll must meet.
| Obligation | What the engine must do |
|---|---|
| PAYE income tax | Apply three regimes: England and Northern Ireland, Scotland, Wales |
| National Insurance | Apply every category letter and the correct rates |
| Student loans | Deduct across Plans 1 to 5 plus postgraduate loans |
| Auto-enrolment | Assess pension duties and calculate contributions on every run |
| RTI filing | Submit the Full Payment Submission on or before payday |
| Payslips | Produce an itemised pay statement for every worker |
Each of these feeds the net pay figure that embedded finance products move, so each has to be correct.
PAYE, National Insurance and net pay
Net pay is what most embedded finance products actually move, and it is the output of several stacked calculations. Income tax applies across three regimes: England and Northern Ireland use a basic rate of 20% up to £50,270, a higher rate of 40% up to £125,140 and an additional rate of 45% above that, all above a £12,570 Personal Allowance [5]. Scotland operates six bands with a lower higher-rate threshold and an `S` tax code prefix, so the engine cannot treat it as a variation on the English tables [10].
National Insurance is deducted separately. Employees pay 8% between the £12,570 Primary Threshold and the £50,270 Upper Earnings Limit, then 2% above, while employers pay 15% above the £5,000 Secondary Threshold for the 2026-27 tax year [6]. The employee's category letter decides which rates apply, and the engine must apply the right one on every run [13]. Only after income tax, National Insurance, student loans and pension contributions are deducted does the engine produce the net figure an embedded finance product can safely move, and every worker is entitled to an itemised statement showing each of those lines [8].
Auto-enrolment and RTI
Pension deductions change the net figure, so auto-enrolment is part of the foundation too. For the 2026-27 tax year, auto-enrolment uses a £10,000 earnings trigger and a qualifying earnings band of £6,240 to £50,270, with a minimum total contribution of 8%, assessed on every pay run [12][9]. A platform that reads pay data has to account for the pension deduction to know the employee's true take-home.
Every pay run also ends with a Full Payment Submission to HMRC, filed on or before payday under Real Time Information, and late or incorrect submissions can trigger automatic penalties [3][11]. This RTI event is the moment the pay data becomes official, and only HMRC-recognised software can file it, which is why recognition is the non-negotiable floor for the engine at the base of any embedded finance stack [4]. A platform embedding payroll through an HMRC-recognised payroll API inherits that recognition rather than building it.
Earned wage access and salary advances
The most visible payroll embedded finance product is earned wage access, sometimes called an employer salary advance scheme. It lets an employee draw a portion of pay they have already earned before the normal payday, using verified earnings data shared with consent. Its growth is what made the FCA's regulatory view so significant.
In 2022 the FCA concluded that schemes providing access to already-earned wages generally do not constitute consumer credit and fall outside consumer credit regulation, though it warned that the way a scheme is structured can bring it inside regulated activity, so providers should consider their design carefully [1]. This matters for any platform building the feature, because the regulatory treatment depends on the mechanics, not the label.
How a salary advance is taxed
A salary advance is not tax-free money. HMRC treats an advance as a payment on account of earnings, so it remains fully subject to income tax and National Insurance through PAYE in the normal way [7]. The employee receives part of their pay early, and the tax position follows the earnings, not the timing of the transfer.
The reporting was simplified from 6 April 2024. Where the conditions apply, an employer no longer files a separate RTI report for the advance and instead reports it on the normal payday alongside the rest of that period's pay, so only one Full Payment Submission is expected for each pay period [3][7]. A platform offering wage access has to reflect this in how it interacts with the payroll engine, so the advance and the final pay reconcile correctly on the FPS.
Comparing the two mechanisms
Earned wage access and a traditional salary advance are related but not identical, and the distinction matters for how a platform designs the product.
| Feature | Earned wage access | Traditional salary advance |
|---|---|---|
| Basis | Pay already earned to date | Advance against future pay |
| Regulatory view | Generally outside consumer credit | Depends on structure |
| Tax treatment | Taxed through PAYE at payday | Taxed through PAYE as payment on account |
| Data needed | Verified earned-to-date figure | Employer authorisation and net pay |
Both mechanisms are taxed through PAYE, and both depend on accurate figures from the payroll engine, which is why a platform building either one starts with the engine, not the payment [7]. The regulatory treatment also turns on the design of the scheme rather than its label, so the mechanics decide whether it stays outside consumer credit [1]. The UK payroll API technical guide covers how those earned and net figures are calculated in detail.
Building payroll embedded finance on an engine
For a platform, the practical route into payroll embedded finance is to embed a compliant payroll engine and build financial products on the data it produces. The engine calculates gross-to-net, files the RTI submission and exposes the results through an API, and the platform reads earned-to-date and net figures to power wage payments, wage access or pay-linked products, all inside its own interface.
This separation of concerns is what makes the model workable. The platform owns the user experience and the financial product; the engine owns the compliance calculation and the HMRC filing. A well-documented API with a sandbox environment and public API documentation lets the platform's engineers build against the engine and test the flows before going live. Because the cost of the engine is usually charged per payslip, the per-payslip pricing scales with payroll activity rather than a fixed licence, which suits a platform whose usage grows with its user base.
The alternative, building the payroll engine in-house, means taking on the full statutory rulebook and passing HMRC recognition before a single wage-access product can launch [4]. For most platforms, payroll compliance is not the differentiator; the embedded financial product is. Consuming the engine through an API keeps the platform focused on the product while the compliance plumbing runs underneath, whether the payroll is for a single employer or a multi-client payroll dashboard serving many.
Conclusion
Payroll embedded finance is a stack, and its stability depends entirely on the layer at the bottom. Wage payments, earned wage access and pay-linked products all move money against figures the payroll engine produces, so an inaccurate or non-compliant calculation undermines everything built above it. The regulatory ground has been laid, with the FCA's view on already-earned wages and HMRC's simplified reporting of advances, but none of the products work without a payroll engine that calculates the numbers correctly and files them with HMRC.
The direction of travel is towards more financial services being delivered inside the platforms people already use for work, rather than through separate providers. As that trend continues, the compliant, HMRC-recognised payroll engine, exposed through a documented API, becomes the foundation on which pay-linked finance is built. For a platform, the strategic question is not whether to offer embedded finance, but whether to build the payroll engine underneath it or embed one that is already compliant.
Frequently asked questions
What is payroll embedded finance?
Payroll embedded finance is the integration of financial services, such as wage payments, earned wage access and pay-linked products, directly into a platform's own product on top of payroll data. It lets an HR platform, workforce app or vertical software product offer pay-related financial features natively rather than sending users to a separate provider [1]. Underneath it sits a compliant payroll engine that calculates net pay and files with HMRC.
Is earned wage access regulated in the UK?
In 2022 the Financial Conduct Authority concluded that schemes giving access to already-earned wages generally do not constitute consumer credit and fall outside consumer credit regulation [1]. The FCA warned that how a scheme is structured can bring it within regulated activity, so providers should consider their design carefully and seek advice where needed.
How is a salary advance taxed in the UK?
HMRC treats a salary advance as a payment on account of earnings, so it is fully subject to income tax and National Insurance through PAYE in the normal way [7]. From 6 April 2024, where the conditions apply, the advance is reported on the normal payday rather than separately, so only one Full Payment Submission is expected for each pay period [3].
Does a platform need HMRC-recognised software to embed payroll?
The payroll engine that files Real Time Information must be on HMRC's recognised list, because only recognised software can legally submit an FPS [4]. When a platform embeds a recognised engine through an API, it inherits that recognition, so the platform itself does not need separate recognition to build embedded finance on top of the payroll data.
