I’m not sure an archive is required. Labeling a new tax code with the valid date can work. Several things to think about, however, are:
Effective dates of tax components may vary. Different taxing authorities may impose new rates on dates that differ from other authorities.
Applicability of tax components may also vary. Normally taxable sales delivered in other jurisdictions or to certain types of organizations may not be taxable by some authorities while remaining taxable by others.
In many cases, the majority of sales will carry the same tax assessment, making it convenient to be able to select a single, “customary” tax code without having to indicate all constituent components separately. But individual components should also be selectable and deselectable, automatically taking into account effective dates of rate changes. That suggests a small database of tax parameters.
As an example, my jurisdiction has a sales tax rate with four components, all set by different authorities, none of which necessarily have the same dates for their frequent rate changes. One component, levied by the state, is applicable to anything delivered in the state, but not to anything delivered outside the state. Another, levied by the city, does not apply when something is delivered outside the city. And so forth. None of the components applies to purchases by religious organizations or non-profits. Some types of products are exempt from one component, but not from others. This can quickly get pretty complex.