IMO DCS vs EU MRV: full comparison

Any ship of 5,000 GT and above that calls at a European Economic Area port must comply simultaneously with two parallel fuel and emissions reporting regimes. The IMO Data Collection System, established by MARPOL Annex VI Regulation 27 and in force from 1 January 2019, collects annual aggregate fuel consumption data submitted to flag Administrations and held in the non-public IMO GISIS database; its output drives the CII rating. The EU MRV Regulation (EU) 2015/757, in force from 1 January 2018, requires per-voyage records submitted through THETIS-MRV, publicly disclosed per ship, and feeding EU ETS allowance surrender and FuelEU Maritime compliance. Both regimes share the same four measurement methods and largely the same ship threshold, but they differ on granularity, gas scope, verifier model, transparency, downstream obligations, and the precise boundary of what counts.

This article places the two regimes side by side: regulatory basis and history, the exact scope of each, the difference-by-difference matrix across nine dimensions, the double-reporting burden, the (limited) alignment between them, and the changes made in 2023 to 2026 that have shifted the distance between the two systems. For the full legal treatment of each regime individually, see IMO Data Collection System and EU MRV Voyage Data.

Regulatory basis and entry-into-force dates

IMO DCS: MARPOL Annex VI Regulation 27

The IMO Data Collection System originates from Resolution MEPC.278(70), adopted at the 70th session of the Marine Environment Protection Committee on 28 October 2016. That resolution amended MARPOL Annex VI to insert what was then called Regulation 22A (now renumbered Regulation 27 in the current consolidated text) and Appendix IX, which prescribes the standardized data reporting form. The amendments entered into force on 1 March 2018, with the first full calendar-year data collection starting 1 January 2019.

The companion resolution MEPC.282(70), adopted the same day, issued the 2016 Guidelines for the Ship Energy Efficiency Management Plan Part II, which is the document a ship uses to record its chosen fuel measurement methodology. The DCS sits inside Chapter 4 of MARPOL Annex VI alongside the EEDI (Regulation 20), the SEEMP (Regulation 26), and the CII (Regulation 28). It was designed explicitly as Phase 2 of a three-phase GHG strategy announced at MEPC 70: Phase 1 was EEDI and SEEMP (2013), Phase 2 was the DCS (2018), and Phase 3 was the operational carbon intensity framework including CII and EEXI, which entered force 1 November 2022.

EU MRV: Regulation (EU) 2015/757

The EU MRV Regulation was adopted by the European Parliament and Council on 29 April 2015 and published in the Official Journal on 19 May 2015. It entered into force on 1 July 2015 and became operational for data collection on 1 January 2018, when ships were first required to carry an approved monitoring plan and begin per-voyage data recording. The European Maritime Safety Agency’s THETIS-MRV platform opened to receive ship data for reporting year 2018 onwards.

The legal text has been amended twice. Commission Delegated Regulation (EU) 2016/2071 tightened the monitoring methodology annexes. The major substantive overhaul came with Regulation (EU) 2023/957, adopted 10 May 2023, which extended the scope to smaller vessels from 1 January 2025, added methane and nitrous oxide to the gases covered from 1 January 2024, adjusted the monitoring plan obligations, and aligned the regulation’s data architecture with the EU ETS for Shipping that started 1 January 2024.

What the two systems share

The overlap is real and useful in practice. Both regimes apply the same four fuel measurement methods: BDN plus tank stocktakes (the mass-balance method), flow meters on fuel supply lines, bunker fuel tank monitoring via daily automated soundings, and direct CO2 exhaust-gas measurement. A method documented in the SEEMP Part II satisfies the EU MRV monitoring plan’s measurement requirement for the same parameter. Most operators maintain one combined monitoring plan with a small annex covering the MRV-only voyage category and cargo fields.

