Joule Expense Report Actions

The transactional Concur Expense use cases of Joule, SAP's conversational assistant embedded in SAP Concur. SAP documents natural-language use cases that create, change and delete expense data on behalf of the signed-in user, including creating, copying, editing, deleting, submitting and recalling expense reports, adding, editing and removing expense items and itemizations, and searching, adding and creating attendees. Informational help search, the Joule Premium Expense Automation Agent and the Expense Report Validation Agent are documented separately and are not part of this record.

Recorded characteristics

Function

SAP states that Joule in SAP Concur solutions supports two conversational types, transactional and informational, and that in transactional cases Joule gives users "easy and quick access to the tasks they want to perform", giving the example that when a user says "I want to submit my expense report", Joule "captures their prompt and then initiates the expense submission process". SAP's current Concur Expense transactional use-case table (SAP Concur Solutions AI Resources, version 2026_08) lists state-changing use cases: Create report ("Creates an expense report"); Copy expense report ("Copies an existing expense report"); Edit expense report ("Edits expense report name and date"); Edit expense item and Edit expense itemization (each "Edits the expense amount and date"); Add expense item; Add expense itemization; Adds hotel itemization; Remove expense item, Remove expense itemization and Remove expense report (each "Deletes the selected..."); Search attendees, Add attendee ("Adds an attendee to an expense item"), Create attendee ("Creates an attendee and adds it to an expense item") and Recent attendees; Submit expense report ("Submits an expense report"); Recall expense report ("Recalls an expense report"); and "Employee confirmation agreement with report submit", which "Prompts the user to accept an employee confirmation agreement before submitting an expense report". The same table lists read-only use cases (show active reports, report header details, expense details, itemizations, attendees, warnings, receipt images, allocation view, search by name or date range) and a conversational help search. The Joule Capabilities guide lists a narrower current set of Concur Expense transactional use cases - show active reports, show report by name, date or date range, recall expense report, copy expense report, delete expense report, update expense report, add expense item, add itemization - and specifies that the Update expense report use case covers report date, report name, business purpose, start date and end date. The Concur Expense release note for Joule states that the integration "allows users to manage and modify expense report information using natural language queries" and that "it supports actions such as editing, copying, submitting, and recalling expense reports". All use cases are documented as user-initiated conversational prompts; SAP notes for several of them that "Joule will prompt you for additional information required" to complete the action.

Data access

SAP documents Joule reading the user's own Concur Expense data for these use cases: active and searched expense reports (report name, report date, report number, report status), report header details, expense items and their details, itemizations, attendees, warnings, receipt images and allocations. SAP states that in transactional cases "Joule has the entire report in context". Documented example prompts are first-person and scoped to the speaking user ("Show my expense reports"), and the prerequisite is that "users must have the Expense User role assigned"; SAP does not document manager, delegate or arbitrary-employee access for these use cases on the pages reviewed. SAP's AI Features table records the Joule commercial model per feature and a separate "Cross Customer AI Training" column; for the Joule Concur Expense features listed there the cross customer AI training value is None.

Actions

Can take actions

External actions

Unknown

Human confirmation

Conditional

Permission basis

User permissions

Administrative control

Documented controls: Joule must be integrated with SAP Concur before it is usable. SAP's integration guide requires SAP Concur single sign-on with SAP Cloud Identity Services, matching Global User ID (GUID) mapping between SAP Concur and SAP Cloud Identity Services (imported through the 315 record flat file or Identity Provisioning service), running the Joule Booster with the SAP Concur system selected, or, for an existing Joule setup, including the SAP Concur system in an SAP BTP formation and selecting "Enable Capability Deployment" and "Enable the Joule Icon in the Integrated System". SAP states that "To access Joule within SAP Concur, an additional entitlement and authorization may be required" and directs customers to their account executive. Access can be narrowed with Joule Selective Access (Pilot mode): after Joule Pilot mode is enabled at company level, only users in the Joule Pilot User group see the Joule icon, and administrators add users either in Administration > Company Admin > User Administration > View Users (Joule Pilot section, "Enable Joule pilot for this user") or through the Identity Authentication service group plus an Identity Provisioning service synchronization job. Feature scope is governed by the Joule commercial model (Base or Premium) recorded per feature in SAP's AI Features tables, by the Expense User role prerequisite, and by the organisation's Concur Expense field configuration, since "Joule can only update a field when it is configured as editable for the user. Fields configured as read-only cannot be updated through Joule." SAP Concur separately documents a cross customer AI model training opt-out switch. No per-action enable/disable toggle for individual Joule expense use cases was found on the pages reviewed.

