SAP Business One in the UK: MTD for VAT and VAT returns

SAP Business One runs in the United Kingdom on an official SAP localization, and SAP supports Making Tax Digital (MTD) for VAT in it. For a UK company the rule that shapes the ERP today is MTD: VAT records must be kept digitally, and the VAT return must reach HMRC through compatible software, with no manual copying between programs on the way. From 1 April 2029 e-invoicing through Peppol follows. This page covers what MTD means inside SAP Business One, what is known about the 2029 e-invoice, how to check your VAT figures with SQL before you submit, and where custom development helps.

I am Zain Abbas, a SAP Business One developer. I have not delivered a project for a UK company yet, so this page is not a case study. It is written from my work on SAP B1 tax and e-invoicing in other countries, and the UK rules come from HMRC and SAP’s own documentation, linked at the end.

What does the UK localization of SAP Business One cover?

When you create a company database in SAP Business One you choose a localization, and it cannot be changed later. A UK company should be created on the UK localization from day one, because that is where SAP puts UK-specific tax behaviour. Two things are visible in SAP’s public support material:

SAP’s detailed MTD setup steps sit in SAP Notes and Guided Answers that need an SAP for Me login, so ask your SAP partner for the current guide that matches your version and patch level. Some UK SAP partners also sell their own MTD submission add-ons for SAP Business One. Either route is fine, as long as the data flow from SAP B1 to HMRC is digital end to end.

What does Making Tax Digital for VAT require from an ERP?

HMRC’s rules are in VAT Notice 700/22. The dates in short:

1. From 1 April 2022: MTD for VAT applies to every VAT-registered business, including those below the registration threshold.
2. From 1 November 2022: HMRC no longer accepts VAT returns through its old online form.

For the software this means three things:

• Digital records. The VAT data behind each return is kept in software, not on paper. In SAP Business One, every posted A/R and A/P document already creates journal entry lines with the tax code, base amount and tax amount, so the records exist by design.
• Digital links. If data moves between programs, for example from SAP B1 to a spreadsheet and then to a bridging tool, every step must be a digital transfer (export, import, API). Retyping or copy-paste of figures between programs breaks the rule.
• API submission. The return goes to HMRC from MTD-compatible software through HMRC’s API. HMRC’s software finder lists the recognised products.

Manual adjustments are allowed. VAT Notice 700/22 says an adjustment made to the return before submission does not need a digital link, but it needs an audit trail back to the calculation behind it. In SAP B1 the clean way is a journal entry with the right tax code, so the adjustment is in the ledger and in the next tax report.

When does e-invoicing become mandatory in the UK?

MTD is about the VAT return. The next change is about the invoice itself. At Budget 2025 the government decided that from 1 April 2029 VAT-registered businesses, public sector bodies included, must issue and receive VAT invoices as e-invoices. The exemptions are tightly defined.

What is known so far, from GOV.UK:

1. Network: Peppol is the core framework, through certified Access Points. Each business connects through its own Access Point or through a provider.
2. Spring 2027: consultation on the technical standards.
3. October 2027 to April 2028: the full requirements are expected.
4. Digital reporting of invoice data to HMRC is a separate future decision, not part of the 2029 rule.

HMRC has not published the technical standards yet, so nobody can tell you today the exact data fields a UK e-invoice will need. What you can do in SAP B1 now is the groundwork I see before every e-invoicing go-live, in any country: complete VAT numbers on business partners (OCRD.LicTradNum), correct tax codes on every line, clean addresses and units of measure, and a decision on who will run your Peppol Access Point. Those gaps take months to fix and do not depend on the final standard.

How do I check my VAT figures in SAP Business One before submitting?

The UK VAT return has nine boxes. Boxes 1 to 5 are VAT amounts, boxes 6 to 9 are net values. Boxes 2, 8 and 9 now cover only Northern Ireland trade in goods with the EU.

Which tax code lands in which box is set up in your localization; the table only shows where the numbers live. Before I trust any tax report I check it against the journal. The query below sums the tax lines of the journal (JDT1, where VatLine = ‘Y’) per tax code for one quarter. If its totals do not match the tax report for the same period, something is wrong in the setup or in a posting, and you want to know that before the return goes to HMRC.

-- SQL Server: VAT per tax code for one VAT quarter (July to September 2026)
SELECT T0.VatGroup        AS TaxCode,
       T1.Name            AS TaxName,
       T1.Category        AS InOut,      -- 'O' output, 'I' input
       T1.Rate,
       SUM(T0.BaseSum)            AS NetBase,
       SUM(T0.Debit - T0.Credit)  AS TaxAmount