Both use the same CO2 conversion factors. MEPC.364(79) Cf factors, such as 3.114 for HFO and VLSFO, 3.206 for MGO, and 2.750 for LNG, are the reference for both regimes. That prevents two different emission accounting results from the same fuel mass.

Both apply to ships of 5,000 GT and above as the primary threshold. Both require an accredited third-party reviewer of some form before the output document is issued. And both sit on a ship’s inspection checklist: port-state control checks for the Statement of Compliance (DCS) and the Document of Compliance (MRV).

These similarities mean the underlying measurement exercise is largely shared. The differences arise in how that measurement is packaged, disclosed, and used downstream.

Difference-by-difference comparison

Scope and ship threshold

The IMO DCS applies to ships of 5,000 GT and above engaged on international voyages, globally. There is no geographic restriction: a ship on a Pacific route that never calls at a European port still falls within DCS scope. The 5,000 GT line is consistent with the CII threshold in Regulation 28 and the EEXI threshold in Regulation 24.

The EU MRV began with the same 5,000 GT threshold but restricted to ships calling at EEA ports. From 1 January 2025, Regulation (EU) 2023/957 extended MRV scope down to general cargo ships of 400 to 4,999 GT calling at EEA ports, and to offshore ships of 400 GT and above. The offshore category was defined by Commission Delegated Regulation (EU) 2024/3214, published 27 December 2024, to include offshore support vessels, pipe-layers, crane vessels, and drilling ships, among others, but not icebreakers. That expansion creates a band of ships, those between 400 and 4,999 GT in certain categories, that must comply with EU MRV but have no DCS obligation at all.

The DCS scope has never included a sub-5,000 GT tier. The IMO has discussed whether smaller vessels should eventually be brought in, but no amendment is in force as of mid-2026.

Reporting granularity: annual aggregate versus per voyage

This is the structural difference from which many others follow. The DCS collects annual aggregates: one row per fuel type covering fuel consumed, distance sailed, and hours underway for the entire calendar year. It does not require any breakdown by voyage, route, or port pair.

The EU MRV requires per-voyage records from which the annual total is built up. For every voyage departing from or arriving at an EEA port, the ship records fuel consumed at sea, fuel consumed at berth, CO2 and (from 2024) CH4 and N2O emissions, distance sailed, time at sea, time at berth, cargo carried or passenger count, and the resulting transport work. Those voyage records are then aggregated into an annual emissions report, but the underlying voyage-level dataset is retained in THETIS-MRV.

The per-voyage requirement is not cosmetic. It enables the voyage category weighting (100% intra-EEA, 50% extra-EEA) that the EU ETS needs to calculate covered emissions. It lets the Commission publish energy efficiency metrics per voyage type. It allows charterers and cargo owners to track the carbon intensity of specific trades. None of that analysis is possible from annual aggregates.

An operator’s data discipline follows from this: voyage departure and arrival timestamps, logged manually in the bridge watch record, must be accurate enough to support the voyage boundary. A ship that fails to log arrival at an EEA port correctly cannot reconstruct the voyage-fuel split post-hoc from an annual total.

Scope weighting

The DCS has no scope weighting. Every tonne of fuel consumed on any international voyage, from a transpacific bulk carrier leg to a short intra-European ferry crossing, counts equally in the annual total. The DCS total is a raw global figure.

The EU MRV applies geographic weighting. Intra-EEA voyages (both ports in the EEA) count at 100%. Voyages where one port is inside the EEA and the other outside count at 50%. Voyages entirely outside the EEA generate no MRV record. This weighting was designed from the outset to feed the EU ETS: the 50/100 split determines how many emission units map to how much CO2.

A ship on a round-the-world route that calls at one EEA port per rotation will have a DCS total comprising its entire year’s fuel burn. Its EU MRV total will cover only the legs touching that EEA port, weighted at 50% for the arriving and departing extra-EEA legs. The two figures will be entirely different in magnitude. Operators who expect them to reconcile are working from a false premise.

