SRS vs CDP vs Cash: How to Hold Your S-REITs in Singapore

Originally published on Finance Pulse Research. This Dev.to mirror is provided for the developer/data-analytics community; the full interactive analysis with live data tables lives on the original.

Introduction to the Metric

One practical question keeps surfacing in Singapore REIT analysis: where exactly are the units held? The data point that frames the issue is simple but revealing. Singapore’s listed REIT universe in this dataset contains 30 names, with an average yield of 6.321, yet only 2 named platforms here support CDP access while 4 are listed as custodian-only. That operational split matters because holding route affects tax wrapper use, legal custody structure, and how analysts classify access pathways for income-focused screens.

This article explains the holding-method framework behind the keyword srs cdp reit singapore. In plain terms, the metric is not a return factor like yield or a balance-sheet ratio like NAV premium or discount. Instead, it is a market-access classification method used to identify whether an S-REIT position is held through SRS, through a CDP-linked brokerage route, or through a custodian arrangement funded with cash. That distinction matters in reference work, platform comparisons, and methodology notes attached to tools such as broker comparisons and research methodology.

Who uses this framework? Primarily analysts, market-data publishers, and self-directed market participants comparing account infrastructure across Singapore. It also appears in operational due diligence when readers want to know whether a broker supports direct CDP settlement or keeps positions under nominee custody. As an evergreen reference, this explainer focuses on definitions, classification logic, and data handling rather than any portfolio stance.

Formula and Definition

Unlike dividend yield, there is no single arithmetic identity that turns market prices into a holding route. The methodology here uses a classification formula: determine the funding wrapper first, then the custody path, then the operational label. This is the clearest way to separate SRS-funded holdings from ordinary cash-funded positions while still distinguishing direct CDP access from custodian-only models.

Holding Route =
  if Funding Source = SRS -> "SRS"
  else if Broker in CDP Supported List -> "Cash via CDP"
  else if Broker in Custodian-Only List -> "Cash via Custodian"
  else -> "not yet covered"

Each variable has a specific role.

Funding Source identifies whether the position is purchased using Supplementary Retirement Scheme funds or regular cash. In this framework, SRS sits above custody detail because an SRS account is a separate tax-advantaged wrapper, so the first branch answers a different question from ordinary brokerage settlement.

Broker in CDP Supported List checks whether the named platform supports Central Depository settlement in the data provided. The dataset lists Saxo Markets and FSMOne under CDP-supported routes.

Broker in Custodian-Only List checks whether the platform operates through nominee or custodian custody in the provided universe. The data lists Tiger Brokers, Moomoo, Webull, and IBKR in that category.

not yet covered is the fallback label when a platform or pathway is absent from the supplied database. That prevents guesswork and keeps the classification auditable.

Why use this structure rather than alternatives? Because the analytical question is categorical, not continuous. A mathematical score would imply degrees of directness, while the practical distinction is binary at each branch: SRS or not, CDP-supported or custodian-only. This method also fits well with platform directories such as Singapore broker coverage and process notes in our methodology center, where clear labels are easier to maintain than subjective rankings.

There is another reason. The S-REIT universe itself is diverse: 8 retail names, 6 office, 5 hospitality, 4 industrial, 3 logistics, 2 diversified, 1 data center, and 1 healthcare. A custody framework needs to remain stable across all these sub-sectors. By using a route-based formula instead of a security-specific one, the classification stays consistent whether the example is Singapore-focused, China-focused, Europe-focused, US-focused, or pan-Asian.

Worked Example 1 — Positive Case

The first example uses Sasseur REIT, ticker CRPU.SI. This case is helpful because the trust combines a high headline payout figure with a straightforward holding-route classification exercise. The REIT sits in the retail sub-sector, has a China-focused geographic profile, carries a current yield of 9.23, and shows a 5-year average yield of 9.212. Its NAV premium or discount stands at -16.67, meaning the market price is below reported net asset value by 16.67 in percentage terms. The Distribution Safety Score is 0, on a 0-100 scale where higher indicates stronger payout coverage in Finance Pulse Research methodology. The name is not an aristocrat, and its distribution growth over 5 years is -4.316.

Now apply the holding-route formula step by step.

Step 1 asks whether the funding source is SRS. If CRPU.SI is held through an SRS account, the label becomes SRS immediately. The trust’s yield, discount, and safety profile do not alter that branch because the classification concerns account wrapper first.

