Warning codes and messages

Code	Message	Additional comments	Resolution
1001	Unrecognized Record Type	The record type number is not defined in this CC Feed process. This error is encountered when an incorrect 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 can be 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
1002	<param1>; data on this line not imported	This message is used for indicating that 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 and provide more insight on the issue.
1003	Credit card not assigned to user: The card must be assigned to a user using the System Administration Tool.		The card must be assigned to a user through the System Administration Tool. The User screen in the SAT provides the functionality to attach credit cards.
1004	Credit Card # <masked card number> not assigned to a user. The card must be assigned to a user using the System Administration Tool.	No employee information available in feed to match employee to card.	The card must be assigned to a user through the System Administration Tool (SAT). The User screen in the SAT application provides a functionality to automatically assign credit cards to a user based on the employee number specified in the feed. Use the appropriate application parameter based on the card type to enable the functionality.
1005	Unrecognized Card: Transaction # <param1> refers to card # <param2>, which is not in the database. The transaction was not imported.	The Credit Card details are not available 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 database of the al- cc_card table. Card number can also be verified on the User Profile screen using SAT and in the data file as described above.
1006	Multiple Cards Found with Same Number: There are <param1> charge cards in the database that have the same account number (<param2>). We will be using the first one we found.	Multiple cards in the database have the same account number. When this scenario occurs the card can be assigned to wrong person. Thus, you must 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. Remove the credit card linked to users who do not own the credit card using User Profile screen in SAT. Extensity imports the first User Name that is found in the file obtained from the credit card vendor. For the incorrect User Name, delete the transaction imported from the alcc_transaction table. Discuss with the credit card vendor about the Credit cards associated with more than one User to resolve the issues in future files.
1007	There are <param1> currencies in the database that have the same currency code (<param2>). We will be using the first one we found as the proper currency.	Currency Codes are not set up correctly in the system.	Identify the Currencies s with the same codes. Update the currency codes with the right code using the SAT application. Currency Data is available on the Corporate Data tab of the SAT application.
1008	There are <param1> merchants in the database that have the same name (<param2>), city (<param3>), and VAT number (< param4>). We will be using the first one we found as the proper merchant.	Multiple merchants that match the data to be imported are found in the database.	This is often not an is- sue and does not affect the data integrity.
1009	Not importing duplicate transaction: Card Number is <param1>. Amount is <param2>. Posting Date is <param3>.	This error is often encountered, if the data file is imported twice.	Another transaction with same reference number, amount, posting date, and card number is already in the database. Thus, the data is not imported again.
1010	Currency code <param1> is not in the database	The specific currency code listed in the log is found in the database.	Contact 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. Once the new currency code is setup, extract the transaction from the Out.txt file into a new file and run the ccimport process again to import the transaction.
1011	Transactions that have a zero amount are not imported. Reference number is <param1>.		Transactions with a zero amount must not be imported. This is only a warning.
1012	Your alcc_sic_code table does not have a default entry. The default entry should have no SIC code (i.e. blanks, or null).		Check if the alcc_sic_code table has a default entry. This error occurs only if there is no default entry in the alcc_sic_code table. Contact Customer Support to report this problem once you have verified the missing default entry in the alcc_sic_code table.
1013	Credit Card #<param1> has been added to the database and has been assigned to a user. Please verify the following information. Cardholder Name : <param2> Extensity User Name : <param3>		The warning message can be used to verify information for new users added to the system. This is not an error message.
1014	The Warning message can be used to verify information for new users added to the system. This is not an error message.	When trying to associate a Credit card to an Extensity User the ccimport program could not find a matching SSN in the database	Verify if the SSN is sent correctly from Citibank. If sent correctly, verify if the Extensity User exists in the system and verify the SSN for that user. If all the above checks are correct, call Extensity Customer Support.
1015	Credit Card #<param1>: More than one Extensity user has the Social Security Number associated with this card. Cardholder Name : <param2>	This issue is encountered when same SSN is assigned to more than one Extensity user.	Identify the users in the Extensity database with the specified SSN. Identify why more than one people use the same SSN.
1016	Credit Card #<param1> has been added to the database but has not been assigned to a user. Invalid social security number was provided. Cardholder Name : <param2>	This error is encountered when the format of the SSN number is incorrect. For example, it may not be a nine-digit number.	Verify if the SSN is sent correctly from Citibank. If sent correctly, verify the Extensity User exists in the system. Verify the SSN for that user. Update the SSN in the system using SAT, if incorrect. If SSN is sent incorrectly from Citibank, call Citibank to correct the information.
1017	Credit Card #<param1> in the database has been assigned to a user. Please verify the following information: Cardholder Name : <param2> Extensity User Name : <param3>		This is only an informative message that indicates a new credit card has been assigned to a user. No action requires to be taken.
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 error is encountered only when a user match is made through SSN option and the target SSN is not found including the database users.	If SSN does not exist in the Database, matching is not done and the card is not assigned to a user.
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 error is encountered when same SSN is assigned to more than one Extensity user.	Verify if the SSN is being sent correctly from Citibank. If sent correctly, identify the correct Extensity User for the respective SSN in the system. For all other users associated with the SSN update the SSN to the correct SSN. Check the data being imported for inaccuracies.
1020	Credit Card #<param1> in the database has been assigned to a user. The Social Security Number was not provided with this card. Cardholder Name : <param2>	This error is encountered when a user match is made through the SSN option and the target SSN is not found among the database users.	If SSN does not exist in the database, data is not matched and the card is not assigned to a user.
1021	Unrecognized Country Code: <param1>		Check the country code associated with the transaction. Use the SAT application to verify whether the corresponding Country code is present in the system.
1023	Not importing duplicate card: Card number = <param1>	This error is not considered as the bank often provides repeated card information in every new transaction.	Card has already been imported into the system. Confirm with Citibank for the duplicate entries being sent to the data file.
1024	Credit card account data updated:Data for card number <param1> are updated		This is only an informative message that indicates that a credit card data has been updated. No action is required.
1026	Non-integer sic code, <param1>, is used	SIC code must always be an integer	Investigate why SIC code data is not in the correct format.
1027	Invalid SSN Number:<param1>		Investigate the reason for the SSN data to be not in the correct format.
1028	Merchant data updated	This is only an informative message
1029	Invalid Employee Number	The employee number is missing.
1030	Credit Card #<param1>No Extensity user has the employee number associated with this card. Cardholder Name: <param2>
1031	Credit Card #<param1> More than one Extensity user has the employee number associated with this card. Cardholder Name: <param2>
1032	Card deactivated, Card #<param1> Need to use SAT to activate this card first before new data associated with this card can be imported. The card was not imported.		Use SAT to activate the card before new data associated with the card is imported. The detailed log messages are self-explanatory.
1034	No card reassignment allowed:Not allowed to reassign the card from the user with a UID of <param1> to another user of <param2>		You must know the reason for the card to be assigned to <param1>. If <param1> is not the right card user, you must use SAT to remove the attached card from <param1> and reattach to <param2> instead.
1035	No data insertion allowed for <param1> The corresponding element data, <param2> do not exist.	This error is encountered as the required data is missing.
1036	Inconsistent currency amounts encountered: Native and billed amounts (<param1> and <param2>) don’t have a consistent sign. The transaction was not imported.	This error is encountered due to a data issue.	Check the data.
1037	Inconsistent date string encountered: <param1> is not a valid date under a date format of <param2>.	This error is encountered due to a data issue.	Check the data.
1038	Skip the invalid airline departure date, <param1>	The corresponding transaction can be imported even without a valid date for the airline departure.	Check the data related to the airline departure date.
1039	Skip the invalid hotel arrival date, <param1>	The corresponding transaction can be imported even without a valid date for the hotel arrival.	Check the data related to the hotel arrival date.
1040	Skip the invalid hotel departure date <param1>	The corresponding transaction can be imported even without a valid date for the hotel departure.	Check the data related to the hotel departure date.
1041	Same currency but inconsistent amounts encountered: Native and billed amounts (<param1> and <param2>) are not consistent	This error is encountered due to a data issue.	Check data related to currency amounts.
1042	Transaction data not imported	This message is for the information purpose only.	This message is displayed with other messages to explain why the corresponding transaction is not imported.
1043	Skip the invalid data for hotel stay duration,<param1>	The corresponding transaction can be imported even without hotel stay duration.	Check the data related to the hotel stay duration.
1044	<param1> is not a recognizable date	The corresponding transaction can be imported even without date.	Check the date format.
1045	Skip the invalid data for hotel room amount.,<param1>	The corresponding transaction can be imported even without a valid amount for the hotel room.	Check the data related to the hotel room amount.
1046	Skip the invalid data for hotel room tax 1.,<param1>	The corresponding transaction can be imported even without a valid tax one amount for the hotel room.	Check the data related hotel room tax one data.
1047	Skip the invalid data for hotel room tax 2.,<param1>	The corresponding transaction can be imported even without a valid tax two amount for the hotel room.	Check the data related to the hotel room tax two.
1048	Skip the invalid data for hotel phone amount.,<param1>	The corresponding transaction can be imported even without a valid amount for the hotel phone.	Check the data related to the hotel phone amount.
1049	Skip the invalid data for hotel phone tax 1.,<param1>	The corresponding transaction can be imported even without a valid tax one amount for the hotel phone.	Check the data related to the hotel phone tax one.
1050	Skip the invalid data for hotel phone tax 2.,<param1>	The corresponding transaction can be imported even without a valid tax two amount for the hotel phone.	Check the data related to the hotel phone tax two .
1051	Skip the invalid data for hotel restaurant amount.,<param1>	The corresponding transaction can be imported even without a valid amount for the hotel restaurant.	Check the data related to the hotel restaurant amount.
1052	Skip the invalid data for hotel restaurant tax 1.,<param1>	The corresponding transaction can be imported even without a valid tax one amount for the hotel restaurant.	Check the data related to the hotel restaurant tax one data.
1053	Skip the invalid data for hotel restaurant tax 2.,<param1>	The corresponding transaction can be imported even without a valid tax two amount for the hotel restaurant.	Check the data related to the hotel restaurant tax two.
1054	Skip the invalid data for hotel service amount.,<param1>	The corresponding transaction can be imported even without a valid amount for the hotel service.	Check the data related to the hotel service amount.
1055	Skip the invalid data for hotel service tax 1.,<param1>	The corresponding transaction can be imported even without a valid tax one amount for the hotel service.	Check the data related to the hotel service tax one.
1056	Skip the invalid data for hotel service tax 2.,<param1>	The corresponding transaction can be imported even without a valid tax two amount for the hotel service.	Check the data related to the hotel service tax two.
1057	Skip the invalid data for hotel tip amount 1.,<param1>	The corresponding transaction can be imported even without a valid tip one amount for the hotel.	Check the data related to the hotel tip amount one.
1058	Skip the invalid data for hotel tip amount 2.,<param1>	The corresponding transaction can be imported even without a valid tip two amount for the hotel.	Check the data related to the hotel tip amount two.
1059	Skip the invalid data for hotel other amount.,<param1>	The corresponding transaction can be imported even without a valid other amount for the hotel.	Check data related to the hotel other amount.
1060	Skip the invalid data for hotel other tax 1, <param1>	The corresponding transaction can be imported even without a valid tax amount for the hotel.	Check data related to the hotel other tax one amount.
1061	Skip the invalid data for hotel other tax 2, <param1>	The corresponding transaction can be imported even without a valid tax amount for the hotel.	Check data related to the hotel other tax two amount.
1062	Skip the invalid data for hotel daily room rate.,<param1>	The corresponding transaction can be imported even without a valid daily room rate of the hotel.	Check data related to the hotel daily room rate.
1063	Skip the invalid data for hotel daily room rate tax.,<param1>	The corresponding transaction can be imported even without a valid daily room rate tax amount for the hotel.	Check data related to the hotel daily room rate tax.
1064	Skip the invalid data for hotel laundry amount.,<param1>	The corresponding transaction can be imported even without a valid laundry amount for the hotel.	Check data related to the hotel laundry amount.
1065	Skip the invalid data for hotel gift shop amount.,<param1>	The corresponding transaction can be imported even without a valid hotel gift shop amount.	Check data related to the hotel gift shop amount.
1066	Skip the invalid data for hotel movie amount, <param1>	The corresponding transaction can be imported even without a valid amount for the movie.	Check data related to the hotel movie amount.
1067	Skip the invalid data for hotel business center amount.,<param1>	The corresponding transaction can be imported even without a valid amount for the hotel business center.	Check data related to the hotel business center amount.
1068	Skip the invalid data for hotel health club amount.,<param1>	The corresponding transaction can be imported even without a valid health club amount for the hotel.	Check data related to the hotel health club amount.
1069	Skip the invalid data for hotel total tax.,<param1>	The corresponding transaction can be imported even without a valid total tax amount for the hotel.	Check data related to the hotel total tax.
1070	Unrecognized transaction code, <param1>. Record will not be processed.	The first character in the Visa VCF40 feed is not a number between one to four or six to nine, therefore, the record is skipped.
1071	Transaction data updated	This is an informational message and not a warning.
1072	Credit card with account number <param1> not found. Record will not be processed.	The Visa card that is indicated as update only does not exist in the database and cannot be added. This scenario is applicable for the Visa importer only.
1073	Transaction with reference number <param1> not found. Record will not be processed.	The transaction code is ’update’, however, the transaction does not exist in the database. The transaction is not added. This error is also encountered when level 2 or level 3 data is being processed and the transaction is not found by reference number. In these cases, the level 2 or level 3 data is not being processed. This scenario is applicable for the Visa importer only.
1074	Credit card with account number <param1> already exists. Card will not be inserted.	The Visa cards that are indicated as add only exists in the database but cannot be updated. This scenario is applicable for the Visa importer only.
1075	Transaction with reference number <param1> already exists. Transaction will not be inserted.	The transaction code is ’add’ but the transaction already exists in the database. The transaction is not added. This scenario is applicable for the Visa importer only.
1076	Level 3 record with folio id <param1> and sequence number <param2> is linked to a transaction with reference number <param3> that can’t be found. Level 3 record will still be inserted. If the transaction comes in later, they will be linked.	The level 3 data is imported, however, not linked to the associated transaction as no transaction with the specific reference number is found. This scenario is applicable for the Amex1080 importer only.
1077	Level 3 record with folio id <param1> and sequence number <param2> does not have a transaction reference number. Record will not be processed.	The level 3 data is not imported as the data does not have the reference number of the associated transaction. This scenario is applicable for the Amex1080 importer only.
1078	Level 3 record with transaction reference number <param1> has no folio id. Record will not be processed.	The level 3 data is not imported as the data does not have a folio ID. This scenario is applicable for the Amex1080 importer only.
1079	Level 3 record with folio id <param1> has no sequence number. Record will not be processed.	The level 3 data is not imported as the data does not have a sequence number. This scenario is applicable for the Amex1080 importer only.
1080	Level 3 record with folio id <param1> does not balance to the transaction amount. Record will not be processed.	1080 Level 3 record with folio id <param1> does not balance to the transaction amount. Record will not be processed. Only level 3 records that indicate the folio amount balances to the transaction amount, are processed. The Amex1080 specification 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 to the local charge amount. This scenario is applicable for the Amex1080 importer only.
1081	Level 3 record with folio id <param1> does not have a matching transaction. Record will not be processed.	The level 3 data is not imported as the data do not match with the transaction. Based on the Amex1080 specification , “’Expense Vendors must code to only use values = 1”. This scenario is applicable for the Amex1080 importer only.
1082	Level 3 record with folio id <param1> and sequence number <param2> already exists. Record will not be processed.	The level 3 data is not imported as a level 3 record already exists for the specific transaction and sequence number. This scenario is applicable for the Amex1080 importer only.
1083	Credit card with id <param1> has an inactive payment type. User may not be able to attach transactions.	The credit card is inserted or updated as the payment type is inactive.	Activate the payment type through SAT.
1084	Unrecognized Card. Transaction # <param1> refers to card #<param2> which is not in the database. Temporary card will be created for the transaction.	Credit card for the associated transaction does not exist in the data base. However, a temporary credit card is created, as the value of the cc.createTemporaryCard application parameter is set to True. The transaction is imported and linked to the temporary credit card. If the card data is later imported, the data of the temporary card is updated.	This is a warning message and not an error message.
1085	Transaction detail for transaction with reference number <param1> not found. Record will not be processed.	The transaction specified is for an air or rail trip but details are not available. This is an informational message and only applicable for the Visa importer.
1086	Invalid VAT amount for transaction with reference number <param1> : <param2>	The VAT amount of the transaction is in an incorrect format. This scenario is specific to the Visa importer.
1087	Invalid credit card limit for card with account number <param1> : <param2>	The credit card limit is in an incorrect format.
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 not updated. An importer can also generate this error when processing level 3 data and the associated transaction is already attached to a line item in an expense report.
1089	Invalid position specified in parameter cc.VCF40.EmpNumPosition <param1>). The value should be an integer > 0. Using 23 instead.	The value of the cc.VCF40EmpNumMatch application parameter is set to True, however, the value of the cc.VCF40.EmpNumPosition application parameter is not in integer format. The importer uses the default position 23 to find the employee number. This scenario is specific to the Visa importer.
1090	Level 3 record with folio id <param1> and sequence number <param2> does not have a transaction reference number as specified in cc.AmexLevel3ReferenceNumberType.	The value of the cc.AmexLevel3ReferenceNumberType application 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 looks for the transaction ID which is used to link the level record to the transaction. The error is encountered when the level 3 data is not imported as the transaction ID is not specified. This is only applicable for the Amex1080 importer.
1091	Level 3 record with folio id <param1> and sequence number <param2> and reference number <param3> already exists. Record will not be processed.	The level 3 data is not imported as a level 3 record already exists for the specific transaction and sequence number. This scenario is applicable for the Amex1080 importer only.
1092	String substitution <param1>	Data read by an importer can be subject to string substitution before regular processing. For example, you might require that all instances of the special character ‘\|’ be re- placed with ‘/’. You can set up this kind of substitution using the cc.substituteSubstring.enabled, cc.substituteSub- string.find and cc.sub- stituteSubstring.re- place application parameters. Whenever a substitution occurs, a warning message is displayed on the log. Additional information such as record type, tag, element, or field can also be written.	Informational only.
1093	No transaction found for transaction detail with reference number <ref num>. Record will not be processed.	Transaction level 2 detail is stored in a separate table as transaction data; the data is linked to the reference number. If the reference number of the record does no match a transaction reference number, the system displays the error message. The transaction is imported but the details are not imported.	Check he feed file has reference numbers that match the secondary data.
1094	Transaction found with reference number <ref num> belonging to diverted card <masked card number> but cc.diverted not set. Set cc.diverted to true and reprocess.	The transaction is linked to a diverted card. However, the diverted card functionality is not enabled.	Set the value of the cc.diverted application parameter to True and reprocess.
1095	Can't set processor on diverted card for <name on card> with account number <masked account number> because cc.diverted not set. Set cc.diverted to true and reprocess.		Set the value of the cc.diverted application parameter to true and reprocess.
1096	Invalid Tax 1 amount (<amount>) for transaction with reference number <ref num> : <error message>	The tax amount is in an invalid format	Check the tax amount of the transaction with the specified reference number.
1097	Invalid Tax 2 amount (<amount>) for transaction with reference number <ref num> : <error message>	The tax amount is in an invalid format.	Check the tax amount of the transaction with the given reference number.

