Enum 6910 "Expense Report Status"
ExpenseAgent · Microsoft.ExpenseAgent
Across versions
- BC23-28not present
- BC29-30present
ExpenseAgent · Microsoft.ExpenseAgent · BC29-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Caption | Expense Report Status |
| Access | Internal |
Values
| Ordinal | Name | Caption | Notes |
|---|---|---|---|
| 0 | Open | Open | |
| 1 | Pending Approval | Pending Approval | |
| 2 | Released | Released | |
| 3 | Approved | Approved | |
| 4 | Rejected | Rejected | |
| 5 | Processed for Payment | Processed for Payment | |
| 6 | Completed | Completed | |
| 7 | Interim Approved | Interim Approved |
Recent changes
- 2026-08-27 #10542 [Master] - Slice 638097: [Expense Agent] Enable simple interim approval scenario (main, BC30, feature)
- 2026-08-04 #9859 [Master] - Move Expense Agent (Preview) app into BCApps (main, BC30, feature, added)
Ask your agent
Procedure bodies are not stored here (D10). For a procedure body or the calls of one procedure, ask bc-code-atlas (external, by Stefan Maron, MIT; default corpus w1-28), which the bc-observatory plugin connects: bcatlas_resolve_node(object_type: "enum", object_name: "Expense Report Status"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.