What is being tested
Were replenishment movements counted as consumption in a consignment invoice? The boundary for this investigation is consignment replenishment mistaken for billable issue. Begin with the disputed transaction or population, then identify which replenishment receipt establishes the observed position and which issue-to-production log supports the comparison. A difference in totals should not replace this question.
Evidence: replenishment receipt
For consignment replenishment mistaken for billable issue, replenishment receipt must be linked to issue-to-production log. Preserve the transaction identity, measured or accepted quantity and who confirmed the event. Distinguish physical evidence from later system posting. Where condition affects acceptance, retain the authorized disposition instead of using a raw observation as an automatic commercial conclusion.
Evidence: issue-to-production log
For consignment replenishment mistaken for billable issue, issue-to-production log must be linked to movement-type dictionary. 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: movement-type dictionary
For consignment replenishment mistaken for billable issue, movement-type dictionary must be linked to consignment invoice. 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: consignment invoice
For consignment replenishment mistaken for billable issue, consignment invoice must be linked to replenishment receipt. 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
Separate stock additions from withdrawals and apply the contract's chargeable movement definition. Build the comparison at the level identified by replenishment receipt and retain the governing version from issue-to-production log. Show intermediate classifications and excluded items separately; a net total can hide an unsupported component or a correctly offset correction.
Exception conditions
A replenishment can simultaneously replace genuinely consumed units. Treat the item as an unresolved exception only when the comparison described here cannot be supported by the linked replenishment receipt, issue-to-production log, movement-type dictionary, consignment 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
Inventory control validates movement semantics. Return a movement-type reconciliation and resolve unsupported replenishment billing. 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 replenishment receipt or issue-to-production log 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 consignment replenishment mistaken for billable issue 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 supplier invoices for customer-owned manufacturing materials
- Consignment drawdown invoicing before consumption
- Supplier invoice receiving cutover after warehouse transfer
- Goods receipt posted after supplier invoice cutoff
Procurement resource hub · All guides in this evidence collection