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.
New AI Community Guidelines. Please review and follow them to ensure AI use stays safe, accurate, and compliant.
Keep an eye out for upcoming NetSuite events, including meetups, workshops, and webinars. These sessions are a great way to connect with peers, learn from experts, and stay current on the latest NetSuite updates and best practices. Registration links are provided in each event.
SuiteWorld | October 25–28, 2026 | Las Vegas Where our community gets ready for what’s next!
SuiteWorld brings thousands of innovators, builders, and leaders together to learn, connect, and shape what’s next. This October, explore how to build a stronger foundation for growth through inspiring keynotes, major product reveals, hands-on sessions, and unforgettable moments—all in one place for our biggest event of the year. Join us
SuiteWorld brings thousands of innovators, builders, and leaders together to learn, connect, and shape what’s next. This October, explore how to build a stronger foundation for growth through inspiring keynotes, major product reveals, hands-on sessions, and unforgettable moments—all in one place for our biggest event of the year. Join us
Make Tax Code Field Not Mandatory in Expense Reports
As documented in SuiteAnswers 31844 || Expense Report Sublist Fields, "The availability of the Tax Amount and Tax Code fields varies depending on the nexus that the Employee is associated with. For example, for an employee associated with a US nexus, these fields are not available. For an employee associated with a UK account, these fields are available."
Unlike US, Tax Code field is mandatory when creating Expense Reports for employees associated with Canada and UK nexuses as these are required under their laws. The ability to hide or remove the Tax Code column on Expense Reports is currently not supported under Legacy Tax. To address this, Enhancement
3