MTD quarterly updates: a practical digital-records workflow

1. Define the reporting cycle before collecting data

Under the current MTD for Income Tax process, quarterly updates are cumulative, covering the tax year to the end of the relevant period. For standard periods, the deadlines are 7 August, 7 November, 7 February and 7 May. Calendar-period arrangements also exist. Check HMRC's quarterly update guidance for the periods that apply to your setup.

Record the selected period, the deadline and the internal date by which information must be ready for review. These are three different things. The end of a reporting period is not necessarily the final day to submit, and the accountant's document deadline needs room for questions.

At the time this guide was checked, October 2026, the next standard update deadline for the 2026 to 2027 cycle is 7 November. Use the calendar as a starting point for the agreed workflow, then verify the current obligations shown by the software and HMRC.

2. Identify every transaction source

List the systems and places that hold business information. They might include sales software, a payment processor, bank accounts, purchase emails, a document app and a stock spreadsheet. The purpose is to understand the full flow, rather than assuming that the bank captures every relevant detail.

For each source, identify the responsible person and how information is transferred into the records. A sales export needs a review for completeness; a supplier invoice needs a document reference; a bank transfer needs an explanation. Mark any points where transactions are entered twice or not entered at all.

For a food wholesaler, the source map may also show where freight documents and supplier credits are kept. Some information supports wider accounting or management work even where the quarterly update uses a simpler total. Preserve the commercial evidence rather than discarding it because it is not visible on a submission screen.

3. Create a usable digital record

HMRC describes the required digital-record information and the available simplifications in its digital records guidance. Check the requirements for your income source and circumstances. A digital record and an image of a receipt are connected pieces of evidence, but a photograph alone should not be assumed to complete every reporting task.

For practical purposes, a transaction should be identifiable by its date, amount, description and supporting reference. The agreed software process determines how those details are held and used. Make the description specific enough that a reviewer can understand the business event without asking the person who entered it to remember what happened.

A description such as “supplier payment” may be sufficient to begin matching a bank item, but it does not explain whether the payment covers one invoice, several invoices or an advance. The supporting records and allocation should make that connection visible.

4. Give sales records a consistent path

Decide how sales invoices, cash sales, customer refunds and credit notes reach the bookkeeping system. If the sales application can provide an export, check which fields it contains and how the total reconciles to its own reporting. Keep the original source accessible.

Use consistent customer and invoice references. They make it easier to connect later receipts and explain differences. When a customer pays several invoices together, the allocation should identify them. When a refund relates to a returned product, retain the reason and original sale reference.

For a wholesale business, review whether invoices and delivery information tell the same story. An invoice issued before goods leave, a rejected delivery or a changed order can raise accounting questions. The person maintaining records should not invent a treatment to remove a mismatch. Flag it with enough context for the agreed review.

5. Collect purchase documents near the time of ordering

Set a routine for collecting supplier invoices and credits. The person placing the order often knows where the document is, while the bookkeeper may only see a bank payment. Connecting the two early reduces later reconstruction.

For imported goods, create a reference that connects the order, supplier invoice, shipment and relevant additional-cost documents. Not every document arrives at the same time. A short outstanding-document list can show what is still expected and which person will follow it up.

Do not enter a supplier statement as another purchase merely because it resembles a list of invoices. Use it to check the underlying ledger. A repeated invoice reference or duplicate document can distort the record totals, so the routine should include a way to identify repeats. Consistent references are often more useful than an elaborate filing structure.

6. Review bank information regularly

A bank feed can speed up access to transactions, but it still needs review. Confirm that the date range is complete and that no items have been duplicated by a manual import. Match receipts and payments to their supporting records where the agreed process requires that.

Identify transfers between accounts, owner movements, finance payments and refunds instead of allowing them to be classified as ordinary sales or expenses by default. Software rules should reflect verified transaction patterns. An automatic category is a starting point for review, not evidence that the transaction is correct.

Keep a monthly reconciliation record that shows how the bank balance connects to the books. If a difference exists, retain the investigation and explanation. This creates continuity for the accountant and makes it easier to locate the period where a problem began, rather than trying to solve a year of differences at once.

7. Use an exception list instead of guessing

The exception list holds the items that need more information or a decision. Include the date, amount, source reference, question and person responsible. It may cover a missing invoice, a private element, an unexplained refund or a transaction spanning more than one reporting period.

Review the list on an agreed schedule. Questions that remain open for months are harder to answer, particularly where the person who ordered goods cannot recall the detail. Resolve ordinary factual questions close to the transaction and refer accounting or tax-treatment questions to the appropriate review.

When an item is resolved, keep the explanation with the record. Avoid deleting the question as though it never existed. A brief decision trail is useful for future reviews and can stop the same misunderstanding recurring. The aim is a manageable list of meaningful exceptions, not an alternative ledger containing every transaction.

8. Keep separate activities identifiable

If you have more than one self-employment or property income source, the records should preserve the distinctions needed for the reporting process. Discuss the arrangement with your adviser and software provider. A combined personal bank account can make source identification more important, not less.

Use labels or separate record areas that explain which activity a transaction belongs to. Where a cost relates to more than one activity or has a private element, keep the reasoning behind any proposed allocation. The reviewer needs the facts and the method, rather than a total that has already been split without explanation.

For landlords, agent statements should remain connected to the relevant property and owner information. For sole traders, a new activity may need discussion about how it is represented in the system. Maintaining clear source records helps the accountant understand the position when preparing updates and the annual return.

9. Build a small monthly close routine

A monthly close can be a short set of checks: sales completeness, purchase document collection, bank reconciliation and review of open questions. The business can then confirm which records are ready and which still need attention.

