I got confused by the current system behaviour.
What i recall is that if e.g. a S-xx standard rate changes from e.g. 5% to 6% at jan 1 xxxx you can set the valid until date of the S-xx tax record and save it.
Then create a new record with the same name S-xx but with an effective date Jan 1 xxxx.
I recall i did exactly this (creating a tax code record with a duplicate name) not that long ago.
On transactions, the user or the tax logic selects the S-xx code based on the effective from and valid until dates and sources the appropriate tax rate. That still works as expected.
However, currently in 2025.2 (or older versions, maybe too), the tax code cannot be saved with the same name. You get instructed to rename the (soon) outdated tax code, set the valid until date, and create a new tax code record S-xx with the effective from date set.
An issue is that reverse charge codes relying on the S-xx also have to be renamed, duplicated, and set up with valid until and effective from dates.
I would expect that the reverse charge codes (RC-xx) that have a Notional rate derived from S-xx do not need a change since the S-xx code is date-dependent.
However, it appears those reverse charge codes need to be set up with effective from and valid until dates, too.
I'm not sure if that worked like this way back then, but it appears a bit messy to me.
Maybe I do something in the wrong order - can anyone tell?
Thanks.