Configuring CSV Parser

A format profile specifies the transaction parser implementation that NetSuite uses to process imported bank statement files. When you select CSV in the Transaction Parser field, the Parser Configuration subtab becomes available. Configuring the CSV parser is part of the standard bank statement parser setup. For the complete workflow, see Setting Up Standard Bank Statement Parsers.

The Parser Configuration subtab contains the Field Mapping and Formatting Preferences subtabs. Use the Field Mapping subtab to map CSV column headers to NetSuite fields. Use the Formatting Preferences subtab to specify date and number formats, delimiters, text qualifiers, credit and debit indicators, and footer lines.

When the format profile is in Edit mode, the Parser Configuration subtab displays a link to a downloadable CSV Bank Statement Template. You can use the template to format your bank statement files for import. You can also get the template from the NetSuite File Cabinet at Documents > Files > File Cabinet. Then, in the SuiteBundles folder, go to Bundle 293699 > com.netsuite.bsp, then click the template folder. Alternatively, you can use your own CSV bank statement file.

Note:

The CSV parser plug-in only supports UTF-8 (Unicode) encoding.

The following sections explain how to configure each Parser Configuration subtab.

Configuring the Transaction Field Mappings for the CSV Parser

The Field Mapping subtab values default to the column headers of the CSV Bank Statement Template file. If you're using your own file, update and map the fields to avoid import errors.

To map your CSV file column headers to NetSuite:

1. On the Parser Configuration subtab of your format profile, click the Field Mapping subtab.

2. The following table lists the available mapping fields and how to enter appropriate values for each field. Enter the matching column header titles in your CSV file for these fields. Field mapping field values are not case-sensitive.

   Important:

   You must map the Account Number, Date, and Transaction Type fields. For transaction amounts, map either Amount or both Credit Amount and Debit Amount.

   Field Mapping	Description
   Account Number	Enter the column header that represents the bank account number in your CSV bank statement file. This field is required.
   Date	Enter the column header that represents the transaction date in your CSV bank statement file. This field is required.
   Amount	Enter the column header that represents the transaction amount in your CSV bank statement file. If the transaction amount is an absolute value, you must also map the Amount Indicator field to identify whether the amount is positive or negative. Also set the Credit Indicator and Debit Indicator preferences on the Formatting Preferences subtab. Map this field if your file uses one column for transaction amounts. Don't map this field with Credit Amount or Debit Amount.
   Credit Amount	Enter the column header that represents the credit amount in your CSV bank statement file. Map this field with Debit Amount if your file has separate columns for credit and debit amounts. Don't map this field with Amount.
   Debit Amount	Enter the column header that represents the debit amount in your CSV bank statement file. Map this field with Credit Amount if your file has separate columns for credit and debit amounts. Don't map this field with Amount.
   Amount Indicator	Enter the column header that represents the amount indicator in your CSV bank statement file. Map this field if the transaction amount shows as an absolute value. You'll also need to set the Credit Indicator and Debit Indicator preferences under the Formatting Preferences subtab.
   Payee or Payer Name	Enter the column header that represents the transaction payee or payer in your CSV bank statement file.
   Transaction Number	Enter the column header that represents the transaction number or ID in your CSV bank statement file.
   Amount Currency	Enter the column header that represents the currency of the transaction amount in your CSV bank statement file. Make sure the amount's currency matches the NetSuite GL account currency to avoid data import errors
   Memo	Enter the column header that represents the transaction memo in your CSV bank statement file.
   Transaction Type	Enter the column header for the bank transaction code or transaction type in your CSV bank statement file. The parser uses the value in this column as the transaction type code for the imported transaction. To map bank-specific transaction codes to NetSuite transaction types, see Mapping Custom Bank Codes and Transaction Types in Matching Rules. This field is required.
   Financial Institution ID	Enter the column header that represents the financial institution ID in your CSV bank statement file. The Financial Institution ID helps the system identify duplicate transactions based on data import history.
   Customer Name	Enter the column header that represents the customer name in NetSuite from your CSV bank statement file. Map this field if you're using the automatic creation of payment transactions feature in NetSuite.
   Customer ID	Enter the column header that represents the customer ID in NetSuite from your CSV bank statement file. Map this field if you are using the automatic creation of payment transactions feature in NetSuite.
   Invoice Numbers	Enter the column header for invoice numbers of received payments in your CSV file. If a line has more than one invoice number, separate them with a comma. Map this field if you are using the automatic creation of payment transactions feature in NetSuite.
   Account Closing Balance	Enter the column header that represents the account's closing balance in your CSV bank statement file.
   Closing Balance Date	Enter the column header that represents the closing balance date in your CSV bank statement file.