Data elements: efficiency metrics and cargo

The DCS original data set is three fields: fuel by type, distance, and hours underway. From data year 2026, MEPC.385(81) adds fuel by consumer type (main engines, auxiliary engines, boilers, and other), transport work, and onshore power in kWh.

The EU MRV has collected cargo carried and transport work since 2018. Each voyage record includes cargo mass or volume (for cargo ships) or passenger numbers (for passenger ships), from which transport work in tonne-miles or passenger-miles is derived. The MRV annual emissions report also includes three energy efficiency indicators: the Energy Efficiency Operational Indicator (EEOI) or a comparable metric, the Average Energy Efficiency per Transport Work (AER-type numerics), and a time-weighted average efficiency across voyages. The Commission publishes these per ship in the THETIS-MRV public dataset.

The Annual Efficiency Ratio that feeds MRV-derived efficiency comparisons is structurally similar to the CII fed by DCS data, but the denominators differ: AER uses actual cargo carried (transport work divided by capacity-miles), CII uses a fixed notional capacity. A ship with variable load factors will score differently on each metric even if the underlying fuel burn is identical.

Gas coverage

The DCS covers CO2 only, using the MEPC.364(79) Cf factors to convert fuel mass to CO2 equivalent. Methane and nitrous oxide are not reported, even for LNG-fuelled ships where methane slip from the combustion process is a material GHG consideration. The IMO MEPC.391(81) LCA guidelines adopted alongside MEPC.385(81) provide well-to-wake emission factors for alternative fuels, and the IMO’s mid-term measure discussions include lifecycle GHG metrics, but no amendment adding CH4 or N2O to the DCS reporting form is yet in force.

The EU MRV, from 1 January 2024 under Regulation (EU) 2023/957, requires ships to monitor and report CH4 and N2O in addition to CO2. The monitoring methodology for each gas is specified in Annex I of the amended regulation. CH4 matters because it is roughly 84 times more potent than CO2 on a 20-year global warming potential basis; N2O is around 298 times more potent. For LNG-fuelled vessels, CH4 slip from high-pressure direct-injection engines can represent a material fraction of total GHG output even if CO2 mass alone looks favorable. Ships reporting under EU MRV must now document CH4 and N2O per voyage in addition to CO2, and those figures appear in the public THETIS-MRV dataset.

This gas-scope gap means a DCS-compliant ship and an MRV-compliant ship burning identical fuels will produce differently shaped annual reports. The DCS number understates total GHG in cases where methane slip is material. Charterers and ESG-rating agencies increasingly cross-reference MRV CH4 disclosures against DCS CO2 figures, and the divergence is visible.

Verification model

The DCS uses a flag-state or recognized organization (RO) verification model. The flag Administration, or an RO it has authorized under MARPOL Annex VI Regulation 27.7, reviews the ship’s annual data and issues the Statement of Compliance not later than 31 May. Resolution MEPC.348(78), the 2022 Guidelines for Administration verification, sets out the verification programme: the Administration checks consistency, completeness, and reliability of the reported data against supporting documents (BDN summaries, logbook entries, tank sounding records). A material discrepancy, defined as one that could influence the total by more than ±5%, must be resolved before the Statement is issued.

The RO acts as an extension of the flag Administration under Regulation 27.7. The Administration “assumes full responsibility for all tasks conducted” by the RO, per MEPC.348(78) section 3.2. In practice, 105 of 135 flag Administrations delegated DCS verification to recognized organizations for reporting year 2023.

The EU MRV uses an independently accredited verifier model. Under Regulation (EU) 2015/757 and the Accreditation and Verification Regulation (EU) 2016/2072, the verifier is an independent body accredited by a national accreditation body in an EU member state, not an agent of a flag state or of the ship company. Class societies (DNV, Lloyd’s Register, Bureau Veritas, and others) operate as accredited verifiers, but they do so under a separate accreditation structure from their RO function. The verifier reviews per-voyage data, the monitoring plan, and supporting documents, then issues the Document of Compliance. The DoC must be on board from 30 June of each year.

