How to export your Trips file from Amazon Relay
The trips history export is one half of a reconciliation. It is the carrier's own record of what was dispatched and what happened to it — the record you check the invoice against.
The Relay portal's menu labels change from time to time. The steps below describe where the export lives as of this writing; if a label has moved, look for a trips or tours history view with a date-range picker and a download or export control.
Pulling the file
- Sign in to the Relay portal as a user with visibility of the whole fleet. A driver-scoped login exports only that driver's work, which will make loads look missing that are not.
- Open the trips (tours) history view.
- Set the date range to the work period you are reconciling — Sunday through Saturday. Relay's pay week runs Sunday 00:00 to Saturday 23:59.
- Export to CSV and save it somewhere you can find it. There is no need to open or clean it first.
What comes out
The export is a UTF-8 CSV with a byte-order mark and roughly sixty columns. It
carries one row per load, not per trip. A multi-load tour therefore appears
as several rows sharing a single Trip ID.
LoadRecon reads these columns:
| Column | What it is used for |
|---|---|
Load ID |
The primary matching key against the invoice. |
Trip ID |
Groups loads into a tour. Sometimes carries a T- prefix, sometimes not — the tool strips it before matching. |
Trip Stage |
Completed, Canceled, or Rejected. |
Load Execution Status |
Completed, Cancelled, or Not Started. |
Facility Sequence |
The lane, e.g. SLC1->DEN8. |
Driver Name |
Display and filtering only. |
Estimated Cost |
Compared against actual pay to flag rate variance. |
Stop N arrival dates and times |
Used to work out when a load actually finished, which decides whether an unpaid load is a likely rollover or something to dispute. |
Everything else is carried through for display but plays no part in matching.
Two things that surprise people
The two status columns disagree, and that is normal. A trip can be
Completed while one of its loads is Cancelled — that is a load dropped
mid-tour, and it is a perfectly ordinary combination. Rejected trips pair with
Not Started loads. LoadRecon reads the load-level status for classification
and keeps the trip stage for context.
The date range is not a hard boundary. A file pulled for one week regularly contains loads dated outside it, because tours that straddle the boundary appear in full. LoadRecon deliberately does not filter by date — it reconciles every row present and lets the ID matching sort out which invoice a load belongs to.
A note on Estimated Cost
On multi-load tours, Estimated Cost reflects the load's own accessorials, not
a share of the tour's base rate. A load on a tour paying $4,235 in base rate may
show an estimate of $0.65, which is its fuel surcharge. This is worth knowing
before you read too much into that column: the tour base pay is real money, it
is simply recorded at the trip level rather than split across loads. LoadRecon
handles this by showing tour rows alongside load rows and subtotalling each
trip, so the totals tie to the invoice.