Every figure this model derived for ACCL, 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 2025-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
23,203
PaymentsToAcquirePropertyPlantAndEquipment
2025-06-30
cash
2,450,033
CashAndCashEquivalentsAtCarryingValue
2025-06-30
current assets
2,873,756
AssetsCurrent
2025-06-30
current liabilities
1,575,405
LiabilitiesCurrent
2025-06-30
equity
2,186,884
StockholdersEquity
2025-06-30
interest expense
38,494
InterestPaidNet
2025-06-30
ocf
1,538,145
NetCashProvidedByUsedInOperatingActivities
2025-06-30
revenue
4,852,182
Revenues
2025-06-30
The ratios
The figures themselves rather than their scores — what somebody looking up
ACCL on one particular measure came for.
Ratio
Value
cash operating margin
22.47
current ratio
2.83
current ratio reported
1.82
deferred revenue growth
15.52
dilution pct
0.0
ebit cagr
49.61
ebit yoy
2.22
fcf margin
31.22
interest cover
28.05
operating margin
22.26
owner earnings margin
31.22
revenue growth
12.54
revenue growth per share
12.54
rule of 40
34.79
sbc pct revenue
0.0
What to be careful about
What this model itself distrusts about ACCL's figures. Written by the
derivation as it ran, not added afterwards.
revenue is annual, not TTM
operating income is annual, not TTM
no current stock compensation tagged; treated as zero, so owner earnings are overstated
no market cap; set `market_cap` in overrides.yaml
share count is from 2025-06-30 (426 days old, dei cover page); a stock split since then would make the market cap wrong. Set `market_cap` in overrides.yaml to be sure.
invested capital is -0M (cash exceeds equity plus debt), so return on capital is unbounded rather than undefined; scored as maximal
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: worst year
growth rests on 3 of 4 inputs; not tagged: sustained growth