Understanding credit card import log errors

Error or Warning	Message	Description	Action
FATAL ERROR 3000 – Cannot read the data	Error occurred on line #<line number> <jre exception information>	The credit card import tool cannot read the data on the indicated line.	Check the file. Contact the credit card issuer providing data for an undamaged file, only if the import file is damaged. Contact the Infor Expense Management customer support, if the import file is not damaged.
FATAL ERROR 3001	Parameters incomplete: -f <Card Type> -d <InputFile> -l <Log File> -c <Currency Code>") or <Card Type> <Input File><Log File> <Currency Code>	Not enough in-line command parameters provided.	Verify the parameters specified on the command line.
FATAL ERROR 3003	File format parameter unrecognized.	The file format corresponds to the <Card Type> specified on the command line and must match the entry in the alcc_import_for-mat.cc_format_name table for the appropriate credit card type.	Verify that the entry in the alcc_import_format table matches the command line parameter for the credit card type.
FATAL ERROR 3004	Could not connect to database.		Check the database connectivity. Check the regular issues that often cause a database connectivity problem. If the disconnection occurs in the middle of importing, the error may be related to a bad data problem. Note the data line where importing stops.
FATAL ERROR 3005	IOException -- Unable open the file.		Ensure that there are read/write permissions on the directory where the log files are created.
FATAL ERROR 3007	I/O Failure	Often refers to a data-related problem.	There are other messages that follow or precede this message that helps to identify the problem. Call the Extensity Customer Support to report this problem and provide them with a copy of the ccimport.log file.
FATAL ERROR 3009 – Problem at the SQL level: Could not open table? Bad query?	<jre exception information>	The credit card import tool cannot process an SQL statement. The import tool cannot open a table because of an incorrect SQL query.	Check the file. Contact the credit card statement, if the import file is damaged. The import tool at the SQL level: issuer providing the data for an undamaged file.
FATAL ERROR 3011	Problem at the SQL level; unable to open table? Bad Query?		Database related problem. Call the Extensity Customer Support to resolve. Email the ccim-port.log file to Extensity Customer Support.
FATAL ERROR 3012 - Database password not found in extensity-appserver.properties. Cannot continue.	<jre exception information>	The credit card import tool cannot access the database as the tool is unable to find the database password in the extensity-appserver.properties file.	Check the extensity-appserver.properties file. Add the password, if the file does not contain the database password.
FATAL ERROR 3013	Cannot find java class file.	This occurs when a JAVA class configured for the CC Feed does not exist. The java class file name is listed along with this error in the ccimport.log file. Note the class file.	Code related problem. Call the Customer Support to resolve. Provide the java class file name to Extensity Customer Support.
FATAL ERROR 3014	The data file has a bad data file format.	Occurs often because a wrong data file is used.	Verify the checksum for the data file received from the credit card vendor. Check with the credit card vendor for the file accuracy. The file may be corrupted while being sent over from the credit card vendor. For example, the data file header is not in a correct format.
FATAL ERROR 3015	The tenant <tenant> was not found.	This message means that the database connection information in the central database for the tenant specified is invalid.	Check the connection information in the central database for the tenant.
FATAL ERROR 3016	You have specified the tenant as <tenant> but this installation is not multi-tenant enabled.	You attempted to run the import process under the specified tenant but the installation is not multi-tenant.	Do not specify the -tenant argument when starting the CC feed.
FATAL ERROR 3017	A tenant required to be specified.	You attempted to run the import process on a multi-tenant installation without specifying a tenant.	You must specify the -tenant argument on the command line when starting the CC feed.
FATAL ERROR 3018	The default currency is specified as USD but the feed is for European countries. This is a configuration error.	You attempted to run the Amex4322 importer but specified the currency as USD. The Amex4322 feed is for European feeds.	Remove the USD specification.
FATAL ERROR 3019	Could not initialize importer: <message>	An unexpected error is encountered. The message provides more details.	Contact your Expense Management administrator.
FATAL ERROR 3020	Amex 1080 import must have parameter cc. AmexLevel3 ReferenceNumber Type set to GL1025 or KR1025, depending on which feed you use to import Amex transactions.	Parameter cc.AmexLevel3 ReferenceNumber Type is not set to GL1025 or KR1025. When the Amex 1080 (hotel folio) feed is imported, the application tries to link the folio records to an existing transaction. The folio record is saved with a reference number that matches to the transaction, if the transactions are missing (usually because the 1080 is imported before the 1025 feed). This parameter lets the application know whether to use the reference number for the KR1025 feed or for the GL1025.	Set the parameter to GL1025 or KR1025.
WARNING 1001	Unrecognized Record Type	The encountered record type number is not defined in this CC feed process. This occurs often because a wrong data file is used.	The credit card file includes record types that are not defined. Check with the credit card vendor regarding the unrecognized record type. The record type is located in the data file sent from the credit card vendor. The location of the Record Type is provided in the Credit Card Mapping document.
WARNING 1002	<param1>; data on this line not imported.	"<param1>" This can be any message and the message is used to indicate when a bad data field has been encountered. For example, a non-integer character is read as an integer.	There are other messages that precede this error message, which provide more insight in to the issue.
WARNING 1003	Credit card not assigned to user: The card must be assigned to a user using System Administration Tool.		The card must be assigned to a user using System Administration Tool. The User screen in the SAT provides the functionality to attach or un-attach credit cards.
WARNING 1005	Unrecognized Card: Transaction # <param1> refers to card # <param2>, which is not in the database. The transaction was not imported.	Card is not in the database.	Check the user name on the transaction line in the credit card data file. Each line in the credit card data file represents a transaction line or a card data line. More detailed information on transactional data is provided in the credit card mapping file. Verify the card number in the alcc_card table. Card number can also be verified in the User Profile screen using the SAT application and in the data file as described above.
WARNING 1006	Multiple Cards Found with Same Number: There are <param1> charge cards in the database that have the same account number (<param2>). We use the first one found.	Multiple cards in the database have the same account number. When this occurs, the card may be assigned to an incorrect person. Therefore, you require to confirm the card assignment.	Identify the Rogue Credit Card in the transaction file sent by the credit card vendor based on the positioning data provided in the credit card mapping file. Confirm the credit card user name. Un-attach the Credit card from the users who do not own the credit card using the SAT application. This can be done in the User Profile screen. Extensity imports the first User Name, the per diem tool finds the name in the file received from the credit card vendor. Delete the transaction imported from the alcc_transaction table, if the imported user name is not the correct. Also, discuss with the credit card vendor the Credit cards associated with more than one User so that they can resolve in future files .
WARNING 1007	There are <param1> currencies in the database that have the same currency code (<param2>). We use the first one found as the proper currency.	Currency codes are not set up correctly in the application.	Identify the currency codes with the same codes. Update the currency codes with the correct code, using the SAT application. Currency data is located in the Corporate Data tab on the SAT application.
WARNING 1008	There are <param1> merchants in the database that have the same name (<param2>), city (<param3>), and VAT number (< param4>). We use the first one found as the proper merchant.	Multiple merchants that match the data to be imported are found in the database.	This is often not an issue and do not affect the data integrity.
WARNING 1009	Not importing duplicate transaction: Card Number is <param1>. Amount is <param2>. Posting Date is <param3>.	This often occurs if the data file is imported twice.	Another transaction with the same reference number, amount, posting date, and card number is already in the database. Thus, the data is imported again.
WARNING 1010	Currency code <param1> is not in the database.	The specific currency code listed in the log is not found in the database.	Call Extensity Customer Support to verify if this is the correct currency code. If this is not the correct currency code, the transaction from the credit card vendor is invalid. Please notify the credit card vendor. If the currency code is valid, the new currency code must be setup in the database, using SAT. Extract the transaction from the Out.txt file to a new file and re-run ccimport to bring in this transaction once the new currency code is setup.
WARNING 1011	Transactions that have a zero amount are not imported. Reference number is <param1>.		Transactions that have a zero amount must not be imported. This is only a warning. There must not be Zero amount transactions received from the credit card vendor.
WARNING 1012	Your alcc_sic_code table does not have a default entry. The default entry must not have the SIC code (such as, blanks or null).		Check if the alcc_sic_code table has a default entry. This error must occur, only if there is no default entry in the alcc_sic_code table. Call Customer Support to report this problem once you have verified the missing default entry in the alcc_sic_code table.
WARNING 1013	Credit Card #<param1> has been added to the database and is assigned to a user. Please verify these information. Cardholder Name: <param2> Extensity User Name: <param3>		The warning message can be used to verify information for the new users added to the application. This is not an error message.
WARNING 1014	Credit Card #<param1>: No Extensity user has the SSN associated with this card. Cardholder Name: <param2>	The ccimport program could not find a matching SSN in the database, when trying to associate a credit card to an Extensity User.	Verify if the SSN is being sent correctly from Citibank. If so, then verify the Extensity user exists in the application and also verify the SSN for that user. If all the above verifications are correct, then call the Extensity Customer Support.
WARNING 1015	Credit Card #<param1>: More than one Extensity user has the Social Security Number associated with this card. Cardholder Name: <param2>	This occurs because the same SSN is assigned to more than one Extensity user.	Find the users from the Extensity database with the specified SSN. Identify why there are more than one user who use this SSN.
WARNING 1016	Credit Card #<param1> has been added to the database but has not been assigned to a user. Invalid social security number is provided. Cardholder Name: <param2>	This occurs because the format of the SSN number is not correct. For example, the SSN number may not be a nine-digit number.	Verify if the SSN is being sent correctly from Citibank. If so, then verify if the Extensity user exists in the application and also verify the SSN for that user. Update the SSN in the application using SAT, if incorrect. Call Citibank to correct the information, if the SSN is sent incorrectly.
NING 1017	Credit Card #<param1> in the database has been assigned to a user. Please verify this information: Cardholder Name: <param2> Extensity User Name: <param3>		This is only an informative message, which indicates that a new credit card has been assigned to a user. No action is required to be taken. Obsolete.
WARNING 1018	Credit Card #<param1> in the database has been assigned to a user. Social Security Number associated with this card does not exist in the Extensity database. Cardholder Name: <param2>	This occurs only when a user is matched, using the SSN option and the target SSN is not found among the database users.	This message is not applicable to Sony, since matching is done based on SSN. If SSN does not exist in the database, then no match is identified and the card is not assigned to a user. Obsolete.
WARNING 1019	Credit Card #<param1> in the database has been assigned to a user. More than one Extensity User has the Social Security Number. Cardholder Name: <param2>	This occurs because same SSN is assigned to more than one Extensity user.	Verify if the SSN is being sent correctly from Citibank. If so, then identify the correct Extensity user for the respective SSN in the system. For all the other users associated with that SSN, update the SSN to the correct SSN. Check the data being imported for inaccuracies. Obsolete.
WARNING 1020	Credit Card #<param1> in the database has been assigned to a user. The Social Security Number is not provided with this card. Cardholder Name: <param2>	This occurs only when a user is matched using the SSN option and the target SSN is not found among the database users.	This message is not applicable to Sony since matching is done based on SSN. If SSN does not exist in the database, then no matching is done and the card is not assigned to a user. Obsolete.
WARNING 1021	Unrecognized Country Code: <param1>		Check the country code associated with this transaction. Using SAT, verify if the corresponding Country code is present in the application.
WARNING 1022	Failure to locate merchant location: <param1>		Merchant location is not imported for Sony. So, this warning message is not applicable.
WARNING 1023	Not importing duplicate card: Card number = <param1>	This can be ignored since the bank regularly provides repeated card information in every new transaction.	Card information has already been imported into the application. Check with Citibank as to why duplicate entries are being sent in the data file.
WARNING 1024	Credit card account data updated: Data for card number <param1> are updated.		This is only an informative message, which indicates that a credit card data is updated. No action required to be taken.
WARNING 1025	Employee number not found in database: Emp Number#<param1> Card Number is <param2>. Amount is <param3>. Posting Date is <param4>.	This occurs only when a user is matched using an employee number option and the target employee number is not found among the database users.	This message is not applicable for Sony, since mapping is based on SSN and not employee number.
WARNING 1026	Non-integer sic code, <param1>, is used.	SIC code must be an integer.	Required to investigate why the SIC code data is not in an expected format.
WARNING 1027	Invalid SSN Number:<param1>		Required to investigate why SSN data is not in an expected format.
WARNING 1028	Merchant data updated.	Informative message.	Merchant location is not being imported for Sony, so this warning is not applicable.
WARNING 1029	Invalid Employee Number.	Employee number is not in an expected format.	This message is not applicable for Sony, since mapping is based on SSN and not employee number.
WARNING 1030	Credit Card #<param1> No Extensity user has the employee number associated with this card. Cardholder Name: <param2>		This message is not applicable for Sony, since mapping is based on SSN and not employee number.
WARNING 1031	Credit Card #<param1> More than one Extensity user has the employee number associated with this card. Cardholder Name: <param2>		This message is not applicable for Sony, since mapping is based on SSN and not employee number.
WARNING 1032	Card deactivated, Card #<param1> Required to use SAT to activate this card first before new data associated with this card can be imported. The card is not imported.		Require to use SAT to activate this card before new data associated with this card can be imported. The detailed log messages are self-explanatory.
WARNING 1034	No card reassignment allowed: Not allowed to reassign the card from the user with a UID of <param1> to another user of <param2>.		Require to know why the card has been assigned to <param1>. If <param1> is not the correct card user, required to use SAT to detach the card from <param1> and reattach the card to <param2> instead.
WARNING 1035	No data insertion allowed for <param1> The corresponding element data, <param2> do not exist	This occurs often due to missing of important data.
WARNING 1036	Inconsistent currency amounts encountered: Native and billed amounts (<param1> and <param2>) do not have a consistent sign. The transaction is not imported.	This occurs often due to a data issue.	Check the problem data.
WARNING 1037	Inconsistent date string encountered: <param1> is not a valid date under a date format of <param2>.	This occurs often due to a data issue.	Check the problem data.
WARNING 1038	Skip the invalid airline departure date, <param1>.	The corresponding transaction can still be imported even without the airline departure date.	Check airline departure date data.
WARNING 1039	Skip the invalid hotel arrival date, <param1>	The corresponding transaction can still be imported even without the hotel arrival date.	Check hotel arrival date data.
WARNING 1040	Skip the invalid hotel departure date., <param1>	The corresponding transaction can still be imported even without the hotel departure date.	Check hotel departure date data.
WARNING 1041	Same currency but inconsistent amounts encountered: Native and billed amounts (<param1> and <param2>) are not consistent.	This occurs often due to a data issue.	Check currency amounts data.
WARNING 1042	Transaction data not imported.	Informative message	This message often comes with other messages to explain why the corresponding transaction is not imported.
WARNING 1043	Skip the invalid data for hotel stay duration, <param1>	The corresponding transaction can still be imported even without hotel stay duration.	Validate the hotel stay duration data.
WARNING 1044	<param1> is not a recognizable date	The corresponding transaction can still be imported even without date.	Validate the date format.
WARNING 1045	Skip the invalid data for hotel room amount.,<param1>	The corresponding transaction can still be imported even without the hotel room amount.	Validate the hotel room amount data.
WARNING 1046	Skip the invalid data for hotel room tax 1.,<param1>	The corresponding transaction can still be imported even without the hotel room tax1.	Validate the hotel room tax1 data.
WARNING 1047	Skip the invalid data for hotel room tax 2.,<param1>	The corresponding transaction can still be imported even without the hotel room tax 2.	Validate the hotel room tax 2 data.
WARNING 1048	Skip the invalid data for hotel phone amount.,<param1>	The corresponding transaction can still be imported even without the hotel phone amount.	Validate the hotel phone amount data.
WARNING 1049	Skip the invalid data for hotel phone tax 1.,<param1>	The corresponding transaction can still be imported even without the hotel phone tax1.	Validate the hotel phone tax1 data.
WARNING 1050	Skip the invalid data for hotel phone tax 2.,<param1>	The corresponding transaction can still be imported even without the hotel phone tax2.	Validate the hotel phone tax2 data.
WARNING 1051	Skip the invalid data for hotel restaurant amount.,<param1>	The corresponding transaction can still be imported even without the hotel restaurant amount.	Validate the hotel restaurant amount data.
WARNING 1052	Skip the invalid data for hotel restaurant tax 1.,<param1>	The corresponding transaction can still be imported even without the hotel restaurant tax 1.	Validate the hotel restaurant tax 1 data
WARNING 1053	Skip the invalid data for hotel restaurant tax 2.,<param1>	The corresponding transaction can still be imported even without the hotel restaurant tax 2.	Validate the hotel restaurant tax 2 data.
WARNING 1054	Skip the invalid data for hotel service amount.,<param1>	The corresponding transaction can still be imported even without the hotel service amount.	Validate the hotel service amount data.
WARNING 1055	Skip the invalid data for hotel service tax 1.,<param1>	The corresponding transaction can still be imported even without the hotel service tax 1.	Validate the hotel service tax 1 data.
WARNING 1056	Skip the invalid data for hotel service tax 2.,<param1>	The corresponding transaction can still be imported even without the hotel service tax 2.	Validate the hotel service tax 2 data.
WARNING 1057	Skip the invalid data for hotel tip amount 1.,<param1>	The corresponding transaction can still be imported even without the hotel tip amount 1.	Validate the hotel tip amount 1 data.
WARNING 1058	Skip the invalid data for hotel tip amount 2.,<param1>	The corresponding transaction can still be imported even without the hotel tip amount 2.	Validate the hotel tip amount 2 data.
WARNING 1059	Skip the invalid data for hotel other amount.,<param1>	The corresponding transaction can still be imported even without the hotel other amount	Validate the hotel other amount.
WARNING 1062	Skip the invalid data for hotel daily room rate.,<param1>	The corresponding transaction can still be imported even without the hotel daily room rate.	Validate the hotel daily room rate.
WARNING 1063	Skip the invalid data for hotel daily room rate tax.,<param1>	The corresponding transaction can still be imported even without the hotel daily room rate tax.	Validate the hotel daily room rate tax.
WARNING 1064	Skip the invalid data for hotel laundry amount.,<param1>	The corresponding transaction can still be imported even without the hotel laundry amount.	Validate the hotel laundry amount.
WARNING 1065	Skip the invalid data for hotel gift shop amount.,<param1>	The corresponding transaction can still be imported even without the hotel gift shop amount.	Validate the hotel gift shop amount.
WARNING 1067	Skip the invalid data for hotel business center amount.,<param1>	The corresponding transaction can still be imported even without the hotel business center amount.	Validate the hotel business center amount.
WARNING 1068	Skip the invalid data for hotel health club amount.,<param1>	The corresponding transaction can still be imported even without the hotel health club amount.	Validate the hotel health club amount.
WARNING 1069	Skip the invalid data for hotel total tax.,<param1>	The corresponding transaction can still be imported even without the hotel total tax.	Validate the hotel total tax.
WARNING 1070	Unrecognized transaction code, <param1>. Record is not processed.	The first field of the VCF40 feed file is invalid. The field requires to be 1,2,3,4,6,7,8 or 9.	The visa card format might be updated. Check the latest VCF40 specifications to see if we required to support additional codes.
WARNING 1071	Transaction data updated.	The transaction is updated.	Informational message.
WARNING 1072	Credit card with account number <masked account number> not found. Record is not processed.	A card record found in the Visa VCF40 feed with a transaction code UPDATE but the record does not exist in the alcc_card table. Therefore, the application cannot update the data. This applies to the Visa importer only.	The transaction code requires to be ADD_OR_UPDATE (4) or ADD (1) for the record to be added.
WARNING 1073	Transaction with reference number <reference number>, not found. Record is not processed.	A transaction found in the Visa VCF40 feed with a transaction code UPDATE but the record does not exist in the alcc_transaction table. Therefore, the application cannot update the data. You can receive this error, if the transaction details or folio record contains a reference number not in the database. This applies to the Visa importer only.	The transaction code requires to be ADD_OR_UPDATE (4) or ADD (1) for the record to be added.
WARNING 1074	Credit card with account number <masked account number>, already exists. Card is not inserted.	A card record found in the Visa VCF40 feed with a transaction code ADD but the record already exists in the alcc_card table. Therefore, the application cannot add the data. This is applicable for the Visa importer only.	The transaction code requires to be ADD_OR_UPDATE (4) or UPDATE (3) for the record to be updated.
WARNING 1075	Transaction with reference number <param1>, already exists. Transaction is not inserted.	A transaction found in the Visa VCF40 feed with a transaction code ADD but the record already exists in the alcc_transaction table. Therefore, the application cannot add the data. This is applicable for the Visa importer only.	The transaction code requires to be ADD_OR_UPDATE (4) or UPDATE (3) for the record to be updated.
WARNING 1076	Level 3 record with folio id <param1> and sequence number <param2> is linked to a transaction with reference number <param3> that cannot be found. Record is not processed.	The level 3 data imported but not linked to the associated transaction because no transaction with the given reference number is found. This is applicable for the Amex1080 importer only.	Run the Amex KR1025 or GL1025 feed before running the 1080 feed.
WARNING 1077	Level 3 record with folio id <param1> and sequence number <param2> does not have a transaction reference number. Record is not processed.	The Amex1080 folio record contains no reference number. No record is inserted into alcc_level3_detail. This is applicable for the Amex1080 importer only.	This can indicate a corrupt 1080 feed file.
WARNING 1078	Level 3 record with transaction reference number <param1> has no folio ID. Record is not processed.	The Amex1080 folio record contains no folio ID. No record is updated into the alcc_level3_detail table. This is applicable for the Amex1080 importer only.	This can indicate a corrupt 1080 feed file.
WARNING 1079	Level 3 record with folio id <param1> has no sequence number. Record is not processed.	The Amex1080 folio record contains no sequence number. The sequence number is used as part of a unique key to check for duplicates. No record is inserted into alcc_level3_detail. This is applicable for the Amex1080 importer only.	This can indicate a corrupt 1080 feed file.
WARNING 1080	Level 3 record with folio id <param1> does not balance to the transaction amount. Record is not processed.	Only level 3 records with balance indicator, indicates that the folio amount balances to the transaction amount is processed. The Amex1080 spec states: "'[The balance indicator] indicates whether the Folio Amount balances to the Local Amount from Charge Transaction. The amounts can be different, if multiple forms of payment are used. In this case, the line items are not added up to the local charge amount. Expense Vendors must code to use only values = 1". This is applicable for the Amex1080 importer only.
WARNING 1081	Level 3 record with folio id <param1> does not have a matching transaction. Record is not processed.	An internal indicator of an Amex folio record indicates that the message does not have a matching transaction. No record is inserted into alcc_level3_detail. The Amex1080 spec states: "'Expense Vendors must code to only use values = 1". This is applicable for the Amex1080 importer only.	This can indicate a corrupt 1080 feed file.
WARNING 1082	Level 3 record with folio id <param1> and sequence number <param2> already exists. Record is not processed.	A record already exists in alcc_level3_detail for the same transaction and with the same sequence number. The record is skipped. This is applicable for the Amex1080 importer only.	Probably indicates the 1080 feed has processed more than once.
WARNING 1083	Credit card with id <param1> has an inactive payment type. User may not be able to attach transactions.	The card has a payment type that is inactive. The application do not insert or update card records with inactive payment types.	The card record can be updated or added, reactivate the payment type or modify the status of the card to an active type.
WARNING 1084	Unrecognized Card. Transaction #<param1> refers to card #<masked account number>, which is not in the database. Temporary card is created for the transaction.	A transaction refers to a card that does not exist based on the account number as the cc.createTemporaryCard parameter is True, a temporary card is created, so that the transaction is imported. The transaction is not accessible until the card record from this or another feed is processed.	Run the feed that has the card record with the same account number. The temporary card is replaced with the real card. The transaction can now be attached.
WARNING 1085	Transaction detail for transaction with reference number <param1>, not found. Record is not processed.	The transaction is for an air or rail trip but there is no leg specific detail. This is informational and applicable for the Visa importer only.
WARNING 1086	Invalid VAT amount for transaction with reference number <param1>:<param2>	The VAT amount of the transaction is in an incorrect format. This is specific to the Visa importer.	This can be a number format problem. There must be another error message near this one that display more details.
WARNING 1087	Invalid credit card limit for card with account number <param1>:<param2>	The card limit on the card record is formatted incorrectly.	This can be a number format problem. There must be another error message near this one that display more details.
WARNING 1088	Transaction with reference number <param1> already attached to an expense report--skipping update	The transaction is already attached to a line item in an expense report and cannot be updated. An importer may also generate this error when processing level 3 data and the associated transaction is already attached to a line item in an expense report.	Detach the transaction, if the card is updated. Or simply ignore the warning.
WARNING 1089	Invalid position specified in the cc.VCF40.EmpNumPosition <param1>) parameter. The value should be an integer > 0. Using 23 instead.	The cc.VCF40EmpNumMatch parameter is set to True but the cc.VCF40.EmpNumPosition parameter is not in the integer form. The importer uses the default position 23 to find the employee number. This is specific to the Visa importer.
WARNING 1090	Level 3 record with folio id <param1> and sequence number <param2> does not have a transaction reference number as specified in cc.AmexLevel3Reference NumberType.	The cc.AmexLevel3ReferenceNumberType parameter can be set to GL1025 or KR1025, based on whether the feed being processed is global or U.S. This parameter also affects where the importer searches for the transaction ID which is used to link the level record to the transaction. The error means that the level 3 data is not imported because the transaction ID is not specified. This is applicable for the Amex1080 importer only.
WARNING 1091	Level 3 record with folio id <param1> and sequence number <param2> and reference number <param3> already exists. Record is not processed.	The level 3 data is not imported because a level 3 record already exists for the given transaction and sequence number. This is applicable for the Amex1080 importer only.
WARNING 1092	String substitution <param1>	Data read by any importer can be subject to string substitution before regular processing. For example, you can require that all instances of ‘\|’ be replaced with ‘/’. You can set up this type of substitution, using the cc.substituteSubstring.enabled, cc.substituteSubstring.find and cc.substituteSubstring.replace parameters. Whenever a substitution occurs, a warning message is written to the log. Additional information such as record type, tag, element, or field can also be written.	Informational only