1001

Unrecognized Record Type

The record type number is not defined in this CC Feed process. This error is encountered when an incorrect 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 can be 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

1002

<param1>; data on this line not imported

This message is used for indicating that 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 and provide more insight on the issue.

1003

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

The card must be assigned to a user through the System Administration Tool.

The User screen in the SAT provides the functionality to attach credit cards.

1004

Credit Card # <masked card number> not assigned to a user.

The card must be assigned to a user using the System Administration Tool.

No employee information available in feed to match employee to card.

The card must be assigned to a user through the System Administration Tool (SAT).

The User screen in the SAT application provides a functionality to automatically assign credit cards to a user based on the employee number specified in the feed. Use the appropriate application parameter based on the card type to enable the functionality.

1005

Unrecognized Card: Transaction # <param1> refers to card # <param2>, which is not in the database. The transaction was not imported.

The Credit Card details are not available 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 database of the al- cc_card table. Card number can also be verified on the User Profile screen using SAT and in the data file as described above.

1006

Multiple Cards Found with Same Number:

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

We will be using the first one we found.

Multiple cards in the database have the same account number. When this scenario occurs the card can be assigned to wrong person. Thus, you must 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.

Remove the credit card linked to users who do not own the credit card using User Profile screen in SAT.

Extensity imports the first User Name that is found in the file obtained from the credit card vendor.

