Page 6901 "Expense Rule Card"

ExpenseAgent · Microsoft.ExpenseAgent · BC29-30 · source at ea08af5e · facts from BC29

Properties

Property	Value
Caption	Expense Rule Card
SourceTable	Expense Rule Header
PageType	Card
ApplicationArea	Basic, Suite

Fields on this page

Layout controls in source order, grouped by the container they sit in. Shows: the table field a control is bound to (or its expression as written); ToolTip: the control’s own, else the bound field’s (marked).

Group	Control	Shows	ToolTip
General	Expense Category Code	Expense Category Code	Specifies the expense category for this rule.
	Expense Location	Expense Location	Specifies the expense location for this rule.
	Effective Date	Effective Date	Specifies when this rule becomes effective.
	Justification Required	Justification Required	Specifies when justification is required for expenses under this rule.
	Currency Code	Currency Code	Specifies the required currency code for expenses under this rule. Leave blank if any currency is allowed.
	Unit of Measure Code	Unit of Measure Code	Specifies the required unit of measure code for mileage expenses under this rule (e.g., Miles, Kilometers). Leave blank if any unit of measure is allowed.
Merchant Requirements	Required Specific Merchant	Required Specific Merchant	Specifies if a specific merchant is required for this expense category and location.
	Specific Merchant Name	Specific Merchant Name	Specifies the required merchant name.
Content	Rule Conditions	part Page 6902 “Expense Rule Conditions”	—

Procedures

1 local procedures, no public ones.

Triggers

OnAfterGetCurrRecord

Relations

source table Table 6927 “Expense Rule Header”

Pages and codeunits on this table

Page 6900 “Expense Management Rules” (card page)

Recent changes

2026-08-14 #10020 [Master] - Bug 641894: [Expense Agent] [Rules] Mileage expense should not validate require receipt number rule (main, BC30, fix)
2026-08-04 #9859 [Master] - Move Expense Agent (Preview) app into BCApps (main, BC30, feature, added)

Documented on Microsoft Learn

Set Up Expense Categories, Rules, and Policies

Source: AL metadata extracted from the code (names, ids, signatures, properties); no code bodies (D10).

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: "page", object_name: "Expense Rule Card"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.