Trace one PTRR transaction back to its exercise and participant
Begin PTRR record review with reproducible relationships, separately from clearing-exemption eligibility.
A service label is not a trace
Using a post-trade risk-reduction service does not explain a transaction's history. A reviewer needs its exercise, participant and before/after records. Truthound can check a prepared relationship table, not decide legal exemption or actual economic-risk reduction.
The October final draft
ESMA published its PTRR final draft report on October 20, 2026, addressing participant information, exercises, controls, record keeping and exemption monitoring. The draft RTS then goes to the Commission for endorsement. A final report and a rule already in force are different stages.
Prepare one exercise ledger
Start with one illustrative transaction, an exercise register and a participant table. Preserve exercise, participant, transaction, state and reference time separately. Owners identify required parents so the fixture can show where a missing relationship stops processing.
A repeated transaction may be a different stage
If a transaction appears at several stages, distinguish original and derived records. Do not delete every repeated identifier or merge distinct versions. Define the composite key from the exercise, participant and stage meanings.
Reproduce the relationship in Truthound
Truthound Core Python SDK 3.3.4, operating on a prepared Polars table, provides ForeignKeyValidator for supplied child/parent keys and MultiColumnUniqueValidator for a declared composite key. Separate a missing-parent fixture from a repeated-key fixture to reveal the different failures. Unexecuted fixtures remain test plans, not claimed results.
The existing pandas join has a boundary
An existing pandas 3.1.1 merge(validate=...) can retain join-cardinality checks. Cardinality, approved-parent membership and complete exercise records are different boundaries. A successful join does not establish that a transaction qualifies for exemption. A pandas match between null exercise keys does not confirm a parent exercise; retain it as a separate failure example.
Do not promote review states into eligibility
Keep an unresolved review state separate from confirmed eligibility. Record the evidence under examination and rule version used. A change in endorsement stage should trigger an explicit review of the internal contract rather than an assumed automatic update.
Follow the exception's cause
An exception should distinguish an absent exercise record, an incorrect participant mapping and a late source arrival. Replacing a missing parent with a default may make the table look valid while removing traceability. Return the issue to the record's owner.
Give the reviewer a walkable path
The artifact is a path a reviewer can walk from transaction to exercise and participant. Hand it over with technical reference results separate from economic and legal judgment. Reproducible records allow that later review to explain which inputs it actually used.
Conditions
Owners establish the final draft's scope and provide authorised records or fixtures with defined relationships.
Alternatives
Retain pandas 3.1.1 join-cardinality checks while assessing approved-parent membership separately.
Limitations
Reference checks do not determine clearing exemptions or realised portfolio-risk reduction.
Evidence
- Event checked
- Subject checked
- Modified
