What is being tested
Was a setup fee charged for a distinct authorized production setup rather than repeated invoice splitting? The boundary for this investigation is supplier setup charge repeat production runs. Begin with the disputed transaction or population, then identify which setup price rule establishes the observed position and which production run record supports the comparison. A difference in totals should not replace this question.
Evidence: setup price rule
For supplier setup charge repeat production runs, setup price rule must be linked to production run record. 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: production run record
For supplier setup charge repeat production runs, production run record must be linked to order releases. 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: order releases
For supplier setup charge repeat production runs, order releases must be linked to setup invoice lines. 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: setup invoice lines
For supplier setup charge repeat production runs, setup invoice lines must be linked to setup price rule. 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
Group invoice lines by actual setup event and compare repeated fees with the agreement's setup boundary. Build the comparison at the level identified by setup price rule and retain the governing version from production run record. Show intermediate classifications and excluded items separately; a net total can hide an unsupported component or a correctly offset correction.
Exception conditions
Several releases may require genuinely separate setups. Treat the item as an unresolved exception only when the comparison described here cannot be supported by the linked setup price rule, production run record, order releases, setup invoice lines. 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
Production validates run changes and sourcing validates charge basis. Retain a run-to-setup fee bridge with unsupported repeats isolated. 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 setup price rule or production run 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 supplier setup charge repeat production runs 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 tolerance thresholds and repeated small variances
- Quote validity expiry before purchase acceptance
- Supplier quote optional-scope inclusion
- Supplier quote discount stacking prohibition
Procurement resource hub · All guides in this evidence collection