Give each check an owner. If the sales total needs confirming by someone using a separate application, ask that person to provide the report and date range. If supplier documents are missing, identify who will chase them. The bookkeeper should not have to infer that information from an unexplained folder of files.

Keep a simple completion note for the period. It might say that bank records have been reconciled, two freight invoices are outstanding and one customer credit is being reviewed. That status is more useful than “everything uploaded”, because it describes the quality and completeness of the information rather than the amount of activity.

10. Review the quarter before submission

Before the agreed submission stage, check that all relevant months are included and that the record totals have been reviewed. Compare the position with earlier information to identify movements that need explaining. A large change is not automatically wrong, but it should make commercial sense.

Review the exception list and establish how outstanding questions are being handled. The accountant and client should understand the information supporting the update and any remaining work. Do not treat a deadline as permission to create unsupported numbers simply to make the submission screen complete.

Keep the responsibility and authorisation arrangements clear. An update generated by software still belongs within an agreed process. The person handling the submission needs to know that the relevant review has happened, and the owner needs to understand what information is being sent. This is a practical control even when the technical transmission takes only a few moments.

11. Retain evidence of what was sent

After an update is sent, retain the confirmation and the relevant reporting information in the system used for the engagement. Record which period and income source it relates to. A simple status log prevents uncertainty about whether an action was prepared, reviewed or actually submitted.

If several people are involved, make the status visible to the person coordinating the records. The bookkeeper may need to know which information has been reviewed, while the owner may need to know which follow-up tasks remain. A submission confirmation should not be mistaken for a statement that every accounting question has been resolved.

Where an error is discovered, explain it and follow the correction process relevant to the records and reporting arrangements. HMRC's cumulative update guidance is useful here. Keep the reason for the correction so that later totals and earlier information can be understood together.

12. Preserve the route to the annual return

The quarterly process does not remove the year-end tax-return stage. Relevant adjustments and other return information still need to be reviewed. Use HMRC's annual-return guidance to understand that stage, and agree the information timetable with your adviser.

Maintain a separate list of year-end matters that ordinary transaction entry will not settle. Depending on the circumstances, these may include personal income documents, changes in business activity or explanations needed for the completed accounts. Regular record review gives these tasks a stronger foundation.

Also keep the earlier tax year in view where it uses a different reporting arrangement. The first year of a new routine can involve overlapping preparation tasks. Label documents and deadlines by year so that work on current digital records does not cause an earlier return to be overlooked.

13. Plan for late information and absence

Real businesses have late invoices, holidays, illness and staff changes. The routine should explain how those situations are handled. Identify a backup contact for document collection and make sure the record location is accessible through the agreed permissions.

For late supplier information, maintain a list showing the expected document and the transaction it relates to. Explain the gap during review rather than treating the lack of an invoice as proof that no cost exists. The appropriate accounting treatment depends on the facts and the agreed work.

HMRC states that it will not apply late quarterly-update penalty points for the 2026 to 2027 tax year, while the annual-return obligations still matter. Check the current guidance. That transitional position is not a reason to abandon the record routine. Complete information remains necessary for reporting and the annual return.

14. A fictional wholesale workflow

Consider a sole-trader wholesaler who has checked that MTD applies. Sales are recorded in an invoicing system, imports produce separate supplier and freight documents, and customers often pay several invoices together. This is a fictional workflow example, not evidence of a client's completed setup.

Each week, the sales report is reviewed, customer receipts are allocated and new purchase documents are collected. The owner labels personal transfers and explains unusual transactions. The bookkeeper adds unresolved items to a shared list rather than guessing their category.

At month end, the bank is reconciled and the missing-document list reviewed. Before the quarterly stage, the accountant receives the agreed records and explanations. After the update, the submission status and follow-up actions are recorded. The useful feature is continuity: the same information path supports ordinary bookkeeping, review and reporting without requiring a separate scramble to rebuild the quarter.

15. Introduce the routine in manageable stages

Start with one complete period and test the whole information path. Check whether records can be located, totals explained and bank items reconciled. Identify the specific points that fail, then improve them before expanding the routine.

A common starting improvement is consistent invoice references. Another is a single purchase-document collection point. A third is a scheduled question review with the person who knows the commercial facts. These changes can make the software more useful without requiring a complicated internal manual.

Review the routine after the first reporting cycle. Ask which tasks took longer than expected and why. A missing export, unclear supplier reference or late approval may be the real problem. Improving that point is more effective than simply requesting that everyone “send information sooner”. Use the experience to adjust the handover and review dates.

A quick quality check after the first month

Choose one sale, one supplier purchase and one refund from the completed period. Ask a person who did not enter them to follow each item from the source document to the recorded transaction and the bank movement. This is an internal record-quality exercise, not an audit opinion. It reveals whether the filing system and descriptions are usable by somebody other than their creator.

If the reviewer cannot find a document, cannot tell which customer payment settled the invoice or cannot explain the refund, improve that connection. Record the change and repeat the check with different items next month. A few well-chosen examples can expose a recurring process problem before it affects a much larger set of records.

16. Discuss support around the actual records

Digital reporting is a recurring information process. A practical setup combines compatible arrangements, clear roles and reliable records. The software is part of that system, but the business still needs a way to explain transactions and resolve questions.

CRV Gudka & Co's dedicated Edgware team can discuss bookkeeping support and relevant tax work around your circumstances. Our wholesale and food-import specialism is useful where purchases, stock and customer credit form part of the record picture.

Bring a short description of your current systems, the entry date or reporting question involved and the areas where information is difficult to collect. That allows the proposed work to be scoped around the real gaps. A repeatable routine with clear responsibilities gives the business a stronger foundation than relying on a new application to solve every record problem automatically.