MiFID II: the seven questions an auditor asks first
Before asking for recordings, the regulator tests whether you can find them, evidence them and retain them. A guide to the questions that decide…
Read article →Most organisations never decided, at any one moment, to record voice in one system, chat in another and email in a third. They got there by accumulation: each channel brought its own tool, each vendor its own repository, each project its own urgency. The result is a fragmented archive, and it is precisely at the joins between fragments, at the seams, that compliance fails. The risk is not in each system on its own; it is in the space between them.
Why does a single conversation live in three systems?
An interaction with a client rarely respects the boundaries of the systems that capture it. It starts on a call, continues in a Teams message, gets confirmed by email. To the client and to the regulator, that is one conversation. To an architecture of silos, it is three disconnected records, stored in three places, with three clocks and three retention policies. Reconstructing the full sequence takes manual correlation work that, under audit pressure, is slow and fragile.
Where does compliance fail?
The failure points of a fragmented archive are predictable:
- Search that cannot be crossed: there is no way to look for every interaction with a client within a date range, because each system answers only for its own part.
- Inconsistent retention: email is deleted at one rhythm, chat at another, voice at a third, and the composite interaction loses its integrity.
- Misaligned audit trails: each system logs access in its own way, or does not log it at all, making a single view of who saw what impossible.
- Silent gaps: when a new channel appears and nobody connects it to the archive, the interactions on that channel are simply never captured.
An auditor does not assess your best system. They assess the weakest one, and in a fragmented archive the weakest link is almost always the join between two systems that nobody owns.
What changes with a single archive?
The answer is not to record more; it is to record into a single governed destination. Multi-channel capture means voice, chat and email converge into the same archive, with the same metadata model, the same access policy and the same audit trail. Integration with Microsoft Teams captures the interactions that today live in day-to-day collaboration; email gateways bring the relevant correspondence into the same repository. The originating channel becomes an attribute of the interaction, not the boundary of the system holding it.
Unification does not require replacing every communication tool at once. It requires that all of them deposit into a single retention archive, which is where governance happens. Telephony, collaboration and mail platforms carry on being what they are; what changes is the common destination where their interactions are preserved, indexed and retained. That is the difference between integrating and consolidating: integrating connects systems that remain separate; consolidating puts all the evidence in one place.
What does cross-channel search make possible?
When everything lives in the same archive, indexed by the same metadata, a business question has a single answer. «Show me every interaction with this client, on any channel, this quarter» stops being a project and becomes a search. It is that capability, searching across channels by client, by employee, by date, by interaction type, that separates a compliance archive from a set of recorders bolted together. Without it, compliance depends on the memory of whoever knows where to look.
Do fewer systems mean less risk?
Consolidating is not merely an operational convenience. Every additional system is one more integration to maintain, one more provider to assess under DORA, one more retention policy to align with MiFID II and the GDPR, one more audit trail to audit. Reducing three archives to one reduces, in the same proportion, the risk surface the compliance team has to watch. Add to that the quiet operational cost of maintaining separate skills for each platform, of reconciling reports that do not speak the same language, and of explaining to an auditor why the same interaction shows up in three different shapes. A compliance project becomes achievable when there is one place where the answer lives, rather than three places where it might be missing.
Published by the uPlayback team, a Grupês product. Three decades of experience in compliance recording.
