Making Tax Digital · Sole traders
What an HMRC submission acknowledgement tells you
ONLY£15A MONTHA submission acknowledgement helps document what happened when figures were sent to HMRC.
A submission acknowledgement helps document what happened when figures were sent to HMRC. It should be retained with the relevant business, reporting period and approved summary. Different messages and identifiers have different meanings, so a technical reference alone is not always proof of acceptance.
Distinguish the request from the outcome
Software may record an attempt, a request identifier, a response or an accepted submission. A correlation identifier can help support investigate a problem without proving that HMRC accepted the update.
Check the status shown by the software and the meaning explained in its current documentation. If the result is uncertain, verify it through the supported status or support process before treating the obligation as complete.
Retain the context
Save the person or client reference, business, tax year, period, submission time and accepted result where available. Keep the version of the figures that was approved. If a later correction changes the totals, retain an explanation linking the earlier and current versions.
An acknowledgement is evidence of reporting, not a tax clearance certificate. It does not establish that every expense is allowable, every income source is complete or an outstanding tax bill has been paid.
Worked example: two attempts
The first attempt returns an error and a technical reference. The second returns an accepted outcome. The business retains both records but marks the accepted submission as the completed reporting event.
Keeping only the first reference could confuse a later review. Keeping only a screenshot with no business or period could also make it difficult to establish what was actually sent.
Keep the evidence connected to the figures
Your digital record should explain the amount, date and nature of the transaction. Keep the invoice, receipt, statement or other evidence that supports it. A photograph can make a paper document easier to retain, but a folder of photographs alone does not create complete transaction records.
For sole traders, HMRC normally requires business records to be kept for at least five years after the relevant 31 January filing deadline. Keep them longer where the rules for a late return, enquiry or other circumstances require it. Check the record-retention guidance.
Make the records usable by your future self. Include a short explanation where a bank description is vague, retain the calculation behind a business-use split and make corrections traceable. For a missing receipt, try the supplier account, email confirmation or a replacement invoice before relying on incomplete evidence.
At review time, compare your records with the bank or payment account and investigate differences. Equal totals are useful, but two errors can cancel each other out. A sample of individual transactions can reveal a duplicated purchase or an omitted customer receipt that a totals-only check misses.
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.
Make responsibility visible at each stage
An effective practice process identifies who supplies the records, who resolves queries, who reviews the figures and who submits. Record those responsibilities in the engagement and workflow. Do not rely on the assumption that somebody else has completed the final step.
Agent authorisation is also separate from client consent to a commercial service. Use HMRC's correct MTD authorisation process and the agent's own access. A client should not hand over their Government Gateway password simply to make the process more convenient. HMRC explains how to authorise an agent.
Track each relevant business and period. A green client-level indicator can hide an outstanding property update if the sole-trade update has been completed. Store the approved figures and acknowledgement against the correct record.
For recurring work, use a short exception list rather than sending the client every transaction again. Give each question a reference, amount and clear request. Access controls and a secure reply route matter, especially where the same practice handles several family members or businesses. Good workflow design reduces repeated questions without replacing professional judgement.
Store evidence where you can retrieve it
Use a consistent business-and-period filing structure and the service's available export options. Confirm retention arrangements rather than assuming indefinite storage. If an adviser submits, agree how the accepted result and approved figures will be made available to you.
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.