This column contains the transaction ID of the record in error. It is taken from positions 375-389 in the KR1025 import file.

If the Batch ID, Batch Type, and Transaction ID already exist for the record being imported, this column contains the hard-coded values of the Batch ID, Batch Type, and Transaction ID. If the error is an unexpected error, this column displays the field name in error, if the information is available. If it is a known error, this column displays the field name.

If the Batch ID, Batch Type, and Transaction ID already exist for the record being imported, this column displays the values for the Batch ID, Batch Type, and Transaction ID. If the error is an unexpected error, this column displays the field information, if available for the field in error. If it is an expected error, this column displays the field information.

If the Batch ID, Batch Type, and Transaction ID already exist for the record being imported, this column displays the following information: "The Batch ID, Batch Type and Transaction ID combination already exists in the Batch Expense Edit table."

If the error is an unexpected error, this column displays the following: "The record could not be imported due to an unexpected error."

If is an expected error, this column displays the error. Some examples are:

• Invalid Date — For Expense Date, Departure Date, Return Date, Start Date, End Date
• Invalid Number — For Ticket Number, Unit Number, Number of Days
• Invalid — For Transaction Currency Code
• Must be equal to system base currency — For Billed Currency Code
• Invalid Amount — For Incurred Amount, Tax Amount