Official sponsor of Oracle-NetSuite SuiteWorld 2025 in Las Vegas, October 6–9! 🎉.

ASC 606 – The International Revenue Recognition Standard At a Glance

Whichever industry we fall into, the key business and profitability indicator is always looked up-to the Revenue generated and gained for the period.

Different business, different types of revenue and with this comes in the added responsibility of recognition of revenue.

To have a uniformity of reporting revenue across business lines, comes the requirement of having an international reporting standard in place.

Thus, for Revenue it is ASC 606 – a single comprehensive model for entities to use in accounting for revenue arising from contracts from customers.

This ASC 606 is a 5-step model making revenue recognition and allocation more streamlined and effective for stakeholders to trust the business and skip from fraudulent business practices of revenue inflation.

ASC 606 –The Five Step Model

undefined

Step 1 – Identify the contract with the Customer

ASC 606 defines contract to be any form of agreement between two or more parties that creates enforceable rights and obligations between them.

This emphasizes the contract to have min 2 identifiable parties where the monetary payment terms are identifiable on exchange of goods/services as determined.

Any change in price or scope of this contract leads to creation of a new contract between the parties.

Step 2 – Identify the Performance Obligations in the Contract

Identify what calls for completion of service against the order generated by the customer.

It could be actual delivery of goods, completion of training activities for the staff post-delivery or it could just be an actual dispatch of goods irrespective the delivery of goods happened or not.

First understand and identify the deliverables and second whether each deliverable should be considered separate or not.

Determine this with the customer what calls a completion of service and mention the same exclusively in the contract.

Step 3 – Determine the Transaction Price

The transaction price is the amount of consideration (e.g. payment or contract revenue) to which a reporting organization expects to be entitled to in exchange for transferring promised goods or services to a customer. This amount excludes third party obligations like sales tax.

However, it should take into consideration discounts, incentives, rebates and other price concessions.

Step 4 – Allocation of Transaction Price As per the Performance Obligation

This is a real accounting step whereby all the first three steps are put into effect, and we allocate the Transaction price as per decided in the performance obligations.

This step is all about mapping fair values to your goods/services exchanged as per the contract in your books of account.

Step 5 – Recognition of Revenue

Revenue is reported when or as it satisfies the performance obligation by transferring the promised goods or service to a customer. Obligations can be satisfied point-in-time or overtime as per what is agreed by the parties to the contract.

Hence amount of revenue recognized in a period = value of services obliged at that stated period.

Thus ASC 606 is an evidence-based reporting standard providing accuracy on amount timing and uncertainty of revenue and related cash flows.

It clearly outlines contracts for how organizations must recognize revenue leading to better SOX compliance across industries including public, private and non-profit entities.

Trending Articles

Guide to Consulting Technology Services: Trends and Strategies 2026
Automating Work Orders in NetSuite Using Custom Suitelets
SuiteWorld 2021: OdeCloud's Top 3 Takeaways from Day 1
Automated Intercompany Eliminations: Simplify Your Close Process with NetSuite
OdeCloud Aiming to Become Leader in NetSuite-Related Content

Trek Travel Streamlines Travel Protection Integration with OdeCloud’s experts

Looking to streamline your operations with more automations? Keith shares an OdeCloud project.

#netsuite

#integrations

Project Outcomes

This new integration system transformed our travel protection service.

  1. Efficiency Gains: Completely automated the process, eliminating the need for monthly roster reconciliation.
  2. Enhanced Guest Experience: Guests benefited from a smoother booking process with transparent travel protection options tailored to their needs.
  3. Accuracy in Pricing: The integration ensured precise calculations based on complex variables.
  4. Scalability: The system can easily accommodate future growth and changes in travel protection offerings.

Background

Our company offers guests the option to protect their travel investments through a travel protection plan. This service is crucial, as it provides coverage in cases where guests need to cancel their trips due to unforeseen circumstances such as illness or emergencies. However, the process for managing this service was previously cumbersome and inefficient, requiring manual coordination and reconciliation with the travel protection partner.

Challenge

We needed a seamless integration within NetSuite to handle complex calculations for travel protection costs. The solution needed to account for multiple variables, including:
Guest-specific factors such as age and location.
Travel details like destination, total cost, and type of coverage (e.g., pre-trip hotels, post-trip hotels, flights).
Dynamic pricing calculations based on these variables.

Before partnering with OdeCloud, the process was manual and error-prone, involving monthly exchanges of rosters between our team and the travel protection provider. This created inefficiencies and delayed customer service.

Solution

OdeCloud worked with us to design and implement a fully integrated travel protection solution within NetSuite. Key features of the solution included:


1. API Integration: OdeCloud enabled real-time communication with the travel protection partner’s API. This allowed us to dynamically calculate the cost of travel protection based on the guest’s specific details.
2. Seamless Booking Experience: The integration allowed the travel protection cost to be automatically added as a line item to guest bookings within NetSuite.
3. Flexible Adjustments: Guests could easily add or cancel travel protection directly through NetSuite without requiring interaction with third-party systems.
4. Eliminating Manual Processes: The previously manual reconciliation process was replaced with automated inline API transactions, eliminating errors and saving significant time.

Conclusion

This integration is one of the most impactful projects we’ve undertaken, and it holds a special place in our transformation journey. With OdeCloud’s expertise, we achieved a solution that not only streamlined operations but also elevated the guest experience. This project exemplifies the power of technology in solving complex business challenges and enhancing customer service.