IP Library Granted Patent US 12,373,900
Granted Patent B2
US 12,373,900 · App. 18/425,417 · Granted Jul 29, 2025

System and method for recognizing revenue and managing revenue lifecycles

Inventors: Jagan Balsundaram (Santa Clara, CA); Seshagiri Chilukuri (San Jose, CA); Katherine Pearson (San Jose, CA); Karthikeyan Ramamoorthy (San Jose, CA)
Assignee: Zuora, Inc.
G06Q40/128G06Q30/018
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,373,900
App. No.
18/425,417
Granted
Jul 29, 2025
Kind
B2
Abstract

A system and method for calculating variable consideration for performance obligations. The method can involve, checking a database for historical transaction data, accessing the historical transaction data, and applying one or more predetermined variable consideration rules to the historical transaction data. The method can include automatically analyzing the historical transaction data generating an analysis report based on the data. The method can include uploading predetermined corrections to variable consideration transactions to a database or other storage medium and applying the corrections to historical performance obligation transaction data. The method can include determining whether variable consideration changes should be applied to individual transaction lines within the variable consideration transactions.

Claims (54)

1. A computer-implemented method of projecting revenue for a performance contract that includes variable consideration, the method comprising:

providing, by a server system to one or more client devices over a communication network, one or more interfaces for configuring based on corresponding business operations a set of one or more performance obligation rules for evaluating a performance contract that includes variable consideration;

receiving, by the server system from the one or more interfaces, first input data specifying the set of one or more performance obligation rules, each performance obligation rule of the set of one or more performance obligation rules including one or more conditions;

obtaining, by the server system, information associated with the performance contract, the performance contract including transaction lines associated with one or more transactions;

applying, by the server system, the set of one or more performance obligation rules to the performance contract to associate the transaction lines with a performance obligation template of one or more performance obligation templates to associate one or more performance obligations with one or more revenue recognition events;

receiving, by the server system, second input specifying one or more variable-consideration types associated with the variable consideration;

receiving, by the server system from a database over the communication network, historical transaction data associated with the one or more variable-consideration types;

using, by the server system, the one or more revenue recognition events and the historical transaction data associated with the one or more variable-consideration types to project revenue for the performance contract; and

generating, by the server system, a report based on the projected revenue for the one or more performance obligations that correspond to the one or more revenue recognition events.

2. The computer-implemented method of claim 1 , further comprising:

identifying an adjustment type for one of the one or more variable-consideration type;

using the one or more revenue recognition events and the historical transaction data associated with the one of the one or more variable-consideration types to generate a variable-consideration modifier for the one of the one or more variable-consideration types based on the adjustment type;

applying the variable-consideration modifier to the projected revenue.

3. The computer-implemented method of claim 2 , wherein the variable-consideration modifier is based on a percentage.

4. The computer-implemented method of claim 2 , wherein the variable-consideration modifier is based on an amount.

5. The computer-implemented method of claim 1 , further comprising:

determining actual revenue from the one or more revenue recognition events;

determining one or more corrections to the projected revenue based on the actual revenue; and

applying the one or more corrections.

6. The computer-implemented method of claim 5 , further comprising:

reallocating the transaction lines by reallocating a transaction price in the performance contract in response to the one or more corrections applied to the one or more transactions.

7. The computer-implemented method of claim 5 , further comprising:

applying the one or more corrections to individual transaction lines.

8. The computer-implemented method of claim 1 , further comprising:

assigning a fair value to each transaction of the one or more transactions; and

recognizing transactional revenue associated with the each transaction of the one or more transactions.

9. A server system for projecting revenue for a performance contract that includes variable consideration, the server system comprising:

at least one processor;

memory in communication with the at least one processor, the memory storing computer-executable instructions, which, upon execution by the at least one processor, cause the at least one processor to perform:

providing, by the server system to one or more client devices over a communication network, one or more interfaces for configuring based on corresponding business operations a set of one or more performance obligation rules for evaluating a performance contract that includes variable consideration;

receiving, by the server system from the one or more interfaces, first input data specifying the set of one or more performance obligation rules, each performance obligation rule of the set of one or more performance obligation rules including one or more conditions;

obtaining, by the server system, information associated with the performance contract, the performance contract including transaction lines associated with one or more transactions;

applying, by the server system, the set of one or more performance obligation rules to the performance contract to associate the transaction lines with a performance obligation template of one or more performance obligation templates to associate one or more performance obligations with one or more revenue recognition events;

receiving, by the server system, second input specifying one or more variable-consideration types associated with the variable consideration;

receiving, by the server system from a database over the communication network, historical transaction data associated with the one or more variable-consideration types;

using, by the server system, the one or more revenue recognition events and the historical transaction data associated with the one or more variable-consideration types to project revenue for the performance contract; and

generating, by the server system, a report based on the projected revenue for the one or more performance obligations that correspond to the one or more revenue recognition events.

10. The server system of claim 9 , wherein the computer-executable instructions further cause the at least one processor to perform:

identifying an adjustment type for one of the one or more variable-consideration types;

using the one or more revenue recognition events and the historical transaction data associated with the one of the one or more variable-consideration types to generate a variable-consideration modifier for the one of the one or more variable-consideration types based on the adjustment type;

applying the variable-consideration modifier to the projected revenue.

11. The server system of claim 10 , wherein the variable-consideration modifier is based on a percentage.

