SME Credit Line Tokenization

Deal context

A credit fund engaged Asset Haus to tokenize a receivables-backed SME credit facility. The structure: a BVI special purpose vehicle issuing tokenized debt notes (ERC-1400) on Ethereum to professional and institutional investors globally, with distributions triggered by repayment events on the underlying receivables. The structuring and launch engagement ran eight weeks, covering SPV formation, note documentation, platform deployment, and go-live of the investor portal with secondary transfer controls.

BVI SPV (Issuer)
    ↓
SME Receivables Pool (Collateral)
    ↓
Tokenized Debt Notes (ERC-1400 on Ethereum)
    ↓
├── Primary Distribution (professional / institutional investors)
└── Secondary Transfers (whitelist-based, compliant)

Asset Haus provided the tokenization infrastructure and structuring support. The fund remained the credit manager, the SPV was the issuer of record, and legal documentation was prepared in coordination with qualified counsel — Asset Haus does not act as lender, broker, or custodian in this pattern.

The structuring problem

Receivables-backed SME credit is one of the harder private-credit assets to tokenize, for three reasons that recur in every deal of this class.

Revolving collateral. Unlike a term loan secured by a fixed asset, a receivables pool turns over continuously: invoices are collected and new receivables are originated into the pool. The token cannot point to a static asset list; it must represent a claim on a changing pool, so eligibility criteria, concentration limits, and covenants live in the collateral documentation rather than in the token itself.

Collection timing. Cash arrives when underlying obligors pay, not on a fixed coupon calendar. A distribution mechanism keyed to calendar dates either traps collected cash or promises payments the pool has not yet generated. This facility instead distributes on repayment events, driven by actual collections.

Credit assessment. SME borrowers rarely carry external ratings, so investors need a documented, repeatable methodology for how receivables are evaluated and admitted to the pool. Without one, the "receivables-backed" label carries little diligence weight.

On top of this, the client wanted lock-ups meaningfully shorter than traditional private credit and a compliant path to secondary transfers — both cutting against private debt's default hold-to-maturity design.

Jurisdiction and compliance constraints

The BVI SPV is a standard pattern for pooling a globally distributed professional-investor base into a single issuing entity. As general practice — always confirmed with qualified counsel — the pattern provides a bankruptcy-remote issuer that ring-fences the receivables pool from the credit manager, is familiar to institutional counsel and administrators, and supports note issuance to non-retail investors across multiple jurisdictions.

Two compliance gates shaped the token design:

• Eligibility. Only verified professional and institutional investors are admitted. Eligibility is checked at onboarding and enforced continuously through the transfer whitelist, not just at subscription.
• Transfer controls. ERC-1400 was used because transfer restrictions operate at the token-contract level: a transfer settles only between wallets that pass the eligibility whitelist and the rules in the secondary transfer protocol. That is what makes secondary market access via compliant transfer controls possible without ever opening the notes to free transferability.

Platform modules deployed

Each module in the Asset Haus stack had a specific job in this deal type:

• Token Factory — configured the ERC-1400 debt notes on Ethereum, with transfer restrictions and noteholder rights encoded at issuance.
• KYC/KYB — identity and entity verification plus professional-investor eligibility screening, feeding the transfer whitelist.
• Investor Portal — the onboarding and subscription front end, and afterward each noteholder's view of positions and distributions.
• E-Sign — execution of the note purchase agreement and subscription documents inside the portal flow.
• Registry — the legal register of noteholders, reconciled against on-chain token positions.
• Distribution Engine — automated the payment waterfall, releasing distributions when repayment events occurred on the receivables pool.
• Transfer Controls (Secondary) — the whitelist-based approval layer governing transfers between eligible investors under the secondary transfer protocol.

Deliverables around the platform included BVI SPV formation, the note purchase agreement, collateral documentation, the credit assessment methodology, the secondary transfer protocol, and the payment waterfall automation itself.

Investor workflow

The end-to-end investor path follows a repeatable sequence:

1. Verification. Investors complete KYC (individuals) or KYB (entities) and are screened against professional and institutional eligibility criteria. Approved investors are added to the transfer whitelist.
2. Subscription. Through the Investor Portal, investors review and execute the note purchase agreement and subscription documents via E-Sign.
3. Note issuance. On settlement of subscription funds to the SPV, notes are minted to the investor's whitelisted wallet and the register is updated in the same step.
4. Distributions. As receivables repay, the Distribution Engine runs the waterfall and pays noteholders on repayment events, recording each distribution against the register.
5. Secondary transfers. A noteholder seeking to exit before maturity can transfer notes to another eligible, whitelisted investor under the secondary transfer protocol; anything outside those rules fails at the contract level.

Registry, settlement, and reporting logic

The register — not the blockchain — is the legal source of truth for who holds the notes. On-chain token positions mirror the register, and the two are reconciled continuously so that every mint, transfer, and redemption has a matching register entry.

The payment waterfall automation sits between collections and distributions: as receivables are collected into the SPV, the engine applies the documented waterfall — priority items first, then pro-rata distributions to noteholders — and records each event.

On reporting: noteholders see position statements and distribution history in the portal; the issuer and its auditors can pull register extracts, distribution logs, and reconciliation reports matching on-chain movements to register entries.

Outcome and current status

The engagement completed in eight weeks (Q4 2024), with the following stated results:

• Lock-up periods significantly reduced versus traditional private credit structures.
• Secondary market access enabled via compliant transfer controls — transferability among eligible investors, not a promise of a liquid market.
• A proprietary SME credit assessment framework documented as part of the facility.

Deal size, investor count, and average ticket remain undisclosed.

What operators can reuse from this pattern

1. Separate the legal claim from the collateral mechanics. Tokenize the note issued by the SPV and let pool eligibility and covenants live in the collateral documentation. That keeps a revolving pool workable without re-issuing tokens as the collateral turns over.
2. Distribute on events, not dates. For collection-driven assets, tie the distribution engine to repayment events. Investor cash flow then matches actual pool performance instead of a calendar the pool cannot guarantee.
3. Treat transfer controls as the liquidity feature. What a compliant structure can honestly offer is transferability among eligible investors under a documented protocol — that alone shortens effective lock-ups versus hold-to-maturity funds. It should never be structured or marketed as a liquid public market.
4. Document the credit methodology as a first-class deliverable. A written, repeatable SME assessment framework is what lets a global professional-investor base diligence a pool of unrated borrowers.
5. Keep the register authoritative. Let on-chain positions mirror the legal register, reconcile continuously, and hand auditors the reconciliation — that is what makes the structure defensible.

Related resources

• Tokenized credit: the complete guide
• How to tokenize a loan portfolio
• Invoice and trade finance tokenization
• Tokenized notes: structuring guide
• Private credit tokenization use case