1. Accounting
  2. Banking
  3. Bank Statement Parsers SuiteApp
  4. Bank Statement Parser Reference
  5. CAMT.053 Parser
  6. CAMT.053 File Import Error Messages

CAMT.053 File Import Error Messages

The following table lists some common file import errors and how you can fix them.

Error Message

Cause or Scenario

Solution

The file upload failed because it does not conform with the valid (CAMT.053.001.02 XML/CAMT053.001.08) Format. Contact your bank to correct the error, and re-upload the file again.

One or more elements in the XML file you uploaded don't conform to the following schemas:

  • camt.053.001.02.xsd

  • camt.053.001.08.xsd

For more information, compare your XML file with the official schemas in the ISO 20022 Messages Archive.

Contact your financial institution for assistance.

The file mapping must begin with '<BkToCstmrStmt> <Stmt>' to import the transactions from the file to NetSuite.

Incorrect parser configuration.

In the Format Profile record, under the Parser Configuration subtab, verify that the File Mapping value for each NetSuite mapped field begins with <BkToCstmrStmt><Stmt>.

Each tag used in the file mapping must be enclosed in '<' and '>', and must be separated by a space. For example, <BkToCstmrStmt> <Stmt> <Acct> <Id> <IBAN>.

The file mapping values in the Parser Configuration subtab don't follow the required tag format.

Tags must follow these rules:

  • Enclose each tag in angle brackets (< >).

  • Separate tags with a single space.

The configurations for the following field(s) will be removed:

<NetSuite field names>

Click OK to restore the default file mapping or click Cancel to manually configure the file mapping for the affected fields.

All mappings for the field are missing from the Parser Configuration subtab.

Verify that your parser configuration includes all standard NetSuite fields.

For the list of default CAMT.053 mapping values, see Configuring CAMT.053 Parser.

The Credit/Debit value is sourced from the statement file to determine the GL Impact of the transaction. Click OK to set the value to N/A and use the indicator in the file or click Cancel to override the amount indicator in the file.

The Credit/Debit field in the Transaction Code Mapping subtab is set to a value other than N/A.

Check your parser configuration.

The bank statement file contains {number} transactions that are not yet posted or booked in your bank account. Only booked or posted transactions are imported.

NetSuite imports only transactions that have Book status.

Verify the transaction status in your CAMT file.

  • CAMT.053.001.02 (version 2) format

                            <Document>
  <BkToCstmrStmt>
    <Stmt>
      <Ntry>
       <Sts>BOOK</Sts>
      </Ntry>
    </Stmt>
  </BkToCstmrStmt>
</Document>

  • CAMT.053.001.08 (version 8) format

                            <Document>
  <BkToCstmrStmt>
    <Stmt>
      <Ntry>
       <Sts><Cd>BOOK</Cd></Sts>
      </Ntry>
    </Stmt>
  </BkToCstmrStmt>
</Document>
Note:

If the status is not Book, contact your financial institution for assistance.

The file mapping {file mapping value} for NetSuite Field {NetSuite field value} already exists. Please enter a unique file mapping path.

Duplicate file mapping rows exist in the Parser Configuration subtab.

In the Format Profile record, under the Parser Configuration subtab, remove any duplicate file mapping rows.

Related Topics

General Notices