I suggest we don't follow how EasyPay configures the CPF Rates cause it's too tricky to use.
1 template which includes all the fields is enough and we follow the formula which was specified backend to map with the fields in calculating CPF.
1 template is enough as long as we store CPF Rates by CPF Rate Policy hence we need Effective Date and CPF Policy Description to maintain this.
And since the CPF Rate Tables are released in patches, hence its not the user who will update the CPF Rate but the system provider. For easier view, I still suggest to use one tabular template to show all rates.