For the incorrect User Name, delete the transaction imported from the alcc_transaction table.

Discuss with the credit card vendor about the Credit cards associated with more than one User to resolve the issues in future files.

1007

There are <param1> currencies in the database that have the same currency code (<param2>).

We will be using the first one we found as the proper currency.

Currency Codes are not set up correctly in the system.

Identify the Currencies s with the same codes. Update the currency codes with the right code using the SAT application. Currency Data is available on the Corporate Data tab of the SAT application.

1008

There are <param1> merchants in the database that have the same name (<param2>), city (<param3>), and VAT number (< param4>).

We will be using the first one we found as the proper merchant.

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

This is often not an is- sue and does not affect the data integrity.

1009

Not importing duplicate transaction: Card Number is <param1>. Amount is <param2>. Posting Date is <param3>.

This error is often encountered, if the data file is imported twice.

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

1010

Currency code <param1> is not in the database

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

Contact 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.

Once the new currency code is setup, extract the transaction from the Out.txt file into a new file and run the ccimport process again to import the transaction.

1011

Transactions that have a zero amount are not imported. Reference number is <param1>.

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

1012

Your alcc_sic_code table does not have a default entry. The default entry should have no SIC code (i.e. blanks, or null).

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

1013

Credit Card #<param1> has been added to the database and has been assigned to a user. Please verify the following information. Cardholder Name : <param2> Extensity User Name : <param3>

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

