What is being tested
Was an unmatched supplier invoice missing receipt evidence only because receiving posted after cutoff? The boundary for this investigation is goods receipt posted after supplier invoice cutoff. Begin with the disputed transaction or population, then identify which delivery proof establishes the observed position and which receipt posting timestamp supports the comparison. A difference in totals should not replace this question.
Evidence: delivery proof
For goods receipt posted after supplier invoice cutoff, delivery proof must be linked to receipt posting timestamp. 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: receipt posting timestamp
For goods receipt posted after supplier invoice cutoff, receipt posting timestamp must be linked to invoice date. Use the opening position, dated movements and closing position together. Preserve the distinction between requested, authorized and posted changes. The reconciliation should explain how the source item moved through the account, not simply assert that the final total agrees.
Evidence: invoice date
For goods receipt posted after supplier invoice cutoff, invoice date must be linked to close cutoff schedule. 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.
Evidence: close cutoff schedule
For goods receipt posted after supplier invoice cutoff, close cutoff schedule must be linked to delivery proof. 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.
Reconciliation logic
Separate physical delivery from posting time and reconstruct the state available at approval. Build the comparison at the level identified by delivery proof and retain the governing version from receipt posting timestamp. Show intermediate classifications and excluded items separately; a net total can hide an unsupported component or a correctly offset correction.
Exception conditions
A later posting can describe an earlier legitimate receipt. Treat the item as an unresolved exception only when the comparison described here cannot be supported by the linked delivery proof, receipt posting timestamp, invoice date, close cutoff schedule. 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
Receiving confirms delivery and the controller confirms cutoff handling. Retain a delivery-to-posting timeline rather than label every late receipt an invalid charge. 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 delivery proof or receipt posting timestamp 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 goods receipt posted after supplier invoice cutoff 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
- Partial goods receipt invoice acceptance
- Receipt reversal after supplier replacement delivery
- Damaged goods accepted with price concession
Procurement resource hub · All guides in this evidence collection