Configuring GL Impact for a Custom Segment
If you've applied a custom segment to transaction types or columns, the segment can have GL impact. When you enable GL Impact, segment values that are saved on transaction instances are displayed on the GL Impact page for those transactions.
If wanted, you can select the GL Impact option even when the segment isn't applied to transaction types or columns. However, until you apply the segment to a transaction type or column, this option has no effect.
Any user who has permission to create a custom segment can enable GL impact for that segment. However, after the segment has been created, this option can't be modified.
For custom segment values, if a period is closed, you can't change custom segment values that impact GL on any transactions in the period.
GL Impact Hidden Lines
Custom segments on GL Impact hidden lines are supported to ensure appropriate financial reporting. The hidden lines get the custom segment values from the item line or transaction body, where applicable. Hidden line support ensures that GL Impact is correctly reflected for landed cost, tax lines, and currency revaluations.
GL Impact and Hidden Custom Segment Fields
If a custom segment with GL impact is set for both the transaction body and transaction line fields, NetSuite automatically uses the body value for the line when the line field is hidden (by clearing the Show option in the Sublist Fields subtab of the form). This keeps financial reporting accurate, even if you can’t set or see the segment at the line level.
However, when the line field is visible, NetSuite doesn’t automatically copy the body value to the line. In this case, you must enter a value in the line field if you want it to be different from, or the same as, the body value—there’s no default carry-over.
This default behavior changes only if a customization, like a Custom GL Lines plug-in or script, overrides it. If the line field is visible, you can enter a different value. This applies only to custom segments with GL impact enabled, ensuring correct reporting on all affected transactions.
Example Scenario
Suppose you have enabled GL impact for a custom segment and use it on Transfer Orders and Item Receipts. When an Item Receipt is created from a Transfer Order, you expect the custom segment value set on the Transfer Order to carry over automatically. If the custom segment’s line field on the Item Receipt form is hidden, NetSuite automatically copies the body value, and the correct segment value will appear. However, if the line field is visible on the form, NetSuite will not auto-populate the value from the body, which may result in the segment value being blank on the Item Receipt lines. In such cases, you must manually enter the value, or edit and save the record to populate it. Consider hiding the line field or using a customization if you want the value to always carry over automatically during record transformations
For details about supported transformations that should be automatically populated, see Supported Transformation Types.
Segment Values Available for Generated COGS and Revenue Lines
When a sale order or sale order item custom segment has GL impact, the appropriate GL segment value is assigned to the generated COGs and revenue GL lines to ensure appropriate financial reporting. The autogenerated COGS and revenue lines get the segment value from the item line or transaction body, where applicable, even if they belong to alternate business transactions.
Automatically-Generated Journals
Custom segments are supported on automatically-generated journals that include classification, department, and location. The following automatically-generated journals include custom segments:
-
Advanced Revenue Recognition Journal
-
Amortization Journal
-
Bill Variances Journal (SCM)
-
Collect Tegata and Pay Tegata
-
Entity Open Balance Journal Entry
-
Intercompany Elimination Journal Entry
-
Offset Journal Entry (Absolute Balance Update)
-
Recognize Gift Certificate (SCIS)
-
Revaluation Journal (FX Revaluation)
-
Revenue Reclassification Journal
-
Revenue Recognition Journal Entry
-
Time Posting to Journal Entry (PSA)
-
Transactions created during historical transaction processing (HTP)
You can apply custom segments to revenue arrangement and revenue element records, which are part of the Advanced Revenue Management (Essentials) feature.
You can set GL impact only when creating a new custom segment. You can't change the GL impact option after saving the segment.
Examples
You enter a standard invoice or cash sale and set or source a GL segment value on the body, line, or both. The autogenerated COGS and revenue lines on the transaction have the same segment value.
You enter a sales order with the GL segment value on the item, and then you fulfill the item. The COGS line on the GL impact page gets the segment value from the item line. When you invoice the sales order later, the revenue line on the GL Impact gets the same segment value. Both COGS and revenue lines source the GL segment value from the sales order item line unless the user manually overwrites the values.
For more information, see GL Impact Page and Cost of Goods Sold (COGS) GL Impact.
To configure GL impact for a custom segment:
-
Go to Customization > Lists, Records, & Fields > Custom Segments > New.
-
Check or clear the GL Impact box as needed.
-
Click Save.
Related Topics
- Custom Segment Creation
- Custom Segment Types
- Creating a Custom Segment
- Filtering for a Custom Segment
- Applying a Custom Segment to Record Types
- Apply to Kit or Assembly Components Setting for Custom Segments and Transaction Line Custom Fields
- Dynamic Default Value Sourcing for Custom Segments
- Validation and Static Default Values for Custom Segments
- User Permissions for a Custom Segment
- Dependent Segments
- Setting Display Order of All Custom Segments