Default state

Disabled

Availability

SAP states that Joule is available for Concur Expense Professional/Premium Edition, Concur Expense Standard Edition, Concur Travel Professional Edition and Concur Travel Standard Edition. The Concur Expense release note "Joule for Concur Expense" (Professional and Standard editions; administrator action "Info only") records an availability target of October 18, 2025, information first published April 24, 2025 and last modified October 10, 2025, and states "Joule Base is required to use this feature." The same release note records the limitation that "This feature won't be available to new and existing clients based in China and deployed to the China datacenter. Other datacenters are not affected by this limitation." SAP's current use-case documentation is published under the production release versions 2026_08 (SAP Concur Solutions AI Resources) and LATEST/CLOUD (Joule Capabilities guide). No explicit general-availability, beta or pilot stage wording was found for the transactional Concur Expense use cases themselves, apart from the separate Joule Selective Access pilot-mode feature and the Preview release-note sections, which are not treated as the current state here.

Licensing

Documented requirements: Joule Base for the Concur Expense transactional and informational use cases; Joule Premium for the separately documented Expense Automation Agent; Concur Expense Professional/Premium or Standard edition; the Expense User role for end users; SAP Cloud Identity Services and SAP BTP for the integration; and a possible additional entitlement and authorization to access Joule within SAP Concur. SAP's AI Features tables record a "Joule Commercial Model" value of Base or Premium per feature. No consumption, credit or message-based pricing model for these Concur Expense use cases was found on the pages reviewed.

External model or provider

Not established

Limitations and uncertainty

