| Category | Function | Share | Rank | Negative rate | Labels | Quadrant | Since September 2026 |
|---|---|---|---|---|---|---|---|
| Treasury management systems | Treasury and cash | 0% | 124 of 124 | 54% | 28 | criticized challenger | =heldSince September 2026: 0% → 0%, ±0 points. Inside the 10-point floor: within noise. Read over the models both editions asked. |
| Cash flow forecasting | Treasury and cash | 0% | 101 of 101 | 100% | 4 | under 10 labels · led by Agicap at 13% | =heldSince September 2026: 0% → 0%, ±0 points. Inside the 10-point floor: within noise. Read over the models both editions asked. |
| Category | September 2026 | Now | Change | Reading | Rank |
|---|---|---|---|---|---|
| Treasury management syst | 0% | 0% | =heldSince September 2026: 0% → 0%, ±0 points. Inside the 10-point floor: within noise. Read over the models both editions asked. | Within noise | Rank 113 → 124 of 124 |
| Cash flow forecasting | 0% | 0% | =heldSince September 2026: 0% → 0%, ±0 points. Inside the 10-point floor: within noise. Read over the models both editions asked. | Within noise | Rank 79 → 101 of 101 |
Shares here are read over the models both editions asked, so they can differ by a point or two from the standing above, which counts every model in this edition.
The floor is 10 points of share, measured: how far the models move a leader on their own when the same questions are asked twice with nothing changed. A larger change is movement; a smaller one is noise, and both are shown. Movement is read over the twelve models both editions asked; GPT-6 Luna, Muse Glimmer 30B joined this edition and are in the standing but not yet in the comparison. How the floor is measured · The editions
| Model | First choice | Alternative | Mention | Negative | Labels |
|---|---|---|---|---|---|
| Claude Haiku 4.5 | 0 | 0 | 0 | 1 | 1 |
| GPT-5.4 mini | 0 | 0 | 0 | 0 | 0 |
| Gemini 3.5 Flash | 0 | 0 | 0 | 3 | 3 |
| Perplexity Sonar | 0 | 0 | 0 | 0 | 0 |
| Grok 4.1 Fast | 0 | 1 | 0 | 1 | 2 |
| Mistral Small | 0 | 2 | 0 | 0 | 2 |
| DeepSeek V4 Flash | 0 | 1 | 0 | 1 | 2 |
| Llama 4 Maverick | 0 | 0 | 1 | 0 | 1 |
| Qwen 3.7 Flash | 0 | 1 | 0 | 4 | 5 |
| Kimi K2 | 0 | 1 | 0 | 3 | 4 |
| GLM 4.7 FlashX | 0 | 1 | 2 | 2 | 5 |
| MiniMax M2.5 | 0 | 0 | 1 | 0 | 1 |
| GPT-6 Luna | 0 | 1 | 0 | 1 | 2 |
| Muse Glimmer 30B | 0 | 1 | 0 | 3 | 4 |
Verbatim evidence the judge attached to positive labels.
“best suited for organizations already using SAP ... but may require more customization for advanced treasury functions” Mistral Small · Treasury management syst · comparative prompt · alternative
“Definitive choice for global conglomerates requiring deep ERP integration and institutional-grade risk controls.” Muse Glimmer 30B · Treasury management syst · comparative prompt · alternative
“If a company already uses SAP ERP, this is often the default choice because it is deeply integrated.” GLM 4.7 FlashX · Treasury management syst · comparative prompt · alternative
“recommended if your ERP is already SAP and you want to keep treasury data within the same ecosystem” Mistral Small · Treasury management syst · negative prompt · alternative
Verbatim evidence attached to negative labels. A warning on a product with few labels is a warning; on a product with many, it is one voice among them.
“Who should avoid: Mid-market treasuries, startups, or teams without a dedicated SAP Basis/admin team.” DeepSeek V4 Flash · Treasury management syst · negative prompt · hard negative
“Avoid enterprise solutions like Kyriba, SAP, or GTreasury if you're on a limited budget” Kimi K2 · Treasury management syst · budget prompt · hard negative
“Avoid unless you're already committed to SAP S/4HANA ecosystem.” Kimi K2 · Treasury management syst · negative prompt · hard negative
“Large enterprise systems like SAP and Kyriba provide extremely deep functionality but are often too complex and expensive for mid-market companies” Claude Haiku 4.5 · Treasury management syst · direct prompt · soft negative
Citations exist only for the models that return a source list, five of the fourteen in this edition, so these counts come from 109 of the 117 answers that named SAP Treasury and Risk Management and are not a share of its labels.
397 of the 397 domain citations in answers naming SAP Treasury and Risk Management came from somebody else's page.
Pages are listed as the models cited them.
Search figures are US estimates from DataForSEO, read September 28, 2026; AI search demand is its modeled, directional estimate, not a count of queries to any assistant. The answers are this edition's. Two measurements side by side: neither is read as the cause of the other.
An email the morning each edition publishes: where this product moved, where it held, and by how much against the noise floor. One address, confirmed by a click; a stop link in every email.
Already following? Everything you follow, with a stop for each.
What SAP Treasury and Risk Management's own pages state, read September 28, 2026: sap.com/products/financial-management/treasury-risk-management.html, sap.com/sea/products/financial-management/treasury-risk-management.html, sap.com/mena/products/financial-management/treasury-risk-management.html, sap.com/korea/products/financial-management/treasury-risk-management.html, sap.com/spain/products/financial-management/treasury-risk-management.html. A claimed page can correct any of them.
Claiming is free and changes nothing in the data. A claimed page shows a verified contact who is told when each edition publishes and when SAP Treasury and Risk Management's standing changes by more than the noise floor; the right to propose corrections to the vendor table, meaning names the judge wrote that should or should not read as SAP Treasury and Risk Management, applied by version and listed in the change log; and a one-line description supplied by the vendor and marked as such.
A new claim receives the current edition's vendor brief for SAP Treasury and Risk Management by email, built from the raw record of the edition. It shows: