Frequently asked questions

Are my files uploaded anywhere?

No. Both files are read by JavaScript running in your own browser, compared there, and discarded when you close the tab. There is no server to upload to — the site is static files on a CDN. You can confirm this yourself: open your browser's developer tools, switch to the Network tab, and run a reconciliation. No request carries your data. The tool document is served with a policy (connect-src 'none') that blocks fetches, XHR, WebSockets, EventSource, and beacon connections.

Ads on this page are served by Google in the surrounding page, which is a separate document from the tool. See the privacy policy for the detail, including what the ad cookies do.

Do I need an account?

No. There is no sign-in, nothing is saved between visits, and no history is kept. Reload the page and the tool is empty again.

Which files do I need?

The trips history export (CSV) and the payment file (XLSX or CSV) for the same work period. Guides: trips export · invoice download.

You can drop them in either box — the tool works out which is which from the columns inside and swaps them if needed.

Can I use just one file?

Partly. With only the trips file you get a status breakdown of your week; with only the payment file you get the invoice summary. Reconciliation needs both, since the whole point is the comparison.

Why does it say loads are "completed, not paid" when I was paid?

Almost always the pay cycle. Relay's work period ends Saturday 23:59, and loads finishing near or after that cutoff are invoiced the following week. LoadRecon labels those likely rollover rather than treating them as missing. Loads labelled review — payment missing are the ones that finished well inside the week, where a rollover does not explain the absence.

The only way to confirm a rollover is to check next week's invoice, which is why the tool calls it a heuristic rather than a verdict.

The totals on screen don't match my invoice. Why?

They should match exactly, and LoadRecon warns you on screen if they do not. If you are comparing against your own spreadsheet instead, the usual cause is tour rows: on multi-load tours the base pay sits on a TOUR row with no Load ID, and a per-load view drops it. In the sample invoice this tool was built against, tour rows were 39% of the total.

Does it tell me whether I'm owed a TONU?

No, and no tool working from these files can. The exports do not record who cancelled a load. LoadRecon shows you which cancelled loads were compensated and which were not; deciding whether an uncompensated cancellation should have been paid is a judgement about the circumstances, which only you have.

How long do I have to dispute?

Disputes go through the Relay portal within 30 days of the invoice date. LoadRecon shows the deadline in the invoice strip when the payment file includes an invoice date. Verify it against the portal before relying on it.

What does the variance flag mean?

A paid load whose gross pay differs from the estimate on the trips export by more than 10%. Treat it as a prompt to look, not a conclusion. On very small amounts the percentage test is noisy, and on multi-load tours it compares accessorials rather than base rates — see the categories guide for why.

My export has different column names.

Relay changes its export format occasionally. If a required column is missing, the tool shows a mapping panel listing the headers it did find, and you point it at the right ones. It will not simply fail.

How big a file can it handle?

Files with a few thousand rows are comfortable. Everything runs in your browser, so very large multi-month exports are limited by your own machine rather than by a server. Results are paginated.

Is this affiliated with Amazon?

No. LoadRecon is an independent tool with no connection to Amazon or Amazon Relay. It reads files you already have. Always verify anything you plan to act on against the Relay portal — see the terms.