This article is the third in our Revenue Recognition series, geared toward Controllers, CFOs, and Revenue Accountants. The first article, NetSuite Revenue Recognition Fundamentals: A Clear Framework for Getting it Right, laid out a framework for sizing Rev Rec solutions to fit business reality. The second, Making Sense of NetSuite ARM: A Straightforward Look at the Fundamentals, examined Advanced Revenue Management and the situations for which it is well-suited. In this article, I describe a different approach: one we use for businesses whose Rev Rec complexity does not warrant the parallel record infrastructure that ARM introduces.
TL;DR Summary
A significant number of businesses subject to ASC 606 have revenue recognition logic that can be easily driven by transaction fields or existing data in the NetSuite environment. For these businesses, a nimble, profile-driven approach that operates directly on the source transaction can deliver compliant revenue and cost recognition without standing up a cumbersome parallel record structure. The Prolecto Revenue Recognition approach is a welcome solution for clients for whom ARM is more advanced than they need.
Background: A Decade of Take-Control Thinking
In 2019, Marty Zigman authored Take Control: A Simplified Approach to NetSuite Revenue Recognition and Cost Amortization, introducing a Prolecto-built approach to revenue recognition that worked from source business events, such as project percent-complete and actual revenue recognized to date. The original solution, engineered by Sean G. in our Accounting Practice, served a project-based services client. It used a custom NetSuite transaction type, configurable profiles, and a reclass tool to produce both revenue recognition and matched cost amortization in one consistent flow.
In 2023, Marty wrote about Simplified Revenue Recognition in NetSuite for Businesses with Recurring Services for a recurring-services business, where invoice-line service dates were the only data needed to push revenue into the period in which it was earned. Recently, we built upon the existing patterns to create a new configuration for a project-based contracting business that needed both revenue recognition tied to invoice activity and nightly cost accrual that self-corrects against actual vendor bills as they post. The architecture there is lighter than the original engine, suited to the simpler revenue trigger of service-date-on-invoice rather than a multi-step acceptance milestone.
Prolecto Revenue Recognition has continued to mature across all of these engagements. The driving philosophy has not changed: use the data the business already has, and produce auditable accounting entries that hold up to scrutiny.
See also:
- 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
- 2026: NetSuite Revenue Recognition Fundamentals: A Clear Framework for Getting it Right
- 2026: Making Sense of NetSuite ARM: A Straightforward Look at the Fundamentals
Prolecto Revenue Recognition Demonstrates Our Model
Readers of this blog are likely already well-familiar with our 75+ “Accelerator Templates“, which represent what two decades of strategic and business-first solutioning can produce. What might be less obvious is what I see as our real value: The critical thinking, planning, and speaking our clients’ language to produce results that are tailored and adaptable to any client situation. We offer our accelerator bundles to all our clients at no recurring cost, because we don’t view them as static “products”. By design, they are meant to be adapted to meet whatever unique situation our clients are in. We leverage the patterns and frameworks in our accelerators where it makes sense, but more importantly, we leverage the mental models, concepts, and sound accounting practices to create a system that matches the requirements. This approach is all the more powerful in our nascent AI era (more on this in the concluding paragraph).
Prolecto’s accomplishments and evolution in the domain of revenue recognition and cost accrual demonstrate this type of leadership. In the most recent Revenue Recognition project, we initially assumed we would implement our existing Prolecto Revenue Recognition accelerator. Yet, after working with the client to sharpen the requirements, it became clear that a different, simpler approach was warranted. We followed the same principles that guided our prior revenue recognition work and produced a new variation that expands our ability to serve the Rev Rec market. Although the remainder of this article will focus more on the capacities of the more robust version of the solution, the core concepts that successfully bridge the gap between ASC606 and NetSuite underlie the more recent lightweight version as well. Bottom line, we carefully listen to client requirements and offer the right fit, leveraging wisdom and patterns to produce elegant solutions.
What Makes Prolecto Revenue Recognition Adaptable in NetSuite
A few design choices give the Prolecto approach to Revenue Recognition its adaptability:
- Profile-driven configuration. The rules that define what counts as revenue for each record type, what saved search returns total contract value, how percent complete is computed, and what status new transactions take are all stored in a profile record. New business models do not require new code; they require a new profile and the saved searches and percent-complete logic to support it.
- A flexible “percent earned” calculation. Different businesses measure “how much of the contract is earned” in different ways. A project services firm may use the project manager’s percent-complete assessment. A hardware business may use a customer acceptance milestone. A recurring services business may use elapsed time within a service period. The engine treats this measurement as a swap-in component, so the same code path can be configured to read whichever source fits the business at hand.
- Parameterized accounts. The balance sheet accounts used for deferred revenue, unbilled receivables, accrued expense, prepaid expense, and Work-in-Process are configured per deployment. A single engine can serve multiple subsidiaries with distinct chart-of-accounts choices.
- Configurable rules through saved searches. The boundary conditions — which transactions qualify, which periods are in scope, and which contracts are considered active — are expressed in saved searches that controllers can review and adjust.
- Transaction Line-Level Field Logic. Column fields support time-driven recognition, making it easy for a user to manage when revenue should start being recognized and for how many periods.
How is Prolecto Revenue Recognition Different from ARM?
Both NetSuite’s Advanced Revenue Management and the Prolecto solution set can produce ASC 606-compliant outcomes. They take fundamentally different postures, however. ARM is built around the premise that Revenue lives on its own parallel record structure, with Arrangements, Elements, and Plans that are intentionally decoupled from the billing transactions. That posture is the right call for businesses whose Revenue narrative diverges meaningfully from their Billing narrative, particularly those needing fair-value allocation or contract merging.
The solutions that Prolecto has built take the opposite posture: revenue and cost recognition are read directly from the source transaction line. That difference opens capabilities that are useful in real-world scenarios.
Neither posture is necessarily “better”. Companies need to ask “which approach is right for us?” and should consider the distinctions and which model fits best. As I wrote in my first article in this series, NetSuite Revenue Recognition Fundamentals: A Clear Framework for Getting it Right, know that you have options!
(It bears repeating here that a completely different way of looking at revenue recognition is by modeling billing and revenue in a “customer deposit” (i.e. prepayment) framework. This has been described in several previous articles. See below for a sample, which has further cross references: Cut NetSuite Complexity: Deposits and Payments Instead of ARM and Proprietary Portals)
1. Real-world Flexibility: Items Subject to Rev Rec Alongside Items That Are Not
Consider an invoice that includes both a recurring service fee that must be deferred and recognized over the service period, and a one-time setup charge that is fully earned at the time of invoicing. Or a project final invoice that bundles completed work (earned now) with a maintenance component that extends into future periods (earned over time). Or a hardware sale that ships a product and a multi-year support contract on the same order.
In ARM, mixed scenarios like these require careful item setup and revenue rule configuration to post the right revenue amounts in the right periods, but assuming that the different item types need to be on the same transaction, both need to be routed through Rev Rec via Arrangements, Elements, Plans, and ultimately, Journal Entries.
The approach taken in the Prolecto Revenue Recognition solution handles the same scenarios at the line level through targeted account-by-account matching. A simple mapping defines which income accounts are subject to deferral. When a transaction posts, only the lines whose accounts are mapped get redirected to deferred revenue. All other lines post normally. Lines that need deferral are deferred, and lines that do not need deferral are left alone to post naturally.
2. Matching Principle: Cost Amortization in Tandem with Revenue Recognition, Using Actual Costs
The accounting matching principle holds that costs should be recognized in the same period as the revenue they support. In a project-based business where subcontractor bills arrive weeks or months after the related work is invoiced, the cost side of the equation often lags the revenue side. The result is an inflated margin in the period of invoicing and a deflated margin in the period when costs catch up.
The Prolecto Revenue Recognition approach treats Cost Amortization just as it treats Revenue Recognition. A profile is created to store the parameters needed to calculate the relevant period cost to recognize cost, and a parallel configuration to Revenue can ensure that the matching principle is kept consistent.
3. Avoid Generic Journal Entries: Custom Transaction Types for Revenue and Cost Recognition
Whenever possible, we advocate using specific, meaningful transaction types that convey the nature of the activity being recorded, rather than reaching for journal entries — see Avoid the Temptation to use Journal Entries. Therefore, we leverage a custom transaction type that is specific to Revenue Recognition, and that is shaped with permissions, approval statuses, and custom fields that provide clarity and show intentionality when recognizing revenue and costs.
Additional Highlight: Forecast-and-Review Staging Before Posting
One of the most useful features for controllers and revenue accountants is built into the data model itself. Each system-generated revenue or cost transaction carries a status. These can be configured or modified according to each client’s needs. Sublists on the source transactions provide a full picture of planned and posted revenue:
- Forecast, for future-period transactions that show what revenue or cost will be recognized if the current trajectory holds. These are non-posting. They sit in the system for reporting and forecasting visibility, but never touch the GL.
- Earned, Unapproved, for the current period’s calculated revenue or cost. These are visible to controllers for review but do not impact financials until approved.
- Earned, Approved, for transactions that controllers have signed off on.
The engine recalculates every transaction every time it runs. If a contract value or schedule changes mid-period, forecasts update. If percent-complete moves between runs, the unapproved current-period transaction updates with it. Stale forecast records that no longer apply are automatically cleaned up. Controllers can run the engine as often as they like during the month without creating duplicates or having to manually clean up.
When Prolecto Revenue Recognition Is the Right Fit, and When It Is Not
Prolecto Revenue Recognition fits businesses whose ASC 606 situation can be summarized as: revenue is earned over identifiable service periods or by project completion, and cost needs to be matched to revenue using data the business already captures. That covers many service businesses, contracting businesses, recurring-services businesses, and project-based organizations.
It is less suited to the more complex revenue scenarios that NetSuite’s Advanced Revenue Management is built to address. As I described in the Making Sense of NetSuite ARM: A Straightforward Look at the Fundamentals, situations requiring fair-value allocation across bundled items, contract merging across multiple sales orders, or sophisticated performance-obligation modeling are situations where the parallel record structure that ARM provides earns its complexity.
The decision between the two postures comes down to which fits the business, rather than which is better in the abstract.
Closing Thoughts
As Marty wrote in his recent article, NetSuite, AI, and the Discipline of Building Serious Business Systems, a solid data architecture that aligns planning, operations, and accounting is an enduring quality, even as AI radically changes how we think about user experience, automation, and cost-effectiveness. Prolecto’s approach to Revenue Recognition is a working example of that principle in practice: a transaction structure fitted to a company’s needs while staying faithful to accounting fundamentals.
For a meaningful share of businesses, the data needed to comply with ASC 606 is already on the transactions they create in the ordinary course of business. A nimble, configurable approach that reads that data and produces auditable period-end entries, with a forecast-and-review staging step before anything posts, can deliver compliant revenue recognition and matched cost amortization with substantially less infrastructure than a parallel-record approach requires.
If your organization is navigating a Rev Rec decision and would benefit from an assessment of where on the spectrum your needs fall, let’s have a conversation.
