Every figure this model derived for SEI, the value it took, and
the element in the company's own XBRL it was read from — so any of it can be checked
against the filing rather than taken on trust.
As at 2026-06-30.
The figures, and where each came from
This is the part no other screener shows. Each figure below names the XBRL element it
was read from, so it can be checked against the filing itself.
Figure
Value
XBRL tag
As at
capex
1,152,503,000
PaymentsToAcquirePropertyPlantAndEquipment
2026-06-30
cash
824,101,000
CashAndCashEquivalentsAtCarryingValue
2026-06-30
current assets
1,069,091,000
AssetsCurrent
2026-06-30
current liabilities
259,279,000
LiabilitiesCurrent
2026-06-30
equity
901,976,000
StockholdersEquity
2026-06-30
interest expense
15,741,000
InterestPaidNet
2026-06-30
ocf
424,707,000
NetCashProvidedByUsedInOperatingActivities
2026-06-30
revenue
762,184,000
Revenues
2026-06-30
sbc
29,658,000
ShareBasedCompensation
2026-06-30
The ratios
The figures themselves rather than their scores — what somebody looking up
SEI on one particular measure came for.
Ratio
Value
cash operating margin
42.59
current ratio
4.43
current ratio reported
4.12
deferred revenue growth
-13.59
ebit cagr
52.98
ebit yoy
108.55
fcf margin
-95.49
growth cv
0.9
interest cover
11.74
net debt ebitda
2.72
operating margin
24.25
owner earnings margin
-99.38
revenue growth
70.52
revenue growth per share
70.52
roic
8.57
rpo growth
-100.0
rule of 40
94.77
sbc pct revenue
3.89
What to be careful about
What this model itself distrusts about SEI's figures. Written by the
derivation as it ran, not added afterwards.
no market cap; set `market_cap` in overrides.yaml
share count is from 2019-09-30 (2526 days old, weighted average diluted); a stock split since then would make the market cap wrong. Set `market_cap` in overrides.yaml to be sure.
no usable diluted share count, so growth is measured on total revenue rather than per share; a company issuing shares to fund that growth reads better than it is
no forward EPS estimate; growth rests on filings only. Analyst consensus is not published in XBRL, so it has to be fetched from a data provider or set by hand in overrides.yaml as `eps_growth_2y`
valuation DROPPED from the total: only 0 of 2 inputs could be computed (ev sales, ev owner earnings not tagged), so the score is not meaningful. Its weight is spread over the other dimensions
durability rests on 3 of 4 inputs; not tagged: gross margin stability