What is being tested
Did a vendor refund settle to a company-controlled card account after its user departed? The boundary for this investigation is procurement card credit after employee departure. Begin with the disputed transaction or population, then identify which card account mapping establishes the observed position and which employee departure record supports the comparison. A difference in totals should not replace this question.
Evidence: card account mapping
For procurement card credit after employee departure, card account mapping must be linked to employee departure record. 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.
Evidence: employee departure record
For procurement card credit after employee departure, employee departure record must be linked to refund reference. 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: refund reference
For procurement card credit after employee departure, refund reference must be linked to card statement. 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.
Evidence: card statement
For procurement card credit after employee departure, card statement must be linked to card account mapping. 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.
Reconciliation logic
Trace the card account continuity and refund posting rather than assume the former user controls the credit. Build the comparison at the level identified by card account mapping and retain the governing version from employee departure record. Show intermediate classifications and excluded items separately; a net total can hide an unsupported component or a correctly offset correction.
Exception conditions
A closed card can route refunds through an issuer process. Treat the item as an unresolved exception only when the comparison described here cannot be supported by the linked card account mapping, employee departure record, refund reference, card statement. 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 issuer settlement and card ownership. Retain a refund-to-company settlement record using minimized employee identifiers. 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 card account mapping or employee departure record 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 procurement card credit after employee departure 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
- Procurement audit software evidence-based evaluation
- Supplier unapplied credit after account migration
- Supplier credit expiry communicated after approval
- Return freight deduction from supplier credit
Procurement resource hub · All guides in this evidence collection