We created a custom segment and want to generate the Income Statement report by this custom segment. An issue was observed specifically for COGS accounts. Upon checking, the sales transactions (e.g. Cash Sales, Cash Refunds) DO have a custom segment assigned - both at the header and item line. The GL impact also has the custom segment on all lines. However, in the IS report, the COGS account amount shows as "Unassigned" while the Sales account amount shows up under the correct Custom Segment column.

AI generated answer (using internal Slack threads):

Based on the conversations, it seems like the issue you're experiencing with the Income Statement report and the custom segment might be due to how NetSuite handles custom segments. In NetSuite, custom segments are typically assigned at the header level of a transaction. However, in some cases, they may need to be assigned at the line level to properly reflect in reports. This could be the reason why the COGS account amount is showing as "Unassigned" in the IS report, even though the custom segment is assigned at the header and item line of the sales transactions. One of the users suggested a workaround for this issue. They recommended creating a workflow that copies the custom segment from the header to the line. This might ensure that the custom segment is properly reflected in the IS report for all lines, including the COGS accounts. However, it's important to note that this is a workaround and might not work in all cases. It's also worth mentioning that there might be a delay in the reporting subsystem, which could cause some transactions to show as 'unassigned' initially. Here are the relevant SuiteAnswers articles that might help you further: 1. [Custom Segments](https://suiteanswers.custhelp.com/app/answers/detail/a_id/93634/loc/en_US) 2. [Custom Segments on Financial Reports](https://suiteanswers.custhelp.com/app/answers/detail/a_id/94149/loc/en_US) ****** Disclaimer: This response was generated by an artificial intelligence assistant based on previous conversations from multiple Slack channels, and may contain inaccuracies or mistakes. ******