Turn SAP Concur expense reports into an API

What you can build on Concur

• Get expense reports

  Build this

  Reads the Report Library section of the Manage Expenses page, for active reports or the view or date range you pick in the View list.

  Takes

  View or date range (optional)

  Returns

  Report name, report date, submit date, approval status, payment status, report total, currency

• List reports waiting for my approval

  Build this

  Reads the expense reports waiting for you under Approvals, the same list the Required Approvals heading in My Tasks opens.

  Takes

  Nothing

  Returns

  Employee, report name, submit date, report total, currency, alerts

• Get company card transactions

  Build this

  Reads the Available Expenses section of the Manage Expenses page and, for each card item, the Expense Source window opened from the Payment Type column.

  Takes

  Transaction date from (optional)

  Returns

  Transaction date, vendor name, location, amount, currency, payment type, receipt attached

• Approve an expense report

  Build this

  Opens one report from Approvals and clicks Approve on the expense report page.

  Takes

  Employee, report name

  Returns

  Report name, employee, report total, approval status

Automate Concur with a workflow

A workflow runs your methods as one process, with nobody at the screen. A schedule or a call from your own system starts it, the steps run in order, and the result arrives in your inbox or in the systems you already use.

• Expense reports waiting for your approval

  Build this

  Starts

  Every weekday at 8:00

  Step 1

  List the reports waiting for your approval in Approvals.

  Step 2

  Stop when there are none.

  Step 3

  Email you the list with employee, report name, submit date and report total.

• Card transactions still in Available Expenses

  Build this

  Starts

  Every Monday at 9:00

  Step 1

  Get the company card transactions in Available Expenses.

  Step 2

  Keep the ones with a transaction date more than 7 days ago.

  Step 3

  Email you the list with transaction date, vendor name and amount.

• Report status changes, posted to your accounting system

  Build this

  Starts

  Every day at 18:00

  Step 1

  Get the expense reports in the Report Library.

  Step 2

  Keep the reports whose approval or payment status changed since the last run.

  Step 3

  Post report name, statuses, report total and currency to your webhook.

You can run a workflow by hand on every plan, Free included. Schedules and webhook triggers come with the paid plans, from $29 a month.

Once built, one call from your code

Once you have built a method, it is one POST to /v1/runs from your backend, or a tool an AI agent calls over MCP. This is what “Get expense reports” would look like.

curl https://api.fous.com/v1/runs \
  -H "Authorization: Bearer $FOUS_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "method": "concursolutions.com/get_expense_reports",
    "input": {
      "view": "Active Reports"
    }
  }'

{
  "status": "completed",
  "data": {
    "reports": [
      {
        "name": "Northwind customer visit, Chicago",
        "report_date": "2026-11-06",
        "submit_date": null,
        "approval_status": "Not Submitted",
        "payment_status": "Not Paid",
        "report_total": 1284.6,
        "currency": "USD"
      }
    ],
    "count": 1
  }
}

An example with invented data, not a ready-made endpoint. The method exists in your organization once you build it, and its name, inputs and fields follow your request.

Concur’s own options

SAP Concur offers APIs for expense reports, receipts, users, travel itineraries and invoices. Access starts with an agreement with SAP Concur, which then issues OAuth 2.0 credentials and sets up sandboxes; the Reports v4 API needs Concur Expense Professional or Standard Edition. Paid expenses can also be downloaded with Data Access and Export.

Read on November 12, 2026: SAP Concur developer getting started, Reports v4 API reference, Concur Expense on the SAP Help Portal.

Signing in to Concur

Concur's sign-in page asks first for your username, verified email address or SSO code, with a Remember me option. With Fous you sign in once through Concur's own sign-in with your own account. The login is sealed with AES-256, never returned by the API or written to logs, and code and AI agents never see it.

Worth knowing

API access starts with an agreement

Once an agreement is in place, SAP Concur sets up a meeting with its technical team, issues a client ID and secret, and sets up sandboxes as needed.

Statuses come in the user's language

Reports v4 returns approvalStatus and paymentStatus in the user's language, with stable codes such as A_NOTF (Not Submitted) and P_NOTP (Not Paid) beside them. Match on the codes.

Your company's configuration decides a lot

Whether approvers can adjust amounts or send single expenses back depends on configuration. Card transaction details show only if the vendor sends them and your company displays them.

Approvals arrive in several places

Reports to approve appear under Approvals and Required Approvals, in the notifications center on the web only, and by email if you turn it on in Profile > Profile Settings > Expense Preferences.

More in Accounting, tax and ERP software

• CONTPAQi
• Comarch ERP Optima
• Cegid Loop
• Domínio Sistemas
• Xero Practice Manager
• a3innuva
• Confirmation
• MyCodabox
• Xero bank feeds
• Exact Online
• Twinfield
• Sage Intacct
• CCH Axcess
• TallyPrime
• TaxDome
• Drake Tax
• Dext Prepare
• Lexware Office
• MYOB Business
• 弥生会計

Other industries: Meta Business Suite and Ads Manager, ALLDATA Repair, mobile.de Händlerbereich, RUN Powered by ADP, Oracle Textura Payment Management, Ingram iPage.