What is being tested
Did each consolidated invoice line map to the correct approved purchase order? The boundary for this investigation is supplier consolidated invoice po attribution. Begin with the disputed transaction or population, then identify which consolidated invoice detail establishes the observed position and which PO crosswalk supports the comparison. A difference in totals should not replace this question.
Evidence: consolidated invoice detail
For supplier consolidated invoice po attribution, consolidated invoice detail must be linked to PO crosswalk. 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: PO crosswalk
For supplier consolidated invoice po attribution, PO crosswalk must be linked to receipt lines. Retain stable identifiers and their effective relationships. Current labels are insufficient when assets or accounts changed during the period. Explain one-to-many relationships explicitly and preserve the history needed to distinguish an alias, replacement or reassignment from a genuinely additional item.
Evidence: receipt lines
For supplier consolidated invoice po attribution, receipt lines must be linked to allocation record. 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: allocation record
For supplier consolidated invoice po attribution, allocation record must be linked to consolidated invoice detail. 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
Reconcile line-level quantities and prices before accepting a header-level order reference. Build the comparison at the level identified by consolidated invoice detail and retain the governing version from PO crosswalk. Show intermediate classifications and excluded items separately; a net total can hide an unsupported component or a correctly offset correction.
Exception conditions
One invoice can legitimately cover several approved orders. Treat the item as an unresolved exception only when the comparison described here cannot be supported by the linked consolidated invoice detail, PO crosswalk, receipt lines, allocation record. 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 line matching and procurement validates order scope. Retain a multi-order invoice allocation with unmatched lines 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 consolidated invoice detail or PO crosswalk 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 consolidated invoice po attribution 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
- Purchase-order quantity mismatch with split deliveries
- Split supplier invoices cumulative order quantity
- Supplier duplicate invoice line within one document
- Supplier invoice revision versus new liability
Procurement resource hub · All guides in this evidence collection