1014

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

When trying to associate a Credit card to an Extensity User the ccimport program could not find a matching SSN in the database

Verify if the SSN is sent correctly from Citibank. If sent correctly, verify if the Extensity User exists in the system and verify the SSN for that user. If all the above checks are correct, call Extensity Customer Support.

1015

Credit Card #<param1>: More than one Extensity user has the Social Security Number associated with this card. Cardholder Name : <param2>

This issue is encountered when same SSN is assigned to more than one Extensity user.

Identify the users in the Extensity database with the specified SSN. Identify why more than one people use the same SSN.

1016

Credit Card #<param1> has been added to the database but has not been assigned to a user.

Invalid social security number was provided. Cardholder Name : <param2>

This error is encountered when the format of the SSN number is incorrect. For example, it may not be a nine-digit number.

Verify if the SSN is sent correctly from Citibank. If sent correctly, verify the Extensity User exists in the system. Verify the SSN for that user. Update the SSN in the system using SAT, if incorrect. If SSN is sent incorrectly from Citibank, call Citibank to correct the information.

1017

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

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

This is only an informative message that indicates a new credit card has been assigned to a user.

No action requires to be taken.

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 error is encountered only when a user match is made through SSN option and the target SSN is not found including the database users.

If SSN does not exist in the Database, matching is not done and the card is not assigned to a user.

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 error is encountered when same SSN is assigned to more than one Extensity user.

Verify if the SSN is being sent correctly from Citibank. If sent correctly, identify the correct Extensity User for the respective SSN in the system. For all other users associated with the SSN update the SSN to the correct SSN.

Check the data being imported for inaccuracies.

1020

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

Cardholder Name : <param2>

This error is encountered when a user match is made through the SSN option and the target SSN is not found among the database users.

If SSN does not exist in the database, data is not matched and the card is not assigned to a user.

1021

Unrecognized Country Code: <param1>

Check the country code associated with the transaction. Use the SAT application to verify whether the corresponding Country code is present in the system.

1023

Not importing duplicate card: Card number = <param1>

This error is not considered as the bank often provides repeated card information in every new transaction.

Card has already been imported into the system. Confirm with Citibank for the duplicate entries being sent to the data file.

1024

Credit card account data updated:Data for card number <param1> are updated

This is only an informative message that indicates that a credit card data has been updated. No action is required.

1026

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

SIC code must always be an integer

Investigate why SIC code data is not in the correct format.

1027

Invalid SSN Number:<param1>

Investigate the reason for the SSN data to be not in the correct format.

1028

Merchant data updated

This is only an informative message

1029

Invalid Employee Number

The employee number is missing.

1030

Credit Card #<param1>No Extensity user has the employee number associated with this card.

Cardholder Name: <param2>

1031

Credit Card #<param1>

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

Cardholder Name: <param2>

1032

Card deactivated, Card #<param1>

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

The card was not imported.

Use SAT to activate the card before new data associated with the card is imported.

The detailed log messages are self-explanatory.

1034

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

You must know the reason for the card to be assigned to <param1>. If <param1> is not the right card user, you must use SAT to remove the attached card from <param1> and reattach to <param2> instead.

1035

No data insertion allowed for <param1>

The corresponding element data, <param2> do not exist.

This error is encountered as the required data is missing.

1036

Inconsistent currency amounts encountered:

Native and billed amounts (<param1> and <param2>) don’t have a consistent sign.

The transaction was not imported.

This error is encountered due to a data issue.

Check the data.

1037

Inconsistent date string encountered:

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

This error is encountered due to a data issue.

Check the data.

1038

Skip the invalid airline departure date, <param1>

The corresponding transaction can be imported even without a valid date for the airline departure.

Check the data related to the airline departure date.

1039

Skip the invalid hotel arrival date, <param1>

The corresponding transaction can be imported even without a valid date for the hotel arrival.

Check the data related to the hotel arrival date.

1040

Skip the invalid hotel departure date <param1>

The corresponding transaction can be imported even without a valid date for the hotel departure.

Check the data related to the hotel departure date.

1041

Same currency but inconsistent amounts encountered:

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

This error is encountered due to a data issue.

Check data related to currency amounts.

1042

Transaction data not imported

This message is for the information purpose only.

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

1043

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

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

