Automated detention and demurrage recovery for PortPro
PortPro dispatch records as proof of pickup, return and failed attempts
- Sync
- Every 15 minutes
- Authentication
- Credentials issued by your PortPro administrator, stored encrypted with AES-256
- Data exchanged
- Loads and containers · Driver events · Appointments · Dispute status
How it connects
PortPro is a transportation management system built for drayage carriers. It covers delivery order intake, load creation, dispatch, a driver app with GPS tracking, customer status updates and billing, with last free day alerts and appointment-aware dispatch planning.
ATAHSKIA reads loads, container moves, driver event time stamps and appointment details from PortPro. For a drayage carrier, that history is the evidence file: when the driver arrived at the terminal, whether the pickup or empty return was refused, which return location the carrier designated and when the empty was dropped. Each detention, demurrage or per diem invoice tied to those containers is checked against the 20 elements of 46 CFR § 541.6 and against the move history.
Drayage carriers often receive bills they did not cause and cannot control. § 541.6(a)(4) requires every D&D invoice to state the basis for why the billed party is the proper party, and the invoice must certify that the billing party's own performance did not cause the charges. Move records from PortPro are what make those elements testable.
Data flows
Loads and containers
Reads
Container number, customer, B/L or booking reference, terminal, last free day and return location.
Driver events
Reads
Arrival, pickup, drop, empty return and failed attempt time stamps from the driver app and GPS.
Appointments
Reads
Pickup and return appointment times recorded on the load.
Dispute status
Writes
Optional notes on the load showing audit outcome and open disputes.
Field mapping
| ATAHSKIA | PortPro | Note |
|---|---|---|
| Container number | Container on the load | |
| Bill of lading number | B/L or booking reference on the load | |
| Discharge terminal | Pickup location (terminal) | |
| Last free day (as reported) | Last free day on the load | |
| Gate-out full date | Pickup completed event | |
| Empty return date | Empty return completed event | |
| Failed attempts | Driver event notes and status changes for refused or turned-away moves | Mapped during onboarding to your status conventions. |
| Appointment time | Appointment on the move |
Setup
Authorize access
Your PortPro administrator authorizes access to loads and driver events through the interfaces available on your account, or schedules an export.
Map your statuses
Tell us which statuses and notes your dispatchers use for terminal refusals, closed gates and empty return refusals.
Load the per diem bills
Forward per diem and detention invoices to your audit inbox. Each is matched to the container's moves.
Share packets with customers
Choose whether audit packets go to the BCO or forwarder whose box it was, so they can dispute charges billed to them.
What it recovers
Empty refused at the designated depot
The driver's GPS and status show the empty was turned away at the return location the carrier designated. The per diem dispute cites the refusal under the § 545.5 incentive principle.
Wrong billed party
A detention invoice reaches the trucker with no stated basis for why the trucker is the proper party. The packet cites the missing § 541.6(a)(4) element.
Prove the return time
The empty return event is time stamped by the driver app, so days billed after it are listed and disputed.
PortPro integration FAQ
Is this for drayage carriers or importers?
Both. Dray carriers use it to dispute bills sent to them; importers whose truckers run PortPro can use the move history in their own disputes.
Does ATAHSKIA change loads in PortPro?
Only if you enable dispute notes. Dispatch data is never altered.
Is ATAHSKIA a PortPro partner?
No formal partnership is claimed.
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.