Custom Transactions with NetSuite Integration

Our Solution

Based on the client’s requirement, we utilized the Custom Transactions functionality:

1. Navigation : To access Custom Transactions, we may go to Customization > Lists, Records & Fields > Transaction Types > New. There is a separate list for each custom transaction type. The custom transaction type you build must have a list style chosen. It is because it controls how transaction instances impact your general ledger. Remember that a list style cannot be altered after a custom transaction type has been saved. The Custom Transactions option offers different list styles: Basic, Journal, Header only, Sales and Purchase. All of these transaction styles determine how users interact with instances of this kind.

Basic: When adding transaction instances, users can submit a sequence of credits or debits to the accounts they designate using the Lines sublist. In the Account field of the transaction type for this style, you must provide the associated account that must be changed for balancing reasons.

Journal: Users who input transactions in a journal keep track of the credits and debits they make to the accounts they manually define. The only design that permits posts to eliminate subsidiaries is this one.

Header Only:Users do not explicitly specify accounts to credit or debit when using the header-only approach. The GL effect is instead computed using a Custom GL Lines plug-in implementation in this way.

Sales: This style allows users to design transaction instances that resemble invoice, cash sale, or credit memo transactions. The Items sublist, inventory effect, taxes (SuiteTax only), and revenue recognition all function similarly to a sales transaction.

Purchase: Users can build transaction instances using this style that resembles vendor invoices. The functionality, which includes the Items and Expenses sublists, amortization, taxes (only for SuiteTax), and inventory implications, is comparable to a buy transaction.

Note: Only the Basic and Journal List styles exhibit the GL effect. A standard form is automatically produced when a custom transaction type is established. You may use this form to input transaction instances and make adjustments, such as moving data around or marking them as read-only, etc. It is necessary to design a custom form for this particular transaction type.

2. Creating links to Custom Transaction types: For any custom transaction, links or menu routes may be created in NetSuite. The developed custom transaction types may then be readily accessed via these links and menu routes.

The many techniques for linking include the following:

Making Plans for Links of Custom Transaction Types: The first thing you should take into account when developing a connection for a custom transaction type is yourCenters. Identifying the Centres connected to the jobs that require access to each transaction type is crucial.

Building Linkages Using Transactions Type Editing: Links may be made by directly altering the custom transaction type. Due to editing limitations, it is occasionally not allowed to alter the transaction type or add links when the transaction is installed via a bundle. In these circumstances, you can use the customization menu to add connections to the transaction type.

Using The Customization Menu To Create Connections: This technique may add connections to your unique transaction type to a custom category.