FATAL ERROR 3000 – Cannot read the data

Error occurred on line #<line number> <jre exception information>

The credit card import tool cannot read the data on the indicated line.

Check the file. Contact the credit card issuer providing data for an undamaged file, only if the import file is damaged.

Contact the Infor Expense Management customer support, if the import file is not damaged.

FATAL ERROR 3001

Parameters incomplete:

-f <Card Type> -d <InputFile> -l <Log File> -c <Currency Code>") or

Not enough in-line command parameters provided.

Verify the parameters specified on the command line.

FATAL ERROR 3003

File format parameter unrecognized.

The file format corresponds to the <Card Type> specified on the command line and must match the entry in the alcc_import_for-mat.cc_format_name table for the appropriate credit card type.

Verify that the entry in the alcc_import_format table matches the command line parameter for the credit card type.

FATAL ERROR 3004

Could not connect to database.

Check the database connectivity. Check the regular issues that often cause a database connectivity problem. If the disconnection occurs in the middle of importing, the error may be related to a bad data problem. Note the data line where importing stops.

FATAL ERROR 3005

IOException -- Unable open the file.

Ensure that there are read/write permissions on the directory where the log files are created.

FATAL ERROR 3007

I/O Failure

Often refers to a data-related problem.

There are other messages that follow or precede this message that helps to identify the problem. Call the Extensity Customer Support to report this problem and provide them with a copy of the ccimport.log file.

