UK Digital Prompts for VAT and Corporation Tax: April 2027 and 2028

The UK government has announced investment in technology to provide real-time digital prompts for taxpayers using compatible VAT filing software from April 2027, followed by Corporation Tax filing software from April 2028. HM Treasury describes the underlying approach as transactional risking: data-driven nudges intended to help businesses get tax information right before submitting a return.

This is a meaningful software and compliance-process development, but it is easy to overstate. The announcement does not by itself replace a VAT return, change Corporation Tax rates, create a new tax, or publish a complete set of compulsory prompts. The rollout is expected to be gradual as software developers integrate the functionality.

What are the new UK digital prompts?

The policy is designed to place real-time, data-driven prompts inside digital tax services and compatible third-party filing software. A prompt might draw attention to information that appears inconsistent, incomplete or worth checking before a return is submitted. The official announcement calls the wider approach transactional risking and says it is intended to help VAT and Corporation Tax taxpayers get their tax right before filing.

The public announcement does not provide a final catalogue of every message, threshold, data source or response. A business should therefore treat a prompt as a review signal, not as an automatic assessment or a substitute for checking its records.

When will VAT prompts start?

The announced VAT date is April 2027. The policy costings say the measure applies to VAT taxpayers using compatible third-party software and will be rolled out gradually as software developers integrate the functionality. That wording matters: April 2027 is the stated start of the intended capability rollout, not proof that every VAT-registered business will see the same prompt on the same day.

VAT-registered businesses should continue to follow the current VAT invoice rules, maintain the records required by HMRC and submit returns under their existing deadlines. A digital prompt may identify a question about a figure, but the business remains responsible for checking the source records, VAT treatment and final return.

When will Corporation Tax prompts start?

The announced Corporation Tax date is April 2028. The government describes the capability as being delivered through Corporation Tax filing software. The rollout is therefore relevant to companies, agents and software providers, but the announcement does not yet establish a single new filing date, a universal software mandate or a final list of Corporation Tax risk checks.

Companies should keep using the current Corporation Tax filing process and the software or adviser arrangement that meets their existing obligations. The HMRC software information for Company Tax Returns is useful for current filing arrangements, but it should not be read as a final specification for the future prompt service.

Does this make VAT or Corporation Tax filing mandatory through new software?

Not on the basis of the Budget announcement alone. The announced measure concerns investment in technology and the gradual integration of prompts into compatible filing software. It does not say that every taxpayer must immediately change provider, nor does it publish a new universal software obligation for every VAT or Corporation Tax taxpayer.

This is separate from other digital-tax measures. For example, Making Tax Digital for Income Tax has its own eligibility thresholds, digital-record requirements and quarterly updates. Read the Making Tax Digital guide for that separate regime. Do not use the VAT or Corporation Tax prompt dates as a shortcut for deciding whether MTD for Income Tax applies.

How should a business prepare?

Preparation should focus on traceable data and a reviewable filing process rather than trying to guess future HMRC messages.

1. Map the source data: identify the sales, purchase, payroll, bank, stock and fixed-asset systems feeding the VAT or Corporation Tax return.
2. Check coding quality: review VAT rates, exemptions, reverse-charge treatment, dates, customer and supplier details, and the treatment of unusual transactions.
3. Keep evidence: retain invoices, adjustments, reconciliations and explanations for material estimates or one-off entries.
4. Test software updates: ask the provider whether it plans to support the new HMRC functionality and how prompts will be recorded, reviewed and cleared.
5. Define escalation: decide when a prompt can be resolved by the finance team and when it needs an accountant, tax specialist or further source evidence.
6. Separate alert from conclusion: document why a figure is correct even when a prompt appears, and investigate a prompt rather than simply overriding it.

Good controls will still matter if no prompt appears. The service cannot be assumed to identify every error, and the absence of a warning is not confirmation that a return is complete or technically correct.

What is not confirmed yet?

As of the date of this guide, the public material does not settle every operational question, including:

• the exact prompts and risk rules that each software product will display;
• the HMRC and third-party data sources used for each check;
• whether a prompt will be informational, require an acknowledgement or block submission;
• the full list of compatible products and the timetable for each provider;
• how agents will see, explain and record prompts for clients;
• the treatment of amended returns, group companies, VAT schemes and unusual accounting periods; and
• penalties or other consequences for ignoring a prompt.

