Per EBA taxonomy, concatenation of following fields in Template 8.01 should be unique (unique key).  
- Entity ID
- Report Name
- Service Identifier 0005
- Service Type 0010
- Unique service title as per bank taxonomy 0020
- Code 0040
- Code 0060
- Contract ID 0130 
This causes duplication error across rows reporting similar intra-entity services between different branches, i.e. identical providers/receiver codes and identical other fields required for unique key.

This was raised to Nasdaq with following response received. However, this does not account for identical reporting in fields across all fields in unique key for similar services: 
According to the Annex II – Instructions on Resolution Planning Reporting published by the EBA on its official website under Reporting Framework 4.2, the combination of values reported in columns 0010, 0020, 0040, 0060, and 0130 of report Z 08.01 - Relevant Services constitutes a primary key and must therefore be unique for each row of the template.
"A similar report structure is also supported by the EBA in the annotated templates for the RES module, where columns 0005, 0010, 0020, 0040, 0060, and 0130 are explicitly marked as key fields.
To align with the report structure defined by the regulator, the dimensions corresponding to these columns are positioned on the Y axis in the EBA RES Taxonomy solution to drive report dynamics and to prevent duplication of identical value combinations within the report.
With regard to columns 0040 and 0060, the mentioned instructions specify that column 0040 must contain a unique identifier of the legal entity reported in column 0030. This identifier must differ from the one reported in column 0060, unless the service is intra entity, in which case the service recipient code and service provider code are expected to be identical. In turn, the EBA RES Taxonomy solution supports this behavior, as noted in your case description."