In this webinar, Jill Hauck, CPA, shares proven strategies for handling the RevRec scenarios that break most finance systems. If you're dealing with bundled software + implementation, parent-child billing structures, or mid-contract modifications, this session shows you the frameworks that actually work.
What You'll Learn:
- When bundled services are one vs. two performance obligations—and how to automate the split
- How to handle hierarchical billing when invoicing and RevRec entities don't match
- The three ways to recognize unused capacity (and which auditors actually accept)
- How to evaluate mid-contract upsells without retrospective nightmares
- Real-time usage and seat additions: separate contracts or modifications?
Meet Your Instructor
Jill Hauck, Founder and Principal Consultant, 12th & Norwegian
- Expert in Quote to Cash, ASC 606, Deal Desk, and Revenue Operations.
- Partnered with Series A to C companies, driving efficiency and revenue growth.
- 10+ years as a freelance consultant optimizing sales, finance, and accounting operations.
- Aligns revenue operations with strategic goals, while coaching mid-level professionals for leadership in dynamic environments.
Who Should Watch:
- Controllers and revenue accountants managing complex contracts
- Finance teams working with usage-based or hybrid pricing models
- Anyone evaluating when to move from spreadsheets to automated RevRec systems
Webinary Summary
1. How should companies handle revenue recognition for bundled software and implementation?
The approach depends on whether the implementation is required for the software to function. If the implementation is mandatory to use the product, it is considered a single performance obligation. However, if third parties can implement it, the software and the implementation are treated as two separate performance obligations. Teams must use a flexible Contract Builder to set backend rules that separate and allocate the revenue accurately, streamlining your overall revenue recognition process.
2. What is the best way to manage hierarchical billing across multiple entities?
In scenarios where a master contract exists with a parent company but services are provided to various child entities, it is crucial to decouple the billing from the revenue recognition process. Establishing a unique identifier to tie the billing address record back to the specific revenue contract ensures that your accounts receivable remains accurate without restricting the sales structure.
3. How do you account for minimum commitments and unused capacity in usage based pricing models?
With the rise of AI and consumption models, unused capacity is a common challenge in usage based pricing. A practical business approach is to recognize revenue on a straight-line basis and perform a sensitivity analysis at the end of the period. If the unused capacity does not roll over, companies evaluate if the straight-line recognition materially differs from actual usage.
4. What are the revenue recognition implications of mid-contract upsells?
If a mid-contract upsell is sold at a similar discount range to the original contract, it can generally be treated as a new, separate contract. However, if a product is given away for free, it triggers a contract modification evaluation. Managing these modifications requires a dynamic SaaS Billing Platform to ensure consistency in pricing policies and to avoid complex restatements.
5. How should finance teams handle changes in rollover policies mid-contract?
Changing a policy mid-contract to allow unused credits to roll over requires a contract modification. For example, if a Rs 120 contract over 12 months is extended to 14 months to allow for credit usage, the monthly recognized revenue drops. Finance teams must evaluate where they currently sit in the contract timeline. Frequent changes to rollover policies can make it nearly impossible to maintain accurate historical data without specialized Contracts AI to track the adjustments.
6. How do overages and real-time additions impact historical revenue recognition?
When a customer adds an additional seat or exceeds their API call limit, this is typically viewed as a separate purchasing decision. The overage is treated as a new transaction added to the existing subscriptions. To manage this at scale, automated systems connect directly to usage data via APIs, recognizing the overage revenue in real-time based on actual consumption.
7. When should a growing SaaS company transition from spreadsheets to an automated revenue recognition platform?
Spreadsheets offer great flexibility early on, but they become a liability as complexity increases. Once a company hits around 20 complex B2B contracts, the manual effort outgrows a spreadsheet. Transitioning to an automated revenue recognition platform ensures accuracy and compliance out of the box. For a comprehensive look at making this transition, we highly recommend watching our session on how to build a future proof finance tech stack.
