A payment waterfall determines how available cash is divided when several parties have claims on the same assets. Tokenisation can execute that sequence, expose its inputs and record each distribution. It does not decide who should rank first, which receipts belong to investors or what happens when the cash is insufficient.
For a tokenised credit pool, the central diligence question is therefore not how often a distribution runs. It is whether the distribution matches the governing rights under normal collections, shortfalls and enforcement. That is a narrower question than the general investment case for private credit onchain, and often a more revealing one.
Start before the distribution contract
The waterfall begins with the definition of available funds. Borrower payments, asset sale proceeds, recoveries, interest on reserves and new investor subscriptions should not be treated as interchangeable cash. Their permitted uses may differ. A receipt can also include money owed to a tax authority, a servicing party or another beneficial owner.
The first reconciliation connects borrower or obligor records to the collection account. The next connects that account to cash released into the distribution mechanism. If a service provider reports a repayment before the bank confirms it, the ledger can show an economically plausible collection that cannot yet fund a payment. Automating the next steps makes the discrepancy travel faster.
A useful design keeps collected, cleared and distributable amounts distinct. Those distinctions also clarify responsibility: the servicer attests to what was collected, the account controller confirms what can move, and the calculation agent determines what the documents permit to be distributed. One entity may perform several roles, but the assertions remain different.
Priority is a rule, not a token label
A simple waterfall might pay permitted senior expenses, replenish a reserve, pay senior interest, amortise senior principal and distribute the residual to junior holders. Another structure might fund reserves later or pay principal only after a trigger. Neither sequence can be inferred from a token called senior.
Centrifuge's programmable vault architecture describes custom allocation logic, including senior and junior waterfalls. The relevant point is configurability. The infrastructure can implement different economic structures, so a buyer has to inspect the particular pool's terms and deployed configuration rather than treating platform membership as a standardised priority promise.
Payment priority and loss allocation also need separate reading. A junior position may absorb losses first without receiving cash last in every ordinary distribution. Reserve replenishment, fees, interest deferral and principal tests can change the result. A capital structure diagram is not a cash-flow model.
Follow $900,000 through a short period
Consider a hypothetical pool receiving $900,000 of distributable collections. Its documents require $50,000 of permitted expenses, $100,000 of reserve replenishment, $300,000 of senior interest and up to $600,000 of scheduled senior principal before a junior residual. Assume those priorities apply in that order, with no other claims or taxes.
Expenses leave $850,000. Replenishing the reserve leaves $750,000, and senior interest leaves $450,000. The entire remaining $450,000 goes to senior principal. The scheduled principal amount is therefore short by $150,000 and the junior class receives nothing. That is a payment result, rather than proof of a $150,000 credit loss.
The unpaid principal could remain due, carry forward under an amortisation schedule or trigger another contractual consequence. If a calculation engine reports it as defaulted principal without checking the terms, it changes the meaning of the shortfall. If it reports only the cash paid, it hides the outstanding obligation. Both the distribution and the remaining claim need records.
Suppose the reserve is already fully funded. Removing the $100,000 replenishment changes the allocation to principal even though borrower collections are identical. A junior payment still does not arise under these assumptions. This small variation shows why modelling only collection totals misses the variables that drive payment priority.
Triggers change the sequence
A waterfall may behave differently after deterioration. A covenant breach can trap cash, accelerate repayment of a senior class or stop residual distributions. These are state changes in the economic rules. They need a defined measurement date, data source, threshold and decision authority.
An asset coverage test, for example, can depend on valuations rather than cleared cash. A stale valuation may leave distributions flowing after collateral has weakened. A disputed valuation may freeze otherwise available payments. The mechanism needs a route for corrections and a clear statement of whether a corrected test changes future payments, creates a clawback claim or requires another remedy.
The governing documents should establish what happens when the data needed for a test is missing. Assuming the previous value is not a neutral choice. It favours whichever claim benefits from the previous state. A transparent default rule is easier to assess than an undocumented intervention by an operator.
Accrual is not a funded coupon
A token can display accumulating interest without a corresponding amount of available cash. The accrual is a calculation of a claim. A distribution is a transfer made under the waterfall. An investor should be able to reconcile both and understand whether unpaid interest compounds, remains simple, ranks alongside later interest or falls behind other claims.
The same caution applies to principal. Token supply may represent original principal, current principal, a participation percentage or a share of net asset value. Burning tokens on repayment can be appropriate for one design and misleading for another. The registry must connect units outstanding to economic claims after each distribution.
That is where tokenised securities entitlements becomes a practical concern. The holder at the record point, the account receiving cash and the party bearing withholding may not be described by a single wallet balance. Transferring the token around a distribution date needs a defined entitlement rule.
Execution can succeed while a payment fails
A distribution transaction can correctly calculate all amounts while one recipient is blocked, unsupported or unable to receive the settlement asset. The system needs a treatment for that unpaid entitlement. It might hold funds for collection or use an authorised alternative route. Moving the amount down the waterfall simply because a recipient could not receive it would require a contractual basis.
The CPMI-IOSCO principles for financial market infrastructures distinguish clear legal arrangements and settlement risks as separate concerns. They are not a product certification for tokenised pools. They provide a useful discipline: technical completion and the legal discharge of an obligation must be analysed together.
Ask to reproduce one distribution using the collection file, reserve balance, class balances and governing priorities. Then change one input: a missing repayment, an unpaid fee or a breached test. The result should explain each amount retained, each amount paid and every claim carried forward. That exercise shows whether the waterfall is a maintained financial mechanism or merely an attractive payout screen.