An application can arrive before its supporting evidence is complete, and cash can arrive before an allocation is approved. A future tokenised-asset service needs to represent those states accurately. The operating decision is when each obligation begins and which evidence permits the investor record to advance, without using a reassuring interface label to collapse unfinished work.
Define the order lifecycle
The servicing specification should distinguish received, incomplete, under review, accepted, allocated and settled as appropriate to the actual product. Each status needs a responsible party and an event that changes it. BIS's tokenisation analysis highlights the relationship between arrangements and their underlying functions. The practical consequence is that putting an application on a ledger does not itself answer who accepted it or under which terms. A hypothetical applicant receiving a confirmation email should understand whether that email acknowledges delivery or confirms a binding subscription, with the governing documents and the service record using compatible language.
Set the cutoff and exception rules
The product's actual terms should determine the relevant deadlines, pricing basis and treatment of late or incomplete instructions. Qualified advisers need to establish the appropriate structure. Operations should then be able to apply it consistently. A hypothetical payment arriving after a deadline should follow an agreed route rather than depend on a support agent's preference. The record needs the time, document version and reason for any authorised exception. Investors should be able to understand the consequences of a missing requirement before sending money or assuming that participation has already been secured through an unfinished application.
Connect acceptance with funds and register controls
The team needs a reconciled account of applications, payments and allocations. A payment reference can help matching while leaving ownership, eligibility or amount unresolved. Issuance should depend on the conditions actually required for the product. CPSS-IOSCO's principles provide useful reference points for legal clarity, operational control and settlement, without establishing that a platform is an FMI. The owner of the servicing process should identify what prevents duplicate allocation and how a rejected or withdrawn instruction affects money already received, with those steps documented before live applications are invited under definitive terms.
Make the investor's evidence durable
A completed subscription record should preserve the accepted terms, relevant approvals, allocation and settlement confirmation. The investor should be able to obtain a clear account without reconstructing scattered messages. Service teams need access to the same authoritative record when answering a query. Holding ALFA does not itself create rights in an asset listed through a separate instrument. These controls concern a potential asset-linked servicing process under its own documents. Readiness would require that process to work through ordinary applications and exceptions, with accurate statuses and accountable decisions from receipt to final investor confirmation.
