571. When the counterparty or the ERR submits a report with action type 'Revive', the TR should process the report and based on the information included in the fields 'Expiration date' or 'Early termination date', assess whether to reinclude it in the TSR or simply update its internal database relating to that derivative (see also an example on update of TSR after a report with action type 'Revive' in section 6.1.2).

572. The reporting counterparty or the ERR should provide complete information regarding the expiration date and the early termination date of a derivative. The provided information should follow the logical timeline sequence included in the validation rules. In particular, early termination date should not be in the future.

573. The field 'Event date' and the date part of the field 'Reporting timestamp' for reports with action type 'Revive' should be the same.

574. Where the expiration date in the derivative report is in the future or it is not populated, and the early termination date is not populated, the TR should include the derivative in the TSR with all the values that have been included in the submission with action type 'Revive'.

575. Where the expiration date or the early termination date are both in the past, the TR should update its own records, but not the TSR.

576. Where the expiration date is in the future, but the early termination date is in the past, the TR should update its own records, but not the TSR.