To configure this feature for business admin users:

1. Ensure Configuring Events Management is complete.

2. Grant the following permissions:

   Object	Object Permission	Object Types	Fields	Field Permission
   expense_type__v	CRED	expense_type__v	active__v country__v expense_code__v expense_type_identifier__v external_id__v included_in_speaker_cap__v meal_expense__v name__v parent_expense_type__v	Edit

To configure this feature for end users:

1. Ensure Configuring Events Management is complete.

2. Grant the following permissions:

   Object	Object Permission	Object Types	Fields	Field Permission
   expense_type__v	R	expense_type__v	active__v country__v expense_code__v expense_type_identifier__v included_in_speaker__v meal_expense__v name__v parent_expense_type__v	Read

Business admin users can define custom expense types for their end users by creating expense_type__v records with the following attributes:

• name__v – The name of the expense type
• expense_code__v – The appropriate expense code of the expense type
• active__v – This check box must be selected to display as available to end users
• expense__type_identifier__v – Enter the appropriate text to help end users select the correct expense type
• parent_expense_type__v – Used to define expense types and sub-types of up to two levels
• country__v – Defines which country the expense type should be available in

Meal and Speaker Expense Types

Expense Types can also be designated as counting toward a speaker cap, or being marked as a meal expense. This designation is based on the following two check boxes:

• meal_expense__v
• included_in_speaker_cap__v

One or both of these check boxes can be selected per Expense Type.

For example, the meal_expense__v check box can be selected for two expense types, one for food and one for beverages. The event's actual_meal_cost_per_person__v field automatically calculates based on the sum of all meal-related expense lines and the total number of attendees with a status of attended__v or signed__v.

The included_in_speaker_cap__v check box tracks the total transfer of value to an individual speaker. This value is tracked in the year_to_date_spend__v field on the em_speaker__v object and automatically resets each year. Expenses logged against an Event Speaker record or an account__v record count toward this cap, since both Event Speakers and accounts can be directly related to a speaker record. See Managing Speaker Caps and Utilization for more information.

See Managing Expense Headers and Expense Lines or Managing Expense Estimates for more information on selecting expense types for an expense or expense estimate.