Every figure this model derived for PDEX, 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-03-31.
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
0
PaymentsToAcquirePropertyPlantAndEquipment
2022-06-30
cash
7,613,000
CashAndCashEquivalentsAtCarryingValue
2026-03-31
current assets
53,710,000
AssetsCurrent
2026-03-31
current liabilities
14,636,000
LiabilitiesCurrent
2026-03-31
equity
45,198,000
StockholdersEquity
2026-03-31
interest expense
753,000
InterestPaidNet
2026-03-31
ocf
7,342,000
NetCashProvidedByUsedInOperatingActivities
2026-03-31
revenue
74,636,000
Revenues
2026-03-31
sbc
665,000
ShareBasedCompensation
2026-03-31
The ratios
The figures themselves rather than their scores — what somebody looking up
PDEX on one particular measure came for.
Ratio
Value
cash operating margin
17.11
current ratio
3.71
current ratio reported
3.67
dilution pct
-5.88
ebit cagr
22.02
ebit yoy
-7.61
fcf margin
9.84
growth cv
0.4
interest cover
14.35
operating margin
14.48
owner earnings margin
8.95
revenue growth
16.39
revenue growth per share
23.67
roic
20.43
rule of 40
30.87
sbc pct revenue
0.89
What to be careful about
What this model itself distrusts about PDEX's figures. Written by the
derivation as it ran, not added afterwards.
no current capital expenditure tagged (last tagged 2022-06-30); treated as zero, so free cash flow is overstated and equals operating cash flow
no market cap; set `market_cap` in overrides.yaml
share count is from 2026-04-28 (124 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.
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