12. The server system of claim 10 , wherein the variable-consideration modifier is based on an amount.

13. The server system of claim 9 , wherein the computer-executable instructions further cause the at least one processor to perform:

determining actual revenue from the one or more revenue recognition events;

determining one or more corrections to the projected revenue based on the actual revenue; and

applying the one or more corrections.

14. The server system of claim 13 , wherein the computer-executable instructions further cause the at least one processor to perform:

reallocating the transaction lines by reallocating a transaction price in the performance contract in response to the one or more corrections applied to the one or more transactions.

15. The server system of claim 9 , wherein the computer-executable instructions further cause the at least one processor to perform:

applying the one or more corrections to individual transaction lines.

16. The server system of claim 9 , wherein the computer-executable instructions further cause the at least one processor to perform:

assigning a fair value to each transaction of the one or more transactions; and

recognizing transactional revenue associated with the each transaction of the one or more transactions.

Assignments (4)
SECURITY INTEREST Recorded Feb 14, 2025
From: ZUORA, INC.
To: ROYAL BANK OF CANADA, AS COLLATERAL AGENT
Reel/Frame 070236/0918 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Feb 15, 2024
From: LEEYO SOFTWARE, INC.
To: ZUORA, INC.
Reel/Frame 066472/0086 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Feb 15, 2024
From: BALSUNDARAM, JAGAN; PEARSON, KATHERINE; RAMAMOORTHY, KARTHIKEYAN
To: LEEYO SOFTWARE, INC.
Reel/Frame 066472/0334 →
EMPLOYMENT AGREEMENT Recorded Feb 15, 2024
From: CHILUKURI, SESHAGIRI
To: LEEYO SOFTWARE, INC.
Reel/Frame 066611/0679 →
Continuity (5)
Continuation 17147221 · Jan 12, 2021
Continuation 16216934 · Dec 11, 2018
Continuation 15003593 · Jan 21, 2016
Provisional Application 62106095 · Jan 21, 2015
Related Publication 20240403973A1 · Dec 5, 2024
References Cited (32)
US 7330717B2 · Gidron et al. · 2008 [cited by applicant]
US 7418426B1 · Reunert et al. · 2008 [cited by applicant]
US 7640213B2 · Reunert et al. · 2009 [cited by applicant]
US 8135633B1 · LeBaron et al. · 2012 [cited by applicant]
US 8204809B1 · Wise · 2012 [cited by examiner]
US 8798576B2 · Krishnamoorthy et al. · 2014 [cited by applicant]
US 8918506B1 · Clubb · 2014 [cited by examiner]
US 9892467B2 · Shak et al. · 2018 [cited by applicant]
US 10152755B2 · Balsundaram et al. · 2018 [cited by applicant]
US 10311522B1 · Jin et al. · 2019 [cited by applicant]
US 10713732B2 · Shak et al. · 2020 [cited by applicant]
US 20040111346A1 · Macbeath · 2004 [cited by examiner]
US 20050171873A1 · Alberti et al. · 2005 [cited by applicant]
US 20050222928A1 · Steier et al. · 2005 [cited by applicant]
US 20050278232A1 · Bruffey et al. · 2005 [cited by applicant]
US 20060064370A1 · Mojsilovic et al. · 2006 [cited by applicant]
US 20060149643A1 · Reiner et al. · 2006 [cited by applicant]
US 20060190366A1 · Nelson et al. · 2006 [cited by applicant]
US 20060235773A1 · Nelson et al. · 2006 [cited by applicant]
US 20070168209A1 · Shah · 2007 [cited by applicant]
US 20080033873A1 · Krishnamoorthy · 2008 [cited by examiner]
US 20090216582A1 · Moran · 2009 [cited by examiner]
US 20130073521A1 · Ng et al. · 2013 [cited by applicant]
US 20140101008A1 · Dennis · 2014 [cited by applicant]
US 20140114709A1 · Olsen et al. · 2014 [cited by applicant]
Aguilera, Marcos K., et al., “Matching Events in a Content-Based Subscription System”, Proceedings ofthe Eighteenth Annual ACM Symposium on Principles of Distributed Computing, 1999 (Year: 1999), pp. 53-61. [cited by applicant]
Dempsey, David, et al., “Recurring Revenue Model in Practice”, Industry Trends in Cloud Computing, Palgrave Macmillan, Chem, 2018 (Year: 2018), pp. 139-183. [cited by applicant]
Jhang-Li, Jhih-Hua, et al., “Resource Allocation and Revenue Optimization for Cloud Service Providers”, Decision Support Systems, vol. 77, 2015, pp. 55-66. [cited by applicant]
IFRS Foundation, “IFRS 15 Revenue from Contracts with Customers”, International Financial Reporting Standard, May 2014, 88 pages. [cited by applicant]
Leeyo Software Inc., “New Revenue Recognition Standard ASU Sep. 2014”, 2013, 11 pages. [cited by applicant]
Financial Accounting Standards Board, “Accounting Standards Update No. Sep. 2014: Revenue from Contracts with Customers (Topic 6306)”, May 2014, 154 pages. [cited by applicant]
Skoviera, Martin, et al., “Monetization of Infrastructures and Services”, 2017 European Conference on Networks and Communications (EuCNC), 2017 (Year: 2017), pp. 1-5. [cited by applicant]