Time-based container charges: demurrage, detention (per diem), combined D&D, terminal storage, chassis per diem, reefer plug-in and monitoring, and related accessorials such as late-return fees. Weight, dimension, fuel surcharge and general freight-rate disputes are not in scope.
Both. Origin detention and export storage are handled with the same timeline logic; the responsibility mapping by Incoterm matters more on the export side and the file applies it.
Any — the agent reads documents, it does not integrate with carrier systems. Letter templates are maintained for the major ocean carriers and can be added for any carrier or terminal you deal with.
Yes for container detention at inland depots and rail ramps where the same event documents exist (gate-in/out, EIR). Rail car demurrage uses different conventions and is not currently supported.
No. It prepares the file and the letter in the carrier's format; a person reviews and sends from the portal or mail client. Nothing goes to a carrier automatically.
Both are shown on the timeline with their sources. If the contract names a primary source of record it is applied; otherwise the difference in chargeable days is stated and the desk chooses which to argue.
It is included, with a provenance note saying it is weaker than an EDI event or a signed EIR. Carriers sometimes accept them; the file does not pretend they are equal.
The file says so and recommends closing the dispute, recording the reason. Desks that only send strong disputes are taken seriously by carrier billing teams.
Yes. Upload service contracts and tariffs once; they are indexed by carrier, trade lane, container type and validity period. The clause check uses the contract that governs each booking, and quotes it.
Invoices and statements as PDF (text or scanned), XLSX/CSV portal exports; B/L and booking as PDF or EDI 301/310; events as EDI 315/322, portal exports or screenshots; EIRs as photos or PDF; correspondence as EML, MSG or pasted text.
Every line is rated against the governing contract (free time, clock start, tier, type band, calendar, exclusions). Lines where the invoiced amount exceeds the computed amount are ranked by the difference and grouped by cause. Pre-screen costs 0.1 file per line; you open full files only for the ones you choose.
Not required. Upload or forward. API access for TMS integration (shipment data in, dispute files and statuses out) is available on Enterprise.
One shipment analysed end to end: timeline, clause check, computed vs invoiced, missing-evidence list and letter draft. Up to 15 documents per shipment; each additional 10 documents is +0.5 file. Re-runs on the same shipment within 30 days — second-round letters, new evidence — are free.
As a separate meter at the provider's list price, model_access_usd on your invoice. With your own key the meter is zero.
The charge lands on your existing Google Cloud invoice and counts toward committed spend. Annual plans can be private offers. Direct invoicing from Carnegie Intelligent Technology Limited (Hong Kong) is available if Marketplace is not an option.
On Enterprise, for freight-audit firms and large 3PLs: a lower platform fee plus a share of credited amounts, reconciled against the tracker. Ask.
Yes — a monthly file cap and a model-spend cap per workspace. At the cap new work queues and the owner is notified; nothing bills past it.
The product is being built with a small number of forwarders, 3PLs and audit desks using their real invoices and contracts. You get a workspace, direct access to the team and pricing locked at today's rates for the first year. Some capabilities on this site describe designed behaviour not yet live.
Upload one carrier's contract and one month of its invoices; the pre-screen runs the same day. Most partners send their first disputes within a week.
We are onboarding a small number of design partners with real documents and real deadlines. Tell us what you work on and we will set up a workspace with your material.