SAP MTR allows employees to capture their travel expenses in a disconnected mode and send the data to the back-end system once a connection is established, also known as synchronization. In both SAP MTS and MTR, the back-end application logic is mirrored with the offline application because the business logic from the back end was recoded for the mobile device. You can access recorded SAP MTR data in the back end as soon as the synchronization is over. Depending on the amount of data you are loading, the synchronization takes between 30 seconds and five minutes to complete. SAP MTR allows users to choose which trips should be synchronized, which is useful if some incomplete expense reports were created offline and are not ready to be sent to the backend yet.

SAP MTR offers the following functionality:

• At trip level, you can enter the general data, additional destinations, mileage, and advances
• Any amount of receipts can be attached to a trip
• Additional destinations can be linked to a receipt
• Receipt itemization is available, very similar to the ESS itemization wizard
• Synchronization is triggered by the user
• Any trips can be changed or deleted after their creation, whether they were created online or offline
• Report simulation is possible for any trip although an initial network connection is required to get the report. After the report is downloaded you have access to it offline.
• Travel requests and travel plans can be displayed
• Expense reports can be created from any travel request or travel plan
• SAP MTR automatically downloads credit cards, which you can assign to any expense report
• F4 help is available for cost assignment objects
• Cost assignment at receipt level can either be percentage or absolute values
• 90-days rule compliant (90 days rule is a legal requirement for taxation in Germany but can also be used in other countries. If a traveler is going to a customer at the same address for more than 90 days in the same fiscal year, this is no longer considered a business trip with tax free reimbursement of per diems).
• Uses the mCAF enhancement concept to easily integrate customer-specific enhancements

When you create a trip offline, you can view a rough estimate of the reimbursement amount. This is just an estimate, however, because SAP ERP calculates the actual amount in the back end after the synchronization completes. After the trip is synchronized, the actual reimbursement amount is available to SAP MTR and its users.

The checks SAP MTR performs are not as extensive as the checks of other Travel Management UIs, which are constantly linked to the SAP back end. If any error messages appear during synchronization, SAP ERP sends the erroneous trips to SAP MTR with all relevant error messages so the user can fix the errors before submitting the trip again. In the event that a trip was changed offline and online at the same time, a conflict resolution screen appears in SAP MTR, which allows the users to see both expense reports simultaneously and determine which report should be recorded.