The accountability structure differs in a legally important way. If an RO acting for a flag state issues a DCS Statement of Compliance for data that later proves inaccurate, responsibility rests with the flag Administration. If an EU MRV accredited verifier issues a Document of Compliance for data later found to be incorrect, the verifier’s accreditation is at risk. That distinction creates different incentive structures around data quality scrutiny.

Transparency and public disclosure

DCS data is not public at the ship level. The IMO publishes an annual anonymized fleet-level report to MEPC covering total fuel consumption and CII rating distributions by ship type and size band. Individual ship records in the GISIS fuel oil consumption database are not accessible to charterers, cargo owners, financial institutions, or the public. MEPC.385(81) added Regulation 27.14, allowing the IMO Secretary-General to share data with analytical consultancies under strict confidentiality rules, and Regulation 27.15, allowing a company access to its own ships’ non-anonymized records on request. Both are access expansions from the original 2016 regime, but neither creates a public per-ship disclosure.

EU MRV data is published per ship annually by the European Commission via THETIS-MRV. The published dataset includes each ship’s total CO2 (and from 2024, CH4 and N2O), annual transport work, and the derived efficiency indicators. The Commission publishes this by 30 June each year for the preceding reporting year, so reporting-year 2024 data was due public by 30 June 2025. The EMSA THETIS-MRV platform makes the per-ship dataset downloadable, and third-party services (including commercial ship databases and ESG data providers) incorporate it into commercial products.

This transparency gap has practical market consequences. A charterer evaluating voyage efficiency can pull a ship’s EU MRV carbon intensity directly from THETIS-MRV for any ship with EEA trade history. For the same ship’s non-EEA performance, or for ships that never call at EEA ports, no analogous public disclosure exists.

Output documents

The SoC records the annual fuel totals by type, distance sailed, hours underway, the attained CII, and the A-to-E rating (from 2023). The DoC records confirmation that the annual emissions report meets Regulation (EU) 2015/757 requirements. Both must be on board for port-state control inspection. A missing SoC is a deficiency under MARPOL Annex VI; a missing DoC can result in port entry being refused and, after two consecutive non-compliant years, an expulsion order.

Downstream use: what each system feeds

DCS data feeds IMO regulatory outputs. The primary downstream obligation is the CII rating: the attained CII is calculated from the DCS annual fuel and distance totals, rated A to E on the Statement of Compliance, and if rated D or E triggers a corrective action plan requirement in SEEMP Part II and III. A D rating for three consecutive years or an E in any single year requires an updated corrective action plan before the next SoC can be issued. The CII is a reputational and operational obligation, not a financial market mechanism.

DCS data also informs the IMO GHG Strategy. The IMO uses the anonymized GISIS dataset to track fleet-level progress toward the 2023 Revised IMO GHG Strategy targets (40% carbon intensity improvement by 2030 against 2008 baseline, net zero GHG by or around 2050). The mid-term measures under discussion at MEPC, including the GHG Fuel Intensity Standard and the IMO Carbon Levy (the “IMO Net Zero Framework”), will draw on enhanced DCS data once MEPC.385(81) transport work figures are available from reporting year 2026.

EU MRV data feeds financial and market obligations. The EU ETS for Shipping, which started 1 January 2024, uses verified MRV emissions data to calculate each shipping company’s EU Allowance surrender obligation. The phase-in applies 40% of 2024 covered emissions (EUAs due September 2025), 70% of 2025 covered emissions (EUAs due September 2026), and 100% from 2027. Covered emissions are the MRV-verified CO2 figures weighted by voyage category.

