Financial Institution Parser Workflows
A Financial Institution Parser Plug-in is invoked when you configure a format profile record and during the bank data import process.
The following diagram shows the workflow for the format profile record:
When you create a format profile and select a Financial Institution Connectivity Plug-in, or edit a format profile that uses that plug-in type, NetSuite calls an interface function. The format profile type dictates which interface function is called:
-
If you are configuring a Bank Reconciliation format profile record, NetSuite calls the getStandardTransactionCodes() interface function. This retrieves custom transaction codes from the plug-in, which are displayed on the Code Type Mapping subtab.
-
If you are configuring a Corporate Card Expenses format profile record, NetSuite calls the getExpenseCodes() interface function to retrieve custom expense codes from the plug-in. These expense codes are displayed on the Expense Code Mapping subtab, which appears in place of the Code Type Mapping subtab.
-
If the plug-in selected in a format profile record implements the getConfigurationPageUrl() interface function, NetSuite retrieves a URL for configuring the plug-in. This URL appears on the Parser Configuration subtab on the Format Profile page.
For more details, see Format Profile Creation.
The following diagram shows the workflow for the bank data import process:
When an import occurs, NetSuite calls the parseData() interface function, which retrieves and transforms a data file into account and transaction data. The plug-in does the following:
-
Accesses the input data to be parsed, using the inputData interface object.
-
Creates a new account data set, using the createAccountData() object function.
-
Adds a new imported transaction to the account data set, using the createNewTransaction() object function.