Software reseller currency-lock settlement

What is being tested

Was reseller pricing converted using the agreed currency-lock date rather than the invoice-date rate? The boundary for this investigation is software reseller currency-lock settlement. Begin with the disputed transaction or population, then identify which reseller currency clause establishes the observed position and which locked-rate confirmation supports the comparison. A difference in totals should not replace this question.

Evidence: reseller currency clause

For software reseller currency-lock settlement, reseller currency clause must be linked to locked-rate confirmation. 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: locked-rate confirmation

For software reseller currency-lock settlement, locked-rate confirmation must be linked to order date. Keep the dated calculation basis, eligible units and any limits or exclusions. Record the sequence of conversion, threshold selection and rounding. An arithmetic result is only supportable after its inputs and applicable version are independently confirmed for the transaction being reviewed.

Evidence: order date

For software reseller currency-lock settlement, order date must be linked to reseller invoice. 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: reseller invoice

For software reseller currency-lock settlement, reseller invoice must be linked to reseller currency clause. 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

Recompute conversion from the expressly agreed currency basis and separate financing or payment conversion fees. Build the comparison at the level identified by reseller currency clause and retain the governing version from locked-rate confirmation. Show intermediate classifications and excluded items separately; a net total can hide an unsupported component or a correctly offset correction.

Exception conditions

A later amendment may reset the lock. Treat the item as an unresolved exception only when the comparison described here cannot be supported by the linked reseller currency clause, locked-rate confirmation, order date, reseller invoice. 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 rate evidence and procurement validates the applicable order. Return a currency-basis bridge and dispute only inconsistent 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

Do not infer license removability from activity alone or describe a proposed configuration change as confirmed savings. The authoritative spend, license and contract producer is not complete; customer evidence and processing validation are prerequisites to production conclusions. In this scenario, absence of reseller currency clause or locked-rate confirmation 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 software reseller currency-lock settlement in the Technology Spend 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 Technology Spend: 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

Technology Spend resource hub · All guides in this evidence collection