What is being tested
Did payment meet the contract's settlement-date condition for an early-payment discount? The boundary for this investigation is early-payment discount bank settlement date. Begin with the disputed transaction or population, then identify which discount terms establishes the observed position and which invoice due timeline supports the comparison. A difference in totals should not replace this question.
Evidence: discount terms
For early-payment discount bank settlement date, discount terms must be linked to invoice due timeline. 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 due timeline
For early-payment discount bank settlement date, invoice due timeline must be linked to bank settlement record. 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: bank settlement record
For early-payment discount bank settlement date, bank settlement record must be linked to remittance discount. Use the opening position, dated movements and closing position together. Preserve the distinction between requested, authorized and posted changes. The reconciliation should explain how the source item moved through the account, not simply assert that the final total agrees.
Evidence: remittance discount
For early-payment discount bank settlement date, remittance discount must be linked to discount terms. 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.
Reconciliation logic
Compare the governing payment event with the deadline rather than internal payment approval date. Build the comparison at the level identified by discount terms and retain the governing version from invoice due timeline. Show intermediate classifications and excluded items separately; a net total can hide an unsupported component or a correctly offset correction.
Exception conditions
A timely instruction may settle after the eligibility cutoff. Treat the item as an unresolved exception only when the comparison described here cannot be supported by the linked discount terms, invoice due timeline, bank settlement record, remittance discount. 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 settlement evidence and procurement validates event definition. Retain a discount eligibility calculation and resolve disputed timing. 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 discount terms or invoice due timeline 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 early-payment discount bank settlement date 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 partial invoice settlement
- Supplier refund bank-fee shortfall
- Supplier price settlement surviving replacement obligations
Procurement resource hub · All guides in this evidence collection