The 2025–26 tax year ends on 6 April 2026. For sole traders and small landlords with qualifying income above £50,000, that is the date Making Tax Digital for Income Tax Self Assessment (MTD ITSA) takes effect. If you are reading this and your business is not yet set up, the clock is ticking — but there is still a path forward.

This article walks through what you need to do in the final weeks before 6 April, and how to structure your IT setup so you are not scrambling in the new tax year.

Why are so many SMEs still unprepared for MTD?

MTD ITSA has been postponed repeatedly since it was first announced. Each postponing cycle pushed the deadline further out, but also normalised delay. Many SMEs assumed the date would shift again. It has not — not this time.

The practical reason for the lag is straightforward. Most small businesses do not have an in-house IT team. The person who handles "the tech" is often balancing finance, operations, or customer delivery alongside it. When MTD ITSA finally lands, that person needs to:

• Select and configure MTD-compatible software

• Migrate existing records into the new system

• Set up quarterly submission workflows

• Train anyone involved in bookkeeping or tax preparation

None of these tasks are inherently complex. They do require focused time, and most SMEs have not yet carved that out.

What exactly does MTD ITSA require from your IT setup?

MTD ITSA is not a tax policy change in the traditional sense. It is a process requirement. HMRC expects you to keep digital records and submit tax data through compatible software, rather than filing a single annual Self Assessment return.

The five core requirements are:

1. MTD-compatible accounting software. Your software must be able to keep digital records and submit data to HMRC via an API. This rules out standalone spreadsheets or non-compatible accounting packages. Most major UK accounting software providers — including Xero, QuickBooks, Sage, and FreeAgent — are MTD-compatible, but you need to verify that your specific plan or tier supports the required API submissions.

2. Digital linking between records. HMRC requires that digital data flows between your accounting software and the submissions you make. Manual copy-and-paste into a web form does not satisfy this requirement. The digital link must be maintained throughout the process.

3. Quarterly submissions. Rather than a single annual return, you will submit four updates to HMRC during the tax year, plus a Final Declaration at year end. Your software needs to be configured for this workflow before 6 April, and your bookkeeping process needs to feed it consistently.

4. Access for authorised agents. If you use an accountant or bookkeeper, they will need appropriate access to your MTD-compatible software. This is not just a technical setup task — it requires agreeing data-sharing arrangements and ensuring the person handling submissions has the right permissions.

5. Record-keeping standards. Your digital records must cover all income, expenses, and tax-relevant transactions from the start of the tax year. If you are switching software mid-process, you need a plan for how historical data is transferred and validated.

What can you realistically achieve in the final weeks before 6 April?

If you have not started, the good news is that the technical setup for MTD-compatible software is rarely complex. The harder part is ensuring your business processes are ready to feed the system consistently. Here is what you can do in a focused sprint:

Week 1: Software selection and migration planning. Confirm that your chosen platform supports MTD ITSA submissions for your business type (sole trader or landlord). Map out what data needs to migrate — current year records only, or historical data for audit purposes? Set a migration deadline at least two weeks before 6 April to allow for testing.

Week 2: Data migration and validation. Move your existing records into the new system. This is where errors creep in. Cross-check migrated data against your previous year's figures. Verify that income categories, expense codes, and VAT status (if applicable) are correctly mapped.

Week 3: Workflow configuration. Set up your quarterly submission calendar. Configure the digital links between your software and HMRC. Run a test submission if possible — some providers offer sandbox environments for this purpose. Ensure anyone involved in the process has the right access and training.

Week 4: Dry run and contingency planning. Run through a full quarter-end cycle in the new system. Identify any gaps. Confirm that your accountant or agent has the access they need to file on your behalf if required.

This timeline is aggressive but achievable for a business that dedicates focused time to it. If you are working alongside day-to-day operations, you will need external support to compress the schedule.

Why IT standardisation matters more than you think at this stage

The temptation when facing a tight deadline is to rush the software switch and hope the details sort themselves out. That approach works for a one-off migration but creates ongoing risk if your IT environment is not standardised.

Standardisation means ensuring that your software configuration, data structures, and access controls follow a consistent baseline across your business. In the context of MTD ITSA, this matters because:

• Inconsistent chart of accounts structures between your old and new software create migration errors

• Ad hoc user permissions mean the wrong person might have access to tax-submission capabilities

