This part of GOV.UK is being rebuilt – find out what beta means

HMRC internal manual

VAT Assessments and Error Correction

How to assess and correct: Error correction procedures: VAT642 pre processing action

N.B. Information on capturing, attaching secure notes and forwarding documents in EF can be found in the EF user guide on the VSLT website System Owner Team.

The authorising officer will then look at case details in the penalty toolkit in SEES (until NPS becomes available) and EF, authorise the VAT642 update the secure note and forward to the VALID team for input

The information which is keyed from this document will be transferred to the VAT Mainframe and processed overnight to update the trader’s file.

However, before the file is actually updated, a number of checks are carried out and the document may be rejected.

The errors that will cause the input to reject are detailed in the document VALID Rejection Errors Reported on D0502 Print along with the action you will have to take to successfully re input the VAT642. This print is sent to the VALID Team who will return the original document for correction, or alternatively, it is possible to view the rejected input document via PRADA (Print Retrieval and Data Access).

If the input passes these checks, the computer will produce a VAT657 Notice of Error Correction, a copy of which is downloaded into EF. This information is used by the VALID team to accept the VAT 642.