Exit fallback moves to BC-EAD with 7-day electronic catch-up

Exit-side customs declarations during a system outage now run under the BC-EAD business-continuity procedureTulli with fixed electronic catch-up deadlinesTulli, and a trader's own system failure means declaring in TulliselvityspalveluTulli. Tulli rewrote the exit-declaration fallback page to that effectTulli.

When Tulli's system has an outage, Tulli tells customers and says whether the exit fallback may be usedTulli. During the outage, exit declarations are given on the BC-EAD and BC-EAD List of Items formsTulli also used in export fallback, sent to the Customs Clearance Centre at vienti.tulliselvityskeskus@tulli.fi. They are completed under the EU Excel table, which carries instructions and a BC-EAD template, and the EU Business Continuity Plan for the UCC Automated Export System for form contentTulli. A form sent for Tulli markings must be pdf. After the outage, an electronic declaration must also be given within seven daysTulli. Where the outage is in the trader's own system, declarations are given in TulliselvityspalveluTulli.

That replaces a permission-request modelTulli. The previous page allowed exceptional forms during a customer or Tulli disruption with a later electronic declaration. A trader outage had to be put to the Clearance Centre at sava.tulliselvityskeskus@tulli.fi. The request had to state the reason, the estimated duration, the place concerned and the declarations concerned. The customer had to report continuation and end to the same address and send the documents there. Retention was the current year plus three years. A message declarant could use net notification without separate permission. That permission machinery is goneTulli; the trader-outage rule is now a direction to the serviceTulli.

For goods with an electronically lodged arrival-at-exit notification, the exit notification is now due at the latest on the next working day after the outage endsTulli, and exit is confirmed to the exporter only once the exit notifications have been givenTulli. The previous text required presentation and exit notifications electronically after the outage with no late-sending code, and confirmed exit once they were in the AREX system.

Transit fallback at exit stays on the continuity procedure at the office of departure under T and TIR rulesTulli. Safety data at exit are required on an exit summary declaration where a TIR carnet was accepted as opened at departure in fallback without electronic transit and is presented at exit without a Tulli-confirmed TSAD carrying safety data or an equivalent documentTulli. Where goods leave under T transit directly across the border by road or rail, or by sea or air without entering temporary-storage records at exit, the TSAD is the transit fallback formTulli. A transit document without safety data may be used, with safety data then given electronically on a separate exit summary declaration. An exit summary reference given before transit may be entered as a preceding document, and where the exit office finds no safety data, the declaration must be lodged at the border before exit.

The previous page named the SSD form or an equivalent document for that safety-data case. The rewritten page names the Tulli-confirmed TSAD form or an equivalent document insteadTulli. For non-export goods moved by sea, air or rail, a manually sought loading permission still turns on the same pair: the MRN of the exit summary or the TSAD with safety data, shown to the nearest customs office. If the nearest office is closed, the messages may go by email to passitusseuranta@tulli.fi. Paper filings are accepted by stamping and emailed filings by reply. After a manual permission, the exit notification must now be given immediately after the outage endsTulli.

The fallback forms follow the EU Business Continuity Plan for the UCC Automated Export System and the EU BC-EAD Excel table and template.