Transaction Category Support for Imported Transactions in
NetSuite enhances Financial Institution Parser Plug-in with transaction category support for imported banking transactions.
The recent enhancements to the Financial Institution Parser Plug-in allow for the inclusion of an optional transaction category for banking transactions imported into NetSuite. This update empowers plug-in developers by enabling them to capture and include transaction categories in the createNewTransaction API call, further improving transaction data handling.
What Changed?
NetSuite now allows plug-in authors to specify a transaction category when importing banking transactions. This is done by including a category field in the additionalFields parameter of the createNewTransaction() function.
Note:
- End-User Impact: Currently, there is no visible impact on the end-user interface or behavior. Existing integrations remain intact if no transaction category is provided.
- Future Enhancements: While the transaction category is not yet used within the UI, this data will support future enhancements in transaction matching processes.
Using createNewTransaction API
To leverage this new feature, plug-in authors should utilize the createNewTransaction function, which has the following parameters:
"text-purple-400">function createNewTransaction(options) { // Implementation here}Key parameters of interest include:
| Parameter | Type | Required | Description |
|---|---|---|---|
Since | String | Yes | The date of the transaction in ISO 8601 format. |
amount | Number | Yes | The transaction amount. |
transactionTypeCode | String | Yes | Maps to a valid bank data type in NetSuite. |
uniqueId | String | No | Used to avoid duplicate transactions. |
category | String | No | Optional category for the transaction. |
Developers are encouraged to begin using the transaction category field to prepare for future features related to transaction categorization and management.
Who This Affects
- Roles Impacted:
- Plug-in Authors
- Developers focusing on banking integrations
- Financial Administrators (indirectly, as future enhancements will assist in transaction matching processes)
In summary, the enhancement of transaction category support for imported transactions allows developers to better organize and track banking transactions in NetSuite, paving the way for future enhancements that will likely benefit transaction management.
Key Takeaways
- NetSuite now supports transaction categories for imported transactions via the Financial Institution Parser Plug-in.
- Plug-in authors can specify transaction categories using the
additionalFieldsparameter in thecreateNewTransactionAPI. - Current UI remains unaffected; categories are not yet operational in the interface.
- The inclusion of transaction categories prepares for future enhancements in transaction management.
Source: This article is based on Oracle's official NetSuite documentation.
Frequently Asked Questions (4)
Do I need to modify existing plug-ins to support transaction categories?
How can plug-in authors specify a transaction category for an imported transaction?
Will including transaction categories affect the current user interface in NetSuite?
Are there any prerequisites for using the transaction category in the Financial Institution Parser Plug-in?
Was this article helpful?
More in Banking
- Payment Date Prediction for Invoices in NetSuite 2026.1
Starting in NetSuite 2026.1, you can now see AI-generated payment date predictions for invoices, enhancing cash flow planning.
- Manually Running Reconciliation Rules in NetSuite 2026.1
In NetSuite 2026.1, you can now manually run reconciliation rules from the Match Bank Data page to streamline bank transaction matching.
- Payment Automation Enhancements in NetSuite 2024.2
Explore Payment Automation enhancements in NetSuite 2024.2, including multi-subsidiary support for streamlined payment processes.
- Submitting Matched Transactions in NetSuite 2026.1
In NetSuite 2026.1, streamline your transaction submission process with enhancements for matched and user-cleared transactions.