Migrating VAT history from spreadsheets
Migrate VAT history with submitted returns, digital links, control account balances and adjustment logs intact.
Moving from spreadsheets to accounting software is a controls project as much as a software choice. VAT migration should preserve what was submitted, not overwrite history with a cleaner-looking but unsupported file. This guide explains VAT history migration so the migration supports VAT, MTD and year-end review.
For wider context, use Switch accounting system . If the topic affects a filing deadline, software choice or tax treatment, confirm the live position before acting. The workflow below is designed to keep the evidence in one place so the owner, bookkeeper and accountant can all review the same record.
Official point to verify
HMRC says data transferred between programs in functional compatible software must move through digital links, and that copy and paste is not a digital link. Check the current wording in HMRC MTD for VAT penalty factsheet before making a binding filing, software or tax decision.
What to control
| Area | Control | Why it matters |
|---|---|---|
| Submitted returns | Archive each VAT return and receipt | Historic filings need evidence |
| Control account | Bring forward the VAT liability or receivable correctly | Opening balances affect the first software return |
| Adjustments | Import or archive VAT error logs and manual workings | Future corrections need context |
| Digital records | Decide what history is live versus archived | Not all old lines need active import |
Review routine
Move in stages: freeze the old spreadsheet, reconcile the final position, map accounts and VAT codes, import opening balances, then run a short parallel review. Do not treat the migration as finished until old suspense items and unreconciled balances have owners.
A useful review note should answer three questions: what source evidence was used, what judgement was applied, and who approved the treatment. Keep that note beside the transaction or period report rather than in a separate inbox.
Common mistakes
- Importing old VAT totals without receipts
- Changing historic spreadsheet formulas after migration
- Forgetting old VAT suspense balances
The best prevention is a short, repeated checklist. If a control is too complicated to run every month or quarter, it will probably fail when the deadline is close.
How ReAI helps
ReAI gives the new system a cleaner start by combining imports, document evidence and accountant review. That helps the migration become a controlled finance process rather than a one-off data dump. For hands-on help with setup, see Accounting Assistance for Small Businesses .
Summary
Treat Migrating VAT history from spreadsheets as a recurring accounting control, not a one-off admin task. Put the source data, review owner, exception list and submission evidence in the same system before the deadline arrives. That makes compliance work easier to check and much less dependent on memory.