SAP Concur Expense · Schema

SAP Concur Expense Report

Schema for an SAP Concur Expense Report, which aggregates individual expense entries submitted by an employee for approval and reimbursement.

Expense ManagementFinancial ManagementReceiptsReimbursementReportingSAPTravel

Properties

Name Type Description
ID string The unique identifier of the expense report
Name string The name/title of the expense report
Total number Total amount of all expenses in the report in the report currency
CurrencyCode string ISO 4217 three-letter currency code for the report total
ApprovalStatusCode string Current approval workflow status code
ApprovalStatusName string Human-readable approval status label
PaymentStatusCode string Current payment processing status code
PaymentStatusName string Human-readable payment status label
SubmitDate string ISO 8601 datetime when the report was submitted for approval
CreateDate string ISO 8601 datetime when the report was created
ProcessingPaymentDate string ISO 8601 datetime when payment processing began
OwnerLoginID string Login ID (email) of the expense report owner
OwnerName string Full display name of the expense report owner
PolicyID string Identifier of the expense policy applied to this report
ReportNumber string Human-readable sequential report number
HasException boolean True if the report contains entries with policy exceptions requiring justification
PurposeStatement string Business purpose statement for the expenses in this report
URI string Full URI for the expense report resource
View JSON Schema on GitHub

JSON Schema

sap-concur-expense-report-schema.json Raw ↑
{
  "$schema": "http://json-schema.org/draft-07/schema#",
  "$id": "https://api-evangelist.github.io/sap-concur-expense/json-schema/sap-concur-expense-report-schema.json",
  "title": "SAP Concur Expense Report",
  "description": "Schema for an SAP Concur Expense Report, which aggregates individual expense entries submitted by an employee for approval and reimbursement.",
  "type": "object",
  "properties": {
    "ID": {
      "type": "string",
      "description": "The unique identifier of the expense report"
    },
    "Name": {
      "type": "string",
      "description": "The name/title of the expense report",
      "maxLength": 40
    },
    "Total": {
      "type": "number",
      "description": "Total amount of all expenses in the report in the report currency"
    },
    "CurrencyCode": {
      "type": "string",
      "description": "ISO 4217 three-letter currency code for the report total",
      "pattern": "^[A-Z]{3}$"
    },
    "ApprovalStatusCode": {
      "type": "string",
      "description": "Current approval workflow status code",
      "enum": [
        "A_AAFH",
        "A_AAPH",
        "A_ADMIN",
        "A_APPR",
        "A_EXTV",
        "A_FILE",
        "A_NOTF",
        "A_PBDG",
        "A_PECO",
        "A_PEND",
        "A_PVAL",
        "A_RESU",
        "A_RHLD",
        "A_TEXP"
      ]
    },
    "ApprovalStatusName": {
      "type": "string",
      "description": "Human-readable approval status label"
    },
    "PaymentStatusCode": {
      "type": "string",
      "description": "Current payment processing status code",
      "enum": ["P_HOLD", "P_NOTP", "P_PAID", "P_PAYC", "P_PROC"]
    },
    "PaymentStatusName": {
      "type": "string",
      "description": "Human-readable payment status label"
    },
    "SubmitDate": {
      "type": "string",
      "format": "date-time",
      "description": "ISO 8601 datetime when the report was submitted for approval"
    },
    "CreateDate": {
      "type": "string",
      "format": "date-time",
      "description": "ISO 8601 datetime when the report was created"
    },
    "ProcessingPaymentDate": {
      "type": "string",
      "format": "date-time",
      "description": "ISO 8601 datetime when payment processing began"
    },
    "OwnerLoginID": {
      "type": "string",
      "description": "Login ID (email) of the expense report owner"
    },
    "OwnerName": {
      "type": "string",
      "description": "Full display name of the expense report owner"
    },
    "PolicyID": {
      "type": "string",
      "description": "Identifier of the expense policy applied to this report"
    },
    "ReportNumber": {
      "type": "string",
      "description": "Human-readable sequential report number"
    },
    "HasException": {
      "type": "boolean",
      "description": "True if the report contains entries with policy exceptions requiring justification"
    },
    "PurposeStatement": {
      "type": "string",
      "description": "Business purpose statement for the expenses in this report"
    },
    "URI": {
      "type": "string",
      "format": "uri",
      "description": "Full URI for the expense report resource"
    }
  },
  "required": ["Name"]
}

Work with this as data

Every JSON Schema here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for schemas

4 MCP tools reach this
  • find_json_schemasBrowse and filter every JSON Schema in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This JSON Schema
curl "https://apis.io/api/v1/json-schemas/sap-concur-expense-report"
All schemas
curl "https://apis.io/api/v1/json-schemas?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.