FuelEU Maritime, which applies from 1 January 2025, uses MRV data to calculate the GHG intensity of energy used on board. The FuelEU intensity calculation is a well-to-wake figure using lifecycle factors from Regulation (EU) 2023/1805 Annex II, not the Cf factors in MEPC.364. Ships that miss the GHG intensity threshold face a FuelEU penalty or must balance their shortfall against a surplus from another ship or from a pool.

The downstream consequence of a DCS failure is a missing or withheld SoC plus an adverse CII rating. The downstream consequence of an MRV failure is, progressively: a missing DoC, port entry refusal, ETS compliance shortfall with penalty interest, and FuelEU compliance exposure. MRV non-compliance carries harder financial teeth.

The double-reporting burden in practice

Every ship of 5,000 GT and above trading to Europe runs two parallel compliance tracks with different deadlines, different verifiers, and different document chains. The combined annual compliance calendar looks like this:

The Q1 data-preparation window runs from 1 January to 28 February and carries obligations for both systems simultaneously. A company that treats DCS and MRV as one compliance exercise will discover that MRV needs its verified report by 31 March while the DCS SoC isn’t required until 31 May. The MRV verification runs ahead of the DCS verification, which means the MRV verifier and the DCS verifier may be reviewing overlapping datasets in January and February with no formal coordination mechanism.

Most fleet operators have resolved this by using the same class society as both the flag RO (for DCS) and the accredited verifier (for MRV). That consolidation cuts the dual-audit overhead, since the verifier can review the monitoring plan, BDN pack, and voyage logs once. It doesn’t eliminate the separate output documents, the separate submission chains, or the separate downstream obligations, but it prevents the same source data being reviewed twice by two completely independent parties who may reach different materiality judgments.

Operators that split the two verifiers, using one class society for flag RO work and a different accredited verifier for MRV, spend more on the combined audit and risk inconsistent findings. If the DCS verifier accepts a gap-filling estimate that the MRV verifier rejects, the company faces two different fuel totals for the same ship year, which shows up as an unexplained discrepancy if a port-state control officer cross-checks the SoC against the DoC.

The monitoring plan: one document, two sets of requirements

One practical alignment tool is the combined monitoring plan. Both regimes require a plan that documents measurement methodology before the first data collection period:

• DCS requires a SEEMP Part II per Resolution MEPC.282(70), which the flag Administration or authorized RO must approve before data collection begins. The plan has nine mandatory sections: ship particulars, revision history, fuel consumers and types, fuel measurement method, distance measurement method, hours underway method, data reporting processes, reporting format, and data quality procedures. The approved plan produces a Confirmation of Compliance, the document that must be on board before the first reporting year begins.

• EU MRV requires a Monitoring Plan under Article 6 of Regulation (EU) 2015/757, approved by the accredited verifier before the monitoring period starts. The plan covers ship identification, fuel types and Cf factors, measurement method per fuel type, procedures for data gaps, voyage boundary definitions, cargo measurement method, and the responsible company contact.

The content overlap is substantial. Operators preparing a combined document typically draft the nine SEEMP Part II sections to satisfy both sets of requirements, then append a short annex covering the MRV-only elements: voyage category classification logic (how the ship identifies whether a port is inside or outside the EEA), per-voyage cargo measurement procedures, and the data fields for CH4 and N2O monitoring from 2024. The four measurement methods accepted by MARPOL Annex VI are identical to those in EU MRV Annex I, so a method documented for DCS satisfies the MRV plan requirement for the same parameter.

The combined plan creates a single audit-ready document. It should state explicitly which sections satisfy which regulatory obligation, so both the flag RO and the MRV accredited verifier can identify their respective scope without re-reading the whole document each time.

One practical complication: the DCS plan needs to be updated before 1 January 2026 to add the enhanced MEPC.385(81) data fields (fuel by consumer type, transport work). That update requires flag Administration or RO re-approval. If the combined monitoring plan covers both regimes, the 2025 SEEMP Part II revision also becomes the point at which the MRV verifier should check that the CH4 and N2O methodology is properly documented, since the 2023/957 amendment’s gas extension also required monitoring plan updates from 2024.

