Making Tax Digital · Sole traders
The day before an MTD deadline: a focused filing review
ONLY£15A MONTHThe day before filing is a time to identify the real blocker and complete the remaining steps in order.
The day before filing is a time to identify the real blocker and complete the remaining steps in order. Avoid restarting finished work or assuming an emergency service can instantly reconstruct missing records. Establish what is ready, what is uncertain and what evidence is needed.
Triage the remaining tasks
First check access and submission status. If an update is already accepted, retain the evidence and confirm whether another business remains outstanding. If it is only drafted, identify the missing review or approval.
Next check completeness. A missing account or month is more fundamental than a preferred label on an otherwise correct record. Resolve large unexplained transfers, duplicate imports and net settlements before relying on the category totals.
Ask a precise question when help is needed
Provide the business, period, error or disputed transaction and the steps already taken. Confirm the support team's availability and scope. A published target or standard service description does not guarantee immediate emergency tax review.
Keep technical evidence if the problem affects submission. If the result of an attempt is unknown, check status before repeating it. Do not treat every unsuccessful screen interaction as proof that HMRC received nothing.
Worked example: a completed review without submission
A client and accountant have approved the figures, but the practice workflow shows no accepted outcome. The submission owner checks the tax software, confirms that the update remains unsent and completes the supported process.
The final evidence is then attached to the approved version. The task was a missing final action, not a need to rebuild the entire quarter.
A review that checks more than the total
Start with coverage: the correct person, business and period, plus all relevant accounts and cash records. Then look at completeness. A feed can be connected today while still missing an earlier week. Confirm the earliest and latest transactions against the source.
Next, inspect unusual items. Large transfers, loan receipts, refunds, net settlements and private purchases often need more context than a bank description provides. Check for duplicate imports where a statement overlaps a live feed. An automatic warning is useful evidence to investigate, not proof that the entry must be removed.
Finally, review category totals. A category unexpectedly showing zero, a large increase or a negative amount deserves an explanation. You do not have to make every annual tax adjustment at this stage, but you should understand the records behind the summary you approve.
HMRC explains what quarterly updates contain. Keep the approved version and the resulting acknowledgement together. If something later changes, correct the source record and use the software's supported update process so you can explain which figures are current.
Keep the reporting dates separate from payment dates
The standard first update for 2026/27 covers 6 April to 5 July 2026 and was due by 7 August 2026. The second covers 6 April to 5 October 2026 and is due by 7 November 2026. The third and fourth deadlines are 7 February 2027 and 7 May 2027. These are cumulative updates, not four isolated sets of three-month totals.
Calendar periods have different cut-offs and the same filing deadlines. Check the setting for each business rather than assuming the dates from a bank statement. HMRC lists both reporting calendars.
The annual return for 2026/27 is due by 31 January 2028. The earlier 2025/26 return normally remains due online by 31 January 2027. Keeping those years distinct avoids a common transition-year misunderstanding.
Payments on account, where required, follow their own January and July timetable. An update acknowledgement confirms a reporting event; it does not confirm that an outstanding tax bill has been paid. Check your actual HMRC account and payment obligations separately from the software's progress indicators.
Understand the first-year concession
HMRC states that there are no penalties for missing quarterly-update deadlines for the 2026/27 tax year. That concession does not remove the digital-record or quarterly-reporting obligations, and it does not make all tax returns and payments penalty-free. Read the precise penalty guidance.
Outstanding quarterly reporting must be dealt with before completing the relevant annual return. However, a missed August 2026 update should not be described as an automatic penalty on the separate 2025/26 return due in January 2027. The 2026/27 annual-return deadline is January 2028.
After the first-year concession, the points rules apply to missed quarterly deadlines as described by HMRC. Do not assume that multiple businesses create multiple points at the same deadline. Annual-return rules, late-payment penalties and interest require their own checks.
If you have fallen behind, establish what is outstanding and work through the supported catch-up process. Keep evidence of technical problems and contact the appropriate support team with the business, period and error details. The useful next step is a complete record and an accepted update, rather than guessing what a generic warning might mean.
End with a clear status
Record accepted, rejected or still unresolved, with the next action and owner. Use the rules for the actual tax year if late. Continue current-period records so the final-day effort does not leave the next update without a routine.
Take the next step
Avona.app offers a self-service route from £15/month. Bring your records together, review the figures and choose a workflow that fits your business. For professional help, discuss the scope and total price of Avona Concierge, managed by chartered accountants, before choosing a service.