HMRC multi-factor sign-in for agent accounts from 28 September 2026
Every agent account without multi-factor authentication is being switched on in daily batches from today until 15 October. An account with out-of-date access code settings will be locked out on the day its batch activates.
Key points
- Every remaining ASA and OSA switches on between 28 September and 15 October 2026; a batch cannot be deferred once it is due
- MFA activates per Government Gateway identifier, taking every staff login tied to it offline in the same instant
- An authenticator app is HMRC's preferred method; set up at least one backup (SMS or voice call) on every login
- Outdated access code settings risk an immediate lockout with no grace period
- Shared logins remain valid if the password and MFA method change the day someone with access leaves
General information for practice owners, accurate as at 28 September 2026. Details are as published by HMRC and the professional bodies. Use HMRC's own Tax Agent Handbook guidance as your working reference during switch-on.
Today, 28 September 2026, is the first day HMRC begins switching on mandatory multi-factor authentication (MFA) for every agent account that has not already opted in. By 15 October, every Agent Services Account (ASA) and legacy Online Services Account (OSA) in the country will require a one-time code on top of the usual Government Gateway sign-in. The code becomes a condition of signing in. If your firm did not take one of the two voluntary windows in July and August, your accounts are now in the mandatory queue, and HMRC will switch them on in a daily batch without further individual notice.
The switch-on is live now. A firm with out-of-date access code settings can lose access to a client's VAT return or PAYE dispute in the week it is due. Work through the checklist for this week before your batch activates.
The switch-on timetable
Two voluntary phases let agents choose their own switch-on date ahead of the mandatory rollout; both have now closed, and HMRC reports that more than 20,000 agent accounts, across roughly 13,000 firms, were switched on through them voluntarily. All other agent accounts are switched on automatically.
- Voluntary phase 1Opt-in by 30 Jun 2026Accounts went live 15 Jul 2026
- Voluntary phase 2Opt-in by 31 Jul 2026Accounts went live 19 Aug 2026
- Mandatory switch-on28 Sep – 15 Oct 2026Every remaining ASA and OSA, in daily batches activated 8–9am, Monday to Thursday
Mandatory window: batch days
| Mon | Tue | Wed | Thu | Fri | Sat | Sun |
|---|---|---|---|---|---|---|
| 28 Sep8–9am | 298–9am | 308–9am | 1 Oct8–9am | 2 | 3 | 4 |
| 58–9am | 68–9am | 78–9am | 88–9am | 9 | 10 | 11 |
| 128–9am | 138–9am | 148–9am | 15 Oct8–9am |
Which accounts are affected
Both account types agents rely on are in scope. The ASA handles Making Tax Digital, trust registration and a growing share of VAT and PAYE work; the older OSA is still used to file Self Assessment and Corporation Tax returns for longer-standing clients. Both are included, and the rollout applies to sole practitioners and firms of every size.
MFA switches on for every login tied to a given Government Gateway identifier at the same time. If your practice has used one shared Government Gateway ID for filing across several staff, all of them lose access at the moment that identifier's batch is activated, including anyone who is part-way through a filing.
- Staff login
- Staff login
- Staff login
- Staff login, part-way through a filing
The three ways to receive a code
Once MFA is live, signing in means entering a one-time access code in addition to the existing user ID and password. HMRC offers three delivery methods, and firms are expected to have at least one primary and one backup configured on every login before their batch activates.
| Method | How it works | HMRC's guidance |
|---|---|---|
| Authenticator app | Generates a time-based code on a smartphone; no phone signal needed once set up | Recommended primary method |
| SMS text message | Six-digit code sent to a mobile, valid for 15 minutes; not available to all countries | Suitable backup |
| Automated voice call | Call from 01749 608007 reads out a six-digit code, valid for 15 minutes | Backup for landlines or staff without a smartphone |
HMRC recommends the app because it works without signal and does not depend on a text or call reaching the right person at the right desk. The voice-call option suits staff who work from a landline or do not yet have a smartphone set up for an authenticator app, and HMRC's guidance treats the call-back number as a permanent route.
Choosing individual or shared logins
Each firm needs to decide whether to move to individual logins for every member of staff or keep a shared login secured with MFA. HMRC's stated preference is the former — named credentials for each person, with client work allocated to individual users — and it is testing a bulk client-allocation tool for legacy OSAs, expected before the end of 2026, to make that change easier for firms with large client banks split across several staff.
Worked example: an eight-partner, 30-staff general practice choosing a login model
The individual-login route
Every one of the 30 staff gets their own Government Gateway credentials and their own MFA method. Client work is allocated to named users. It is the more secure model. When someone leaves, the firm removes that one person's access and the rest of the team carries on.
The cost is upfront: reallocating several hundred clients across 30 named users by hand, on an OSA that was never built for bulk reassignment, is likely to take several days of admin this autumn.
The shared-login route
The firm keeps its existing shared Government Gateway ID, adds an authenticator app as the MFA method, and installs it on two or three trusted managers' phones. Set-up takes an afternoon.
The cost comes later: every time someone with access to that shared login leaves the firm, the password and the MFA method both have to change immediately, or that person retains the ability to sign in indefinitely.
Illustrative figures based on a firm of this size; the right call depends on staff turnover and how your client base is currently split across logins.
For a firm under about 15 staff, the shared-login route is a practical choice for now.
For a larger firm with regular staff turnover, the one-off admin cost of individual logins is likely to be lower than the ongoing work a shared login needs every time someone hands in their notice.
How firms get locked out
The main risk is a firm reaching its batch's activation window with access code settings that are out of date: a mobile number that changed two years ago, or an authenticator app that was never installed. HMRC has been explicit that outdated options can lock an account out the moment MFA switches on, and there is no grace period built into the process to fix it retrospectively once that has happened.
The second risk comes from how the firm handles staff changes. A firm using a shared login that does not update the MFA method when a member of staff leaves keeps a security gap open, because the departed employee's device or number can still generate a valid code.
Both risks fall in a busy period. The mandatory window overlaps with MTD for Income Tax's quarterly filing cycle and the run-up to Self Assessment season. A lockout can stop a client return being filed on the day it is due, for a reason within the firm's own control.
Checklist for this week
Each step is straightforward. This season also brings mandatory tax adviser registration and HMRC's own auto sign-up drive for MTD, so put the MFA checks in the diary this week with a named person responsible for them.
- List every ASA and OSA login your firm holds, and which Government Gateway identifier each sits under. The rest of the checklist depends on this list.
- Appoint at least two administrators per account, so a reset is possible if the usual person is unavailable, or is the one locked out.
- Decide individual or shared logins for each account, based on staff numbers and turnover.
- Set an authenticator app as the primary method on every login, with at least one backup delivery method configured alongside it.
- Remove access for anyone who has left the firm, and check that shared credentials were rotated when they went.
- Check third-party and practice-management software that logs into HMRC systems automatically — bulk filing tools and integrations may need reconfiguring once a code is required at sign-in.
- Check access again the morning your batch activates, between 8 and 9am on a weekday, and confirm every login still works.
Frequently asked questions
What is changing on 28 September 2026?
HMRC has begun switching on mandatory multi-factor authentication (MFA) for every Agent Services Account and legacy Online Services Account that hasn't already opted in during the two voluntary phases in July and August. From 28 September to 15 October, HMRC is enabling MFA on all remaining accounts in daily batches, activated between 8am and 9am, Monday to Thursday. From the moment your account's batch runs, signing in requires a one-time code — from an authenticator app, a text message, or an automated voice call — on top of the usual Government Gateway user ID and password. An account cannot opt out or defer once its slot arrives, so make sure your access code settings are ready before it does.
Which HMRC accounts does this affect?
It affects both of the account types agents use: the Agent Services Account (ASA), which handles Making Tax Digital, trust registration and some VAT and PAYE work, and the older HMRC Online Services for Agents Account (OSA), still used for Self Assessment and Corporation Tax filing for many longer-standing clients. MFA switches on for every login tied to the same Government Gateway identifier at the same time. If several members of staff share one set of credentials to file client work, all of them lose access simultaneously the moment that identifier's batch activates, unless the new access code settings have already been configured and communicated to the team.
What happens if we missed both voluntary phases?
Your accounts are switched on during the mandatory window running from 28 September to 15 October 2026, alongside every other agent account that did not opt in. HMRC is not sending individual notice of which day your batch activates, so the practical approach is to treat every account as due at any point in that fortnight. If your current access code options are out of date — a landline that is no longer staffed, an old mobile number — that is the setting to fix first, since HMRC has been explicit that outdated options can lock an account out the moment MFA switches on, with no grace period to sort it out afterwards.
Can we carry on using one shared login across the team after MFA switches on?
Yes, shared logins remain allowed. HMRC's preference is individual staff logins with client work allocated to named users, because that is the more secure model. It is testing a bulk client-allocation tool for legacy OSAs before the end of 2026 to make that switch easier for firms. A shared login secured with an authenticator app or password manager remains a valid route, provided the password and MFA method are changed the moment anyone with access leaves the firm. The administrative risk of a shared login is failing to remove a leaver's access when they go.
What should we do if our firm gets locked out?
Contact HMRC's Online Support Helpdesk, using an alternative registered contact method if the one on file is now the thing you cannot access. For this reason HMRC recommends every firm nominate at least two administrators before switch-on: a second person who can reset settings if the first is unavailable, travelling, or happens to be the one who is locked out. Preventing a lockout takes less effort than fixing one: check your access code options today, confirm at least two delivery methods are current on every login your firm holds, and do not leave that check until the week your batch is due to activate.

Freeing up partner time
MFA, mandatory tax adviser registration and the MTD rollout all take partner time. To talk about freeing up capacity, bringing in fractional support, or what your practice is worth, book a confidential call with us.
Book a confidential call
Andy Jackson, co-founder