Transparency alternatives to SAP Concur
Other Expense management vendors we measure, sorted by how much we found at them and not at SAP Concur. This is a comparison of disclosure, not of features or fitness.
12 shown of 31 that differ from SAP Concur on at least one criterion we measured for both. Public transparency score, not a product or security rating.
SAP Concur has 10 gaps in what we could measure: Data processing agreement, Subprocessor list, Data location stated, Status page with history, Public pricing, Certifications named, Uptime SLA with a figure, HTTPS enforced with HSTS, No third-party tracking before consent, Notice before subprocessors change. The column “Found there, not found at SAP Concur” is the one that closes them.
| Vendor | Score | Found there, not found at SAP Concur | Found at SAP Concur, not found there | |
|---|---|---|---|---|
| Brexbrex.comSee also Transparency alternatives to Brex | 70/100 | 7 Data processing agreement, Data location stated, Status page with history, +4 | 1 security.txt (RFC 9116) | Compare |
| Payhawkpayhawk.comSee also Transparency alternatives to Payhawk | 57/100 | 5 Data processing agreement, Data location stated, Certifications named, +2 | nothing | Compare |
| ExpenseInexpensein.comSee also Transparency alternatives to ExpenseIn | 52/100 | 5 Subprocessor list, Data location stated, Certifications named, +2 | 1 security.txt (RFC 9116) | Compare |
| Klippaklippa.comSee also Transparency alternatives to Klippa | 52/100 | 5 Data processing agreement, Data location stated, Status page with history, +2 | 1 Named privacy contact | Compare |
| Rydoorydoo.comSee also Transparency alternatives to Rydoo | 52/100 | 5 Data location stated, Status page with history, Public pricing, +2 | nothing | Compare |
| Navannavan.comSee also Transparency alternatives to Navan | 48/100 | 5 Data processing agreement, Public pricing, Certifications named, +2 | 1 security.txt (RFC 9116) | Compare |
| Tipaltitipalti.comSee also Transparency alternatives to Tipalti | 48/100 | 4 Data processing agreement, Data location stated, Public pricing, +1 | 1 security.txt (RFC 9116) | Compare |
| Emburseemburse.comSee also Transparency alternatives to Emburse | 43/100 | 4 Data location stated, Certifications named, HTTPS enforced with HSTS, +1 | nothing | Compare |
| Expensifyexpensify.comSee also Transparency alternatives to Expensify | 43/100 | 4 Data location stated, Status page with history, Public pricing, +1 | 1 security.txt (RFC 9116) | Compare |
| Spendeskspendesk.comSee also Transparency alternatives to Spendesk | 43/100 | 4 Data location stated, Status page with history, Certifications named, +1 | nothing | Compare |
| Mobilexpensemobilexpense.comSee also Transparency alternatives to Mobilexpense | 35/100 | 3 Data location stated, Public pricing, HTTPS enforced with HSTS | 1 security.txt (RFC 9116) | Compare |
| ExpenseOnDemandexpenseondemand.comSee also Transparency alternatives to ExpenseOnDemand | 26/100 | 3 Public pricing, Certifications named, HTTPS enforced with HSTS | 1 security.txt (RFC 9116) | Compare |
Only criteria we could measure for both are counted. Where we could measure one and not the other, the row is silent: that would be a statement about our measurement, not about either vendor. Every single result with its source is on the two profiles.