Skip to content

Systems and records

Procurement contract rebate data: eligibility across several entities

By SourceX Editorial · Reviewed by Noah Loul ·

9 sections

Short answer

Represent rebate eligibility across several entities with a dated roster of eligible entities, purchase lines tagged with the buying legal entity, counting date and scope flags, and a period calculation that applies the roster as of each line's date. Keep returns linked, separate tier volume from the rebate base, and reconcile to the supplier statement and the settlement document that proves the rebate was credited.

License terms

Procurement contract rebate

This page covers procurement contract rebate data: eligibility across several entities.Illustrative

Key takeaways

  • Eligibility is a dated roster set by the agreement, not today's ownership chart or ERP group.
  • Every purchase line needs the buying legal entity, the counting date and scope flags.
  • Tier volume and rebate base can differ; keep separate flags so the calculation can be rerun.
  • Reconcile to the supplier statement line by line and explain each difference.
  • A settlement document, not a status field, proves the outcome.

How do you represent rebate eligibility across purchases by several entities?

Represent it as three linked things rather than one total. First, a dated roster of the entities the agreement says are eligible, each with the date it joined and left. Second, purchase lines tagged with the legal entity that bought, the date the agreement counts from (order, receipt or invoice) and the product's scope flags. Third, a period calculation that applies the roster as of each line's counting date, keeps returns and credits, and separates the volume that sets the tier from the volume the rebate is paid on.

Then reconcile the result to the supplier's rebate statement and to the settlement record that shows the rebate was actually paid or credited. A rebate that depends on purchases across several entities is a reconciliation problem first and an arithmetic problem second. Most disputes trace back to one question the CRM or ERP never answered: did this entity's purchase count on that date?

The rest of this page builds a contract and transaction reconciliation case that procurement and finance teams can use as is, shows where each field comes from in real rebate modules, and works through an illustrative case with a counterexample. It describes data structures, not the legal meaning of any particular agreement.

What the rebate modules in major ERPs record about eligibility

ERP rebate modules already encode most of the variables, which makes them a good checklist for what a case packet must capture. As described in each vendor's own documentation read on October 18, 2026, Microsoft Dynamics 365 Supply Chain Management describes a rebate as the return of part of the purchase price, typically based on a quantity or value of goods bought in a period and settled after the purchase amount is fully invoiced. Vendor rebates there can be based on purchase orders or on sales orders, and calculation periods can run by invoice, day, week, month, quarter, year or a customized period.

Scope is set per deal line. Each line names a company (legal entity), an account code of a single vendor or customer, a group or all, and an item code with the same three options. The documentation adds that users can process only deal lines assigned to the company they are currently using, even though the list page offers a multi-company view. Rebate groups can be attached to master records, and each customer can belong to any number of groups. A group-wide agreement therefore needs an explicit decision about which lines and which entity's run carry the pooled volume.

Tier logic varies more than people expect. Dynamics 365 offers stepped, cumulative, rolling and total calculation methods, and the same purchase volume produces different rebates under each. SAP S/4HANA condition contracts hold a list of eligible partners who may make claims; new partners start as Not Released and must be released before conditions apply, and pricing finds conditions only when the contract and partner entries are released and valid on the pricing date. SAP also lets business volume criteria be flagged as relevant for the scale, for the rebate, or both, so a product can count toward reaching a tier without earning a rebate itself.

Which entities' purchases count toward the threshold, and from when?

Only the entities the agreement makes eligible, and only from the date they became eligible. That sounds obvious, but the CRM account hierarchy, the ERP's vendor or customer groups and the corporate ownership chain are three different lists, and each drifts out of date at its own pace.

Ownership data helps check the roster but does not replace it. GLEIF's Level 2 data records who owns whom: legal entities with an LEI report their direct and ultimate accounting consolidating parents, defined through consolidated financial statements, with relationship records carrying dates. That tells you when a subsidiary entered the group. Whether its purchases count depends on the agreement's own definition of affiliate or eligible entity, which may be narrower, broader or a fixed named list.

Record each eligibility change as a dated event: entity added by amendment, entity acquired and added on notice, entity divested, entity excluded because it buys under its own agreement. When an acquisition closes mid-period, the roster entry starts on the effective date the agreement or notice sets, not the deal closing date and not the date someone updated the ERP group.

Why does adding up every entity's purchases overstate rebate volume?

The obvious total is the sum of every purchase by every entity in the group during the period. It is wrong whenever one of these constraints applies, and each one needs its own flag on the purchase line so the calculation can be rerun when someone disputes it.

