#10542 [Master] - Slice 638097: [Expense Agent] Enable simple interim approval scenario
Expense reports now support a two-stage approval flow with interim and final approvers in agent mode, with automatic prepopulation of the final approver from the user's designated approver.
- 10files
- 9AL files
- 9objects
Pull request · merged into main (BC30) on 2026-08-27 by v-rohangarg20 · 10 files (+962 -11), 9 AL · feature · tier official · reviewed (checked by Opus)
What changed
- Added interim and final approver fields to expense report headers with validation rules
- Introduced ‘Interim Approved’ status for two-step approval workflow (or single-step when no interim approver set)
- UI and API support for assigning interim approvers, restricted to agent mode
- Guards prevent interim approver conflicts (not submitter, not final approver, required selection)
- Activity logging tracks interim approver assignments and interim approvals
- Behaviour changes for users or extensions.
AL objects touched
- Page 6969 “Approver View API”, ExpenseAgent: modified
- Page 6928 “Expense Reports API”, ExpenseAgent: modified
- Enum 6922 “Expense Activity Event Type”, ExpenseAgent: modified
- Codeunit 6901 “Expense Report Approval Mgmt”, ExpenseAgent: modified
- Enum 6910 “Expense Report Status”, ExpenseAgent: modified
- Page 7091 “Accountant Expense Reports”, ExpenseAgent: modified
- Codeunit 6984 “Release Exp. Report Document”, ExpenseAgent: modified
- Page 6910 “Expense Report”, ExpenseAgent: modified
- Table 6906 “Expense Report Header”, ExpenseAgent: modified
Context
- Work items: AB#638097
- Labels: AL: Apps (W1), Team: Finance
- Systems: development
- From the description: “Enables a simple two-stage interim approval step for expense reports in agent mode.”
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).