10 Revenue Recognition Experts, Firms, and ASC 606 Resources I'd Use
Updated August 2026 · By Devon Coombs, CPA, MBA
ASC 606 is no longer a new accounting standard. That does not mean the hard revenue questions have gone away.
If anything, evolving business models have created a different set of problems: consumption and usage pricing, complex partnerships, marketplaces, reseller arrangements, bundled software and services, customer incentives, contract modifications, noncash consideration, new monetization models, and increasingly automated revenue processes.
Those questions often require more than knowing the five-step model. They require understanding the authoritative literature, how similar arrangements are treated in practice, what an auditor is likely to challenge, and how the accounting interacts with the underlying commercial structure.
I work in this area, so I regularly use, read, work with, or encounter the people, firms, and technical resources below. I have not tried to rank a former SEC Chief Accountant against a consulting firm or a free technical library. Instead, I have identified where I think each is particularly useful.
Where I have a commercial relationship with someone listed, I disclose it.
Quick Comparison
| Expert or resource | Best fit |
|---|---|
| Devon Coombs | Complex technology revenue, commercial deal structures, embedded revenue leadership, and AI-assisted revenue workflows |
| Scott A. Taub | Difficult interpretive questions requiring deep SEC and standard-setting perspective |
| Tony Sondhi | Revenue recognition and financial reporting questions involving software and technology |
| Angela Fergason / PwC | Big Four interpretive guidance, technology revenue, and complex ASC 606 judgments |
| RSM Revenue Recognition Guide | Practical, comprehensive ASC 606 guidance for middle-market and private companies |
| Connor Group | Hands-on technical accounting support for high-growth and transaction-oriented companies |
| CFGI | Revenue accounting combined with systems, process, IPO, M&A, or finance transformation work |
| Renee Rampulla | Structured ASC 606 education and CPE |
| RevenueHub | Free, searchable explanations of specific ASC 606 topics |
| KPMG Revenue Recognition Handbooks | Deep technical research, particularly for software and SaaS |
Devon Coombs
CPA, MBA · Teaching Professor of Finance, Santa Clara University
Best fit: Complex technology revenue, commercial transactions, and building the revenue function around them
My niche is not explaining the five-step model from scratch. It is helping when the facts become difficult.
I spent part of my career in Big Four consulting and later worked on complex commercial transactions inside Google Cloud. My practice today includes technical revenue accounting, contract and deal review, monetization structures, accounting position papers, audit support, and embedded leadership of revenue organizations.
The work tends to sit where accounting and the business collide: software and cloud arrangements, usage-based models, strategic partnerships, bundled offerings, reseller structures, incentives, contract modifications, M&A, and new products that do not fit neatly into an old accounting policy.
I also work with revenue teams on AI-assisted contract review, accounting research, documentation, controls, and other workflows. I think AI can materially improve how technical accounting teams operate, but it does not remove the need for experienced judgment or review.
I would use my practice when: the issue involves a real transaction or operating revenue organization and you need the accounting answer to work with the commercial structure, systems, audit process, and people actually responsible for executing it.
I would use someone else when: the primary need is a formal training curriculum, a large systems implementation, or consultation that specifically requires the company's independent auditor or another firm's national office.
How I workScott A. Taub
Managing Director, Financial Reporting Advisors, LLC · Former SEC Acting Chief Accountant
Best fit: Difficult technical positions where SEC reporting history and authoritative interpretation matter
Scott Taub is one of the first people I would think of for an unusually difficult financial reporting question.
He previously served as Deputy Chief Accountant and Acting Chief Accountant of the SEC and later participated in the FASB/IASB Joint Transition Resource Group for Revenue Recognition. He is also the author of Wolters Kluwer's extensive Revenue Recognition Guide.
That background is unusually relevant to ASC 606. He brings the perspective of someone who has been involved not simply in applying accounting literature, but in regulatory interpretation and the standard-setting ecosystem around it.
I would use Scott when: the issue is highly judgmental, potentially material, unusual, or likely to receive significant auditor, audit committee, or SEC scrutiny.
I would use a different model when: the problem is less about reaching a difficult accounting conclusion and more about executing hundreds of contracts, operating a revenue team, or implementing systems and processes.
Ashwinpaul C. "Tony" Sondhi
Founder, A.C. Sondhi & Associates
Best fit: Revenue recognition and financial reporting issues involving software and technology
Tony Sondhi has worked around revenue recognition and financial reporting standards for decades.
He has served on the FASB Emerging Issues Task Force, co-authored prior editions of the CCH Revenue Recognition Guide, and advised companies and professional organizations on U.S. GAAP and international accounting issues.
His work has included a particular emphasis on revenue reporting and technology companies, which makes his background relevant to software arrangements where licensing, services, support, implementation, and evolving delivery models create difficult questions.
I would use Tony when: the issue requires deep historical knowledge of revenue accounting and standard setting, particularly in software or technology.
I would use someone else when: the primary need is a large embedded delivery team, systems implementation, or outsourced revenue operation.
Angela Fergason · PwC
Partner and Standard Setting Leader, PwC National Office
Best fit: Big Four interpretive guidance on complex revenue issues, particularly in technology
Angela Fergason is a PwC National Office partner specializing in revenue and compensation accounting and broader financial reporting issues affecting technology companies.
She has been one of the practitioners behind PwC's public ASC 606 education, including its detailed Revenue Toolkit discussions of the five-step model.
PwC's broader revenue guide is also one of the references I would keep available when researching a difficult question because it combines the underlying accounting requirements with interpretive guidance and examples.
I would use PwC when: the company needs deep Big Four technical resources, the issue is material or highly judgmental, or PwC's particular interpretive position matters to the engagement.
I would use a more specialized provider when: the company needs flexible embedded support or a small team working directly inside day-to-day revenue operations.
PwC Revenue ToolkitRSM · A Guide to Revenue Recognition
Technical accounting resource and advisory firm
Best fit: Practical end-to-end ASC 606 guidance, particularly for middle-market companies
RSM publishes one of the more usable comprehensive ASC 606 guides.
Its A Guide to Revenue Recognition walks through the scope of Topic 606, the five-step model, presentation and disclosure, contract costs under ASC 340-40, derecognition of nonfinancial assets under ASC 610-20, and common implementation questions.
The guide was updated in May 2026 for issues encountered in practice and forthcoming changes to relevant guidance.
I particularly like resources like this for questions where you need more depth than a summary article but do not yet need to commission a separate technical consultation.
I would use RSM's guide when: a controller, accounting manager, auditor, or technical accountant needs a practical ASC 606 reference that can be read without beginning with several hundred pages of raw Codification.
I would escalate beyond the guide when: the issue is highly fact-specific, material, or involves competing interpretations that need to be documented and defended.
Read RSM's GuideConnor Group
Specialized finance and accounting advisory firm
Best fit: High-growth technology companies that need people who can both research the accounting and execute it
Connor Group has built a significant practice around technical accounting, IPO readiness, M&A, financial operations, and related finance work.
Revenue recognition fits naturally into that model because difficult revenue problems rarely stop with a memo. Companies may also need contract reviews, accounting policies, audit support, system requirements, processes, controls, and people who can operate the function while the business scales.
Connor Group's involvement with RevenueHub, discussed below, also reflects a longstanding investment in ASC 606 education and technical accounting.
I would use Connor Group when: a growth company needs substantial hands-on technical accounting support, particularly around an IPO, acquisition, scaling finance organization, or other major transaction.
I would use an individual specialist when: the problem is one narrow technical question and the company does not need a broader delivery team.
Visit Connor GroupCFGI
Accounting advisory firm
Best fit: Revenue recognition connected to finance transformation, transactions, processes, or systems
CFGI approaches revenue recognition as part of a broader accounting and finance infrastructure problem.
That is often the right framing.
ASC 606 conclusions ultimately have to flow through contracts, billing, revenue systems, the general ledger, disclosures, internal controls, forecasts, and audit evidence. A technically correct memo does not solve much if the organization cannot operationalize the conclusion.
CFGI's revenue work has included technical assessments as well as revenue automation, data, systems, and transformation considerations.
I would use CFGI when: the revenue problem is part of a broader IPO, M&A, private-equity, systems, or finance-transformation project.
I would use someone else when: the problem is an isolated interpretive question and the company does not need a broader project team.
Visit CFGIRenee Rampulla
Founder, Rampulla Advisory Services, LLC · CPA, CGMA
Best fit: Structured ASC 606 education and continuing professional education
There is a difference between hiring someone to solve a revenue issue and teaching an accounting organization to solve the next one itself.
Renee Rampulla is particularly relevant to the second problem.
She has more than 30 years of accounting and auditing experience and teaches revenue-recognition programs through AICPA & CIMA, including courses on interpreting and applying ASC 606.
Her broader background in standard setting, auditing, and professional ethics also makes the education more useful than a simple walkthrough of the five steps.
I would use Renee when: the objective is structured technical training or CPE for accounting professionals.
I would use a transactional consultant when: the team needs someone to analyze specific contracts, draft accounting positions, negotiate audit conclusions, or operate the revenue function.
RevenueHub
Free technical resource · Collaboration between the BYU School of Accountancy and Connor Group
Best fit: Fast, free research on specific ASC 606 questions
RevenueHub is one of the first free resources I would give a staff accountant learning ASC 606.
The site grew out of a collaboration between Brigham Young University's School of Accountancy and Connor Group. Its articles break revenue recognition into specific issues organized around the ASC 606 model and industry fact patterns.
That makes it particularly useful when someone does not need a 500-page handbook. They need to understand one issue, such as contract modifications, principal-versus-agent considerations, variable consideration, warranties, licenses, or a specific industry application.
I would not treat a RevenueHub article as authoritative accounting literature. I would use it to understand the issue quickly, identify the relevant guidance, and then confirm the conclusion against the Codification and other appropriate interpretive sources.
I would use RevenueHub when: someone needs an accessible starting point for a particular revenue-recognition topic.
I would not stop there when: the conclusion is material, unusual, subject to significant judgment, or headed into an accounting memorandum or audit review.
Visit RevenueHubKPMG Revenue Recognition Handbooks
Technical accounting reference
Best fit: Deep ASC 606 research, especially for software and SaaS
KPMG publishes both a general revenue-recognition handbook and a separate handbook devoted specifically to software and SaaS.
These are among the resources I would use when a question moves beyond the basic five-step model and into detailed interpretive issues.
The software and SaaS handbook is particularly useful because ASC 606 remains highly judgmental for arrangements involving software licenses, SaaS, implementation, support, modifications, variable pricing, and multiple promises.
KPMG updated both publications in December 2025, including new interpretations and examples reflecting recent standard-setting developments.
I would use KPMG's handbooks when: I need detailed interpretive guidance, examples, and industry-specific analysis before forming an accounting position.
I would still go back to the Codification when: documenting the final conclusion. Big Four guides are valuable interpretive resources, but they are not authoritative U.S. GAAP.
How I Would Choose a Revenue Recognition Expert
Start with the problem.
If the question is "What does ASC 606 actually require in this unusual transaction?", I would favor deep technical expertise and strong interpretive credentials.
If it is "We have a new software, AI, cloud, marketplace, reseller, or usage-based offering and need to figure out the accounting before launch," I would favor someone who understands both revenue accounting and commercial deal structures.
If it is "Our auditors disagree with our position," I would bring in someone with enough technical depth to work through the literature, facts, precedent, and alternative views rather than simply producing another memo.
If it is "We need to analyze thousands of contracts, build policies, establish controls, and operationalize ASC 606," I would use a firm or embedded team with enough capacity to execute.
If it is "Our accounting team needs to learn ASC 606," I would use a structured education provider rather than paying consulting rates to walk through basic guidance.
And if it is "I need to understand this issue before I decide whether it is actually difficult," I would start with RevenueHub and the major accounting-firm guides.
What Makes Revenue Recognition Difficult?
The five-step model is straightforward to state. Applying it to an actual contract is often not.
The difficult questions tend to arise around a handful of recurring areas:
- identifying all promised goods and services in an arrangement;
- determining whether promises are distinct;
- estimating variable consideration and applying the constraint;
- determining standalone selling prices;
- evaluating options, discounts, credits, rebates, and other customer incentives;
- distinguishing licenses from hosted services;
- accounting for usage-based and consumption pricing;
- determining whether an entity is a principal or an agent;
- evaluating consideration payable to a customer;
- accounting for contract modifications;
- determining whether revenue transfers at a point in time or over time;
- evaluating material rights;
- accounting for contract acquisition and fulfillment costs;
- analyzing reseller, marketplace, and strategic partnership arrangements; and
- translating technical conclusions into systems, processes, controls, and disclosures.
The accounting becomes harder when several of these issues occur in the same commercial arrangement.
That is increasingly common in technology.
ASC 606 and Revenue Recognition FAQ
What are the five steps of ASC 606?
ASC 606's revenue model consists of five steps:
- Identify the contract with a customer.
- Identify the performance obligations in the contract.
- Determine the transaction price.
- Allocate the transaction price to the performance obligations.
- Recognize revenue when, or as, each performance obligation is satisfied.
The difficult work is generally not remembering those steps. It is applying them to ambiguous facts and documenting the judgments required by the model.
When does a company need a revenue recognition expert?
I would consider outside technical accounting support when a transaction is unusual, financially significant, likely to receive substantial audit scrutiny, or outside the experience of the internal accounting team.
Common triggers include:
- launching a new product or monetization model;
- software or SaaS arrangements with multiple promises;
- usage or consumption pricing;
- strategic partnerships;
- reseller or marketplace models;
- material customer incentives;
- significant contract modifications;
- acquisitions or IPO preparation;
- disagreements with auditors;
- recurring manual accounting that no longer scales; and
- revenue policies that have not kept pace with how the business now sells.
The earlier accounting is considered in a new commercial model, the more flexibility the business generally has to address problems without unwinding an executed transaction.
What does a revenue recognition consultant do?
It depends on the problem.
A technical revenue consultant may review contracts, identify relevant accounting questions, research ASC 606 and related guidance, analyze alternatives, document conclusions, prepare accounting memoranda, develop policies, and support discussions with auditors.
A broader engagement can also include contract inventories, revenue-stream scoping, process design, systems requirements, internal controls, disclosures, audit readiness, and training.
For a mature organization, the best outcome is usually not permanent dependency on the consultant. The engagement should leave behind policies, documentation, processes, and internal capability that make the next transaction easier to handle.
What does ASC 606 consulting cost?
There is not a useful single market price because the engagements are too different.
Reviewing one unusual contract and documenting a technical conclusion is fundamentally different from assessing a new monetization model, analyzing hundreds of contracts, rebuilding revenue policies, or providing an interim revenue team.
Pricing also varies significantly between independent specialists, accounting advisory firms, and the Big Four.
I would ask providers to define the expected deliverable before comparing rates. A lower hourly rate is not necessarily cheaper if the engagement requires substantially more hours or produces work that must later be redone.
Who handles revenue recognition for software and SaaS companies?
Software and SaaS remain among the areas where ASC 606 requires substantial judgment.
Common issues include distinguishing licenses from hosted services, identifying performance obligations, implementation and professional services, support and updates, variable or usage-based consideration, standalone selling prices, contract modifications, material rights, and contract costs.
For research, I would start with KPMG's dedicated software and SaaS revenue handbook and the corresponding guidance from the other major accounting firms.
For outside support, I would choose someone who works regularly with software and technology arrangements rather than someone whose ASC 606 experience is primarily in unrelated industries.
How does ASC 606 apply to usage-based pricing?
There is no single answer simply because consideration is usage-based.
The accounting depends on the nature of the promise, the form of variable consideration, whether the arrangement contains a license or other distinct performance obligations, and how the relevant variable-consideration guidance applies to the facts.
This is a good example of why applying a label such as "consumption" or "usage" is not enough to reach an accounting conclusion.
The contract and the underlying economics matter.
Can AI be used for revenue recognition and ASC 606?
Yes, but I would distinguish assistance from judgment.
AI can be useful for extracting contract terms, identifying unusual clauses, comparing agreements to accounting policies, organizing evidence, researching questions, generating initial issue lists, drafting documentation, and testing large populations for exceptions.
Those uses can materially reduce low-value manual work.
I would not allow an AI model to autonomously determine material ASC 606 conclusions without appropriate human review. Revenue accounting depends on contractual facts, accounting judgment, company-specific policies, materiality, precedent, and sometimes legal conclusions that a model may not have or may interpret incorrectly.
The better design is usually AI-assisted technical accounting with defined review and control points.
What are the best free ASC 606 resources?
For free research, I would start with:
- RevenueHub for accessible explanations of individual topics;
- RSM's A Guide to Revenue Recognition for a comprehensive walkthrough;
- KPMG's Revenue Recognition Handbook for detailed interpretive questions;
- KPMG's Software and SaaS Revenue Handbook for technology arrangements;
- PwC Viewpoint's revenue guide and Revenue Toolkit for technical interpretation and examples; and
- the FASB Accounting Standards Codification when you have authorized access to the authoritative literature.
I would use summaries and interpretive guides to understand the issue, but the ultimate accounting position should be grounded in the applicable authoritative guidance.
What should I ask a revenue recognition consultant before hiring them?
I would ask questions that test actual experience rather than general accounting credentials:
- What types of revenue arrangements do you work on most often?
- Have you handled our business model before?
- Who will actually perform the work?
- Do you primarily advise, or can you also implement the conclusion?
- How do you document significant judgments?
- How do you work with external auditors?
- Can you help before contracts are signed?
- Can you support accounting policies, controls, and systems after the technical conclusion?
- What would cause you to bring in another specialist?
- What does the final deliverable look like?
I would also give the provider a difficult fact pattern and listen to the questions they ask.
Good technical accountants usually resist reaching a conclusion too quickly. They want to understand the contract, economics, business practices, and facts that could change the accounting.
Where I Would Start
For a routine question, start with the literature and the major interpretive guides.
For a difficult transaction, determine what kind of help you actually need: an authoritative technical interpretation, software-industry experience, additional execution capacity, audit support, training, or a broader revenue transformation.
Those are different problems and they should not automatically go to the same provider.
My own work is concentrated in complex technology revenue, deal structures, technical accounting, revenue operations, and embedded support. You can see the broader practice on my consulting page.
If the issue is better suited to one of the specialists or resources above, I would use them.