MTD for Income Tax: who needs it and how to prepare

1. Start with the person and business structure

MTD for Income Tax is relevant to affected sole traders and landlords, subject to income thresholds and exemptions. It is not a rule that every limited company must join merely because it has sales. HMRC's entry-date guidance explains who needs to use the service and the current position for partnerships.

Start by identifying the person whose income is being considered. A trading name does not tell you whether the activity belongs to a sole trader, a partnership or a company. The same commercial sector can contain several structures with different reporting arrangements. A food wholesaler operating as a sole trader needs a different scope discussion from a company selling the same products.

Collect the recent tax returns and a short explanation of the structure. Where there are several activities or property interests, list them separately. This helps your adviser establish which income and records belong to the assessment before discussing software or a reporting calendar.

2. Check the phased start dates against the relevant year

HMRC's current timetable links qualifying income in an earlier tax year to the later start date. Over £50,000 in 2024 to 2025 means entry from 6 April 2026; over £30,000 in 2025 to 2026 means entry from 6 April 2027; and over £20,000 in 2026 to 2027 means entry from 6 April 2028, subject to exemptions. Check the official timetable for your position.

The reference year matters. Comparing the threshold only with today's bank balance or this month's sales does not answer the question. Find the relevant return and identify the figures used. If the business began, ended or changed during the period, describe that clearly so the position can be reviewed.

For someone already in the April 2026 group, the priority is current compliance and complete records from the appropriate point. For someone entering in April 2027, the preparation window can be used to agree the system and responsibilities before the next tax year begins.

3. Understand qualifying income before looking at profit

Qualifying income is based on relevant gross self-employment and property income, before expenses, with the applicable sources considered together. It is not simply the profit left after costs. HMRC provides detailed examples and special circumstances in its qualifying income guidance.

For illustration, consider someone with £24,000 of self-employment income and £12,000 of relevant property income in a reference year. Adding those simplified figures gives £36,000. That is a different question from calculating the profit or taxable result of either activity. The example is fictional and leaves out any special circumstances that could affect the actual assessment.

A wholesale business can have high sales and substantial purchase costs. The owner may think of the small margin as “my income”, while the threshold assessment is concerned with a different measure. Label gross receipts, costs and profit clearly in your records so those conversations do not become confused.

4. Distinguish MTD for Income Tax from other reporting

Businesses can have several reporting obligations at the same time. VAT arrangements, payroll, company accounts and an individual's Income Tax reporting do not become one process just because a software product offers several modules. Identify the taxpayer, tax and period for each task.

A sole trader who is VAT registered may already use a digital system for VAT but still need to check the separate MTD for Income Tax position. A company owner may have personal Self Assessment questions as well as company accounting work. Your accountant can discuss how the records connect while keeping the legal and administrative responsibilities distinct.

Write a simple reporting map with a row for each obligation, the responsible person, software and deadline source. This prevents a successful submission in one module from being mistaken for completion of another task. It also makes handovers clearer when bookkeeping, tax and payroll work are handled by different people.

5. Review exemptions using the facts

There are automatic exemptions and exemptions that require an application. Digital exclusion can be relevant in some circumstances, but unfamiliarity with software alone is not the same as an accepted exemption. Read HMRC's exemption guidance and discuss the evidence and process that apply.

If health, disability, religious beliefs or access issues affect your ability to use a digital process, explain the practical circumstances. The question is what is reasonable for the person involved, rather than whether a family member finds software easy. An adviser can help identify the relevant questions, but an exemption should not be assumed simply because a reporting routine feels inconvenient.

Keep correspondence and the reasons for any decision with the tax records. If circumstances change later, revisit the position. Someone who is exempt still needs to consider their ordinary reporting obligations. A clear record avoids treating an exemption from one digital requirement as a general exemption from tax administration.

6. Map the records you already have

