A close deadline is not a reason to admit an investor. Who decides, on what evidence, and how the case returns to the standard process.
Consider, for illustration, a tokenization project for a residential building. The subscription window closes on Friday. One investor, a company, has completed almost everything: the transfer has arrived and the identity of its legal representative has been verified. However, a document needed to complete the verification of the beneficial owners is missing. The owner of the property, who has followed the project for months, asks for the investor to be admitted anyway: the documents will arrive on Monday.
The case is invented, but anyone who has run a fundraising will recognise it. It is not about what the token represents or about the legal framework of the offer, which I treat here as already settled. It concerns a more practical question: what should happen when an access process, designed for the standard case, meets an exception.
In the illustrative case, I would not authorise admission on the strength of a promise to complete the documents on Monday. First, it must be established whether the applicable rules allow the process to go ahead with verification still incomplete. Only then do three questions become decisive: who can authorise the exception, on what evidence and within what operational limits.
Why the Exception Tests the Project
An access workflow describes the standard path: documents, checks, approval, enablement. The exception shows whether rules also exist for handling whatever falls outside that path.
Where those rules are missing, the pressure to decide remains. The solution then risks becoming informal: a message, a phone call, a manual enablement. The problem is not only the decision itself, but the ability to reconstruct afterwards who took it, on what basis and under what conditions.
The three questions help to distinguish a governed procedure from an improvised decision.
Who Can Decide
The first concerns the decision-maker.
The property owner has a legitimate interest in closing the raise, but that interest does not automatically give them the power to decide on the investor’s access. Nor does the mere technical ability to enable a digital address.
The party responsible for the checks depends on the structure of the transaction, on the activities actually carried out and on the applicable rules. The qualification of the instrument and the regime of the services involved are important elements, but they do not replace the identification of the anti-money laundering obligations and of the parties required to meet them.
The project should identify these responsibilities before an exception arises. The workflow should also distinguish between whoever has the authority to approve a decision and whoever can carry it out technically.
In our example, a request from the property owner would not be sufficient to proceed.
On What Evidence
The second question concerns the elements that can support a decision.
European law establishes as a general rule that checks on the identity of the customer and of the beneficial owner precede the establishment of the relationship or the execution of the transaction. Directive (EU) 2015/849 allows for certain limited possibilities of completing the checks at a later stage, the applicability of which also depends on national law.
There is therefore no exception that can be used automatically in any European project. Before providing for one in the workflow, the responsible party must have verified whether it is permitted in the specific case and on what conditions.
The regulatory framework is also set to change: Regulation (EU) 2024/1624 will become generally applicable from 10 July 2027.
For this reason, in Friday’s case, a close deadline would not be a sufficient justification. It would be necessary to know which check is incomplete, why it has not been concluded, what risk assessment has been made, who is competent to decide and which conditions apply.
This information must be documented and linked to the decision. An informal message may form part of the evidence, but it should not replace the authorisation process.
How the Case Returns to the Process
The third question concerns what happens after the decision.
Where the rules allow some checks to be completed at a later stage, the workflow must define exactly which activities are permitted in the meantime and which must remain blocked.
It cannot be assumed that a subscription, the allocation of tokens or a later transfer are permitted merely because the system makes it possible to restrict certain functions.
Any temporary condition must have an owner, a deadline and rules that determine how it is closed. The system must also retain the evidence of the checks completed and of the decisions taken.
The opposite path must exist as well. Article 14 of Directive (EU) 2015/849 provides that, where the obliged entity is unable to meet certain customer due diligence requirements, it must not establish the relationship or carry out the transaction and must terminate a relationship already begun, also considering whether to make a report to the financial intelligence unit.
Operationally, this means providing for how to block the transaction, how to manage a position that may already be open and how to treat the funds received in accordance with the applicable procedures and obligations. It cannot be assumed that a refund is always immediate or automatically permitted.
An exception is properly governed when the decision, the evidence and the closure path are defined before the case arises.
Without these conditions, an exception left open risks becoming a second procedure, never formally approved.
What This Reasoning Does Not Establish
It does not establish that a conditional admission is possible in a given project. The answer depends on the applicable rules, on the risk assessment and on the procedures of the responsible party.
In many cases, the correct decision will be not to proceed. In our example, I would not authorise admission if even one of the necessary legal and operational conditions were missing.
Nor does it establish how many exceptions are acceptable. It does suggest recording and analysing them: if they become frequent, it may be a sign that the standard process has weaknesses and needs to be revised, rather than bypassed case by case.
The role of the technology infrastructure is not to decide which derogations are admissible. It is to apply the rules defined by the competent parties, prevent unauthorised operations and retain the evidence needed to reconstruct what happened.
For this reason, Friday’s decision matters less than the one that precedes it: having designed a system capable of handling non-standard situations without losing control of responsibilities.
How would your team evaluate an exception of this kind?