The (lack of) full alignment and why it persists

The IMO and the EU are aware that running parallel systems creates duplicate compliance cost. They have not reached full harmonization, and three structural reasons explain why that gap is unlikely to close completely.

Political jurisdiction. The IMO is an intergovernmental body whose MARPOL amendments require broad ratification. The EU acts within its own legal order and can amend Regulation 2015/757 by internal legislative procedure. The EU’s 2015 MRV predates the IMO’s 2018 DCS by three years. Having established a working system, the EU had no reason to wait for the IMO’s slower process. The IMO, for its part, cannot simply adopt the EU MRV per-voyage format without amending MARPOL Annex VI through the tacit amendment procedure, which requires two-thirds approval at MEPC plus a 16-month waiting period.

Downstream obligation design. The EU MRV produces data that feeds two financial obligations (EU ETS, FuelEU Maritime), each of which requires the voyage-category split and per-voyage granularity that the DCS was never designed to provide. Making the IMO DCS match MRV granularity would be the equivalent of designing the IMO DCS to service EU financial market mechanisms, which is outside the IMO’s mandate and would be contested by non-EU member states.

The gas extension. The EU’s addition of CH4 and N2O from 2024 reflects the EU’s precautionary approach to LNG shipping’s methane slip issue and to N2O from SCR systems. The IMO’s MEPC.391(81) LCA guidelines take a lifecycle approach to alternative fuel GHG emissions, but that framework feeds the mid-term fuel intensity standard, not the DCS reporting form. The IMO has not adopted CH4 or N2O into the DCS mandatory data elements.

What the IMO has done is narrow the most visible measurement gap. The MEPC.385(81) transport work addition, from data year 2026, brings DCS data closer to the MRV cargo-and-efficiency information that the EU has collected since 2018. Once the first DCS transport-work figures enter GISIS (expected from the MEPC 84 reporting cycle in late 2027), analysts will be able to compare per-ship intensity on a tonne-mile basis from both datasets for the first time. The comparison will still not be equivalent because DCS covers the global voyage profile while MRV covers only the EEA-touching legs, but the metric is at last common.

Recent and forthcoming changes

Already in force (2023 to 2025)

EU MRV gas extension (1 January 2024). Regulation (EU) 2023/957 added CH4 and N2O to the MRV monitoring obligation. Ships must monitor and report both gases per voyage from reporting year 2024. The monitoring methodology for CH4 and N2O is in Annex I of the amended regulation; the mass-based approach using fuel-type-specific emission factors is the baseline method.

EU MRV scope extension to smaller vessels (1 January 2025). General cargo ships of 400 to 4,999 GT and offshore ships of 400 GT and above now have MRV reporting obligations. The 400-4,999 GT band does not yet carry an EU ETS obligation (the threshold remains 5,000 GT for ETS), so these vessels face MRV data collection without ETS surrender requirements. The practical effect is that a general cargo feeder calling at Rotterdam must now compile a monitoring plan, per-voyage records, and an annual emissions report, even though it doesn’t surrender EUAs.

IMO DCS enhanced granularity (data year 2026). MEPC.385(81), in force 1 August 2025, adds fuel by consumer type, transport work, and onshore power to Appendix IX. Ships must update their SEEMP Part II before 1 January 2026 to document the new measurement methodologies. The enhanced data enters the GISIS database from reporting year 2026 onwards, making the first IMO dataset with systematic transport work coverage available at MEPC 84 in the second half of 2027.

EU ETS phase-in through 2027

The EU ETS for shipping phase-in directly uses MRV verified data. The allowance surrender schedule is:

• 40% of covered 2024 emissions: EUAs surrendered by 30 September 2025.
• 70% of covered 2025 emissions: EUAs surrendered by 30 September 2026.
• 100% of covered 2026 emissions and all subsequent years: EUAs surrendered by 30 September each year from 2027.

