Differentiating Between Attendee Status and Attendee Types

Objective

After completing this lesson, you will be able to compare Attendee Status and Attendee Types.

Best Method for You

As discussed previously, the Attendee Status field is not supported on the SAP Concur mobile app. This means that users cannot add attendee details to their FBT eligible expenses on the mobile app, that step must be done on the web version. This causes frustration as users need multiple tools to complete an expense.

While not commonly used, the Status field is also not supported on the expense level Attendee Import Template.

The alternative solution is to create two different types of employee attendees: Employee Not Traveling and Employee Traveling. This means that users can do everything related to FBT on the mobile app. However, this can cause confusion and require extra training for users in regions that do not need to account for FBT.

Summary

The table below summarizes the results of the matching activity. While the Attendee Types method seems to have more cons than pros, the ability to use the feature on both the web and mobile platforms outweighs all the cons for most companies.

 ProsCons
Attendee StatusCan be configured to only impact your Australian users.Not supported on the SAP Concur mobile app.
Minimal training requirements.Not supported on the expense level Attendee Import.
Attendee TypesWorks on both mobile and web versions.Impacts all users.
 Can cause confusion for non-Australian users.
 All users require training.

In the end, there is no "right" way to configure the feature. You need to do what you think is best for your users. The proceeding lessons will cover both options.

The next several lessons will cover the details of configuring FBT in your site. The first step is configuring Attendee Types.

Log in to track your progress & complete quizzes