Documents & inboxAutomated detention and demurrage recovery for INTTRA
Booking and shipping instruction records from INTTRA for export D&D disputes
- Sync
- Daily, or event-driven where messages are copied to ATAHSKIA
- Authentication
- Report export or message copy authorized by your INTTRA administrator
- Data exchanged
- Bookings and confirmations · Booking amendments · Shipping instructions and VGM · Track and trace events
How it connects
INTTRA is an ocean shipping network that shippers and forwarders use to submit bookings, shipping instructions and VGM declarations to many carriers through one interface, and to receive booking confirmations and track containers.
ATAHSKIA reads booking requests, carrier confirmations, amendments and shipping instruction records for your exports. Those records establish the vessel and cutoff the export was booked against, any later changes, and the earliest return date the carrier gave. § 541.6(b) requires an export D&D invoice to state the earliest return date, so the booking history is what lets the audit test it.
Export disputes often turn on rolled bookings. When a booking is moved to a later vessel and the receiving window shifts, storage or detention billed for days the terminal would not accept the full container is a prime target under the incentive principle in 46 CFR § 545.5.
Data flows
Bookings and confirmations
Reads
Booking number, carrier, vessel, voyage, port of loading, cutoffs and confirmation dates.
Booking amendments
Reads
Vessel changes, rolled bookings and revised cutoffs, with time stamps.
Shipping instructions and VGM
Reads
Submission times and container references.
Track and trace events
Reads
Container events for the export leg where available.
Field mapping
| ATAHSKIA | INTTRA | Note |
|---|---|---|
| Booking number | Carrier booking number | |
| Bill of lading number | B/L number from shipping instructions | |
| Container number | Container on the booking or SI | |
| Port of loading | Port of load on the booking | |
| Vessel and voyage | Vessel and voyage on the confirmation | |
| Rolled booking | Booking amendment with changed vessel or voyage | |
| Earliest return date | Receiving date information from the carrier, where provided | Often comes from the terminal; we record the source. |
| Cutoff | Cargo and documentation cutoffs on the confirmation |
Setup
Agree the export method
Your INTTRA administrator chooses how booking and SI records are shared: a report export or a copy of the messages your systems already receive.
Scope the bookings
Choose the ports of loading, carriers and business units to include.
Map booking to invoice
ATAHSKIA matches export D&D invoices to bookings by booking number, B/L and container.
Load history
Backfill 12 months of bookings and amendments so past rolls can be tested against invoices still inside the dispute window.
What it recovers
Rolled booking, billed anyway
The carrier rolled the booking twice. Storage billed while the terminal would not receive the container for the new vessel is disputed with the amendment history attached.
Missing earliest return date
An export detention invoice omits the earliest return date required by § 541.6(b). The packet cites the missing element.
Export free time start
The booking confirmation and empty release dates test when export free time should have started.
INTTRA integration FAQ
Is this only for exporters?
Mostly. INTTRA data is most useful for export detention and storage. Import disputes rely on carrier, terminal and tracking data.
Do you submit bookings through INTTRA?
No. The connection is read-only.
Is ATAHSKIA an INTTRA partner?
No formal partnership is claimed.
Related connectors
Don't let your 30-day dispute window expire.
Send your recent D&D invoices for a free audit. We report what is recoverable within 48 hours.