Entity Setup
Technology Requirements Under MTD for Income Tax: What Software Developers Need to Know
HMRC has updated requirements and support for Making Tax Digital (MTD) for Income Tax—this article breaks down the technical obligations, changes for 2026/27, and what developers building compliant software must implement.
By NomadicTax Research Team • 5-8 min read • May 30, 2026
## Overview of MTD for Income Tax in 2026/27
From **6 April 2026**, **sole traders and landlords** with qualifying income over **£50,000** will be required to use MTD-compatible software, maintain digital records, and submit quarterly updates of income and expenses to HMRC. ([gov.uk](https://www.gov.uk/government/news/one-year-until-making-tax-digital-for-income-tax-launches?utm_source=openai))
## Recent Guidance & Changes for Developers (May 2026)
HMRC's **‘Use Making Tax Digital for Income Tax – Updates’** guidance was updated on **19 May 2026**. Key changes include:
- Clarifications on **quarterly update periods and deadlines**, specifying that updates automatically cover the full year-to-date period.
- New examples showing treatment of **student/postgraduate loans** and how other income sources are recorded.
- Updates to identity checks, software authorisation, and instructions connecting software to HMRC. ([gov.uk](https://www.gov.uk/guidance/use-making-tax-digital-for-income-tax/updates?utm_source=openai))
There is also a new communication for software developers—the **Edition 3 Newsletter** published **29 May 2026**—covering service performance updates and developer tasks. ([gov.uk](https://www.gov.uk/government/publications/edition-3-making-tax-digital-for-income-tax-software-developer-newsletter?utm_source=openai))
## Core Technical Obligations for Compliant Software
Developers building or updating software need to support:
- **Quarterly updates**: summarised income and expenses for each period, aligned with tax year start.
- **Digital record-keeping**: capturing income, allowable expenses, disallowed items, and integrating sources like student loans.
- **Income sources**: clarity on partnership profit shares, non-employment income etc. must be recorded properly.
- **Software authorization**: identity verification and secure connection to HMRC’s systems.
- **User guidance**: tools or modules that help taxpayers not miss deadlines or misreport periods.
## Developer Workflows & Compliance Strategy
- **Build a schedule** aligning to notice and update deadlines.
- **Implement identity checks** per HMRC guidelines.
- **Include sample scenarios** in product documentation: e.g., landlords, self-employed, multiple income streams.
- **Test deadlines and error handling**, especially for rejected period updates.
- **Ensure security and data protection**, as sensitive financial data will be flowing through your software.
## Example Scenario
A software firm is building a platform for landlords: the product must let users digitise rent income, expenses, loan interest, and also record whether they pay postgraduate loans, show year-to-date summaries, help them send updates per quarter and final submission—all while verifying user’s identity and connection to HMRC.
## Best Practices for Developers
- Subscribe to HMRC’s developer newsletters and stay alert to guidance updates.
- Conduct end-to-end testing ahead of launch or feature updates.
- Provide clear tooltips or help screens for complex areas, especially for mixed income or overseas income.
- Reach out to HMRC sandbox or contact points for clarifications wherever possible.
**Summary**: The digital transformation under MTD for Income Tax is well underway—software developers must align with defined timelines, updated guidance, and robust functionalities, so clients can meet compliance obligations smoothly.