What is being tested
Was a refund shortfall explained by authorized bank fees rather than an unpaid supplier credit? The boundary for this investigation is supplier refund bank-fee shortfall. Begin with the disputed transaction or population, then identify which refund instruction establishes the observed position and which bank receipt supports the comparison. A difference in totals should not replace this question.
Evidence: refund instruction
For supplier refund bank-fee shortfall, refund instruction must be linked to bank receipt. 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: bank receipt
For supplier refund bank-fee shortfall, bank receipt must be linked to fee allocation terms. 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: fee allocation terms
For supplier refund bank-fee shortfall, fee allocation terms must be linked to approved credit. 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: approved credit
For supplier refund bank-fee shortfall, approved credit must be linked to refund instruction. Trace the financial reference to the original obligation and final application or cash settlement. Approval is not the same as receipt of money. Preserve partial amounts, currency and reversals so one adjustment cannot be counted at several stages as separate financial benefit.
Reconciliation logic
Bridge the supplier remittance amount to net cash and separate correspondent or conversion fees. Build the comparison at the level identified by refund instruction and retain the governing version from bank receipt. Show intermediate classifications and excluded items separately; a net total can hide an unsupported component or a correctly offset correction.
Exception conditions
The agreement may assign certain transfer costs to the recipient. Treat the item as an unresolved exception only when the comparison described here cannot be supported by the linked refund instruction, bank receipt, fee allocation terms, approved credit. 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
Treasury validates remittance chain and fee authority. Close confirmed cash separately from disputed fee responsibility. 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 PO, acceptance record or supplier credit request alone cannot prove a complete recovery. The authoritative supplier, contract, PO, invoice and receipt processor is not complete. Treat commercial interpretation, authorized acceptance and final credit application as separate validation steps. In this scenario, absence of refund instruction or bank receipt 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 supplier refund bank-fee shortfall in the Procurement 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 Procurement: 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
- Supplier bank-detail changes and invoice review boundaries
- Early-payment discount bank settlement date
- Supplier credit memo wrong purchase order
- Supplier unapplied credit after account migration
Procurement resource hub · All guides in this evidence collection