The Accounting Question Nobody Asks Until It's Urgent

When an ISV starts generating meaningful marketplace revenue, the finance team inevitably raises a question that the sales and partnerships team never considered: How do we recognize this revenue?

The Core Question: Gross vs. Net

When a customer pays $100,000 through AWS Marketplace and AWS takes a 3% commission, does your company recognize $100,000 in revenue (gross) or $97,000 (net)?

The answer matters enormously for financial reporting. Under ASC 606, the determining factor is whether you are the principal (gross) or an agent (net) in the transaction.

When You're the Principal (Gross Recognition)

You recognize the full transaction amount as revenue and record the marketplace commission as a cost of revenue. This applies when you control the product or service before it is transferred to the customer, you set the pricing, and you bear inventory risk.

When You're the Agent (Net Recognition)

You recognize only the net amount (after commission) as revenue. This applies when the marketplace controls the customer relationship and the pricing, and you are essentially a supplier to the marketplace.

For most SaaS ISVs on cloud marketplaces, gross recognition is appropriate because you control the product, set pricing (especially through private offers), and bear the performance obligation.

Payment Timing and Cash Flow

AWS pays on Net 60. Azure pays on Net 30–45. GCP pays on Net 30–45. This creates cash flow timing differences that finance teams need to model, especially for companies transitioning from direct sales (typically Net 30) to marketplace channels.

Multi-Year Contracts and Installment Billing

A 3-year private offer with monthly installments creates a complex revenue recognition pattern. Under ASC 606, you recognize revenue as the performance obligation is satisfied (typically ratably over the contract term), regardless of the payment schedule.

Commission Capitalization (ASC 340-40)

If your sales team earns commission on marketplace deals, those commissions may need to be capitalized and amortized under ASC 340-40 if the expected benefit period exceeds one year.

Multi-Cloud Reconciliation

When you transact on AWS, Azure, and GCP simultaneously, you're reconciling three separate payout schedules, three different reporting formats, and three different commission structures against a single revenue ledger. This is where manual processes break.

Practical Recommendations

1. Establish your gross vs. net position with your auditor before marketplace revenue becomes material
2. Build a reconciliation process that maps marketplace payouts to your internal revenue records
3. Track marketplace commissions as a separate cost-of-revenue line item
4. Model the cash flow impact of marketplace payout timelines
5. Use a unified platform to consolidate multi-cloud revenue data

Automatum provides unified analytics across all three marketplaces, making revenue reconciliation straightforward. Visit automatum.io to learn how we help finance teams manage marketplace revenue.