Why connecting to HMRC for MTD IT feels confusing
Key Takeaways
The HMRC setup is doing three distinct jobs: establishing the practice, authorising the client relationship, and creating the client’s MTD for Income Tax obligations.
Confusion usually comes from those steps being missed or conflated, especially authorisation and sign-up.
Once those steps are complete, the software part becomes simple.
The setup before the setup
Before the MTD software can connect to HMRC and submit quarterly updates, some setup has to happen with HMRC.
In practice, most connection issues start here. The usual cause is not the software itself, but HMRC steps being missed or conflated. Once you separate those steps, the setup becomes easier to follow.
In simple terms, the process is establishing that:
the practice exists in the right HMRC service
the practice has permission to act for the client
the client is registered for MTD for Income Tax, with quarterly obligations created
That sequence is the key to the whole connection.
The practice exists
The first step is having an Agent Services Account.
This establishes the practice in HMRC’s newer digital agent services. It gives HMRC a digital identity for the practice. Without it, there is nothing for the software connection to sit on top of.
The Agent Services Account is also part of a wider shift in how HMRC is delivering digital agent services. MTD for Income Tax sits there alongside services such as VAT digital handshake authorisation, Trust Registration Service and Capital Gains Tax on UK property, while older services such as Self Assessment and Corporation Tax still sit in HMRC online services for agents.
That matters, but it is only one part of the setup. The Agent Services Account establishes the practice. It does not create the client relationship or register the client for MTD for Income Tax.
The practice has permission
The next step is client authorisation.
For existing clients, this means moving an existing Self Assessment authorisation from HMRC online services for agents into the Agent Services Account, so HMRC can use that relationship for MTD for Income Tax.
For new clients, this means creating a new authorisation through HMRC’s digital handshake. That creates the practice-client relationship directly in the newer digital service, rather than bringing it across from the legacy one.
Different route, same outcome: HMRC can recognise that your practice is authorised to act for that client in the right digital service.
Just as importantly, authorisation is not sign-up. It gives the practice the right to act, but it does not sign the client up for MTD for Income Tax.
The client has obligations
The next step is signing the client up for MTD for Income Tax.
This is the step that registers the client to submit quarterly updates. It includes choosing the tax year they are starting from. That detail matters, because if sign-up happens after a tax year has already started, there may already be quarterly obligations in that year that need to be filed promptly.
What this creates is the HMRC side of the filing relationship the software needs. Once those obligations exist, the client is live in MTD for Income Tax and HMRC has generated the records needed for linking and submission.
This is the point where MTD for Income Tax becomes operational for the client: not just authorised, but registered, with live obligations behind it.
Now the software
Once that HMRC groundwork is in place, the software part is much simpler.
There are two connections to make. The first is the practice connection, using the practice’s Agent Reference Number, which authorises the software to act for the practice in MTD for Income Tax.
The second is the income source connection, using the client’s NINO, which links the client’s income sources to the HMRC records the submissions will be made against.
In Solo, those two layers are handled separately: first the practice, then the client’s income sources.
If the practice is already connected, new clients can have their income sources connected as part of setup. That is where the process starts to feel more proportionate: once the HMRC groundwork is done, the software connection becomes straightforward.
Once connected, the software can pull in obligations, populate dashboards, and enable the submission of quarterly updates to HMRC.
Why this matters
The setup is doing four distinct jobs: establishing the practice, establishing permission, creating the client’s obligations, and then connecting the software to all of that.
Once you see it in that sequence, the process feels less arbitrary. And once the practice connection is in place, the rest of the setup becomes much easier to manage.
The practice exists. It has permission. The client has obligations. Then the software can do its job.