FATAL ERROR 3009 – Problem at the SQL level: Could not open table? Bad query?

The credit card import tool cannot process an SQL statement. The import tool cannot open a table because of an incorrect SQL query.

Check the file. Contact the credit card statement, if the import file is damaged. The import tool at the SQL level: issuer providing the data for an undamaged file.

FATAL ERROR 3011

Problem at the SQL level; unable to open table? Bad Query?

Database related problem. Call the Extensity Customer Support to resolve. Email the ccim-port.log file to Extensity Customer Support.

FATAL ERROR 3012 - Database password not found in extensity-appserver.properties. Cannot continue.

The credit card import tool cannot access the database as the tool is unable to find the database password in the extensity-appserver.properties file.

Check the extensity-appserver.properties file. Add the password, if the file does not contain the database password.

FATAL ERROR 3013

Cannot find java class file.

This occurs when a JAVA class configured for the CC Feed does not exist. The java class file name is listed along with this error in the ccimport.log file. Note the class file.

Code related problem. Call the Customer Support to resolve. Provide the java class file name to Extensity Customer Support.

FATAL ERROR 3014

The data file has a bad data file format.

Occurs often because a wrong data file is used.

Verify the checksum for the data file received from the credit card vendor. Check with the credit card vendor for the file accuracy. The file may be corrupted while being sent over from the credit card vendor.