Check the data related to the hotel stay duration.

1044

<param1> is not a recognizable date

The corresponding transaction can be imported even without date.

Check the date format.

1045

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

The corresponding transaction can be imported even without a valid amount for the hotel room.

Check the data related to the hotel room amount.

1046

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

The corresponding transaction can be imported even without a valid tax one amount for the hotel room.

Check the data related hotel room tax one data.

1047

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

The corresponding transaction can be imported even without a valid tax two amount for the hotel room.

Check the data related to the hotel room tax two.

1048

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

The corresponding transaction can be imported even without a valid amount for the hotel phone.

Check the data related to the hotel phone amount.

1049

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

The corresponding transaction can be imported even without a valid tax one amount for the hotel phone.

Check the data related to the hotel phone tax one.

1050

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

The corresponding transaction can be imported even without a valid tax two amount for the hotel phone.

Check the data related to the hotel phone tax two .

1051

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

The corresponding transaction can be imported even without a valid amount for the hotel restaurant.

Check the data related to the hotel restaurant amount.

1052

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

The corresponding transaction can be imported even without a valid tax one amount for the hotel restaurant.

Check the data related to the hotel restaurant tax one data.

1053

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

The corresponding transaction can be imported even without a valid tax two amount for the hotel restaurant.

Check the data related to the hotel restaurant tax two.

1054

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

The corresponding transaction can be imported even without a valid amount for the hotel service.

Check the data related to the hotel service amount.

1055

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

The corresponding transaction can be imported even without a valid tax one amount for the hotel service.

Check the data related to the hotel service tax one.

1056

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

The corresponding transaction can be imported even without a valid tax two amount for the hotel service.

Check the data related to the hotel service tax two.

1057

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

The corresponding transaction can be imported even without a valid tip one amount for the hotel.

Check the data related to the hotel tip amount one.

1058

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

The corresponding transaction can be imported even without a valid tip two amount for the hotel.

Check the data related to the hotel tip amount two.

1059

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

The corresponding transaction can be imported even without a valid other amount for the hotel.

Check data related to the hotel other amount.

1060

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

The corresponding transaction can be imported even without a valid tax amount for the hotel.

Check data related to the hotel other tax one amount.

1061

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

The corresponding transaction can be imported even without a valid tax amount for the hotel.

Check data related to the hotel other tax two amount.

1062

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

The corresponding transaction can be imported even without a valid daily room rate of the hotel.

Check data related to the hotel daily room rate.

1063

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

The corresponding transaction can be imported even without a valid daily room rate tax amount for the hotel.

Check data related to the hotel daily room rate tax.

1064

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

The corresponding transaction can be imported even without a valid laundry amount for the hotel.

Check data related to the hotel laundry amount.

1065

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

The corresponding transaction can be imported even without a valid hotel gift shop amount.

Check data related to the hotel gift shop amount.

1066

Skip the invalid data for hotel movie amount, <param1>

The corresponding transaction can be imported even without a valid amount for the movie.

Check data related to the hotel movie amount.

1067

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

The corresponding transaction can be imported even without a valid amount for the hotel business center.

Check data related to the hotel business center amount.

1068

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

The corresponding transaction can be imported even without a valid health club amount for the hotel.

Check data related to the hotel health club amount.

1069

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

The corresponding transaction can be imported even without a valid total tax amount for the hotel.

Check data related to the hotel total tax.

1070

Unrecognized transaction code, <param1>.

Record will not be processed.

The first character in the Visa VCF40 feed is not a number between one to four or six to nine, therefore, the record is skipped.

1071

Transaction data updated

This is an informational message and not a warning.

1072

Credit card with account number <param1> not found. Record will not be processed.

The Visa card that is indicated as update only does not exist in the database and cannot be added.

This scenario is applicable for the Visa importer only.

1073

Transaction with reference number <param1> not found. Record will not be processed.

The transaction code is ’update’, however, the transaction does not exist in the database. The transaction is not added.

This error is also encountered when level 2 or level 3 data is being processed and the transaction is not found by reference number. In these cases, the level 2 or level 3 data is not being processed.

This scenario is applicable for the Visa importer only.

1074

Credit card with account number <param1> already exists. Card will not be inserted.

The Visa cards that are indicated as add only exists in the database but cannot be updated.

This scenario is applicable for the Visa importer only.

1075

Transaction with reference number <param1> already exists. Transaction will not be inserted.

The transaction code is ’add’ but the transaction already exists in the database. The transaction is not added.

