Unilateral change of parameter names in IFS Cloud REST APIs

Hi IFS Community,
We are in the righteous process of upgrading from IFS Cloud 22R1 to 23R2.
In our non-regression tests we are examining all the ETL jobs we created using IFS Cloud REST APIs and some of them are failing upon 23R2 because there has been some unilateral change of parameter names by IFS in the methods we are using in their REST APIs.
Example :
* 22R1 : StatementDate on PRD

https://xxxxxx/main/ifsapplications/projection/v1/AutomaticTransactionMatchingHandling.svc/FetchBankTransDetails(Company='{Company}',CashAccount='{CashAccount}',ExcludeMatched={ExcludeMatched},IsFinalMatched='{IsFinalMatched}',StatementDate={StatementDate})

* 23R2 : BalanceDate on UAT
https://xxxxxx/main/ifsapplications/projection/v1/AutomaticTransactionMatchingHandling.svc/FetchBankTransDetails(Company='{Company}',CashAccount='{CashAccount}',ExcludeMatched={ExcludeMatched},IsFinalMatched='{IsFinalMatched}',BalanceDate={BalanceDate})

This is just one example, I can provide others…
Here for CVE, we are talking of an essential job used to interface daily bank transactions into hundreds of bank accounts.
In that case we cannot just use the same job during our tests, we have to clone it for 23R2 UAT, and then we will have to switch to that new one when go live with 23R2 in PRODUCTION.

I have 2 questions :
* I had in mind that upwards compatibility is essential when you are a software editor, isn’t it ?

* To prevent us from discovering those little surprises one by one as we go along in our tests, is there a documentation somewhere tracking all those IFS Cloud API methods parameters changes ?

Thanks for your help

PS : I will also open a more official case on IFS Support Portal