Corporate Card Connectivity
You can now use format profiles to configure imports for expense reporting in addition to bank and credit card reconciliation. If you use the Expense Reports feature, you can set up imports of corporate card charges for employee expense reports. To set up a format profile for manual import of corporate card charges, create an implementation of the new Financial Institution Parser Plug-in. For details on the plug-in, see the help topic Financial Institution Parser Plug-in Interface Overview. To set up a format profile for automatic import of corporate card charges, you need to use both a parser and connectivity plug-in. You can do one of the following:
- Use the connectivity and parser plug-in available through the new AMEX Corporate Card Integration SuiteApp. These plug-ins enable you to configure a direct connection to American Express to automatically retrieve expense data daily. For information about corporate card integration with American Express, see American Express Integration for Expense Reports.
- Use a custom connectivity and parser plug-in built with the Financial Institution Connectivity Plug- in and Financial Institution Parser Plug-in APIs. These plug-ins enable you to configure a direct connection to a specific corporate card company, not just American Express. For information on the Financial Institution Connectivity Plug-in, see the help topic Financial Institution Connectivity Plug-in Interface Overview. If you configure automatic import of corporate card charges, you can do the following:
- Validate expense lines daily
- Have corporate card charges automatically available in the system, which employees can add to expense reports
- Provide automatic email notification to employees about their newly imported charges For the overall procedure on configuring corporate card imports, see the help topic Creating Format Profiles for Expense Reporting. For details on the corporate card expense reporting process, see the help topic Corporate Card Expenses.
Auto-Create Account Transactions from Bank Import
In this release, you can automate the process of creating and matching account transactions with imported bank data. Auto-create rules enable you to automatically create and match the following transactions:
- Deposits and charges for general ledger bank accounts
- Charges and refunds for general ledger credit card accounts Consequently, you no longer need to manually enter an account transaction for every imported bank line that does not have a corresponding transaction in NetSuite. If you import bank lines with a recurring Payor/Payee or Memo, auto-create rules look for imported bank lines with the transaction type and Payor/Payee specified by the rule. If the imported bank line has no Payor/Payee, the rule looks for the Memo that was specified. You do not need to manually create an auto-create rule, because the system generates one provided that certain criteria are met. For details, see the help topic Generating Auto-Create Rules. Note: Transactions that are automatically created and matched do not impact your general ledger account until you submit them on the matching page. For details on submitting transactions, see the help topic Submitting Transaction Matches. For information on automatically creating account transactions, see the help topic Automatic Creation of Account Transactions.
Manage Duplicates on the Match Bank Data Page
In NetSuite 2020.1, imported bank lines flagged as duplicates were automatically excluded from the matching process and were displayed on the Import Details page. On the Import Details page, you could clear the Duplicate box next to an imported bank line to include it in the matching process.
Now, you can manage duplicates directly from the Match Bank Data page. NetSuite automatically stores
imported bank lines flagged as duplicates in the Excluded subtab. If the system misidentifies an imported bank line as a duplicate, you can include it in the matching process by clicking Restore. See the help topic Restoring Excluded Bank Data. For information on the matching process, see the help topic Matching Bank Data.
Financial Institution Parser Plug-in Interface
In NetSuite 2020.1, you could import bank and credit card data for reconciliation using the Bank Statement Parser Plug-in interface. In NetSuite 2020.2, the new Financial Institution Parser Plug-in interface enables you to import and parse additional data types, including corporate card expenses. This plug-in interface enables you to develop
SuiteScript plug-ins designed to import the following:
- Bank and credit card data for reconciliation
- Corporate card expense data for expense reporting For more details on the Financial Institution Parser Plug-in interface, see the help topic Financial Institution Parser Plug-in Interface Overview. For details on the Financial Institution Parser Plug-in interface definition, see the help topic Financial Institution Parser Plug-in Interface Definition. If you want to connect to American Express to retrieve corporate card charges, you can use the plug- ins available through the new AMEX Corporate Card Integration SuiteApp. For details, see the help topic
American Express Integration for Expense Reporting
You can use the Financial Institution Parser Plug-in interface to create and manage plug-ins in NetSuite or in the SuiteCloud Development Framework (SDF). For information on SDF support for Financial Institution Parser Plug-ins, see Financial Institution Parser Plug-in Support. Banking Import History Page Improvements
View Import History and Delete Imports
As seen in the following illustration, the Banking Import History page (previously called Imported Statement List) now includes status details about each bank import. You can expand each row to view the import details.
Rather than going to the Import Details page for each import, you can now see import details such as
error messages and delete manual imports from one place. For details, see the help topics Viewing Imported Banking Data and Deleting Imported Statements.
Troubleshooting Information
The Banking Import History page is a place to audit imports and to troubleshoot issues. If an import fails, NetSuite displays a Failed status with a red exclamation mark icon. If you have the Import Online Banking File permission with create-level access at a minimum, NetSuite displays a specific failure reason in the expanded details. The following illustration displays a failed import and a corresponding failure reason:
Fewer Columns
The Banking Import History page provides the status of recent imports and helps you troubleshoot issues. Other information such as the number of imported, automatched, and duplicate bank lines has been removed. The Next Steps column has also been removed. For more information, see the help topic Viewing Imported Banking Data.