/ THE SHORT ANSWER
- 01Locate the electronic account before assessing digital links.
- 02Preserve invoice evidence alongside extracted fields.
- 03Reconcile transfers using counts, values and identifiers.
- 04Make correction ownership explicit across business and accountant.
/ dotSuper point of view
The useful unit of a VAT systems review is the transaction journey, including its exceptions, rather than the software subscription.
Locate the electronic account
Ask them to follow an ordinary sales invoice.
Record each application, spreadsheet and handover, including any work performed by the external accountant.
HMRC permits a combination of software and describes acceptable digital links.
Its notice also distinguishes records inside the electronic account from other business systems.[
1] That distinction matters more than whether every factory application has an API.
Mark the point where transaction data becomes part of that account.
Then highlight every later transfer.
A clipboard operation that feels harmless to the operator may deserve a different assessment from initial capture.
Do not interpret a useful production spreadsheet as a tax system automatically.
Conversely, do not exclude a workbook merely because the finance manager calls it a working paper.
Its actual role should determine the review.
Preserve evidence beside extracted numbers
Store an accessible link to the invoice and any supporting correspondence.
Give the document a stable identifier independent of its filename.
GOV.UK's invoice guidance identifies core information such as supplier and customer details, dates, amounts and an invoice identifier.[
2] Use those fields as a starting point for validation, while separately checking applicable VAT invoice requirements.
For AI extraction, distinguish what the document says from what the business concludes.
An extracted tax amount is a proposed transcription.
It does not establish recoverability, the correct accounting period or treatment of a mixed supply.
Ask reviewers to correct the structured record, retaining the original evidence.
Quietly replacing the image with a cleaned-up version makes later explanations harder.
A readable archive and a controlled correction history serve different purposes.
Work through a hypothetical machining invoice
A supplier sends two documents with the same invoice number: the original and a corrected version.
The extraction service reads both successfully.
Without a duplicate rule, apparent automation accuracy conceals a duplicate liability.
Finance needs to identify the replacement relationship before either record feeds the return preparation process.
Suppose the shop processes 240 invoices monthly and eight need clarification.
Eight divided by 240 is about 3.3%.
That measures the clarification share, not an error rate or an expected saving from new software.
Track why those eight stopped.
A supplier document problem needs a different response from a broken import mapping.
Resolve the corrected-invoice example end to end before widening the exercise to purchase credits and deposits.
Choose transfers that someone can explain
It is a proposed operating control, not a substitute for applying the notice to the business's circumstances.
Retain row counts and control totals with each export.
A successful upload message says the system accepted a file.
It does not prove that every intended transaction arrived once, with the right sign and period.
Assign one person to maintain the mapping between source fields and destination fields.
When a supplier changes a column heading, an unattended integration should stop visibly rather than manufacture a plausible replacement value.
A modest file-based connection can be easier to govern than a heavily customised integration.
The choice should reflect transaction volume, exception frequency, support arrangements and the ability to recover a failed transfer.
| Transfer | Evidence to request | Decision |
|---|---|---|
| Ledger to spreadsheet | Export file and stable transaction IDs | Use a repeatable import |
| Spreadsheet to bridge | Linked cells or supported file import | Remove manual rekeying |
| Invoice to first record | Source image and approved extraction | Review ambiguous fields |
| Correction to ledger | Reason, owner and original reference | Preserve the audit trail |
| Accountant handover | Version and control totals | Agree one filing dataset |
Make corrections travel through the same system
If the correction exists only in their workbook, the business may repeat the error in the next extract.
Agree where the authoritative correction belongs and how the adjusted dataset returns to finance.
Separate a revised transaction from a filing adjustment so that neither silently overwrites the other.
Lock approved periods through normal application controls.
When reopening is necessary, record the reason, approver and affected downstream outputs.
An AI assistant may draft the explanation, but it should not decide whether to reopen records.
Include a recovery procedure for interrupted imports.
A second attempt should recognise transactions already loaded.
Otherwise, recovering from a connection failure can create a larger reconciliation problem than the original interruption.
Decide whether repair is enough
These cases reveal whether the existing tools can support a coherent process with reasonable maintenance effort.
Replacement becomes more credible when required exports are unavailable, record ownership remains fragmented, or supported correction paths are missing.
A frustrating interface alone does not establish that migration will solve the underlying problem.
Before approving expenditure, write down the current reconciliation effort and the specific failure each proposed change addresses.
Include training, archive access and the accountant's workload in the decision.
The immediate next move is a shared transaction map and an agreed correction owner.
Those deliverables make either a small integration repair or a larger migration substantially easier to specify and review.
What this page cannot conclude
- 01VAT schemes, groups and exemptions require case-specific accounting review.
- 02This workflow does not determine tax treatment or certify software compliance.
- 03This article was researched and drafted with AI assistance. Sources and limitations are provided for scrutiny; it is not an independent professional review or a compliance certification.
Sources
- 01VAT Notice 700/22: Making Tax Digital for VATHM Revenue & Customs · accessed Sep 15, 2026
- 02Invoices: what they must includeGOV.UK · accessed Sep 15, 2026
This article was researched and drafted with AI assistance. Sources and limitations are provided for scrutiny; it is not an independent professional review or a compliance certification.
Our editorial standard · Found an error? Send a correction with its source.
/ CITE OR SHARE THIS GUIDE
Make the evidence easy to verify.
When you reference this guide, link to its canonical URL. That gives readers one stable place for the evidence, limitations and future updates.
dotSuper Research Desk. (September 15, 2026). Your VAT Spreadsheet Needs a Traceable Digital Journey. dotSuper. https://dotsuper.net/feeds/applied-systems/uk-vat-spreadsheet-digital-links