Browse 9 Gruv blog articles tagged Revenue Recognition. Payout rails, FX, reconciliation, and platform money-movement playbooks.
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.
Choosing accounting software for a payment platform is a controls and integration decision first, not just a General Ledger feature comparison. If your product depends on recurring billing, payment collection, and reporting, a tool that looks complete at the GL surface can still leave rollout gaps. Revenue treatment and exception handling should be tested early.
If you collect cash upfront for an annual plan, you have not automatically earned revenue. For a platform selling prepaid subscriptions across markets, the gap between cash receipt and service delivery is a control issue, not just an accounting entry.
A marketplace can earn revenue before the buyer pays. To post it correctly, separate the platform’s performance, its right to consideration, the invoice and cash collection. Those facts determine the revenue amount, the balance-sheet account and the later clearing entry.
For platform operators, cash timing often does not match accounting timing, so payout date should not be your default anchor for revenue or payout-cost recognition.
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.
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.
Multi-currency SaaS pricing needs a clear customer price and a traceable path to cash. Separate the currency shown and charged from settlement and bank receipt before adding markets.
For accrual financial statements applying ASC 606 or IFRS 15, a client payment received before the related promised goods or services transfer normally creates a contract liability. This guide addresses that book treatment; cash-basis and tax rules can differ.
