Vigenza

CASP complaints registers: linking receipt, investigation and response

· Redazione Vigenza

Draft date: 8 November 2026. Author: Vigenza Editorial Team.

A crypto-asset service provider's complaints register must allow the complaint received and the measures taken in response to be reconstructed. In practice, it helps to connect the initial communication, investigation and decision sent to the client within the same file. A row marked “closed” does not explain which issues were examined or why that response was given.

The legislative reference is Article 71 of Regulation EU 2023/1114, MiCA, supplemented by Delegated Regulation EU 2025/294. This guide concerns register organisation for CASPs within that scope: it does not describe every intermediary's complaints regime or complaints made directly to authorities. The suggested practical fields must be coordinated with the procedure actually applicable.

Give the case an identity on receipt

Allocate a stable reference and record the communication in the channel through which it arrived. Retain the initial content so it is distinguishable from an internal summary. A client may describe several problems in one message: immediately reducing these to a general category risks losing part of the complaint during investigation.

Identify the service concerned and link previous communications where relevant. A support contact and a formal complaint should not become disconnected files about the same event, but neither should they be conflated without applying the procedure's criteria. If classification is uncertain, assign review to a competent function and retain the content received.

Separate receipt from checking information

The calendar should distinguish arrival of the message from completion of a request for further information. These dates answer different questions. Do not replace the initial date with that of the latest document, as this would remove elapsed time from the chronology. If a stage depends on missing information, make clear what was requested and why.

A clarification request should connect to the unresolved issue. Before requesting new documents, check those already held in the relevant systems and the applicable rules. A general request to resubmit the whole file may delay work without clarifying the complaint. Keep references to the communication sent and the response received in the register.

Organise investigation around specific issues

Prepare a note distinguishing the points raised by the client. For each, link the documents examined and identify what is confirmed, disputed or still awaiting verification. A technical extract may need explanation for the person preparing the decision. Do not automatically treat the absence of information from a system as proof that an event did not happen.

Assign a case owner and identify contributing functions. If information is required from a supplier, record the request and follow-up while retaining control of the internal file. Passing a question to another function does not resolve the complaint. The register should show which stage is actually awaiting a response rather than making an internal referral look like completion.

Connect timing to the correct procedure

Configure deadlines from the current text and approved procedure, distinguishing statutory time limits from shorter internal targets. Delegated Regulation 2025/294 governs timing and the handling of delays: a deadline should not be imported by analogy from another sector. This guide does not propose one duration for every stage or automatic suspension whenever additional information is requested.

If a deadline is at risk, escalate the problem before closure and apply the relevant procedure. Preserve the actual dates of activities. Retrospectively changing the calendar does not remedy a delay and prevents it being measured. The file must distinguish an updated forecast from a deadline already passed. Internal reminders should help identify the issue early enough for the responsible function to act.

A fictional example with two different issues

The imaginary CASP “Riva Digitale” receives a complaint challenging a charge and a failure to answer a support request. The operator checks the charge and drafts a response only on that point. A reviewer notices that the initial message contained a second issue which has not yet been analysed.

The case remains open while the investigation into client communications is completed. Support messages and the reasons concerning both points are linked. The final response distinguishes the outcomes instead of merging them into a general “complaint rejected”. This example is invented and is neither a decision on a real case nor a template to use without adaptation.

Close with the document actually sent

Link the final decision and evidence of its transmission using the relevant channel. Make the version sent to the client recognisable against internal drafts. A preparatory note may contain assumptions later corrected: it should not be the only document that the register presents as the final response.

After closure, determine whether connected internal actions are required, such as a process review. Closing the complaint and completing a corrective action may happen on different dates. Separating them allows outstanding work to be monitored without misrepresenting the status of the client response. Register categories should be consistent enough to support useful comparison over time and to distinguish an isolated issue from a recurring operational problem.

Sources and limitations

The primary sources are MiCA on EUR-Lex and Delegated Regulation EU 2025/294. The latter also regulates analysis of complaints data. The field arrangement described here is an operational proposal rather than an official format imposed by these pages. Attachments containing personal information also require assessment of the applicable data protection framework.

An orderly register alone does not demonstrate that an investigation or decision is correct. Expertise and substantive review remain necessary. To compare this approach with a system connecting registers and documents to activities, you can view Vigenza.