Every figure this model derived for INNI, 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 2013-09-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,279
PaymentsToAcquirePropertyPlantAndEquipment
2012-12-31
cash
16,919
CashAndCashEquivalentsAtCarryingValue
2013-09-30
current assets
975,219
AssetsCurrent
2013-09-30
current liabilities
4,874,373
LiabilitiesCurrent
2013-09-30
equity
-728,066
StockholdersEquity
2013-09-30
interest expense
412,762
InterestExpense
2013-09-30
ocf
-1,228,720
NetCashProvidedByUsedInOperatingActivities
2013-09-30
revenue
527,689
Revenues
2013-09-30
sbc
191,919
ShareBasedCompensation
2012-12-31
The ratios
The figures themselves rather than their scores — what somebody looking up
INNI on one particular measure came for.
Ratio
Value
cash operating margin
-816.36
current ratio
0.21
current ratio reported
0.2
deferred revenue growth
30.13
dilution pct
3.0
fcf margin
-233.09
interest cover
-12.01
operating margin
-939.26
owner earnings margin
-269.46
roic
-51.87
sbc pct revenue
36.37
What to be careful about
What this model itself distrusts about INNI's figures. Written by the
derivation as it ran, not added afterwards.
newest fact in the filing is 2013-09-30 (12y old); this company's data is not usable and the scores below should be ignored
no operating income tagged; derived as revenue minus CostsAndExpenses
revenue period ends 2013-09-30 (4717 days ago) - the tag chain found nothing recent, so treat this row as unscored
no market cap; set `market_cap` in overrides.yaml
share count is from 2013-06-30 (4809 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 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 DROPPED from the total: only 2 of 4 inputs could be computed (worst year, gross margin 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 (revenue growth, sustained growth, 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