Discussions
Join us for complimentary one-day events around the world and step into a future fueled by AI and limitless potential. Explore new breakthroughs, sharpen your skills, and connect with experts who are shaping what’s next. Experience bold keynotes, interactive learning, and connections that span the global NetSuite community. Discover what's next at SuiteConnect Tour 2026.
We’re excited to announce that the 2025 Community Recap is now available! This special recap highlights the amazing contributions and achievements of our members over the year and celebrates the collective success of our community.
Check your personalized recap to see the impact you made in 2025 and how your efforts helped shape our community’s growth and success.
View Your 2025 Community Recap
Thank you to everyone for your passion, collaboration, and support. Here’s to building an even stronger community together in the year ahead!
Season’s greetings to you and yours! As we head into the holidays (December 24 – January 4), we want to take a moment to celebrate the incredible strength and collaboration within our community. Even during the break, you can continue to benefit from connecting with peers, searching related threads, posting your questions, and marking helpful replies as “Accepted” in the Support Community.
Please note our dedicated team will be on reduced coverage during this time, and regular responsiveness will resume on January 5. Wishing you a joyful and restful holiday season!
-The NetSuite Support Community Team
Fulfilment posting to GL on created date, not shipped stage date
Hi,
We are still doing some testing, but we have come across an issue where if you use the '3 stage - pick/pack/ship' fulfilment process instead of the single fulfill step - the G/L impact can get backdated into a closed period.
The example for our business is that we do some customizing of a product and attach some labour, but don't use assembly builds for it, what we had done was fulfill the order to Picked stage - go do the QA/Upfit work on it - then return it to the despatch area and mark is as Packed. When it is physically shipped, it is marked as shipped, and that is when the G/L should be posted (that date/that period). The problem appears to be that the inventory is debited correctly (on the shipping stage), but the G/L COGS hit occurs