“Covered emissions” means the MRV-verified CO2 total weighted by voyage category. The 100% phase-in from 2027 will represent the first year in which the full MRV-verified figure drives allowance surrender with no discount for the phase-in. Companies that have been managing ETS exposure at 40% and 70% of covered emissions face a step change in allowance cost in 2027. Operators can model the exposure using the EU ETS for shipping framework alongside the FuelEU Maritime compliance tools.

FuelEU Maritime from 2025

FuelEU Maritime, Regulation (EU) 2023/1805, applies from 1 January 2025. The annual GHG intensity target is expressed as a maximum grams of CO2-equivalent per megajoule of energy used on board, calculated on a well-to-wake basis. The FuelEU assessment uses the same MRV voyage data as the EU ETS but applies lifecycle emission factors from FuelEU Annex II rather than the Cf factors in MEPC.364. Ships that miss the target face the FuelEU surplus/deficit pooling mechanism and, if the deficit persists, a financial penalty.

FuelEU thus creates a third downstream use for MRV data, alongside EU ETS allowance calculation and the public efficiency disclosure in THETIS-MRV. A single verified MRV annual emissions report now simultaneously determines the ship’s ETS surrender obligation, its FuelEU GHG intensity compliance status, and its position in the public THETIS database. The DCS SoC determines only the CII rating, which carries no direct financial obligation (the corrective action plan obligation is operational, not monetary).

IMO mid-term measures under negotiation

MEPC 80 (July 2023) adopted the Revised IMO GHG Strategy, committing to net zero by or around 2050. The mid-term measures package being finalized at MEPC 83 (2025) and MEPC 84 (2026) includes a GHG Fuel Intensity Standard and an economic mechanism (widely described as a carbon levy). Both would use DCS data as the underlying compliance signal. If an IMO carbon levy is adopted, the DCS system would for the first time carry a direct financial consequence analogous to the EU ETS, and the data quality and transparency debate around GISIS would intensify. The outcome of the MEPC 83 negotiations has not been finalized as of this writing. See IMO Net Zero Framework for the developing picture.

Compliance architecture for dual-regime operators

Ships trading to Europe run both compliance tracks. The practical architecture that minimizes cost and error risk has four components.

Unified source data. A single on-board data system, or at minimum a single company-side data lake, captures the fuel measurements, BDNs, voyage timestamps, and cargo figures that both regimes need. The voyage-granularity required for MRV is a superset of what DCS needs; maintaining voyage-level records automatically satisfies DCS’s annual aggregate requirement. Operators who run DCS and MRV as separate data streams end up with reconciliation work at year-end when the MRV voyage-sum and the DCS annual total don’t match because they started from different raw data.

Combined monitoring plan. One document covering both SEEMP Part II obligations and the MRV Article 6 monitoring plan requirements, structured to be readable by both the flag RO and the MRV accredited verifier. The plan should call out, section by section, which requirement each section satisfies.

Single verifier where possible. Using the same class society as both the flag RO (for DCS verification) and the MRV accredited verifier eliminates parallel review of the same source documents. This is the standard practice for major fleets at DNV, Lloyd’s Register, Bureau Veritas, and similar societies, all of which operate both functions under the same umbrella with appropriate internal segregation.

Parallel document tracking. Despite the shared methodology, the SoC and the DoC have separate issuance chains and separate on-board retention requirements. The SoC must be retained for five years. The DoC must be current (a DoC for reporting year 2023 is not valid for 2024 compliance). A fleet management system should track both documents by ship, flag, and verifier identity, because a port-state control inspection that finds a current SoC but an expired DoC results in a deficiency for the MRV regime regardless of DCS compliance status.

Limitations

Neither regime produces a frictionless picture of fleet-level emissions, and practitioners should approach both datasets with calibrated skepticism.

