Receivables disputed freight recharge evidence

What is being tested

Was a freight recharge supported by the customer's accepted cost basis? The boundary for this investigation is receivables disputed freight recharge evidence. Begin with the disputed transaction or population, then identify which customer recharge clause establishes the observed position and which carrier invoice supports the comparison. A difference in totals should not replace this question.

Evidence: customer recharge clause

For receivables disputed freight recharge evidence, customer recharge clause must be linked to carrier 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: carrier invoice

For receivables disputed freight recharge evidence, carrier invoice must be linked to allocation schedule. 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.

Evidence: allocation schedule

For receivables disputed freight recharge evidence, allocation schedule must be linked to customer dispute. 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: customer dispute

For receivables disputed freight recharge evidence, customer dispute must be linked to customer recharge 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.

Reconciliation logic

Separate seller transport cost from the specific customer's agreed recharge rights and markup. Build the comparison at the level identified by customer recharge clause and retain the governing version from carrier invoice. Show intermediate classifications and excluded items separately; a net total can hide an unsupported component or a correctly offset correction.

Exception conditions

A fixed sales price may already include freight. Treat the item as an unresolved exception only when the comparison described here cannot be supported by the linked customer recharge clause, carrier invoice, allocation schedule, customer dispute. 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

Sales operations validates scope and logistics validates carrier linkage. Retain a recharge entitlement package and disposition of unsupported extras. 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

No message, payment demand or cash application should be triggered solely by an unresolved comparison. The native full finding producer is not complete. Receipt ownership, settlement authority and the final ledger state require human validation. In this scenario, absence of customer recharge clause or carrier invoice 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 receivables disputed freight recharge evidence in the AR/Collections 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 AR/Collections: 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

AR/Collections resource hub · All guides in this evidence collection