Tri-Party Tokenisation: Why Reconciliation Needs an Exception Process

Shane Ian Murphy in conversation outdoors by a lake

Tokenisation is often described as a way to connect an asset with a programmable digital record. That connection is only credible if the digital record and the authoritative off-chain evidence continue to agree. When they do not, the project needs more than a technical alert: it needs a defined exception process.

I am Shane Ian Murphy, co-founder and partner of Tri-Party Tokenisation. Our educational position is that reconciliation should be designed before issuance, not improvised after a mismatch appears. Tokenisation does not guarantee ownership, financing, liquidity or commercial acceptance, and an on-chain balance cannot correct weak or conflicting source records.

What should be reconciled?

The precise comparison depends on the asset and legal structure. It may include token supply, the quantity or face value described in source documents, custody status, ownership records, transfer restrictions, encumbrances and the version of each supporting document. The goal is not to force every fact onto a blockchain. It is to ensure that important digital claims can be traced to the evidence and authority behind them.

The Bank for International Settlements has described tokenisation as combining records of underlying assets with rules governing their transfer. A recent BIS discussion of the “digital twin” model notes that where the primary ownership record remains off-chain, tokenisation does not remove the reconciliation burden. That is an important boundary: better technology may improve the process without eliminating the need to compare records.

A mismatch must have a named status

Suppose a custodian reports a lower quantity than the amount represented in the latest digital record. The system should not silently overwrite history, and it should not allow business-as-usual transfer merely because the token contract still functions. The exception policy should state who can open the case, what activity is paused, which evidence is required and who has authority to resolve it.

Useful exception categories might include:

  • Timing difference: a valid change has occurred but one record has not yet been updated.
  • Document expiry: a confirmation or valuation has passed its review date.
  • Scope conflict: two sources answer different questions but have been treated as equivalent.
  • Quantity or identity mismatch: the asset description, units or identifiers do not agree.
  • Authority issue: the person submitting or approving an update lacks verified authority.
  • Unresolved legal restriction: a lien, hold or transfer condition requires further review.

A hypothetical example

Consider a hypothetical warehouse holding represented by a fixed number of tokens. A routine review finds that some units were moved to a different location, but the custody confirmation and token metadata still point to the original facility. The appropriate response is not to describe the whole asset as missing. It is to open an exception, verify the transfer, update the relevant evidence and preserve the change history.

If the movement cannot be verified, the exception remains open and the governance policy determines whether transfers, redemptions or new issuance must pause. The decision and supporting evidence should be recorded. A later reviewer needs to understand not only the final result but how the conflict was handled.

Operational discipline matters

The Financial Stability Board’s work on tokenisation identifies operational fragilities among the vulnerabilities that warrant attention. The source does not validate any Tri-Party project; it supports the broader point that operational controls and dependencies matter alongside the technology.

A credible exception process should define thresholds, escalation routes, evidence requirements, decision rights and closure criteria. It should also separate a corrected clerical difference from a material challenge to asset identity, title or custody. Not every mismatch has the same significance.

For Tri-Party Tokenisation, reconciliation is not a promise that every source will always agree. It is the discipline of detecting differences, limiting their consequences and resolving them transparently. The strongest digital record is one that knows what to do when reality does not follow the happy path.

Leave a Reply

Is this your new site? Log in to activate admin features and dismiss this message
Log In