Step 2 applies only when the purchase is made with regular cash. If the cash-funded trade goes through Saxo Markets or FSMOne, the route becomes Cash via CDP because those are the 2 platforms named in the CDP-supported list.

Step 3 applies when the cash-funded trade goes through Tiger Brokers, Moomoo, Webull, or IBKR. In that case, the label becomes Cash via Custodian because those 4 platforms are identified as custodian-only in the dataset.

The worked result is therefore positive in a methodological sense: CRPU.SI is fully classifiable under all branches using only the supplied data. Analysts can tag the same REIT under different operational buckets without changing the underlying security data.

That distinction matters when interpreting metrics. A yield figure of 9.23 may draw attention, but the holding route remains independent of the income profile. Likewise, a -16.67 NAV discount does not convert a custodian-held unit into a CDP-held unit. In other words, security analytics and custody analytics intersect in workflow, not in formula design.

Beyond the headline numbers, CRPU.SI also shows how route labels coexist with longitudinal context. Its 9 years of continuous distributions and negative 5-year distribution growth of -4.316 tell analysts something about payout history, yet neither figure changes the output of the holding classification. This separation is exactly why the methodology remains useful as reference infrastructure rather than as a valuation shortcut.

Worked Example 2 — Contrasting Case

The second example uses ARA Hospitality Trust, ticker A7RU.SI, and the contrast is sharp. The trust belongs to the hospitality sub-sector and is US-focused. Its current yield is 7.73, compared with a 5-year average yield of 8.142. The reported NAV premium or discount is 286.36, which is an extreme premium. The dataset explicitly flags this with an anomaly note: an extreme NAV premium of 286.4% may reflect stale NAV data, illiquid market, or structural factors. That annotation cannot be ignored in any responsible methodology discussion.

The Distribution Safety Score again reads 0 on the same 0-100 scale, the aristocrat flag is false, and 5-year distribution growth is -3.427. The trust also records 19 continuous distribution years in the dataset.

Here is the step-by-step route calculation.

If the funding source is SRS, the output is SRS. Nothing in the anomaly note overrides that branch. The custody label is not inferred from premium or discount behavior.

If the trade is funded with cash and routed through a CDP-supported broker, the output is Cash via CDP. In this dataset that means Saxo Markets or FSMOne.

If the trade is funded with cash and routed through Tiger Brokers, Moomoo, Webull, or IBKR, the output is Cash via Custodian.

So why is this a contrasting case? Because the underlying REIT metrics look far less ordinary than the route label. Example 1 showed a high-yield retail trust trading at a discount. Example 2 shows a hospitality trust with an extreme 286.36 NAV premium anomaly and a lower yield than the first example. Yet the holding-route formula behaves identically. That is not a flaw. It is the point. The classification is insulated from noisy valuation fields, including values that may be distorted by stale marks or thin liquidity.

A different pattern emerges when the anomaly is interpreted analytically. A route methodology that depended on market valuation could become unstable exactly when data quality deteriorates. By contrast, this framework uses platform support status and funding source, both of which are structurally easier to verify. That makes the methodology more robust for evergreen pages such as broker setup references and classification notes.

This example also highlights a common misuse pattern: readers may try to infer account preference from an unusually large premium, discount, or yield gap. The data does not support that leap. A7RU.SI’s extreme NAV field is a security-level anomaly; the holding route remains an account-level classification.

Worked Example 3 — Edge Case

The third example uses Sabana Industrial REIT, ticker M1GU.SI. This is a useful edge case because it sits between stronger and weaker readings rather than at an obvious extreme. The trust is Singapore-focused and belongs to the industrial sub-sector. Its current yield is 7.63, above its 5-year average yield of 6.493. The NAV premium or discount is -8.92, a milder discount than the deeper dislocations seen elsewhere in the sample. Its Distribution Safety Score is 25, on the 0-100 scale where higher indicates stronger payout coverage. That is still low in absolute terms, but it is distinct from the zero-score cases above. The trust is not an aristocrat, shows 16 continuous distribution years, and records -3.866 distribution growth over 5 years.

Apply the formula and the edge behavior becomes clear.

An SRS-funded purchase is labeled SRS.

A cash-funded purchase through Saxo Markets or FSMOne is labeled Cash via CDP.

A cash-funded purchase through Tiger Brokers, Moomoo, Webull, or IBKR is labeled Cash via Custodian.

