Discussions

Stay up-to-date with the latest news from NetSuite. You’ll be in the know about how to connect with peers and take your business to new heights at our virtual, in-person, on demand events, and much more.
Now is the time to ask your NetSuite-savvy friends and colleagues to join the NetSuite Support Community! Refer now! Click here to watch and learn more!
Update your Profile with your Support type to get your Support Type badge.
Don't miss out on our Pop Quiz You only have until November 7, 2025, 2:00PM ET to comment your answers and earn rewards! Click here for more details.
Uncover the power of data with the Analytics Hub —your ultimate guide to mastering NetSuite Saved Searches and Reports. Simplify the complex and unlock your organization's true potential. Dive into the Analytics Hub now and soar to new heights!
To help you get the most out of your 2025.2 Release Preview account, review the topics outlined in the 2025.2 Release Preview Guide.
Nominate Your Peers for NetSuite Support Community's Choice of the Quarter! Submit your nomination today.
Intelligent Payment Automation version 1.0.3 is now available in the SuiteApp Marketplace. The SuiteApp, powered by BILL, lets you automate payments, manage vendor details, and bank account information within NetSuite. Learn more

Assembly Build posting to COGS?

edited Feb 17, 2010 4:36PM in Accounting / ERP 2 comments

I am seeing a curious G/L impact on one of our assembly build transactions.

In addition to debiting the parent asset account and crediting the components' asset accounts, the assembly build transaction also debited COGS and credited the parent asset account for the amount of the build.

I.e. the following transactions occurred:

DR Parent Inventory Asset Account
   CR Component Inventory Asset Account(s)
DR COGS
   CR Parent Inventory Asset Account

This only happened on one instance of an assembly build (other assembly builds did not have the COGS transaction).

Is there a reason why this might have happened? Was it the way the assembly build itself was transacted, or was it due to the way the parent assembly part was set up? How do I prevent it from happening again?

Howdy, Stranger!

Log In

To view full details, sign in.

Register

Don't have an account? Click here to get started!

Leaderboard

Community Whiz

Quarter 4 (Oct-Dec 2025)

This Week's Leaders

This Month's Leaders

All Time Leaders