What is being tested
Were rejected units billed while ownership and return disposition remained unresolved? The boundary for this investigation is rejected goods vendor disposition pending. Begin with the disputed transaction or population, then identify which quality rejection report establishes the observed position and which return authorization supports the comparison. A difference in totals should not replace this question.
Evidence: quality rejection report
For rejected goods vendor disposition pending, quality rejection report must be linked to return authorization. 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: return authorization
For rejected goods vendor disposition pending, return authorization must be linked to ownership clause. 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: ownership clause
For rejected goods vendor disposition pending, ownership clause must be linked to supplier invoice. 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: supplier invoice
For rejected goods vendor disposition pending, supplier invoice must be linked to quality rejection report. 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
Compare accepted versus rejected quantities and the governing return mechanism before calculating a credit expectation. Build the comparison at the level identified by quality rejection report and retain the governing version from return authorization. Show intermediate classifications and excluded items separately; a net total can hide an unsupported component or a correctly offset correction.
Exception conditions
Rejection does not automatically transfer goods back to the supplier. Treat the item as an unresolved exception only when the comparison described here cannot be supported by the linked quality rejection report, return authorization, ownership clause, 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
Quality validates the rejection and procurement validates contractual disposition. Maintain a rejected-stock exception register without asserting a completed recovery. 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 quality rejection report or return authorization 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 rejected goods vendor disposition pending 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 unresolved findings at financial close
- Goods receipt posted after supplier invoice cutoff
- Partial goods receipt invoice acceptance
- Damaged goods accepted with price concession
Procurement resource hub · All guides in this evidence collection