DCS cannot distinguish operational choices from structural efficiency. A ship that switched to slow-steaming mid-year will show a lower annualized fuel total than a similar ship that maintained speed throughout, but the DCS annual aggregate cannot reveal when or why the change occurred. The EU MRV voyage records, with per-voyage fuel and distance data, allow a more granular analysis. Even MRV data can’t fully control for cargo load factor until the transport work fields are populated consistently.

Both regimes face verification quality variation. The DCS materiality threshold of ±5% in MEPC.348(78) means a discrepancy just below that level doesn’t block issuance of the SoC. The EU MRV accredited verifier applies a similar materiality concept (3% of annual fuel for the monitoring plan materiality threshold, per Regulation (EU) 2016/2072 section 1.4 of Annex II). Errors within these bands may pass undetected. Systematic under-reporting by a specific fuel type across a fleet may not surface in either system until a port-state control spot check or an EMSA technical audit cross-references BDNs against the reported totals.

The gas scope gap creates an asymmetric picture for alternative fuel ships. An LNG-fuelled vessel reporting under DCS looks favorable in CO2 terms, because LNG Cf of 2.750 is lower than HFO Cf of 3.114. But that vessel’s MRV report, which includes CH4 from 2024, shows the methane slip contribution. A charterer looking at DCS data alone will see a lower emission intensity than one looking at MRV data. The divergence is ship-specific and depends heavily on engine type: high-pressure direct-injection engines have negligible methane slip while low-pressure two-stroke Otto-cycle engines can show slip of 3 to 5 grams of CH4 per gram of fuel burned, per studies by class societies.

The scope extension to 400-4,999 GT vessels creates a new asymmetry. From 2025, small general cargo ships have MRV obligations but not DCS obligations. A shipping analyst comparing MRV public data with DCS fleet totals will find more vessels in the MRV dataset than in the DCS dataset for any given ship type. Fleet-level intensity averages computed from one dataset won’t match those from the other because the population composition differs.

CII ratings and MRV efficiency indicators use different denominators. The CII, fed by DCS data, uses fixed deadweight or gross tonnage as the denominator. The AER and similar MRV-derived indicators use actual cargo carried. A ship operating at consistently high load factors looks better on MRV-derived metrics than on CII, and vice versa for ships with variable loading. Neither metric is wrong; they measure different things. But conflating them, or assuming they should align, is a common mistake in charter negotiation and ESG reporting contexts.

The two totals will never match for world-trading ships. The DCS annual fuel total covers all international voyages globally. The MRV annual total covers only EEA-touching legs, weighted by voyage category. A ship on an Asia-Europe-Americas rotation will have a DCS total that is the entire year’s fuel consumption and an MRV total that is a fraction of that. No methodology adjustment will bring them to the same number. Operators who are asked by charterers or insurers to reconcile DCS and MRV totals need to explain that the difference is structural, not a data quality problem.

See also

• IMO Data Collection System: full legal treatment of the DCS, SEEMP Part II, Statement of Compliance, and MEPC.385(81) amendments
• EU MRV Voyage Data: the per-voyage parameters required under Regulation (EU) 2015/757 and the 2023/957 amendment
• EU MRV Regulation 2015/757: legal history, scope, and enforcement provisions
• Carbon Intensity Indicator (CII): how the CII is calculated from DCS annual data
• Annual Efficiency Ratio (AER): the MRV-derived efficiency metric using actual cargo carried
• EU ETS for Shipping: how EU MRV verified data drives allowance surrender obligations
• FuelEU Maritime: how MRV data feeds the GHG intensity compliance check
• SEEMP I, II and III: the three-part SEEMP document family including the Part II data collection plan
• MARPOL Annex VI: the parent annex covering DCS, CII, EEXI, and all air-pollution regulations
• IMO Net Zero Framework: the 2023 Revised IMO GHG Strategy and the mid-term measure negotiations