Every year, a fuel record that began as a noon report or a bunker delivery note has to survive a verifier's review and come out as a Statement of Compliance. When it works, the SoC arrives by the end of May and nobody notices. When it does not, a missing IMO number or a split voyage delays the certificate and takes up the compliance team's spring. This guide explains what the verifier looks at, how to handle gaps and corrections, and how to keep the process calm.

Pass IMO DCS Verification the First Time and Get the SoC on Board
What verifiers expect, how to handle data gaps and corrections, and the reporting errors that delay the Statement of Compliance.
Free trial available. Or book a walkthrough built around your own DCS reporting calendar.
5,000 GT
Ships generally covered
In international shipping, per DNV and Lloyd's Register.
31 March
Data to the verifier
For the previous calendar year, per the Bahamas notice and DNV.
31 May
Statement of Compliance issued
Five months after the start of the year (Reg. 6.6).
12 months
Source documents kept
After the calendar year ends, per the Bahamas notice.

The DCS Calendar: From the Reporting Year to the Statement of Compliance

Which dates drive the work: data to the verifier, the SoC and the upload to IMO

DNV gives the DCS schedule as the fuel oil consumption report within three months after the end of each calendar year, which the FAQ lists as 31 March for submission to the verifier, and the SoC five months after the beginning of the calendar year, which it lists as 31 May. The Bahamas Maritime Authority notice adds that verified data is uploaded to IMO's database within one month after the SoC and not later than 30 June. Other flags may set different dates.

The DCS Year: From the Reporting Year to the Statement of Compliance and Beyond
DATA TO VERIFIER BY 31 MARCH
SoC BY 31 MAY
GISIS BY 30 JUN
JANFEBMARAPRMAYJUN
Reporting year ends 31 December. This calendar covers the following year, January to June. The SoC stays valid until the end of May of the year after issue (Bahamas notice).
Dates from the Bahamas Maritime Authority notice (data and attained CII by 31 March, SoC by 31 May, GISIS upload within one month of the SoC and not later than 30 June) and DNV's FAQ. The drawing is ours and the day positions are approximate.

How many days each stage really gives you, and why the first stage is the one to protect

Counting from 1 January, the window to assemble and submit data is about 90 days. The verifier then has about 61 days to the SoC date, and the upload another 30. The first stage is the one the company controls, and it is the one most affected by data quality. LR says early submission gives the verifier time to find errors, and warns that late or incomplete submissions may need resubmission and extra verification. Our IMO Data Collection System guide to fuel consumption reporting requirements gives the background to the reporting rules.

Days Available at Each Stage of the DCS Reporting Window (Our Arithmetic From the Reported Dates, Non-Leap Year)
1 January to 31 March: assemble and submit the data

90 days
31 March to 31 May: verification and SoC issue

61 days
31 May to 30 June: upload verified data to GISIS

30 days
Calculated from the dates in the Bahamas Maritime Authority notice. The notice says GISIS upload is within one month after the SoC and not later than 30 June. Your flag state may set its own dates.

How a Fuel Record Becomes a Statement of Compliance

The five steps from the ship's log abstract to the certificate on board

Ships report voyage data and bunker reports, and the company builds the annual report using the ship's SEEMP Part II method. The verifier reviews it and, once it is satisfied the data was collected and reported correctly, issues the SoC. DNV says verification is generally done in its offices rather than by a surveyor on board. LR says submissions need supporting evidence for verification under MEPC.348(78).

How a Fuel Record Becomes a Statement of Compliance
1
Ship records
Log abstracts and bunker reports through the year.
2
Company reports
Annual fuel oil consumption report built under the SEEMP Part II method.
3
Verifier checks
Consistency and accuracy against the evidence, mostly from an office, not on board.
4
SoC issued
Verifier issues the Statement of Compliance once data is confirmed correct.
5
Reported on
Verified data goes to the flag and to IMO's database.
Sources: DNV FAQ on IMO DCS, Lloyd's Register class news 05/2023 and the Bahamas notice. The Bahamas notice says the verifier issues the SoC once it confirms the data was collected and reported correctly under MEPC.348(78). Some flags issue the confirmation themselves.
Keep the DCS Evidence Ready Before the Deadline
Track log abstracts, bunker delivery notes, SEEMP documents and the Statement of Compliance for every ship, with alerts before each date.
Free trial available. Or book a walkthrough built around your own DCS reporting calendar.