For example, the data file header is not in a correct format.

FATAL ERROR 3015

The tenant <tenant> was not found.

This message means that the database connection information in the central database for the tenant specified is invalid.

Check the connection information in the central database for the tenant.

FATAL ERROR 3016

You have specified the tenant as <tenant> but this installation is not multi-tenant enabled.

You attempted to run the import process under the specified tenant but the installation is not multi-tenant.

Do not specify the

-tenant argument when starting the CC feed.

FATAL ERROR 3017

A tenant required to be specified.

You attempted to run the import process on a multi-tenant installation without specifying a tenant.

You must specify the -tenant argument on the command line when starting the CC feed.

FATAL ERROR 3018

The default currency is specified as USD but the feed is for European countries. This is a configuration error.

You attempted to run the Amex4322 importer but specified the currency as USD. The Amex4322 feed is for European feeds.

Remove the USD specification.

FATAL ERROR 3019

Could not initialize importer: <message>

An unexpected error is encountered. The message provides more details.

Contact your Expense Management administrator.

FATAL ERROR 3020

Amex 1080 import must have parameter cc. AmexLevel3 ReferenceNumber

Type set to GL1025 or KR1025, depending on which feed you use to import Amex transactions.

Parameter cc.AmexLevel3

ReferenceNumber

Type is not set to GL1025 or KR1025. When the Amex 1080 (hotel folio) feed is imported, the application tries to link the folio records to an existing transaction. The folio record is saved with a reference number that matches to the transaction, if the transactions are missing (usually because the 1080 is imported before the 1025 feed). This parameter lets the application know whether to use the reference number for the KR1025 feed or for the GL1025.

Set the parameter to GL1025 or KR1025.

WARNING 1001

Unrecognized Record Type

The encountered record type number is not defined in this CC feed process. This occurs often because a wrong data file is used.

The credit card file includes record types that are not defined. Check with the credit card vendor regarding the unrecognized record type. The record type is located in the data file sent from the credit card vendor. The location of the Record Type is provided in the Credit Card Mapping document.

WARNING 1002

<param1>;

data on this line not imported.

"<param1>"

This can be any message and the message is used to indicate when a bad data field has been encountered. For example, a non-integer character is read as an integer.

There are other messages that precede this error message, which provide more insight in to the issue.

WARNING 1003

Credit card not assigned to user: The card must be assigned to a user using System Administration Tool.

The card must be assigned to a user using System Administration Tool. The User screen in the SAT provides the functionality to attach or un-attach credit cards.

WARNING 1005

Unrecognized Card:

Transaction # <param1> refers to card # <param2>, which is not in the database.

The transaction was not imported.

Card is not in the database.

Check the user name on the transaction line in the credit card data file. Each line in the credit card data file represents a transaction line or a card data line. More detailed information on transactional data is provided in the credit card mapping file. Verify the card number in the alcc_card table. Card number can also be verified in the User Profile screen using the SAT application and in the data file as described above.

WARNING 1006

Multiple Cards Found with Same Number:

There are <param1> charge cards in the database that have the same account number (<param2>).

We use the first one found.

Multiple cards in the database have the same account number. When this occurs, the card may be assigned to an incorrect person. Therefore, you require to confirm the card assignment.

Identify the Rogue Credit Card in the transaction file sent by the credit card vendor based on the positioning data provided in the credit card mapping file. Confirm the credit card user name. Un-attach the Credit card from the users who do not own the credit card using the SAT application. This can be done in the User Profile screen.

Extensity imports the first User Name, the per diem tool finds the name in the file received from the credit card vendor.

Delete the transaction imported from the alcc_transaction table, if the imported user name is not the correct.

Also, discuss with the credit card vendor the Credit cards associated with more than one User so that they can resolve in future files .

WARNING 1007

There are <param1> currencies in the database that have the same currency code (<param2>). We use the first one found as the proper currency.

Currency codes are not set up correctly in the application.

Identify the currency codes with the same codes. Update the currency codes with the correct code, using the SAT application. Currency data is located in the Corporate Data tab on the SAT application.

WARNING 1008

There are <param1> merchants in the database that have the same name (<param2>), city (<param3>), and VAT number (< param4>). We use the first one found as the proper merchant.

Multiple merchants that match the data to be imported are found in the database.

This is often not an issue and do not affect the data integrity.

WARNING 1009

Not importing duplicate transaction:

Card Number is <param1>. Amount is <param2>. Posting Date is <param3>.

This often occurs if the data file is imported twice.

Another transaction with the same reference number, amount, posting date, and card number is already in the database. Thus, the data is imported again.

WARNING 1010

Currency code <param1> is not in the database.

The specific currency code listed in the log is not found in the database.

Call Extensity Customer Support to verify if this is the correct currency code. If this is not the correct currency code, the transaction from the credit card vendor is invalid. Please notify the credit card vendor. If the currency code is valid, the new currency code must be setup in the database, using SAT.

Extract the transaction from the Out.txt file to a new file and re-run ccimport to bring in this transaction once the new currency code is setup.

WARNING 1011

Transactions that have a zero amount are not imported.

Reference number is <param1>.

Transactions that have a zero amount must not be imported. This is only a warning.

There must not be Zero amount transactions received from the credit card vendor.

WARNING 1012

Your alcc_sic_code table does not have a default entry. The default entry must not have the SIC code (such as, blanks or null).

Check if the alcc_sic_code table has a default entry. This error must occur, only if there is no default entry in the alcc_sic_code table. Call Customer Support to report this problem once you have verified the missing default entry in the alcc_sic_code table.

WARNING 1013

Credit Card #<param1> has been added to the database and is assigned to a user. Please verify these information.

Cardholder Name: <param2> Extensity User Name: <param3>

The warning message can be used to verify information for the new users added to the application. This is not an error message.

WARNING 1014

Credit Card #<param1>:

No Extensity user has the SSN associated with this card.

Cardholder Name: <param2>

The ccimport program could not find a matching SSN in the database, when trying to associate a credit card to an Extensity User.

Verify if the SSN is being sent correctly from Citibank. If so, then verify the Extensity user exists in the application and also verify the SSN for that user. If all the above verifications are correct, then call the Extensity Customer Support.

WARNING 1015

Credit Card #<param1>:

More than one Extensity user has the Social Security Number associated with this card.

Cardholder Name: <param2>

This occurs because the same SSN is assigned to more than one Extensity user.

Find the users from the Extensity database with the specified SSN. Identify why there are more than one user who use this SSN.

WARNING 1016

Credit Card #<param1> has been added to the database but has not been assigned to a user. Invalid social security number is provided.

Cardholder Name: <param2>

This occurs because the format of the SSN number is not correct. For example, the SSN number may not be a nine-digit number.

Verify if the SSN is being sent correctly from Citibank. If so, then verify if the Extensity user exists in the application and also verify the SSN for that user. Update the SSN in the application using SAT, if incorrect. Call Citibank to correct the information, if the SSN is sent incorrectly.

NING 1017

Credit Card #<param1> in the database has been assigned to a user. Please verify this information:

Cardholder Name: <param2> Extensity User Name: <param3>

This is only an informative message, which indicates that a new credit card has been assigned to a user. No action is required to be taken. Obsolete.

WARNING 1018

Credit Card #<param1> in the database has been assigned to a user. Social Security Number associated with this card does not exist in the Extensity database.

Cardholder Name: <param2>

This occurs only when a user is matched, using the SSN option and the target SSN is not found among the database users.

This message is not applicable to Sony, since matching is done based on SSN. If SSN does not exist in the database, then no match is identified and the card is not assigned to a user. Obsolete.

WARNING 1019

Credit Card #<param1> in the database has been assigned to a user. More than one Extensity User has the Social Security Number.

Cardholder Name: <param2>

This occurs because same SSN is assigned to more than one Extensity user.

Verify if the SSN is being sent correctly from Citibank. If so, then identify the correct Extensity user for the respective SSN in the system. For all the other users associated with that SSN, update the SSN to the correct SSN. Check the data being imported for inaccuracies. Obsolete.

WARNING 1020

Credit Card #<param1> in the database has been assigned to a user. The Social Security Number is not provided with this card.

Cardholder Name: <param2>

This occurs only when a user is matched using the SSN option and the target SSN is not found among the database users.

This message is not applicable to Sony since matching is done based on SSN. If SSN does not exist in the database, then no matching is done and the card is not assigned to a user. Obsolete.

WARNING 1021

Unrecognized Country Code: <param1>

Check the country code associated with this transaction. Using SAT, verify if the corresponding Country code is present in the application.

WARNING 1022

Failure to locate merchant location: <param1>

Merchant location is not imported for Sony. So, this warning message is not applicable.

WARNING 1023

Not importing duplicate card:

Card number = <param1>

This can be ignored since the bank regularly provides repeated card information in every new transaction.

Card information has already been imported into the application. Check with Citibank as to why duplicate entries are being sent in the data file.

WARNING 1024

Credit card account data updated:

Data for card number <param1> are updated.

This is only an informative message, which indicates that a credit card data is updated. No action required to be taken.

WARNING 1025

Employee number not found in database: Emp Number#<param1>

Card Number is <param2>. Amount is <param3>. Posting Date is <param4>.

This occurs only when a user is matched using an employee number option and the target employee number is not found among the database users.

This message is not applicable for Sony, since mapping is based on SSN and not employee number.

WARNING 1026

Non-integer sic code, <param1>, is used.

SIC code must be an integer.

Required to investigate why the SIC code data is not in an expected format.

WARNING 1027

Invalid SSN Number:<param1>

Required to investigate why SSN data is not in an expected format.

WARNING 1028

Merchant data updated.

Informative message.

Merchant location is not being imported for Sony, so this warning is not applicable.

WARNING 1029

Invalid Employee Number.

Employee number is not in an expected format.

This message is not applicable for Sony, since mapping is based on SSN and not employee number.

WARNING 1030

Credit Card #<param1>

No Extensity user has the employee number associated with this card.

Cardholder Name: <param2>

This message is not applicable for Sony, since mapping is based on SSN and not employee number.

WARNING 1031

Credit Card #<param1>

More than one Extensity user has the employee number associated with this card.

Cardholder Name: <param2>

This message is not applicable for Sony, since mapping is based on SSN and not employee number.

WARNING 1032

Card deactivated, Card #<param1>

Required to use SAT to activate this card first before new data associated with this card can be imported.

The card is not imported.

Require to use SAT to activate this card before new data associated with this card can be imported. The detailed log messages are self-explanatory.

WARNING 1034

No card reassignment allowed:

