Transaction Parser Configuration

This section explains the options for the Transaction Parser dropdown list. From the list, you can select either a standard or custom parser:

• Standard parser – Available through either the Bank Statement Parsers SuiteApp or AMEX Corporate Card Integration SuiteApp:

  • Bank Statement Parsers SuiteApp – Includes OFX/QFX , BAI2, MT940, CAMT.053, and CSV file formats. After you select the BAI2, MT940, or CAMT.053 parser and save the format profile record, the Parser Configuration subtab values appear and is populated with configuration settings. For details on modifying the parser-specific default settings, see Configuring Standard Bank Transaction Parsers. For details on the SuiteApp, see Bank Statement Parsers SuiteApp.

  • AMEX Corporate Card Integration SuiteApp – Includes the AMEX Parser Plug-in, which you use to parse corporate card charges for expense reports. For details, see American Express Integration for Expense Reporting.

    The AMEX Parser Plug-in does not support parser configuration. When you select this parser plug-in, the Parser Configuration subtab is not visible.

• Custom parser – Created using the Financial Institution Parser Plug-in interface. For a custom (non-standard) parser to be available in the Transaction Parser list, you must develop and upload one to NetSuite. For details, see Financial Institution Parser Plug-in.

  Note:

  The Bank Statement Parser Plug-in interface is not supported as of NetSuite 2020.2.

If you’re creating a new format profile, save it first before configuring the parser.

Related Topics

• Financial Institution Records
• Format Profile Creation
• Configuring a Connection to a Financial Institution (Without a SuiteApp)
• Bank Account Linking
• Mapping Custom Bank Codes

General Notices