Why does adding up every entity's purchases overstate rebate volume?
ConstraintHow it distorts the totalField that captures itTypical evidence
Entity not yet eligiblePre-joining purchases inflate qualifying volumeeligible_from on the roster, compared with the line's counting dateAmendment, notice letter, acquisition effective date
Wrong counting dateLines near period end land in the wrong periodcount_basis (order, receipt or invoice) and count_dateAgreement definition of qualifying purchase
Returns and credit notesGross volume overstates net qualifying volumeLinked credit lines with the original line referenceCredit memos, return authorizations
Off-scope itemsProducts outside the item scope countedin_scope flag from the item code or item groupProduct schedule attached to the agreement
Scale-only itemsItems that count for the tier are paid on, or the reversescale_relevant and rebate_relevant flagsAgreement tier and base definitions
Indirect purchasesPurchases through a distributor counted or missedchannel and selling-party fieldsDistributor tracing reports, agreement channel clause
Separate agreementsEntity buys under its own contract and is counted twicegoverning_agreement_id per lineContract register

The contract and transaction reconciliation case, component by component

A case packet is one agreement, one period and every record needed to reproduce the rebate decision. It should let a reviewer who never saw the deal recompute qualifying volume, choose the tier, and check the result against what was settled. Fields marked as evidence references point to documents; the packet stores the reference and the extracted value, not a retyped summary.

At a glance

The contract and transaction reconciliation case, component by component

The contract and transaction reconciliation case, component by component
ComponentKey fieldsSource recordCheck before the case is accepted
Agreement headeragreement_id, version, counterparties, effective and end dates, governing agreement for each entitySigned agreement and amendmentsVersion in force for the period is identified
Eligible entity rosterentity legal name, LEI or registry ID, ERP company or account IDs, eligible_from, eligible_to, basisAgreement schedule, amendments, noticesEvery buying entity in the lines appears on the roster or is marked ineligible
Product scopeitem or group IDs, in_scope, scale_relevant, rebate_relevantProduct schedule, ERP item groupsScope flags match the agreement text, not just the ERP setup
Tier schedulebasis (quantity or value), thresholds, calculation methodAgreement and ERP deal linesCalculation method named explicitly
Period calendarperiod start and end, count_basis, cut-off ruleAgreement and ERP period setupBoundary lines tested against the cut-off rule
Purchase linesline ID, buying entity, count_date, quantity, item, channel, agreement_idPO, receipt and invoice recordsLine totals reconcile to the ERP for each entity
Adjustmentscredit and return lines linked to original line IDsCredit memos, return recordsNo unlinked credits in the period
Supplier statementsupplier's qualifying volume and tier per periodSupplier rebate statementDifferences explained line by line
Decision and outcomecomputed tier, approver role and date, settlement document referenceApproval record, credit note or payment remittanceOutcome evidence exists, not only a settled status

Worked case (illustrative): an acquisition mid-year and a joint venture

This case is invented for illustration; the companies, dates and counts are not drawn from a real agreement, and it uses quantities instead of money. A distribution group signs an annual purchase agreement with a manufacturer. The agreement's eligible entities are the parent distributor and any subsidiary it controls, added from the date the parent gives written notice. Tier 1 applies from 40,000 units of in-scope product in the year and tier 2 from 60,000 units, with a cumulative method, so the highest tier reached applies to all qualifying units.

Starting state: the parent buys 38,000 in-scope units during the year. A regional distributor acquired on 1 July bought 9,000 units before notice was given on 15 July and 14,000 units after. A joint venture in which the parent holds a minority stake bought 6,000 units under its own name. Returns linked to the parent's purchases total 1,500 units.

The obvious total adds everything: 38,000 plus 23,000 plus 6,000, or 67,000 units, which reaches tier 2. The roster says otherwise. The acquired distributor's pre-notice 9,000 units fall before its eligible_from date, the joint venture is not a controlled subsidiary and is not named, and returns reduce the parent's volume. Qualifying volume is 38,000 plus 14,000 minus 1,500, or 50,500 units: tier 1.

The supplier's statement reports 52,000 units. The line-level comparison shows the difference is the 1,500 returned units, which the supplier booked in the following period because the credit notes were issued after year end. Under the agreement's invoice-date counting rule the supplier is right for this period, so the case records 52,000 units for the year, tier 1 either way, and carries the returns into the next period's packet.

