What is being tested
Was a catalog order transmitted in the intended contract currency? The boundary for this investigation is catalog currency default mismatch. Begin with the disputed transaction or population, then identify which catalog currency setting establishes the observed position and which requisition currency supports the comparison. A difference in totals should not replace this question.
Evidence: catalog currency setting
For catalog currency default mismatch, catalog currency setting must be linked to requisition currency. 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: requisition currency
For catalog currency default mismatch, requisition currency must be linked to order acknowledgment. Keep the accepted version, covered scope and relationship to earlier documents. Identify whether it adds, replaces or transfers an obligation. A newer document should not be assumed to govern an earlier transaction unless its scope and effective period support that conclusion.
Evidence: order acknowledgment
For catalog currency default mismatch, order acknowledgment must be linked to invoice currency. 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 currency
For catalog currency default mismatch, invoice currency must be linked to catalog currency setting. 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
Trace currency through request, order and supplier acceptance before interpreting numeric price differences. Build the comparison at the level identified by catalog currency setting and retain the governing version from requisition currency. Show intermediate classifications and excluded items separately; a net total can hide an unsupported component or a correctly offset correction.
Exception conditions
Identical numeric amounts in different currencies are not equivalent prices. Treat the item as an unresolved exception only when the comparison described here cannot be supported by the linked catalog currency setting, requisition currency, order acknowledgment, invoice currency. 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 and procurement validate accepted currency and correction authority. Document the governing currency and request correction of unsupported conversion. 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 catalog currency setting or requisition currency 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 catalog currency default mismatch 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
- Purchase-order quantity mismatch with split deliveries
- Catalog item configuration price components
- Quote validity expiry before purchase acceptance
- Supplier quote optional-scope inclusion
Procurement resource hub · All guides in this evidence collection