What is being tested
Did a supplier aggregate only entities permitted by the rebate agreement? The boundary for this investigation is supplier rebate multiple legal-entity aggregation. Begin with the disputed transaction or population, then identify which entity eligibility schedule establishes the observed position and which purchase ledger supports the comparison. A difference in totals should not replace this question.
Evidence: entity eligibility schedule
For supplier rebate multiple legal-entity aggregation, entity eligibility schedule must be linked to purchase ledger. 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: purchase ledger
For supplier rebate multiple legal-entity aggregation, purchase ledger must be linked to rebate clause. 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: rebate clause
For supplier rebate multiple legal-entity aggregation, rebate clause must be linked to settlement statement. 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: settlement statement
For supplier rebate multiple legal-entity aggregation, settlement statement must be linked to entity eligibility schedule. 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
Match entity membership dates to the eligible purchase population before testing thresholds. Build the comparison at the level identified by entity eligibility schedule and retain the governing version from purchase ledger. Show intermediate classifications and excluded items separately; a net total can hide an unsupported component or a correctly offset correction.
Exception conditions
Shared ownership alone may not authorize aggregated rebates. Treat the item as an unresolved exception only when the comparison described here cannot be supported by the linked entity eligibility schedule, purchase ledger, rebate clause, settlement statement. 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
Sourcing validates group eligibility and finance validates entity totals. Retain an entity-to-rebate base schedule. 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 entity eligibility schedule or purchase ledger 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 rebate multiple legal-entity aggregation 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
- Supplier credit applied to the wrong legal entity
- Retrospective rebate returns adjustment
- Supplier credit memo wrong purchase order
- Supplier unapplied credit after account migration
Procurement resource hub · All guides in this evidence collection