Fallback and Recovery Specification (FRS)

More documents

Recommendations

Info

DG TAXUD – EXCISE COMPUTERISATION PROJECT REF: ECP2-FITSDEV2-SC03-FRS FALLBACK AND RECOVERY SPECIFICATION (FRS) VERSION: 3.11-EN Management of data 4 Management of data 4.1 Ownership and holding of data In EMCS, each piece of information has: � an owner, i.e. the user who submitted the information; most times, it is an economic operator, either registered, and in that case he enters the information himself, or nonregistered, and in that case another user, possibly an official, enters it on his behalf; � a holder, i.e. the MSA that is responsible for keeping the reference version of information and for transferring it to any authorised partner whenever required; in principle it is the MSA that initially validated it, also called initiating MSA. The general principles that govern management of data are the following: � the owner is responsible for the accuracy of the submitted information; � only the owner of a data item is authorised to submit any update to that item, if updating is allowed; � if the case arises, the person (in particular, the official) who enters data on behalf of the owner is not responsible for the given information but only for entering exactly what the owner requested; � the holder MSA is responsible for formally validating submitted information and to report errors to the owner; � the holder MSA is not entitled to change anything to the information held, unless he is the owner as well; � the holder MSA is responsible for keeping information correct. Example: Upon submission of an e-AAD, the MSA of dispatch formally validates the submitted information and returns back the errors to the consignor, if any. The consignor (owner of the e-AAD) is responsible for correcting errors and resubmitting the e-AAD. If no errors are found, the MSA of dispatch becomes the holder of the e-AAD. In addition, the MSA of dispatch allocates an ARC to the e-AAD; the MSA of dispatch is therefore the owner of the ARC. This example shows how the same data group may be built from data items with different owners. 4.2 Rectification of data If, as a result of errors or mistakes, the information entered into EMCS needs to be rectified, the general business principle is that rectification information can only be cancelled or amended by its owner and that the rectification is validated by the holder of data. For convenience, it may be acceptable that the holder updates the information on behalf of the owner, but only with his explicit agreement. ECP2-FITSDEV2-SC03-FRSv3.11.doc Page 24 of 53
DG TAXUD – EXCISE COMPUTERISATION PROJECT REF: ECP2-FITSDEV2-SC03-FRS FALLBACK AND RECOVERY SPECIFICATION (FRS) VERSION: 3.11-EN Management of data Invalid or outdated information is never deleted but marked for history purpose, including where it results from mistakes. Necessary rectification of information is limited to a part of information and is changed only through well identified ways. Rectification is required at two levels: � at entry level: when information is submitted but not yet approved and stored; � at application level: when information has been entered into EMCS and, in most cases, immediately and automatically disseminated to all concerned partners, either economic operators or MSAs. 4.2.1 Rectification at entry level No information should be accepted and recorded within EMCS unless it has been submitted to a formal validation. The rules of formal validation are detailed in the description of each concerned use case. This applies both where information is submitted by an economic operator and where it is submitted by an official. MSA may find it useful to locally store a part of information they are preparing to send to their partners (for instance administrative cooperation messages); details of rectification depend on the organisation of each MSA and will have to be defined at the national level. MSAs are never allowed to rectify information of which they are not the owner; if they detect any anomaly that justifies a rectification, the MSA requires the owner of information, usually an economic operator, to perform the relevant rectification operation. 4.2.2 Rectification at application level Once information has been recorded in EMCS, it should only be corrected by using defined use cases. The System specification offers a range of functions that result in the ability to update a part of information. However, some information can only be rectified by cancellation and possible replacement of an e-AAD. Example 1: If, at submission time, an e-AAD is validated based on erroneous information, it is possible for the consignor to immediately cancel it (UC2.10) and resubmit the correct information (UC2.01). A new ARC is then allocated. This is possible only where the goods have not yet left the place of dispatch. Example 2: If at submission time, the consignor made a mistake when typing the excise number of the consignee, which could not be prevented by the initial checking, he may immediately issue a change of destination (UC2.05). ECP2-FITSDEV2-SC03-FRSv3.11.doc Page 25 of 53
Page 1 and 2: OWNER DG TAXUD ISSUE DATE 01/12/200
Page 3 and 4: DG TAXUD - EXCISE COMPUTERISATION P
Page 23: DG TAXUD - EXCISE COMPUTERISATION P
Page 53: DG TAXUD - EXCISE COMPUTERISATION P

Fallback and Recovery Specification (FRS)

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?