Not allowed to reassign the card from the user with a UID of <param1> to another user of <param2>.

Require to know why the card has been assigned to <param1>. If <param1> is not the correct card user, required to use SAT to detach the card from <param1> and reattach the card to <param2> instead.

WARNING 1035

No data insertion allowed for <param1>

The corresponding element data, <param2> do not exist

This occurs often due to missing of important data.

WARNING 1036

Inconsistent currency amounts encountered:

Native and billed amounts (<param1> and <param2>) do not have a consistent sign.

The transaction is not imported.

This occurs often due to a data issue.

Check the problem data.

WARNING 1037

Inconsistent date string encountered:

<param1> is not a valid date under a date format of <param2>.

This occurs often due to a data issue.

Check the problem data.

WARNING 1038

Skip the invalid airline departure date, <param1>.

The corresponding transaction can still be imported even without the airline departure date.

Check airline departure date data.

WARNING 1039

Skip the invalid hotel arrival date, <param1>

The corresponding transaction can still be imported even without the hotel arrival date.

Check hotel arrival date data.

WARNING 1040

Skip the invalid hotel departure date., <param1>

The corresponding transaction can still be imported even without the hotel departure date.

Check hotel departure date data.

WARNING 1041

Same currency but inconsistent amounts encountered:

Native and billed amounts (<param1> and <param2>) are not consistent.

This occurs often due to a data issue.

Check currency amounts data.

WARNING 1042

Transaction data not imported.

Informative message

This message often comes with other messages to explain why the corresponding transaction is not imported.

WARNING 1043

Skip the invalid data for hotel stay duration, <param1>

The corresponding transaction can still be imported even without hotel stay duration.

Validate the hotel stay duration data.

WARNING 1044

<param1> is not a recognizable date

The corresponding transaction can still be imported even without date.

Validate the date format.

WARNING 1045

Skip the invalid data for hotel room amount.,<param1>

The corresponding transaction can still be imported even without the hotel room amount.

Validate the hotel room amount data.

WARNING 1046

Skip the invalid data for hotel room tax 1.,<param1>

The corresponding transaction can still be imported even without the hotel room tax1.

Validate the hotel room tax1 data.

WARNING 1047

Skip the invalid data for hotel room tax 2.,<param1>

The corresponding transaction can still be imported even without the hotel room tax 2.

Validate the hotel room tax 2 data.

WARNING 1048

Skip the invalid data for hotel phone amount.,<param1>

The corresponding transaction can still be imported even without the hotel phone amount.

Validate the hotel phone amount data.

WARNING 1049

Skip the invalid data for hotel phone tax 1.,<param1>

The corresponding transaction can still be imported even without the hotel phone tax1.

Validate the hotel phone tax1 data.

WARNING 1050

Skip the invalid data for hotel phone tax 2.,<param1>

The corresponding transaction can still be imported even without the hotel phone tax2.

Validate the hotel phone tax2 data.

WARNING 1051

Skip the invalid data for hotel restaurant amount.,<param1>

The corresponding transaction can still be imported even without the hotel restaurant amount.

Validate the hotel restaurant amount data.

WARNING 1052

Skip the invalid data for hotel restaurant tax 1.,<param1>

The corresponding transaction can still be imported even without the hotel restaurant tax 1.

Validate the hotel restaurant tax 1 data

WARNING 1053

Skip the invalid data for hotel restaurant tax 2.,<param1>

The corresponding transaction can still be imported even without the hotel restaurant tax 2.

Validate the hotel restaurant tax 2 data.

WARNING 1054

Skip the invalid data for hotel service amount.,<param1>

The corresponding transaction can still be imported even without the hotel service amount.

Validate the hotel service amount data.

WARNING 1055

Skip the invalid data for hotel service tax 1.,<param1>

The corresponding transaction can still be imported even without the hotel service tax 1.

Validate the hotel service tax 1 data.

WARNING 1056

Skip the invalid data for hotel service tax 2.,<param1>

The corresponding transaction can still be imported even without the hotel service tax 2.

Validate the hotel service tax 2 data.

WARNING 1057

Skip the invalid data for hotel tip amount 1.,<param1>

The corresponding transaction can still be imported even without the hotel tip amount 1.

Validate the hotel tip amount 1 data.

WARNING 1058

Skip the invalid data for hotel tip amount 2.,<param1>

The corresponding transaction can still be imported even without the hotel tip amount 2.

Validate the hotel tip amount 2 data.

WARNING 1059

Skip the invalid data for hotel other amount.,<param1>

The corresponding transaction can still be imported even without the hotel other amount

Validate the hotel other amount.

WARNING 1062

Skip the invalid data for hotel daily room rate.,<param1>

The corresponding transaction can still be imported even without the hotel daily room rate.

Validate the hotel daily room rate.

WARNING 1063

Skip the invalid data for hotel daily room rate tax.,<param1>

The corresponding transaction can still be imported even without the hotel daily room rate tax.

Validate the hotel daily room rate tax.

WARNING 1064

Skip the invalid data for hotel laundry amount.,<param1>

The corresponding transaction can still be imported even without the hotel laundry amount.

Validate the hotel laundry amount.

WARNING 1065

Skip the invalid data for hotel gift shop amount.,<param1>

The corresponding transaction can still be imported even without the hotel gift shop amount.

Validate the hotel gift shop amount.

WARNING 1067

Skip the invalid data for hotel business center amount.,<param1>

The corresponding transaction can still be imported even without the hotel business center amount.

Validate the hotel business center amount.

WARNING 1068

Skip the invalid data for hotel health club amount.,<param1>

The corresponding transaction can still be imported even without the hotel health club amount.

Validate the hotel health club amount.

WARNING 1069

Skip the invalid data for hotel total tax.,<param1>

The corresponding transaction can still be imported even without the hotel total tax.

Validate the hotel total tax.

WARNING 1070

Unrecognized transaction code, <param1>. Record is not processed.

The first field of the VCF40 feed file is invalid. The field requires to be 1,2,3,4,6,7,8 or 9.

The visa card format might be updated. Check the latest VCF40 specifications to see if we required to support additional codes.

WARNING 1071

Transaction data updated.

The transaction is updated.

Informational message.

WARNING 1072

Credit card with account number <masked account number> not found. Record is not processed.

A card record found in the Visa VCF40 feed with a transaction code UPDATE but the record does not exist in the alcc_card table. Therefore, the application cannot update the data.

This applies to the Visa importer only.

The transaction code requires to be ADD_OR_UPDATE (4) or ADD (1) for the record to be added.

WARNING 1073

Transaction with reference number <reference number>, not found. Record is not processed.

