Financial Institution Parser Plug-in Interface Overview
The Financial Institution Parser Plug-in interface uses SuiteScript 2.0. Your entry point scripts and supporting library scripts must also use SuiteScript 2.0. For information, see SuiteScript 2.x Script Creation Process and SuiteScript 2.x.
Use a Financial Institution Parser Plug-in implementation to parse and retrieve the following:
-
Bank and credit card data for matching and reconciliation
-
Corporate card charges for expense reporting
Financial Institution Parser Plug-ins enable you to create and upload your own parsers for different bank and credit card statement formats and store them in NetSuite. The plug-in translates the information from data formats not supported by NetSuite’s default parsers into financial data NetSuite can understand and use. This enables you to import statements in additional data formats, and then use the appropriate downstream feature, such as bank data matching and reconciliation or expense reporting.
To create a Financial Institution Parser Plug-in, you need to create the plug-in implementation script file, and then upload the script file and other utility files as required. For details, see Creating a Financial Institution Parser Plug-in Script File.
You can define alternative implementations that suit your needs by customizing the core plug-in logic. To accommodate this process, NetSuite provides an interface definition that describes the name, parameters, and return type of each function defined in the plug-in’s interface. For details, see Financial Institution Parser Plug-in Interface Definition.
To use a Financial Institution Parser Plug-in, you need to create or edit a format profile record. The plug-in is compatible with both the Bank Reconciliation and Corporate Card Expenses format profile type.
To import corporate card expense data, you must use a Financial Institution Parser Plug-in.
If you are configuring an automatic bank data import, you must use a Financial Institution Parser Plug-in with a Financial Institution Connectivity Plug-in. Together, these enable you to configure a direct connection to your data source so you can retrieve and parse financial data.
You can use a Financial Institution Parser Plug-in to configure automatic or manual import of bank or credit card data for reconciliation. If you are configuring corporate card expense data imports for expense reporting, you should only use the automatic import method.
For details on configuring financial institution records and associated format profiles, see Creating Financial Institution Records.
To run and test a Financial Institution Parser Plug-in, see Conditions for Running a Financial Institution Parser Plug-in and Testing a Financial Institution Parser Plug-in.
A Financial Institution Parser Plug-in is supported by the SuiteCloud Development Framework (SDF). SDF enables you to customize your NetSuite account from an integrated development environment (IDE) on your local computer. For details, see SuiteCloud Development Framework.
You can customize a Financial Institution Parser Plug-in in SDF by defining fiparserplugin objects. For details, see Financial Institution Parser Plug-ins as XML Definitions.
For more information about Financial Institution Parser Plug-ins, see the following topics:
|
NetSuite Role |
Help Topics |
|---|---|
|
All roles |
|
|
Developer |
|
|
Administrator |
In addition to using the API specifications to create a plug-in, you can use a default implementation of the plug-in called the AMEX Parser Plug-in. This plug-in is bundled with the AMEX Connectivity Plug-in and is provisioned by the AMEX Corporate Card Integration SuiteApp. Use these plug-ins if you want to import corporate card charges from American Express and do not want to write your own plug-ins. For details, see American Express Integration for Expense Reporting.