5 November 2026compliance

MTD for VAT readiness checklist for an Odoo 19 UK implementation

MTD for VATVAT100HMRCChecklistOdoo 19

Reviewed 5 November 2026. Use this checklist with the finance owner and qualified accountant before relying on an Odoo 19 UK VAT workflow. It covers implementation evidence and operational controls. It does not determine statutory treatment, exemption eligibility or the correctness of a return.

1. Confirm the legal-entity and obligation scope

Record each legal entity, principal place of business, VAT registration number, VAT accounting schemes and relevant VAT periods.
Confirm which entities are UK-based and therefore within the documented Odoo submission workflow.
Identify outstanding, late or amended obligations before selecting the first live Odoo period.
Record any exemption question and use the HMRC process; do not infer an exemption from migration difficulty or software unfamiliarity.
Name the finance owner, return preparer, reviewer, authorised software user and qualified accountant responsible for advice and review.

Evidence should include the approved entity register, VAT details, obligation calendar and any relevant HMRC correspondence. A database containing several companies is not proof that every company has the same VAT status or submission responsibilities.

Primary references: HMRC's MTD for VAT collection and VAT Notice 700/22.

2. Verify the Odoo 19 UK localisation baseline

Confirm the intended environment uses the Odoo version and modules named in the approved design. The current product baseline for this checklist is Odoo 19; Odoo 20 announcements are evaluated separately and are not current-capability evidence.

The Odoo 19 UK localisation guide documents UK Accounting with a CT600-ready chart of accounts and VAT100-ready tax structure, and UK Accounting Reports with VAT-report submission through the MTD-VAT API.

Verify the installed modules and UK chart, taxes and reports against the approved configuration.
Review account types, tax groups, tax accounts, report lines and default taxes with finance.
Confirm journal, currency, payment-term and fiscal-position behaviour using representative transactions.
Record every local deviation from the baseline and its acceptance result.

A CT600-ready chart does not file Corporation Tax returns. A VAT100-ready structure does not establish correct treatment for the organisation. Payroll, CIS, Bacs, Peppol and other requirements need their own assessment and are not implied by this checklist.

3. Check required digital records

Map the fields required by VAT Notice 700/22 to the systems and records that will form the electronic account. The notice allows the complete account to span compatible programs, provided the required digital journey is maintained.

Designatory data: Verify business name, principal place of business, VAT registration number and VAT schemes.
Supplies made: Verify tax point, net value excluding VAT and VAT rate for relevant supplies, plus required period summaries and adjustments.
Supplies received: Verify tax point, value and input tax to be claimed, together with the evidence needed to support deduction.
Summary data: Verify the values and adjustments needed to support the VAT Return are produced from the maintained digital records.
Original evidence: Identify invoices, import VAT certificates and other records that must be retained in original or permitted digital form.

Use organisation-specific scenarios approved by the accountant. Include relevant credit notes, partial payments, cash or invoice accounting, reverse charges, corrections and adjustments. Do not add tax scenarios that do not apply merely to create a longer test script.

The acceptance record links each scenario to its source evidence, ledger entries, tax values and VAT-report effect.

4. Prove the digital-link journey

Draw the complete journey from operational source to VAT submission. Include sales and purchase systems, expenses, inventory or manufacturing postings, spreadsheets, manual adjustments, migration files, bridging products and HMRC submission.

For every hand-off, record the source, destination, data owner, mechanism, transformation, evidence and error recovery. Confirm that transfers within and between products forming the electronic account use a digital link where HMRC requires one.

HMRC accepts examples including linked cells, CSV or XML import and export, file upload and download, automated transfer and API transfer in the appropriate context. Copy-and-paste is not a digital link. Do not confuse initial manual capture with an undocumented manual transfer between parts of the electronic account; ask the accountant to review the statutory interpretation of the actual design.

Test failed and repeated transfers as well as normal ones. A digital mechanism is not adequately controlled if a retry silently duplicates records or an integration error requires untracked rekeying.

5. Reconcile migrated data and opening VAT positions

Before live submission, reconcile the chart, taxes, contacts, open invoices, bills, credit notes, payments and opening balances to the approved source baseline. Use stable external IDs and repeatable imports so corrections do not create duplicates.

Verify open-document dates, outstanding amounts, currencies, tax codes and allocations with finance. Check their effect on the intended VAT report and period. A trial-balance match alone does not prove that document-level tax behaviour is correct.