Recorded boundaries and open questions: (1) Scope. This record covers only the transactional Concur Expense use cases of Joule. SAP documents informational use cases (summarised answers and links to Concur Expense end-user help) and separate AI features - the Joule Premium Expense Automation Agent, which "automatically creates your expense reports in the background, with no start or set up required", and the Expense Report Validation Agent, which scans a report, identifies missing or inconsistent details and suggests corrections the user can apply - as distinct entries; neither is attributed to this capability. The Booking Agent is a Concur Travel agentic feature. (2) Two SAP sources currently list different use-case sets. The SAP Concur Solutions AI Resources table (version 2026_08) is the broader list and includes Submit expense report, Create report, attendee actions and removals; the Joule Capabilities guide table lists ten Concur Expense transactional use cases and does not list submit, create report or attendee actions. Both are current SAP primary documentation and both are recorded here; the difference is not explained by SAP on those pages. (3) Editable fields. SAP documents editing at field level only as: expense report name and date (AI Resources) or report date, report name, business purpose, start date and end date (Joule Capabilities guide); and expense amount and date for an expense item or itemization. No documentation was found for Joule changing expense type, allocations, payment type, currency, custom fields or receipt attachments. SAP adds that fields configured as read-only for the user cannot be updated through Joule, and that organisation-specific additional required fields not collected in the conversation may cause an action to fail, in which case the user should complete it in Concur Expense instead. (4) Execution boundary. SAP describes Joule as capturing the user's prompt and initiating the corresponding Concur Expense process; the persistent change is made by Concur Expense. SAP does not publish the internal call chain, service identity or API used by these use cases. (5) Submission is not approval. Submit places the report into the Concur Expense workflow; SAP documents no Joule authority to approve, audit, reimburse, post accounting entries or initiate payment, and changing or submitting an expense report is not money movement. No documented Joule authority after submission was found, other than the documented Recall use case. (6) Recall. SAP's Joule pages state only that Joule recalls an expense report; workflow-stage, ownership, approval-state and company-configuration restrictions documented for the ordinary Concur Expense recall feature are not connected to Joule on those pages and are therefore not attributed here. (7) Human confirmation is recorded as conditional: SAP documents one explicit confirmation use case, "Employee confirmation agreement with report submit", which prompts the user to accept an employee confirmation agreement before submitting, and documents Joule prompting for additional information needed to complete several actions; no general per-action confirmation requirement for editing, copying, deleting, recalling, itemization or attendee actions is documented. (8) Permission basis is recorded as user_permissions on the strength of the Expense User role prerequisite and the statement that Joule can only update a field configured as editable for the user; SAP does not document a separate Joule runtime identity, service account or integration user for these Concur Expense actions, and the integration is built on GUID-matched single sign-on between SAP Concur and SAP Cloud Identity Services. (9) External action is recorded as unknown: every documented action changes state inside Concur Expense, and SAP makes no affirmative statement on these pages about whether these Joule use cases can or cannot change state in systems outside SAP Concur. (10) Model and provider are not established: no model or provider statement specific to Joule's Concur Expense transactional use cases was found. (11) Availability of individual use cases may vary by edition, region and rollout; the China datacenter exclusion is documented, and the Preview sections of the Concur Expense release notes were not used as evidence of current behaviour.

Evidence

• Transactional Use Cases (Joule Use Cases in Concur Expense) - SAP Concur Solutions AI Resources

  Supports: Function · Actions · Data access · Human confirmation · Permission basis · Availability · Limitations · Primary source

  Lists the Concur Expense transactional use cases including Create report, Copy expense report, Edit expense report, Edit expense item, Edit expense itemization, Add expense item, Add expense itemization, Adds hotel itemization, Remove expense item, Remove expense itemization, Remove expense report, Submit expense report and Recall expense report.

  Describes each state-changing use case in verbs of persistent change: creates, copies, edits, adds, deletes, submits and recalls.

  Lists the read-only use cases and the data shown: active reports with report name, date, number and status, report header details, expense details, itemizations, attendees, warnings, receipt images and allocation.

  Documents the use case "Employee confirmation agreement with report submit", which prompts the user to accept an employee confirmation agreement before submitting an expense report.

  States the prerequisite that users must have the Expense User role assigned to use these use cases.

  Records the commercial model per use case, with the transactional expense use cases marked Base and the Expense Automation Agent marked Premium.

  Shows that attendee handling is limited to searching, adding, creating and listing recent attendees on an expense item, with no documented edit or removal of attendees.

• Joule Use Cases in Concur Expense: Transactional Use Cases - Joule Capabilities guide

  Supports: Function · Actions · Data access · Permission basis · Admin controls · Limitations · Human confirmation · Primary source

  Lists the Joule Capabilities guide set of Concur Expense transactional use cases with example prompts: show, recall, copy, delete and update expense reports and add expense items and itemizations.

  Documents Recall expense report, Copy expense report and Delete expense report as user-invoked actions on an existing report identified by name or report id.

  Documents searching and displaying the user's own active expense reports by name, date, date range or report number.

  States that users must have the Expense User role assigned, and that Joule can only update a field when it is configured as editable for the user, with read-only fields not updatable through Joule.

  Records the Configured Expense Fields constraints, under which organisation-configured additional required fields not collected in the conversation may prevent an action from completing.

  Enumerates the exact updatable expense report fields as report date, report name, business purpose, start date and end date, and notes that Joule prompts for additional information needed to add an expense item or itemization.

  Documents Joule prompting the user for additional information required to complete an action, without stating a general confirmation requirement for these use cases.

