The revenue recognition is an accounting principle that asserts that revenue must be recognized as it is earned. The focus is on recognizing revenue at the time goods or services are delivered to customers, as opposed to when payment is made. The principle is regulated by similar standards in both the U.S. and internationally.
For SaaS companies and service providers expanding between the United States and Brazil, revenue recognition can quickly become a complex topic. While U.S. GAAP (ASC 606) and Brazilian GAAP (CPC 47/IFRS 15) are built on the same five-step framework, the way the rules play out in practice isn’t always identical. Understanding these nuances is critical for finance leaders, controllers, and founders navigating cross-border operations.
One of the biggest areas of difference lies in implementation costs. Under U.S. GAAP, many cloud implementation expenses can be capitalized and amortized over the contract term. By contrast, Brazilian and IFRS rules usually require these costs to be expensed immediately—unless they result in a separable intangible asset.
Another key consideration is how to classify SaaS versus software licenses. SaaS arrangements are almost always recognized over time, reflecting the ongoing nature of service delivery. Licenses, however, can fall into two categories: point-in-time recognition (when control of the software transfers) or over-time recognition (when updates or access rights significantly affect utility). In Brazil, auditors will pay particular attention to documentation to ensure the classification supports both accounting and tax treatments.
Finally, Brazilian taxes add an extra layer of complexity. Levies such as PIS, COFINS, ISS, and withholdings (IRRF/CSRF) directly impact revenue presentation and cash flow. Companies must make sure their contracts clearly define whether values are gross or net, as this affects how revenue is reported and how cash is collected.
Despite these differences, the core principles remain the same. Both standards require identifying the contract and performance obligations, determining the transaction price, allocating it appropriately, and recognizing revenue either over time or at a point in time. Setup or activation fees are rarely recognized upfront and are generally deferred.
ASC 606 and CPC 47 usually result in similar revenue timing, but companies must carefully manage cost treatment, tax rules, and documentation to ensure compliance in both jurisdictions. For SaaS and service businesses aiming to scale internationally, having clear policies and audit-ready documentation is not just good practice—it’s a strategic necessity.
To know more about the differences in revenue recognition, and other aspects of business’ accounting, contact our specialists at Drummond Advisors! #LetsDoItTogether!
Written by Paola Von Atzingen, from the Drummond Advisors team