specification: FinOps Framework
specificationVersion: '1.0'
schema: https://www.finops.org/framework/
alignedWith:
  framework: FinOps Foundation Framework
  frameworkUrl: https://www.finops.org/framework/
  dataSpec: FOCUS
  dataSpecVersion: '1.3'
  dataSpecUrl: https://focus.finops.org/focus-specification/v1-3/
provider: SAP Concur
providerId: concur
publisherName: SAP Concur Technologies, Inc.
serviceCategory: Travel & Expense Management
created: '2026-05-04'
# Provenance stamped 2026-08-11: this artifact was written by the API Evangelist
# bulk sweep dated 2026-05-04, not harvested from the provider. See roadmap#35.
method: generated
modified: '2026-05-05'
reconciled: false
tags:
  - Expense Management
  - Finance
  - Invoice
  - SAP
  - Travel
  - FinOps
  - FOCUS
description: 'FOCUS-aligned FinOps for SAP Concur: enterprise SaaS subscription where API consumption
  is bundled with the customer''s SAP Concur (Expense / Travel / Invoice / Request) contract; spend allocation
  follows the SAP enterprise invoice rather than per-API-call billing.'
notes: SAP Concur does not publish per-call API pricing; spend rolls up under the customer's enterprise
  Concur subscription. Meters here describe what consumers should track internally for chargeback even
  though SAP does not bill per-call externally.
sources:
  - https://developer.concur.com/api-reference/
  - https://www.concur.com/
billingModel:
  pricingCategory: Enterprise Subscription
  billingFrequency: Annual
  billingCurrency: USD
  chargeCategories:
    - Purchase
    - Tax
    - Adjustment
    - Credit
focusColumns:
  ServiceName: SAP Concur
  ServiceCategory: Travel & Expense Management
  ProviderName: SAP Concur
  PublisherName: SAP Concur Technologies, Inc.
  InvoiceIssuerName: SAP America, Inc.
  BillingCurrency: USD
  ChargeCategory: Purchase
meters:
  - name: concur_subscription
    description: Annual SAP Concur subscription fee (Expense / Travel / Invoice / Request modules)
    unit: month
    aggregation: max
    dimensions:
      - module
      - tenant
  - name: api_calls_internal
    description: Internal-only meter — count of API calls per consuming application for chargeback within
      the customer organization. Not billed externally by SAP.
    unit: request
    aggregation: sum
    dimensions:
      - api
      - consumer_app
      - environment
  - name: active_users
    description: Per-user (employee) component of the SAP Concur subscription
    unit: seat
    aggregation: avg
    dimensions:
      - module
      - tenant
principles:
  - name: Visibility
    description: SAP does not bill API calls separately; for internal cost allocation use the Concur Audit
      / Reporting APIs and the partner application credential identifiers to attribute consumption to
      consuming apps and teams.
  - name: Allocation
    description: Tag SAP Concur OAuth2 application credentials and entity IDs (companyId) per consuming
      product; allocate the overall Concur subscription across business units using employee headcount
      and module activation.
  - name: Optimization
    description: Optimize the SAP contract by reviewing module activation (Expense vs Travel vs Invoice
      vs Request) annually and pruning unused integration apps; reduce API churn via batch endpoints
      and webhook-driven sync rather than polling.
  - name: Accountability
    description: Travel & expense ops typically owns the Concur subscription line; integration owners
      (HR / IT / partner integrations) are accountable for API usage patterns within the bundled allowance.
maintainers:
  - FN: Kin Lane
    email: kin@apievangelist.com