{
 "categories": [
  "finance",
  "invoicing",
  "enterprise"
 ],
 "deployment": "saas",
 "evidence": [
  {
   "date": "2026-09-01",
   "fact": "homepage",
   "note": "SAP Concur presents a cloud spend platform for Concur Expense, Concur Travel, and Concur Invoice, with receipt capture, travel booking, invoice matching, and a sales-contact path.",
   "source": "https://www.concur.com/",
   "tier": "declared"
  },
  {
   "date": "2026-09-01",
   "fact": "vendor",
   "note": "The product is branded SAP Concur throughout the homepage and FAQ.",
   "source": "https://www.concur.com/",
   "tier": "declared"
  },
  {
   "date": "2026-09-01",
   "fact": "deployment",
   "note": "The FAQ states SAP Concur is a cloud-based platform that centralizes expense, travel, and invoice processes.",
   "source": "https://www.concur.com/",
   "tier": "declared"
  },
  {
   "date": "2026-09-01",
   "fact": "license",
   "note": "The homepage offers contact-sales and implementation conversations. No public free tenant is published.",
   "source": "https://www.concur.com/",
   "tier": "declared"
  },
  {
   "date": "2026-09-01",
   "fact": "platforms",
   "note": "SAP Concur documents a companion mobile app for iPhone and Android in addition to the web platform. The app requires an active subscription.",
   "source": "https://www.concur.com/products/mobile-app",
   "tier": "declared"
  },
  {
   "date": "2026-09-01",
   "fact": "modalities.api.exists",
   "note": "The SAP Concur Developer Center documents HTTP APIs that pull, post, update, and delete data in the Concur product ecosystem.",
   "source": "https://developer.concur.com/api-reference/",
   "tier": "declared"
  },
  {
   "date": "2026-09-01",
   "fact": "modalities.api.kinds[0]",
   "note": "The API reference states most APIs support GET, POST, PUT, and DELETE against an HTTPS endpoint, with optional parameters for query or write.",
   "source": "https://developer.concur.com/api-reference/",
   "tier": "declared"
  },
  {
   "date": "2026-09-01",
   "fact": "modalities.api.auth[0]",
   "note": "SAP Concur documents OAuth 2.0 Bearer access tokens from POST /oauth2/v0/token. Supported grants are authorization, password, client credentials, and one-time password. Access tokens last one hour; refresh tokens last six months. The token response includes a geolocation base URI.",
   "source": "https://developer.concur.com/api-reference/authentication/apidoc.html",
   "tier": "declared"
  },
  {
   "date": "2026-09-01",
   "fact": "modalities.api.coverage",
   "note": "Reports v4 covers Concur Expense Professional and Standard editions and can retrieve, create, patch, and delete report headers and patch workflow status. The page states access to the documentation does not provide access to the API and that clients must purchase Concur Expense.",
   "source": "https://developer.concur.com/api-reference/expense/expense-report/v4.reports.html",
   "tier": "declared"
  },
  {
   "date": "2026-09-01",
   "fact": "modalities.api.coverage",
   "note": "Purchase Orders v3 documents POST, PUT, and GET of approved purchase orders for Concur Invoice Professional and Standard. Clients must purchase Concur Invoice, Concur Purchase Order, and Concur Web Services. The API is limited to direct client integrations.",
   "source": "https://developer.concur.com/api-reference/invoice/v3.purchase-order.html",
   "tier": "declared"
  },
  {
   "date": "2026-09-01",
   "fact": "modalities.api.coverage",
   "note": "The Itinerary API documents programmatic access to Concur Travel trips and bookings for TMCs, TripLink suppliers, and Web Services clients. Access depends on who is calling and which products were purchased.",
   "source": "https://developer.concur.com/api-reference/travel/itinerary/itinerary.html",
   "tier": "declared"
  },
  {
   "date": "2026-09-01",
   "fact": "modalities.api.docs",
   "note": "Opened as the current API Reference landing page. It points to the Swagger explorer, per-API pages, and integration guides.",
   "source": "https://developer.concur.com/api-reference/",
   "tier": "declared"
  },
  {
   "date": "2026-09-01",
   "fact": "modalities.api.exists",
   "note": "Getting started states that after an agreement is in place SAP Concur issues a client_id and client_secret, assigns scopes and grants, and can provision sandboxes. Credentials are not self-serve for unentitled tenants.",
   "source": "https://developer.concur.com/getting-started.html",
   "tier": "declared"
  },
  {
   "date": "2026-09-01",
   "fact": "modalities.mcp.third_party",
   "note": "The official MCP registry search for concur returned {\"servers\":[],\"metadata\":{\"count\":0}}. Registry silence is not proof that SAP has no first-party server.",
   "source": "https://registry.modelcontextprotocol.io/v0.1/servers?search=concur",
   "tier": "scraped"
  },
  {
   "date": "2026-09-01",
   "fact": "modalities.integrations.zapier",
   "note": "Zapier's public app directory returned 404 for /apps/sap-concur/integrations and /apps/concur/integrations on 2026-09-01.",
   "source": "https://zapier.com/apps/sap-concur/integrations",
   "tier": "scraped"
  },
  {
   "date": "2026-09-01",
   "fact": "modalities.integrations.make",
   "note": "Make's app catalogue rendered a coming-soon 404 for /sap-concur and /concur on 2026-09-01.",
   "source": "https://apps.make.com/sap-concur",
   "tier": "scraped"
  },
  {
   "date": "2026-09-01",
   "fact": "modalities.integrations.power_automate",
   "note": "Microsoft's connector path /connectors/sapconcur/ and /connectors/concur/ returned 404 on 2026-09-01.",
   "source": "https://learn.microsoft.com/en-us/connectors/sapconcur/",
   "tier": "scraped"
  },
  {
   "date": "2026-09-01",
   "fact": "modalities.integrations.power_automate",
   "note": "Microsoft's Power Platform SAP FAQ says products such as Ariba and Concur that do not run on the NetWeaver stack should use custom REST and SOAP connectors, not the SAP ERP connector.",
   "source": "https://learn.microsoft.com/en-us/power-platform/sap/explore/faqs",
   "tier": "scraped"
  },
  {
   "date": "2026-09-01",
   "fact": "modalities.integrations.n8n",
   "note": "n8n built-in app-node documentation returned 404 for n8n-nodes-base.sapconcur and n8n-nodes-base.concur on 2026-09-01. n8n.io/integrations/sap-concur also returned 404.",
   "source": "https://docs.n8n.io/integrations/builtin/app-nodes/n8n-nodes-base.sapconcur/",
   "tier": "scraped"
  },
  {
   "date": "2026-09-01",
   "fact": "modalities.extensibility.webhooks",
   "note": "Event Subscription Service v4 delivers events to a subscriber HTTPS endpoint for topics such as public.concur.expense.report and public.concur.travel.request. Delivery uses mutual TLS and a Concur-Signature header. An application may have up to five subscriptions.",
   "source": "https://developer.concur.com/api-reference/ess/v4.event-subscription.html",
   "tier": "declared"
  },
  {
   "date": "2026-09-01",
   "fact": "modalities.extensibility.scripting[0]",
   "note": "Callouts invoke a client-hosted application connector for Fetch Attendee, Fetch List Item, Event Notification, and Launch External URL. Administrators register connectors under Web Services. Partner endpoints must be safelisted.",
   "source": "https://developer.concur.com/api-reference/callouts/callouts-application-connectors.html",
   "tier": "declared"
  },
  {
   "date": "2026-09-01",
   "fact": "modalities.data_access.export[0]",
   "note": "GET /expensereports/v4/users/{userID}/context/{contextType}/reports/{reportId} returns a JSON report header, including approval status and custom data.",
   "source": "https://developer.concur.com/api-reference/expense/expense-report/v4.reports.html",
   "tier": "declared"
  },
  {
   "date": "2026-09-01",
   "fact": "modalities.data_access.import[0]",
   "note": "POST creates a new report and PATCH applies JSON Merge Patch updates to unsubmitted or submitted report headers.",
   "source": "https://developer.concur.com/api-reference/expense/expense-report/v4.reports.html",
   "tier": "declared"
  },
  {
   "date": "2026-09-01",
   "fact": "modalities.data_access.import[0]",
   "note": "POST /api/v3.0/invoice/purchaseorders accepts a JSON purchase-order body to create or update an approved purchase order.",
   "source": "https://developer.concur.com/api-reference/invoice/v3.purchase-order.html",
   "tier": "declared"
  },
  {
   "date": "2026-09-01",
   "fact": "modalities.agent_docs.llms_txt",
   "note": "https://www.concur.com/llms.txt returned 404 on 2026-09-01 and did not serve a first-party agent document. developer.concur.com/llms.txt also returned 404.",
   "source": "https://www.concur.com/llms.txt",
   "tier": "scraped"
  },
  {
   "date": "2026-09-01",
   "fact": "verdict.scores.api",
   "note": "The API path is broad, documented, OAuth-authenticated, event-enabled, and actively versioned, but Client Web Services, partner enablement, per-product purchase, geolocation routing, and remaining v3/v1 surfaces keep it below unusual completeness.",
   "source": "https://developer.concur.com/api-reference/authentication/apidoc.html",
   "tier": "declared"
  },
  {
   "date": "2026-09-01",
   "fact": "verdict.scores.api",
   "note": "SAP Concur publishes an API lifecycle policy with a 24-month minimum active-or-deprecated lifespan and 12 months in deprecated status before decommission, with stated legal and security exceptions.",
   "source": "https://developer.concur.com/tools-support/deprecation-policy.html",
   "tier": "declared"
  },
  {
   "date": "2026-09-01",
   "fact": "verdict.scores.api",
   "note": "The OAuth 2.0 Application Management Tool lets Client Web Services customers generate client IDs and secrets after CWS enables the tool. It is available in US2, EU2, and APJ1. That is entitled self-serve, not open signup.",
   "source": "https://developer.concur.com/api-reference/authentication/oauth2-app-mgmt-tool.html",
   "tier": "declared"
  },
  {
   "date": "2026-09-01",
   "fact": "verdict.scores.integrations",
   "note": "Bounded 2026-09-01 checks of Zapier, Make, Microsoft Power Automate connector paths, and n8n built-in nodes found no SAP Concur product connector. Microsoft tells integrators to use custom REST or SOAP connectors for Concur.",
   "source": "https://learn.microsoft.com/en-us/connectors/sapconcur/",
   "tier": "scraped"
  },
  {
   "date": "2026-09-01",
   "fact": "freshness.watch[0].url",
   "note": "Opened and verified as the current SAP Concur product homepage for Expense, Travel, and Invoice.",
   "source": "https://www.concur.com/",
   "tier": "declared"
  },
  {
   "date": "2026-09-01",
   "fact": "freshness.watch[1].url",
   "note": "Opened and verified as the current OAuth 2.0 grants, token, refresh, and geolocation reference.",
   "source": "https://developer.concur.com/api-reference/authentication/apidoc.html",
   "tier": "declared"
  },
  {
   "date": "2026-09-01",
   "fact": "freshness.watch[2].url",
   "note": "Opened and verified as the current Reports v4 expense-report header API, including create, patch, delete, and workflow.",
   "source": "https://developer.concur.com/api-reference/expense/expense-report/v4.reports.html",
   "tier": "declared"
  },
  {
   "date": "2026-09-01",
   "fact": "freshness.watch[3].url",
   "note": "Opened and verified as the current Event Subscription Service v4 webhook documentation.",
   "source": "https://developer.concur.com/api-reference/ess/v4.event-subscription.html",
   "tier": "declared"
  },
  {
   "date": "2026-09-01",
   "fact": "freshness.watch[4].url",
   "note": "Opened and verified as the current developer-platform release-notes index, including August 2026 API notes.",
   "source": "https://developer.concur.com/tools-support/release-notes/index.html",
   "tier": "declared"
  },
  {
   "date": "2026-09-01",
   "fact": "freshness.watch[5].url",
   "note": "Opened the official MCP registry search for concur; count was 0.",
   "source": "https://registry.modelcontextprotocol.io/v0.1/servers?search=concur",
   "tier": "scraped"
  }
 ],
 "freshness": {
  "last_verified": "2026-09-01",
  "volatility": "high",
  "watch": [
   {
    "type": "docs",
    "url": "https://www.concur.com/"
   },
   {
    "type": "docs",
    "url": "https://developer.concur.com/api-reference/authentication/apidoc.html"
   },
   {
    "type": "docs",
    "url": "https://developer.concur.com/api-reference/expense/expense-report/v4.reports.html"
   },
   {
    "type": "docs",
    "url": "https://developer.concur.com/api-reference/ess/v4.event-subscription.html"
   },
   {
    "type": "changelog",
    "url": "https://developer.concur.com/tools-support/release-notes/index.html"
   },
   {
    "type": "registry",
    "url": "https://registry.modelcontextprotocol.io/v0.1/servers?search=concur"
   }
  ]
 },
 "homepage": "https://www.concur.com/",
 "id": "sap-concur",
 "license": "commercial",
 "modalities": {
  "agent_docs": {
   "llms_txt": false
  },
  "api": {
   "auth": [
    "oauth2"
   ],
   "coverage": "partial",
   "docs": "https://developer.concur.com/api-reference/",
   "exists": true,
   "kinds": [
    "rest"
   ]
  },
  "cli": {
   "exists": "unknown"
  },
  "computer_use": {
   "issues": [],
   "viability": "unknown"
  },
  "data_access": {
   "export": [
    "api-json"
   ],
   "import": [
    "api-json"
   ]
  },
  "extensibility": {
   "scripting": [
    "application-connectors"
   ],
   "webhooks": true
  },
  "integrations": {
   "make": false,
   "n8n": false,
   "power_automate": false,
   "zapier": false
  },
  "mcp": {
   "first_party": "unknown",
   "third_party": [],
   "verdict": "unknown"
  },
  "rpa": {
   "drivability": "unknown",
   "notes": "No repeatable UI probe was run. The documented REST APIs, Event Subscription Service webhooks, and application-connector callouts are the supported automation paths. Browser and mobile UI control remain unassessed.\n",
   "ui_stack": [
    "web-dom"
   ],
   "vendor_support": []
  },
  "sdk": {
   "exists": "unknown",
   "languages": [],
   "official": "unknown"
  }
 },
 "name": "SAP Concur",
 "platforms": [
  "web",
  "ios",
  "android"
 ],
 "related": {
  "alternatives": [
   "sap-s4hana",
   "sap-successfactors",
   "basware",
   "visma-proceedo"
  ],
  "our_products": []
 },
 "schema_version": 1,
 "score_version": 1,
 "status": "active",
 "vendor": "SAP",
 "verdict": {
  "best_path": "api",
  "scores": {
   "api": 7,
   "cli": null,
   "computer_use": null,
   "integrations": 0,
   "mcp": null,
   "overall": 7,
   "rpa": null
  },
  "summary": "SAP Concur is automatable today through its documented REST APIs. The Developer Center publishes OAuth 2.0 at geolocation hosts such as https://us.api.concursolutions.com/oauth2/v0/token. Documented grants are authorization code, password, client credentials, and one-time password. Access tokens last one hour and refresh tokens last six months. Callers must store and reuse the token geolocation as the base URI. Reports v4 can create, read, JSON-merge-patch, and delete expense-report headers and can approve or send back a report in workflow, using company or user Bearer tokens and scopes such as expense.report.read and expense.report.readwrite. Purchase Orders v3 creates and updates approved purchase orders for Concur Invoice. The Itinerary API reads and posts travel trips and bookings. Event Subscription Service v4 delivers signed HTTPS webhooks for topics such as public.concur.expense.report. Callouts let a tenant host an application connector that Concur invokes during expense workflows. Custom API access requires Client Web Services; the OAuth 2.0 Application Management Tool mints client IDs only after CWS enables it. Access to the documentation does not grant API access. Entitlements follow the purchased Expense, Travel, or Invoice edition. The official MCP registry returned no Concur servers, and vendor docs do not declare a first-party MCP server. Zapier, Make, Microsoft Power Automate, and n8n had no product connector on 2026-09-01. Computer-use viability is unassessed. This record is not SAP S/4HANA, SAP SuccessFactors, Basware, or Visma Proceedo.\n"
 }
}