Fallback and Recovery Specification (FRS)

DG TAXUD – EXCISE COMPUTERISATION PROJECT REF: ECP2-FITSDEV2-SC03-FRS
FALLBACK AND RECOVERY SPECIFICATION (FRS) VERSION: 3.11-EN
Solution elements
5.3.2 FB02: Revert to manual without subsequent input
If an automated business process becomes unavailable, it is possible to carry out
manually the equivalent operations. No subsequent data input is then required (no
recovery needed). This is the case if the faulty process does not normally result in an
update of the e-AAD, or if the lack of update is judged acceptable, from a business point
of view.
Example:
If automatic risk assessment is unavailable, instead of waiting for the resources to
recover, it is more efficient to exercise it manually.
5.3.3 FB03: Revert to manual with subsequent input
If an automated business process becomes unavailable (e.g. due to a software or a
hardware failure or in case of scheduled unavailability for maintenance), the equivalent
operations are first carried out manually.
This is in particular the object of the paper fallback procedures described in Chapter 6.
To ensure completeness of the EMCS processing, the standard electronic operations have
then to be completed in deferred mode.
Technically, the only difference between the normal submission and the deferred
submission is the initial submission of an e-AAD. In all other cases, normal mode and
deferred mode are identical.
Example:
If submission of an e-AAD proves unavailable (although its availability requirement is
permanent), the consignor ought to delay the electronic submission as much as possible.
However, business constraints make that the actual dispatch of goods cannot be delayed.
Consequently, the goods will have to leave before a valid e-AAD exists. A fallback AAD
has then to be made to allow the goods moving under the cover of the Excise Number of
the consignor plus the Local Reference Number of the consignment.
It becomes then mandatory to submit the corresponding e-AAD as soon as the function
becomes available again.
5.3.4 FB04: No intervention – wait
When an exception impacts business processes that are not critically time-dependent and
when the anticipated delay does not exceed the acceptable limit for the related functions,
the normal response is to wait until the cause of the exception has been suppressed, and
the normal procedure can be used.
The economic operator chooses to use this response any time the expected delay is
judged acceptable, or if, for business reasons, regular EMCS procedures are preferred to
fallback procedures.
ECP2-FITSDEV2-SC03-FRSv3.11.doc Page 35 of 53