What is being tested
Did an inside-delivery premium reflect the agreed floor or access level? The boundary for this investigation is inside delivery floor-level premium approval. Begin with the disputed transaction or population, then identify which delivery order establishes the observed position and which floor-level acceptance supports the comparison. A difference in totals should not replace this question.
Evidence: delivery order
For inside delivery floor-level premium approval, delivery order must be linked to floor-level acceptance. Preserve the transaction identity, measured or accepted quantity and who confirmed the event. Distinguish physical evidence from later system posting. Where condition affects acceptance, retain the authorized disposition instead of using a raw observation as an automatic commercial conclusion.
Evidence: floor-level acceptance
For inside delivery floor-level premium approval, floor-level acceptance must be linked to premium rate schedule. Preserve the authorized sender, accepted scope and event timestamp. Distinguish a request from its acceptance and check whether the approver had authority for this change. Later approval should remain visible as a separate event rather than rewrite the original sequence.
Evidence: premium rate schedule
For inside delivery floor-level premium approval, premium rate schedule must be linked to carrier invoice. Keep the dated calculation basis, eligible units and any limits or exclusions. Record the sequence of conversion, threshold selection and rounding. An arithmetic result is only supportable after its inputs and applicable version are independently confirmed for the transaction being reviewed.
Evidence: carrier invoice
For inside delivery floor-level premium approval, carrier invoice must be linked to delivery order. 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
Separate base inside placement from approved stairs or upper-floor service. Build the comparison at the level identified by delivery order and retain the governing version from floor-level acceptance. Show intermediate classifications and excluded items separately; a net total can hide an unsupported component or a correctly offset correction.
Exception conditions
A basic inside-delivery agreement may exclude upper floors. Treat the item as an unresolved exception only when the comparison described here cannot be supported by the linked delivery order, floor-level acceptance, premium rate schedule, carrier 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
Receiving validates accepted placement and sourcing validates scope. Return a placement-level price bridge. 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 delivery order or floor-level acceptance 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 inside delivery floor-level premium approval 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 inside-delivery charges and dock evidence
- Residential delivery classification amended address
- Parcel large-package surcharge threshold inclusivity
- Parcel additional-handling exclusion for paid oversize
Freight resource hub · All guides in this evidence collection