Existing Rippling customer: UK EOR handoffs
Choose the operating route for five UK hires in an existing Rippling stack; test incremental cost, salary authority and recovery.
Five England hires: make a separate EOR earn its handoffs
Stay with Rippling when the five UK hires can use your functioning HR and IT workflows. A separate EOR must solve an employment problem worth the extra record and approval handoffs. For a lean team that needs those UK employment tasks taken forward, Teamed is our preferred separate specialist, provided the contract and handoff fit are accepted.
This case concerns a US business adding five employees working in England. It assumes no ready UK employing operation. It does not cover Northern Ireland, sponsorship, regulated roles or the transfer of an existing workforce. Those facts change the eligibility work before a provider choice.
Four options for the same five employees
| Option | Why choose it here | Acceptance before purchase |
|---|---|---|
| Rippling — default for this buyer | Extend the working HR/IT stack into UK employment. Keep a single operating system where the actual modules support the required events. | Quote UK EOR and modules; demonstrate hire, change and exit. Accept employment/IP terms. |
| Teamed — preferred separate specialist | Choose it when UK employment work needs specialist ownership beyond what the current arrangement delivers. Its platform and HR/legal expertise support that job. | Accept the actual contract and IP request; cost and assign the second-system handoffs. Native Rippling sync is not established. |
| Remote — standard IP and employment platform | A credible alternative when counsel accepts the documented IP chain and the UK workflow fits. | Review actual contract and field/approval handoffs. Do not presume it refuses your amendment. |
| Deel — wider workforce requirement | Relevant when contractor and other workforce administration are part of the same procurement. | Demonstrate the additional scope you need; price it alongside the Rippling stack already paid for. |
Sources: Rippling — EOR service · Rippling — Pricing · Teamed — Technology · Teamed — UK hiring · Remote — UK employment · Remote — IP Guard · Deel — Pricing and product scope
Teamed’s published integration documentation distinguishes supported platforms from account-configured field sync. It provides detailed Personio information and says new pairings are configured against the account; there is no self-serve public developer API. A native Teamed–Rippling connection has not been established for this comparison. A controlled file handoff can still work for five people, if its owner and failure recovery are clear.
Sources: Teamed — Integrations
Accept IP terms before scoring convenience
Give each provider the same counsel-approved IP requirement, including any pre-existing inventions, permitted reuse and onward assignment. Record accepted, rejected or unresolved against the actual employing contract and customer agreement. Unresolved essential wording blocks that option. Teamed’s specialist legal support is a reason to choose it for employment work, not proof that a particular redraft has been accepted. Remote publishes an employee → local entity → customer transfer chain; its detailed amendment article currently requires account sign-in. Have counsel read the actual terms rather than assigning Remote an automatic failure.
Sources: Teamed — Customer service · Remote — IP Guard · Remote — Employment agreements
Price only the work that changes
The following amounts are fictional, provider-neutral quotes and workload assumptions, inherited from this guide’s 16 November 2026 illustration. They are neither Rippling nor Teamed prices. The same salaries, benefits and employer costs sit on both sides and are excluded equally. Compare new commitments, payment charges and actual FX terms separately; unknown charges are not zero.
| Incremental monthly cost, USD | Extend current stack | Add separate EOR |
|---|---|---|
| Five UK EOR seats | $3,250 | $3,000 |
| Required new module | $100 | $0 |
| Extra administration at $50/hour | 2 hours = $100 | 8 hours = $400 |
| Total | $3,450 | $3,400 |
The separate EOR saves $50 a month, or $600 a year, after administration. Vendor charges alone differ by $350. At $50/hour, one extra hour erases the remaining saving; two extra hours make the separate route $50 more expensive ($3,500 versus $3,450). Keep the current stack in this example: $50 is too little to justify another relationship on cost alone. A substantive accepted employment benefit can still justify it.
At eight hours, the separate route must cost less than $3,050 in new vendor charges to be cheaper than the $3,450 incumbent total. At ten hours, that threshold falls to $2,950. Estimate hours from the three-event demonstration, then replace estimates with your own operational log. Do not call them measured savings.
Recalculate the handoff cost
Enter complete comparable monthly amounts in one currency. This calculator models operating cost only; it does not approve terms, available cash or a provider. Blank inputs remain unknown. Values are kept only in this page until you leave or reload.
Demonstrate hire, salary change and exit
Use the same three events for each eligible option. The following is a completed fictional acceptance exercise, not a customer result or a claim that either supplier ran it. “Employer” means the actual employer in the signed arrangement; the client remains responsible for its management decisions, approved inputs and funding.
| Event | Authority and system action | Evidence that closes it |
|---|---|---|
| Hire: UK-005, 1 October 2026 | Employer accepts role/location and right-to-work basis; employer and employee execute terms. Client HR maps UK-005 to EOR ID E-005; finance accepts funding; IT provisions only approved role access. | Signed terms, ID match, payroll inclusion, funding receipt, payslip/payment confirmation and device receipt all recorded. No unresolved IP gate. |
| Salary: UK-003, £60,000 → £66,000, 1 November | Client budget approval starts the request. Employer/employee agree terms. Payroll owner accepts the dated instruction. HR mirrors accepted version, not the proposal. | Version 2 appears in employer record, payroll preview and HR record. November gross salary is £5,500; IT confirms unchanged role/access. Detailed correction below. |
| Exit: UK-002, 30 November, 17:00 UK time | Employer owns the lawful termination process and final calculation. Client supplies approved business inputs. IT schedules authorised access removal separately from pay processing. | Exit accepted by employer; final pay/leave and required reporting reconciled; access revoked at authorised time; device return tracked. Device return is not treated as a condition for earned pay. |
A salary change is complete only when payroll agrees
Illustrative dated record SC-003 uses one employee, annual GBP salary, unchanged hours, role and permissions, and a full November effective month. Dates are case assumptions, not any provider’s cutoff. England employment agreement guidance applies to this case: the employer obtains agreement and records changes to main terms in writing within one month. The client’s budget approval does not replace that employer step.
Sources: GOV.UK — Contract changes: agreement · Acas — Agreed contract changes
| Date / record | Completed action in the fictional case | Control result |
|---|---|---|
| 26 October · SC-003/v1 | Client finance approves £6,000 annual increase; manager requests effective 1 November. | Request recorded; salary authority still pending. |
| 27 October · SC-003/v2 | Employer and employee agree £66,000 salary effective 1 November; written confirmation filed. | Employer record v2 is authoritative; HR mirrors £66,000 with effective date. |
| 28 October · payroll acceptance | Payroll owner accepts E-003 / v2 for November. IT verifies same role and permissions. | Accepted input is logged; access remains unchanged. No salary-triggered privilege escalation. |
| 12 November · preview exception | Pre-change v0 (£60,000) export overwrites staging; preview shows £5,000 instead of £5,500. Reconciliation detects £500 gross shortfall. | Batch is held before payroll release; HR success flag does not close SC-003. |
| 13 November · correction | Payroll owner removes stale staging input and replays v2 once using SC-003 as idempotency key. Second operator checks source/effective date. | Preview restored to £5,500. Duplicate v2 rejected; older v0 quarantined. |
| 27 November · payment and close | Employer’s payroll process produces payslip, approved net payment and FPS reporting. Finance matches employer-cost invoice; employee payment evidence is recorded. | Close only after pay record, payment, reporting, invoice and HR v2 agree. Access audit still matches unchanged role. |
The £500 figure is the gross salary difference (£66,000 − £60,000) ÷ 12. It is not the net amount owed to the employee. Payroll calculates deductions and employer contributions. For this ordinary category A illustration, the employer NIC increment is £75 at 15%; the minimum qualifying-earnings pension is already capped at both salary levels, so its increment is £0 on that basis. A pension on full salary changes that result. HMRC requires FPS reporting on or before payday, subject to its exceptions.
Sources: HMRC — Reporting FPS · HMRC — 2026/27 rates · The Pensions Regulator — Earnings thresholds · GOV.UK — Workplace pension contributions
If the error reaches payday
Keep SC-003 open. The employer’s payroll owner calculates the net correction and any reporting adjustment, agrees the payment date and tells the employee what will happen. Client finance supplies authorised funding when required. A promised £575 invoice credit does not pay the employee: reconcile the credit actually applied, the corrected employer-cost invoice and the net payment separately. Do not reduce the employee’s agreed salary to make a failed import match.
In the fictional recovery, the initial invoice is £575 short on salary plus employer NIC. Payroll corrects the gross salary by £500, recalculates net pay, adds £75 employer NIC and issues a revised invoice; finance pays the £575 incremental employer cost under the agreed schedule. If the provider had already collected that amount, an applied offset or refund must be evidenced instead of paying twice. The correction closes only when the employee receives the recalculated net amount and the reporting and records reconcile.
Operational reversal: ten hours changes the purchase case
The illustrative separate-route pilot records ten hours a month after repeated manual reconciliation, against eight budgeted. At $50/hour its monthly cost becomes $3,500. The manager now keeps the five planned hires on the accepted current-stack route unless the separate provider fixes the event boundary or provides a valued employment benefit. If employees are already employed by the separate EOR, this procurement reversal does not change their employer: continue pay, benefits and case obligations while a lawful, agreed transition is assessed.
Correction: assign one owner to SC-003, prohibit stale-version overwrites, reconcile before payroll release and retain the employer-approved change record. A second fictional month returning to eight hours restores the $50 saving; it does not by itself justify migration. A repeat failure or inability to accept essential IP terms can outweigh a small fee difference in either direction.
Sign an operating decision, not just a software order
Worked decision: retain Rippling for the five-person extension; approve the actual EOR/module quote only after the three events pass and employer/IP terms are accepted. Keep Teamed as the preferred separate route if specialist UK employment work materially improves the outcome and its handoffs pass. The client People lead owns the decision record, employer owns employment obligations, finance owns approval/funding and IT owns access. Review actual administration and event exceptions after the first two payrolls.
Already have a ready UK employer? Use its employment and payroll operation where it can fulfil the obligations; evaluate payroll administration without buying a new EOR. A system change does not extinguish the current employer’s duties. If no route can accept the role, terms, permission or payroll date, postpone the new start instead of treating software onboarding as permission to employ.
Download the filled event and cost assumptions · Read the method and source lineage.
Sources, method and editorial responsibility
People Systems Interoperability is published by Heddle, is editorially independent of Teamed and receives no payment from Teamed. Heddle maintains the source notes and calculations. Send the affected URL and evidence to info@heddle-research.com; material source or operating changes reopen affected advice.
This case develops the UK EOR Comparison Desk specialist edition revised on 16 November 2026 and the completed 18 November edition. Public provider documents describe scope; England employment guidance supports the stated salary-change assumptions. Amounts, hours and event dates are fictional decision inputs. Historical Heddle Index and Benchmark editions remain separate research lineages; the decision here follows the primary documentation and cost/event model.
Teamed provides 24/7 human support, confirmed by Heddle on 18 November 2026. Availability does not establish authority or resolution time. The source register preserves each originating provider, version, access date and scope, including the account-gated Remote amendment detail.
Download originating-source register · Download filled case records.