What the Verifier Expects: The Points That Delay or Speed the Statement

Which data points in a fuel report most often raise questions, and how to prepare for each

DNV's FAQ does not give a list of common errors, but it flags specific points that matter. Voyages crossing the year end must be split, bunker reports must show the receiving vessel's IMO number, ice class belongs in the report and in SEEMP Part II, fuel type should follow the ISO 8217 grade, and any distance travelled should be reported. The table adds the SEEMP condition and the evidence pack.

What a DCS verifier will look at, and why each point can delay the Statement of Compliance
Point checkedWhy it mattersHow to be ready
SEEMP Part II confirmedDNV says FOC reports cannot be verified without a SEEMP Part IIKeep the confirmation of compliance on board and in the file
Year-end voyagesVoyages crossing the year end must be split with a log abstract event at the year end (DNV)Add the split event before the report is built
Bunker report identifiersThe bunker report must show the IMO number of the receiving vessel (DNV)Check every bunker delivery note before filing
Fuel type and gradeDNV says fuel type should follow the ISO 8217:2024 gradeUse the grade on the delivery note, not an abbreviation
Distance travelledAny distance travelled should be reported, including small dynamic positioning distances (DNV)Include manoeuvring and DP distance in the log abstract
Time at sea definitionDNV defines it as departure from berth to arrival at berth, excluding anchorageApply one definition across the whole fleet
Ice classIce class belongs in the FOC report and SEEMP Part II (DNV)Check it matches class records
Supporting evidenceLR says submissions need supporting evidence for verification under MEPC.348(78)Assemble the evidence pack before the deadline
Sources: DNV FAQ on IMO DCS (class society) and Lloyd's Register class news 05/2023. The right-hand column is our suggestion.

Why a missing SEEMP Part II blocks verification however clean the fuel data is

DNV says FOC reports cannot be verified without a SEEMP Part II, under MARPOL regulations 22.2 and 22A.1, and that the SEEMP II is confirmed by the flag or a recognised organisation, which issues a confirmation of compliance. On a change of flag or company, a new SEEMP II and confirmation are needed. Check the document is on board and current before the data work starts, not after.

Data Gaps and Corrections: Handling What Is Missing or Wrong

What the sources say to do when a log abstract or bunker report is missing

The honest answer is that sources differ. We did not find a general IMO rule that tells a ship how to treat a data gap. What we found is practical: rebuild from source documents where you can, submit early, and ask the verifier and flag how they want gaps explained. One flag, the Bahamas, describes a route for a company that cannot complete submission or review on time.

When the Data Has a Gap: Three Routes and Their Limits
1. FILL IT FROM SOURCE
Rebuild missing entries from disaggregated source documents such as noon reports, bunker delivery notes and engine logs. These must be kept for at least 12 months after the year ends (Bahamas notice).
2. SUBMIT EARLY AND EXPLAIN
LR says early submission gives the verifier time to find errors, and that incomplete or late submissions may need resubmission and extra verification.
3. IF THE DEADLINE CANNOT BE MET
The Bahamas notice says the company requests a conditionally issued short-term IEE Certificate through the class society, assessed case by case. This is one flag's route: check yours.
Sources: Bahamas Maritime Authority notice (2022), Lloyd's Register class news 05/2023. The Bahamas notice says IMO had not issued detailed guidance on end-of-year reporting with only partial fuel data when it was written. We did not find a general IMO rule on how a data gap is treated: ask your verifier and flag.

How corrections, changes of company and changes of flag change who reports what

DNV describes a correction route in its own system: notify the verifier, update the log abstracts and resubmit. For changes of company or flag, DNV says each manager reports its own part of the year and each flag period is verified. The table sets out the main cases.

