Common MTD UK Errors and How to Fix Them: OAuth, Digital Links, Box Mismatches, and Late Returns (2026)

The seven recurring failure modes in MTD for VAT are: (1) OAuth token expired or revoked, (2) Box 1 / Box 6 reconciliation mismatch, (3) submission rejected for VRN mismatch, (4) duplicate submission for a period already fulfilled, (5) broken digital link from manual override, (6) missed obligation deadline triggering a penalty point, and (7) cross-period tax-point miscategorisation. For each, the fix runs through re-authorisation, VAT code correction at line level, or filing an error-correction notice — never patching the return manually, which itself breaks the digital-link rule.

Why most MTD errors look the same up close

An MTD submission failure usually presents as one of three symptoms: HMRC returns an HTTP 4xx with a JSON error code; the boxes refuse to balance; or HMRC silently accepts the submission but an inspector later finds a figure that does not trace back to a digital record.

An MTD submission failure usually presents as one of three symptoms: HMRC returns an HTTP 4xx with a JSON error code; the boxes refuse to balance; or HMRC silently accepts the submission but an inspector later finds a figure that does not trace back to a digital record. The patterns below cover ~95% of what we see across UK Invoicemonk tenants.

Error 1 — OAuth token expired or revoked

Symptom: the platform fails to pull obligations or submit a return; HMRC returns 401 Unauthorized with INVALID_CREDENTIALS.

Symptom: the platform fails to pull obligations or submit a return; HMRC returns 401 Unauthorized with INVALID_CREDENTIALS.

Cause: the OAuth token bound to the VAT registration was revoked from inside the Government Gateway, the user changed their gateway password, or the refresh hit the 18-month boundary without renewal.

Fix: re-authorise the platform via the OAuth flow. Invoicemonk surfaces a re-authorisation banner — clear it before the next obligation deadline. After re-auth, retry the obligations call and confirm a fresh access-token timestamp.

Error 2 — Box 1 and Box 6 do not reconcile

Symptom: total VAT due (Box 1) does not match the expected VAT rate applied to Box 6 net sales.

Symptom: total VAT due (Box 1) does not match the expected VAT rate applied to Box 6 net sales.

Cause: usually a line item with a zero-rated or exempt code misclassified as standard rate, a partial-exemption adjustment that bypassed the digital link, or a manual journal posted directly to the VAT control account.

Fix: drill into the invoices contributing to Box 6 and check each VAT code. Recategorise wrong lines at source — never patch the difference in the return itself. If the variance is genuine (e.g. mixed-rate supplies), document the calculation in the partial-exemption working paper.

Error 3 — Submission rejected: VRN mismatch

Symptom: HMRC returns VRN_INVALID on submission.

Symptom: HMRC returns VRN_INVALID on submission.

Cause: the OAuth token was authorised against a different VAT registration than the one configured in the platform — common when a finance team manages multiple group VRNs.

Fix: confirm the VRN in platform settings matches the VRN used at OAuth time. If they differ, re-authorise against the correct gateway login.

Error 4 — Duplicate submission ("obligation already fulfilled")

Symptom: HMRC returns HTTP 403 with BUSINESS_ERROR and a message containing "obligation already fulfilled".

Symptom: HMRC returns HTTP 403 with BUSINESS_ERROR and a message containing "obligation already fulfilled".

Cause: the return was already filed for that period — often via the legacy HMRC portal before the period was migrated to MTD, or by a second user inside the same tenant.

Fix: check the obligations list — HMRC marks fulfilled periods. If a duplicate was created in error and you need to amend, follow Error 8 in VAT Notice 700/45: if the net error sits below £10,000 and below 1% of Box 6, correct in the next return; otherwise file a separate error-correction notice (form VAT652).

Error 5 — Broken digital link (manual override)

Symptom: an HMRC inspector finds a difference between the underlying records and the submitted return; or your internal reconciliation produces an unexplained delta.

Symptom: an HMRC inspector finds a difference between the underlying records and the submitted return; or your internal reconciliation produces an unexplained delta.

Cause: someone retyped a figure between the records and the return, breaking the digital-link rule (the single largest audit finding HMRC publishes).

Fix: identify the override, restore the digital link end to end, document the correction in the audit trail. If the override changed the submitted figure materially, file an amended return per the £10,000 / 1% rule above.

Error 6 — Missed obligation deadline

Symptom: HMRC issues a late-submission penalty point.

Symptom: HMRC issues a late-submission penalty point.

Cause: the quarterly return was not submitted by one calendar month + seven days after period end.

Fix: submit as soon as possible. Points accumulate; the £200 fixed penalty applies at the threshold (four points for quarterly filers). After a "good behaviour" period of on-time submissions, HMRC resets the points. Set calendar triggers for every obligation date and a separate trigger for the OAuth refresh-token expiry.

Error 7 — Cross-period tax-point miscategorisation

Symptom: an invoice issued in one period but with a supply date (tax point) in the previous period distorts the boxes.

Symptom: an invoice issued in one period but with a supply date (tax point) in the previous period distorts the boxes.

Cause: HMRC uses the tax point — date of supply — to allocate the VAT, which may differ from the invoice issue date.

Fix: confirm the tax point on every invoice; Invoicemonk uses tax point by default. If a previous entry used the wrong date, correct at source and reconcile across the affected periods.

Triage flow

Triage flow includes: Capture the exact HMRC error code from the API response (error. code and error.

1. Capture the exact HMRC error code from the API response (error.code and error.message).
2. If 401 → Error 1 (OAuth).
3. If 403 with BUSINESS_ERROR → Error 4 (duplicate).
4. If 400 with VRN_INVALID → Error 3 (VRN).
5. If boxes won't balance → Error 2 (reconciliation) or Error 7 (tax point).
6. If submitted but figure is wrong → Error 5 (digital-link audit) — apply the £10,000 / 1% rule.

Authority sources

• HMRC Developer Hub — MTD VAT API and error reference
• HMRC — VAT Notice 700/45: How to correct VAT errors
• HMRC — Penalties for late submission
• HMRC — Late VAT payment penalties (2025 rates)
• HMRC — Keep digital records (Notice 700/22)
• HMRC — Agent Update Issue 142 (current operational guidance)

TL;DR

OAuth, reconciliation, VRN, duplicate, digital-link, deadline, tax point — seven failure modes, each with a documented fix. Treat the HMRC error code as the entry point, never patch a submitted return manually, and rely on the £10,000 / 1% threshold to decide between in-return correction and VAT652.

OAuth, reconciliation, VRN, duplicate, digital-link, deadline, tax point — seven failure modes, each with a documented fix. Treat the HMRC error code as the entry point, never patch a submitted return manually, and rely on the £10,000 / 1% threshold to decide between in-return correction and VAT652.

Related reading

Related reading includes: MTD UK — Invoicemonk's MTD VAT implementation How to comply with MTD for VAT — step-by-step

• MTD UK — Invoicemonk's MTD VAT implementation
• How to comply with MTD for VAT — step-by-step
• MTD UK explained: scope, digital links, ITSA
• Choosing an e-invoicing platform — buyer's checklist