FROM JDT1 T0
INNER JOIN OVTG T1 ON T1.Code = T0.VatGroup
WHERE T0.VatLine = 'Y'
  AND T0.RefDate BETWEEN '20260701' AND '20260930'
GROUP BY T0.VatGroup, T1.Name, T1.Category, T1.Rate
ORDER BY T1.Category, T0.VatGroup

-- SAP HANA version
SELECT T0."VatGroup"       AS "TaxCode",
       T1."Name"           AS "TaxName",
       T1."Category"       AS "InOut",
       T1."Rate",
       SUM(T0."BaseSum")              AS "NetBase",
       SUM(T0."Debit" - T0."Credit")  AS "TaxAmount"
FROM JDT1 T0
INNER JOIN OVTG T1 ON T1."Code" = T0."VatGroup"
WHERE T0."VatLine" = 'Y'
  AND T0."RefDate" BETWEEN '20260701' AND '20260930'
GROUP BY T0."VatGroup", T1."Name", T1."Category", T1."Rate"
ORDER BY T1."Category", T0."VatGroup"

Three notes from running checks like this:

• Signs. Output VAT sits on the credit side, so it shows as negative in TaxAmount; input VAT shows as positive. Run the query once on a period you have already filed, and compare it with that return, before you rely on it.
• Tax date vs posting date. The query filters on RefDate (posting date). If your company reports VAT by tax date, use TaxDate instead, and use the same field the tax report uses.
• Unknown codes. A tax code that appears here but is not mapped to a VAT box in the setup is a figure that will be missing from the return. Fix the mapping, not the return.

To run the same check every quarter without SQL access, save it as a query in the Query Manager with date parameters, or let a small add-on run it and send the result to the finance team. The JDT1 table page lists the journal line fields used above. If you have queries written for SQL Server, the SQL to HANA converter rewrites them for a HANA database.

Which ERP and accounting systems are common in the UK?

Small UK companies often run cloud accounting such as Xero, QuickBooks, Sage 50, FreeAgent or IRIS KashFlow. Growing companies move to mid-market systems such as Sage 200, Access Financials, AccountsIQ, Acumatica, Microsoft Dynamics 365 Business Central, Oracle NetSuite and SAP Business One. The move usually happens when stock, multi-entity reporting or production outgrows the accounting package.

Every system on HMRC’s list can file an MTD VAT return, so MTD alone does not decide the choice. Compare systems on your processes, your accountant’s workflow and the integrations you need. Our ERP selector is a neutral starting point and shows the sources behind each product’s data.

What can Kodenova do for SAP Business One users in the UK?

I work remotely from Pakistan. In winter Pakistan is 5 hours ahead of the UK, in summer 4, so a UK morning is my afternoon and we overlap for most of the UK working day. The work I do for SAP B1 companies:

• Add-ons inside SAP B1 with the UI API and DI API: approval screens, checks before posting, scanning, production steps. See the add-on development guide.
• Integrations through the Service Layer: web shops, CRM, logistics, bank and payment tools. The Service Layer guide shows the method.
• Validation rules in SBO_SP_TransactionNotification, for example blocking an invoice with a missing tax code or a customer without required data. See the TransactionNotification examples.
• Portals for staff, customers or suppliers who do not need a full SAP B1 licence.
• Queries, reports and SQL Server to HANA migration. See the migration guide.
• AI on top of SAP B1: an MCP server so ChatGPT or Claude can answer questions from live SAP data, with permissions.

To be clear about scope: I do not sell an MTD submission tool. MTD comes from SAP’s UK localization or from UK SAP partners. Kodenova is not an SAP partner and does not resell licences; if you have a partner for licences and support, I work alongside them on development.

Sources

• HMRC: Find software that's compatible with Making Tax Digital for VAT
• HMRC: VAT Notice 700/22, Making Tax Digital for VAT
• HMRC: Making Tax Digital software finder
• GOV.UK: VAT electronic invoicing
• GOV.UK: Roadmap for e-invoicing implementation
• SAP Knowledge Base Article 3373077: Creating a support incident for Making Tax Digital (MTD)
• SAP Knowledge Base Article 3269244: Troubleshooting MTD related issues (Guided Answer)
• SAP Knowledge Base Article 3209076: VAT Adjustment for Cash Discount in UK Localization Database

Related services

• SAP Business One development
• Web & B2B portals