For the system to automatically assign credit card transactions, you have to be sure to have assigned the travel expense type a ‘further procedure’, when assigning credit card transaction expense keys to travel expense types,

This further procedure determines the trip status with which the system is to save the trip after it has created a credit card document. To do so, the system compares the current trip status with the trip status stored in the further procedure. From these two trip statuses, the system chooses the status with the lower further processing priority. This prevents, for example, trips that have not yet been approved from being approved and sent on to accounting as a result of automatic processing in credit card clearing.

If you have assigned a credit card transaction key to a travel expense type for which the system settings require you to enter additional receipt information, the system can not create credit card documents in the trip for the credit card transactions of this key. The system stores these credit card transactions in the document buffer.

You have to have started the transfer of credit card transactions in an update run with one of the processing parameters Documents to empty trips only or Import receipts also, if any, which allow automatic assignment.

If the relevant personnel number is locked when a data record is imported, the system can not create a credit card document in the trip from the credit card transaction. This is always the case when a Travel Management function accesses a personnel number to make changes or when HR master data is edited in Personnel Management. The system stores these credit card transactions in the document buffer.