What makes this an edge case is not a missing output, but the temptation to overread moderate fundamentals into account treatment. M1GU.SI has neither the deepest discount nor the most distorted premium in the examples, and its safety score of 25 creates a middle ground between clear stress and stronger coverage. The methodology still returns the same route categories. That demonstrates how the framework handles borderline operating profiles without introducing discretionary overrides.

The data shifts when viewed through this lens: account classification stays stable even when security-level indicators move from weak to merely less weak. For analysts building screeners, that consistency is more useful than a subjective blended score.

Data Sources

The holding-route methodology depends on two source groups in the supplied database: the S-REIT context block and the freshness block. Both matter, but they play different roles.

First, the S-REIT context defines the market universe in which the methodology is explained. It states that there are 30 Singapore REITs in scope and that the average yield across that universe is 6.321. It also records 1 aristocrat count, alongside the sub-sector distribution: retail 8, office 6, hospitality 5, industrial 4, logistics 3, diversified 2, data center 1, and healthcare 1. These figures do not decide whether a route is SRS, CDP, or custodian-held. Instead, they establish the coverage context for the explainer and show that the framework applies across a broad listed property market rather than a narrow niche.

Second, the same context block supplies the named popular examples used to illustrate the methodology. All 8 entries contribute to coverage notes even though only the first 3 are used as formal worked examples. The list includes CRPU.SI Sasseur REIT, A7RU.SI ARA Hospitality Trust, M1GU.SI Sabana Industrial REIT, A17U.SI CapitaLand Ascendas REIT, UD1U.SI IREIT Global, C38U.SI CapitaLand Integrated Commercial Trust, HMN.SI CapitaLand Ascott Trust, and P40U.SI Starhill Global REIT. These examples span retail, hospitality, industrial, and office segments, with geography labels including China-focused, US-focused, Singapore-focused, Europe-focused, and pan-Asian. That spread matters because it demonstrates portability of the route method across different operating exposures.

Third, the context block identifies the platform source lists that directly feed the formula. CDP-supported names are Saxo Markets and FSMOne. Custodian-only names are Tiger Brokers, Moomoo, Webull, and IBKR. This is the core classification input. When a platform appears in one of these lists, the methodology maps the holding route accordingly. When a platform is absent, the output becomes not yet covered.

Fourth, the freshness block provides update timing. The real yield snapshot date is 2026-06-07, the REIT snapshot date is 2026-06-06, and the database fetched_at stamp is 2026-06-08. These dates are essential because custody support notes and REIT metrics can change over time. A methodology page is evergreen, but its examples still require timestamped sourcing. Readers can cross-check implementation details in our methods page and supporting platform references in the broker directory.

The table below consolidates the source inputs used in this explainer.

Limitations and Caveats

This methodology is intentionally narrow. It answers where the holding route sits in structural terms, not whether a given REIT looks expensive, cheap, stable, or volatile. That matters because the S-REIT examples span a wide range of operating profiles.

Zooming into the individual entries, several names highlight what the route metric does not capture. CapitaLand Ascendas REIT, A17U.SI, records a current yield of 7.59, a 5-year average yield of 5.658, a 10.02 NAV premium, a Distribution Safety Score of 25, 22 continuous distribution years, and 12.875 distribution growth over 5 years. Those numbers describe a very different operating picture from IREIT Global, UD1U.SI, which shows 7.23 current yield, 13.717 average yield over 5 years, a -55.09 NAV discount, a safety score of 0, 12 continuous distribution years, and -13.689 growth over 5 years. UD1U.SI also carries an anomaly note for its extreme -55.1% discount, flagged as potentially affected by stale NAV data, illiquid market, or structural factors. Yet the holding-route method treats both securities the same way at the account-classification level.

That separation creates both strength and limitation. The strength is consistency. The limitation is that route labels cannot substitute for fundamental analysis. A CDP-held unit is not automatically safer than a custodian-held unit, and an SRS-held unit does not inherit a different REIT-level risk profile simply because of account wrapper.

Stepping back to the aggregate level, trailing data introduces another caveat. The dataset timestamps show 2026-06-07 for real yield fields, 2026-06-06 for the REIT snapshot, and 2026-06-08 for fetch timing. Those dates are recent, but still historical. If platform support terms or account features change after that point, the methodology output for a newly updated broker may become stale until the source list is refreshed.

