What is being tested
Was a third-party receipt allocated to the intended debtor with authorized evidence? The boundary for this investigation is customer payment sender differs from contracted debtor. Begin with the disputed transaction or population, then identify which bank sender record establishes the observed position and which customer authorization supports the comparison. A difference in totals should not replace this question.
Evidence: bank sender record
For customer payment sender differs from contracted debtor, bank sender record must be linked to customer authorization. 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: customer authorization
For customer payment sender differs from contracted debtor, customer authorization must be linked to invoice debtor. 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: invoice debtor
For customer payment sender differs from contracted debtor, invoice debtor must be linked to remittance reference. 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: remittance reference
For customer payment sender differs from contracted debtor, remittance reference must be linked to bank sender record. 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
Compare remittance authority and debtor identity rather than infer ownership from sender name. Build the comparison at the level identified by bank sender record and retain the governing version from customer authorization. Show intermediate classifications and excluded items separately; a net total can hide an unsupported component or a correctly offset correction.
Exception conditions
A parent company can legitimately pay another entity's invoice. Treat the item as an unresolved exception only when the comparison described here cannot be supported by the linked bank sender record, customer authorization, invoice debtor, remittance reference. 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 payer attribution and authorized customer instruction. Return a payer-to-debtor allocation record with ambiguous cash unapplied. 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 bank sender record or customer authorization 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 customer payment sender differs from contracted debtor 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
- Customer short payment investigation
- Customer duplicate remittance split-bank receipts
- Customer advance transferred between projects
- Collections payment evidence hold expiry
AR/Collections resource hub · All guides in this evidence collection