Outcome check: the case is closed only when the settlement document exists, here a supplier credit note referencing the agreement and the period. A status of settled in the procurement system is not enough. Counterexample: if the parent had sent an amendment naming the joint venture as an eligible entity, its 6,000 units would count from the amendment's effective date, and the same purchases would produce a different answer. The roster, not the ownership chart, decides.

Which record proves the tier decision, and which proves the rebate was credited?

The settlement document proves the outcome, and the approval record proves the decision. In Dynamics 365, financial rebate outputs can be customer deduction journals, free text invoices or vendor invoices, and they include a reference to the originating rebate agreement for auditing. In SAP's condition contract settlement, settlement documents play the same role. Link the case to that document's ID and to the remittance or offset that shows money or credit actually moved.

Keep the decision and the outcome as separate fields. A tier computed by procurement, a tier claimed by the supplier and a tier actually credited can all differ, and the disagreements are the most useful part of the record for anyone studying how rebate disputes are resolved. A task record that ends at the procurement system's status field teaches only that someone clicked a button.

Agreement terms, accounting and confidentiality: where specialists take over

Three questions sit outside a data team's remit. What counts as an affiliate, a qualifying purchase or a valid notice is contract interpretation, so counsel reviews the agreement language before the roster is treated as final. How rebates are recognized in the books is an accounting decision for finance. Whether supplier pricing and rebate terms can be shared at all depends on the confidentiality clauses in the supplier agreement.

Narrow the scope when the roster cannot be rebuilt for a period, when amendments are missing, or when purchase lines cannot be tied to a buying legal entity. A smaller set of fully reconciled cases is more useful than a large set where eligibility was inferred from today's corporate structure.

Can reconciled rebate cases be licensed?

Sometimes, with the commercial terms handled carefully. Reconciled rebate cases show how purchasing decisions, eligibility rules and settlements interact, which is the kind of linked workflow record AI developers look for. They also contain supplier-confidential terms, and the supplier agreement usually decides what may leave the company. Removing names does not by itself create a right to license the records.

A procurement or finance team that wants to offer such cases can work through SourceX, which qualifies the records and then handles rights review, contracting, preparation and delivery. Supplier names and other identifying details are de-identified by SourceX through approved processing routes, and only after the buying company has signed an agreement fixing what the scope and terms are. Eligibility is checked first through a few questions about the company, with no purchase lines or rebate statements sent.

Frequently asked questions

Do a subsidiary's purchases count toward the parent's rebate?

Only if the agreement makes the subsidiary eligible, and only from the date it says. Some agreements cover any controlled affiliate, some require notice, and some list entities by name. Check the agreement's definition and the dated roster before pooling volume.

Which date decides the rebate period for a purchase near year end?

The date the agreement uses to define a qualifying purchase, which may be the order, receipt or invoice date. ERP rebate modules can be configured on different bases, so record the counting basis on each line and test lines near the cut-off explicitly.

What is the difference between scale volume and rebate base?

Scale volume decides which tier is reached; the rebate base is the volume the rate is applied to. SAP S/4HANA, for example, lets business volume criteria be marked as relevant for the scale, for the rebate, or both. Keep two flags on each line so the calculation stays reproducible.

How do you handle returns that cross a rebate period?

Link each credit or return line to the original purchase line and apply the agreement's counting rule to the credit itself. If credits are counted when issued, a return of last year's goods can reduce next year's volume; the case packet should show where each credit landed.

Is a settled status in the procurement system proof the rebate was paid?

No. A status shows that someone closed the task. Proof is the settlement document, such as a credit note or vendor invoice that references the agreement, together with the payment or offset that applied it.

Sources

  • Dynamics 365 describes rebates as a return of part of the purchase price based on quantity or value in a period, supports vendor rebates on purchase or sales orders, and references the originating agreement on financial outputs. Source
  • Dynamics 365 rebate deal lines name a legal entity, account scope and item scope, are processed per company, and use stepped, cumulative, rolling or total calculation methods. Source
  • Dynamics 365 rebate groups attach to master records, and a customer can belong to any number of groups. Source
  • SAP condition contracts list eligible partners who may claim, and new partners must be released before the conditions apply to them. Source
  • SAP S/4HANA can mark business volume criteria as relevant for the rebate scale, the rebate calculation, or both. Source
  • GLEIF Level 2 data records direct and ultimate accounting consolidating parents of legal entities with an LEI. Source

See if your company qualifies

A short company assessment. No data uploads are needed.

See if your company qualifies