What is being tested
Did catalog pricing include only the selected configuration components? The boundary for this investigation is catalog item configuration price components. Begin with the disputed transaction or population, then identify which catalog configuration establishes the observed position and which component price schedule supports the comparison. A difference in totals should not replace this question.
Evidence: catalog configuration
For catalog item configuration price components, catalog configuration must be linked to component price schedule. 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: component price schedule
For catalog item configuration price components, component price schedule must be linked to approved requisition. 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: approved requisition
For catalog item configuration price components, approved requisition must be linked to supplier invoice. 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: supplier invoice
For catalog item configuration price components, supplier invoice must be linked to catalog configuration. 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
Rebuild the selected configuration price and separate default options from accepted options. Build the comparison at the level identified by catalog configuration and retain the governing version from component price schedule. Show intermediate classifications and excluded items separately; a net total can hide an unsupported component or a correctly offset correction.
Exception conditions
A mandatory component may not appear as a user-selected option. Treat the item as an unresolved exception only when the comparison described here cannot be supported by the linked catalog configuration, component price schedule, approved requisition, supplier 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
The requisitioner validates configuration and procurement validates price version. Retain a configuration price bridge rather than compare unlike catalog products. 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 configuration or component price schedule 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 item configuration price components 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
- Review index-linked supplier price adjustments
- Supplier price floor after index decline
- Catalog currency default mismatch
- Contract price effective date by shipment
Procurement resource hub · All guides in this evidence collection