Detention clock suspension during carrier interruption

What is being tested

Were agreed nonchargeable interruption intervals excluded from detention? The boundary for this investigation is detention clock suspension during carrier interruption. Begin with the disputed transaction or population, then identify which arrival and departure log establishes the observed position and which interruption event supports the comparison. A difference in totals should not replace this question.

Evidence: arrival and departure log

For detention clock suspension during carrier interruption, arrival and departure log must be linked to interruption event. Document the observation window, units, inclusion criteria and export version. Identify gaps and corrected events before using the total. Keep raw observations separate from derived quantities so a reviewer can reproduce the population without assuming every logged event is independently chargeable.

Evidence: interruption event

For detention clock suspension during carrier interruption, interruption event must be linked to detention suspension clause. 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: detention suspension clause

For detention clock suspension during carrier interruption, detention suspension clause must be linked to invoice calculation. 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: invoice calculation

For detention clock suspension during carrier interruption, invoice calculation must be linked to arrival and departure log. 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

Subtract only the documented intervals the agreement excludes before applying free time and increments. Build the comparison at the level identified by arrival and departure log and retain the governing version from interruption event. Show intermediate classifications and excluded items separately; a net total can hide an unsupported component or a correctly offset correction.

Exception conditions

Not every loading pause suspends the contractual clock. Treat the item as an unresolved exception only when the comparison described here cannot be supported by the linked arrival and departure log, interruption event, detention suspension clause, invoice calculation. 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

Site operations validates cause and logistics validates clock rule. Retain a detention interval trace with disputed interruptions isolated. 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 arrival and departure log or interruption event 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 clock suspension during carrier interruption 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