Browse 5 Gruv blog articles tagged Asc 606. Tax filings, invoicing rules, and treaty guidance for cross-border operators.
If you handle commissions or similar deal costs, start with two GAAP tests: is the cost incremental to obtaining a customer contract, and do you expect to recover it? If either answer is no, expense treatment is usually the right starting point.
Many global subscription platforms can start from one operating assumption: IFRS 15 and ASC 606 are aligned enough that you may be able to standardize much of your revenue recognition governance. They are not so aligned that every judgment call can be treated as interchangeable. The goal is practical: cut duplicate policy work without letting a real accounting difference or contract nuance slip into close week.
A discounted subscription bundle can put one amount on an invoice while producing several revenue schedules. The invoice total does not tell finance how much belongs to software access, a distinct training service or another promised deliverable. Start with the actual promises and supported stand-alone selling prices, then calculate the allocation and recognize each amount when or as its obligation is satisfied.
ASC 606 is not just a compliance topic for subscription companies. It is a pricing and packaging constraint that affects how you sell, how you report, and how much confidence people can place in your financial statements. The practical goal of this guide is simple: turn subscription revenue recognition under ASC 606 from accounting language into decision rules you can use before a launch, not after a close problem.
Under ASC 606, revenue follows the transfer of promised goods or services rather than the date money arrives. A customer prepayment for future service creates a contract liability, commonly called deferred revenue. Cash, billings, receivables and recognized revenue therefore need separate records.
