What is being tested
Were optional quote components billed without an accepted selection? The boundary for this investigation is supplier quote optional-scope inclusion. Begin with the disputed transaction or population, then identify which quotation options establishes the observed position and which accepted order scope supports the comparison. A difference in totals should not replace this question.
Evidence: quotation options
For supplier quote optional-scope inclusion, quotation options must be linked to accepted order scope. 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: accepted order scope
For supplier quote optional-scope inclusion, accepted order scope must be linked to option approval. 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: option approval
For supplier quote optional-scope inclusion, option approval must be linked to invoice detail. 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 detail
For supplier quote optional-scope inclusion, invoice detail must be linked to quotation options. 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
Match option identifiers to the accepted order and separate mandatory base scope from elective additions. Build the comparison at the level identified by quotation options and retain the governing version from accepted order scope. Show intermediate classifications and excluded items separately; a net total can hide an unsupported component or a correctly offset correction.
Exception conditions
An accepted bundle can include options without separate invoice labels. Treat the item as an unresolved exception only when the comparison described here cannot be supported by the linked quotation options, accepted order scope, option approval, invoice detail. 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 confirms selected scope and procurement confirms authorization. Return an option acceptance schedule and question unsupported extras. 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 quotation options or accepted order scope 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 supplier quote optional-scope inclusion 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 reconciliation software implementation prerequisites
- Supplier quote discount stacking prohibition
- Quote validity expiry before purchase acceptance
- Delivery-term change duplicated logistics scope
Procurement resource hub · All guides in this evidence collection