Identify obligations more than three months late before migration. Odoo 19 states that these cannot be submitted through Odoo because only open obligations from the last three months are retrieved; the documented route is to contact HMRC for manual submission.

Preserve source extracts, mapping versions, import logs, exception decisions and reconciliation sign-offs. They provide the audit trail from old-system records to the new electronic account.

6. Test HMRC authorisation and access control

Record the authorised Odoo user and the legal entity for every connection. Test the connection from the intended UK tax report and confirm that company information is entered on the HMRC platform by an authorised person.

Verify obligation retrieval, period selection and the send action with the intended user and entity.
Confirm who can grant, renew or withdraw software authority and how role changes are handled.
Confirm that credentials are not shared informally in project documents or support tickets.
Retain the test result, relevant HMRC response and the operational escalation route.

HMRC's compatible-software guidance explains the authority granted to software. Treat that authority as part of finance access governance, including leaver and transfer procedures.

The HMRC software service lists “Odoo - Accounting” for record keeping and VAT-return submission. HMRC says it cannot recommend one product over another; use the listing as compatibility evidence and still test your exact environment.

7. Rehearse multi-company submission where applicable

Odoo 19 documents that only one company and one user can connect to HMRC simultaneously. If several UK-based companies share a database, rehearse the documented procedure for each company before the close calendar depends on it.

The documented sequence requires the submitting user to select the intended company, reset or remove existing authentication credentials in the connected user's UK HMRC Integration settings, register for that company, submit its report and repeat for the others. During the process, the connection button is not available to the other UK companies in the documented flow.

Record the authorised user, company context, credential-reset owner, submission order and evidence for every entity. Test that the report and obligation belong to the intended VAT registration before declaration.

If the proposed operating model expects separate simultaneous connections, validate it rather than assuming it. The documented constraint may affect close scheduling and submission ownership.

8. Perform the pre-declaration review

The preparer and reviewer should work from the same controlled evidence pack. The pack includes the selected obligation, report period, VAT100 values, source ledger reports, digital-link exceptions, migration reconciliation and all manual adjustments.

Reconcile report values to the ledger and supporting records at the level finance requires.
Review tax codes, account mappings, credit notes, partial payments and corrections against the approved scenarios.
Investigate warnings, unexpected values and changes from the comparable prior period.
Confirm late obligations or multi-company constraints have been handled through their documented route.
Obtain the qualified accountant's review where required and record the treatment decisions.

The finance reviewer then makes the declaration decision. Neither the implementation partner nor the software declares that the organisation's information is correct on its behalf.

9. Control submission and retain the result

At submission, verify company, VAT registration, obligation and period one final time. Retain the values presented for declaration, approver evidence, submission confirmation or error response, and any follow-up action.

If submission fails, use the triage route to distinguish authentication, company context, obligation selection, configuration, data and third-party causes. Do not repeatedly send without understanding whether HMRC received an earlier attempt.

Store HMRC responses and receipts according to the organisation's retention controls. Link any subsequent correction to the original return evidence and accountant decision.

Update the operational runbook with what users actually encountered. Training should cover obligation retrieval, review, declaration, submission, error handling and evidence retention, not only the happy-path button sequence.

10. Complete the readiness sign-off

Before go-live, each owner confirms their evidence rather than giving a general readiness opinion.

The finance owner accepts entity, VAT, account, tax and report configuration.
Data owners accept migrated open documents, balances and exception resolution.
Process and integration owners accept digital records, digital links and recovery controls.
The authorised user accepts connection, company selection, obligation and submission procedures.
The reviewer confirms the declaration and evidence-retention process, with accountant input where required.
The release authority records residual risks, late-obligation actions and multi-company constraints.
Training and support owners confirm users know how to operate and escalate the live workflow.

Reassess the checklist when the Odoo version, modules, entity structure, VAT scheme, integration journey or statutory guidance changes. The review date and source list should change with that review.

Primary sources and educational boundary

This checklist was reviewed on 5 November 2026 against the following official sources:

The public OXP2026 sessions on discovery, migration practice and testing and readiness provide educational context for prototype, import and rehearsal controls. They are not Oakland references or statutory sources. HMRC and qualified professional advice govern statutory decisions; versioned Odoo documentation governs the product boundary.