This article is relevant if you seek to ground your knowledge and make better decisions for Recognizing Revenue in NetSuite. This will be the first of a series of articles on Revenue Recognition, and it lays the foundation for navigating revenue complexities to enable strategic decision-making.
TL;DR Summary
Revenue recognition is about timing and valuation, recording income when it is earned rather than when cash is received. Many NetSuite users misunderstand when a true revenue recognition solution is required. The approach should be sized to fit. Many Revenue Recognition needs can be addressed using core NetSuite tools, with Advanced Revenue Management, or ARM, reserved for more complex scenarios.
Introduction
What is “Revenue Recognition”? Why is it important?
Whether you are an accounting professional well-versed in “ASC 606” and “IFRS 15” (The U.S. and international accounting standards for Revenue Recognition) or just a NetSuite user trying to understand what all the fuss is about, a clear understanding of the concepts behind “Rev Rec” rules is crucial to getting your NetSuite environment set up in an optimal manner.
Note, before we address Revenue Recognition, this discussion is backed by years of hands-on experience led by our Firm.
Prolecto’s Prior Accomplishments
Marty Zigman has written extensively about Revenue Recognition in NetSuite over the past decade. Here is a sample of articles and solutions that he has written about on the topic:
See also:
- 2013: How NetSuite Relieves Quickbooks Revenue Recognition Pain
- 2013: Automate NetSuite Cost Amortization via Revenue Recognition
- 2019: Take Control: A Simplified Approach to NetSuite Revenue Recognition and Cost Amortization
- 2023: Simplified Revenue Recognition in NetSuite for Businesses with Recurring Services
- 2025: Cut NetSuite Complexity: Deposits and Payments Instead of ARM and Proprietary Portals
About Prolecto: Our Model for Planning and Execution
Led by our NetSuite Architecture practice, client engagements begin with a business-focused planning phase. This phase starts with client intake and a structured understanding of the business, its operational goals, and impacted accounting requirements. The output is a roadmap that defines the appropriate NetSuite solution and sequencing of work.
Once the roadmap is established, where appropriate, we use Accelerator Templates, which are pre-written code assets, to implement the defined solution efficiently and consistently. These templates provide a structured foundation that can be refined to fit each client’s specific requirements. Learn more about Prolecto’s roadmapping approach as explained by Marty Zigman.
Prolecto Revenue Recognition and Cost Amortization:
As an alternative to NetSuite Advanced Revenue Management (ARM), we effectively generate custom revenue and cost amortization transactions shaped by custom criteria. Tools are created to produce profiles to shape the amortization algorithms. Individual projects and other transactions can have supporting amortization. Bulk tools are offered. Reclass functions for end of period between Unbilled Receivables and Deferred Revenue.
The Prolecto Customer Deposits Generator:
A solution for handling non-parallel Revenue and Billing timing without complicated Revenue Recognition technology. The solution allows the generation of invoices with proper accounting and natural cash receipt operations that automatically become customer deposit records.
Revenue Recognition: It’s All About the Timing
There is a broad spectrum of companies that are subject to Revenue Recognition treatment, ranging from small service companies with one product line to large, multinational corporations with complex project billing that requires a team of revenue accountants to ensure compliance with Revenue Recognition rules.
Yet, regardless of complexity, Revenue Recognition can be distilled to one primary concern: Timing. GAAP has an exact definition of Revenue timing, and it boils down to the point in time at which a company has fulfilled its promise to the customer, thereby entitling it to the cash (or other consideration) that the customer gives it in exchange. In other words, Revenue must be recorded only when the company has truly earned the money it will receive (or has already received).
When I sell you a widget, ship it to you, and send you an invoice, revenue recognition in NetSuite is straightforward. I create an invoice, which records Accounts Receivable as the debit and Revenue as the credit. The timing of the fulfillment of my promise (shipment of the widget) coincides with my right to collect the consideration from you. In this situation, the invoice satisfies both the accrual of the asset (Receivable) and the recognition of revenue.
However, if billing occurs at a different time than the promise fulfillment, we need to decouple the Asset impacts (Accounts Receivable or Cash) from the Income impacts (Revenue). This is when we are in a potential Revenue Recognition concern.
I will come back to this simplified scenario in more detail below, but first, one more concept about Revenue Recognition is needed:
Rev Rec: Also About Valuation
Admittedly, the above description of Revenue Recognition pertaining to “Timing” is oversimplified. Revenue Recognition is also about valuation: How much should I record as Revenue? The accounting rules have a lot to say on this topic. Consider a situation where the widget I sell you also includes membership to an exclusive widget club. I may market the membership as a “free” perk with the widget, but the accountants see it differently. GAAP requires me to spread part of the widget price over the membership lifetime, allocating a portion of the sale amount away from the widget and toward the subscription.
Still, at its core, the concern relates to timing. After all, if the membership starts and ends in the same period as the widget shipment, the relative values of each part of the sale are somewhat moot. I recognize the full value of the entire deal in the same period. It is only because the timing of my fulfillments varies that I also need to figure out how much I can record as revenue in each period.
Once we understand that the issue of Revenue Recognition relates to the timing and the definition of “earned” revenue, we can start to synthesize each business event in light of Revenue Recognition concepts and then plan how these concepts can best be expressed in NetSuite.
Revenue Recognition Is Not One-Size-Fits All!
If there’s one takeaway from this article that I hope to provide, it is this: You have options. While NetSuite’s native Advanced Revenue Management (ARM) module is powerful for the correct type of business situations, in many cases, it is overkill or worse.
(My next planned article will go deeper into ARM and highlight where it is the right solution, and will describe some of its strengths and cautionary areas.)
NetSuite’s highly customizable record structure and transaction types provide great flexibility for crafting the right process flows and automating transactions.
It takes careful consideration and knowledge of the nuances of NetSuite’s transaction architecture to provide the best fit for Recognizing Revenue. Knowledge is power, and having a NetSuite Ninja in your corner can help you make the right decisions.
Revenue Recognition Levels of Complexity
Customers requiring Revenue Recognition solutions often fall into different levels of complexity. The degree of complexity should naturally determine the appropriate solution. A frequent error is assuming a complex solution is necessary. To guide decision-making, we outline four typical scenarios below:
Scenario One: Invoice in Advance of Shipment
This is the most common scenario we encounter. The customer needs to be billed in advance of shipment (in part, in full, or in installments), and Revenue is deemed earned only when a product is shipped or a service is performed (recall the “fulfillment of a promise” concept outlined above).
The natural instinct of novice NetSuite users in this advance-billing scenario is to assume that a Revenue Recognition solution is needed to record the initial invoices to Deferred Revenue, and then to record revenue via journal entries upon fulfillment. Indeed, this is what the Advanced Revenue Management module would do.
Revenue Recognition vs. Customer Deposit Accounting
A better strategy in the above situation is to utilize Customer Deposit accounting. This method records a liability when an advance payment is received. Revenue recognition then naturally occurs upon shipment through the standard invoicing process against the sales order.
We have created a widely used solution, called The Prolecto Customer Deposits Generator, that generates an advance invoice, which seamlessly initiates the appropriate customer deposit accounting. This approach meets the need to record Accounts Receivable at the correct time while ensuring that the revenue is recognized in a manner consistent with product delivery. See the diagram below for a simplified overview, and see the article Cut NetSuite Complexity: Deposits and Payments Instead of ARM and Proprietary Portals, which includes cross-references to many others on the topic.
Scenario Two: Even-Period Service Dates
Another common scenario is when a service is performed over time, requiring revenue to be recognized ratably over a service period.
Here too, one should not rush to assume that a complex solution is needed. If the service dates are known at the time of creation of a Sales Order (or Quote), and revenue needs to be recognized with a straight-line method over the period between the start and end dates, it is relatively straightforward to create automated transactions to recognize the correct proportion of revenue each month.
We have created a solution designed for revenue recognition driven by service dates called “Prolecto Revenue Recognition and Cost Amortization” as part of our accelerator templates, and as with all of our solutions, it is intended to be refined to fit each client’s particular needs. I intend to discuss this in more detail in a forthcoming article. See the diagram below for a visualization.
Scenario Three: Subscription Billing with Fluctuating Revenue
A third scenario often encountered is businesses with a subscription billing model, where subscription revenue may be subject to changes midway through the contract lifecycle or may fluctuate based on service usage. Typically, in addition to a Revenue Recognition solution, a Billing solution is needed, such as NetSuite SuiteBilling or Zone & Co.’s Zone Advance Billing SuiteApp. The complexities of Subscription Billing often require robust Revenue solutions tightly integrated with the Subscription system. While the NetSuite platform is certainly flexible enough to build custom solutions to fit these more advanced revenue scenarios, most companies in these scenarios would opt for either NetSuite’s Advanced Revenue Management (ARM) or other 3rd party solutions. I will discuss this in more detail in a forthcoming article dedicated to ARM.
Scenario Four: Multi-Component Revenue with Fair Value Allocation
Another scenario that can involve significant complexity is a scenario where the amount of revenue to be recognized requires complex fair value calculations and allocations across tangible and intangible products/services. Consider a situation where a business sells bundled hardware, software, and post-sale services under a single contract. According to the accounting standards as codified under ASC606, the company needs to identify when each component of the sale is earned (known as the “performance obligations” in the accounting rulings), and it needs to allocate revenue to the components based on the relative fair values of each component if it were sold on its own, known as the “stand-alone selling price”.
Companies subject to this level of complexity are served best when the NetSuite implementation team and the internal or external revenue accountants have alignment and are knowledgeable about the standards and record modeling that is needed to get NetSuite to perform the calculations correctly and record revenue correctly.
This scenario is one that ARM is especially built for, and I plan to discuss this in greater detail in a forthcoming article.
As with all NetSuite solutioning, be sure that the business requirements are clearly defined and that the requirements are leading the software configuration design.
Getting it Right: Understanding Your Business Should Drive the NetSuite Solution
Given that the cornerstone of Rev Rec relates to the timing of fulfillment, decisions about how to go about revenue recognition in NetSuite need to be informed first and foremost by a core understanding of the timing factors and the economic definitions of the events that impact revenue.
The optimal Revenue Recognition solution requires a thorough planning exercise, prioritizing business requirements to design the supporting software and related practices. Because Revenue Recognition solutions can be demanding to set up and troublesome to undo, they should not be implemented without first addressing the following key planning topics:
- Understand the Fundamentals: What are the business events that drive Billing, Collection, Fulfillment, and Revenue? ASC 606 provides a 5-step model for assessing Rev Rec, and companies should build on that analysis to carefully consider the timing and economic meaning of each stage of their transaction cycle.
- Understand the relevant NetSuite transaction types: Carefully think through which transaction types and record types in NetSuite would best capture the economic meaning of the events that occur in the billing and revenue cycle.
- Know the end game: Consider the company’s reporting needs and the required granularity for revenue reporting.
- Conceptualize, Design, Prototype, and Test: Create a vision and process design that combines NetSuite expertise and authoritative accounting knowledge. Model the transaction flow and GL impacts, and prototype the solution before adding automation. Does it pass the standards, and will it stand up to auditor scrutiny? Thorough review with business stakeholders and accounting management at this stage mitigates the risk of rework and enables alignment on accounting policy.
As the adage goes, “measure twice, cut once”. Solid planning, using a framework such as the one above, makes for a successful implementation.
Revenue Recognition Guided by Accounting Discipline and NetSuite Architecture
I am blessed to work with high-caliber professionals with strong accounting pedigrees. It takes a combination of NetSuite expertise and authoritative Accounting knowledge to get to the heart of Revenue Recognition challenges, and alongside Marty Zigman, we have built a hand-picked team of professionals who possess the qualities needed to help our clients navigate these complex issues.
If this article resonates, consider subscribing to receive notifications for new posts. If you would like to get expert help in NetSuite Revenue Recognition best practices, let’s have a conversation.
