Every figure this model derived for IVA, 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 2024-12-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.
The figures themselves rather than their scores — what somebody looking up
IVA on one particular measure came for.
Ratio
Value
cash operating margin
-1021.72
current ratio
2.96
current ratio reported
2.96
dilution pct
31.74
fcf margin
-934.2
interest cover
-8.01
operating margin
-1060.64
owner earnings margin
-973.12
revenue growth
-47.37
revenue growth per share
-60.05
rule of 40
-1108.01
sbc pct revenue
38.92
What to be careful about
What this model itself distrusts about IVA's figures. Written by the
derivation as it ran, not added afterwards.
WITHHELD: net margin -- net margin came out at -2,003% against a scale that tops out near 1,500%, which is arithmetic on a revenue figure of 9,198,000 rather than a margin. The figure is absent rather than corrected: there is no right value to put here.
revenue is annual, not TTM
operating income is annual, not TTM
revenue period ends 2024-12-31 (607 days ago) - the tag chain found nothing recent, so treat this row as unscored
no current capital expenditure tagged; treated as zero, so free cash flow is overstated and equals operating cash flow
no market cap; set `market_cap` in overrides.yaml
reports in EUR and no currency is recorded for its share price, so the two cannot be shown to match. The price refresh records one; until it has run for this company the multiples are left out rather than assumed comparable
share count is from 2025-12-31 (242 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`
quality rests on 4 of 5 inputs; not tagged: roic
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 DROPPED from the total: only 0 of 4 inputs could be computed (worst year, contracted coverage, gross margin stability, cash flow stability not tagged), so the score is not meaningful. Its weight is spread over the other dimensions
growth DROPPED from the total: only 1 of 4 inputs could be computed (sustained growth, margin trend, margin recent not tagged), so the score is not meaningful. Its weight is spread over the other dimensions
3 of 5 dimensions could not be measured (valuation, durability, growth -- 55% of the model), so this row is not comparable with the others; its total rests on what was left