Skip to main content
Request a demo
Platform

Asset Lifecycle

Issuance is a day. Servicing is a decade. The arithmetic that goes wrong is the arithmetic that runs every quarter across a register that keeps changing.

One transaction boundaryThree stacked elements — a record, a rule and a ledger posting — enclosed by a single boundary, indicating that all three commit together or not at all.ONE TRANSACTION BOUNDARYRecordwhat is trueRulewhat is permittedPostingwhat it did to the bookscommit together

What it changes

  1. Distributions pay holders of recordThe register is rebuilt from confirmed movements as at the record date, not read from today’s holdings. Paying today’s register for a record date three weeks ago pays the people who bought since and not the ones who sold.
  2. The pool is split exactlyLargest-remainder allocation means the lines sum to precisely what was funded. Rounding each share independently leaves the issuer a few minor units out every cycle, and across a thousand holders and twelve months that is a break nobody can explain.
  3. A split is planned before it is appliedA unit adjustment rewrites every position at once, so it is computed, previewed, hashed into the approval, and re-checked against the register at execution. A ratio that does not divide some holding exactly is refused, naming the holders it fails on.
Ask, agree, then actThree steps. One person requests, a different person approves, and only then does the state change. The approval binds to what was requested, so editing it afterwards invalidates the sign-off.Requestone personApprovea different oneActnow it movesThe approval binds to what was asked.Edit it afterwards and the sign-off is void.
Every irreversible act on this platform takes this shape, whatever the subject of the page: one person asks, a different one agrees, and only then does anything move.
How a distribution is splitA funded pool is divided among holders of record as at the record date using largest-remainder allocation, then withholding is deducted from each holder's gross rather than from the pool.Funded poolone exact amountRegister as atthe record dateRebuilt from confirmedmovements, not today’sbalancesNet to the holderWithheld, from that holder’s grossThe lines sum to exactly what was fundedLargest-remainder allocation, so no minor unit is created or lost. Rounding each slice independently leaves the issuer a few units out every cycle.There is no per-jurisdiction withholding matrix in this build — one rate is entered per run.
Holders of record as at the record date, split by largest remainder so the lines sum exactly, with withholding taken from each holder’s gross rather than off the top of the pool.

What it includes

DistributionsRecord dates, per-holder withholding, exact allocation, per-line payment.
Corporate actionsSplits, consolidations, votes, notices, maturities and wind-downs.
RedemptionsEligibility, pricing at a supplied valuation, burn and payable in one transaction.
WithholdingRecognised as its own liability and remitted with its own reference, so a balance that never clears is visible.

See it against something real.

Bring an instrument you are actually considering. Structuring it is the only way to judge whether the model fits.

Request Enterprise DemoBack to platform
Your instrument, against this modelAn unspecified asset on the left feeds four stages: structure, compliance policy, the offering book and the register. The asset is drawn as an outline because it is the reader's, not the platform's.Your assetwhatever it isStructurePolicyBookRegister