Versioning can be implemented across different parts of your scheme to allow for different versions of rates, documents etc to all be running at the same time

Rate Versioning

The main concept of versioning is that we set a date for the new version to be effective from and assign a version number.

e.g. currently our rates are version 1 but from the 1st January 2026 we want to set rates version 2

Setting Versioning Date

When setting the date that a version needs to change, we only add this to our First premium (FP) and Renewal (RNL) rating files.

The formula to set the version control value using the date should not be added to the MTA rating file; an MTA will carry over the version control value set in the First premium (FP) or Renewal (RNL) record.

This value will ensure that the rates originaly applied to the record continue to be set, even if the rates have since changed.

Follow the steps below to add versioning into your scheme:

Step 1: Build a hidden question called “RatesVersion” in your question set. Set this up as a number type question

Step 2: Build a section at the top of your FP and RNL rating file that will populate this question:
SetCover:RatesVersion

Step 3: Build a formula for this section of your rating. This formula will tell SchemeServe which rates to use based on certain dates:

SetCover:RatesVersion
IF([Policy.InceptionDate_DateValue] >= #2026-01-01#, 2, 1)

- If the policy inception date is on or after 01/01/2026 → it returns 2
- If the policy inception date is before 01/01/2026 → it returns 1

Step 4: Add in your different rates:

Although you didn't include the formula to set the version control value using the date in the MTA rating file, you must include Step 4 in the MTA rating file. This will look for the rate version value set in your hidden field and apply the correct rates to the MTA (the same rates as applied at FP / RNL).

Documents:

Step 1: Create a hidden question called “DocumentVersion”. Make this a number type question.

Step 2: Build a section at the top of your rating file that will populate this question:
SetCover:DocumentVersion

Step 3: Build a formula for this section of your rating. This formula will tell SchemeServe which documents to use based on certain dates
SetCover:DocumentVersion
IF([Policy.InceptionDate_DateValue] >= #2026-01-01#, 2, 1)

- If the policy inception date is on or after 01/01/2026 → it returns 2
- If the policy inception date is before 01/01/2026 → it returns 1

Step 4: Head to your rule builder and build your document generation rules under your scheme, your insurer and when you want the document to be generated e.g. Any Type at On Cover.

Your rule will include one condition
If Document version is equal to 1 - then output Statement of Fact V1
If document version is equal to 2 - then output Statement of Fact V2
 

   This formula doesn't have to use [Policy.InceptionDate] as its condition. You can add whichever system ID suits your scheme.

   With Document versioning you could build this so that, unlike rates versioning, document branding could change at MTA. e.g. your logo has changed and you want it updated at MTA