#11333 Align travel request APIs with employee travelers and expense report lifecycle

Pull request · merged into main (BC30) on 2026-09-17 by claudiuciumedean · 18 files (+1384 -40), 13 AL · feature · tier official · reviewed (checked by Opus)

What changed

Employees API gains filterable isExpenseUser field to distinguish expense-enabled employees
Travel request approval automatically creates Expense Reports for the Requested For user and prevents duplicate creation
Travel requests expose employees as a read-only navigation property filtered by SystemId
Owner-scoped report recreation allowed after draft deletion if no existing posted history exists
Added indirect permissions and nonunique lookup keys to support these operations
Behaviour changes for users or extensions.

AL objects touched

Page 6917 “Employees API”, ExpenseAgent: modified
Page 7134 “Travel Requests API”, ExpenseAgent: modified
Page 7103 “Travelers API”, ExpenseAgent: modified
Table extension 7110 “Expense Employee”, ExpenseAgent: added
Table 6906 “Expense Report Header”, ExpenseAgent: modified
Table 6915 “Posted Expense Report Header”, ExpenseAgent: modified
Table 6916 “Posted Expense Report Line”, ExpenseAgent: modified
Table 6923 “Expense User”, ExpenseAgent: modified
Permission set 6952 “Expense Agent - Objects”, ExpenseAgent: modified
Codeunit 7133 “Travel Request Approval”, ExpenseAgent: modified
Query 7111 “Travel Request Employees”, ExpenseAgent: added
Table 6938 “Traveler”, ExpenseAgent: modified
Table 6840 “Spend Request”, Base Application: modified

Context

Work items: AB#626966, AB#650245, AB#650277
Labels: AL: Apps (W1), ExpenseManagement, Team: Finance
Systems: development, finance
From the description: “Aligns the Expense Agent travel request and expense report API flow used by the web client.”

Source: metadata of a merged pull request in microsoft/BCApps (bcapps): title, labels, changed paths and counts, with a summary in our words. No source text and no description beyond one short quote (D10, D61).