Every figure this model derived for AATC, 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 2021-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
2,140,000
PaymentsToAcquirePropertyPlantAndEquipment
2022-09-30
cash
3,833,000
CashAndCashEquivalentsAtCarryingValue
2022-09-30
current assets
10,632,000
AssetsCurrent
2022-09-30
current liabilities
1,525,000
LiabilitiesCurrent
2022-09-30
equity
18,659,000
StockholdersEquity
2022-09-30
interest expense
54,000
InterestExpenseDebt
2022-09-30
ocf
1,362,000
NetCashProvidedByUsedInOperatingActivities
2022-09-30
revenue
8,500,000
Revenues
2021-12-31
sbc
391,000
AllocatedShareBasedCompensationExpense
2022-09-30
The ratios
The figures themselves rather than their scores — what somebody looking up
AATC on one particular measure came for.
Ratio
Value
cash operating margin
20.67
current ratio
7.54
current ratio reported
6.97
deferred revenue growth
30.68
dilution pct
0.79
ebit cagr
-13.08
ebit yoy
-36.09
fcf margin
-9.15
interest cover
22.43
operating margin
14.25
owner earnings margin
-13.75
revenue growth
2.41
revenue growth per share
1.61
roic
5.79
rule of 40
16.66
sbc pct revenue
4.6
What to be careful about
What this model itself distrusts about AATC's figures. Written by the
derivation as it ran, not added afterwards.
newest fact in the filing is 2022-11-08 (3y old); this company's data is not usable and the scores below should be ignored
revenue is annual, not TTM
revenue period ends 2021-12-31 (1703 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 2022-09-30 (1430 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