Records · procedure · next step
Transaction reporting: rejections and corrections
A regulatory transaction-reporting record links a source trade to report identifiers, actual submissions, responses and corrective versions. French MiFIR and Swiss participant/securities-firm reporting have different scopes and recipients. A transport receipt does not establish regulatory acceptance, and a changed local record is not a corrected submission. This preparation does not determine reportability, generate an accepted message or replace management disclosures, suspicion reporting or a customer execution complaint.
General information and document preparation. The facts, actual procedural acts and applicable versions must be checked.
Julie’s legal research currently covers French law. The Swiss sections prepare documents; they do not establish Swiss-law product capability.
Julie by AlphaDeep
Julie currently assists with French law. Which French transaction, report and rejection references would you like to reconcile?
3 free questions at signup. Avoid names and sensitive information.
Which reporting actor and legal perimeter were supplied?
Record the executing firm and professionally assessed scope. MiFIR article 26 differs from Swiss FinMIA/FinMIO-FINMA participant and securities-firm duties; similar technical formats do not create identical legal obligations.
Which source trade supports the reported figures?
Connect source reference, instrument, execution, quantity, price and currency to supporting records. The record reconciles supplied information rather than inventing missing classification or identifying real counterparties publicly.
Prepare the records
Julie’s legal research currently covers French law. The Swiss sections prepare documents; they do not establish Swiss-law product capability.
Synthetic example
Source trade, report, submission, response and corrective-version chain
- Reporter
- Firm E1, supplied capacity R1
- Documented perimeter
- Instrument T1, professional assessment Q1
- Source transaction
- T-001, 100 units, 3 November 2026
- Identifiers
- R-001 linked to T-001; masked counterparty C1
- Format and channel
- Schema V1 and mechanism M1 to verify from records
- Submission
- S1 on 4 November; transport receipt A1
- Received status
- Rejection J1 for R-001, actual reason retained
- Correction
- R-002 replaces R-001; new submission outcome unknown
This record organises supplied documents and values; it certifies no entitlement, permission or safety.
Which identifiers connect report and response?
Keep source-trade ID, report ID and recipient/message references. Swiss Transaction Report data include specific trade references; similar labels alone do not establish that two responses concern the same submission.
Which report type and schema were actually used?
Preserve the current technical specification and channel. SIX Trade Reports and Transaction Reports differ; acceptance of an RTS22 format under SIX rules does not turn the Swiss duty into MiFIR.
Which event and submission dates are evidenced?
MiFIR specifies reporting as quickly as possible and no later than the following working day’s end under its scope. Preserve event, submission and actual response dates without transplanting that deadline into every Swiss branch.
What is the difference between transport receipt and rejection?
Connect the actual status to its report ID and meaning. A technical acknowledgment proves only its stated processing step; retain rejected reports and their reasons rather than marking them accepted.
How are gaps and duplicate submissions reconciled?
Compare front-office records with reported data and, where available, authority samples. RTS22 addresses duplicates, omissions and unnecessary reports; do not delete a mismatch merely to balance a count.
What proves correction or cancellation reached the recipient?
Retain original report, cancellation where applicable, replacement and responses. MiFIR requires correction; SIX provides distinct correction/cancellation mechanisms, including deletion and resubmission for a Transaction Report.
Frequently asked questions
Which reporting actor and legal perimeter were supplied?
Record the executing firm and professionally assessed scope. MiFIR article 26 differs from Swiss FinMIA/FinMIO-FINMA participant and securities-firm duties; similar technical formats do not create identical legal obligations.
Which identifiers connect report and response?
Keep source-trade ID, report ID and recipient/message references. Swiss Transaction Report data include specific trade references; similar labels alone do not establish that two responses concern the same submission.
Which event and submission dates are evidenced?
MiFIR specifies reporting as quickly as possible and no later than the following working day’s end under its scope. Preserve event, submission and actual response dates without transplanting that deadline into every Swiss branch.
What proves correction or cancellation reached the recipient?
Retain original report, cancellation where applicable, replacement and responses. MiFIR requires correction; SIX provides distinct correction/cancellation mechanisms, including deletion and resubmission for a Transaction Report.
Sources and versions
- LIMF — Obligation de déclarer des participants
État au 1er février 2024
- OIMF-FINMA — Transactions et contenu de la déclaration
État au 1er février 2023
- OIMF-FINMA — Transactions et contenu de la déclaration
État au 1er février 2023
- Règlement (UE) 600/2014 — Déclaration des transactions, article 26
Consolidation française du 23 novembre 2025
- Règlement délégué (UE) 2017/590 — Méthodes de déclaration, article 15
Article 15 français, version 000.002 vérifiée le 9 novembre 2026
- SIX — Règlement de l’Instance pour les déclarations
Règlement du 19 mai 2026, en vigueur le 1er juillet 2026
- SIX — Règlement de l’Instance pour les déclarations
Règlement du 19 mai 2026, en vigueur le 1er juillet 2026
- SIX — Règlement de l’Instance pour les déclarations
Règlement du 19 mai 2026, en vigueur le 1er juillet 2026
- SIX — Règlement de l’Instance pour les déclarations
Règlement du 19 mai 2026, en vigueur le 1er juillet 2026