Skip to main content
Imports
Search
Search Indirect Tax Support Help and Support.

This article applies to:

  • Product: ONESOURCE Indirect Tax Compliance,ONESOURCE Indirect Tax
  • Subject: Import

Import errors

The
Import details
 screen shows errors and warnings. The
Errors
 column shows allocation, import and rule errors. To view errors, select the hyperlinked number in the
Errors
 column.
Import details screen with the errors column highlighted showing 50 and 14.
The window that opens shows error details of the import. The header bar for the error screen contains details of import name, file name, imported date, allocation and import specification.
note
This information is also visible in
Active
,
Edited
 and
Warnings
 screens.
Error screen showing this error: Errors for ESL-EPL (published countries) - TDS transactions. Filename and import date, import specifications, and allocation specifications.
Columns in the errors screen:
  • Error
    : Displays the details of the error.
  • Original Line Number
    : Displays the line number from the source file.
  • Entity
    : Name of the entity allocated to. Blank if the entity cannot be determined (i.e. import errors and allocation errors).
  • Reporting Date
    : Reporting date for the transaction. Blank in the case of import errors but not for allocation or rule errors.
  • Entity Code
    : Blank in the case of import errors but not for allocation or rule errors.
  • Jurisdiction ID
    : Blank in the case of import errors, but not for allocation or rule errors.
  • InvoiceID: Blank for import errors but not for allocation or rule errors.
  • Import Allocation Errors: Provides detailed information. For example, if tax code or entity code is not mapped:
    • The Tax Code
      XXX
       is not mapped
    • The Entity Code
      ZZZ
       is not mapped.
    The same has been shown for any allocations being missed for mappings, including Entity, TransactionType, TaxCode, SupplyType, and IrrecoverableCode.
Error Message Reference
Error message
Explanation
Resolution
Error importing the original value from 'line 2, column 1' into the 'text' field 'EntityCode' The field is blank (zero length) but a value is required. The following lines have the this type of error at the same location: 2->11.
This error appears when the
EntityCode
 value is missing from the source file. This field is required to import data.
Check the source file and update the missing entity code value. The import should be successful after you update the missing mandatory field.
Error importing the original value from 'line 12, column 2' into the 'date and time' field 'ReportingDate' String was not recognized as a valid DateTime. Format used 'dd/MM/yyyy'. The following lines have this type of error at the same location: 12->21.
This error appears when the mandatory
ReportingDate
field and values are missing in the source file.
Check the source file and update the missing
Reporting Date
 value. The import should be successful after you update the missing mandatory field.
Error importing the original value from 'line 2, column 5' into the 'decimal' field 'TransactionAmountNet' Input string was not in a correct format. The following lines have this type of error at the same location: 2->9.
This error appears when the values for mandatory field
TransactionAmountNet
are missing in the source file.
Check the source file and update the missing
Transaction Amount Net
 value. The import should be successful after you update the missing mandatory field.
Error importing the original value from 'line 4, column 6' into the 'decimal' field 'TransactionAmountTax' Input string was not in a correct format.
This error appears when values for mandatory field
TransactionAmountTax
 are missing in the source file.
Check the source file and update the missing
Transaction Amount Tax
 value. The import should be successful after you update the missing mandatory field.
Error importing the original value from 'line 4, column 3' into the 'text' field 'TransactionTypeCode' The field is blank (zero length) but a value is required.
This error appears when values for mandatory field TransactionTypeCode are missing in the source file.
Check the source file and update the missing
Transaction Type code
 value. The import should be successful after you update the missing mandatory field.
Error importing the original value from 'line 4, column 4' into the 'text' field 'TaxClassificationCode' The field is blank (zero length) but a value is required.
This error appears when values for mandatory field
TaxClassificationCode
 are missing in the source file.
Check the source file and update the missing
Tax Classification code
 value.The import should be successful after you update the missing mandatory field.
Field 'GeneralLedgerAmount' cannot have a blank value
This error appears when values for mandatory field
GeneralLedgerAmount
 are missing in the source file.
Check the source file and update the missing
General Ledger Amount
 value. The import should be successful after you update the missing mandatory field.
Template license is missing for jurisdiction 'CL', please add the license and import again.
This error appears when the jurisdiction's license is missing.
Check
Administration
 >
Customer Management
 for the respective country licence details.
Entity code 'US2079812' not mapped
This error appears when
EntityCode
 is not mapped in the allocation spec.
Check the
Allocation Specification
 >
Entity Map
 file for missing entity code mapping and update it. The import should be successful after you update the missing mandatory field.
InvoiceDate' is required for exchange rate conversions for Transaction Currency 'GBP' to Currency 'EUR'
This error appears when exchange rates and the invoice date are missing in the source file.
Check the source file and update the missing
Invoice Date
 value. The import should be successful after you update the missing mandatory field.
Error converting the value '8/15/2021' from 'line 2, column 2' into the 'date and time' field 'ReportingDate' String was not recognized as a valid DateTime. The following lines have the this type of error at the same location: 2->11.
This error appears when source file has an incorrect date format for the
ReportingDate
 field.
Check the import specification and source file for the expected date format. The format in both should match. The import should be successful after you update the missing mandatory field.
Error importing the original value 'GBBP' from 'line 2, column 9' into the 'text' field 'TransactionCurrency' The value is '4' characters long but the maximium allowed length is '3'. The following lines have the this type of error at the same location: 2->4.
This error appears when the
Transaction Currency
 column contains data with more than three characters.
Check the currency code value in the source file and ensure that it contains three characters. The import should be successful after you update the missing mandatory field.
Invalid currency conversion TransactionCurrency 'GBP' To Currency 'EURR'
This error is caused by an incorrect exchange rates configuration.
Check the exchange rate mappings in the allocation specification and correct them.
Exchange Rate 'GBP' To 'EUR' not set up for 'InvoiceDate' '2022-05-05'
This error appears when exchange rates are not configured for given date.
Check the exchange rate mappings and update the mapping for the missing date.
Error while importing. Please review import spec/source file - One or more errors occurred.
This error appears when an incorrect import specification is selected for data import.
Check that you are using correct import specification.
LineRule Data - Data specifies a column (6) out of range (5). The LineItem 'TransactionAmountTax' for the LineTypeRule 'Data - Data' specifies a column with index '6' but there are only '5' columns available. Index was out of range. Must be non-negative and less than the size of the collection. Parameter name: index
This error appears when the wrong file type imported. The system will give various errors. For example the specificaiton is in .xlsx format, but data is .txt.
Check that you are using correct import specification.
File has already been imported.
This error appears when the setting
Do not allow import with same file name more than once
 is enabled. When enabled, a user is prevented from importing a file with the same name more than once.
Select
Administration
>
Settings
 and check the setting
Do not allow import with same file name more than once
 Disable the setting or rename the source file.
System Error in Validating
This error appears when an exception is raised in a validation step and cannot be corrected by altering data.
Report this issue to the ONESOURCE Support team.
Failed to parse CSV file. Invalid end quote (found in line 1103) Invalid end quote(found in line 1103)
This error appears when there are quotes in a.csv file. This can happen because of an invalid .csv file.
Check
Administration
>
Settings
. Enable the setting
Importer: Use old CSV reader
.

Related Content