• Non-standard data formats make it harder to validate that migrated records are accurate

If your business already works with an IT partner who enforces standardisation, the migration will be cleaner and faster. If you are operating ad hoc, this is the moment to build structure before the deadline creates pressure to cut corners.

See how standardisation creates control instead of guesswork in growing businesses. Understand the difference between control and guesswork.

What about Cyber Essentials and other compliance requirements?

Cyber Essentials is not directly part of MTD ITSA, but it is the other major compliance deadline converging around 6 April. Your certificate expires after 12 months, and if you were certified in March or early April last year, your renewal is due right now.

Under the updated scheme rules — the NCSC's Requirements for IT Infrastructure v3.3, replacing the previous set from 26 April 2026 — the marking criteria have been tightened, cloud services are now explicitly in scope, and a senior director must sign a compliance declaration. If your certificate is due for renewal around the same time as your MTD migration, you are looking at two significant IT projects running in parallel.

Prioritise carefully. MTD compliance is a legal requirement with a fixed deadline. Cyber Essentials renewal, while important, can sometimes be scheduled for the immediate weeks after 6 April if you need to compress your timeline. But do not neglect either one, because the consequences of missing Cyber Essentials — losing government contracts or failing a commercial client's security questionnaire — can be just as costly.

Learn more about our Cyber Essentials support.

What happens if you miss the 6 April deadline entirely?

HMRC has indicated that businesses which are late to join MTD ITSA will be automatically enrolled. You will not face an immediate penalty for the first cycle, but you will lose control over your migration timeline. HMRC will assign you a software provider and a start date that may not align with your business readiness.

The practical consequence is that you will be migrating under pressure, without the ability to plan properly. Your IT setup will be rushed, your staff may not be trained, and your data migration will lack the validation that a planned approach allows. It is not a catastrophe, but it is a suboptimal outcome that could have been avoided with a few weeks of focused preparation.

Can your existing IT support handle the MTD transition?

If you already work with a managed IT support provider, this is an opportunity to build on that relationship. A competent managed IT support provider can accelerate your MTD setup by handling the technical configuration while you focus on validating the data and training your team.

Before 6 April, have a conversation with your support provider about their MTD readiness plan. Ask specifically about:

• Their experience with MTD ITSA implementations for businesses of your size

• The typical timeline for a migration of your business size

• How they handle data validation during the switch

• Whether they support the quarterly submission workflow after go-live

If you do not yet have a managed IT support arrangement, or if your current setup is ad hoc, this deadline is a catalyst for building structure. A standardised IT approach — consistent software platforms, documented processes, clear access controls — makes MTD migration faster and reduces the risk of errors.

See how our standard-by-default approach to managed IT support works.

What about your backups and business continuity during the migration?

A software migration is a period of elevated risk. Your data is moving between systems. Access permissions are being reconfigured. Staff are learning new workflows. This is not the time to assume your backup arrangements are adequate without verification.

Before 6 April, run a restoration test on your critical backups. Verify that your off-site or cloud copies are current and that the restoration process is documented. If you have not tested recently, treat this as a priority task — because the last thing you need during an MTD migration is to discover that your backups are not recoverable.

Learn about our backup and business continuity service.

Taking action before the deadline

The IT setup required for MTD ITSA is not complex, but it does require focused time. If you are reading this in late March 2026, you have roughly five weeks before the 6 April deadline. That is enough time to complete a proper migration if you start now and do not treat it as a secondary priority.

Here is the minimum viable plan:

1. This week: Confirm your MTD-compatible software and begin planning the data migration

2. Week 2: Execute the migration with a two-week buffer before 6 April for validation

3. Week 3: Configure quarterly submission workflows and train your team

4. Week 4: Run a dry run of the first quarter-end cycle

5. Week 5: Final validation and contingency planning

If you do not have the internal capacity to execute this plan, bringing in external support is a practical option — not a sign of weakness. A competent partner can compress the timeline and reduce the risk of errors.

Ready to get your MTD setup right before 6 April?

We offer a Security Triage Baseline Review that covers your current IT posture, identifies compliance gaps, and produces a prioritised action plan. It is a practical starting point for SMEs that need clarity on where they stand and what needs to happen next.

Book a Security Triage Baseline Review

If you are unsure where to start, our team can help you meet both your compliance and MTD obligations.