CMS API – potential breaking changes
Please be aware that if you are a Qualified Intermediary and you are submitting your end-client’s “Relief at Source” data via the CMS API, then you need to ensure that the following conditions are met before 10 May 2024.
- When submitting “Relief at Source” information over the CMS API, if the flag ReliefAtSource.Enabled is set to “true”, and a ReliefAtSource.TypeID submitted, then it will be mandatory to also submit a valid future date* (relative to the date of submission) in the field ReliefAtSource.ExpiryDate**
If, after this deployment, you have not taken action to guarantee the above, meaning the expiry date field is either = Null or has a past date (relative to the date of submission), your request will be rejected, and it may break your integration.
This validation affects the CMS API’s CreateCounterpart and UpdateCounterpart requests.
We will deploy the new validation in the Live/TST CMS API endpoint on 27 April 2024. This will allow you to test any developments that you may need to execute to cater for this change, taking place 10 May 2024. Please note that you can access the Live/Test environment with your Test CMS API User.
* It is possible to send an expiry date as late as 2099.
** Portuguese Relief at Source documents do not have an expiry date. Therefore, a ReliefAtSource.ExpiryDate is not required if the ReliefAtSource.TypeID is one of the following:
ReliefAtSource.TypeID | Description |
13 | Local corp (PT SH) |
16 | Foreign Corp (PT SH) |
19 | Local Indv (PT SH) |
22 | Foreign indv (pt sh) |
Previous updates
Product Update
Platform Enhancements
Learn moreProduct Update
SaxoPartnerConnect (SPC) enhancements during Q1/Q2
Learn moreProduct Update
SaxoPartnerConnect (SPC) enhancements during Q1/Q2
Learn more