We're using expense management and when importing transactions where the card number is for example '6080', we get below message in the data management import job.Results. The credit card import can't be completed because the card ending in 6080 is a credit card number and is not allowed in the system. Please correct the import file to contain numbers in the format entered in the employee credit card form.Results. Validations failed while writing entity recordThese 4 digits are what identify a card(employee) in the bank's transaction file. I also get similar error when I try to setup 6080 as the card number under HR>Employee>Expense>Credit Card but have found a work around where i'll start with 16080 and it will let me save the last 4 digits. It's same issue on PU31/10.0.7 and PU33/10.0.9.
The overall workaround I did was I changed the card number to something that system would accept but cannot continue doing that as the transaction file will always have 6080 and what if in future there is an actual card with the number i'm using here.
Has anyone else faced this issue with credit card transactions import? How did you resolve it? Let me know please.
I have to be honest, never came across that specific error before - but we're on 10.0.8/PU32, and our file comes in with ************1234 as the number, and that's how I entered it into the employee record, although it is not showing the * in the employee record at all.There is a setting in the expense management parameters that determines how your credit card numbers are stored in the system:
You might want to play around with that to see if it helps? Good luck!
If you've found this thread useful, dive deeper into User Group community content by role