Supplier invoice number reused across fiscal years

What is being tested

Were invoices with reused numbers kept distinct by supplier, year and transaction evidence? The boundary for this investigation is supplier invoice number reused across fiscal years. Begin with the disputed transaction or population, then identify which invoice dates establishes the observed position and which order references supports the comparison. A difference in totals should not replace this question.

Evidence: invoice dates

For supplier invoice number reused across fiscal years, invoice dates must be linked to order references. 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: order references

For supplier invoice number reused across fiscal years, order references must be linked to supplier numbering policy. 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: supplier numbering policy

For supplier invoice number reused across fiscal years, supplier numbering policy must be linked to payment ledger. 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: payment ledger

For supplier invoice number reused across fiscal years, payment ledger must be linked to invoice dates. 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.

Reconciliation logic

Compare service periods and source records before treating repeated invoice numbers as duplicates. Build the comparison at the level identified by invoice dates and retain the governing version from order references. Show intermediate classifications and excluded items separately; a net total can hide an unsupported component or a correctly offset correction.

Exception conditions

Supplier numbering may restart each year. Treat the item as an unresolved exception only when the comparison described here cannot be supported by the linked invoice dates, order references, supplier numbering policy, payment ledger. 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

AP validates transaction identity independently of document labels. Record distinct legitimate liabilities or supported duplicates. 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 invoice dates or order references 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 invoice number reused across fiscal years 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 resource hub · All guides in this evidence collection