05.07.2014 Views

Changes to Sea Cargo Reporting

Changes to Sea Cargo Reporting

Changes to Sea Cargo Reporting

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Scenario 1<br />

The freight forwarder reports their HBOL cargo report <strong>to</strong> the ICS before the shipping company reports their OBOL cargo report <strong>to</strong><br />

the ICS. There are no Cus<strong>to</strong>ms or AQIS interventions.<br />

Description of Business Scenario<br />

• Freight forwarder reports a House Bill of Lading (HBOL) for an<br />

FCL container <strong>to</strong> the ICS using an OBOL number different <strong>to</strong><br />

that issued by the shipping company<br />

.<br />

• Shipping company reports the OBOL sea cargo report <strong>to</strong> the<br />

ICS using their OBOL number<br />

• There is no underbond move as the container is delivered<br />

form the wharf<br />

When the ocean bill number reported in the freight forwarder cargo report<br />

does not match with the ocean bill number reported in the shipping<br />

company ocean bill.<br />

The current system behaviour and<br />

result is:<br />

• The shipping company OBOL<br />

sea cargo report is rejected,<br />

because it is identified as a<br />

duplicate of the freight forwarder<br />

HBOL sea cargo report by the<br />

ICS;<br />

• The freight forwarder must<br />

withdraw and resubmit their sea<br />

cargo report with the correct<br />

OBOL number;<br />

• The shipping company must<br />

resubmit their sea cargo report<br />

The changed system behaviour and<br />

result is:<br />

• The freight forwarder HBOL sea<br />

cargo report is accepted by the<br />

ICS;<br />

• The shipping sompany OBOL<br />

sea cargo report is accepted by<br />

the ICS, and the derived OBOL<br />

for the freight forwarder HBOL<br />

sea cargo report is updated

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!