Before choosing a product, identify where transactions originate. A wholesale business may create sales invoices in one system, record stock in another and keep supplier documents in email folders. A landlord may receive agent statements and bank deposits while keeping repair invoices separately. The system map should describe these sources.

For each source, note how information reaches the accounts, who checks it and how errors are found. Look for duplicate entry, missing documents and manual totals that cannot be traced back. These are record-quality problems that a new application may not solve automatically.

Use the map to define the intended routine. For example, sales records may be transferred using an approved export, purchase invoices captured in a shared document process and bank items reviewed weekly. The exact arrangement should be discussed with the adviser and software provider. A useful system follows the real flow of information rather than requiring the owner to remember every transaction at quarter end.

7. Choose software around compatibility and the actual work

Use HMRC's compatible-software guidance to check the relevant functionality. A general bookkeeping application or spreadsheet is not automatically a complete MTD reporting solution. The combination used needs to support the requirements that apply.

Then consider practical fit. Can the system handle the way invoices are issued, the bank accounts used and any separate activities? Can the people keeping records operate it consistently? What access will the accountant need? What is included in the price and what requires another product or service?

Ask for a demonstration using realistic transactions, including refunds, transfers and supplier credits. A tidy sample dashboard is less informative than seeing how your ordinary complications are handled. Keep the decision criteria written down so that compatibility, usability and cost are assessed together rather than selecting the first familiar brand name.

8. Agree who does what before the first update

Digital reporting still needs people to collect documents, record transactions, review classifications and authorise submissions. Agree the responsibilities early. A vague understanding that “the software sends it” leaves questions about who checks the records and what happens when information is missing.

A simple responsibility schedule can identify who raises sales invoices, uploads purchase evidence, reviews bank items, resolves questions and handles the submission process. Include deadlines for supplying information to the accountant. These should leave time before the formal reporting deadline for review and corrections.

Also agree who receives notices or software alerts and what happens if that person is absent. An owner may assume the bookkeeper sees every notification, while the bookkeeper assumes the accountant does. Clear communication is a practical control, particularly when the same business has several reporting routines running together.

9. Understand the purpose of quarterly updates

Quarterly updates provide information from the digital records through compatible software. They are not four separate annual tax returns. Under the current process, updates cover the year to date for the relevant update period, allowing records to be corrected in subsequent cumulative information. HMRC explains the periods and deadlines in its quarterly update guidance.

For the business, the useful consequence is a more regular review of records. Missing supplier invoices and unexplained bank items should be identified through the year instead of left for a single annual sorting exercise. That routine can also support financial reporting, although the tax update and management report serve different purposes.

Do not mistake a software estimate for a final agreed tax position. The year-end process and other relevant information still matter. Keep reporting status, business performance and tax planning as connected conversations with clear explanations of what each figure represents.

10. Keep the annual return in the plan

The annual Self Assessment return remains part of the process. For an affected MTD year, it is completed and submitted through the compatible-software arrangements after the relevant adjustments and other return information are dealt with. HMRC's annual return guidance explains this stage.

Keep a year-end task list alongside the quarterly routine. It can include information not resolved within regular transaction entry, relevant personal income documents and questions requiring review. Regular updates do not make those tasks disappear. They can provide a stronger starting point if the records have been maintained well.

The tax year before entry also needs attention. A person starting MTD in April 2026 may still be preparing the 2025 to 2026 return through the usual arrangements. Label each year's process clearly. This prevents the new digital routine from distracting attention from an earlier return that remains unfinished.

11. What this means for a sole-trader wholesaler

Wholesale records often involve more than simple bank receipts. Customer invoices, supplier credits, overseas purchasing and stock movements need a clear information trail. The accounting method and reporting scope determine the treatment, but the underlying commercial facts should be recorded consistently.

Begin with the purchase and sales ledgers and how they connect to the bank. Explain whether one customer payment settles several invoices, how returns are recorded and who holds import documents. Then consider how the digital system will preserve those connections. A bank feed alone may not provide enough explanation.