These are implementation questions. They should not be converted into claims that a company will automatically be investigated, that a prompt is an assessment, or that a particular software product is already approved for the future service.

Prepare for a digital prompt without treating it as an assessment

Start with a clean data map for each return. For VAT, identify the sales and purchase systems, tax-point dates, VAT codes, exemptions, reverse-charge transactions, partial-exemption method and adjustment records. For Corporation Tax, map the accounting period, statutory accounts, fixed-asset register, disallowable expenditure, losses, group relationships and transfer-pricing or related-party records where relevant. A prompt may point to an unusual pattern, but it cannot understand an undocumented business decision or replace the legal analysis behind the return.

Ask the software provider how source transactions are imported, how VAT codes are maintained, how amendments are logged and whether an agent can see the same prompt as the client. Keep a record of the product version and integration date. Do not assume that a product advertised as “HMRC-ready” is already connected to the future prompt service. The official rollout is gradual, so the absence of a prompt may mean that the functionality is not yet available, that the transaction falls outside the data used, or that HMRC has not identified a risk.

Create a prompt-response log with the date, return period, message, underlying transactions, reviewer, conclusion and action. Classify the result as confirmed error, explainable difference, data-quality issue, unresolved technical question or no change required. If the return is corrected, preserve the original calculation, the reason for correction and the submission confirmation. If no change is made, record the evidence supporting that decision. This creates an audit trail without treating every automated nudge as an allegation of deliberate non-compliance.

Agents should agree in advance who receives messages, who contacts the client, who approves a correction and who retains the evidence. A prompt shown to an agent may relate to information held by the client, while a client may interpret a technical message as a tax demand. Use plain explanations and distinguish an informational prompt from an assessment, compliance check, penalty notice or payment request. Verify any request for payment through the official HMRC account rather than through a software pop-up or unsolicited message.

Review the controls before the announced rollout dates, but do not bring forward an unconfirmed statutory deadline. Test a representative set of invoices, credit notes, imports, exports, payroll costs, finance charges and fixed-asset entries. Include unusual accounting periods, group-company transactions and amended returns in the test plan. Record which issues are caused by missing data, which are caused by a VAT or Corporation Tax judgement, and which require a software change. That distinction helps the business decide whether to improve bookkeeping, obtain tax advice or contact the provider.

What a prompt cannot decide for the business

A digital prompt may compare information or highlight an unexpected relationship, but it cannot determine the objective nature of a supply, the recoverability of an input, the availability of a Corporation Tax relief or the correct treatment of a transaction that depends on a contract. Those questions still require the underlying legislation, HMRC guidance and the facts of the business. A warning should therefore start a review, not dictate an automatic adjustment.

The same figure can be reasonable in one business and wrong in another. A sudden change in VAT on sales may reflect a new product, a customer in another jurisdiction, a change in place-of-supply analysis, a one-off credit note or a genuine bookkeeping error. A change in Corporation Tax profit may reflect capital expenditure, an accounting estimate, a group transaction or a relief claim. Record the commercial explanation alongside the tax conclusion so a later reviewer can follow the chain from source data to return.

Businesses should also plan for false positives and missing signals. A prompt can be triggered by incomplete data, timing differences or an unusual but correct transaction. Conversely, no prompt does not prove that the return is complete. Continue the existing review of reconciliations, VAT control accounts, bank postings, payroll and accounts-production schedules. Treat HMRC technology as an additional control layer, not as a replacement for management review or professional judgement.

When a prompt leads to a correction, use the correct HMRC process for the relevant return and period. Keep the revised workings, submission receipt, client approval and payment or repayment record together. If the issue concerns software data rather than tax treatment, raise it with the provider and retain the ticket number. This separation prevents a technical defect from being described as a tax position and makes it easier to establish whether another return may be affected.

Frequently Asked Questions

The safest interpretation is that the UK is preparing a more interactive filing experience, not replacing the taxpayer's responsibility for accurate returns. Recheck HMRC and your software provider as the VAT and Corporation Tax rollout details are published.

Official sources

• GOV.UK: Budget 2025
• HM Treasury: Budget 2025 policy costings
• HMRC: Transformation Roadmap progress update 2026
• GOV.UK: VAT invoices
• GOV.UK: VAT record keeping
• GOV.UK: Filing your Company Tax Return online