• Joule in SAP Concur Solutions - SAP Concur Solutions AI Resources

  Supports: Function · Actions · Availability · General · Primary source

  Defines Joule transactional cases in SAP Concur and gives the example that when a user says they want to submit an expense report, Joule captures the prompt and initiates the expense submission process.

  States that Joule gives users quick access to the tasks they want to perform and has the entire report in context for itemization questions.

  Lists the solutions for which Joule is available: Concur Expense Professional/Premium Edition, Concur Expense Standard Edition, Concur Travel Professional Edition and Concur Travel Standard Edition.

  Separates transactional, informational and agentic conversational types, with the Booking Agent given as the agentic example in Concur Travel.

• SAP Concur Expense AI Features

  Supports: Licensing · Availability · Data access · Limitations · Primary source

  Records the Joule commercial model per Concur Expense AI feature, with Joule Premium required for the Expense Automation Agent and Joule Base for the Expense Report Validation Agent.

  Records edition applicability of Concur Expense AI features as Professional and Standard.

  Records a Cross Customer AI Training value per feature, listed as None for the Joule Concur Expense features in the table.

  Documents the Expense Automation Agent and Expense Report Validation Agent as separate named features, supporting their exclusion from this capability record.

• Joule for Concur Expense - Concur Expense Professional Edition Release Notes

  Supports: Function · Actions · Availability · Licensing · Limitations · Default state · Primary source

  States that the integration allows users to manage and modify expense report information using natural language queries and supports actions such as editing, copying, submitting and recalling expense reports, and managing expense itemizations and attendees.

  Confirms submission and recall of expense reports as documented Joule actions in Concur Expense.

  Records Professional and Standard editions, administrator action "Info only" and an availability target of October 18, 2025, with information last modified October 10, 2025.

  States that Joule Base is required to use this feature.

  Records that the feature is not available to new and existing clients based in China and deployed to the China datacenter.

  Points to the integration documentation for feature activation, indicating that use follows an integration procedure rather than being present by default.

• Integrating Joule with SAP Concur - Integrating Joule with SAP Solutions

  Supports: Default state · Admin controls · Permission basis · Primary source

  Sets out the setup required before Joule is usable in SAP Concur: single sign-on with SAP Cloud Identity Services, Global User ID mapping, the Joule Booster with the SAP Concur system selected, or inclusion of the system in an existing SAP BTP formation.

  Documents the formation options "Enable Capability Deployment" and "Enable the Joule Icon in the Integrated System" that deploy the Concur scenarios and activate the Joule icon.

  Documents that the Global User ID must match between SAP Concur and SAP Cloud Identity Services for Joule to be operational for users, tying Joule use to the signed-in Concur user identity.

• Integration with SAP Concur - Integrating Joule with SAP Solutions

  Supports: Licensing · Default state · Primary source

  States that an additional entitlement and authorization may be required to access Joule within SAP Concur.

  Lists the integration steps required to reach a working Joule integration with SAP Concur, including trust configuration, trusted domains, user attributes and the Joule Booster.

• Joule Selective Access - Pilot Mode Onboarding

  Supports: Admin controls · Default state · Primary source

  Documents Joule Pilot mode, under which only users in the Joule Pilot User group see the Joule icon once Joule is enabled, managed in Concur user administration or through Identity Authentication and Identity Provisioning services.

  States that enabling pilot mode after activation removes Joule access from users who previously had it unless they are added to the pilot group.

• Expense Automation Agent - Joule Capabilities guide

  Supports: Limitations · General · Primary source

  Describes the Expense Automation Agent as a separate Joule Premium agent that creates expense reports automatically in the background with no start or setup required, distinguishing background automation from the user-initiated conversational actions recorded here.

  Confirms that the background expense report creation behaviour belongs to a separately documented agent rather than to the transactional Concur Expense use cases.