Checklist for Filing Market Transaction Records with Italian Authorities

Italian market regulation rarely asks for one document. It asks for a family of them, each with its own authority, portal, format and clock. A trade that looks routine to the front office can trigger a transaction report to Consob, a submission to a trade repository under EMIR, an update to a major holdings notification, an entry in the insider list and, depending on the entity, a line in the anti-money-laundering file. Filing three out of four on time is not partial compliance. It is non-compliance with a smaller number of things.

What follows is the working checklist — the sequence an experienced compliance or finance team runs before, during and after submission.

Map the regime before you open a form

The most common filing mistake happens well before anyone touches a portal: the team reaches for the form it used last time. Start instead by matching the transaction to an obligation and an authority. Italian transaction records can fall under MiFIR reporting to Consob, EMIR reporting to a trade repository, transparency and market abuse duties, beneficial ownership registration with the Register of Beneficial Owners held through the Chambers of Commerce, AML record-keeping, or sector rules administered by Banca d'Italia or the competition authority.

Four questions to answer before submission

1. Which authority, which regime? A report filed with the right content to the wrong authority is still late.
2. Which legal entity is the reporting entity? The Italian bank, the branch, the investment firm subsidiary, the issuer — they are not interchangeable.
3. Is this event-driven or periodic? Event-driven filings are the ones that slip, because nobody owns the calendar.
4. Who signs, and is that delegation current? Check the board resolution or power of attorney rather than assuming the person who signed last year is still authorised.

Record the answers in a short internal register. When an examiner asks why a file went where it went, that register is your first exhibit.

Deadlines: build the calendar backwards

Most regimes give you less room than people assume, and some give you less than the front office realises. Transaction reporting under MiFIR must reach the competent authority as soon as possible and no later than the close of the next working day. EMIR reporting to a trade repository generally follows a next-working-day rhythm as well. Neither is a 24-hour rule, and treating it as one creates its own errors: trades booked after the daily cut-off, Italian public holidays, and the difference between a working day and a trading day.

Event-driven filings to flag on the trading day itself

• Significant shareholding notifications under the transparency rules, which run on a trading-day clock counted from the transaction, not from month-end.
• Managers' transactions, notified to the authority and disclosed by the issuer within three working days under the market abuse regime.
• Inside information disclosures, which cannot wait for a scheduled committee.
• Suspicious transaction and order reports, which must go without delay once the suspicion exists — there is no batching window.
• Merger and competition notifications where thresholds are met, filed before completion rather than after.

A useful habit: put the deadline in the trade blotter as a derived field, computed by system, and compare it with the actual submission timestamp the following morning. Two weeks of that comparison usually reveals where the process leaks.

Forms, portals and access before the clock starts

Credentials are the quiet failure point. A filing that cannot be submitted because a token expired or an account belonged to someone who left in March is no different, in regulatory terms, from a filing nobody attempted.

• A registered and actively monitored PEC address at the entity level, not a personal mailbox.
• A qualified digital signature in date, with a renewal date in the calendar.
• At least two named people with working portal access, plus a documented escalation contact at the authority.
• The current version of the form itself. Authorities revise fields and validation rules without much ceremony.
• A test or staging submission where the portal offers one, particularly before a first filing or a new instrument type.

Keep a short portal sheet: URL, account owner, token location, signature holder, support telephone number. It sounds administrative. It is the difference between a calm Thursday and a missed deadline.

Data and supporting documents

Content errors are rarely about the economics of the trade. They are about identifiers, and they are found by reconciliation rather than by reading.

1. LEI of the reporting entity and counterparty — valid, current, not lapsed for non-renewal. This single check prevents a large share of rejections.
2. ISIN confirmed against the instrument actually traded, not the similar one on the same desk.
3. MIC of the execution venue, and the correct capacity and client identifier fields.
4. Price, quantity, currency and timestamp matched to the front-office booking, allowing for the documented aggregation or netting methodology.
5. Late bookings routed deliberately to the following day, with the decision noted rather than improvised.

Behind the data, keep the file that would let a reviewer reconstruct it: order tickets and confirmations, the authorisation to file, the delegation of signature, and the key correspondence. For AML records, Italian rules generally require retention of around ten years; other regimes have their own clocks, so store to the longest applicable period.

The errors that keep appearing

Filing the wrong entity, usually the parent instead of the regulated subsidiary. Reporting an aggregate where individual records are required, or the reverse. Resubmitting a rejected file with no change log, so nobody can tell what was corrected. Assuming a portal acknowledgement means regulatory acceptance. Reusing last year's form, with a field quietly deprecated. Filing with Consob what belongs with Banca d'Italia, or with a trade repository what belongs to the national authority. And, most avoidably, having no archive of what was actually sent, by whom, and at what time.

Tip: when a rejection arrives, log three things — the rejection message verbatim, the corrected field, and the resubmission timestamp. That log is worth more than any procedure document when questions come later.

Review before you submit, and after

Two pairs of eyes, always, with the reviewer starting from the source document rather than from the draft report. A reviewer who reads the finished file tends to see what the preparer saw. Someone who begins with the confirmation and the blotter line catches the mismatched ISIN in seconds.

After submission, make sure somebody owns the response. Portals reject quietly, sometimes into a mailbox nobody monitors. Check the status the next morning, archive the acknowledgement, and store a dated copy of the submitted file in a folder with read-only permissions. Retention without reconstruction is just storage.

A one-page checklist to run each week

• Obligation, authority and reporting entity confirmed and logged.
• Deadline computed by system; holiday calendar applied.
• LEI, ISIN, MIC and identifiers reconciled to source.
• Signatory delegated and signature valid.
• Four-eyes review completed and initialled.
• Submission accepted, timestamp captured, file archived.
• Event-driven items checked on the trading day, not at week-end.

Rules, thresholds and portal requirements do change, and the specifics differ between entities and instruments. Verify the current guidance from Consob, Banca d'Italia and, where relevant, the Chambers of Commerce before relying on any deadline, and take professional advice where the exposure is material.

Photo: myrfa / Pixabay