European Union (and EEA)

Regulation (EU) 2019/1239 on the Maritime Single Window (MSW)

30 controls. 1 other frameworks in our corpus share controls with it. Here is all of it, and how much of it you are already doing.

Page built . This page is derived from the framework corpus, which changes when the corpus is extended rather than daily.

30 controls 1 frameworks share controls with it European Union (and EEA) verified against its source document

Every control below is one this framework asks for. The right hand column counts how many other frameworks in our corpus carry the same control, which is the difference between doing this work once and doing it again for the next standard.

There is no implementation kit for this framework yet. The control list and the overlap above are free and complete.

What you already have

Frameworks whose controls overlap this one, most first. If you run any of them, the count is roughly what you have already evidenced.

If you runShared controls
ISO/IEC 23894:20231measure it →

Every control

CodeControlAlso in
EUMSW-1Maritime Single Window Reporting Obligations0
EUMSW-2Common Data Standards, Information Sharing, Interoperability0
EUMSW-3Data Protection, Cybersecurity, Privacy1
EUMSW-4Governance and EMSA Cooperation0
11Reuse the carrier's entry summary declaration data for other port-call reports0
12Designate the registration authority and register senders in the EMSWe user registry0
13Run a publisher node for the common addressing service0
14Feed the EMSWe ship database and use the location and hazmat databases0
17Name the user management authority for the ship sanitation database0
18Designate a national EMSWe coordinator with a clear mandate0
22Report EMSWe usage to the Commission every year0
4(2)Introduce no new national reporting requirement without Commission approval0
5(1)Establish and operate a maritime National Single Window for once-only reporting0
5(3)Keep the MNSW compatible, integrated, connected, supported and staffed0
5(4)Route information only to the authorities that need it and keep their systems interoperable0
5(5)Accept partial and extended submissions and let declarants share a subset with port service providers0
5(7)Store MNSW data only as long as necessary and then delete it0
5(8)Publish estimated and actual arrival and departure times in the harmonised format0
5(9)Use the uniform mnsw internet addresses and support website structure0
7Allow reporting through data service providers and voluntary channels, with a fallback0
8Apply the once-only principle across port calls0
9Declarants answer for the data they submit and keep it up to date0
AnnexReport every listed port-call obligation through the single window0
DR205Submit data in the harmonised EMSWe data set format0
IR204-IProvide the common graphical user interface functionalities0
IR204-SAccept harmonised XLSX spreadsheet uploads with version and data checks0
MACHINERYCommission duties and procedures under the Regulation0
REGULATIONRegulation (EU) 2019/1239: scope and definitions0
RIMIntegrate the reporting interface module and connect senders through AS40
STATUSStatus: applicable since 15 August 2025, implementation still incomplete, customs link pending0

Tell me when Regulation (EU) 2019/1239 on the Maritime Single Window (MSW) files something new

One email when a public company newly discloses something this framework governs, naming the company and what our corpus says it puts in scope. Nothing else, and one click to stop.

What this page is

A control-level reference for Regulation (EU) 2019/1239 on the Maritime Single Window (MSW), drawn from our framework corpus. Control codes and titles are references to the standard, not reproductions of it. The overlap counts and the auditor artefacts are our own work and are the part you will not find elsewhere.

Measure this against what you already run · All frameworks · Today's edition