This scenario is applicable for the Visa importer only.

1076

Level 3 record with folio id <param1> and sequence number <param2> is linked to a transaction with reference number <param3> that can’t be found. Level 3 record will still be inserted. If the transaction comes in later, they will be linked.

The level 3 data is imported, however, not linked to the associated transaction as no transaction with the specific reference number is found.

This scenario is applicable for the Amex1080 importer only.

1077

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

The level 3 data is not imported as the data does not have the reference number of the associated transaction.

This scenario is applicable for the Amex1080 importer only.

1078

Level 3 record with transaction reference number <param1> has no folio id. Record will not be processed.

The level 3 data is not imported as the data does not have a folio ID.

This scenario is applicable for the Amex1080 importer only.

1079

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

The level 3 data is not imported as the data does not have a sequence number.

This scenario is applicable for the Amex1080 importer only.

1080

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

1080 Level 3 record with folio id <param1> does not balance to the transaction amount. Record will not be processed. Only level 3 records that indicate the folio amount balances to the transaction amount, are processed.

The Amex1080 specification 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 to the local charge amount.

This scenario is applicable for the Amex1080 importer only.

1081

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

The level 3 data is not imported as the data do not match with the transaction.

Based on the Amex1080 specification , “’Expense Vendors must code to only use values = 1”.

This scenario is applicable for the Amex1080 importer only.

1082

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

Record will not be processed.

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

This scenario is applicable for the Amex1080 importer only.

1083

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

The credit card is inserted or updated as the payment type is inactive.

Activate the payment type through SAT.

1084

Unrecognized Card. Transaction # <param1> refers to card #<param2> which is not in the database. Temporary card will be created for the transaction.

Credit card for the associated transaction does not exist in the data base. However, a temporary credit card is created, as the value of the cc.createTemporaryCard application parameter is set to True. The transaction is imported and linked to the temporary credit card. If the card data is later imported, the data of the temporary card is updated.

This is a warning message and not an error message.

1085

Transaction detail for transaction with reference number <param1> not found.

Record will not be processed.

The transaction specified is for an air or rail trip but details are not available.

This is an informational message and only applicable for the Visa importer.

1086

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

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

This scenario is specific to the Visa importer.

1087

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

The credit card limit is in an incorrect format.

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 not updated.

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

1089

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

The value of the cc.VCF40EmpNumMatch application parameter is set to True, however, the value of the cc.VCF40.EmpNumPosition application parameter is not in integer format. The importer uses the default position 23 to find the employee number.

This scenario is specific to the Visa importer.

1090

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

The value of the cc.AmexLevel3ReferenceNumberType application 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 looks for the transaction ID which is used to link the level record to the transaction. The error is encountered when the level 3 data is not imported as the transaction ID is not specified. This is only applicable for the Amex1080 importer.

1091

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

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

This scenario is applicable for the Amex1080 importer only.

1092

String substitution <param1>

Data read by an importer can be subject to string substitution before regular processing. For example, you might require that all instances of the special character ‘|’ be re- placed with ‘/’. You can set up this kind of substitution using the cc.substituteSubstring.enabled, cc.substituteSub- string.find and cc.sub- stituteSubstring.re- place application parameters.

Whenever a substitution occurs, a warning message is displayed on the log.

Additional information such as record type, tag, element, or field can also be written.

Informational only.

1093

No transaction found for transaction detail with reference number <ref num>. Record will not be processed.

Transaction level 2 detail is stored in a separate table as transaction data; the data is linked to the reference number. If the reference number of the record does no match a transaction reference number, the system displays the error message. The transaction is imported but the details are not imported.

Check he feed file has reference numbers that match the secondary data.

1094

Transaction found with reference number <ref num> belonging to diverted card <masked card number> but cc.diverted not set. Set cc.diverted to true and reprocess.

The transaction is linked to a diverted card. However, the diverted card functionality is not enabled.

Set the value of the cc.diverted application parameter to True and reprocess.

1095

Can't set processor on diverted card for <name on card> with account number <masked account number> because cc.diverted not set. Set cc.diverted to true and reprocess.

Set the value of the cc.diverted application parameter to true and reprocess.

1096

Invalid Tax 1 amount (<amount>) for transaction with reference number <ref num> : <error message>

The tax amount is in an invalid format

Check the tax amount of the transaction with the specified reference number.

1097

Invalid Tax 2 amount (<amount>) for transaction with reference number <ref num> : <error message>

The tax amount is in an invalid format.

Check the tax amount of the transaction with the given reference number.