Viktor.comAn AI coworker that actually does the work
SMS System
UK sponsor licence compliance — track every deadline
11 followers
UK sponsor licence compliance — track every deadline
11 followers
UK sponsor licences are revoked for missed deadlines — not deliberate fraud. SMS System fixes that. AI extracts every CoS field on upload. Salary compliance checked by SOC code including the SW 14.3B rolling-window rule. 10-working-day UKVI reporting clock starts automatically. Audit packs generated in one click. Plus: HR portal, employee self-service, GPS clock in/out, and Pro tier task management — all audit-logged. Built for care, construction, hospitality and IT. First employee free.
Uploaded a CoS and watched it pull out every field without me touching a thing. The SW 14.3B rolling check is the bit I never want to do manually again.
@kranalayan39574 Really glad the extraction landed well — the SW 14.3B
rolling-window check was the one we knew nobody wanted
to do manually. Three months of pay data, variable
hours, bonus components — it adds up fast. Exactly
why we built it into the engine rather than leaving
it as a manual calculation. Thanks for trying it out!
@kranalayan39574 Glad the SW 14.3B check caught your attention —
it's the one most compliance tools skip entirely.
If you want to see it on your own CoS documents,
first employee is completely free at smssystem.co.uk,
no card required. Takes about 2 minutes to upload
your first CoS and see the compliance check run.
One thing I'd love to see is a bulk CoS upload that pre-flights the whole batch and flags which ones will fail SOC code salary checks before you even submit them to the sponsor system. Would save a ton of back-and-forth when onboarding a cohort of carers or hospitality staff at once.
@kaanc8iq This is exactly the right ask — and honestly something
we've been thinking about. The current bulk upload
processes each CoS after upload; a pre-flight that
runs the SOC + salary check across the whole batch
before you commit would save a significant amount of
back-and-forth, especially for care home onboarding
cohorts where you might have 20 CoS documents and
want to catch the salary issues before they become
reportable changes.
Adding it to the roadmap. If you want to follow
progress or give more detail on your specific workflow,
drop us a note at support@smssystem.co.uk.
The SOC code salary check caught a borderline case on one of my test CoSes that I would have missed manually. Feels like something built by people who have actually dealt with a sponsor licence audit.
@nehiraltunobvv This is exactly the scenario we built it for — the
borderline cases are the ones that catch sponsors
out. A salary that looks fine against the general
£41,700 threshold but falls short of the SOC-specific
going rate for that job code, or a variable-hours
contract that passes the annual check but fails the
SW 14.3B rolling-window. The manual calculation is
genuinely error-prone.
Glad it caught it before it became a reportable
change. If you're testing further, the bulk upload
handles multiple CoS documents at once — same checks
run across the whole batch.
The SW 14.3B rolling-window check is a detail most sponsors miss until it's too late, so seeing it baked into the AI extraction on upload is genuinely thoughtful work.
@kadriye3zo7 Thank you — SW 14.3B was the rule we knew we had
to get right. Most platforms check salary against
the general threshold and stop there. The rolling
window changes the calculation entirely for
monthly-paid and variable-hours workers — a salary
that looks compliant annually can fail quarterly,
and that's when sponsors get caught.
Baking it into the extraction flow rather than
making it a separate manual check was deliberate —
the moment you upload a CoS is exactly when you
need to know, not six months later when a payslip
drift triggers an alert.