The picture changes at the sub-sector level as well. CapitaLand Integrated Commercial Trust, C38U.SI, is a Singapore-focused retail trust with a 6.85 yield, 4.439 average yield over 5 years, 6.03 NAV premium, safety score 25, 19 continuous payout years, and -3.312 distribution growth. CapitaLand Ascott Trust, HMN.SI, sits in hospitality with a 6.82 yield, 6.104 5-year average yield, a -23.37 NAV discount, safety score 25, 19 continuous payout years, and 7.345 distribution growth. Starhill Global REIT, P40U.SI, another retail name, shows 6.73 yield, 6.838 5-year average yield, -26.1 NAV discount, safety score 25, 19 continuous payout years, and -1.955 growth. These differences illustrate why the route metric must not be used as a shortcut for comparing fundamentals across sectors.

Another caveat is data coverage. The methodology names only 2 CDP-supported platforms and 4 custodian-only platforms. If a reader asks about a broker outside these lists, the correct output is not yet covered or data not available. Expanding beyond the supplied list without source backing would break the classification discipline.

Finally, currency effects sit mostly outside the holding-route formula, but they still matter in interpretation because several examples have non-Singapore operating exposures: China-focused, Europe-focused, US-focused, and pan-Asian. Account route and underlying cash-flow geography are different dimensions. The method handles the former, not the latter.

How Finance Pulse Applies This Metric

Switching from security metrics to implementation, Finance Pulse uses this classification as a tagging layer inside its Singapore REIT coverage. The route label helps organize educational pages, broker comparison tables, and operational notes attached to REIT datasets. It is especially useful when readers move between broker pages, methodology documentation, and broader S-REIT screens that already display yield, NAV premium or discount, and distribution-safety fields.

In practice, the workflow is simple. The platform name is matched against the CDP-supported list or the custodian-only list. If the funding source is SRS, the security is tagged under the SRS route. If neither condition is satisfied, the system returns not yet covered. This design keeps the classification auditable and prevents unsupported assumptions.

Update timing follows the supplied freshness stamps in this dataset: real-yield snapshots dated 2026-06-07, REIT snapshots dated 2026-06-06, and data fetched at 2026-06-08. Those dates anchor the reference state of the article. Readers looking for the process logic behind those updates can review the methodology explainer hub and related platform comparison resources.

Related Methodologies

Cross-referencing with adjacent frameworks helps place this page in context. The closest companion is the broader methodology library, which explains how Finance Pulse handles derived fields such as distribution safety and NAV premium or discount. For operational setup questions, the broker directory complements this article by mapping platform characteristics to account access routes.

Viewed through a five-year lens, security analytics such as average yield, distribution growth, and payout continuity answer a different question from custody route. This page covers the holding structure. Other methodology references cover the market metrics layered on top of that structure.

Data Sources and Methodology

Finance Pulse Research compiled this explainer from the supplied Singapore REIT context, platform support lists, and dataset freshness stamps. The S-REIT universe in scope includes 30 names with an average yield of 6.321 and 1 aristocrat in the current database snapshot. Sub-sector counts are retail 8, office 6, hospitality 5, industrial 4, logistics 3, diversified 2, data center 1, and healthcare 1. Worked examples were drawn from the named entries in the dataset and used strictly for methodological illustration.

The route logic is categorical rather than predictive. It assigns SRS when the funding source is SRS, Cash via CDP when a cash-funded position uses one of the CDP-supported platforms listed in the database, and Cash via Custodian when the platform appears in the custodian-only list. Platforms not included in the supplied lists are marked not yet covered.

Anomaly annotations were preserved exactly where present. A7RU.SI carries an extreme NAV premium note tied to 286.36, and UD1U.SI carries an extreme NAV discount note tied to -55.09. Those flags may reflect stale NAV data, illiquid market, or structural factors, so the figures were discussed with caution rather than presented as straightforward valuation signals.

Freshness matters in any reference framework. In this dataset, the real yield snapshot date is 2026-06-07, the REIT snapshot date is 2026-06-06, and the fetch timestamp is 2026-06-08. Readers can use those dates to assess whether a custody-support classification or supporting REIT metric may require a fresh check.

This analysis is based on publicly available market data and derived
metrics calculated by Finance Pulse Research. Finance Pulse Research
is a data analytics publisher. Content is for informational and
educational purposes only. Nothing herein constitutes investment
advice, a recommendation to buy or sell any security, or an offer of
any kind. Data as of 2026-06-08.

Finance Pulse Research builds open data analytics for Asian dividend markets — real yields, REIT NAV discounts, and foreign-flow signals across 11 countries. Stack: FastAPI + Next.js + Postgres + Celery, with data from yfinance, FRED, World Bank, and direct exchange feeds. More at finance-pulse24.com.