CAB Payments Holdings PLC (CABP.L)
Every figure this model derived for CABP.L, 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.
| Figure | Value | XBRL tag | As at |
|---|---|---|---|
| capex | 2,428,000 | PurchaseOfPropertyPlantAndEquipmentClassifiedAsInvestingActivities |
2024-12-31 |
| cash | 1,258,435,000 | CashAndCashEquivalents |
2025-01-01 |
| equity | 146,551,000 | Equity |
2025-01-01 |
| interest expense | 39,300,000 | InterestExpense |
2024-12-31 |
| ocf | 84,975,000 | CashFlowsFromUsedInOperatingActivities |
2024-12-31 |
| revenue | 105,544,000 | Revenue |
2024-12-31 |
The ratios
The figures themselves rather than their scores — what somebody looking up CABP.L on one particular measure came for.
| Ratio | Value |
|---|---|
| fcf margin | 78.21 |
| owner earnings margin | 78.21 |
| revenue growth | -23.0 |
| revenue growth per share | -23.0 |
| sbc pct revenue | 0.0 |
What to be careful about
What this model itself distrusts about CABP.L's figures. Written by the derivation as it ran, not added afterwards.
- newest fact in the filing is 2025-01-01 (1y old); this company's data is not usable and the scores below should be ignored
- revenue is annual, not TTM
- no operating income found in XBRL
- revenue period ends 2024-12-31 (626 days ago) - the tag chain found nothing recent, so treat this row as unscored
- no current stock compensation tagged; treated as zero, so owner earnings are overstated
- no market cap; set `market_cap` in overrides.yaml
- 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`
- quality DROPPED from the total: only 2 of 5 inputs could be computed (operating margin, roic, cash operating margin not tagged), so the score is not meaningful. Its weight is spread over the other dimensions
- valuation DROPPED from the total: only 0 of 2 inputs could be computed (ev ebit, 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 1 of 4 inputs could be computed (worst year, contracted coverage, gross margin stability not tagged), so the score is not meaningful. Its weight is spread over the other dimensions
- resilience DROPPED from the total: only 1 of 3 inputs could be computed (interest cover, liquidity 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
- 5 of 5 dimensions could not be measured (quality, valuation, durability, resilience, growth -- 100% of the model), so this row is not comparable with the others; its total rests on what was left