Every figure this model derived for TCPA, 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 2017-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.
Figure
Value
XBRL tag
As at
capex
7,383,000,000
PaymentsToAcquirePropertyPlantAndEquipment
2017-12-31
cash
1,044,000,000
CashAndCashEquivalentsAtCarryingValue
2017-12-31
current assets
4,650,000,000
AssetsCurrent
2017-12-31
current liabilities
12,408,000,000
LiabilitiesCurrent
2017-12-31
equity
22,417,000,000
StockholdersEquity
2017-12-31
interest expense
2,137,000,000
InterestExpense
2017-12-31
ocf
5,162,000,000
NetCashProvidedByUsedInOperatingActivities
2017-12-31
revenue
13,449,000,000
SalesRevenueNet
2017-12-31
sbc
12,000,000
AllocatedShareBasedCompensationExpense
2017-12-31
The ratios
The figures themselves rather than their scores — what somebody looking up
TCPA on one particular measure came for.
Ratio
Value
cash operating margin
50.2
current ratio
0.37
current ratio reported
0.37
fcf margin
-16.51
interest cover
2.19
net debt ebitda
5.26
operating margin
34.83
owner earnings margin
-16.6
revenue growth
7.19
revenue growth per share
7.19
roic
6.39
rule of 40
42.02
sbc pct revenue
0.09
What to be careful about
What this model itself distrusts about TCPA's figures. Written by the
derivation as it ran, not added afterwards.
newest fact in the filing is 2017-12-31 (8y old); this company's data is not usable and the scores below should be ignored
revenue is annual, not TTM
operating income is annual, not TTM
revenue period ends 2017-12-31 (3164 days ago) - the tag chain found nothing recent, so treat this row as unscored
no market cap; set `market_cap` in overrides.yaml
reports in CAD 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
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 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