UK Making Tax Digital VAT Filing

The problem

Making Tax Digital requires that the figures in your VAT return travel from your accounting records to HMRC through digital links, with no manual re-keying anywhere along the chain. Plenty of UK NetSuite tenants technically comply while doing exactly what MTD was designed to stop: export the VAT report to Excel, tidy it, paste the nine boxes into a bridging tool, and submit. The digital link exists on paper. In practice the numbers are touched by hand at the point where mistakes happen.

The cost is not only compliance risk. Because the return is assembled outside NetSuite, nothing in NetSuite knows what was filed. There is no record of the submission, no receipt, no way to drill from a filed box figure back to the transactions behind it, and no way to tell whether a late-posted invoice landed in a period you already submitted. When HMRC queries a figure eighteen months later, the reconstruction starts with finding the right spreadsheet.

What ECOSIRE builds

We build the whole chain inside NetSuite: the return is assembled from your transactions, reviewed in NetSuite, submitted to HMRC from NetSuite, and the receipt is stored in NetSuite.

Nine-box assembly from transactions

A Map/Reduce script builds each of the nine boxes from posted transactions for the obligation period — output VAT due on sales, VAT due on intra-community acquisitions where applicable, total VAT due, VAT reclaimed on purchases, net VAT, and the four value boxes for total sales and purchases excluding VAT. Box composition is driven by a mapping held in custom records that links your tax codes and tax groups to boxes, so a new tax code is a configuration change rather than a code change. Each box figure retains the list of transaction internal IDs that produced it.

Review before you submit

A Suitelet presents the return as HMRC will receive it, with drill-down from any box to the contributing transactions and a comparison against the prior period so an unexpected movement is visible before submission rather than after. Reversals, credit notes and journals hitting VAT control accounts are all included in that view. Nothing submits until a user with the right permission explicitly approves it.

Digital-link submission to HMRC

Submission goes over HMRC's MTD VAT API from a SuiteScript 2.1 RESTlet and Scheduled script pair, using OAuth 2.0 tokens stored securely in NetSuite, with automatic token refresh. The integration retrieves your open obligations, so NetSuite knows which periods are due and their exact date ranges rather than assuming calendar quarters. It submits the return, captures the receipt — processing date, form bundle number, charge reference — and writes it to the stored return record. It also retrieves liabilities and payments, so what you owe and what HMRC has recorded as paid are visible in NetSuite.

HMRC requires fraud-prevention headers on every API call. These are assembled and sent correctly as part of the build; getting them wrong is one of the most common reasons a technically working integration fails validation, so it is handled explicitly rather than left as an afterthought.

Period control and adjustments

A VAT return custom record holds each period's status: open, submitted, or superseded. Once a period is submitted it is locked, and transactions posted with a date inside that period are collected into an adjustments list that carries forward to the next return — the standard treatment for errors below the notification threshold. Larger adjustments are flagged for manual disclosure rather than silently absorbed.

Partial exemption and adjustments

Where you operate partial exemption, flat rate, or a retail scheme, the calculation and its supporting workings are held as adjustment records attached to the return, with the calculation basis stored alongside the figure. The adjustment is part of the digital record, not a number someone typed into box 4.

Roles, audit and OneWorld

Permissions are configured so preparation and submission can be separated. Every action — generation, regeneration, approval, submission, receipt capture — is recorded against the return record with user and timestamp. In OneWorld accounts each UK VAT registration is scoped to its subsidiary or VAT group as configured, and a group registration can consolidate the subsidiaries you specify.

Who this is for

UK VAT-registered businesses on NetSuite that currently bridge through a spreadsheet; groups with a UK VAT registration inside a wider OneWorld structure; and finance teams who want the filed figure, its supporting transactions and the HMRC receipt to live in one place they can query.

How delivery works

1. Scoping call. We review your VAT registration structure, your tax code setup, whether you operate any special scheme or partial exemption, who prepares and who approves, and your HMRC access. We look at the last few returns you filed.

2. Fixed quote. A written scope and a fixed price before any development begins.

3. Build. Development as an SDF project — Map/Reduce, Scheduled and RESTlet scripts, custom records for returns, box mappings and adjustments, the Suitelet review screen, saved searches and role permissions. Typical lead time is one working week.

4. Install in your sandbox. We deploy to your sandbox and connect to HMRC's sandbox environment for the API, then reconcile generated returns against returns you have already filed. Box-by-box agreement with your submitted figures is the acceptance test.

5. Production deployment. The same bundle is deployed to production, connected to live HMRC credentials, permissions configured, and the first live period submitted with us alongside you.

6. Support window. A defined post-go-live period for defect resolution and configuration support, plus full source and documentation.

This is built to order for your account. Nothing is available as a ready-made download and there is no trial — we scope, quote, build, install in test then production, and you own the SDF project.

What you should know upfront

You need HMRC credentials with authority to submit VAT returns for your VAT registration number, and the connection must be authorised by someone who holds that authority. We build the integration and configure it; we do not act as your agent and we do not submit on your behalf. We are not tax advisers — the composition of your boxes and the treatment of any special scheme is agreed with your accountant during scoping, and we implement what is agreed.