A practical guide to SAP Making Tax Digital (MTD) for UK businesses, covering VAT compliance, SAP DRC, automation, digital reporting, and HMRC integration.
UK finance, tax, and IT teams are operating in a rapidly changing regulatory environment. HM Revenue & Customs (HMRC) continues to expand its Making Tax Digital (MTD) initiative, moving tax compliance away from periodic, largely manual processes towards digital record-keeping and electronic reporting.
For organisations running SAP S/4HANA, this shift has an important practical consequence: MTD compliance is not simply about submitting a VAT return electronically. The organisation also needs a controlled process that connects transactional data, VAT calculations, reporting, review, and electronic submission in a way that remains traceable and auditable.
This is where many enterprise environments encounter difficulties.
Large organisations may still rely on a combination of SAP exports, spreadsheets, manual adjustments, reconciliation workbooks, and third-party bridging software. These tools can support VAT submissions, but every additional handoff creates another point where data can be changed, duplicated, or disconnected from the underlying accounting records. As transaction volumes, legal entities, and reporting requirements increase, maintaining those processes becomes increasingly difficult.
The underlying challenge is therefore broader than the HMRC submission itself. Organisations need to understand where VAT-relevant data originates, how it moves through the reporting process, where validation takes place, who approves the return, and how the final figures can be reconciled back to the accounting records.
For SAP S/4HANA customers, SAP Document and Reporting Compliance (DRC), SAP Business Technology Platform (SAP BTP), and related automation capabilities can provide the foundation for a more integrated approach.
Instead of treating MTD as a separate tax submission exercise, organisations can connect it more closely to the finance processes that already generate the relevant data.
This guide follows that journey from regulatory requirements to solution architecture and implementation. It explains what MTD requires, why traditional VAT reporting processes become difficult to scale, how SAP can support the reporting lifecycle, what an enterprise MTD architecture can look like, and what organisations should consider when implementing or modernising their approach.
Short answer: For SAP S/4HANA customers, MTD compliance starts with digital VAT records and compliant digital links, but a robust enterprise approach goes further. Organisations should assess their tax configuration, reporting processes, SAP DRC capabilities, integration landscape, and governance before deciding whether to extend the existing architecture or move towards a more integrated SAP-based model.
The most effective MTD programmes begin with the reporting process rather than the submission interface. Before selecting a technical solution, organisations need to understand how VAT data is created, transformed, reviewed, and ultimately submitted to HMRC.
For enterprise organisations, the key considerations are:
The right solution therefore depends on the organisation's existing SAP landscape, number of entities, VAT complexity, integration requirements, regulatory scope, and desired level of automation.
To understand why these architectural decisions matter, it is first necessary to look at what MTD actually requires.
Making Tax Digital (MTD) is HMRC's programme to modernise the UK tax system by moving businesses towards digital record-keeping and electronic tax reporting.
For VAT, businesses within the scope of MTD must maintain the required VAT records digitally and submit VAT returns to HMRC using compatible software.
For an SAP S/4HANA organisation, this means that the VAT reporting process needs to connect the financial information held in SAP with the digital reporting and submission process.
For a business user, the practical question is not simply whether the company can submit a VAT return electronically. The question is whether the complete process - from the original transaction through VAT calculation, adjustments, review, and submission - is sufficiently digital, controlled, and traceable.
This distinction is particularly important for larger organisations. A company may already have an electronic VAT submission process but still depend heavily on spreadsheets, manual data transfers, or offline calculations during VAT preparation.
In practical terms, an MTD-compliant VAT process should allow the organisation to answer four questions:
For organisations using SAP, these questions typically involve SAP Finance and Tax configuration, VAT reporting processes, any external reporting or bridging software, and the controls surrounding the final submission.
This is why MTD should be considered an end-to-end finance and tax process, rather than simply an HMRC connectivity project.
The main requirements include:
HMRC introduced MTD as part of its wider effort to modernise tax administration and reduce avoidable errors. In an enterprise environment, the implications go beyond the final submission.
The reporting process must also provide confidence that data has been transferred correctly from the original accounting records through VAT calculations, adjustments, validation, and final reporting.
VAT Notice 700/22 sets out HMRC's requirements for digital records and digital links. Organisations should therefore pay close attention to the complete reporting chain rather than focusing only on the HMRC API connection.
This leads to the next question: if the requirements are digital, why do traditional VAT reporting processes create so many problems?
Historically, enterprise tax departments often managed VAT returns through a combination of ERP exports, spreadsheets, manual adjustments, reconciliation workbooks, and separate reporting or bridging applications.
A typical process might look like this:
SAP financial data → spreadsheet export → manual adjustments → reconciliation → VAT reporting tool → HMRC
This approach can work at a limited scale, but complexity grows quickly as the number of transactions, entities, VAT registrations, and reporting requirements increases.
Every spreadsheet export or manual adjustment creates another handoff. Finance teams may need to reconcile figures across multiple files, investigate differences manually, and document how the final VAT return relates to the original SAP transactions.
The result is not necessarily non-compliance, but it can create additional operational risk and make the process harder to control and audit.
For finance users, the practical impact is usually seen in the amount of time spent on activities that do not directly add tax value:
An integrated process does not eliminate the need for tax expertise. Instead, it can shift finance users away from repetitive data preparation towards reviewing exceptions, investigating unusual results, and making tax decisions.
Moving towards an integrated SAP-based approach changes not only how VAT returns can be prepared, but also how organisations manage control, transparency, and scalability.
| Area |
Legacy Spreadsheet Workflows |
Native SAP Automation |
|
Data Management |
Manual exports, spreadsheet adjustments, and disconnected systems |
Data captured and processed directly within SAP |
|
VAT Reporting |
Time-consuming preparation and manual reconciliation |
Automated calculation, validation, and submission workflows |
|
Audit Trail |
Requires manual tracking across multiple files and systems |
Greater digital traceability from transactions to HMRC submission |
|
Compliance Risk |
Greater exposure to manual errors and inconsistent data |
Automated controls and validation can reduce compliance risks |
|
Scalability |
Manual effort increases as business complexity grows |
Better suited to multiple entities, processes, and evolving requirements |
The key benefit is therefore not simply speed. A more integrated process can make it easier to identify where a number came from, investigate exceptions, and maintain consistent controls across reporting periods.
That is why MTD can become part of a broader finance transformation rather than remaining a standalone compliance task.
For VAT, businesses that are VAT-registered and within the scope of MTD must maintain digital records and submit VAT returns through compatible digital software.
For most business users, the first step is therefore to establish whether the organisation's VAT registrations and reporting arrangements fall within the relevant MTD requirements.
This becomes more important in enterprise environments where a group may have:
The presence of multiple systems does not automatically mean that an organisation is non-compliant. However, it does mean that the data flows between those systems need to be understood and controlled.
A finance or tax manager should be able to answer the following questions:
If several of these questions require information from different people, spreadsheets, or systems, the organisation may benefit from reviewing its MTD architecture.
HMRC's digital tax roadmap extends beyond VAT. Making Tax Digital for Income Tax (MTD for ITSA) introduces digital reporting requirements for self-employed individuals and landlords, with phased implementation beginning in April 2026.
For enterprise organisations with complex corporate structures, joint ventures, or subsidiary partnerships, establishing a standardised tax reporting architecture can provide a useful foundation for responding to future digital reporting requirements.
The specific obligations and implementation timelines should, however, always be assessed against the latest HMRC guidance rather than assumed to apply uniformly across all organisations.
For organisations using SAP S/4HANA, MTD compliance depends on more than having an HMRC-compatible submission process. The underlying finance and tax processes also need to support accurate digital records, appropriate digital links, and clear reporting controls.
The key areas to review include:
Before selecting or implementing a solution, the organisation should perform a current-state assessment.
This assessment should identify:
Source data → Tax calculation → Adjustments → VAT return → Review → HMRC submission
For each step, the business should document which system is used, whether the process is automated or manual, and who owns the activity.
This often reveals that the biggest MTD improvement opportunity is not the HMRC connection itself but the processes immediately before submission.
For example, if SAP contains the source transactions but VAT figures are exported into Excel, manually adjusted, and then uploaded to a separate application, the organisation should review the complete data flow rather than focusing only on the final submission interface.
This assessment establishes the baseline. Only after these dependencies are understood does it make sense to decide what the target SAP architecture should look like.
SAP can support UK MTD requirements through SAP Document and Reporting Compliance (DRC), integrated with SAP S/4HANA and, where required by the architecture, SAP Business Technology Platform.
The underlying principle is straightforward: rather than reconstructing VAT information separately at the end of a reporting period, organisations can use SAP as the primary source of financial and tax-relevant data and connect that information to the statutory reporting process.
Transactions such as sales invoices, purchase invoices, and general ledger postings generate the financial information required for VAT reporting. SAP DRC can then support the preparation and validation of the relevant reporting data and, for applicable scenarios, facilitate electronic submission to HMRC.
This can help organisations:
However, DRC should not be viewed as a standalone solution that automatically makes an organisation MTD-compliant. Compliance depends on the end-to-end process, including digital record-keeping, digital links between relevant systems, tax configuration, data quality, reporting controls, and the way adjustments and approvals are handled.
For example, if VAT data is extracted from SAP into spreadsheets, manually changed, and then transferred to the reporting process, the organisation still needs to assess whether those data flows and adjustments meet the applicable MTD digital-link requirements. Implementing DRC does not by itself eliminate these process considerations.
SAP DRC is the compliance and statutory reporting layer.
Depending on the applicable SAP product and reporting scenario, it can support activities such as preparing regulatory reports, applying reporting logic and validations, and supporting electronic reporting and submission processes.
For a business user, the main benefit is that statutory reporting can be brought closer to the financial data already maintained in SAP.
SAP BTP is the integration and extension platform.
It can be used where the organisation needs to connect SAP with external applications, automate processes, orchestrate data flows, or extend functionality without unnecessarily modifying the S/4HANA core.
BTP is therefore not automatically required simply because an organisation uses MTD.
Whether it is needed depends on the customer's SAP landscape, DRC deployment model, external systems, integration requirements, and target architecture.
Bridging software provides another route to HMRC submission.
It can be appropriate when the organisation already has a VAT reporting process and needs a compatible mechanism to connect the relevant digital records with HMRC.
The important point is that the choice of submission technology does not remove the underlying MTD obligations.
The organisation still needs to consider digital records, digital links, data accuracy, controls, and auditability.
The choice is therefore not simply:
"SAP DRC or bridging software?"
A better question is:
"What level of integration and control does our organisation need across the entire VAT reporting process?"
A smaller or less complex environment may be adequately served by a compatible bridging solution.
A large SAP organisation with multiple entities, complex tax processes, and broader statutory reporting requirements may have a stronger business case for a more integrated SAP architecture.
The exact architecture depends on the SAP products and versions in use, the DRC deployment model, existing tax and finance processes, integration requirements, and the UK reporting scenario in scope.
A robust MTD architecture needs to connect four activities:
Financial transactions → VAT reporting → validation and approval → HMRC submission
A business-friendly way to understand the architecture is to follow the journey of a VAT figure:
Transaction → Tax calculation → VAT reporting → Review → HMRC submission → Evidence
Each stage should have a clearly defined system, process owner, and control.
SAP S/4HANA serves as the system of record, where financial and tax-relevant transactions are created and maintained.
This is where users record business activities such as sales, purchases, invoices, and financial postings.
Business question:
Can we trace the VAT amount back to the underlying financial transaction?
SAP DRC supports statutory reporting, applies relevant reporting logic and validations, and supports regulatory submission scenarios.
Business question:
Can we turn the relevant SAP data into a controlled statutory reporting process?
SAP BTP can provide integration, extension, automation, and orchestration capabilities where they are required by the solution architecture.
Business question:
Do we need additional integration or automation between SAP and other systems?
HMRC's digital services provide the external destination for the relevant VAT submission.
Business question:
Can we demonstrate what was submitted, when it was submitted, and the resulting status?
This separation of responsibilities can simplify maintenance, support a Clean Core strategy, and make it easier to adapt the solution as regulatory and business requirements evolve.
The exact role of each component should be determined during solution design rather than assuming that every SAP MTD implementation requires the same technical architecture.
Once the architecture is defined, the reporting process can be viewed as an end-to-end operational workflow rather than a collection of disconnected technical components.
Business transactions, including sales invoices, purchase invoices, and financial postings, are recorded in SAP S/4HANA or SAP ECC through standard business processes.
SAP calculates VAT based on configured tax rules and maintains the tax-relevant financial information required for reporting.
SAP DRC can consolidate the relevant data, prepare the VAT return according to the applicable UK reporting structure, and perform validation checks before submission.
The organisation's finance and tax controls determine which checks and approvals are required before submission.
Exceptions, missing mappings, unusual values, or other issues can be reviewed before the return is submitted.
HMRC provides an electronic response to the submission, while the SAP reporting process can retain relevant filing status and supporting information.
This gives finance teams a clearer view of whether a return has been prepared, reviewed, submitted, or requires further action.
The workflow also clarifies where automation should stop. Tax specialists remain responsible for judgement, exception handling, and compliance decisions; the system takes responsibility for repeatable data and process steps.
SAP DRC vs. Bridging Software vs. Custom Development
Once the reporting workflow is understood, organisations can evaluate how best to implement it.
Enterprise architecture teams commonly compare SAP DRC with bridging solutions and custom development.
| Area |
SAP DRC |
Bridging Software |
Custom Development |
|
Integration |
Designed to integrate with SAP regulatory reporting processes |
Adds an external connection layer |
Fully custom integration |
|
Data and Audit Trail |
Strong visibility within the SAP reporting environment |
Data moves between SAP and an external application |
Depends on solution design |
|
Scalability |
Suited to enterprise SAP landscapes and broader regulatory scenarios |
Depends on third-party capabilities |
Requires ongoing development |
|
Maintenance |
Supported through SAP's product and regulatory update framework |
Additional vendor dependency |
Higher internal support requirements |
|
Flexibility |
Strong fit for organisations standardising on SAP |
Useful where a lightweight submission layer is required |
High flexibility but higher ownership costs |
Bridging software can remain an appropriate solution, particularly where an organisation needs to connect an existing accounting system to HMRC.
However, using bridging software does not remove the need to maintain compliant digital links and appropriate controls throughout the reporting process.
For larger SAP environments, an integrated approach can offer additional benefits. Keeping financial data and statutory reporting closer together can reduce reconciliation effort, improve traceability, and provide a more scalable foundation as regulatory requirements evolve.
Custom development provides flexibility but also creates responsibility for ongoing development, testing, support, and regulatory updates.
For organisations already investing in SAP S/4HANA, SAP DRC can therefore provide a more sustainable option where the strategic objective is to integrate MTD into a broader tax and compliance architecture.
At this point, MTD can be viewed as more than a technical submission requirement.
When VAT reporting is integrated into the SAP finance landscape, organisations can modernise the processes and controls surrounding tax reporting itself.
Instead of preparing VAT information separately at the end of the reporting period, finance teams can work with a more connected process in which data, validation, reporting, review, and submission are linked together.
The same architecture can also provide a foundation for future initiatives such as:
Read our guide on SAP Preparation for UK E-Invoicing to explore how organisations can prepare their SAP environment for the next phase of digital compliance.
The strategic opportunity is therefore to use MTD as one component of a broader finance and tax transformation rather than creating another isolated compliance application.
With the target process and architecture defined, the implementation can be structured into a series of controlled phases.
Evaluate the current SAP landscape, VAT processes, reporting requirements, and existing MTD arrangements.
Identify:
The objective is to establish the current-state process before designing the future-state architecture.
Business outcome: A documented current-state process showing where VAT data originates, how it is transformed, who reviews it, and how it reaches HMRC.
Configure SAP DRC, VAT reporting processes, tax rules, and submission workflows according to the organisation's business and regulatory requirements.
Where integrations or extensions are required, define their role without introducing unnecessary customisation into the ERP core.
Business outcome: A defined target process showing how VAT reporting will operate after implementation and which activities will be automated.
Review and optimise tax-relevant master data, including:
The mapping between financial data and VAT reporting requirements should be validated before end-to-end testing.
Business outcome: Clean and consistent tax data that can support reliable VAT reporting.
Perform end-to-end testing of:
Testing should use representative financial scenarios rather than relying only on technical interface tests.
Business outcome: Evidence that the complete reporting process works before it is used for production submissions.
Deploy the solution into production, support user adoption, and establish ongoing monitoring and maintenance processes.
The operating model should also define how SAP and HMRC changes will be assessed, tested, and introduced after go-live.
Business outcome: A sustainable operating model defining who owns VAT reporting, who handles exceptions, and how regulatory or SAP changes will be managed.
Implementation timelines and costs vary significantly between organisations.
A standard scenario with a relatively simple SAP landscape will generally require less effort than a multinational environment with multiple UK entities, VAT registrations, legacy systems, complex integrations, and extensive data remediation.
The cost should therefore be assessed against the scope of the transformation, rather than the MTD submission itself.
Typical implementation estimates can vary substantially. Any indicative figure should be treated as a planning benchmark rather than a standard market price.
The main cost drivers include:
When comparing implementation proposals, business stakeholders should ask whether the estimate includes:
This helps avoid a situation where a low initial implementation estimate excludes activities that later become additional project costs.
The implementation roadmap addresses the technical sequence, but enterprise tax projects also encounter recurring operational and governance challenges.
Challenge: Many organisations still rely on spreadsheets, CSV exports, and manual data adjustments, increasing the risk of errors and weakening process traceability.
Remediation: Maintain controlled digital data flows and eliminate unnecessary manual handoffs wherever possible.
Challenge: Outdated VAT codes, incorrect tax settings, or inconsistent master data can result in inaccurate reporting.
Remediation: Review tax configuration and master data as part of the MTD readiness process and establish appropriate governance for ongoing maintenance.
Challenge: Errors may only become visible when the VAT return is being prepared, increasing the risk of delays and additional investigation.
Remediation: Introduce validation controls that identify missing, inconsistent, or unusual data before submission.
Challenge: Without clearly defined roles, VAT preparation and submission processes may lack appropriate governance.
Remediation: Establish clear responsibilities and role-based approvals across finance, tax, and IT teams.
Challenge: HMRC requirements and digital reporting standards continue to evolve, requiring organisations to keep their processes and systems up to date.
Remediation: Monitor regulatory developments and maintain a flexible SAP architecture that can accommodate future changes.
Challenge: Organisations need to be able to explain reported figures and provide relevant records and submission information during an audit or internal review.
Remediation: Maintain appropriate digital audit trails, submission confirmations, supporting records, and documentation within the relevant systems.
The most difficult MTD projects are therefore rarely difficult because of VAT calculation itself. More often, problems originate in fragmented processes, inconsistent data, unclear ownership, and manual controls.
Before investing in a new MTD solution, UK businesses should first understand how their current VAT reporting process works.
Use the following questions as a quick readiness check:
If the answer to several of these questions is "not yet", the organisation may benefit from an MTD readiness assessment before selecting a technology solution.
The assessment should identify the gaps between the current process and the desired future state, then determine whether those gaps can be addressed through SAP configuration, SAP DRC, SAP BTP, process redesign, or a combination of these approaches.
A SAP-based MTD implementation should also be assessed against the wider UK regulatory environment.
Disclaimer: The information in this section is provided for technical and operational guidance only and does not constitute formal legal or tax advice. Organisations should consult qualified tax professionals and the latest HMRC guidance to confirm the requirements applicable to their specific circumstances.
Once the core reporting process is automated, organisations can consider where intelligent automation can add another layer of value.
Artificial intelligence is not a requirement for Making Tax Digital. Its role is complementary: helping finance teams identify anomalies, investigate exceptions, and process supporting information more efficiently.
By combining SAP Business AI with automation capabilities such as SAP Build Process Automation and SAP Joule, organisations can move beyond simple data processing.
AI-based tools can help identify unusual patterns and potential data-quality issues across large transaction volumes.
Potential use cases include:
AI can help finance teams identify unusual movements in tax data before a VAT return is finalised.
For example, significant changes in output or input VAT compared with historical reporting periods can be flagged for investigation.
These alerts do not replace tax review, but they can help teams focus attention on transactions and reporting movements that are more likely to require investigation.
Document Information Extraction and related SAP BTP capabilities can help organisations process incoming supplier invoices by extracting and classifying invoice information.
Where appropriately configured, automation can reduce manual data entry and route invoices for review based on tax and business rules.
Conversational AI can make tax and financial information easier for authorised users to investigate.
For example:
“Why has Box 4 Input VAT increased compared with the previous quarter?”
or:
“Show me the vendor invoices contributing to Box 6 above £100,000 with zero-rated tax codes.”
The exact capabilities available depend on the SAP products, releases, data model, configuration, and AI services deployed.
Artificial intelligence does not replace tax specialists. Instead, it can reduce repetitive validation work, identify potential issues earlier, and help finance teams focus on exceptions, judgement, and strategic tax activities.
AI should therefore be considered an additional optimisation layer, not a prerequisite for MTD compliance.
Once manual handoffs have been reduced and the reporting process is more closely integrated with SAP, the benefits extend beyond compliance.
The benefits of SAP-based MTD automation should be measured against the organisation's current process rather than assumed in advance.
Useful KPIs can include:
| KPI | What to Measure |
| VAT preparation time | Hours required to prepare a return |
| Reconciliation effort | Time spent reconciling SAP with reporting outputs |
| Manual adjustments | Number and value of manual corrections |
| Exceptions | Number of issues identified before submission |
| Submission cycle time | Time from period close to submission |
| Investigation time | Time required to trace reporting discrepancies |
| Audit preparation | Time required to provide supporting evidence |
| Automation rate | Percentage of reporting activities performed without manual intervention |
Reduced Manual Effort: Automating VAT data collection, validation, and submission can reduce the time spent on repetitive compliance activities and manual reconciliation.
Improved Data Accuracy: Automated tax calculations and validation rules can help identify inconsistencies earlier and reduce the risk of reporting errors.
Faster Compliance Cycles: Streamlined workflows can help finance teams prepare, review, and submit VAT returns more efficiently.
Enhanced Audit Readiness: A more connected digital audit trail can provide greater transparency and simplify internal and external audit processes.
Scalable Compliance Operations: SAP automation can help organisations support additional entities, higher transaction volumes, and evolving regulatory requirements without increasing manual workload at the same rate.
The biggest productivity gains come from shifting finance professionals away from repetitive data preparation towards higher-value activities such as tax analysis, planning, and exception management.
The value of an integrated approach becomes clearer when the reporting process is considered in a real enterprise scenario.
A UK-based enterprise was already running its core finance processes in SAP but relied on a fragmented process to prepare and submit VAT returns under Making Tax Digital (MTD).
The finance team had to bring together tax-relevant data from SAP, perform manual reconciliations, validate VAT figures, and then transfer the final information to a separate compliance or bridging solution for submission to HMRC. Supporting spreadsheets and manual checks were used to investigate discrepancies and confirm that the figures submitted to HMRC matched the company's financial records.
The process worked at a relatively small scale but became increasingly difficult to manage as transaction volumes and the number of reporting entities grew.
The main problems were:
The goal was to make VAT reporting a more integrated part of the company's SAP finance landscape rather than treating MTD as a separate compliance activity.
The target solution was designed to:
The target architecture connected the SAP finance environment with the digital tax reporting layer and HMRC services.
At a high level, the flow was:
SAP finance data → tax reporting and validation → digital submission → HMRC → status and audit trail
Depending on the customer's SAP landscape, this can be implemented using SAP's compliance reporting capabilities and SAP Business Technology Platform for integration and extension scenarios. SAP positions BTP as a platform for integration, development, automation, and extension across SAP and non-SAP systems.
VAT-relevant transaction data remained in the SAP environment rather than being manually reconstructed in spreadsheets.
The implementation first identified the relevant tax data, company codes, VAT registrations, tax codes, reporting periods, and mappings required to produce the VAT return.
This created a more consistent relationship between the figures used for reporting and the underlying financial transactions.
The reporting layer collected the required information from SAP and prepared the VAT return according to the applicable UK reporting structure.
Validation rules were introduced before submission to identify missing or inconsistent information early in the process.
Instead of reviewing every figure manually, finance users could focus on exceptions and items requiring investigation.
The solution connected the reporting workflow to HMRC's digital services through API-based integration.
The HMRC VAT API supports functions including retrieving VAT obligations and submitting VAT returns, as well as retrieving VAT liabilities and payments.
This allowed the submission process to become part of the digital workflow rather than requiring users to export information and manually transfer it between disconnected systems.
Where integration between the SAP environment and external services was required, SAP BTP could provide the connectivity and orchestration layer.
SAP Integration Suite, for example, provides standard adapters and non-SAP connectors for connecting SAP and third-party applications, as well as options for developing custom integrations where required.
This approach is particularly useful when an enterprise operates a mixed landscape that includes SAP S/4HANA, legacy SAP systems, tax applications, or other corporate platforms.
Automation was deliberately not designed to eliminate human involvement completely.
When a transaction failed a validation check, a mapping was missing, or the reporting result required review, the item was routed to the appropriate finance user.
This changed the role of the finance team from manually preparing every VAT submission to managing exceptions and reviewing the results generated by the system.
The reporting process retained relevant submission information and status, allowing finance users to determine whether a return had been prepared, reviewed, submitted, or rejected.
This also made it easier to investigate issues without reconstructing the reporting process from emails and spreadsheets.
The implementation could be structured into several stages.
The team reviewed:
The objective was to establish where the required VAT data already existed and where manual intervention was still taking place.
Tax and technical specialists mapped SAP financial data to the information required for the VAT reporting process.
This included reviewing:
The mapping stage is critical because automation cannot compensate for inconsistent or incomplete tax configuration.
The team defined how data would move between SAP, the reporting layer, and HMRC.
For an SAP-centric landscape, this could include SAP BTP and Integration Suite as the integration layer, depending on the customer's architecture and the SAP products in scope.
The VAT reporting workflow was implemented and tested against representative financial data.
Validation rules were introduced to identify issues before the return reached HMRC.
The HMRC connection was configured and the end-to-end submission process was verified.
An important consideration is that HMRC's testing environment and production behaviour need to be understood as part of the implementation plan. SAP documentation notes, for example, that testing capabilities can vary by SAP product and UK MTD scenario, so configuration and testing procedures need to be planned accordingly.
Finance users tested the complete process using realistic reporting scenarios, including corrections and rejected or incomplete data.
After validation, the solution was rolled out with user documentation and operational procedures for handling exceptions.
The main value of the solution was not simply replacing one VAT submission method with another. It was connecting tax reporting more closely to the financial processes that generated the underlying data.
The resulting process provided:
The biggest improvement came not from a single automation step, but from reducing manual handoffs across the reporting cycle, from SAP data preparation and validation through to submission and exception handling.
Note: This case study is an anonymised, illustrative example. Any quantified results should be replaced with verified customer data before publication. Actual outcomes vary by organisation, SAP landscape, transaction volumes, reporting scope, and implementation approach.
The same architecture can address different operational challenges depending on the industry.
Manufacturing organisations often operate across multiple plants, legal entities, and VAT registrations, creating complex tax reporting requirements.
High volumes of supplier invoices, intercompany transactions, and different tax treatments can make manual VAT consolidation time-consuming and difficult to audit.
SAP DRC can help organisations consolidate relevant tax data from SAP S/4HANA, maintain appropriate digital links throughout the reporting process, and automate VAT return preparation before submission to HMRC.
Business Outcome: Faster VAT reporting cycles, improved audit readiness, and reduced dependency on manual tax preparation activities.
Retail and FMCG
Retail and FMCG organisations process large volumes of daily transactions across multiple sales channels, including stores, e-commerce platforms, and third-party marketplaces.
Different VAT treatments and high transaction volumes increase the risk of tax coding errors and reconciliation challenges.
SAP DRC can help connect transactional finance data with statutory reporting processes, improving VAT reporting accuracy and providing greater transparency before HMRC submission.
Business Outcome: More reliable VAT reporting, fewer manual reconciliations, and improved control over high-volume transaction environments.
Financial institutions often manage complex VAT structures, including partial exemption calculations, multiple entities, and strict regulatory requirements.
Traditional spreadsheet-based approaches can create additional compliance risks and limit audit transparency.
SAP DRC provides a structured framework for statutory reporting by connecting tax reporting with SAP financial data and supporting traceability between reported figures and underlying transactions.
Business Outcome: Stronger compliance governance, improved audit transparency, and greater confidence in VAT reporting accuracy.
HMRC's digital tax programme extends beyond VAT. As tax administration becomes increasingly digital, organisations should consider how today's MTD architecture can support future regulatory requirements without creating unnecessary technical debt.
Potential areas of development include:
Wider Income Tax rollout (MTD for ITSA): Digital reporting requirements for self-employed individuals and landlords are being introduced on a phased basis from April 2026.
Corporation Tax digitisation: HMRC has explored the future digitisation of Corporation Tax processes, although organisations should distinguish between confirmed requirements and longer-term policy developments.
Real-Time Transactional Reporting: International tax authorities are increasingly moving towards more frequent, transaction-level reporting and Continuous Transaction Controls.
Global E-Invoicing Alignment: E-invoicing frameworks and standards such as Peppol are expanding across international markets, increasing the importance of flexible tax and integration architectures for multinational organisations.
Investing in SAP DRC today is not only about meeting current MTD requirements. It can also form part of a broader digital tax strategy.
Organisations that embed tax reporting capabilities into their SAP landscape can benefit from:
Continuous regulatory readiness: A structured SAP compliance architecture can make it easier to respond as HMRC introduces new digital reporting requirements.
Reduced future transformation costs: Building on SAP DRC, SAP S/4HANA, and appropriate SAP BTP capabilities can reduce the need for completely separate compliance projects as new requirements emerge.
Stronger audit transparency: Integrated digital records can provide clearer traceability from statutory reports back to the underlying financial data.
Scalable global compliance capabilities: The same architectural principles can support future requirements such as e-invoicing, Continuous Transaction Controls (CTCs), and international digital reporting models.
Protection of the SAP Clean Core strategy: Using SAP-standard compliance capabilities and appropriate extensions can help organisations avoid unnecessary custom development that increases technical debt.
By treating MTD as part of a broader digital tax strategy, organisations can build a more flexible foundation for the continued evolution of digital taxation.
Once the organisation has defined its regulatory requirements, target process, and architecture, partner selection becomes the next practical consideration.
Implementing a future-ready SAP tax compliance architecture requires more than configuring reporting tools. The partner should understand SAP Finance, tax processes, integration, regulatory reporting, and enterprise transformation.
Key capabilities to evaluate include:
A useful procurement question is:
Can the partner demonstrate successful delivery of an SAP MTD or statutory reporting environment similar to ours in terms of SAP landscape, number of entities, tax complexity, integration requirements, and operational scale?
A useful procurement process should go beyond asking whether the partner has implemented SAP DRC.
Ask the partner:
A strong partner should be able to explain the proposed architecture in both technical terms for IT and business terms for Finance and Tax.
Implementing an SAP tax compliance architecture requires the combination of technology, finance, integration, and regulatory expertise.
As an SAP Gold Partner and Global System Integrator with more than 20 years of SAP experience, LeverX helps organisations design, implement, and optimise SAP landscapes that support UK tax compliance requirements and broader digital reporting initiatives.
| Capability | Business Value |
| SAP Gold Partner Expertise | Proven SAP delivery experience across complex enterprise environments, supporting organisations throughout assessment, implementation, and optimisation. |
| Fortune 500 Enterprise Experience | Experience supporting large global organisations with complex SAP landscapes, multi-country operations, and demanding regulatory requirements. |
| SAP Center of Excellence (CoE) | Dedicated SAP expertise across architecture, implementation, integration, and continuous improvement, supporting consistent delivery and long-term platform optimisation. |
| SAP DRC & Tax Compliance Expertise | Experience implementing SAP Document and Reporting Compliance solutions to support UK MTD requirements and broader global tax reporting initiatives. |
| SAP S/4HANA Finance Expertise | Deep knowledge of SAP Finance architecture, Universal Journal (ACDOCA), tax configuration, reporting structures, and multi-entity environments. |
| Clean Core SAP Architecture | Designs SAP BTP-based extensions and integrations that protect the ERP core while enabling business-specific innovation. |
| UK Regulatory Alignment | Supports requirements related to HMRC MTD, VAT reporting, audit transparency, UK GDPR, and statutory reporting processes. |
| Application Management Services (AMS) | Provides ongoing optimisation, system monitoring, SAP release management, compliance updates, and operational support after go-live. |
Making Tax Digital is changing how UK organisations manage VAT compliance, but the most important transformation is not the final API submission.
For SAP S/4HANA customers, the opportunity is to establish a connected process in which financial transactions, VAT calculations, reporting, validation, approval, and HMRC submission work as part of a controlled digital flow.
The right architecture will depend on the organisation's SAP landscape and regulatory requirements. For some businesses, compatible bridging software may remain sufficient. For larger or more complex SAP environments, SAP DRC and, where appropriate, SAP BTP can provide a more integrated foundation for statutory reporting.
The strongest results come when MTD is approached as part of a broader finance and tax transformation rather than as an isolated compliance project.
By combining SAP S/4HANA Finance, SAP Document and Reporting Compliance, SAP Business Technology Platform where appropriate, and intelligent automation, organisations can reduce manual reporting effort, improve auditability, and create a more scalable foundation for future digital tax requirements.
Spreadsheets can form part of an MTD process in certain circumstances, provided the overall process meets HMRC's requirements for digital records and digital links. Manual copying or rekeying of VAT data between digital records can breach the requirements set out in VAT Notice 700/22.
The practical question is therefore not whether an organisation uses Excel at all, but where Excel is used and whether the relevant data transfers and calculations meet the applicable HMRC requirements.
Yes. HMRC permits compatible bridging software for MTD VAT submissions. However, organisations must ensure that the complete process, including transfers between systems and any calculations or adjustments, complies with the applicable digital-link requirements.
For enterprise organisations, an integrated SAP approach may provide additional benefits in terms of scalability, traceability, and integration with broader tax processes.
No. SAP DRC can automate aspects of data aggregation, statutory reporting, validation, and electronic submission, but tax specialists remain essential for reviewing exceptions, maintaining tax controls, interpreting tax rules, and managing audit and compliance activities.
SAP solutions can support electronic VAT submission to HMRC through the relevant MTD services. The exact integration architecture depends on the SAP products, DRC scenario, deployment model, and integration services used.
Organisations should monitor both HMRC updates and the relevant SAP regulatory and product updates. SAP may provide updated regulatory content, software corrections, or configuration guidance where applicable. Changes should still be assessed and tested within the customer's environment before being moved into production.
SAP can support complex organisational and VAT reporting scenarios, but the exact approach depends on the SAP product, DRC scope, configuration, and reporting architecture. VAT group requirements should therefore be assessed as part of the solution design.
SAP Business AI can support VAT operations by helping identify unusual transactions, potential data-quality issues, duplicate invoices, and reporting variances. These capabilities can reduce manual investigation work, but they complement rather than replace tax controls and professional review.
Not necessarily. The required architecture depends on the SAP products, DRC deployment model, integration requirements, and HMRC submission scenario.
SAP BTP can provide integration, extension, automation, and orchestration capabilities where they are required. Organisations should therefore determine the role of BTP during solution design rather than assume that it is mandatory for every SAP MTD implementation.
A CFO should primarily consider:
The technology should support these business objectives rather than become the objective itself.
A Tax Manager should focus on whether the solution provides:
IT should assess:
This separation of concerns helps Finance, Tax, and IT evaluate the same MTD project from their respective responsibilities while maintaining a common target architecture.
For organisations still relying on fragmented VAT reporting processes, the first step does not necessarily need to be a technology implementation.
A structured MTD readiness assessment can help identify where the current process creates manual effort, compliance risk, reconciliation work, or limited audit visibility.
From there, organisations can determine whether the appropriate next step is to optimise the existing process, introduce or extend SAP DRC, add SAP BTP capabilities, replace legacy integrations, or redesign the broader tax reporting architecture.
Disclaimer: This guide is provided for general informational purposes only and does not constitute legal, tax, or implementation advice. Actual SAP MTD requirements, timelines, technical configurations, and outcomes depend on each organisation's systems, processes, SAP products, and regulatory obligations. Organisations should seek appropriate professional advice and consult the latest HMRC and SAP documentation before making compliance or technology decisions.