Bank Statement Parsers SuiteApp

The Bank Statement Parsers SuiteApp delivers standard parser plug-ins that read bank and credit card statement files and import the data in NetSuite to aid with bank reconciliation. If the Financial Institution and Format Profiles are set up correctly, the SuiteApp can identify multiple bank accounts in a single file. For more information, see Creating Financial Institution Records and Format Profile Creation.

The SuiteApp also includes sample scripts you can download and use as a reference when you create custom parsers. For more information, see Downloading Sample Bank Statement Parsers Scripts.

The Bank Statement Parsers SuiteApp includes parser plug-ins for the following file formats in (Unicode) UTF-8 and UTF-8 BOM encoding:

• BAI2 — The BAI2 parser plug-in recognizes default and standard BAI2 bank transaction codes and supports account total and record count import validation. The SuiteApp also lets you set the decimal precision for the BAI2 parser plug-in.

• OFX/QFX — The OFX/QFX parser plug-in parses bank and credit card statement files that use OFX/QFX versions 102, 103, 211, and 220. The parser recognizes default and standard OFX/QFX bank transaction codes and supports using a period (.) or comma (,) as a decimal separator.

• MT940 — The MT940 parser plug-in recognizes standard SWIFT transaction bank codes and supports using a period (.) or comma (,) as a decimal separator. The plug-in also decodes remittance information from the bank and display it in a more readable format.

• CAMT.053 — The CAMT.053 parser plug-in parses bank statement files that use the CAMT.053.001.02 version and recognizes standard ISO bank transaction codes. The plug-in includes default mappings for XML elements to NetSuite fields. You can also create new mappings or override the defaults.

  Note:

  The CAMT.053 parser plug-in only supports (Unicode) UTF-8 encoding. Some editors add the BOM (Byte Order Marker) to the start of the file. You might need to use a third-party editor to convert your file to UTF-8 before importing it into NetSuite.

• CSV – The CSV parser plug-in parses bank statement files in CSV format. The plug-in includes a CSV Bank Statement Template you can use to format your bank statement files. Default mappings to NetSuite fields and formatting preferences are preconfigured based on the template file. Or, you can use your own CSV file and set up your format profile by mapping the file to NetSuite fields and updating the formatting preferences.

  Note:

  The CSV parser plug-in only supports (Unicode) UTF-8 encoding. Some editors add the BOM (Byte Order Marker) to the start of the file. You might need to use a third-party editor to convert your file to UTF-8 before importing it into NetSuite.

Read the following topics to learn more about the Bank Statement Parsers SuiteApp:

• Installing the Bank Statement Parsers SuiteApp

• Roles and Permissions for Bank Statement Parsers

• Setting Up Standard Bank Statement Parsers

• Supported Transaction Codes for Bank Statement Parsers SuiteApp

• File Import Error Messages for Bank Statement Parsers

General Notices