10 FuelEU Maritime Pitfalls Owners are Hitting (and How to Avoid Them)

📊 Subscribe to the Ship Universe Weekly Newsletter
FuelEU Maritime is reshaping day-to-day decisions on fuel, paperwork, and port operations. Small gaps, like scope tags, OPS records, or factor versions can snowball at verification, while well-documented choices can unlock real headroom against the target. This report distills the ten pitfalls owners are running into most often, and the signals that tend to give them away.
< Click Items to Expand >
1 Monitoring Plan and verifier sign-off Priority setup
Overview
The Monitoring Plan sets how the ship measures well to wake energy and GHG intensity, what is in scope, and how data is compiled in THETIS. If it is not aligned to current Implementing Acts or lacks verifier approval, non conformities and late corrections are likely in the verification period.
Frequent issues
- Tank to wake factors used, methane slip and N2O omitted.
- Scope tagging applies 100 percent to extra EU legs instead of 50 percent.
- At berth electricity fields left blank, OPS power demand not stated.
- Bio or RFNBO claims without EU recognised chain of custody documents.
- Verifier engagement starts late and approval is not in THETIS before the year.
Actions
- Use the latest Commission template and map data sources end to end.
- Apply well to wake defaults or certified values where allowed.
- Tag scope correctly, 100 percent intra EU, 50 percent extra EU, 100 percent at berth.
- State OPS capability and maximum kW, list target ports and exemptions logic.
- Buy bio and RFNBO with EU recognised certification and keep batch documents.
- Book a recognised verifier early and have approval recorded in THETIS.
| Phase | Owner | Verifier |
|---|---|---|
| Before year | Submit plan and SOPs, attach certificates | Assess and record approval in THETIS |
| During year | Collect well to wake data and tag scope | Spot checks if needed |
| Verification period | Submit dataset, confirm pooling or banking | Verify, issue DoC, set any penalties |
2 Wrong scope percentages for intra EU, extra EU, and at berth Scope rules
Overview
Misapplied scope splits are common. Treating extra EU as 100 percent or missing at berth energy creates over or under reporting and shifts the compliance balance. The Monitoring Plan should state the tagging logic and the fields used to calculate each share.
Frequent issues
- All voyages set to 100 percent without distinguishing extra EU legs.
- At berth energy not captured or filed under auxiliary underway.
- Turnaround ports misidentified when there is a feeder or transhipment leg.
- No audit trail explaining how the 50 percent share was derived per voyage.
Actions
- Define scope tags in the SOP. Intra EU equals 100 percent. Extra EU equals 50 percent. At berth equals 100 percent for energy used alongside.
- Store port country codes, alongside timestamps, and cargo ops status so the tag can be reconstructed.
- Record shore power imports as separate metered energy. If OPS is not available, record generator load at berth.
- Create a monthly scope report that lists each voyage id, origin, destination, and percentage applied.
- Add a check that flags any extra EU voyage that is set to 100 percent.
| Voyage leg | Scope share | Notes |
|---|---|---|
| Rotterdam to Valencia | 100 percent | Both ports in EU |
| Shanghai to Hamburg | 50 percent | Extra EU leg counted at half |
| At berth in Antwerp | 100 percent | Electricity or generator energy alongside |
| Feeder Colombo to Jebel Ali, tranship to EU | 50 percent on main leg only | Document which leg is in the company scope |
3 Treating emission factors as tank to wake only Well to wake required
Overview
Tank to wake ignores upstream emissions. FuelEU requires well to wake factors that include extraction, processing, transport, and combustion. For LNG the methane slip term matters. Electricity at berth is not zero because the grid mix carries upstream emissions.
Frequent issues
- Using tank to wake CO2 only and omitting CH4 and N2O terms.
- Applying one generic LNG factor without an engine slip value.
- Treating OPS electricity as zero or copying a single grid factor for all ports.
- Claiming biofuel or RFNBO reductions without accepted certification and LCA data.
- No record of which Annex table or version the factor came from.
Actions
- Use the Commission well to wake defaults from the current Annex tables or certified values where allowed. Store the table name and version.
- For LNG record engine type and slip basis. Apply CH4 term and N2O term in addition to CO2.
- For OPS capture port country and grid factor source. Update factors when the grid baseline is revised.
- For biofuels and RFNBOs purchase with EU recognised sustainability and chain of custody certificates. Keep batch ids and delivery notes.
- Save the factor id with each fuel entry so the verifier can trace the number back to the source.
| Energy source | What to include | Field to capture |
|---|---|---|
| HFO, VLSFO, MGO | Well to wake CO2, CH4, N2O | Factor id, version, fuel qty and LHV |
| LNG | Well to wake CO2, CH4 slip, N2O | Engine type, slip source, factor id |
| Biofuel | Certified well to wake intensity | Certificate scheme, batch id, CoC reference |
| RFNBO | Certified well to wake intensity | Supplier id, certificate id, delivery note |
| Electricity at berth | Grid factor for berth location | Port country, kWh imported, factor source |
4 Fuel certification gaps for biofuels and RFNBOs Certification
Overview
Claims for low GHG intensity only count when the batch is covered by an EU recognised sustainability certificate and an accepted chain of custody model. Without matching paperwork, the fuel must use default factors and the expected reduction will not apply.
Frequent issues
- Supplier certificate is from a scheme that is not recognised for maritime use.
- Mass balance model is claimed but transfer documents do not show the balance across sites.
- Delivery note lacks a clear batch id, feedstock, or GHG intensity value.
- RFNBO claim made without renewable electricity evidence for hydrogen production.
- Book and claim used where physical delivery is required by the contract.
Actions
- Buy only from suppliers certified under EU recognised schemes and keep the scheme id and validity dates.
- Capture batch id, feedstock, production site, chain of custody model, and declared well to wake intensity on the fuel entry.
- Link the bunker delivery note to the certificate and the invoice so the batch can be traced end to end.
- For RFNBOs retain evidence of renewable electricity and electrolyser location rules where applicable.
- Run a monthly reconciliation showing opening balance, inputs, outputs, and carryover for mass balance.
- Where any document is missing, set the entry to defaults and mark the variance for the verifier.
| Document | Purpose | Who provides | Linkage field |
|---|---|---|---|
| Sustainability certificate (scheme id) | Confirms feedstock eligibility and methodology | Fuel supplier or producer | Scheme id, certificate number, expiry |
| Chain of custody statement | Shows mass balance or other accepted model | Supplier | Site ids, transfer reference |
| Batch GHG statement | Provides well to wake intensity for the batch | Supplier or verifier | Batch id, intensity value, method version |
| Bunker delivery note | Confirms physical delivery | Bunker barge | BDN number, batch id |
| Invoice | Commercial audit trail | Supplier | Invoice number, BDN number |
| RFNBO renewable electricity evidence | Shows renewable input compliance where required | RFNBO producer | Plant id, period, MWh evidence |
5 OPS (shore power) blind spot: data and hardware At berth
Overview
Many ships report at berth energy poorly and delay OPS upgrades. Without clear metering, the at berth share is wrong and the well to wake electricity factor is missing. Hardware gaps also lead to avoidable penalties when a port has OPS available but the ship cannot connect.
Frequent issues
- At berth energy captured as auxiliary underway or not captured at all.
- No field for maximum electrical load, plug standard, or voltage on the ship record.
- OPS used but kWh import not metered; grid factor not recorded for the berth location.
- Ports assumed OPS ready when berth or feeder substation is not yet commissioned.
- No written exception logic when OPS is unavailable for safety or operational reasons.
Actions
- Add at berth fields to the Monitoring Plan: maximum kW, voltage, frequency, plug standard, compatible berths.
- Meter OPS kWh at the ship side if possible and store the grid factor source with country and port.
- When OPS is not available, record generator load profile at berth so the energy is still counted correctly.
- Publish an OPS exceptions list that covers safety, weather, parallel cargo ops, and equipment faults, with timestamped evidence.
- Map target ports by OPS status and book OPS capable berths at nomination stage when possible.
- Plan retrofit windows for transformer, cable management, and control integration; include spares and crew training.
| Area | What to check | Evidence |
|---|---|---|
| Data | Separate at berth meter or reliable estimate method | kWh log, timestamped alongside window, grid factor source |
| Ship hardware | Transformer rating, cable reel, plug, protections tested | Commissioning report, test sheets |
| Port | OPS berth live, load limit fits ship demand | Port confirmation, berth id, capacity note |
| Procedures | Connection steps, crew roles, emergency disconnect | SOP reference, training record |
| Exceptions | When OPS can be skipped with reasons logged | Exception log with photos or port message |
6 Pooling and banking misuse or left too late Compliance balance
Overview
Pooling lets compliant ships cover shortfalls on others if the combined balance is positive. Banking lets you carry a surplus to the next year. Problems arise when pools are formed after data is locked, when surpluses are not banked before the Document of Compliance is issued, or when contracts do not allow pooling across ownership or management.
Frequent issues
- Pool assembled late with no time to correct a negative total.
- Banking request not filed before the DoC and the surplus is lost.
- Mixed operator pool without a clear mandate from each company.
- Pool rules not mirrored in charterparty, leading to disputes over who owns the surplus.
- No monthly forecast of balances, so deficits appear during verification.
Actions
- Run a monthly compliance forecast per ship and a consolidated pool forecast. Flag any month where the pool might turn negative.
- Create pool participation letters that authorise the administrator to allocate surpluses and settle deficits.
- Decide early which ships will bank a surplus and file the banking step before the DoC is issued.
- Align charterparty clauses so that pooling, banking, and any penalty pass through is pre agreed.
- Keep a change log for pool membership with effective dates and the balance transfers applied.
| Step | When | Owner task | Output |
|---|---|---|---|
| Pool setup | Early in year | Nominate members, appoint administrator, sign participation letters | Pool roster and rules |
| Monthly forecast | Each month | Update ship balances and the pool total | Alert if pool risks turning negative |
| Banking decision | Before DoC issue | Select ships with surplus and submit banking request | Banked amount recorded |
| Verification and settlement | Verification period | Confirm pool total, settle any penalties by due date | DoC issued, balances closed |
7 Penalty math errors from outdated rule of thumb constants Verification
Overview
Penalties are calculated from the verified compliance balance using the current year formula. Errors appear when a fixed euro per unit constant from a prior note is reused, when well to wake intensity is mixed in gCO2e per MJ and gCO2e per kWh, or when pooling and banking adjustments are not applied before computing the deficit.
Frequent issues
- Using a legacy euro per MJ constant not valid for the current year.
- Mixing units between MJ and kWh without converting with lower heating value or grid factors.
- Wrong sign on the compliance balance so a surplus is treated as a penalty.
- Not separating at berth electricity from voyage fuel when aggregating energy.
- Applying pooling after penalties instead of before, banking request filed too late.
- No record of the formula version and parameter set used for the year.
Actions
- Implement the Annex calculation flow for the current year and store the version id with the result.
- Carry units through the calculation. Convert kWh to MJ or vice versa before combining sources.
- Compute ship balances monthly, apply pooling across members, then decide banking before the Document of Compliance.
- Validate the sign: positive means surplus, negative means deficit. Add an automated sanity check.
- Lock the penalty parameter set in code for the year and require a change log for edits.
| Step | Input fields | Output |
|---|---|---|
| 1. Gather energy | Fuel MJ by type, OPS kWh at berth, voyage tags | Total energy in a single unit |
| 2. Apply intensities | Well to wake factors by source with ids | Weighted actual intensity |
| 3. Compare to target | Year target intensity and parameters | Compliance balance per ship |
| 4. Pool and bank | Member balances, pool rules, banking choices | Final pool balance |
| 5. Penalty math | Deficit amount and current formula parameters | Penalty payable in verification period |
8 Missing verification and payment timelines Deadlines
Overview
Teams slip when they treat FuelEU like a loose year end process. Data needs to be compiled, verified, and any pool or banking decisions completed inside the verification period. Payment of any penalty follows the verified result and must be settled by the due date set by the administering authority.
Frequent issues
- Late data consolidation so the verifier cannot complete checks on time.
- Pooling agreed after verification starts, leaving no time to correct a negative pool.
- Banking decisions left until after the Document of Compliance is issued.
- Penalty invoice arrives but internal approval and vendor setup delay payment.
- OPS exceptions and at berth kWh evidence missing when the verifier asks.
Actions
- Publish a compliance calendar that names owners, verifiers, and the administering authority with exact handoff dates.
- Freeze monthly datasets and run a pre verification check so open items are closed before submission.
- Confirm pool composition and file banking choices early in the verification period.
- Create a payment pack in advance with vendor details, account codes, and approvals so penalty settlement is same week.
- Track a readiness list per ship for OPS evidence, certificates, and factor references.
| Phase | Typical window | Owner task | Verifier / authority | Output |
|---|---|---|---|---|
| Year close | By 31 Dec | Lock logs, meters, and voyage tags | — | Complete dataset per ship |
| Data submission | Early verification period | Upload to THETIS, respond to clarifications | Kick off checks | Data accepted for verification |
| Pooling and banking | Early to mid verification period | Confirm members, file banking requests | Review if required | Pool total and banked amounts recorded |
| DoC issue | Before payment deadline | Address non conformities | Issue Document of Compliance | Verified result published |
| Penalty settlement | Within authority due date | Approve and pay invoice | Confirm receipt | Balance closed in period |
9 Contract clauses not FuelEU proof Commercial alignment
Overview
Many forms still ignore FuelEU terms. Without clear allocation of fuel certification duties, data rights, pooling and banking consent, OPS responsibilities, and penalty pass through, disputes arise during verification and payment.
Frequent issues
- Charterparty silent on certified bio or RFNBO requirements and chain of custody.
- No right to obtain voyage tags, meter logs, and factor references used in THETIS.
- Pooling and banking not authorised by all parties in the compliance company.
- OPS connection duties unclear and exceptions not allocated.
- Penalty and incentive formula missing or based on outdated constants.
- No change in law or reopen provision if targets or factors are revised mid term.
Actions
- Add certified fuel clause that sets scheme eligibility, batch documents, and fallback to defaults if proof is missing.
- Include a data access clause for voyage scope tags, meters, certificates, and factor ids used for well to wake accounting.
- Obtain written consent for pooling and for banking of surpluses, with who owns the balance defined.
- State OPS obligations at nominated ports, including connection standard, evidence, and reason codes for exceptions.
- Define penalty and incentive pass through tied to the verified compliance balance and the current year formula.
- Add change in law and reopen mechanics for target or factor updates and for port OPS mandates.
| Clause | What it covers | Wording cue |
|---|---|---|
| Certified fuel | Acceptable schemes, batch ids, chain of custody, fallback to defaults | Supplier shall deliver fuel with EU recognised certification and provide batch documents on request |
| Data access | Voyage tags, kWh at berth, meter and factor references | Owner shall provide data used for FuelEU accounting and keep records for audit |
| Pooling consent | Authority to include ships in a pool and to allocate balances | Parties consent to pooling and appoint the administrator to allocate balances |
| Banking consent | Right to carry surplus to next year and who owns it | Surplus may be banked by the compliance company and remains its property |
| OPS responsibility | Connection duties, standards, evidence, and exceptions | At nominated ports the vessel shall connect to OPS where available or log an exception with reason code |
| Penalty pass through | Allocation of verified deficits and timing of payment | Any verified deficit attributable to the charterer’s acts shall be reimbursed within the verification period |
| Incentive sharing | Split of verified surplus or KPI credits | Verified surplus or credits shall be shared as per schedule X |
| Change in law | Mid term regulatory or factor changes | Either party may reopen to adjust for material FuelEU changes |
| Audit and cooperation | Right to review records and cooperate with verifiers | Parties shall cooperate with the verifier and allow reasonable audit access |
| Dispute and escrow | Payment while disputing | If disputed, amounts may be placed in escrow pending resolution |
10 Overlooking tech adjusters that reduce GHG intensity Optimisers
Overview
FuelEU calculates well to wake GHG intensity per unit of energy used. Some technologies affect the intensity term or the share of lower intensity energy. Common wins are the wind assist factor where installed and proven, higher use of shore electricity at berth with a documented grid mix, and verified reductions in methane slip on LNG engines.
Frequent issues
- Wind assist installed but no data trail to claim the factor in the Monitoring Plan.
- OPS capability present but at berth energy not metered, so shore share does not shift the average.
- LNG engine type and slip basis not recorded, default factors used instead of improved settings.
- Bio or RFNBO blends used operationally without certified batch values, so defaults apply.
- Battery or shaft generator changes logged as efficiency only and not tied to intensity inputs where relevant.
Actions
- Add wind assist to the Monitoring Plan with the required evidence package and apply the recognised factor where eligible.
- Increase OPS connection rate and meter kWh at berth. Store location so the correct grid factor is applied.
- For LNG record engine model and slip calibration or retrofit status and use the matching CH4 and N2O terms.
- Use certified bio or RFNBO for blends and log batch ids and chain of custody so the lower intensity is accepted.
- Where hybrid systems shift energy to electricity, capture the kWh and the factor source that applies to that energy.
| Adjuster | How it reduces intensity | Evidence to capture |
|---|---|---|
| Wind assist (sails, rotors, kites) | Applies an approved factor to lower effective GHG per MJ | Install documentation, operations data, Monitoring Plan entry, factor reference |
| OPS electricity at berth | Replaces onboard generation with grid factor for kWh imported | kWh meter logs, berth location, grid factor source, exception notes |
| LNG slip reduction | Lower CH4 term in the well to wake factor for the engine | Engine type, slip source or calibration proof, factor id and version |
| Certified biofuel or RFNBO blend | Uses batch well to wake intensity lower than fossil default | Scheme id, batch id, chain of custody, delivery notes |
| Battery and shaft generator integration | Shifts part of hotel or propulsion load to electricity with documented factor | kWh logs, charging source, factor source, system description in plan |
FuelEU Maritime isn’t about last-minute heroics; it’s about steady, visible structure. With a verified Monitoring Plan in place, clear scope tagging, well-to-wake factors backed by evidence, and OPS data that’s easy to audit, the compliance picture can start to feel predictable. Pooling and banking can become calendar items rather than fire drills, and contracts can reflect how the work really runs. Many owners find that a light monthly review and a small “evidence pack” per ship keeps surprises out of the verification window and confidence high.
We welcome your feedback, suggestions, corrections, and ideas for enhancements. Please click here to get in touch.