Correcting reported data and handling changes of company or flag
SituationWhat the sources saySource
Error found after the report is submittedNotify the verifier, update the log abstracts and resubmit. The verifier sets the report to unsubmitted and the data refreshes.DNV FAQ (DNV's own system)
Change of companyEach manager reports and submits the FOC report for its own part of the year (Reg. 22A.5)DNV FAQ
Change of flagA flag change triggers FOC verification for each flag period (Reg. 22A.4). A new SEEMP Part II and confirmation of compliance are needed.DNV FAQ
Previous company does not provide the SoCConsequences depend on the flag, because the regulation does not specify themDNV FAQ
Lay-up or inactivityKeep the last SoC on board for inspectionBahamas notice
Expired SoCNeed not be kept once a new one is delivered on boardBahamas notice
Sources: DNV FAQ (its own process and its reading of the regulations) and the Bahamas Maritime Authority notice. Other verifiers and flags may differ.

The DCS Readiness Checklist: From the Ship to the Certificate

A checklist with a checkpoint type on each item that works for ships and for the office

Use the checklist below as a monthly routine and as a final check before submission. It is built from the sources above, so adapt it to your verifier's instructions. For how DCS connects to energy efficiency compliance more widely, see our EEXI compliance guide to the energy efficiency existing ship index.

DCS verification readiness checklist, with a checkpoint type on every item (our suggested template)
ItemWhat to checkCheckpoint type
SEEMP Part II and confirmationOn board and currentRecord
Log abstracts for the yearNo missing days, year-end voyage splitVisual
Bunker delivery notesAll present, IMO number and fuel grade correctRecord
Fuel quantitiesOpening, bunkered and closing quantities reconcile for each tank groupMeasure
Distance and hoursDistance includes DP and manoeuvring, time at sea uses one definitionMeasure
Data submittedBefore the verifier's deadline, with evidence attachedRecord
SoC on boardIssued and on board, with the date and validity notedRecord
Source documentsKept for at least 12 months after the year endRecord
Our suggested template. Checkpoint types: Visual, Measure and Record.

Mistakes That Delay the Statement of Compliance

Six habits that turn an easy verification into a spring-long project

1
Starting to assemble data in March
The window from 1 January to 31 March is about 90 days. Most of the work should already be in the ship's monthly routine.
2
Ignoring small distances
DNV says any distance travelled, even small dynamic positioning distances, should be reported.
3
Missing IMO number on bunker reports
DNV says the bunker report must show the receiving vessel's IMO number. A missing number triggers questions.
4
Inconsistent time-at-sea definitions
Different ships using different definitions makes fleet reports hard to verify.
5
Late discovery of a SEEMP gap
FOC reports cannot be verified without a SEEMP Part II, so a gap blocks the SoC.
6
Not keeping source documents
The Bahamas notice says disaggregated source documents are kept for at least 12 months after the calendar year ends.

Systems That Keep Fuel Records, SEEMP Documents and the SoC in One Place

How a dated photo repository, task ownership and deadlines keep DCS evidence together

DCS is a year-long records exercise with a short, hard deadline. Marine Inspection supports a dated photo repository, observations turned into tasks with owners, deadlines and evidence, and certificate and equipment tracking. A dated photo of a bunker delivery note or a flow meter reading, attached to the voyage record, makes the evidence pack quick to assemble in March.

Frequently Asked Questions About IMO DCS Verification and the Statement of Compliance

What is the IMO DCS Statement of Compliance?

A certificate issued by the verifier once the ship's annual fuel oil consumption data is confirmed as collected and reported correctly. The Bahamas notice says it is valid through the calendar year of issue and the first five months of the next year.

When must DCS data be submitted and the SoC issued?

The Bahamas notice and DNV give 31 March for the data to reach the verifier and 31 May for the SoC. MARPOL Annex VI Regulation 6.6 gives five months after the beginning of the calendar year for the SoC, as quoted by DNV.

Which ships need to report?

DNV and Lloyd's Register describe ships of 5,000 GT and above in international shipping. DNV adds that platforms are excluded and windfarm installation jack-ups are covered.

Who verifies the data?

A verifier acting for the flag, such as a recognised organisation. DNV says verification is done in its offices, not by a surveyor on board. Some flags, such as Liberia and Germany according to DNV, issue the confirmation of compliance themselves.

What if we find an error after submission?

DNV says to notify the verifier, update the log abstracts and resubmit, and the verifier will set the report to unsubmitted. Process details vary by verifier.

What if the data has gaps and we cannot finish on time?

The Bahamas notice says the company requests a conditionally issued short-term IEE Certificate through the class society. That is one flag's rule. We did not find a general IMO rule for gaps, so check with your verifier and flag.

How long must the source documents be kept?

The Bahamas notice says disaggregated source documents are kept on board or with the company for at least 12 months after the calendar year ends, and provided to the flag or class on request.
Make the Statement of Compliance an Annual Non-Event
Fuel records, SEEMP documents, verification dates and certificates for the whole fleet, in one system your compliance team can use.
Free trial available. Or book a walkthrough built around your own DCS reporting calendar.