A transaction found in the Visa VCF40 feed with a transaction code UPDATE but the record does not exist in the alcc_transaction table. Therefore, the application cannot update the data. You can receive this error, if the transaction details or folio record contains a reference number not in the database.

This applies to the Visa importer only.

The transaction code requires to be ADD_OR_UPDATE (4) or ADD (1) for the record to be added.

WARNING 1074

Credit card with account number <masked account number>, already exists. Card is not inserted.

A card record found in the Visa VCF40 feed with a transaction code ADD but the record already exists in the alcc_card table. Therefore, the application cannot add the data.

This is applicable for the Visa importer only.

The transaction code requires to be ADD_OR_UPDATE (4) or UPDATE (3) for the record to be updated.

WARNING 1075

Transaction with reference number <param1>, already exists. Transaction is not inserted.

A transaction found in the Visa VCF40 feed with a transaction code ADD but the record already exists in the alcc_transaction table. Therefore, the application cannot add the data.

This is applicable for the Visa importer only.

The transaction code requires to be ADD_OR_UPDATE (4) or UPDATE (3) for the record to be updated.

WARNING 1076

Level 3 record with folio id <param1> and sequence number <param2> is linked to a transaction with reference number <param3> that cannot be found. Record is not processed.

The level 3 data imported but not linked to the associated transaction because no transaction with the given reference number is found.

This is applicable for the Amex1080 importer only.

Run the Amex KR1025 or GL1025 feed before running the 1080 feed.

WARNING 1077

Level 3 record with folio id <param1> and sequence number <param2> does not have a transaction reference number. Record is not processed.

The Amex1080 folio record contains no reference number. No record is inserted into alcc_level3_detail.

This is applicable for the Amex1080 importer only.

This can indicate a corrupt 1080 feed file.

WARNING 1078

Level 3 record with transaction reference number <param1> has no folio ID. Record is not processed.

The Amex1080 folio record contains no folio ID. No record is updated into the alcc_level3_detail table.

This is applicable for the Amex1080 importer only.

This can indicate a corrupt 1080 feed file.

WARNING 1079

Level 3 record with folio id <param1> has no sequence number. Record is not processed.

The Amex1080 folio record contains no sequence number. The sequence number is used as part of a unique key to check for duplicates. No record is inserted into alcc_level3_detail.

This is applicable for the Amex1080 importer only.

This can indicate a corrupt 1080 feed file.

WARNING 1080

Level 3 record with folio id <param1> does not balance to the transaction amount. Record is not processed.

Only level 3 records with balance indicator, indicates that the folio amount balances to the transaction amount is processed.

The Amex1080 spec states: "'[The balance indicator] indicates whether the Folio Amount balances to the Local Amount from Charge Transaction. The amounts can be different, if multiple forms of payment are used. In this case, the line items are not added up to the local charge amount. Expense Vendors must code to use only values = 1".

This is applicable for the Amex1080 importer only.

WARNING 1081

Level 3 record with folio id <param1> does not have a matching transaction. Record is not processed.

An internal indicator of an Amex folio record indicates that the message does not have a matching transaction. No record is inserted into alcc_level3_detail.

The Amex1080 spec states: "'Expense Vendors must code to only use values = 1".

This is applicable for the Amex1080 importer only.

This can indicate a corrupt 1080 feed file.

WARNING 1082

Level 3 record with folio id <param1> and sequence number <param2> already exists. Record is not processed.

A record already exists in alcc_level3_detail for the same transaction and with the same sequence number. The record is skipped.

This is applicable for the Amex1080 importer only.

Probably indicates the 1080 feed has processed more than once.

WARNING 1083

Credit card with id <param1> has an inactive payment type. User may not be able to attach transactions.

The card has a payment type that is inactive. The application do not insert or update card records with inactive payment types.

The card record can be updated or added, reactivate the payment type or modify the status of the card to an active type.

WARNING 1084

Unrecognized Card. Transaction #<param1> refers to card #<masked account number>, which is not in the database. Temporary card is created for the transaction.

A transaction refers to a card that does not exist based on the account number as the cc.createTemporaryCard parameter is True, a temporary card is created, so that the transaction is imported. The transaction is not accessible until the card record from this or another feed is processed.

Run the feed that has the card record with the same account number. The temporary card is replaced with the real card. The transaction can now be attached.

WARNING 1085

Transaction detail for transaction with reference number <param1>, not found. Record is not processed.

The transaction is for an air or rail trip but there is no leg specific detail.

This is informational and applicable for the Visa importer only.

WARNING 1086

Invalid VAT amount for transaction with reference number <param1>:<param2>

The VAT amount of the transaction is in an incorrect format.

This is specific to the Visa importer.

This can be a number format problem. There must be another error message near this one that display more details.

WARNING 1087

Invalid credit card limit for card with account number <param1>:<param2>

The card limit on the card record is formatted incorrectly.

This can be a number format problem. There must be another error message near this one that display more details.

WARNING 1088

Transaction with reference number <param1> already attached to an expense report--skipping update

The transaction is already attached to a line item in an expense report and cannot be updated.

An importer may also generate this error when processing level 3 data and the associated transaction is already attached to a line item in an expense report.

Detach the transaction, if the card is updated. Or simply ignore the warning.

WARNING 1089

Invalid position specified in the cc.VCF40.EmpNumPosition <param1>) parameter. The value should be an integer > 0. Using 23 instead.

The cc.VCF40EmpNumMatch parameter is set to True but the cc.VCF40.EmpNumPosition parameter is not in the integer form. The importer uses the default position 23 to find the employee number.

This is specific to the Visa importer.

WARNING 1090

Level 3 record with folio id <param1> and sequence number <param2> does not have a transaction reference number as specified in cc.AmexLevel3Reference

NumberType.

The cc.AmexLevel3ReferenceNumberType parameter can be set to GL1025 or KR1025, based on whether the feed being processed is global or U.S. This parameter also affects where the importer searches for the transaction ID which is used to link the level record to the transaction. The error means that the level 3 data is not imported because the transaction ID is not specified.

This is applicable for the Amex1080 importer only.

WARNING 1091

Level 3 record with folio id <param1> and sequence number <param2> and reference number <param3> already exists. Record is not processed.

The level 3 data is not imported because a level 3 record already exists for the given transaction and sequence number.

This is applicable for the Amex1080 importer only.

WARNING 1092

String substitution <param1>

Data read by any importer can be subject to string substitution before regular processing. For example, you can require that all instances of ‘|’ be replaced with ‘/’. You can set up this type of substitution, using the cc.substituteSubstring.enabled, cc.substituteSubstring.find and cc.substituteSubstring.replace parameters. Whenever a substitution occurs, a warning message is written to the log. Additional information such as record type, tag, element, or field can also be written.

Informational only