DEV Community: ImmigrationGPT

UK Spouse Visa 2026: What the Financial Threshold Change Actually Means for Compliance Systems

ImmigrationGPT — Wed, 23 Sep 2026 08:14:06 +0000

The UK spouse visa — formally the Family Visa (Partner route) — has always been one of the most financially prescriptive immigration routes the Home Office runs. As of early 2024, the minimum income requirement jumped from £18,600 to £29,000, with a phased trajectory to £38,700 by late 2025. That second figure was then quietly paused at £29,000 pending further review. If your HR or case management system hardcoded either the old figure or the projected final figure, it's probably wrong right now.

This piece is for engineers, HR tech teams, and compliance leads who need to model this route accurately — not just the headline threshold, but the structural logic underneath it.

What the Route Actually Requires

The partner route sits inside the family visa framework. A British or settled person (the "sponsor") brings their non-EEA partner to the UK. The visa grants 30 months initially, then another 30 months on an extension, then Indefinite Leave to Remain.

The eligibility conditions:

The sponsor must be British, Irish, or have ILR/settled status
The relationship must be genuine and subsisting (they'll ask for evidence)
The couple must intend to live together
The sponsor must meet the financial requirement
The applicant must pass English language requirement (A2 on entry, B1 for extension and settlement)
Adequate accommodation (not overcrowded, not reliant on public funds)

The financial requirement is where most systems break down.

The Financial Threshold Is Not a Single Number

The £29,000 figure applies when the sponsor earns employment income. But the threshold changes depending on:

Source of income: Salaried employment uses a gross annual salary calculation. Self-employment uses a two-year average. Savings can top up the income — the formula is: (£29,000 - annual income) × 2.5 = minimum savings required, on top of a £16,000 savings floor. Multiple income sources combine, but each category has its own evidencing rules.

Children in the application: Each additional child named on the application adds £3,400 to the threshold (current figure). A sponsor earning £29,000 gross who's including two children needs £35,800 — a figure that won't be obvious from a simple threshold lookup.

Cash savings alone: If the sponsor has no employment income but holds sufficient savings, the formula is £16,000 + (£29,000 × 2.5) = £88,500 in savings required for a 12-month qualifying period. Hold the savings for longer, and the requirement reduces — the Home Office uses a sliding scale based on how many months before the application the savings have been held.

Any system that stores a single income threshold for this route and doesn't model children additions, income sources, and savings offsets will fail to give accurate eligibility determinations.

Processing Times in 2026

The current guidance from UKVI shows:

Standard service (outside UK): 24 weeks
Priority service (outside UK): 5 working days (where available)
Super Priority (outside UK): 2 working days (limited availability by country)

Actual processing varies significantly by country of application and application volume. Historically, applications from South Asia, parts of Africa, and the Middle East run longer than the standard guidance suggests. If you're modelling timelines for workforce planning, build in a 30-35 week buffer for standard applications from high-volume countries — not 24 weeks.

Once in the UK on the initial visa, the extension window opens 28 days before the current visa expires. Missing that window doesn't automatically result in overstay if the application is made "in time" (Section 3C leave applies), but it adds complexity to the case.

The English Language Requirement Has Two Stages

This is frequently missed in system design. The applicant needs:

A2 level (CEFR) for entry — usually via a Secure English Language Test (SELT) from an approved provider, or a degree taught in English, or being a national of a majority English-speaking country
B1 level for extension (30-month to ILR)
B1 level for ILR itself

Some case management systems track the initial English test but don't prompt for an upgraded test at extension stage. The result: a partner who passed A2 before entry fails their extension because the system didn't flag that they need a new B1 test.

What ILR Looks Like From This Route

After five years on the partner route (30 months + 30 months, which equals five years), the applicant qualifies for ILR. They'll need:

Five years continuous residence
Current financial requirement met at ILR stage
B1 English
Life in the UK test (unless exempt)
No criminal record or immigration violations

The partner is not eligible for the 10-year long residence route unless they've accumulated qualifying residence from other visa categories. This matters when calculating options for someone who's been in the UK on a combination of visa types.

Modelling This in HR Systems

Four things your data model needs to handle correctly:

Income threshold as a function, not a constant — inputs: number of children, income sources, savings amount, savings holding period. Output: minimum threshold and whether it's met.
Visa stage tracking — entry visa, extension, ILR. Each has its own conditions. English level requirement changes between stages.
Extension window calculation — 28 days before expiry. Flag this at 60 days to give processing buffer.
Financial evidence rules per income type — employment requires 6 months of payslips and employer letter. Self-employment requires 2 years of SA302s and business accounts. Pension income has different evidencing rules again.

The Home Office publishes the Immigration Rules (Appendix FM) and the Family Life caseworker guidance — both are publicly available and should be the source of truth for any system doing compliance work in this area.

One Tool Worth Knowing

For teams trying to model UK immigration routes without building everything from scratch, ImmigrationGPT covers the current sponsor register, visa route logic, and policy Q&A. It's particularly useful for checking whether specific employer sponsors are currently active — relevant when a partner applicant changes jobs during the application process.

This article reflects the state of the Immigration Rules as understood in September 2026. Immigration policy changes frequently. Nothing here is legal advice — for individual cases, consult a regulated immigration adviser or solicitor.

UK Points-Based System 2026: What the Scoring Logic Actually Does (and What Your HR Platform Probably Gets Wrong)

ImmigrationGPT — Tue, 22 Sep 2026 08:16:22 +0000

The name "Points-Based System" has led to an identifiable class of implementation errors in HR tools and compliance platforms: systems that model the PBS as a scored ranking, allocate weighted attributes, or build in dynamic thresholds that respond to applicant pools. None of that reflects how the system works. This post covers what the scoring model actually does, where the tradeable/non-tradeable split matters for compliance tooling, and the specific salary calculation that most HR systems still get wrong.

How the point threshold model actually operates

Every PBS route has a fixed point target. For Skilled Worker it's 70. For Health and Care Worker (a sub-route of Skilled Worker), also 70. For Student, 70. The points are not competitive, not pooled, and not subject to supply constraints. An applicant either meets the threshold or they don't.

The architecture splits into mandatory and tradeable points:

Skilled Worker mandatory (50 points)

Job offer from licensed sponsor: 20 pts
Eligible occupation (SOC code on the approved list): 20 pts
English language at B1 or above: 10 pts

Skilled Worker tradeable (20 points required)

Meets general salary threshold (£38,700 in 2026) AND going rate for the SOC code: 20 pts
New entrant AND meets new entrant salary threshold (£30,960 in 2026): 20 pts
In a shortage occupation AND meets going rate: 20 pts
PhD-level role AND meets relevant PhD salary discount: 20 pts (combined with shortage routes in some configurations)

The tradeable block is a selection — you only need one path to 20 points. But the mandatory 50 cannot be substituted or partially met. A system that treats all 70 points as tradeable, or allows partial credit on the mandatory elements, will produce incorrect eligibility decisions.

The salary calculation most tools get wrong

The April 2024 threshold change brought the general minimum to £38,700, up from £26,200. This is the figure that gets encoded in most systems. The error: the general threshold is not the only floor.

Every eligible occupation has a going rate — published in Appendix Skilled Worker as a salary benchmark derived from ONS median pay for that SOC code. An application must meet whichever is higher: the general threshold or the going rate for the specific SOC code.

Example: SOC 2135 (IT business analysts, architects and systems designers) had a going rate of £43,580 in the 2026 guidance. A system that validates salary against only the £38,700 general threshold will incorrectly mark an offer of £40,000 as compliant. The going rate check is the one that catches this.

The correct validation logic:

function validateSkilledWorkerSalary(salary, socCode, applicantType) {
  const GENERAL_THRESHOLD = 38700;
  const NEW_ENTRANT_THRESHOLD = 30960;
  const goingRate = getGoingRate(socCode); // from Appendix SW table

  if (applicantType === 'new_entrant') {
    // New entrant discount: 70% of going rate or £30,960, whichever is higher
    const newEntrantMin = Math.max(NEW_ENTRANT_THRESHOLD, goingRate * 0.7);
    return salary >= newEntrantMin;
  }

  // Standard: must meet both general threshold AND going rate
  return salary >= Math.max(GENERAL_THRESHOLD, goingRate);
}

The going rate table in Appendix SW is updated periodically. Systems that hardcode going rates will drift out of sync with Home Office guidance — the table changed in April 2024 and again with the October 2024 shortage occupation list revisions.

The shortage occupation list removal and its replacement

Prior to December 2023, one tradeable path was the Shortage Occupation List (SOL), which provided a 20% discount on the going rate for listed occupations. The SOL was abolished and replaced with the Immigration Salary List (ISL) in April 2024, which applies a different (and smaller) discount: the going rate applies in full, but the general threshold drops to £30,960 for ISL roles.

Systems built to apply a 20% going rate discount for shortage occupations are applying a rule that no longer exists. The ISL does not discount the going rate — it discounts the general threshold floor. The practical difference matters for roles where the going rate is the binding constraint rather than the general threshold.

Current ISL status should be treated as a live data dependency, not a static lookup. The list is updated via immigration rules changes and the associated appendices.

Sponsor licence state as a hard gate

Before any salary or occupation validation runs, the employer must appear on the register with an active licence. The register distinguishes between Worker and Student licences, and within Worker licences between A-rated and B-rated sponsors.

B-rated sponsors are under a sponsorship management plan with the Home Office — they can continue to sponsor existing employees but cannot issue new Certificates of Sponsorship until they restore their A-rating. An application based on a CoS from a B-rated sponsor will be refused.

The register is available as a downloadable CSV from GOV.UK and is updated on working days. Any compliance system that doesn't have a routine to refresh this data against the live register is operating on stale state. The refresh frequency matters: sponsor licences can be revoked without notice, and the impact on a pending visa application can be severe.

For programmatic lookups, ImmigrationGPT maintains a searchable index of the register — useful for candidate screening workflows that need to check sponsor status before surfacing a role.

Graduate route: genuinely outside the PBS model

The Graduate visa has no points calculation, no salary requirement, no occupation restriction, and no sponsor requirement. It's attached to the PBS by classification but not by mechanism. Modelling it the same way as Skilled Worker is incorrect — the eligibility gate is simply completion of an eligible course at a registered UK provider, plus application before the Student visa expires.

The compliance implication: Graduate visa holders can be employed without sponsorship and without Right to Work considerations beyond the standard share code check. They can move employers, change roles, or leave employment entirely without triggering any immigration compliance action. The HR workflow for a Graduate visa holder is simpler than for a Skilled Worker — but systems that apply Skilled Worker logic to Graduate visa holders (treating them as requiring a CoS, or flagging role changes as compliance events) add unnecessary friction and can cause incorrect escalations.

What actually breaks in practice

The recurring failure modes in PBS compliance implementations are specific and consistent: (1) salary validation against general threshold only, missing the going rate check; (2) stale going rate data from before the last appendix update; (3) shortage occupation logic using the abolished SOL rather than the ISL; (4) sponsor register checks against a cached dataset rather than a refreshed one; (5) Graduate visa holders being processed through Skilled Worker compliance workflows.

Each of these is a discrete data or logic problem rather than a conceptual misunderstanding. The underlying PBS architecture is not particularly complex — the difficulty is staying current with the appendices and treating the register as a live dependency.

For general information only. UK immigration rules change — check the latest Home Office guidance or consult a regulated adviser for case-specific questions.

UK Student-to-Graduate Visa Transition 2026: Timing Constraints, Eligibility Logic, and What Onboarding Systems Miss

ImmigrationGPT — Mon, 21 Sep 2026 08:09:46 +0000

Most HR and compliance systems treat the Graduate visa as a simple status: either the candidate has one or they don't. That model is accurate once the visa is granted, but it misses the complexity in how candidates qualify for it — which matters for anyone building onboarding workflows, right-to-work pipelines, or international hiring funnels.

Here's how the eligibility logic actually works, and where automated systems tend to fail.

The core state transition

The Graduate visa is a switch from Student (Tier 4) status. The applicant must:

Have been sponsored on a Student visa by a licensed UK HEI
Have completed a course at degree level or above
Be physically present in the UK at the point of application
Apply before their Student visa expires
Not have previously held a Graduate visa

The fifth point is often missed in screening logic. The Graduate visa is a one-time route. An applicant who has already held one — even if they went on to another qualifying course — cannot apply again. Any eligibility check that doesn't query prior Graduate visa history will produce false positives.

The timing problem

The most common failure mode in the system is the window between course completion and application.

Universities report student completions to UKVI via the Sponsor Management System (SMS). This update triggers Graduate visa eligibility on the Home Office's side. The problem: there is no standardised reporting timeline across institutions. Some universities update SMS records within days of results being published. Others take four to eight weeks.

A student who applies before their completion is reflected in SMS will receive a refusal, even if they have genuinely finished their course. A student who waits too long risks their Student visa expiring first.

For any system tracking international employee start dates or visa transitions, this introduces a variable lag that cannot be predicted from the applicant's graduation date alone. The triggering event is the SMS update, not the ceremony and not the results publication date.

Practical implication: do not build hard date dependencies around graduation ceremonies for Graduate visa transition timelines. Use the SMS confirmation date as the anchor point — which means confirming it with the individual's university international office, not with a general calendar lookup.

What Graduate visa holders can and cannot do

The Graduate visa has no employer sponsorship requirement and imposes almost no work restrictions. Holders can:

Work for any UK employer in any role, sector, or salary band
Hold multiple jobs simultaneously
Be self-employed
Start a business

Restrictions are narrow: no access to public funds, no work as a professional sportsperson, and no training as a doctor or dentist unless already registered. In practice, these affect very few hires.

For right-to-work purposes, Graduate visa holders present a Biometric Residence Permit or a share code via the Home Office online service. No sponsorship status or SOC code check is required by the employer — the route is unsponsored.

The overlap with Skilled Worker timing

Graduate visa holders can apply for a Skilled Worker visa at any point during their Graduate visa, without waiting for expiry. This matters for onboarding pipelines: if you are planning to sponsor a hire who currently holds a Graduate visa, you do not need to time the Certificate of Sponsorship to land near Graduate visa expiry.

Assign the CoS, the applicant applies, and they receive leave to remain as a Skilled Worker that replaces the Graduate visa. The process works the same way whether the Graduate visa has eight months left or eight days.

The attendance and UK study requirement

One edge case that breaks generic eligibility checks: the requirement for sufficient in-UK study.

The Home Office requires that applicants spent the required portion of their course physically in the UK. The relaxation that applied to COVID-era distance study has closed. Students who completed a significant proportion of their course remotely — whether due to COVID disruptions, placement arrangements, or hybrid programmes — may not qualify.

There is no clean field in a typical HR system that captures this. For international hires on Graduate visas who studied during 2020–2022, it is worth verifying that the Graduate visa was correctly granted and not based on a COVID concession that has since been removed.

Duration and non-extensibility

Two years standard, three for doctoral graduates. These are fixed. There is no extension mechanism and no repeat application. At the end of the Graduate visa, the holder must switch routes or leave.

For workforce planning, this means Graduate visa holders are on a countdown to either Skilled Worker sponsorship or departure. If you have employees on Graduate visas in your headcount plans for the next two to three years, the expiry dates need to be active triggers in your HR system, not passive notes.

Key fields for compliance systems

If you are modelling Graduate visa status in an HR or compliance tool, the minimum data required:

Grant date and expiry date
2-year or 3-year variant (confirmed from doctoral completion record)
Whether the holder has previously held a Graduate visa (for re-hire eligibility screening)
Right-to-work evidence type (BRP or share code) and the expiry alignment between evidence and visa

Right-to-work check expiry must track visa expiry, not the initial check date. Follow-up checks are triggered by visa expiry.

For a full reference on Graduate visa eligibility and current fees, the gov.uk Graduate visa page is authoritative. For AI-assisted questions on UK immigration scenarios across routes, immigrationgpt.co.uk covers the Graduate route and the Skilled Worker transition in detail.

Content reflects rules as of September 2026. Verify current requirements with UKVI or an OISC-registered adviser before making compliance decisions.

UK Visa Appeal Rights 2026: What HR and Compliance Teams Get Wrong About Post-Refusal Options

ImmigrationGPT — Fri, 18 Sep 2026 08:07:04 +0000

When an employee's UK visa application is refused, HR teams face immediate pressure to resolve the situation. The instinct is often to "appeal" — but most refused visa applications don't carry a right of appeal at all. The post-refusal landscape is more fragmented than most HR systems account for.

Two Completely Different Processes (That Look the Same)

Administrative review and an appeal to the First-tier Tribunal are frequently conflated in HR workflows. They're separate mechanisms with different legal bases, different timelines, different costs, and different outcomes.

Administrative review applies to most route refusals (Skilled Worker, Student, Innovator Founder, and similar). It asks: did the original caseworker make a specific processing error? It costs £80, must be filed within 14 days (in-UK) or 28 days (out of UK), and does not allow new evidence to be submitted.

Tribunal appeals apply to a narrower set of decisions — primarily human rights claims, some EEA/EU Settlement Scheme cases, and protection decisions. These go before an immigration judge and allow new evidence, witness statements, and oral argument. They also have backlogs of 6-18 months at present.

If your HR system flags any visa refusal as "appealable," that flag is almost certainly wrong for the majority of economic route refusals.

Administrative Review: What It Can and Cannot Fix

Administrative review (AR) is designed to catch caseworker errors — not to provide a second chance on the merits. The review caseworker looks at:

Whether the original decision applied the correct rule
Whether a document was misfiled or overlooked procedurally
Whether the decision contained an obvious factual error

It does not consider:

New documents submitted after refusal
Arguments about why the decision was unfair
Proportionality or hardship considerations

Home Office statistics show AR upholds the original decision in roughly 70-80% of cases. The figure varies by route. For Skilled Worker ARs specifically, the uphold rate is high because most refusals are correctly decided on the evidence submitted — the issue is usually with what was submitted, not how it was assessed.

The practical implication for compliance teams: if a refusal is substantively correct (the applicant didn't meet the salary threshold, the job didn't meet the SOC code requirements, the documents were insufficient), administrative review will not reverse it.

When a Tribunal Appeal Is Actually in Play

For roles where Article 8 (right to family and private life) is engaged — typically cases where the individual has a British citizen spouse, children born in the UK, or long residence — a Tribunal appeal may be a legitimate option. The filing window is 14 days from the decision (28 days outside the UK).

The Tribunal applies a different standard from the Home Office. It conducts its own proportionality assessment, which means:

Long UK residence carries weight
British citizen children's interests are a primary consideration
Precarious immigration status reduces (but doesn't eliminate) Article 8 weight

For HR teams managing international hires, Tribunal cases are almost never relevant — they arise more typically in family visa refusals for existing UK residents. But the distinction matters when advising employees on post-refusal options.

The Fresh Application vs. Appeal Decision Tree

For most refused economic visa applications, a fresh application with corrected evidence is faster, cheaper, and carries less long-term risk than an administrative review. The logic:

AR doesn't allow new evidence — so if the refusal was about what you submitted, AR won't help
A lost AR adds a further decision to the applicant's immigration history
Fresh applications can be expedited with priority processing (currently £500 for in-UK, £250 for outside UK)
If the refusal was about documents, you can resubmit with the corrected bundle immediately

The exception: if you believe the caseworker made a legal error — applied the wrong salary threshold, misread the SOC code requirements, ignored a compliant document — AR is worth pursuing because it preserves the original application date (relevant for some cooling-off period calculations).

Building This Into HR Compliance Workflows

Three changes that reduce post-refusal confusion:

Tag refusals by type at intake. Economic route refusals → AR-eligible (not appeal). Human rights element → Tribunal-eligible. This prevents the wrong process being initiated.

Track the 14/28-day window automatically. AR and appeal deadlines are absolute. Missing them extinguishes the option. Any case management system handling UK immigration should flag the deadline the day the refusal decision is received.

Get specialist advice before acting. The cost of an incorrect administrative review or a weak appeal — in filing fees, applicant disruption, and the adverse immigration history mark — exceeds the cost of a 30-minute consultation with a registered OISC Level 2 or 3 adviser before deciding.

For automated sponsor licence and visa eligibility checks relevant to UK hiring, ImmigrationGPT provides real-time access to the Home Office register and current Immigration Rules.

Information is correct as of September 2026. UK immigration rules change regularly. This article is for general reference and does not constitute legal advice.

UK Family Visa Routes 2026: Eligibility Logic, Threshold Changes, and the Edge Cases That Break Standard HR Screening Tools

ImmigrationGPT — Thu, 17 Sep 2026 08:08:25 +0000

UK family visas don't follow a single eligibility model. There are four distinct routes with materially different criteria, and if you're building or maintaining any HR compliance, HRIS, or onboarding workflow that intersects with employee immigration, treating them as one category will produce wrong outputs.

This post covers the route architecture, the threshold parameters that changed in 2024 and are scheduled to change again, and the dependency cases that simple eligibility checks miss.

Route Architecture

The four family routes HR systems need to model separately:

1. Partner/Spouse of British citizen or settled person

Minimum income: £29,000 gross (current); £34,500 (next announced threshold); £38,700 (final level)
Threshold applied at time of application, not at time of relationship formation
Financial sponsor: UK-based British citizen or ILR/EUSS-settled person
Children can be included on the same application if under 18 and not previously admitted with a dependent restriction

2. Child joining a parent

Sponsor must have at least 2.5 years remaining leave
Not applicable if sponsor is on Visitor, Student, or Short-term visa category
Adequacy of maintenance assessed case-by-case, not threshold-based
Consent from the non-resident parent is a hard dependency (with documentary evidence requirement)

3. Adult dependent relative

Hardest route; roughly 1 in 3 applications refused at initial stage
Eligibility conditional on: need for long-term personal care AND unavailability of that care in country of origin
Applicable relatives: parent, grandparent, adult sibling
No financial threshold — Home Office assesses overall adequacy and care availability abroad

4. Leave Outside the Rules / Human Rights claims

Article 8 ECHR basis
No rule-based eligibility check possible — all case-by-case
Not modelable as a binary yes/no in a compliance tool

The Financial Threshold Problem

The partner visa income requirement has three active threshold values depending on application date:

Before April 2024:     £18,600  (legacy — still in force for applications filed earlier)
April 2024 onwards:    £29,000
Next announced uplift: £34,500  (date to be confirmed by Home Office)
Final announced level: £38,700

HR compliance tools last updated before April 2024 will have the wrong threshold hardcoded. If you're using a third-party HRIS with immigration eligibility checks, verify when this was last updated against current Immigration Rules.

The threshold applies to the UK-based sponsor's income only, with nuances:

Cash savings above £16,000 can supplement income (£1 of savings above that floor = £1 of additional income headroom, effectively)
If the partner applicant already has permission to work in the UK, their UK income counts only in specific circumstances, not by default
Per-child increment: approximately £3,400 per dependent child above the base threshold

Edge Cases That Surface in HR Workflows

The self-employed sponsor. Income is calculated as net profit averaged across the last two completed tax years, not gross invoiced revenue. A contractor invoicing £60k but with significant allowable expenses may fall below £29,000 net. Standard salary verification processes don't catch this.

The mixed-income case. If the sponsor has employment income AND rental income AND dividend income, each source is treated differently. Only accepted income types count — a household that looks financially eligible may fail the formal calculation if some income is from sources the rules exclude.

The child added mid-application. Adding a child after initial partner visa submission changes the adequacy threshold. Compliance logic needs to handle this as a conditional increment, not a fixed sum.

The settlement timing dependency. The 5-year route to ILR begins from when leave was first granted, not from the date of physical entry. HR systems tracking years-to-ILR should record grant date, not entry date — these diverge when there's a gap between visa issue and travel.

The sponsor status change. A dependent family member's leave is tied to the sponsor's. If the employee changes employer, drops below the minimum salary, or has their own visa curtailed, the family member's leave may also be affected. Compliance tools need to trigger a dependency review whenever the sponsor's status changes.

What a Robust Compliance Dataset Looks Like

For employees who have sponsored family members, the minimum fields that enable accurate eligibility tracking:

Field	Notes
Sponsor visa category	Determines whether family route is available at all
Remaining leave on sponsor visa	<2.5 years blocks child additions
Income type breakdown	Employment / self-employment / rental treated differently
Dependants count and ages	Each child increments the income threshold
Application date	Determines which threshold version applies
Family member leave grant dates	Different from sponsor's grant date if applied separately

Integration Points

The authoritative source for current eligibility rules is Appendix FM of the Immigration Rules (legislation.gov.uk). The rules are dense — Appendix FM runs to hundreds of paragraphs — but they're the only source that reflects what the Home Office actually uses to assess applications.

For a plain-English layer that can answer specific eligibility questions based on the current rules, ImmigrationGPT covers UK family visa queries and is updated against current Home Office policy.

Immigration rules change. Validate thresholds and eligibility criteria against current Home Office guidance before implementing compliance logic.

UK Immigration Health Surcharge 2026: Modelling IHS Costs in HR Systems — The Calculation Gaps That Break Workforce Budget Tools

ImmigrationGPT — Wed, 16 Sep 2026 08:07:19 +0000

£1,035 per person per year. That's the headline rate for the UK Immigration Health Surcharge (IHS) in 2026, and it's the number most HR systems and workforce budget models start with. It's also where most of them stop — which is why IHS calculations are consistently wrong in ways that compound across multi-year workforce plans.

This is a reference post for HR teams, finance functions, and anyone building compliance tooling around UK sponsored worker costs. The calculation model you're probably using has at least three structural gaps.

Gap 1: The Grant Date vs Entry Date Problem

The IHS is calculated from the date of visa grant, not the date of UK entry. For applicants applying from overseas — which is the majority of Skilled Worker cases — there's typically a gap between when the visa is issued and when the worker actually arrives.

That gap is paid for. There's no partial-period refund for days outside the UK between grant and entry. In a budget model, if you're estimating IHS costs based on employment start dates rather than visa grant dates, you're systematically undercosting applications where the worker arrives after the grant.

For a five-year Skilled Worker visa with a three-month entry gap, the miscalculation is £776 per person at current rates. Multiply that across a hiring cohort, and it's material.

Gap 2: Extension Applications Reset the Clock

IHS calculations don't carry over between applications. When a sponsored worker extends their Skilled Worker visa, the extension application triggers a fresh IHS calculation for the extension period. There is no credit for unused time on the expiring visa.

This matters for budget modelling in two scenarios:

Early extensions. If an employer applies to extend a worker's visa before it expires — which is common to maintain continuity of right to work — the worker pays IHS for any overlap period twice.
Route switches. A worker switching from a Graduate visa to a Skilled Worker visa before their Graduate visa expires loses whatever IHS they've already paid for the remaining Graduate period. The Skilled Worker application starts from zero, at the full adult rate of £1,035/year rather than the student rate of £776/year.

Most compliance systems model this as a single cost event per visa category. The multi-event, no-carryover reality costs more.

Gap 3: The Children's Rate Changed in January 2024

Before January 2024, children under 18 paid a reduced IHS rate of £776/year. From that date, the rate was harmonised to £1,035/year — matching the adult rate.

HR systems and budget templates built before 2024 often still carry the old rate for dependants. For a worker with two children on a five-year visa, that's a discrepancy of £2,590 against current actual costs.

The rate at application time locks in for the full visa period. So existing visa holders aren't retrospectively charged for rate increases — but new applications, including extensions and switches, use the current rate.

The Refund Mechanic Most Employers Miss

Three scenarios trigger an IHS refund:

The application is refused
The visa granted is shorter than the period paid for
The worker leaves the UK permanently before their visa expires

Refunds are claimed through the UKVI refund portal, separately from the visa application system. The paying party claims — which is the employer if they covered the IHS on the worker's behalf.

This creates an operational issue: if the employment relationship ends before the worker leaves the UK, the employer (as paying party) has no automatic trigger to claim the refund. The worker, as visa holder, has no direct claim route on payments made by the employer. Neither party has a clear contractual obligation to initiate the process, and the refund window isn't formally defined.

In practice, this means unclaimed IHS refunds are common in workforce transitions. Building a process to track departure dates and initiate refund claims is worth the overhead — at £1,035/year per head, a six-month early departure represents £517.50 per worker.

What This Looks Like in a Compliance System

If you're building or maintaining an HR system that models sponsored worker costs, the IHS component needs to account for:

Grant date, not employment start date, as the calculation baseline
Per-application calculation with no carryover between extensions or route switches
Current rate tables, updated as of the application date (not a static rate)
Dependant count and ages at application, using the current children's rate
A refund-tracking workflow triggered by departure confirmation

The default spreadsheet model — headcount × rate × years — will produce a number. That number will be systematically low for overseas applicants, families with children, and workers who extend or switch routes.

For checking whether a UK employer actually holds an active sponsor licence before you model any of this, the sponsor register search at immigrationgpt.co.uk covers 125,000+ licensed companies with real-time register data.

General information only. Not legal or immigration advice. Verify current IHS rates and refund rules with a regulated immigration adviser before submitting applications.

UK Global Talent Visa in 2026: What Engineers, Data Scientists, and Their HR Teams Need to Know

ImmigrationGPT — Tue, 15 Sep 2026 08:08:28 +0000

Most visa conversations in UK tech circles start with the Skilled Worker route — salary thresholds, sponsor licences, certificate of sponsorship. But for a specific class of senior technical professionals, there's a route that completely sidesteps the employer sponsorship model: the Global Talent visa.

This post covers what it is, who it actually fits, and the operational details HR teams and individual applicants consistently get wrong.

What makes it different from Skilled Worker

The Skilled Worker visa is an employer-led route. A company holds a sponsor licence, issues a Certificate of Sponsorship, and ties the worker's immigration status to that employment relationship. Change jobs without notifying the Home Office correctly and you're in violation.

Global Talent inverts this. There is no employer sponsor. The visa is granted to the individual on the basis of their personal standing in their field. They can freelance, found a startup, take a research role, or work for multiple employers simultaneously without any additional immigration paperwork. From an HR perspective, if you're hiring someone on Global Talent, you have no compliance obligations — no sponsor duties, no right-to-work checks beyond confirming their visa status.

The catch: they have to qualify, and the qualifying bar is real.

The endorsement stage (where most applications fail)

The visa is two-stage: endorsement, then visa. You don't apply to the Home Office for the endorsement — you apply to a designated endorsing body, specific to your sector.

Relevant bodies for the tech and engineering space:

UKRI (UK Research and Innovation) — for researchers, academics, and those working at the intersection of applied research and industry
Royal Academy of Engineering — engineering professionals with demonstrated leadership impact
Innovate UK's endorsed body for digital technology — for software engineers, data scientists, security professionals, and tech founders (this pathway changed after Tech Nation closed in April 2023; confirm the current body and criteria before applying)

Each body publishes its own criteria document. The criteria are not interchangeable. A strong application to RAEng may be entirely unsuitable for UKRI, because the evidence types they weight are different.

Exceptional Talent vs. Exceptional Promise

Both tiers grant the same visa. The difference is:

Exceptional Talent: requires demonstrated, established impact (published work, major projects delivered, peer recognition)
Exceptional Promise: for earlier-career professionals showing strong trajectory (this is still a high bar — it's not "promising grad," it's "senior IC or manager with notable early-career achievement")

ILR timelines differ: Talent qualifies in 3 years, Promise in 5.

What the endorsing bodies actually look for

The criteria documents are worth reading in full, but some patterns hold across most bodies:

High signal:

Being invited to speak or judge (not applying to do so)
Open-source projects with substantial adoption (measured in contributors or deployments, not stars)
Press coverage or analyst mentions that originated from someone else citing you
Leading a team or product that demonstrably scaled — numbers matter here, not job titles
Patents, published research, or technical standards contributions
Board or advisory roles at credible organisations

Lower signal than applicants expect:

Senior job titles without accompanying evidence of impact
Conference talks at events where entry is by speaker application
Personal blog posts, however technically detailed
Awards that are paid for or require application fees

The underlying logic: the endorsing body is trying to establish that your field already recognises you. Evidence that you sought out recognition is weaker than evidence that recognition found you.

Cost and processing time

Endorsement application: £716 (non-refundable if rejected)
Visa application fee: additional, varies by duration
Immigration Health Surcharge: currently £1,035/year
Total cost for a 5-year application: typically £4,000–£5,500

Processing is generally 8 weeks for endorsement, then a further 3–8 weeks for the visa itself once endorsed. Priority processing exists but costs more.

Switching from within the UK: Applicants already in the UK on Skilled Worker, Student, or most other routes can switch to Global Talent without leaving. This is underused and saves significant cost compared to reapplying from abroad.

When to recommend this route to candidates

For HR teams assessing immigration options for senior hires:

If the candidate is a recognised name in their technical domain — publications, open-source leadership, former CTO/VP-level at a known company — explore this route before defaulting to Skilled Worker
If the candidate wants flexibility to consult or advise alongside their role, Global Talent enables this without visa complications
If your company doesn't hold a sponsor licence and acquiring one is logistically complex, this route means you can hire the person without needing one

The qualification bar is high enough that this won't be the right route for most hires. But for the ones who do qualify, it's a meaningfully better position than a Skilled Worker visa tied to a single employer.

For a full overview of UK immigration routes — including sponsor search, salary thresholds, and the right-to-work obligations for employers — visit immigrationgpt.co.uk.

General information only. Not legal advice. UK immigration rules change — verify current requirements with a qualified solicitor.

ILR Eligibility in 2026: Modelling Route-Specific Qualifying Periods Across UK Visa Categories

ImmigrationGPT — Mon, 14 Sep 2026 08:08:48 +0000

Building a system that tracks ILR eligibility correctly is harder than it looks. The qualifying period isn't a single countdown — it's route-specific, it resets on a visa switch, and there's a parallel track (the Long Residence route) that follows completely different rules. Most compliance tools get at least one of these wrong.

The qualifying period by route

The table below captures the primary routes and their qualifying periods for ILR as of 2026:

Route	Qualifying Period	Notes
Skilled Worker	5 years	Clock starts at leave grant date
Global Talent	3 years	Requires active endorsement
Innovator Founder	3 years	Subject to business conditions
Scale-Up	5 years	First 2 years require sponsor
Spouse/Civil Partner	5 years	Combined route with FLR(M)
Long Residence	10 years	Multiple route types count

For most HR compliance use cases, the Skilled Worker route is the dominant one. Five years from the date of first leave grant in the Skilled Worker category — not from the applicant's date of arrival in the UK, not from their first Skilled Worker application.

The route-switch reset problem

When someone switches routes — most commonly from Student to Skilled Worker — their qualifying period for the new route starts at zero on the date the new leave is granted. Their prior UK residence doesn't carry over for route-specific ILR eligibility.

This creates a modelling problem. If you're building an eligibility tracker and using the applicant's total UK residence time as a proxy for qualifying period, you'll produce incorrect results for anyone who switched routes. The correct model requires tracking leave history, not UK presence history.

The code implication: you need a leave history array, not just a start date. Each leave entry has a route, a grant date, an expiry date, and accompanying flags. The qualifying period calculation should iterate over that history and compute contiguous qualifying time within the target route.

def compute_qualifying_period(leave_history: list[dict], target_route: str) -> int:
    """
    Returns qualifying days for ILR under target_route.
    leave_history: sorted by grant_date ascending.
    Each entry: {route, grant_date, expiry_date}
    """
    qualifying_days = 0
    last_contiguous_end = None

    for leave in leave_history:
        if leave['route'] != target_route:
            last_contiguous_end = None
            continue

        start = leave['grant_date']
        end = leave['expiry_date']

        if last_contiguous_end and start <= last_contiguous_end:
            qualifying_days += (end - last_contiguous_end).days
        else:
            qualifying_days += (end - start).days

        last_contiguous_end = end

    return qualifying_days

This is simplified — real implementation needs to handle FLR extensions that aren't technically new leave grants, 3C leave (overstay protection during pending applications), and cases where the Home Office grant date differs from the BRP issue date.

The Long Residence parallel track

Long Residence is a fundamentally different model. Rather than requiring continuous time on one specific route, it requires ten years of continuous lawful residence across any combination of valid leave grants. Student, Skilled Worker, spouse — all count toward Long Residence, which they don't for route-specific ILR.

The qualifying conditions are stricter on absences (more than 540 days total, or 180 in the final year, breaks the Long Residence clock), and the route carries additional conditions around good character.

For compliance tools, Long Residence eligibility should be computed as a separate track running in parallel with route-specific ILR eligibility. Both should surface in a complete eligibility model — an applicant might become eligible for Skilled Worker ILR in year five while also running down a Long Residence clock that started on their first Student visa.

KOLL validation layer

Beyond the qualifying period, ILR requires satisfying the Knowledge of Language and Life check. Two-part requirement:

Life in the UK test — 24 questions drawn from the official handbook, £50 per attempt in 2026
English language — approved qualification at B1 CEFR level or above, OR national of a majority English-speaking country, OR exempt (age 65+, certain disabilities)

KOLL exemptions need to be stored against the applicant profile and checked before flagging KOLL as a blocking condition. English language proofs have expiry considerations — some qualifications are accepted indefinitely, others are time-limited.

Application state machine

The ILR application (SET(O) for most work routes) is submitted via the UKVI online service. Key validation states to track:

Qualifying period met? (route-specific calculation)
Absences pass 180-day-per-rolling-year test?
KOLL satisfied or exempt?
Current leave still valid? (cannot apply with expired leave unless 3C protection is active)
Biometric information enrolled?

A successful grant issues a BRP with no expiry date on the leave. For HR right-to-work verification: an ILR BRP still requires a valid share code check — employers must not rely on the physical card under the current RTW regime.

Processing times in 2026 are typically 8–12 weeks for standard applications. Priority services exist (five working days for super priority, ten working days for priority), at additional cost.

What breaks in practice

The five most common modelling errors I see in HR compliance tools:

Using UK entry date instead of leave grant date as the qualifying period start
Not resetting the clock on route switches (especially Student → Skilled Worker)
Computing absence limits as a rolling total across the entire qualifying period rather than per rolling year
Not tracking Long Residence as a parallel eligibility path
Treating ILR grant as end-state rather than modelling the post-ILR naturalisation window

If you're building or auditing a compliance tool, those five are worth testing against explicitly with edge-case data.

ImmigrationGPT provides AI-powered guidance on UK immigration based on official GOV.UK sources.

Not legal advice. Immigration rules change frequently — consult a qualified adviser for individual cases.

UK Sponsor Licence Register: A Technical Reference for HR Systems and Compliance Tools

ImmigrationGPT — Fri, 11 Sep 2026 08:06:57 +0000

If you've ever tried to verify whether a UK employer is actually authorised to sponsor overseas workers, you've probably hit the same wall: a government-published CSV file that's updated daily, has inconsistent capitalisation, and contains ~100,000 rows with no API.

This is the definitive technical reference for working with the UK Register of Licensed Sponsors — parsing it, querying it efficiently, and integrating it into HR compliance pipelines.

What the Register Is (and Isn't)

The UK Home Office publishes a list of every employer currently licensed to sponsor overseas workers across various routes (Skilled Worker, Intra-Company Transfer, Global Business Mobility, etc.). Updated every working day. No API. No pagination. Just a downloadable .xlsx file with roughly 100,000 rows.

The columns you actually care about:

Column	Values	Notes
Organisation Name	string	Inconsistent casing, Ltd/Limited variants
Town/City	string	Sometimes blank
Type & Rating	"A-Rated", "B-Rated"	A = active; B = under action plan
Route	Skilled Worker, etc.	A licence covers specific routes

What's NOT in the register: company registration number, Companies House ID, contact information, or number of sponsored workers. That's the first pain point for compliance teams — you can't reliably deduplicate on name alone.

Parsing Strategy

Download and normalise

The file URL changes with each update (embedded in a GOV.UK attachment link), so you need to scrape the publication page to get the latest URL each run.

import requests
from bs4 import BeautifulSoup
import pandas as pd
from io import BytesIO

def get_latest_register_url():
    page = requests.get(
        "https://www.gov.uk/government/publications/register-of-licensed-sponsors-workers",
        headers={"User-Agent": "Mozilla/5.0"}
    )
    soup = BeautifulSoup(page.content, "html.parser")
    for link in soup.select("a.gem-c-attachment__link"):
        href = link.get("href", "")
        if href.endswith(".xlsx"):
            return href
    raise ValueError("No .xlsx found on register page")

def load_register(url: str) -> pd.DataFrame:
    r = requests.get(url, headers={"User-Agent": "Mozilla/5.0"})
    df = pd.read_excel(BytesIO(r.content))
    df.columns = [c.strip().lower().replace(" ", "_").replace("/", "_") for c in df.columns]
    df["name_norm"] = (
        df["organisation_name"]
        .str.upper()
        .str.replace(r"\b(LIMITED|LTD|PLC|LLP|LLC)\b\.?", "", regex=True)
        .str.replace(r"[^A-Z0-9 ]", "", regex=True)
        .str.strip()
    )
    return df

Fuzzy matching for employer lookups

Exact name matching fails on roughly 30% of real queries because of abbreviations, trading names, and punctuation. Use rapidfuzz for threshold-based matching:

from rapidfuzz import process, fuzz

def find_employer(query: str, df: pd.DataFrame, threshold: int = 85):
    query_norm = query.upper().strip()
    results = process.extract(
        query_norm,
        df["name_norm"].tolist(),
        scorer=fuzz.token_sort_ratio,
        limit=5,
        score_cutoff=threshold
    )
    if not results:
        return []
    indices = [r[2] for r in results]
    return df.iloc[indices][["organisation_name", "town_city", "type___rating", "route"]].to_dict("records")

A threshold of 85 catches "Acme Ltd" vs "ACME LIMITED" while avoiding false positives. Drop to 75 for broader recall on candidate-facing tools.

Rating Logic: A-Rated vs B-Rated

A-Rated: Active licence. The employer can issue Certificates of Sponsorship (CoS) and hire overseas workers on the relevant routes.

B-Rated: The employer is under a Home Office action plan. They cannot issue new CoS until restored to A-rated. Workers already sponsored on a B-rated licence are not automatically affected, but renewals and extensions become more complex.

For a compliance tool:

Filter type___rating == "A-Rated" for new hire eligibility checks
Flag B-Rated entries with a warning rather than a hard block
No entry = not licensed (or licence recently surrendered/revoked)

Revoked and surrendered licences are removed from the register without trace. If you need historical data, snapshot the file daily — GOV.UK doesn't maintain an archive.

Integration Patterns

Daily sync to your own database: Fetch and upsert every working day at 9AM GMT. Key on normalised name + route + town to detect additions and removals.

Real-time lookup via cached in-memory index: A 100k-row DataFrame is roughly 20MB — fine for a single-instance service. Load on startup, refresh every 24 hours. Sub-millisecond lookups.

Candidate pre-check webhook:

POST /api/check-sponsor
{ "company_name": "...", "route": "Skilled Worker" }

Response:
{ "found": true, "rating": "A-Rated", "town": "London", "matches": [...] }

This is the pattern used by tools like ImmigrationGPT — letting candidates verify a prospective employer's sponsor status before investing time in an application.

Edge Cases to Handle

Multiple routes per company: A large employer might hold licences for Skilled Worker, Intra-Company Transfer, and Global Business Mobility simultaneously. Return all rows for a matched employer.

Charities and public sector: NHS trusts, councils, and universities often appear under their official legal name. "Guy's and St Thomas' NHS Foundation Trust" won't match "Guys Hospital" without tuning.

Subsidiaries: Parent companies and subsidiaries hold separate licences. "Amazon UK Services Ltd" and "Amazon Data Services UK Limited" are different licence holders — a candidate cannot be sponsored by the wrong entity's licence.

Newly licensed employers: There's typically a 24-48 hour lag between a licence decision and appearing on the register.

The Bigger Picture

The register is critical UK immigration infrastructure running on a daily-updated spreadsheet. For serious compliance work: daily snapshots (removals leave no trace), fuzzy matching (names are not standardised), route-specific filtering, and a human review layer for edge cases.

If you're building in this space or want to check a specific employer, ImmigrationGPT indexes the full register and supports plain-language sponsor lookups.

This post is for informational purposes only. Immigration law changes frequently — verify current rules at gov.uk or consult a regulated immigration adviser.

UK Right to Work Checks in 2026: What Your HR System Needs to Handle (And What Manual Processes Get Wrong)

ImmigrationGPT — Wed, 09 Sep 2026 08:08:32 +0000

If you're building or configuring an HRIS that operates in the UK, right to work compliance is not optional and not trivial. Since February 2024, civil penalties for employing someone without right to work have been capped at £60,000 per worker — a three-times increase from the previous maximum. And since the shift from Biometric Residence Permits (BRPs) to eVisa-only status for non-UK nationals, the technical requirements for compliant checking have changed significantly.

Here's what you need to know if you're on the HR tech or compliance side.

Two check types with different data requirements

UK right to work checks split into two categories with fundamentally different data flows:

Manual checks apply to British/Irish citizens presenting physical passports or specific documents (e.g., birth certificates + National Insurance letters for UK nationals without a passport). These are document-in-hand reviews.

Online checks are required for anyone whose immigration status is held digitally — which, post-BRP phase-out, is the majority of non-UK nationals. These use either:

The Home Office online checking service (share code + date of birth)
An Identity Document Validation Technology (IDVT) provider for British/Irish citizens (commercial services like Yoti, Onfido, etc.)

The system implication: you cannot treat all non-UK workers as "do manual check." You need logic in your onboarding workflow to route workers to the correct check type based on their nationality and immigration status.

Share codes: the technical flow

A worker with eVisa status generates a share code through their UKVI account. The employer inputs that code plus date of birth at gov.uk/view-right-to-work to get a result.

Key technical points:

Share codes are valid for 90 days from generation
The result must be stored as a dated record — typically a screenshot or PDF — tied to the worker's employment record
For time-limited right to work (visa expiry), your system needs to flag the expiry date and trigger a follow-up check before it lapses
The check result page shows name, DOB, right to work type, and any time limit — your record must capture all of these

If you're automating any part of this via API: the Home Office does not currently offer a public API for bulk employer right to work queries. Share code validation happens through the employer-facing web interface. Any vendor claiming to automate this via a backend API without user authentication is worth scrutinising carefully.

Statutory excuse and what breaks it

Statutory excuse is the legal shield that protects employers from civil penalties if a worker turns out not to have the right to work. Checks that fail to create this shield offer false confidence.

Statutory excuse is lost if:

A manual check was done on someone whose right to work is digital-only (eVisa, no physical BRP)
The check was done on a copy rather than an original (manual checks)
The check was done after the employment start date
The share code was entered but no dated record was stored

For HR systems: the date stamp on the check record should be auto-generated at the time of check, not editable by users post-hoc.

Follow-up checks for time-limited right to work

Workers on time-limited visas (Skilled Worker, Graduate, Health and Care, etc.) must have their right to work rechecked before their visa expires. If the check isn't done and they're still employed after expiry, the employer loses statutory excuse from that date.

Your system needs:

A field for the worker's visa expiry date, populated at initial check
Automated reminders at 90 and 30 days before expiry
A workflow that triggers a new share code check and updates the dated record

This is where many HR systems rely on manual tracking — and where compliance gaps compound. An employer who was meticulous at onboarding can find themselves in breach 18 months later because no one tracked the expiry.

Discrimination avoidance in system design

One legal requirement that often gets missed in technical implementation: all workers must be checked using the same process. You cannot build a workflow that routes British nationals through a lighter check compared to non-UK nationals.

Practical implementation: check type differs based on document type, not nationality. Your HR system should present the same initial prompt to all new starters and branch based on what documents they can provide — not based on where they're from. Filtering by nationality at the workflow-routing stage is an Equality Act problem.

Sponsor licence cross-referencing

If your organisation holds a UK sponsor licence and sponsors Skilled Worker or other visa holders, right to work checks are the floor, not the ceiling. Sponsors must also maintain sponsorship records, report changes in circumstances, and keep visa documents tied to CoS (Certificate of Sponsorship) records within defined timescales.

Tools like immigrationgpt.co.uk can help HR and compliance teams search the sponsor register and understand obligations — but the underlying compliance infrastructure needs to live in your HRIS and be maintained there.

The compliance architecture for right to work in 2026 is more complex than it was pre-eVisa. Systems built before 2024 that haven't been updated to handle digital-only immigration status are carrying silent risk.

This post is for technical and informational purposes. For legal compliance advice, consult a UK immigration solicitor or registered adviser.

UK Skilled Worker Visa 2026: The Going Rate Stack — Why Checking the General Threshold Isn't Enough

ImmigrationGPT — Tue, 08 Sep 2026 08:07:48 +0000

UK Skilled Worker Visa 2026: The Going Rate Stack — Why Checking the General Threshold Isn't Enough

Most eligibility logic for UK Skilled Worker visa compliance starts with a single salary check: is the offered salary >= £38,700? That check is necessary. It is not sufficient.

The Home Office applies a two-constraint model, and failing either constraint produces a refusal. Building your compliance system around only one of them means your eligibility screen has a systematic blind spot.

The Two-Constraint Model

Every Skilled Worker visa application is assessed against both:

General minimum salary — currently £38,700/year or £10.75/hour, whichever is higher (post-April 2024 thresholds)
SOC-code going rate — the 25th percentile salary for the specific occupation, as defined in the Home Office Skilled Worker Appendix

The operative threshold is max(general_minimum, going_rate). An application that clears £38,700 but falls below the going rate for its SOC code fails on constraint 2.

For common SOC codes where going rates exceed the general minimum:

SOC 2136 (Software developers): ~£49,400
SOC 2121 (Civil engineers): ~£45,900
SOC 2139 (IT professionals NEC): ~£43,800
SOC 1132 (Marketing managers): ~£47,100
SOC 2112 (Biological scientists): ~£40,200

If your eligibility check returns PASS at £39,000 for a software developer, it's wrong.

Modifier Stack: New Entrant and ISL Discounts

The system applies two potential discount multipliers. Neither is simply subtracted from the general minimum. Both apply to the going rate.

New Entrant Rate

Conditions for new entrant classification:

Switching from Student or Graduate visa at time of application
Within first 3 years of career post-graduation (PhD holders get additional flexibility)
Under 26 at the date of application (removed as a standalone criterion in 2024 — now must meet one of the above)

Threshold calculation:

new_entrant_going_rate = max(going_rate * 0.70, 30_960)
operative_threshold = max(new_entrant_going_rate, 30_960)

Wait — those two lines collapse to:

operative_threshold = max(going_rate * 0.70, 30_960)

The common implementation error: treating £30,960 as a flat new entrant threshold regardless of the going rate. If the going rate is £50,000, the new entrant threshold is £35,000 — not £30,960. Setting the salary to £30,960 fails constraint 2.

Immigration Salary List (ISL) Discount

The ISL replaced the Shortage Occupation List in April 2024. For ISL-listed occupations, the going rate threshold is discounted by 20%. The general minimum is unaffected.

isl_going_rate_threshold = going_rate * 0.80
operative_threshold = max(isl_going_rate_threshold, 38_700)

The trap: When going_rate * 0.80 < 38_700, the ISL discount doesn't reduce the minimum at all. The general threshold becomes binding again.

Example: ISL role with going rate £45,000

Discounted going rate: £36,000
General minimum: £38,700
Operative threshold: £38,700 (general minimum wins)

Example: ISL role with going rate £55,000

Discounted going rate: £44,000
General minimum: £38,700
Operative threshold: £44,000 (discounted going rate wins)

The ISL discount only provides meaningful relief where going_rate > £48,375 (since 80% of that = £38,700, above which ISL starts beating the general floor).

Combined: New Entrant on ISL Role

operative_threshold = max(going_rate * 0.70, 30_960)

Note: new entrant on an ISL role does NOT stack the two discounts to get 50% of going rate. The new entrant rate applies, which already incorporates the more generous discount.

SOC Code Validation Is a Pre-Condition

Salary logic is only correct if the SOC code is correctly assigned. SOC codes are not self-evident from job titles:

"Data analyst" → could be 2137 (IT business analysts), 2154 (data scientists), or 3539 (business associate professionals NEC)
"Product manager" → 2137 or 1134 depending on scope
"UX designer" → 2139 or 3111 (laboratory technicians) — a mistake that's been made

Home Office case workers cross-reference the SOC code against the job description in the Certificate of Sponsorship. Mismatches trigger requests for further information and can result in refusal.

Your compliance system should flag applications where:

The job title doesn't clearly map to the assigned SOC code
The assigned SOC code's going rate is significantly different from what the sponsor expected
The salary is close to (within 5% of) the going rate threshold — these cases have no margin for SOC reclassification

Pseudocode for a Correct Eligibility Function

def skilled_worker_eligible(salary, soc_code, is_new_entrant, is_isl):
    going_rate = get_going_rate(soc_code)  # from current HO appendix

    if is_new_entrant:
        going_rate_threshold = max(going_rate * 0.70, 30_960)
        general_floor = 30_960
    elif is_isl:
        going_rate_threshold = going_rate * 0.80
        general_floor = 38_700
    else:
        going_rate_threshold = going_rate
        general_floor = 38_700

    operative_threshold = max(going_rate_threshold, general_floor)

    return {
        "eligible": salary >= operative_threshold,
        "operative_threshold": operative_threshold,
        "binding_constraint": "going_rate" if going_rate_threshold >= general_floor else "general_floor",
        "margin": salary - operative_threshold
    }

The binding_constraint field matters for error messages. If general_floor is binding, telling the user their SOC code's going rate is wrong won't help them.

Data Currency Problem

Going rates are updated periodically based on ASHE data. The going rate for SOC 2136 in 2023 was different from 2024. Any system that hardcodes going rates rather than pulling from a regularly updated source will drift out of compliance within 12 months.

For the current going rate table and a working eligibility check against real applicant parameters, ImmigrationGPT maintains an up-to-date implementation.

This post covers the technical structure of UK Skilled Worker salary thresholds as of September 2026. Immigration rules change. Verify against the current Home Office Skilled Worker Appendix before making compliance decisions.

UK Spouse Visa 2026: Calculating the Minimum Income Requirement — Where Compliance Logic Breaks Down

ImmigrationGPT — Mon, 07 Sep 2026 08:09:43 +0000

The problem isn't the threshold

The £29,000 Minimum Income Requirement for UK spouse visas sounds like a simple field to validate: sponsor_income >= 29000 → eligible. Most HR and compliance systems treat it that way. That's wrong.

The UKVI assessment logic is more granular, and several edge cases that are common in real workforces produce incorrect pass/fail outputs when you model them as a single threshold check.

Income categorisation matters before the comparison

UKVI doesn't aggregate across income types. The categories are mutually exclusive for assessment purposes:

Category A: Salaried and non-salaried employment (6+ months at current employer)
Category B: Salaried/non-salaried with <6 months at current employer, or recent employment gap
Category C: Self-employment, sole trader, limited company director
Category D: Non-employment income (rental, pension, investments)
Category E/F: Cash savings top-up

If the sponsor has both self-employment income and salaried income, they can't add them. They pick the category that applies to their primary income source, and only that income counts.

This breaks the naive "total income >= threshold" validation.

Category B edge cases

Category B is where most HR integration errors occur. It applies when the sponsor:

Has been with their current employer less than 6 months
Had a gap in employment in the past 12 months
Changed from self-employment to employment (or vice versa) within the last 12 months

For Category B, UKVI looks at both current employment income and income from any previous employer in the past 12 months — but only employment income, and the two employers must be distinct entities.

If your system is pulling the sponsor's income from their current payroll record only, it will misclassify Category B sponsors who have 12-month income that satisfies the threshold across two employers.

The savings top-up formula

If income is insufficient, savings bridge the gap:

required_savings = ((threshold - annual_income) * 2.5) + 16000

Example:

Threshold: £29,000
Annual income: £22,000
Gap: £7,000
Required savings: (7000 × 2.5) + 16000 = £33,500

Savings must be:

Held in a regulated financial institution
Continuously held for at least 6 months before application date
In the name of the sponsor, the applicant, or jointly (fully counted in all cases)

The 6-month rule is applied strictly. A transfer from a foreign account to a UK account 5 months and 28 days before application will fail the continuous holding test, even if the foreign account held the funds for years prior.

What income categories don't contribute

Building the exclusion list is as important as the inclusion logic:

Child benefit: not counted
Working Tax Credit / Universal Credit: not counted
Maintenance payments received: not counted
Income from the applicant (overseas partner): not counted at entry clearance stage
Casual work / informal economy income not evidenced by payslips: not counted

Child benefit in particular causes errors in financial aggregation pipelines — many APIs include it in "household income" figures, producing false positives if passed to an MIR check without filtering.

The threshold drift problem

£29,000 is the current MIR as of early 2026. It was £18,600 before April 2024, raised in stages. A further increase was planned but has not been confirmed. Any system that hardcodes the threshold needs a configuration point — not a constant — for this value.

The same logic applies to the savings floor (currently £16,000). Both figures have changed in the last two years and may change again.

Summary of failure modes in eligibility modelling

Error	Common cause
False positive for mixed income	Aggregating across UKVI categories
False negative for Category B	Only checking current employer payslips
False positive savings top-up	Not checking 6-month holding period
False positive benefit income	Including child benefit in income total
Stale threshold	Hardcoded £18,600 from pre-2024 rules

The MIR seems like a simple eligibility check. The edge cases are dense enough that they warrant a separate decision tree, not a single comparison operator.

For up-to-date information on current thresholds and acceptable evidence, ImmigrationGPT provides answers based on live Home Office guidance.

For general information only. Not legal advice. UK immigration rules change frequently.