Audit Trail

Opened from Audit Trail in the GoRate menu. Give it a record that is in OTM today and it answers with the upload that put it there, who approved that upload and the file it came from. Download evidence produces the same answer as a spreadsheet.

Nothing on this screen is copied into GoRate's database. The record is read from OTM at the moment you search; GoRate holds only the chain of custody and the source file.

OTM domain

The domain the records live in, at the top right of the search panel.

This is not your platform domain. It is the domain the rate template writes to, so it is the same value you would see on the template. Leave it blank to search every domain your OTM user can see.

Only the two searches that read OTM use it — OTM Record ID and Origin / Destination. Publication Period reads GoRate's own records and ignores it.

The value is remembered between visits.

Records

The record type decides which OTM table is read and how the upload behind a record is established.

Records	Read from	Traced by
Rates	Rate geo	The upload id stamped on each rate in OTM
Capacity limits	Capacity limit	The upload that was loading into OTM when OTM wrote the record
Commitments	Capacity commitment	The upload that was loading into OTM when OTM wrote the record
Allocations	Capacity commitment allocation	The upload that was loading into OTM when OTM wrote the record

Rates are exact: GoRate writes a GORATE_UPLOAD_ID reference on every rate it loads, so the upload is read straight off the record.

The other three tables have no reference field in OTM, so the match is made from time. GoRate records when each upload's load into OTM starts and finishes; a record whose insert time falls inside that window belongs to that upload. Only one upload per project loads at a time, so the windows do not overlap. If two uploads could still have written a record the answer says so rather than guessing, and the record ids let you confirm which one it was.

A capacity limit, commitment or allocation can only be traced from the environment that loaded it - GoRate's load record lives there, not in OTM.

Every search is limited to records loaded by the integration user (RATE_UPLOAD_INTEGRATION). Records somebody typed into OTM by hand, or that another system loaded, are not GoRate's and do not appear.

The three searches

OTM Record ID

Paste the ids, one per line or comma separated, or switch to List to add them one at a time. Each id is read live from OTM.

Use this when you have a record in front of you — from an OTM screen, a carrier query, a client question — and need to know where it came from.

Origin / Destination

Finds records by lane rather than by id: a geo type and value at each end, an effective date range and, optionally, a carrier SCAC.

Either endpoint may be left blank. The value is matched against whichever lane column the geo type fills, so a CITY lane, a USZIP3 lane and a ZONE2 lane all resolve.

Use this when the question is about a lane rather than a specific record — "what did we send this carrier for Chicago to Dallas in January".

Publication Period

Answers with files rather than records: every upload published in a date range, optionally narrowed to one template.

This one reads GoRate's own records, not OTM, so it works even when OTM is unreachable and it does not use the OTM domain.

Use it for the periodic evidence pack — everything published in a quarter, with its approvals.

Reading a result

Exceptions only hides the rows whose chain is clean, leaving the ones worth looking at.

Click a row to open the detail panel:

• In OTM today — the record as OTM holds it right now, read at the moment you asked.
• Chain of custody — the upload, its validation result, its approvals and the push, in order with times and names.
• Source file — the file as it was uploaded, still stored.

Download evidence

Produces a spreadsheet of whatever the search returned, with the chain of custody for each row. This is the artefact to hand to an auditor or a client; it is generated from the same reads the screen shows, at the time you press it.

When the search fails

A Publication Period search reads GoRate's own records. A failure there is on our side — the backend log has the detail.

The other two read OTM directly, so they need:

• an OTM adapter on the project (see GoRate Setting), and
• the GORATE_UPLOAD_ID refnum qualifier to exist in OTM, for rate searches.

See Troubleshooting.