Revenue recognition under ASC 606 and IFRS 15: Principles-based approach to
recognizing revenue from contracts with customers
Introduction
Revenue is a crucial performance metric for businesses. Earlier revenue recognition
guidance was considered complex and lacked consistency across jurisdictions and
industries. To address these challenges, converged standards ASC 606 and IFRS 15 were
issued establishing a common set of principles for revenue recognition from contracts with
customers. This paper examines the five-step principles-based approach, core concepts and
new requirements introduced to recognize revenue at an amount reflecting expected
consideration for goods or services transferred. It analyzes implications for financial
reporting and key industry implementation challenges.
The Five-Step Model
The new standards follow a principles-based five-step model for revenue recognition:
1. Identify the contract with customer - A contract exists when collectability is probable,
parties are committed and enforceable rights/payment terms defined.
2. Identify separate performance obligations - Promised goods/services distinct within
context of contract terms and underlying economic factors.
3. Determine the transaction price - Fixed and variable consideration estimated at contract
inception, excluding amounts from financing components.
4. Allocate the transaction price - Price allocated to each distinct obligation based on
standalone selling prices of goods/services.
5. Recognize revenue as obligations are satisfied - Revenue recognized as control of
promised goods/services transfers to customer over time or at point in time.
This model provides a systematic framework to recognize revenue to depict transfer of
control of promised goods/services to customers in an amount reflecting expected value.
Core Concepts
The standards introduce significant new concepts including:
- Contracts - Binding agreements involving commercial substance between parties with
approved rights/obligations.
- Performance obligations - Distinct goods/services promised in contracts forming separate
units of account.
- Transaction price - Consideration expected in exchange, including variable amounts based
on most likely outcome.
- Control - Ability to direct use and obtain benefits from asset transferred, can prevent others
accessing same benefits.
- Satisfaction of obligations - Transfer of control over time or point in time based on specific
criteria.
These concepts change previous notions while providing consistency to evaluate revenue
contracts across jurisdictions and industries.
Implications
Key implications of the principles-based approach are:
- Earlier revenue recognition for certain hardware/software, telecom, construction contracts
satisfied over time.
- Separating performance obligations requires judgment, affects revenue
allocation/recognition pattern.
- Variable consideration estimates using expected value method increase estimation
complexity.
- Disclosures on judgments, contract balances, performance obligations, disaggregation of
revenue give comprehensive overview.
- Implementation requires cataloging all contract types/terms and assessing impact on
financials, business processes and controls.
- Greater financial reporting risk due to increased judgments and complexity in application
across diverse industries and contracts.
While enhancing comparability, the principles impose substantial costs to adopt and will
likely increase opportunities for earnings management. Robust implementation is key.
Industry Perspectives
Following issues are prevalent during implementation across key industries:
Hardware/Software: Revenue from licensing and support contracts requires assessment of
distinct performance obligations to recognize appropriately over time or point in time.
Telecom: Contract modifications, bundled pricing plans, customer acquisition costs
recognition differ substantially from previous treatment.
Construction: Assessing performance obligations, measuring progress to recognize revenue
over time as control transfers upon enhancing/creating assets.
Real Estate: Determining timing of control transfer for properties under development or sold
with post-closing involvement increases complexity.
Shipping/Transportation: Judging distinct performance obligations and timing of revenue
recognition for freight-forwarding contracts based on supply chain activities poses
challenges.
Adopting the principles consistently across complex, multi-element contracts demands
significant industry-specific application guidance and examples.
Transition Requirements
Entities can adopt the standards on either a full retrospective or modified retrospective basis:
- Full retrospective approach requires recasting all comparative periods presented in
accordance with new guidance. Poses significant effort but increases comparability.
- Modified retrospective approach applies to incomplete contracts on transition date, with
optionally chosen practical expedients. Comparability is reduced in initial year but
substantially less effort than full retrospective approach.
- Transitional reliefs may be elected including hindsight to determine performance
obligations, portfolio approach to similar contracts, no restatement of contract modifications
before transition date.
Careful evaluation of transition methods and practical expedients ensures optimum balance
between comparability and transition costs for various stakeholders.
Conclusion
The principles-based revenue recognition approach harmonizes guidance globally and
addresses inconsistencies prevalent earlier. While judgments, complexity and effort involved
are substantial, it provides a systematic framework to depict economic substance of
customer contracts. Consistent application and high-quality disclosures will enhance
transparency. Transitional reliefs facilitate smooth implementation. Overall, it raises financial
reporting standards through improved depiction of revenue streams and contract obligations.
With judicious application, it leads to more decision-useful information for investors.
Revenue is a crucial performance metric for businesses. Earlier revenue recognition
guidance was considered complex and lacked consistency across jurisdictions and
industries. To address these challenges, converged standards ASC 606 and IFRS 15 were
issued establishing a common set of principles for revenue recognition from contracts with
customers. This paper examines the five-step principles-based approach, core concepts and
new requirements introduced to recognize revenue at an amount reflecting expected
consideration for goods or services transferred. It analyzes implications for financial
reporting and key industry implementation challenges.
The Five-Step Model
The new standards follow a principles-based five-step model for revenue recognition:
1. Identify the contract with customer - A contract exists when collectability is probable,
parties are committed and enforceable rights/payment terms defined.
2. Identify separate performance obligations - Promised goods/services distinct within
context of contract terms and underlying economic factors.
3. Determine the transaction price - Fixed and variable consideration estimated at contract
inception, excluding amounts from financing components.
4. Allocate the transaction price - Price allocated to each distinct obligation based on
standalone selling prices of goods/services.
5. Recognize revenue as obligations are satisfied - Revenue recognized as control of
promised goods/services transfers to customer over time or at point in time.
This model provides a systematic framework to recognize revenue to depict transfer of
control of promised goods/services to customers in an amount reflecting expected value.
Core Concepts
The standards introduce significant new concepts including:
- Contracts - Binding agreements involving commercial substance between parties with
approved rights/obligations.
- Performance obligations - Distinct goods/services promised in contracts forming separate
units of account.
- Transaction price - Consideration expected in exchange, including variable amounts based
on most likely outcome.
- Control - Ability to direct use and obtain benefits from asset transferred, can prevent others
accessing same benefits.
- Satisfaction of obligations - Transfer of control over time or point in time based on specific
criteria.
These concepts change previous notions while providing consistency to evaluate revenue
contracts across jurisdictions and industries.
Implications
Key implications of the principles-based approach are:
- Earlier revenue recognition for certain hardware/software, telecom, construction contracts
satisfied over time.
- Separating performance obligations requires judgment, affects revenue
allocation/recognition pattern.
- Variable consideration estimates using expected value method increase estimation
complexity.
- Disclosures on judgments, contract balances, performance obligations, disaggregation of
revenue give comprehensive overview.
- Implementation requires cataloging all contract types/terms and assessing impact on
financials, business processes and controls.
- Greater financial reporting risk due to increased judgments and complexity in application
across diverse industries and contracts.
While enhancing comparability, the principles impose substantial costs to adopt and will
likely increase opportunities for earnings management. Robust implementation is key.
Industry Perspectives
Following issues are prevalent during implementation across key industries:
Hardware/Software: Revenue from licensing and support contracts requires assessment of
distinct performance obligations to recognize appropriately over time or point in time.
Telecom: Contract modifications, bundled pricing plans, customer acquisition costs
recognition differ substantially from previous treatment.
Construction: Assessing performance obligations, measuring progress to recognize revenue
over time as control transfers upon enhancing/creating assets.
Real Estate: Determining timing of control transfer for properties under development or sold
with post-closing involvement increases complexity.
Shipping/Transportation: Judging distinct performance obligations and timing of revenue
recognition for freight-forwarding contracts based on supply chain activities poses
challenges.
Adopting the principles consistently across complex, multi-element contracts demands
significant industry-specific application guidance and examples.
Transition Requirements
Entities can adopt the standards on either a full retrospective or modified retrospective basis:
- Full retrospective approach requires recasting all comparative periods presented in
accordance with new guidance. Poses significant effort but increases comparability.
- Modified retrospective approach applies to incomplete contracts on transition date, with
optionally chosen practical expedients. Comparability is reduced in initial year but
substantially less effort than full retrospective approach.
- Transitional reliefs may be elected including hindsight to determine performance
obligations, portfolio approach to similar contracts, no restatement of contract modifications
before transition date.
Careful evaluation of transition methods and practical expedients ensures optimum balance
between comparability and transition costs for various stakeholders.
Conclusion
The principles-based revenue recognition approach harmonizes guidance globally and
addresses inconsistencies prevalent earlier. While judgments, complexity and effort involved
are substantial, it provides a systematic framework to depict economic substance of
customer contracts. Consistent application and high-quality disclosures will enhance
transparency. Transitional reliefs facilitate smooth implementation. Overall, it raises financial
reporting standards through improved depiction of revenue streams and contract obligations.
With judicious application, it leads to more decision-useful information for investors.
Revenue is a crucial performance metric for businesses. Earlier revenue recognition
guidance was considered complex and lacked consistency across jurisdictions and
industries. To address these challenges, converged standards ASC 606 and IFRS 15 were
issued establishing a common set of principles for revenue recognition from contracts with
customers. This paper examines the five-step principles-based approach, core concepts and
new requirements introduced to recognize revenue at an amount reflecting expected
consideration for goods or services transferred. It analyzes implications for financial
reporting and key industry implementation challenges.
The Five-Step Model
The new standards follow a principles-based five-step model for revenue recognition:
1. Identify the contract with customer - A contract exists when collectability is probable,
parties are committed and enforceable rights/payment terms defined.
2. Identify separate performance obligations - Promised goods/services distinct within
context of contract terms and underlying economic factors.
3. Determine the transaction price - Fixed and variable consideration estimated at contract
inception, excluding amounts from financing components.
4. Allocate the transaction price - Price allocated to each distinct obligation based on
standalone selling prices of goods/services.
5. Recognize revenue as obligations are satisfied - Revenue recognized as control of
promised goods/services transfers to customer over time or at point in time.
This model provides a systematic framework to recognize revenue to depict transfer of
control of promised goods/services to customers in an amount reflecting expected value.
Core Concepts
The standards introduce significant new concepts including:
- Contracts - Binding agreements involving commercial substance between parties with
approved rights/obligations.
- Performance obligations - Distinct goods/services promised in contracts forming separate
units of account.
- Transaction price - Consideration expected in exchange, including variable amounts based
on most likely outcome.
- Control - Ability to direct use and obtain benefits from asset transferred, can prevent others
accessing same benefits.
- Satisfaction of obligations - Transfer of control over time or point in time based on specific
criteria.
These concepts change previous notions while providing consistency to evaluate revenue
contracts across jurisdictions and industries.
Implications
Key implications of the principles-based approach are:
- Earlier revenue recognition for certain hardware/software, telecom, construction contracts
satisfied over time.
- Separating performance obligations requires judgment, affects revenue
allocation/recognition pattern.
- Variable consideration estimates using expected value method increase estimation
complexity.
- Disclosures on judgments, contract balances, performance obligations, disaggregation of
revenue give comprehensive overview.
- Implementation requires cataloging all contract types/terms and assessing impact on
financials, business processes and controls.
- Greater financial reporting risk due to increased judgments and complexity in application
across diverse industries and contracts.
While enhancing comparability, the principles impose substantial costs to adopt and will
likely increase opportunities for earnings management. Robust implementation is key.
Industry Perspectives
Following issues are prevalent during implementation across key industries:
Hardware/Software: Revenue from licensing and support contracts requires assessment of
distinct performance obligations to recognize appropriately over time or point in time.
Telecom: Contract modifications, bundled pricing plans, customer acquisition costs
recognition differ substantially from previous treatment.
Construction: Assessing performance obligations, measuring progress to recognize revenue
over time as control transfers upon enhancing/creating assets.
Real Estate: Determining timing of control transfer for properties under development or sold
with post-closing involvement increases complexity.
Shipping/Transportation: Judging distinct performance obligations and timing of revenue
recognition for freight-forwarding contracts based on supply chain activities poses
challenges.
Adopting the principles consistently across complex, multi-element contracts demands
significant industry-specific application guidance and examples.
Transition Requirements
Entities can adopt the standards on either a full retrospective or modified retrospective basis:
- Full retrospective approach requires recasting all comparative periods presented in
accordance with new guidance. Poses significant effort but increases comparability.
- Modified retrospective approach applies to incomplete contracts on transition date, with
optionally chosen practical expedients. Comparability is reduced in initial year but
substantially less effort than full retrospective approach.
- Transitional reliefs may be elected including hindsight to determine performance
obligations, portfolio approach to similar contracts, no restatement of contract modifications
before transition date.
Careful evaluation of transition methods and practical expedients ensures optimum balance
between comparability and transition costs for various stakeholders.
Conclusion
The principles-based revenue recognition approach harmonizes guidance globally and
addresses inconsistencies prevalent earlier. While judgments, complexity and effort involved
are substantial, it provides a systematic framework to depict economic substance of
customer contracts. Consistent application and high-quality disclosures will enhance
transparency. Transitional reliefs facilitate smooth implementation. Overall, it raises financial
reporting standards through improved depiction of revenue streams and contract obligations.
With judicious application, it leads to more decision-useful information for investors.
Revenue is a crucial performance metric for businesses. Earlier revenue recognition
guidance was considered complex and lacked consistency across jurisdictions and
industries. To address these challenges, converged standards ASC 606 and IFRS 15 were
issued establishing a common set of principles for revenue recognition from contracts with
customers. This paper examines the five-step principles-based approach, core concepts and
new requirements introduced to recognize revenue at an amount reflecting expected
consideration for goods or services transferred. It analyzes implications for financial
reporting and key industry implementation challenges.
The Five-Step Model
The new standards follow a principles-based five-step model for revenue recognition:
1. Identify the contract with customer - A contract exists when collectability is probable,
parties are committed and enforceable rights/payment terms defined.
2. Identify separate performance obligations - Promised goods/services distinct within
context of contract terms and underlying economic factors.
3. Determine the transaction price - Fixed and variable consideration estimated at contract
inception, excluding amounts from financing components.
4. Allocate the transaction price - Price allocated to each distinct obligation based on
standalone selling prices of goods/services.
5. Recognize revenue as obligations are satisfied - Revenue recognized as control of
promised goods/services transfers to customer over time or at point in time.
This model provides a systematic framework to recognize revenue to depict transfer of
control of promised goods/services to customers in an amount reflecting expected value.
Core Concepts
The standards introduce significant new concepts including:
- Contracts - Binding agreements involving commercial substance between parties with
approved rights/obligations.
- Performance obligations - Distinct goods/services promised in contracts forming separate
units of account.
- Transaction price - Consideration expected in exchange, including variable amounts based
on most likely outcome.
- Control - Ability to direct use and obtain benefits from asset transferred, can prevent others
accessing same benefits.
- Satisfaction of obligations - Transfer of control over time or point in time based on specific
criteria.
These concepts change previous notions while providing consistency to evaluate revenue
contracts across jurisdictions and industries.
Implications
Key implications of the principles-based approach are:
- Earlier revenue recognition for certain hardware/software, telecom, construction contracts
satisfied over time.
- Separating performance obligations requires judgment, affects revenue
allocation/recognition pattern.
- Variable consideration estimates using expected value method increase estimation
complexity.
- Disclosures on judgments, contract balances, performance obligations, disaggregation of
revenue give comprehensive overview.
- Implementation requires cataloging all contract types/terms and assessing impact on
financials, business processes and controls.
- Greater financial reporting risk due to increased judgments and complexity in application
across diverse industries and contracts.
While enhancing comparability, the principles impose substantial costs to adopt and will
likely increase opportunities for earnings management. Robust implementation is key.
Industry Perspectives
Following issues are prevalent during implementation across key industries:
Hardware/Software: Revenue from licensing and support contracts requires assessment of
distinct performance obligations to recognize appropriately over time or point in time.
Telecom: Contract modifications, bundled pricing plans, customer acquisition costs
recognition differ substantially from previous treatment.
Construction: Assessing performance obligations, measuring progress to recognize revenue
over time as control transfers upon enhancing/creating assets.
Real Estate: Determining timing of control transfer for properties under development or sold
with post-closing involvement increases complexity.
Shipping/Transportation: Judging distinct performance obligations and timing of revenue
recognition for freight-forwarding contracts based on supply chain activities poses
challenges.
Adopting the principles consistently across complex, multi-element contracts demands
significant industry-specific application guidance and examples.
Transition Requirements
Entities can adopt the standards on either a full retrospective or modified retrospective basis:
- Full retrospective approach requires recasting all comparative periods presented in
accordance with new guidance. Poses significant effort but increases comparability.
- Modified retrospective approach applies to incomplete contracts on transition date, with
optionally chosen practical expedients. Comparability is reduced in initial year but
substantially less effort than full retrospective approach.
- Transitional reliefs may be elected including hindsight to determine performance
obligations, portfolio approach to similar contracts, no restatement of contract modifications
before transition date.
Careful evaluation of transition methods and practical expedients ensures optimum balance
between comparability and transition costs for various stakeholders.
Conclusion
The principles-based revenue recognition approach harmonizes guidance globally and
addresses inconsistencies prevalent earlier. While judgments, complexity and effort involved
are substantial, it provides a systematic framework to depict economic substance of
customer contracts. Consistent application and high-quality disclosures will enhance
transparency. Transitional reliefs facilitate smooth implementation. Overall, it raises financial
reporting standards through improved depiction of revenue streams and contract obligations.
With judicious application, it leads to more decision-useful information for investors.
Revenue is a crucial performance metric for businesses. Earlier revenue recognition
guidance was considered complex and lacked consistency across jurisdictions and
industries. To address these challenges, converged standards ASC 606 and IFRS 15 were
issued establishing a common set of principles for revenue recognition from contracts with
customers. This paper examines the five-step principles-based approach, core concepts and
new requirements introduced to recognize revenue at an amount reflecting expected
consideration for goods or services transferred. It analyzes implications for financial
reporting and key industry implementation challenges.
The Five-Step Model
The new standards follow a principles-based five-step model for revenue recognition:
1. Identify the contract with customer - A contract exists when collectability is probable,
parties are committed and enforceable rights/payment terms defined.
2. Identify separate performance obligations - Promised goods/services distinct within
context of contract terms and underlying economic factors.
3. Determine the transaction price - Fixed and variable consideration estimated at contract
inception, excluding amounts from financing components.
4. Allocate the transaction price - Price allocated to each distinct obligation based on
standalone selling prices of goods/services.
5. Recognize revenue as obligations are satisfied - Revenue recognized as control of
promised goods/services transfers to customer over time or at point in time.
This model provides a systematic framework to recognize revenue to depict transfer of
control of promised goods/services to customers in an amount reflecting expected value.
Core Concepts
The standards introduce significant new concepts including:
- Contracts - Binding agreements involving commercial substance between parties with
approved rights/obligations.
- Performance obligations - Distinct goods/services promised in contracts forming separate
units of account.
- Transaction price - Consideration expected in exchange, including variable amounts based
on most likely outcome.
- Control - Ability to direct use and obtain benefits from asset transferred, can prevent others
accessing same benefits.
- Satisfaction of obligations - Transfer of control over time or point in time based on specific
criteria.
These concepts change previous notions while providing consistency to evaluate revenue
contracts across jurisdictions and industries.
Implications
Key implications of the principles-based approach are:
- Earlier revenue recognition for certain hardware/software, telecom, construction contracts
satisfied over time.
- Separating performance obligations requires judgment, affects revenue
allocation/recognition pattern.
- Variable consideration estimates using expected value method increase estimation
complexity.
- Disclosures on judgments, contract balances, performance obligations, disaggregation of
revenue give comprehensive overview.
- Implementation requires cataloging all contract types/terms and assessing impact on
financials, business processes and controls.
- Greater financial reporting risk due to increased judgments and complexity in application
across diverse industries and contracts.
While enhancing comparability, the principles impose substantial costs to adopt and will
likely increase opportunities for earnings management. Robust implementation is key.
Industry Perspectives
Following issues are prevalent during implementation across key industries:
Hardware/Software: Revenue from licensing and support contracts requires assessment of
distinct performance obligations to recognize appropriately over time or point in time.
Telecom: Contract modifications, bundled pricing plans, customer acquisition costs
recognition differ substantially from previous treatment.
Construction: Assessing performance obligations, measuring progress to recognize revenue
over time as control transfers upon enhancing/creating assets.
Real Estate: Determining timing of control transfer for properties under development or sold
with post-closing involvement increases complexity.
Shipping/Transportation: Judging distinct performance obligations and timing of revenue
recognition for freight-forwarding contracts based on supply chain activities poses
challenges.
Adopting the principles consistently across complex, multi-element contracts demands
significant industry-specific application guidance and examples.
Transition Requirements
Entities can adopt the standards on either a full retrospective or modified retrospective basis:
- Full retrospective approach requires recasting all comparative periods presented in
accordance with new guidance. Poses significant effort but increases comparability.
- Modified retrospective approach applies to incomplete contracts on transition date, with
optionally chosen practical expedients. Comparability is reduced in initial year but
substantially less effort than full retrospective approach.
- Transitional reliefs may be elected including hindsight to determine performance
obligations, portfolio approach to similar contracts, no restatement of contract modifications
before transition date.
Careful evaluation of transition methods and practical expedients ensures optimum balance
between comparability and transition costs for various stakeholders.
Conclusion
The principles-based revenue recognition approach harmonizes guidance globally and
addresses inconsistencies prevalent earlier. While judgments, complexity and effort involved
are substantial, it provides a systematic framework to depict economic substance of
customer contracts. Consistent application and high-quality disclosures will enhance
transparency. Transitional reliefs facilitate smooth implementation. Overall, it raises financial
reporting standards through improved depiction of revenue streams and contract obligations.
With judicious application, it leads to more decision-useful information for investors.
Revenue is a crucial performance metric for businesses. Earlier revenue recognition
guidance was considered complex and lacked consistency across jurisdictions and
industries. To address these challenges, converged standards ASC 606 and IFRS 15 were
issued establishing a common set of principles for revenue recognition from contracts with
customers. This paper examines the five-step principles-based approach, core concepts and
new requirements introduced to recognize revenue at an amount reflecting expected
consideration for goods or services transferred. It analyzes implications for financial
reporting and key industry implementation challenges.
The Five-Step Model
The new standards follow a principles-based five-step model for revenue recognition:
1. Identify the contract with customer - A contract exists when collectability is probable,
parties are committed and enforceable rights/payment terms defined.
2. Identify separate performance obligations - Promised goods/services distinct within
context of contract terms and underlying economic factors.
3. Determine the transaction price - Fixed and variable consideration estimated at contract
inception, excluding amounts from financing components.
4. Allocate the transaction price - Price allocated to each distinct obligation based on
standalone selling prices of goods/services.
5. Recognize revenue as obligations are satisfied - Revenue recognized as control of
promised goods/services transfers to customer over time or at point in time.
This model provides a systematic framework to recognize revenue to depict transfer of
control of promised goods/services to customers in an amount reflecting expected value.
Core Concepts
The standards introduce significant new concepts including:
- Contracts - Binding agreements involving commercial substance between parties with
approved rights/obligations.
- Performance obligations - Distinct goods/services promised in contracts forming separate
units of account.
- Transaction price - Consideration expected in exchange, including variable amounts based
on most likely outcome.
- Control - Ability to direct use and obtain benefits from asset transferred, can prevent others
accessing same benefits.
- Satisfaction of obligations - Transfer of control over time or point in time based on specific
criteria.
These concepts change previous notions while providing consistency to evaluate revenue
contracts across jurisdictions and industries.
Implications
Key implications of the principles-based approach are:
- Earlier revenue recognition for certain hardware/software, telecom, construction contracts
satisfied over time.
- Separating performance obligations requires judgment, affects revenue
allocation/recognition pattern.
- Variable consideration estimates using expected value method increase estimation
complexity.
- Disclosures on judgments, contract balances, performance obligations, disaggregation of
revenue give comprehensive overview.
- Implementation requires cataloging all contract types/terms and assessing impact on
financials, business processes and controls.
- Greater financial reporting risk due to increased judgments and complexity in application
across diverse industries and contracts.
While enhancing comparability, the principles impose substantial costs to adopt and will
likely increase opportunities for earnings management. Robust implementation is key.
Industry Perspectives
Following issues are prevalent during implementation across key industries:
Hardware/Software: Revenue from licensing and support contracts requires assessment of
distinct performance obligations to recognize appropriately over time or point in time.
Telecom: Contract modifications, bundled pricing plans, customer acquisition costs
recognition differ substantially from previous treatment.
Construction: Assessing performance obligations, measuring progress to recognize revenue
over time as control transfers upon enhancing/creating assets.
Real Estate: Determining timing of control transfer for properties under development or sold
with post-closing involvement increases complexity.
Shipping/Transportation: Judging distinct performance obligations and timing of revenue
recognition for freight-forwarding contracts based on supply chain activities poses
challenges.
Adopting the principles consistently across complex, multi-element contracts demands
significant industry-specific application guidance and examples.
Transition Requirements
Entities can adopt the standards on either a full retrospective or modified retrospective basis:
- Full retrospective approach requires recasting all comparative periods presented in
accordance with new guidance. Poses significant effort but increases comparability.
- Modified retrospective approach applies to incomplete contracts on transition date, with
optionally chosen practical expedients. Comparability is reduced in initial year but
substantially less effort than full retrospective approach.
- Transitional reliefs may be elected including hindsight to determine performance
obligations, portfolio approach to similar contracts, no restatement of contract modifications
before transition date.
Careful evaluation of transition methods and practical expedients ensures optimum balance
between comparability and transition costs for various stakeholders.
Conclusion
The principles-based revenue recognition approach harmonizes guidance globally and
addresses inconsistencies prevalent earlier. While judgments, complexity and effort involved
are substantial, it provides a systematic framework to depict economic substance of
customer contracts. Consistent application and high-quality disclosures will enhance
transparency. Transitional reliefs facilitate smooth implementation. Overall, it raises financial
reporting standards through improved depiction of revenue streams and contract obligations.
With judicious application, it leads to more decision-useful information for investors.
Revenue is a crucial performance metric for businesses. Earlier revenue recognition
guidance was considered complex and lacked consistency across jurisdictions and
industries. To address these challenges, converged standards ASC 606 and IFRS 15 were
issued establishing a common set of principles for revenue recognition from contracts with
customers. This paper examines the five-step principles-based approach, core concepts and
new requirements introduced to recognize revenue at an amount reflecting expected
consideration for goods or services transferred. It analyzes implications for financial
reporting and key industry implementation challenges.
The Five-Step Model
The new standards follow a principles-based five-step model for revenue recognition:
1. Identify the contract with customer - A contract exists when collectability is probable,
parties are committed and enforceable rights/payment terms defined.
2. Identify separate performance obligations - Promised goods/services distinct within
context of contract terms and underlying economic factors.
3. Determine the transaction price - Fixed and variable consideration estimated at contract
inception, excluding amounts from financing components.
4. Allocate the transaction price - Price allocated to each distinct obligation based on
standalone selling prices of goods/services.
5. Recognize revenue as obligations are satisfied - Revenue recognized as control of
promised goods/services transfers to customer over time or at point in time.
This model provides a systematic framework to recognize revenue to depict transfer of
control of promised goods/services to customers in an amount reflecting expected value.
Core Concepts
The standards introduce significant new concepts including:
- Contracts - Binding agreements involving commercial substance between parties with
approved rights/obligations.
- Performance obligations - Distinct goods/services promised in contracts forming separate
units of account.
- Transaction price - Consideration expected in exchange, including variable amounts based
on most likely outcome.
- Control - Ability to direct use and obtain benefits from asset transferred, can prevent others
accessing same benefits.
- Satisfaction of obligations - Transfer of control over time or point in time based on specific
criteria.
These concepts change previous notions while providing consistency to evaluate revenue
contracts across jurisdictions and industries.
Implications
Key implications of the principles-based approach are:
- Earlier revenue recognition for certain hardware/software, telecom, construction contracts
satisfied over time.
- Separating performance obligations requires judgment, affects revenue
allocation/recognition pattern.
- Variable consideration estimates using expected value method increase estimation
complexity.
- Disclosures on judgments, contract balances, performance obligations, disaggregation of
revenue give comprehensive overview.
- Implementation requires cataloging all contract types/terms and assessing impact on
financials, business processes and controls.
- Greater financial reporting risk due to increased judgments and complexity in application
across diverse industries and contracts.
While enhancing comparability, the principles impose substantial costs to adopt and will
likely increase opportunities for earnings management. Robust implementation is key.
Industry Perspectives
Following issues are prevalent during implementation across key industries:
Hardware/Software: Revenue from licensing and support contracts requires assessment of
distinct performance obligations to recognize appropriately over time or point in time.
Telecom: Contract modifications, bundled pricing plans, customer acquisition costs
recognition differ substantially from previous treatment.
Construction: Assessing performance obligations, measuring progress to recognize revenue
over time as control transfers upon enhancing/creating assets.
Real Estate: Determining timing of control transfer for properties under development or sold
with post-closing involvement increases complexity.
Shipping/Transportation: Judging distinct performance obligations and timing of revenue
recognition for freight-forwarding contracts based on supply chain activities poses
challenges.
Adopting the principles consistently across complex, multi-element contracts demands
significant industry-specific application guidance and examples.
Transition Requirements
Entities can adopt the standards on either a full retrospective or modified retrospective basis:
- Full retrospective approach requires recasting all comparative periods presented in
accordance with new guidance. Poses significant effort but increases comparability.
- Modified retrospective approach applies to incomplete contracts on transition date, with
optionally chosen practical expedients. Comparability is reduced in initial year but
substantially less effort than full retrospective approach.
- Transitional reliefs may be elected including hindsight to determine performance
obligations, portfolio approach to similar contracts, no restatement of contract modifications
before transition date.
Careful evaluation of transition methods and practical expedients ensures optimum balance
between comparability and transition costs for various stakeholders.
Conclusion
The principles-based revenue recognition approach harmonizes guidance globally and
addresses inconsistencies prevalent earlier. While judgments, complexity and effort involved
are substantial, it provides a systematic framework to depict economic substance of
customer contracts. Consistent application and high-quality disclosures will enhance
transparency. Transitional reliefs facilitate smooth implementation. Overall, it raises financial
reporting standards through improved depiction of revenue streams and contract obligations.
With judicious application, it leads to more decision-useful information for investors.
Revenue is a crucial performance metric for businesses. Earlier revenue recognition
guidance was considered complex and lacked consistency across jurisdictions and
industries. To address these challenges, converged standards ASC 606 and IFRS 15 were
issued establishing a common set of principles for revenue recognition from contracts with
customers. This paper examines the five-step principles-based approach, core concepts and
new requirements introduced to recognize revenue at an amount reflecting expected
consideration for goods or services transferred. It analyzes implications for financial
reporting and key industry implementation challenges.
The Five-Step Model
The new standards follow a principles-based five-step model for revenue recognition:
1. Identify the contract with customer - A contract exists when collectability is probable,
parties are committed and enforceable rights/payment terms defined.
2. Identify separate performance obligations - Promised goods/services distinct within
context of contract terms and underlying economic factors.
3. Determine the transaction price - Fixed and variable consideration estimated at contract
inception, excluding amounts from financing components.
4. Allocate the transaction price - Price allocated to each distinct obligation based on
standalone selling prices of goods/services.
5. Recognize revenue as obligations are satisfied - Revenue recognized as control of
promised goods/services transfers to customer over time or at point in time.
This model provides a systematic framework to recognize revenue to depict transfer of
control of promised goods/services to customers in an amount reflecting expected value.
Core Concepts
The standards introduce significant new concepts including:
- Contracts - Binding agreements involving commercial substance between parties with
approved rights/obligations.
- Performance obligations - Distinct goods/services promised in contracts forming separate
units of account.
- Transaction price - Consideration expected in exchange, including variable amounts based
on most likely outcome.
- Control - Ability to direct use and obtain benefits from asset transferred, can prevent others
accessing same benefits.
- Satisfaction of obligations - Transfer of control over time or point in time based on specific
criteria.
These concepts change previous notions while providing consistency to evaluate revenue
contracts across jurisdictions and industries.
Implications
Key implications of the principles-based approach are:
- Earlier revenue recognition for certain hardware/software, telecom, construction contracts
satisfied over time.
- Separating performance obligations requires judgment, affects revenue
allocation/recognition pattern.
- Variable consideration estimates using expected value method increase estimation
complexity.
- Disclosures on judgments, contract balances, performance obligations, disaggregation of
revenue give comprehensive overview.
- Implementation requires cataloging all contract types/terms and assessing impact on
financials, business processes and controls.
- Greater financial reporting risk due to increased judgments and complexity in application
across diverse industries and contracts.
While enhancing comparability, the principles impose substantial costs to adopt and will
likely increase opportunities for earnings management. Robust implementation is key.
Industry Perspectives
Following issues are prevalent during implementation across key industries:
Hardware/Software: Revenue from licensing and support contracts requires assessment of
distinct performance obligations to recognize appropriately over time or point in time.
Telecom: Contract modifications, bundled pricing plans, customer acquisition costs
recognition differ substantially from previous treatment.
Construction: Assessing performance obligations, measuring progress to recognize revenue
over time as control transfers upon enhancing/creating assets.
Real Estate: Determining timing of control transfer for properties under development or sold
with post-closing involvement increases complexity.
Shipping/Transportation: Judging distinct performance obligations and timing of revenue
recognition for freight-forwarding contracts based on supply chain activities poses
challenges.
Adopting the principles consistently across complex, multi-element contracts demands
significant industry-specific application guidance and examples.
Transition Requirements
Entities can adopt the standards on either a full retrospective or modified retrospective basis:
- Full retrospective approach requires recasting all comparative periods presented in
accordance with new guidance. Poses significant effort but increases comparability.
- Modified retrospective approach applies to incomplete contracts on transition date, with
optionally chosen practical expedients. Comparability is reduced in initial year but
substantially less effort than full retrospective approach.
- Transitional reliefs may be elected including hindsight to determine performance
obligations, portfolio approach to similar contracts, no restatement of contract modifications
before transition date.
Careful evaluation of transition methods and practical expedients ensures optimum balance
between comparability and transition costs for various stakeholders.
Conclusion
The principles-based revenue recognition approach harmonizes guidance globally and
addresses inconsistencies prevalent earlier. While judgments, complexity and effort involved
are substantial, it provides a systematic framework to depict economic substance of
customer contracts. Consistent application and high-quality disclosures will enhance
transparency. Transitional reliefs facilitate smooth implementation. Overall, it raises financial
reporting standards through improved depiction of revenue streams and contract obligations.
With judicious application, it leads to more decision-useful information for investors.
Revenue is a crucial performance metric for businesses. Earlier revenue recognition
guidance was considered complex and lacked consistency across jurisdictions and
industries. To address these challenges, converged standards ASC 606 and IFRS 15 were
issued establishing a common set of principles for revenue recognition from contracts with
customers. This paper examines the five-step principles-based approach, core concepts and
new requirements introduced to recognize revenue at an amount reflecting expected
consideration for goods or services transferred. It analyzes implications for financial
reporting and key industry implementation challenges.
The Five-Step Model
The new standards follow a principles-based five-step model for revenue recognition:
1. Identify the contract with customer - A contract exists when collectability is probable,
parties are committed and enforceable rights/payment terms defined.
2. Identify separate performance obligations - Promised goods/services distinct within
context of contract terms and underlying economic factors.
3. Determine the transaction price - Fixed and variable consideration estimated at contract
inception, excluding amounts from financing components.
4. Allocate the transaction price - Price allocated to each distinct obligation based on
standalone selling prices of goods/services.
5. Recognize revenue as obligations are satisfied - Revenue recognized as control of
promised goods/services transfers to customer over time or at point in time.
This model provides a systematic framework to recognize revenue to depict transfer of
control of promised goods/services to customers in an amount reflecting expected value.
Core Concepts
The standards introduce significant new concepts including:
- Contracts - Binding agreements involving commercial substance between parties with
approved rights/obligations.
- Performance obligations - Distinct goods/services promised in contracts forming separate
units of account.
- Transaction price - Consideration expected in exchange, including variable amounts based
on most likely outcome.
- Control - Ability to direct use and obtain benefits from asset transferred, can prevent others
accessing same benefits.
- Satisfaction of obligations - Transfer of control over time or point in time based on specific
criteria.
These concepts change previous notions while providing consistency to evaluate revenue
contracts across jurisdictions and industries.
Implications
Key implications of the principles-based approach are:
- Earlier revenue recognition for certain hardware/software, telecom, construction contracts
satisfied over time.
- Separating performance obligations requires judgment, affects revenue
allocation/recognition pattern.
- Variable consideration estimates using expected value method increase estimation
complexity.
- Disclosures on judgments, contract balances, performance obligations, disaggregation of
revenue give comprehensive overview.
- Implementation requires cataloging all contract types/terms and assessing impact on
financials, business processes and controls.
- Greater financial reporting risk due to increased judgments and complexity in application
across diverse industries and contracts.
While enhancing comparability, the principles impose substantial costs to adopt and will
likely increase opportunities for earnings management. Robust implementation is key.
Industry Perspectives
Following issues are prevalent during implementation across key industries:
Hardware/Software: Revenue from licensing and support contracts requires assessment of
distinct performance obligations to recognize appropriately over time or point in time.
Telecom: Contract modifications, bundled pricing plans, customer acquisition costs
recognition differ substantially from previous treatment.
Construction: Assessing performance obligations, measuring progress to recognize revenue
over time as control transfers upon enhancing/creating assets.
Real Estate: Determining timing of control transfer for properties under development or sold
with post-closing involvement increases complexity.
Shipping/Transportation: Judging distinct performance obligations and timing of revenue
recognition for freight-forwarding contracts based on supply chain activities poses
challenges.
Adopting the principles consistently across complex, multi-element contracts demands
significant industry-specific application guidance and examples.
Transition Requirements
Entities can adopt the standards on either a full retrospective or modified retrospective basis:
- Full retrospective approach requires recasting all comparative periods presented in
accordance with new guidance. Poses significant effort but increases comparability.
- Modified retrospective approach applies to incomplete contracts on transition date, with
optionally chosen practical expedients. Comparability is reduced in initial year but
substantially less effort than full retrospective approach.
- Transitional reliefs may be elected including hindsight to determine performance
obligations, portfolio approach to similar contracts, no restatement of contract modifications
before transition date.
Careful evaluation of transition methods and practical expedients ensures optimum balance
between comparability and transition costs for various stakeholders.
Conclusion
The principles-based revenue recognition approach harmonizes guidance globally and
addresses inconsistencies prevalent earlier. While judgments, complexity and effort involved
are substantial, it provides a systematic framework to depict economic substance of
customer contracts. Consistent application and high-quality disclosures will enhance
transparency. Transitional reliefs facilitate smooth implementation. Overall, it raises financial
reporting standards through improved depiction of revenue streams and contract obligations.
With judicious application, it leads to more decision-useful information for investors.
Revenue is a crucial performance metric for businesses. Earlier revenue recognition
guidance was considered complex and lacked consistency across jurisdictions and
industries. To address these challenges, converged standards ASC 606 and IFRS 15 were
issued establishing a common set of principles for revenue recognition from contracts with
customers. This paper examines the five-step principles-based approach, core concepts and
new requirements introduced to recognize revenue at an amount reflecting expected
consideration for goods or services transferred. It analyzes implications for financial
reporting and key industry implementation challenges.
The Five-Step Model
The new standards follow a principles-based five-step model for revenue recognition:
1. Identify the contract with customer - A contract exists when collectability is probable,
parties are committed and enforceable rights/payment terms defined.
2. Identify separate performance obligations - Promised goods/services distinct within
context of contract terms and underlying economic factors.
3. Determine the transaction price - Fixed and variable consideration estimated at contract
inception, excluding amounts from financing components.
4. Allocate the transaction price - Price allocated to each distinct obligation based on
standalone selling prices of goods/services.
5. Recognize revenue as obligations are satisfied - Revenue recognized as control of
promised goods/services transfers to customer over time or at point in time.
This model provides a systematic framework to recognize revenue to depict transfer of
control of promised goods/services to customers in an amount reflecting expected value.
Core Concepts
The standards introduce significant new concepts including:
- Contracts - Binding agreements involving commercial substance between parties with
approved rights/obligations.
- Performance obligations - Distinct goods/services promised in contracts forming separate
units of account.
- Transaction price - Consideration expected in exchange, including variable amounts based
on most likely outcome.
- Control - Ability to direct use and obtain benefits from asset transferred, can prevent others
accessing same benefits.
- Satisfaction of obligations - Transfer of control over time or point in time based on specific
criteria.
These concepts change previous notions while providing consistency to evaluate revenue
contracts across jurisdictions and industries.
Implications
Key implications of the principles-based approach are:
- Earlier revenue recognition for certain hardware/software, telecom, construction contracts
satisfied over time.
- Separating performance obligations requires judgment, affects revenue
allocation/recognition pattern.
- Variable consideration estimates using expected value method increase estimation
complexity.
- Disclosures on judgments, contract balances, performance obligations, disaggregation of
revenue give comprehensive overview.
- Implementation requires cataloging all contract types/terms and assessing impact on
financials, business processes and controls.
- Greater financial reporting risk due to increased judgments and complexity in application
across diverse industries and contracts.
While enhancing comparability, the principles impose substantial costs to adopt and will
likely increase opportunities for earnings management. Robust implementation is key.
Industry Perspectives
Following issues are prevalent during implementation across key industries:
Hardware/Software: Revenue from licensing and support contracts requires assessment of
distinct performance obligations to recognize appropriately over time or point in time.
Telecom: Contract modifications, bundled pricing plans, customer acquisition costs
recognition differ substantially from previous treatment.
Construction: Assessing performance obligations, measuring progress to recognize revenue
over time as control transfers upon enhancing/creating assets.
Real Estate: Determining timing of control transfer for properties under development or sold
with post-closing involvement increases complexity.
Shipping/Transportation: Judging distinct performance obligations and timing of revenue
recognition for freight-forwarding contracts based on supply chain activities poses
challenges.
Adopting the principles consistently across complex, multi-element contracts demands
significant industry-specific application guidance and examples.
Transition Requirements
Entities can adopt the standards on either a full retrospective or modified retrospective basis:
- Full retrospective approach requires recasting all comparative periods presented in
accordance with new guidance. Poses significant effort but increases comparability.
- Modified retrospective approach applies to incomplete contracts on transition date, with
optionally chosen practical expedients. Comparability is reduced in initial year but
substantially less effort than full retrospective approach.
- Transitional reliefs may be elected including hindsight to determine performance
obligations, portfolio approach to similar contracts, no restatement of contract modifications
before transition date.
Careful evaluation of transition methods and practical expedients ensures optimum balance
between comparability and transition costs for various stakeholders.
Conclusion
The principles-based revenue recognition approach harmonizes guidance globally and
addresses inconsistencies prevalent earlier. While judgments, complexity and effort involved
are substantial, it provides a systematic framework to depict economic substance of
customer contracts. Consistent application and high-quality disclosures will enhance
transparency. Transitional reliefs facilitate smooth implementation. Overall, it raises financial
reporting standards through improved depiction of revenue streams and contract obligations.
With judicious application, it leads to more decision-useful information for investors.
Revenue is a crucial performance metric for businesses. Earlier revenue recognition
guidance was considered complex and lacked consistency across jurisdictions and
industries. To address these challenges, converged standards ASC 606 and IFRS 15 were
issued establishing a common set of principles for revenue recognition from contracts with
customers. This paper examines the five-step principles-based approach, core concepts and
new requirements introduced to recognize revenue at an amount reflecting expected
consideration for goods or services transferred. It analyzes implications for financial
reporting and key industry implementation challenges.
The Five-Step Model
The new standards follow a principles-based five-step model for revenue recognition:
1. Identify the contract with customer - A contract exists when collectability is probable,
parties are committed and enforceable rights/payment terms defined.
2. Identify separate performance obligations - Promised goods/services distinct within
context of contract terms and underlying economic factors.
3. Determine the transaction price - Fixed and variable consideration estimated at contract
inception, excluding amounts from financing components.
4. Allocate the transaction price - Price allocated to each distinct obligation based on
standalone selling prices of goods/services.
5. Recognize revenue as obligations are satisfied - Revenue recognized as control of
promised goods/services transfers to customer over time or at point in time.
This model provides a systematic framework to recognize revenue to depict transfer of
control of promised goods/services to customers in an amount reflecting expected value.
Core Concepts
The standards introduce significant new concepts including:
- Contracts - Binding agreements involving commercial substance between parties with
approved rights/obligations.
- Performance obligations - Distinct goods/services promised in contracts forming separate
units of account.
- Transaction price - Consideration expected in exchange, including variable amounts based
on most likely outcome.
- Control - Ability to direct use and obtain benefits from asset transferred, can prevent others
accessing same benefits.
- Satisfaction of obligations - Transfer of control over time or point in time based on specific
criteria.
These concepts change previous notions while providing consistency to evaluate revenue
contracts across jurisdictions and industries.
Implications
Key implications of the principles-based approach are:
- Earlier revenue recognition for certain hardware/software, telecom, construction contracts
satisfied over time.
- Separating performance obligations requires judgment, affects revenue
allocation/recognition pattern.
- Variable consideration estimates using expected value method increase estimation
complexity.
- Disclosures on judgments, contract balances, performance obligations, disaggregation of
revenue give comprehensive overview.
- Implementation requires cataloging all contract types/terms and assessing impact on
financials, business processes and controls.
- Greater financial reporting risk due to increased judgments and complexity in application
across diverse industries and contracts.
While enhancing comparability, the principles impose substantial costs to adopt and will
likely increase opportunities for earnings management. Robust implementation is key.
Industry Perspectives
Following issues are prevalent during implementation across key industries:
Hardware/Software: Revenue from licensing and support contracts requires assessment of
distinct performance obligations to recognize appropriately over time or point in time.
Telecom: Contract modifications, bundled pricing plans, customer acquisition costs
recognition differ substantially from previous treatment.
Construction: Assessing performance obligations, measuring progress to recognize revenue
over time as control transfers upon enhancing/creating assets.
Real Estate: Determining timing of control transfer for properties under development or sold
with post-closing involvement increases complexity.
Shipping/Transportation: Judging distinct performance obligations and timing of revenue
recognition for freight-forwarding contracts based on supply chain activities poses
challenges.
Adopting the principles consistently across complex, multi-element contracts demands
significant industry-specific application guidance and examples.
Transition Requirements
Entities can adopt the standards on either a full retrospective or modified retrospective basis:
- Full retrospective approach requires recasting all comparative periods presented in
accordance with new guidance. Poses significant effort but increases comparability.
- Modified retrospective approach applies to incomplete contracts on transition date, with
optionally chosen practical expedients. Comparability is reduced in initial year but
substantially less effort than full retrospective approach.
- Transitional reliefs may be elected including hindsight to determine performance
obligations, portfolio approach to similar contracts, no restatement of contract modifications
before transition date.
Careful evaluation of transition methods and practical expedients ensures optimum balance
between comparability and transition costs for various stakeholders.
Conclusion
The principles-based revenue recognition approach harmonizes guidance globally and
addresses inconsistencies prevalent earlier. While judgments, complexity and effort involved
are substantial, it provides a systematic framework to depict economic substance of
customer contracts. Consistent application and high-quality disclosures will enhance
transparency. Transitional reliefs facilitate smooth implementation. Overall, it raises financial
reporting standards through improved depiction of revenue streams and contract obligations.
With judicious application, it leads to more decision-useful information for investors.
Revenue is a crucial performance metric for businesses. Earlier revenue recognition
guidance was considered complex and lacked consistency across jurisdictions and
industries. To address these challenges, converged standards ASC 606 and IFRS 15 were
issued establishing a common set of principles for revenue recognition from contracts with
customers. This paper examines the five-step principles-based approach, core concepts and
new requirements introduced to recognize revenue at an amount reflecting expected
consideration for goods or services transferred. It analyzes implications for financial
reporting and key industry implementation challenges.
The Five-Step Model
The new standards follow a principles-based five-step model for revenue recognition:
1. Identify the contract with customer - A contract exists when collectability is probable,
parties are committed and enforceable rights/payment terms defined.
2. Identify separate performance obligations - Promised goods/services distinct within
context of contract terms and underlying economic factors.
3. Determine the transaction price - Fixed and variable consideration estimated at contract
inception, excluding amounts from financing components.
4. Allocate the transaction price - Price allocated to each distinct obligation based on
standalone selling prices of goods/services.
5. Recognize revenue as obligations are satisfied - Revenue recognized as control of
promised goods/services transfers to customer over time or at point in time.
This model provides a systematic framework to recognize revenue to depict transfer of
control of promised goods/services to customers in an amount reflecting expected value.
Core Concepts
The standards introduce significant new concepts including:
- Contracts - Binding agreements involving commercial substance between parties with
approved rights/obligations.
- Performance obligations - Distinct goods/services promised in contracts forming separate
units of account.
- Transaction price - Consideration expected in exchange, including variable amounts based
on most likely outcome.
- Control - Ability to direct use and obtain benefits from asset transferred, can prevent others
accessing same benefits.
- Satisfaction of obligations - Transfer of control over time or point in time based on specific
criteria.
These concepts change previous notions while providing consistency to evaluate revenue
contracts across jurisdictions and industries.
Implications
Key implications of the principles-based approach are:
- Earlier revenue recognition for certain hardware/software, telecom, construction contracts
satisfied over time.
- Separating performance obligations requires judgment, affects revenue
allocation/recognition pattern.
- Variable consideration estimates using expected value method increase estimation
complexity.
- Disclosures on judgments, contract balances, performance obligations, disaggregation of
revenue give comprehensive overview.
- Implementation requires cataloging all contract types/terms and assessing impact on
financials, business processes and controls.
- Greater financial reporting risk due to increased judgments and complexity in application
across diverse industries and contracts.
While enhancing comparability, the principles impose substantial costs to adopt and will
likely increase opportunities for earnings management. Robust implementation is key.
Industry Perspectives
Following issues are prevalent during implementation across key industries:
Hardware/Software: Revenue from licensing and support contracts requires assessment of
distinct performance obligations to recognize appropriately over time or point in time.
Telecom: Contract modifications, bundled pricing plans, customer acquisition costs
recognition differ substantially from previous treatment.
Construction: Assessing performance obligations, measuring progress to recognize revenue
over time as control transfers upon enhancing/creating assets.
Real Estate: Determining timing of control transfer for properties under development or sold
with post-closing involvement increases complexity.
Shipping/Transportation: Judging distinct performance obligations and timing of revenue
recognition for freight-forwarding contracts based on supply chain activities poses
challenges.
Adopting the principles consistently across complex, multi-element contracts demands
significant industry-specific application guidance and examples.
Transition Requirements
Entities can adopt the standards on either a full retrospective or modified retrospective basis:
- Full retrospective approach requires recasting all comparative periods presented in
accordance with new guidance. Poses significant effort but increases comparability.
- Modified retrospective approach applies to incomplete contracts on transition date, with
optionally chosen practical expedients. Comparability is reduced in initial year but
substantially less effort than full retrospective approach.
- Transitional reliefs may be elected including hindsight to determine performance
obligations, portfolio approach to similar contracts, no restatement of contract modifications
before transition date.
Careful evaluation of transition methods and practical expedients ensures optimum balance
between comparability and transition costs for various stakeholders.
Conclusion
The principles-based revenue recognition approach harmonizes guidance globally and
addresses inconsistencies prevalent earlier. While judgments, complexity and effort involved
are substantial, it provides a systematic framework to depict economic substance of
customer contracts. Consistent application and high-quality disclosures will enhance
transparency. Transitional reliefs facilitate smooth implementation. Overall, it raises financial
reporting standards through improved depiction of revenue streams and contract obligations.
With judicious application, it leads to more decision-useful information for investors.
Revenue is a crucial performance metric for businesses. Earlier revenue recognition
guidance was considered complex and lacked consistency across jurisdictions and
industries. To address these challenges, converged standards ASC 606 and IFRS 15 were
issued establishing a common set of principles for revenue recognition from contracts with
customers. This paper examines the five-step principles-based approach, core concepts and
new requirements introduced to recognize revenue at an amount reflecting expected
consideration for goods or services transferred. It analyzes implications for financial
reporting and key industry implementation challenges.
The Five-Step Model
The new standards follow a principles-based five-step model for revenue recognition:
1. Identify the contract with customer - A contract exists when collectability is probable,
parties are committed and enforceable rights/payment terms defined.
2. Identify separate performance obligations - Promised goods/services distinct within
context of contract terms and underlying economic factors.
3. Determine the transaction price - Fixed and variable consideration estimated at contract
inception, excluding amounts from financing components.
4. Allocate the transaction price - Price allocated to each distinct obligation based on
standalone selling prices of goods/services.
5. Recognize revenue as obligations are satisfied - Revenue recognized as control of
promised goods/services transfers to customer over time or at point in time.
This model provides a systematic framework to recognize revenue to depict transfer of
control of promised goods/services to customers in an amount reflecting expected value.
Core Concepts
The standards introduce significant new concepts including:
- Contracts - Binding agreements involving commercial substance between parties with
approved rights/obligations.
- Performance obligations - Distinct goods/services promised in contracts forming separate
units of account.
- Transaction price - Consideration expected in exchange, including variable amounts based
on most likely outcome.
- Control - Ability to direct use and obtain benefits from asset transferred, can prevent others
accessing same benefits.
- Satisfaction of obligations - Transfer of control over time or point in time based on specific
criteria.
These concepts change previous notions while providing consistency to evaluate revenue
contracts across jurisdictions and industries.
Implications
Key implications of the principles-based approach are:
- Earlier revenue recognition for certain hardware/software, telecom, construction contracts
satisfied over time.
- Separating performance obligations requires judgment, affects revenue
allocation/recognition pattern.
- Variable consideration estimates using expected value method increase estimation
complexity.
- Disclosures on judgments, contract balances, performance obligations, disaggregation of
revenue give comprehensive overview.
- Implementation requires cataloging all contract types/terms and assessing impact on
financials, business processes and controls.
- Greater financial reporting risk due to increased judgments and complexity in application
across diverse industries and contracts.
While enhancing comparability, the principles impose substantial costs to adopt and will
likely increase opportunities for earnings management. Robust implementation is key.
Industry Perspectives
Following issues are prevalent during implementation across key industries:
Hardware/Software: Revenue from licensing and support contracts requires assessment of
distinct performance obligations to recognize appropriately over time or point in time.
Telecom: Contract modifications, bundled pricing plans, customer acquisition costs
recognition differ substantially from previous treatment.
Construction: Assessing performance obligations, measuring progress to recognize revenue
over time as control transfers upon enhancing/creating assets.
Real Estate: Determining timing of control transfer for properties under development or sold
with post-closing involvement increases complexity.
Shipping/Transportation: Judging distinct performance obligations and timing of revenue
recognition for freight-forwarding contracts based on supply chain activities poses
challenges.
Adopting the principles consistently across complex, multi-element contracts demands
significant industry-specific application guidance and examples.
Transition Requirements
Entities can adopt the standards on either a full retrospective or modified retrospective basis:
- Full retrospective approach requires recasting all comparative periods presented in
accordance with new guidance. Poses significant effort but increases comparability.
- Modified retrospective approach applies to incomplete contracts on transition date, with
optionally chosen practical expedients. Comparability is reduced in initial year but
substantially less effort than full retrospective approach.
- Transitional reliefs may be elected including hindsight to determine performance
obligations, portfolio approach to similar contracts, no restatement of contract modifications
before transition date.
Careful evaluation of transition methods and practical expedients ensures optimum balance
between comparability and transition costs for various stakeholders.
Conclusion
The principles-based revenue recognition approach harmonizes guidance globally and
addresses inconsistencies prevalent earlier. While judgments, complexity and effort involved
are substantial, it provides a systematic framework to depict economic substance of
customer contracts. Consistent application and high-quality disclosures will enhance
transparency. Transitional reliefs facilitate smooth implementation. Overall, it raises financial
reporting standards through improved depiction of revenue streams and contract obligations.
With judicious application, it leads to more decision-useful information for investors.
Revenue is a crucial performance metric for businesses. Earlier revenue recognition
guidance was considered complex and lacked consistency across jurisdictions and
industries. To address these challenges, converged standards ASC 606 and IFRS 15 were
issued establishing a common set of principles for revenue recognition from contracts with
customers. This paper examines the five-step principles-based approach, core concepts and
new requirements introduced to recognize revenue at an amount reflecting expected
consideration for goods or services transferred. It analyzes implications for financial
reporting and key industry implementation challenges.
The Five-Step Model
The new standards follow a principles-based five-step model for revenue recognition:
1. Identify the contract with customer - A contract exists when collectability is probable,
parties are committed and enforceable rights/payment terms defined.
2. Identify separate performance obligations - Promised goods/services distinct within
context of contract terms and underlying economic factors.
3. Determine the transaction price - Fixed and variable consideration estimated at contract
inception, excluding amounts from financing components.
4. Allocate the transaction price - Price allocated to each distinct obligation based on
standalone selling prices of goods/services.
5. Recognize revenue as obligations are satisfied - Revenue recognized as control of
promised goods/services transfers to customer over time or at point in time.
This model provides a systematic framework to recognize revenue to depict transfer of
control of promised goods/services to customers in an amount reflecting expected value.
Core Concepts
The standards introduce significant new concepts including:
- Contracts - Binding agreements involving commercial substance between parties with
approved rights/obligations.
- Performance obligations - Distinct goods/services promised in contracts forming separate
units of account.
- Transaction price - Consideration expected in exchange, including variable amounts based
on most likely outcome.
- Control - Ability to direct use and obtain benefits from asset transferred, can prevent others
accessing same benefits.
- Satisfaction of obligations - Transfer of control over time or point in time based on specific
criteria.
These concepts change previous notions while providing consistency to evaluate revenue
contracts across jurisdictions and industries.
Implications
Key implications of the principles-based approach are:
- Earlier revenue recognition for certain hardware/software, telecom, construction contracts
satisfied over time.
- Separating performance obligations requires judgment, affects revenue
allocation/recognition pattern.
- Variable consideration estimates using expected value method increase estimation
complexity.
- Disclosures on judgments, contract balances, performance obligations, disaggregation of
revenue give comprehensive overview.
- Implementation requires cataloging all contract types/terms and assessing impact on
financials, business processes and controls.
- Greater financial reporting risk due to increased judgments and complexity in application
across diverse industries and contracts.
While enhancing comparability, the principles impose substantial costs to adopt and will
likely increase opportunities for earnings management. Robust implementation is key.
Industry Perspectives
Following issues are prevalent during implementation across key industries:
Hardware/Software: Revenue from licensing and support contracts requires assessment of
distinct performance obligations to recognize appropriately over time or point in time.
Telecom: Contract modifications, bundled pricing plans, customer acquisition costs
recognition differ substantially from previous treatment.
Construction: Assessing performance obligations, measuring progress to recognize revenue
over time as control transfers upon enhancing/creating assets.
Real Estate: Determining timing of control transfer for properties under development or sold
with post-closing involvement increases complexity.
Shipping/Transportation: Judging distinct performance obligations and timing of revenue
recognition for freight-forwarding contracts based on supply chain activities poses
challenges.
Adopting the principles consistently across complex, multi-element contracts demands
significant industry-specific application guidance and examples.
Transition Requirements
Entities can adopt the standards on either a full retrospective or modified retrospective basis:
- Full retrospective approach requires recasting all comparative periods presented in
accordance with new guidance. Poses significant effort but increases comparability.
- Modified retrospective approach applies to incomplete contracts on transition date, with
optionally chosen practical expedients. Comparability is reduced in initial year but
substantially less effort than full retrospective approach.
- Transitional reliefs may be elected including hindsight to determine performance
obligations, portfolio approach to similar contracts, no restatement of contract modifications
before transition date.
Careful evaluation of transition methods and practical expedients ensures optimum balance
between comparability and transition costs for various stakeholders.
Conclusion
The principles-based revenue recognition approach harmonizes guidance globally and
addresses inconsistencies prevalent earlier. While judgments, complexity and effort involved
are substantial, it provides a systematic framework to depict economic substance of
customer contracts. Consistent application and high-quality disclosures will enhance
transparency. Transitional reliefs facilitate smooth implementation. Overall, it raises financial
reporting standards through improved depiction of revenue streams and contract obligations.
With judicious application, it leads to more decision-useful information for investors.
Revenue is a crucial performance metric for businesses. Earlier revenue recognition
guidance was considered complex and lacked consistency across jurisdictions and
industries. To address these challenges, converged standards ASC 606 and IFRS 15 were
issued establishing a common set of principles for revenue recognition from contracts with
customers. This paper examines the five-step principles-based approach, core concepts and
new requirements introduced to recognize revenue at an amount reflecting expected
consideration for goods or services transferred. It analyzes implications for financial
reporting and key industry implementation challenges.
The Five-Step Model
The new standards follow a principles-based five-step model for revenue recognition:
1. Identify the contract with customer - A contract exists when collectability is probable,
parties are committed and enforceable rights/payment terms defined.
2. Identify separate performance obligations - Promised goods/services distinct within
context of contract terms and underlying economic factors.
3. Determine the transaction price - Fixed and variable consideration estimated at contract
inception, excluding amounts from financing components.
4. Allocate the transaction price - Price allocated to each distinct obligation based on
standalone selling prices of goods/services.
5. Recognize revenue as obligations are satisfied - Revenue recognized as control of
promised goods/services transfers to customer over time or at point in time.
This model provides a systematic framework to recognize revenue to depict transfer of
control of promised goods/services to customers in an amount reflecting expected value.
Core Concepts
The standards introduce significant new concepts including:
- Contracts - Binding agreements involving commercial substance between parties with
approved rights/obligations.
- Performance obligations - Distinct goods/services promised in contracts forming separate
units of account.
- Transaction price - Consideration expected in exchange, including variable amounts based
on most likely outcome.
- Control - Ability to direct use and obtain benefits from asset transferred, can prevent others
accessing same benefits.
- Satisfaction of obligations - Transfer of control over time or point in time based on specific
criteria.
These concepts change previous notions while providing consistency to evaluate revenue
contracts across jurisdictions and industries.
Implications
Key implications of the principles-based approach are:
- Earlier revenue recognition for certain hardware/software, telecom, construction contracts
satisfied over time.
- Separating performance obligations requires judgment, affects revenue
allocation/recognition pattern.
- Variable consideration estimates using expected value method increase estimation
complexity.
- Disclosures on judgments, contract balances, performance obligations, disaggregation of
revenue give comprehensive overview.
- Implementation requires cataloging all contract types/terms and assessing impact on
financials, business processes and controls.
- Greater financial reporting risk due to increased judgments and complexity in application
across diverse industries and contracts.
While enhancing comparability, the principles impose substantial costs to adopt and will
likely increase opportunities for earnings management. Robust implementation is key.
Industry Perspectives
Following issues are prevalent during implementation across key industries:
Hardware/Software: Revenue from licensing and support contracts requires assessment of
distinct performance obligations to recognize appropriately over time or point in time.
Telecom: Contract modifications, bundled pricing plans, customer acquisition costs
recognition differ substantially from previous treatment.
Construction: Assessing performance obligations, measuring progress to recognize revenue
over time as control transfers upon enhancing/creating assets.
Real Estate: Determining timing of control transfer for properties under development or sold
with post-closing involvement increases complexity.
Shipping/Transportation: Judging distinct performance obligations and timing of revenue
recognition for freight-forwarding contracts based on supply chain activities poses
challenges.
Adopting the principles consistently across complex, multi-element contracts demands
significant industry-specific application guidance and examples.
Transition Requirements
Entities can adopt the standards on either a full retrospective or modified retrospective basis:
- Full retrospective approach requires recasting all comparative periods presented in
accordance with new guidance. Poses significant effort but increases comparability.
- Modified retrospective approach applies to incomplete contracts on transition date, with
optionally chosen practical expedients. Comparability is reduced in initial year but
substantially less effort than full retrospective approach.
- Transitional reliefs may be elected including hindsight to determine performance
obligations, portfolio approach to similar contracts, no restatement of contract modifications
before transition date.
Careful evaluation of transition methods and practical expedients ensures optimum balance
between comparability and transition costs for various stakeholders.
Conclusion
The principles-based revenue recognition approach harmonizes guidance globally and
addresses inconsistencies prevalent earlier. While judgments, complexity and effort involved
are substantial, it provides a systematic framework to depict economic substance of
customer contracts. Consistent application and high-quality disclosures will enhance
transparency. Transitional reliefs facilitate smooth implementation. Overall, it raises financial
reporting standards through improved depiction of revenue streams and contract obligations.
With judicious application, it leads to more decision-useful information for investors.
Revenue is a crucial performance metric for businesses. Earlier revenue recognition
guidance was considered complex and lacked consistency across jurisdictions and
industries. To address these challenges, converged standards ASC 606 and IFRS 15 were
issued establishing a common set of principles for revenue recognition from contracts with
customers. This paper examines the five-step principles-based approach, core concepts and
new requirements introduced to recognize revenue at an amount reflecting expected
consideration for goods or services transferred. It analyzes implications for financial
reporting and key industry implementation challenges.
The Five-Step Model
The new standards follow a principles-based five-step model for revenue recognition:
1. Identify the contract with customer - A contract exists when collectability is probable,
parties are committed and enforceable rights/payment terms defined.
2. Identify separate performance obligations - Promised goods/services distinct within
context of contract terms and underlying economic factors.
3. Determine the transaction price - Fixed and variable consideration estimated at contract
inception, excluding amounts from financing components.
4. Allocate the transaction price - Price allocated to each distinct obligation based on
standalone selling prices of goods/services.
5. Recognize revenue as obligations are satisfied - Revenue recognized as control of
promised goods/services transfers to customer over time or at point in time.
This model provides a systematic framework to recognize revenue to depict transfer of
control of promised goods/services to customers in an amount reflecting expected value.
Core Concepts
The standards introduce significant new concepts including:
- Contracts - Binding agreements involving commercial substance between parties with
approved rights/obligations.
- Performance obligations - Distinct goods/services promised in contracts forming separate
units of account.
- Transaction price - Consideration expected in exchange, including variable amounts based
on most likely outcome.
- Control - Ability to direct use and obtain benefits from asset transferred, can prevent others
accessing same benefits.
- Satisfaction of obligations - Transfer of control over time or point in time based on specific
criteria.
These concepts change previous notions while providing consistency to evaluate revenue
contracts across jurisdictions and industries.
Implications
Key implications of the principles-based approach are:
- Earlier revenue recognition for certain hardware/software, telecom, construction contracts
satisfied over time.
- Separating performance obligations requires judgment, affects revenue
allocation/recognition pattern.
- Variable consideration estimates using expected value method increase estimation
complexity.
- Disclosures on judgments, contract balances, performance obligations, disaggregation of
revenue give comprehensive overview.
- Implementation requires cataloging all contract types/terms and assessing impact on
financials, business processes and controls.
- Greater financial reporting risk due to increased judgments and complexity in application
across diverse industries and contracts.
While enhancing comparability, the principles impose substantial costs to adopt and will
likely increase opportunities for earnings management. Robust implementation is key.
Industry Perspectives
Following issues are prevalent during implementation across key industries:
Hardware/Software: Revenue from licensing and support contracts requires assessment of
distinct performance obligations to recognize appropriately over time or point in time.
Telecom: Contract modifications, bundled pricing plans, customer acquisition costs
recognition differ substantially from previous treatment.
Construction: Assessing performance obligations, measuring progress to recognize revenue
over time as control transfers upon enhancing/creating assets.
Real Estate: Determining timing of control transfer for properties under development or sold
with post-closing involvement increases complexity.
Shipping/Transportation: Judging distinct performance obligations and timing of revenue
recognition for freight-forwarding contracts based on supply chain activities poses
challenges.
Adopting the principles consistently across complex, multi-element contracts demands
significant industry-specific application guidance and examples.
Transition Requirements
Entities can adopt the standards on either a full retrospective or modified retrospective basis:
- Full retrospective approach requires recasting all comparative periods presented in
accordance with new guidance. Poses significant effort but increases comparability.
- Modified retrospective approach applies to incomplete contracts on transition date, with
optionally chosen practical expedients. Comparability is reduced in initial year but
substantially less effort than full retrospective approach.
- Transitional reliefs may be elected including hindsight to determine performance
obligations, portfolio approach to similar contracts, no restatement of contract modifications
before transition date.
Careful evaluation of transition methods and practical expedients ensures optimum balance
between comparability and transition costs for various stakeholders.
Conclusion
The principles-based revenue recognition approach harmonizes guidance globally and
addresses inconsistencies prevalent earlier. While judgments, complexity and effort involved
are substantial, it provides a systematic framework to depict economic substance of
customer contracts. Consistent application and high-quality disclosures will enhance
transparency. Transitional reliefs facilitate smooth implementation. Overall, it raises financial
reporting standards through improved depiction of revenue streams and contract obligations.
With judicious application, it leads to more decision-useful information for investors.
Revenue is a crucial performance metric for businesses. Earlier revenue recognition
guidance was considered complex and lacked consistency across jurisdictions and
industries. To address these challenges, converged standards ASC 606 and IFRS 15 were
issued establishing a common set of principles for revenue recognition from contracts with
customers. This paper examines the five-step principles-based approach, core concepts and
new requirements introduced to recognize revenue at an amount reflecting expected
consideration for goods or services transferred. It analyzes implications for financial
reporting and key industry implementation challenges.
The Five-Step Model
The new standards follow a principles-based five-step model for revenue recognition:
1. Identify the contract with customer - A contract exists when collectability is probable,
parties are committed and enforceable rights/payment terms defined.
2. Identify separate performance obligations - Promised goods/services distinct within
context of contract terms and underlying economic factors.
3. Determine the transaction price - Fixed and variable consideration estimated at contract
inception, excluding amounts from financing components.
4. Allocate the transaction price - Price allocated to each distinct obligation based on
standalone selling prices of goods/services.
5. Recognize revenue as obligations are satisfied - Revenue recognized as control of
promised goods/services transfers to customer over time or at point in time.
This model provides a systematic framework to recognize revenue to depict transfer of
control of promised goods/services to customers in an amount reflecting expected value.
Core Concepts
The standards introduce significant new concepts including:
- Contracts - Binding agreements involving commercial substance between parties with
approved rights/obligations.
- Performance obligations - Distinct goods/services promised in contracts forming separate
units of account.
- Transaction price - Consideration expected in exchange, including variable amounts based
on most likely outcome.
- Control - Ability to direct use and obtain benefits from asset transferred, can prevent others
accessing same benefits.
- Satisfaction of obligations - Transfer of control over time or point in time based on specific
criteria.
These concepts change previous notions while providing consistency to evaluate revenue
contracts across jurisdictions and industries.
Implications
Key implications of the principles-based approach are:
- Earlier revenue recognition for certain hardware/software, telecom, construction contracts
satisfied over time.
- Separating performance obligations requires judgment, affects revenue
allocation/recognition pattern.
- Variable consideration estimates using expected value method increase estimation
complexity.
- Disclosures on judgments, contract balances, performance obligations, disaggregation of
revenue give comprehensive overview.
- Implementation requires cataloging all contract types/terms and assessing impact on
financials, business processes and controls.
- Greater financial reporting risk due to increased judgments and complexity in application
across diverse industries and contracts.
While enhancing comparability, the principles impose substantial costs to adopt and will
likely increase opportunities for earnings management. Robust implementation is key.
Industry Perspectives
Following issues are prevalent during implementation across key industries:
Hardware/Software: Revenue from licensing and support contracts requires assessment of
distinct performance obligations to recognize appropriately over time or point in time.
Telecom: Contract modifications, bundled pricing plans, customer acquisition costs
recognition differ substantially from previous treatment.
Construction: Assessing performance obligations, measuring progress to recognize revenue
over time as control transfers upon enhancing/creating assets.
Real Estate: Determining timing of control transfer for properties under development or sold
with post-closing involvement increases complexity.
Shipping/Transportation: Judging distinct performance obligations and timing of revenue
recognition for freight-forwarding contracts based on supply chain activities poses
challenges.
Adopting the principles consistently across complex, multi-element contracts demands
significant industry-specific application guidance and examples.
Transition Requirements
Entities can adopt the standards on either a full retrospective or modified retrospective basis:
- Full retrospective approach requires recasting all comparative periods presented in
accordance with new guidance. Poses significant effort but increases comparability.
- Modified retrospective approach applies to incomplete contracts on transition date, with
optionally chosen practical expedients. Comparability is reduced in initial year but
substantially less effort than full retrospective approach.
- Transitional reliefs may be elected including hindsight to determine performance
obligations, portfolio approach to similar contracts, no restatement of contract modifications
before transition date.
Careful evaluation of transition methods and practical expedients ensures optimum balance
between comparability and transition costs for various stakeholders.
Conclusion
The principles-based revenue recognition approach harmonizes guidance globally and
addresses inconsistencies prevalent earlier. While judgments, complexity and effort involved
are substantial, it provides a systematic framework to depict economic substance of
customer contracts. Consistent application and high-quality disclosures will enhance
transparency. Transitional reliefs facilitate smooth implementation. Overall, it raises financial
reporting standards through improved depiction of revenue streams and contract obligations.
With judicious application, it leads to more decision-useful information for investors.