AuditRes
Revenue Recovery Intelligence
One AuditRes platform

Freight · Accessorial events

Detention allowance per stop versus per load

What is being tested

Was free time applied at the agreed stop or load boundary? The boundary for this investigation is detention allowance per stop versus per load. Begin with the disputed transaction or population, then identify which multi-stop route establishes the observed position and which stop timestamps supports the comparison. A difference in totals should not replace this question.

Evidence: multi-stop route

For detention allowance per stop versus per load, multi-stop route must be linked to stop timestamps. Preserve the source owner, transaction reference, period and accepted version. Explain which field answers the financial question and which facts still require confirmation. Incomplete supporting records should create a named evidence gap rather than an assumed quantity, price or entitlement.

Evidence: stop timestamps

For detention allowance per stop versus per load, stop timestamps must be linked to free-time boundary clause. Record the date convention and timezone where relevant. Separate occurrence, notification and posting times. A later administrative entry may describe an earlier event; the review must use the event specified by the governing record rather than whichever date is easiest to extract.

Evidence: free-time boundary clause

For detention allowance per stop versus per load, free-time boundary clause must be linked to detention invoice. Retain the applicable wording, effective dates and scope of covered transactions. Identify the event or population that controls the calculation. Do not silently replace a contractual definition with a dashboard label, customary practice or the latest published rule.

Evidence: detention invoice

For detention allowance per stop versus per load, detention invoice must be linked to multi-stop route. Keep the issued document version and line-level quantity, currency and service period. A header total cannot establish which component is being tested. Retain later corrections as linked versions, so a replacement does not create a second liability.

Reconciliation logic

Allocate elapsed and free time using the contract's stated boundary rather than sum every stop into one clock. Build the comparison at the level identified by multi-stop route and retain the governing version from stop timestamps. Show intermediate classifications and excluded items separately; a net total can hide an unsupported component or a correctly offset correction.

Exception conditions

A load-level allowance may not reset at each stop. Treat the item as an unresolved exception only when the comparison described here cannot be supported by the linked multi-stop route, stop timestamps, free-time boundary clause, detention invoice. Document the conflicting input or rule. A plausible operational explanation requires validation, but it should not be discarded to maximize an apparent financial difference.

Human review and outcome

Logistics validates stop grouping and rate terms. Produce a stop-to-load detention calculation. Keep the reviewer's reason and source references with that disposition. A supported correction should be followed to the revised record or settlement; an accepted explanation can close the question with no adjustment. Missing authority or evidence should remain an open task rather than a confirmed recovery.

Limitations and processing boundary

A repeated reference, missing scan or estimated comparison does not prove an overcharge. The native shipment and invoice matching engine is not complete. Validate shipment identity, governing rates and accepted adjustments before reporting a financial outcome. In this scenario, absence of multi-stop route or stop timestamps limits whether the comparison can be completed. The review method describes what people should validate, not a promise that AuditRes automatically detects or executes this specific outcome.

AuditRes pathway

Discuss detention allowance per stop versus per load in the Freight workspace. Review current plans, the shared platform and secure evidence requirements; use the existing contact path to confirm the sources and validation this scope requires.

AuditRes Freight: Available for onboarding. Public previews use synthetic demonstration data; production processing remains gated until applicable customer sources and authoritative processors are connected and validated.

Neighboring financial questions

Freight resource hub · All guides in this evidence collection