Book Image

NetSuite for Consultants

By : Peter Ries
Book Image

NetSuite for Consultants

By: Peter Ries

Overview of this book

NetSuite For Consultants takes a hands-on approach to help ERP and CRM consultants implement NetSuite quickly and efficiently, as well deepen their understanding of its implementation methodology. During the course of this book, you’ll get a clear picture of what NetSuite is, how it works, and how accounts, support, and updates work within its ecosystem. Understanding what a business needs is a critical first step toward completing any software product implementation, so you'll learn how to write business requirements by learning about the various departments, roles, and processes in the client's organization. Once you've developed a solid understanding of NetSuite and your client, you’ll be able to apply your knowledge to configure accounts and test everything with the users. You’ll also learn how to manage both functional and technical issues that arise post-implementation and handle them like a professional. By the end of this book, you'll have gained the necessary skills and knowledge to implement NetSuite for businesses and get things up and running in the shortest possible time.
Table of Contents (27 chapters)
1
Section 1: The NetSuite Ecosystem, including the Main Modules, Platform, and Related Features
5
Section 2: Understanding the Organization You Will Implement the Solution for
11
Section 3: Implementing an Organization in NetSuite
21
Section 4: Managing Gaps and Integrations
Appendix: My Answers to Self-Assessments

Using Journal Entries

There are many reasons we end up with entries in the GL within an active NetSuite account. Some of those are user-initiated and some are system-generated. For instance, users create GL-posting transactions such as Invoices, Payments, and Journal Entries and in some companies, users will need to create Advanced Intercompany Journals (AIJs) as well. The system auto-generates a variety of journals as well, for things such as Fixed Asset Management and Revenue Recognition. In most cases, we want the accounting team to know about the system-generated journals so that they can anticipate their impact on the business (and tweak them in the rare cases that this is needed). When a client requires a custom solution for things such as journals or the GL impact of other transactions (via SuiteScript), we want to be very careful both when delivering such customization (with ample testing, for instance) and afterward, as we also need someone to actively monitor the customization...