Skip to content
ATAHSKIA

Comparison

Disputing in carrier portals vs ATAHSKIA

Most ocean carriers and many terminals offer billing portals where you can view D&D invoices and submit disputes. They are the official channel, they show the billing party's own data, and for a shipper working with one or two carriers they can be enough.

With more carriers, each portal has its own login, dispute form, evidence limits and status tracking. And a portal shows the billing party's view of events, which is the view you may be disputing. This page compares portal-by-portal disputing with running one audit and evidence process across all of them.

DimensionCarrier portal disputesATAHSKIA
Audit depth
Invoice checksNone; the portal presents the invoice as issued.All 20 § 541.6 elements and § 541.7 timing checked independently.
Cross-carrier viewOne carrier or terminal per portal.Every carrier and MTO in one queue.
Evidence
Source of eventsThe billing party's own records.Independent sources: carrier EDI, terminals, tracking APIs, appointment and dispatch records.
AttachmentsLimited by each portal's upload rules.Complete evidence packet generated once, usable in any portal or by email.
Disputes
Dispute contentFree-text fields and reason codes chosen by the carrier.Packets citing exact CFR subsections, which you can paste or attach in the portal.
Deadline trackingStatus shown per portal, if at all.§ 541.8 windows and 30-day resolution deadlines tracked across all billing parties.
EscalationEnds at the carrier's decision.Unresolved disputes can become § 41310 dossiers for the billed party to submit.
Operations
Logins and workflowsOne per carrier and terminal.One workflow; submission still goes through each billing party's required channel.
ReportingPer portal, in each carrier's format.Billed, disputed and recovered across carriers, plus carrier scorecards.
Commercials
CostFree to use.Platform fee plus success fee, with a break-even guarantee.

Portals are the channel, not the audit

§ 541.6 requires each invoice to include contact information and a URL, QR code or digital watermark pointing to a page that explains what a relief request must contain. Many billing parties meet that with a portal, and ATAHSKIA respects it: disputes go through whatever channel the billing party designates.

What a portal cannot do is tell you the invoice is defective. That check has to happen before you open the dispute form.

Independent evidence

If the carrier's system shows a container available on day one and your trucker's appointment history shows no slots for three days, the portal will show the first fact and not the second. ATAHSKIA brings the second fact into the packet, along with the terminal's hold history and the time stamped outgate.

One scorecard across billing parties

Because every dispute and response runs through one system, you can compare carriers and terminals on invoice compliance, dispute acceptance and response time in your own book, which is useful evidence at contract time and impossible to assemble from separate portals.

When carrier portal disputes is enough

If you ship with one or two carriers, receive few D&D invoices, and those carriers' portals handle disputes quickly and fairly, using the portals directly is sensible and costs nothing. ATAHSKIA adds most value once several billing parties, terminals and dispute deadlines are in play at once.

FAQ

Do we still have to use carrier portals?

Where a billing party designates a portal for relief requests, yes. ATAHSKIA prepares the content and evidence; you submit through the required channel.

Can ATAHSKIA log into carrier portals for us?

We do not store or use your carrier portal passwords. Your team submits, and the dispute status is recorded back in ATAHSKIA.

Will carriers accept a packet with CFR citations?

Billing parties must resolve relief requests within 30 days under § 541.8. A precise, cited packet makes the request easy to evaluate, whatever the outcome.

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.