3. Click Submit.

Configuring the Formatting Preferences for the CSV Parser

By default, some fields on the Formatting Preferences subtab use your account preference (Home > Set Preferences). Make sure your file matches these preferences to avoid import errors.

To set the formatting preferences for the CSV parser:

1. On the Parser Configuration subtab of your format profile, click the Formatting Preferences subtab.

2. The following table lists the available formatting preferences and how to enter appropriate values for each preference.

   Formatting Preferences	Description
   Date Format	Enter the date format used in your CSV bank statement file. The Date Format preference applies to the Date and Closing Balance Date mappings. If you map Closing Balance Date, its value must use the format specified in the Date Format preference. By default, this field uses MM/DD/YYYY. You can use these date format combinations: 2 - 3 M (month), 2 D (day), and 2 or 4 Y (year) characters with no separators Example: MMDDYY, DDMMYYYY, or MMMDDYYYY 1 D (day) or 1 M (month) character but must include a separator. You can use hyphen (-), slash (/), period (.), or space as separators. Example: M-D-YYYY, YYYY-MM-D, or M-DD-YYYY The parser does not support long date formats. Example: Month D, YYYY, which interprets to March 1, 2021. Note: The CSV parser plug-in only supports English date abbreviations.
   Number Format	Select the number format for thousands separator and decimals. This preference determines the number format of your transaction amount in your CSV bank statement file. By default, this field uses the Number Format from Home > Set Preferences > Formatting.
   Negative Number Format	Select the format to display negative numbers. This preference determines the negative number format of your transaction amount in your CSV bank statement file. By default, this field uses the Negative Number Format from Home > Set Preferences > Formatting.
   CSV Column Delimiter	Select the delimiter character that separates column values in each row of your CSV bank statement file. The character must match the delimiter used in the file. If a value contains the delimiter, enclose the value with the character specified in Text Qualifier. By default, the value comes from the CSV Column Delimiter preference at Home > Set Preferences > Formatting.
   Text Qualifier	If your CSV bank statement file encloses column values, select the character used to enclose them. The character must match the qualifier used in the file. When an enclosed value contains the CSV Column Delimiter, the parser treats the delimiter as part of the value and does not create an additional column. For example, suppose that the delimiter is a semicolon (;) and the text qualifier is a double quotation mark ("). The parser reads "Payee; Inc." as one column value.
   Credit Indicator	Enter the character or code used in your CSV bank statement file for credit transactions. Set this preference if you are mapping the Amount Indicator field. Note: This preference is case-sensitive. Make sure the character or code matches the credit indicator value in your CSV file.
   Debit Indicator	Enter the character or code used in your CSV bank statement file for debit transactions. Set this preference if you are mapping the Amount Indicator field. Note: This preference is case-sensitive. Make sure the character or code matches the debit indicator value in your CSV file.
   Footer Lines	If your bank statement has footer lines, you can configure the parser to automatically remove them. Enter the number of footer lines in your bank statement file. This can be any positive number or zero. If your bank sometimes sends files with a different number of footer lines, check your footer lines settings before importing them into NetSuite.

3. Click Submit.

Related Topics

• Downloading Sample Bank Statement Parsers Scripts
• Preparing CSV Parser Bank Statement Files for Import
• CSV File Import Error Messages
• Identifying Unique Account IDs for Standard Bank Statement Parsers
• Setting Up Standard Bank Statement Parsers
• Supported Transaction Codes for Bank Statement Parsers SuiteApp

General Notices