Master data & transactions

What changing master data affects

When you change a counterparty, material or price in ClaimDS, it applies to future transactions — past business volume keeps the values it was loaded with.

This is the single most important thing to understand about changing master data in ClaimDS: a change applies to the future, not the past. Rename a partner, adjust a price, re-categorise a material — and your old transactions stay exactly as they were. Only new ones use the new values.

Why — the snapshot principle

When a business-volume line is loaded, ClaimDS freezes the details it needs onto that line — the partner's code, name and GSTIN, the material's code, the prices, the category classifications. That frozen copy is what the line keeps forever. So a later edit to the counterparty or material record doesn't reach back and rewrite it.

What that means in practice

  • Rename a partner or change its code — old invoices still show the name and code they were issued under; new ones use the new value.
  • Change a price — past business volume keeps the price it was loaded with; future volume picks up the new price.
  • Re-categorise a material — historical lines keep their original classification; new lines get the new one.

In every case, the accruals already built from those past lines are undisturbed.

When you DO want to change the past

If a historical figure is genuinely wrong, the fix isn't to edit master data — it's to correct the transaction itself. See edit or cancel a transaction. That keeps the distinction clean: master data sets the rules going forward; transactions hold what actually happened.

Still stuck?

Book a demo and we'll walk through it on your own data — or just talk to us.

What changing master data affects — ClaimDS