Stock information can remain important for the business's accounts and management decisions even when a particular tax update is based on a different reporting view. Do not discard operational records because a submission screen asks for fewer totals. Keep the information needed for the agreed accounting work and discuss how the different outputs fit together.

12. Move systems without losing the opening position

A system transition needs an agreed date and a clear opening position. Identify the bank balances, records carried forward and transactions that will remain in the old system. Keep a copy of the old information so earlier questions can still be answered.

Decide how invoices spanning the change date will be handled. A customer may pay an invoice raised in the previous system, or a supplier may send a credit against an earlier purchase. These ordinary events need a process so the new records do not become disconnected from their history.

Run a small reconciliation after the first set of transactions has been entered. Check that the opening information and new movements connect to the bank and ledger records. This is a more useful test than merely confirming that the new application can be opened. A transition should create continuity, not just a fresh screen.

13. A fictional readiness review

Imagine a sole-trader food wholesaler whose invoices are issued from a sales application, purchases are stored in email and the bank is reviewed only before the annual accounts. The owner has checked the applicable MTD entry date with an adviser. The following example illustrates organisation rather than asserting any client's actual compliance status.

The readiness review identifies three practical gaps. Supplier documents are not collected in one place, sales refunds are not always linked to the original invoice and personal transfers are not consistently labelled. The owner and bookkeeper agree a weekly document routine, a standard credit-note reference and a bank review list.

Software selection then focuses on connecting those records to the agreed reporting process. A trial period tests ordinary transactions and a review timetable is set. The improvement comes from the combined routine: people know what to do, the evidence can be found and the accountant receives information in time to discuss questions.

14. Questions to ask before committing to a setup

• Which taxpayer and income sources are in scope?
• Which reference tax year establishes the start date?
• Is an exemption relevant, and does it need confirmation or an application?
• Which software functions cover the digital records, updates and annual return?
• How will existing records and opening information move into the process?
• Who records transactions, resolves questions and handles submissions?
• When does the accountant need the information?
• How will invoices, credits and bank items stay connected?
• What access and document-sharing arrangements are needed?
• How will the routine be reviewed when the business changes?

Write the answers in a short setup note. It becomes a reference for the people involved and helps distinguish software capability from the work included in the accountant's engagement. The more specific the answers are to your business, the more useful the plan will be.

A useful first-month implementation plan

In the first week, assemble the relevant return, income-source list and current reporting map. Ask the adviser to confirm which facts still need checking before the setup is agreed. In the second week, demonstrate the ordinary transaction flow, including a customer refund and a supplier credit. Those examples reveal whether the proposed process preserves the information needed for review.

Use the third week to agree access, document storage and the question-handling routine. Make sure someone can identify which records have been supplied and which remain missing. A shared folder without naming conventions can recreate the same uncertainty as a box of paper.

In the fourth week, review a small set of completed records against the bank and source documents. Write down any corrections needed and who will make them. This is an operational preparation plan rather than a statutory timetable. It should be adapted to the entry date and the actual state of the records, including any catch-up work already required. A short, tested routine is easier to sustain than a long setup document nobody uses.

15. Turn the requirements into a manageable routine

The most effective starting point is a clear assessment followed by a practical record plan. Confirm the person, income, reference year and entry date. Then map the records, choose compatible arrangements and agree the responsibilities. Test the process with ordinary transactions before relying on it for a deadline.

Read our guide to organising records for quarterly updates for a detailed workflow. The two guides serve different purposes: this one helps establish the scope and preparation decisions, while the companion article explains the recurring information routine.

CRV Gudka & Co's dedicated Edgware team can discuss the bookkeeping and tax work relevant to your circumstances, with specialist understanding of wholesale and food-import records. Contact the practice with your business structure, current records and the MTD question you need addressed. The proposed support and responsibilities can then be agreed around the actual requirement.