App Store Commissions: An ASC 606 Accounting Guide

December 30, 2025
Cody Leach, CPA
Finance

Get clear on app store commissions and ASC 606 compliance. Learn how to account for Apple App Store and Google Play sales with practical, step-by-step guidance.

Your top-line revenue from the App Store is only half the story. To understand your true profitability, you need to dig into the complex web of costs that come with selling on platforms like Apple and Google. The app store commissions aren't a simple flat fee; they vary based on your earnings, subscription length, and even your customer's location. Without a clear process for accounting for these fees, along with taxes and refunds, your margin analysis is based on guesswork. This guide will show you how to work with the financial reports from both platforms to build accurate journal entries and gain a clearer view of your actual revenue streams.

Introduction

Mastering subscription revenue accounting in the digital marketplace is challenging for finance professionals. Platforms like Apple App Store and Google Play add complexity with unique data extraction and opaque and incomplete reports. This guide simplifies the process with platform-specific insights, step-by-step instructions for data extraction, journal entry formulation, and margin analysis. Use these strategies to ensure ASC 606/GAAP compliance, streamline accounting, and gain valuable insights into subscription revenue streams across digital ecosystems.

Apple App Store

Apple holds the data needed to do accounting for subscription revenue and the order-to-cash cycle in 2 reports (Summary Sales and Financial Report) and requires understanding your Apple Contractual Obligations. 

Apple maintains only a portion of the necessary data to record revenue according to ASC 606 correctly. Some deficiencies on the standard reports available to the accounting team through the App Store UI include:

  1. VAT/GST Revenue Gross Up and Withholding - The Apple Summary Sales Dashboard includes VAT/GST collections on behalf of your company. As such, if this is being recorded into revenue, a manual adjustment for an estimate of this tax needs to be made each month and trued up as payments are received.
  2. Subscriber Level Granularity - The Apple Summary Sales and Financial Transaction Reports do not contain subscriber level detail nor a link to reconcile sales/refunds to payouts. This data only lives within the API. If you need this level of granularity - automating with HubiFi is the only option and happy to chat. 
  3. Foreign Exchange - The data needed to calculate accurate FX Gain and Loss does not exist in the Summary Sales and Financial Transactions reports (the direct comparison of the sale and payment amount is not available.)  If you need this level of granularity - automating with HubiFi is the only option and happy to chat. 

This guide will walk through how to calculate the revenue recognition as closely as possible manually. 

Data Extraction

To compile all necessary data for as accurate accounting as possible, the Summary Sales and Financial reports need to be downloaded from Apple’s website. They have not been changed in almost ten years, and Apple’s Customer Support does not generally respond to queries about the reports. 

Understanding Apple App Store Commissions

Before we get into the weeds of Apple’s financial reports, let’s talk about the fees. Understanding Apple’s commission structure is the first step to accurately reconciling your revenue. These fees directly impact your net proceeds, and knowing the rules can help you forecast your finances more effectively. Apple has a few different tiers and programs, so the percentage they take isn't always the same. It depends on your total earnings, the type of sale (like a one-time purchase versus a subscription), and how long a customer has been subscribed. Let's break down the key commission rates you need to be aware of.

Standard Commission Rate and Developer Fee

For most developers, the journey begins with two primary costs: the standard commission on sales and the annual fee to keep your account active. These are the baseline expenses you'll encounter when selling on the App Store, forming the foundation of your cost structure. It's essential to factor both into your financial projections from day one to get a clear picture of your potential profitability. While one is a percentage of your sales, the other is a fixed cost, and both play a significant role in your overall financial health on the platform.

The 30% Standard Rate

Apple's default commission is a straightforward 30% cut. This rate applies to the sale of paid apps, any in-app purchases your users make, and the first year of most subscriptions. So, for every dollar you earn through these channels, Apple retains 30 cents. This has been the industry standard for years and is the baseline you should use for initial financial modeling. It’s a significant portion of your gross revenue, which is why understanding the exceptions and programs that can lower this rate is so important for maximizing your take-home pay and ensuring your revenue recognition is precise.

Annual Developer Program Fee

In addition to the commission on sales, you must be a member of the Apple Developer Program to distribute apps on the App Store. This membership comes with an annual fee, which is typically $99 per year for individuals and most organizations. While it's not a transaction-based fee, it's a fixed operational cost you need to account for in your budget. Think of it as the price of admission to access Apple's massive global audience and the tools needed to build and maintain your app. This fee is constant regardless of your sales volume, making it a predictable expense in your financial planning.

The App Store Small Business Program

To support smaller developers, Apple introduced the App Store Small Business Program. If your app's proceeds are $1 million or less in a calendar year, you can qualify for a reduced commission rate of just 15%. This program is a game-changer, as it allows you to reinvest more of your earnings back into your business for growth and innovation. If your earnings surpass the $1 million threshold, the standard 30% rate applies for the remainder of the year. However, you can re-qualify for the 15% rate in a future year if your proceeds drop back below the threshold, offering valuable flexibility for growing businesses.

Subscription Commission Rates

The commission structure for subscriptions has a unique and beneficial twist. While the standard 30% rate applies to a subscriber's first year, Apple rewards you for customer retention. After a subscriber completes one full year of service, the commission rate on all their subsequent payments drops to 15%. This applies to auto-renewing subscriptions processed through Apple's in-app purchase system. This policy incentivizes developers to build long-term relationships with their customers, as retaining a subscriber for more than a year directly improves your profit margins on that user. It's a critical detail for any subscription-based business trying to build a sustainable revenue model.

Navigating Apple's Financial Reports

Now that you understand the commission structure, the next step is to see how these numbers appear in Apple's financial reports. This is where things can get tricky. Apple provides a few different reports, primarily the Summary Sales Report and the Financial Report, but they don't always make it easy to connect the dots. For example, the reports often bundle transactions, making it difficult to trace a single sale from gross revenue to the final net payout, especially when factoring in different commission rates, taxes like VAT/GST, and foreign exchange fluctuations. You might see your total sales, but reconciling that against the 15% vs. 30% commission rates or identifying which subscribers have crossed the one-year threshold requires careful analysis and often manual calculations.

This lack of granular detail is a common frustration for finance teams. The standard reports don't provide subscriber-level data, which is essential for true ASC 606 compliance and detailed margin analysis. You can't easily see the journey of an individual subscriber or reconcile specific sales to their corresponding payouts. This is why many high-volume businesses turn to automated solutions. A system like HubiFi can connect directly to the App Store API to pull the raw, detailed data that isn't available in the standard reports. This allows for precise, automated revenue recognition and gives you the clarity needed to make strategic decisions without spending days buried in spreadsheets.

Summary Sales Report 

The Apple Summary Sales Report is highly opaque, but it contains the needed information to do subscription revenue accounting except for settlement entries (which are on the Financial Report). 

Some nuances to keep in mind about the Apple Summary Report to do ASC 606 accounting:

  1. This is a daily report, though it can be run monthly.
  2. No unique identifiers - Subscription transactions are aggregated by date and stock-keeping unit (SKU). At this time, Apple does not provide transaction-level reporting, and it is not possible to split transactions into individual invoices and line items. As such, a unique identifier has to be created through concatenation and use of the row number, SKU, and report date.
  3. Implicit fees - Apple fees have to be derived. Instead of an actual fee amount or %, they provide a “Proceeds Reason” (Rate After One Year or NULL) - and you have to determine what % it is based on your agreement (typically 30% in year one, 15% thereafter, but could be different depending on your organization). 
  4. No direct connection between Subscriptions and related Refunds if issued. This makes getting direct allocation for reversing/offsetting subscription revenue difficult.
  5. Developer proceeds/costs must be inferred: proceedAmount = Developer Proceeds * Units.
  6. To determine if the line is a Sale vs. Refund, it is more accurate to follow that the customer price field >= 0 is a sale, and < 0 is a refund (rather than the Sales / Return flag on the report)
  7. No Bad Debt: Only successfully paid subscriptions are populated on the report, so bad debt isn’t a concept for Apple transactions in this regard. 
  8. Apple limits data retention to 12 months. 
  9. Backdated Summary Sales Reports: As of 1/1/24 - Apple began backdating the summary sales reports for additional sales and refunds. As such, if the report reconciles for, say, January 2024, if you pull down the January report again in March and re-reconcile, there is a chance that new sales were added or refunds reversed without notification. This can be up to 10-15% of adjustments to the past month’s revenues from Apple. 

Financial Report

  1. This is a monthly report that comes out 4-5 days after the last day of the month. This makes it impossible to reconcile your cash account until then, but you can get close using the Summary Sales Report data.
  2. The Settlement Date for accounting has to be inferred from the settlement date on the report. Apple settles 35 days after the settlement date on the report. Apple’s Settlement Policy can support this in the App Store Agreement.
  3. To determine if the line is a Settlement vs. Refund, it is more accurate to follow that customer price >/= 0 is a sale, and < 0 is a refund (rather than the Sales / Return flag on the report)

Accounting - Journal Entries

Summary Sales Report

Journal Entries:

  • Revenue Deferral: Dr. Accounts Receivable (AR), Cr. Deferred Revenue
  • Revenue Recognition: Dr. Deferred Revenue, Cr. Revenue
  • Customer Pays: Dr. Cash in Transit (Apple), Cr. AR 
  • Developer Proceeds Liability: Dr. AR, Cr. Developer Proceeds Liability

Steps:

  1. Create a unique identifier for each row of the report by concatenating Report Name - Row Number - Apple Identifier.
  2. Filter the report for Customer Price >= 0 (this determines what is a sale vs refund)
  3. Calculate revenue to the company by backing out developer proceeds: Developer Proceeds * Units ) / proceedsRatio
  4. If volume is manageable, maintain each subscription on a line in Excel to create a detailed waterfall report; otherwise, summarize entries to a summarized waterfall.
  5. Note: Because Apple only populates the report with paid items, the Revenue Entries and Payments can be posted from the same report.

  • Payment Processor Fees: Dr. Payment Processor (PSP) Fees, Cr. Cash in Transit (Apple) 

Steps:

  1. Calculate the fees by taking the inverse of the amount calculated for revenue for each line: (amount *(1 - proceedsRatio) and putting it into its own column.

Refunds

  • Dr. AR, Cr. Cash in Transit (Stripe)
  • Dr. Revenue/Contra Revenue, Cr. Deferred Revenue
  • Dr. Cash in Transit (Stripe), Cr. PSP Fees 

Steps:

  1. Filter the report for Customer Price < 0 (this determines what is a sale vs refund)
  2. Calculate refund to the company by backing out developer proceeds: Developer Proceeds * Units ) / proceedsRatio
  3. If volume is manageable, maintain each subscription on a line in Excel to create a detailed waterfall report; otherwise, summarize entries to a summarized waterfall.
  4. Note: The refunds also have fees refunded; as such, refunds also need to have the fee amount calculated and accounted for.

Financial Report

Journal Entries:

  • Apple Settlements: Dr. Cash - Bank, Cr. Cash in Transit (Apple)

Steps:

  1. Apple’s settlement report comes out on day 4-5 after month end. Users can determine which payments were settled using VLOOKUP on the concatenated unique identifier discussed above. 
  2. The actual settlement date for accounting purposes is the settlement date on the report + 35 days. 

What accounting cannot be done with Apple data

Journal entries:

  • Sales Tax Accrual: Dr. AR, Cr. Sales Tax Liability
    • Apple Reports do not capture this data
  • Refunds - Contra-Revenue - Dr. Revenue/Contra Revenue, Cr. Deferred Revenue
    • Because Apple does not allow users to connect a refund with the related subscription, accountants have to determine how to handle refunds (either taken immediately or over time, as well as the mix of contra-revenue to offset)
  • Subscription Upgrades/Downgrades
    • Because Apple does not allow users to connect a refund with the related subscription, it is impossible to account for upgrades and downgrades outside general refunds/subscription accounting.
  • Disputes Dr. Revenue/Contra Revenue, Cr. Deferred Revenue
    • Apple does not process disputes; all sales on the report are held until paid. 
  • Credit Issuances: Dr. Deferred Revenue, Cr. Credit Payable
  • Credit Applications: Dr. Credit Payable, Cr. AR

Key Insights and Best Practices

Revenue Completeness

The best identifier for revenue lines in Apple is the SKU or Apple Identifier on your reports. These should map to a revenue stream. Review monthly to ensure all are accounted for.

Low-Quality Data and Audit

Unfortunately, Apple provides very low-quality data on which to do accounting. As such, be prepared to provide documentation and supporting assumptions regarding allocation methodologies and estimates to compensate for the data shortfall for audit preparation. 

Automating Revenue Recognition for ASC 606 Compliance

Given the limitations of Apple's reporting, it's clear that a manual approach to revenue recognition is not just difficult—it's risky. The standard reports lack the subscriber-level detail and foreign exchange data required for precise ASC 606 compliance. This forces finance teams to rely on assumptions and complex workarounds, which can be a major headache during an audit. Automating the process is the most reliable way to handle these data gaps. It removes the potential for human error, saves countless hours of manual work, and ensures your financial records are consistently accurate and defensible.

An automated system can tackle the specific challenges Apple's data presents. For instance, instead of manually calculating implicit fees based on a "Proceeds Reason," an automated tool can derive these figures accurately every time. The biggest advantage comes from accessing data the standard reports omit. Solutions like HubiFi use API integrations to pull the granular, subscriber-level transaction data needed to properly reconcile sales, refunds, and payouts. This direct data access provides the clarity required for true ASC 606 compliance, moving your team away from guesswork and toward data-driven precision.

Ultimately, automation is about building a reliable and auditable financial infrastructure. When you automate revenue recognition, you create a clear, documented trail from the initial transaction all the way to your journal entries. This systematic approach helps you confidently provide the necessary documentation and supporting assumptions that auditors require, especially when dealing with low-quality source data. It also ensures that all revenue streams are correctly mapped and accounted for, giving you a complete and accurate picture of your company's financial health. If you're ready to see how this works in practice, you can always schedule a demo to learn more.

Conclusion

Accurately accounting for subscription revenue through Apple is not actually possible manually and is highly manual. By following this guide, finance teams can get as close as possible. 

Hubifi can significantly simplify and improve this process by automating the data gathering, data cleaning, reconciliation, and eliminating the need for all the manual file creation entirely - automatically generating your journal entries and enrichment needed to analyze the data at a level not available manually.

 Contact us to learn more about automating this process, or schedule a demo with your Apple data to get started today. For Apple connections, this takes about 2 weeks to implement. 

Google Play

Google holds the data needed to account for subscription revenue and the order-to-cash cycle in two reports (Estimated Sales and Earnings Report). 

Google maintains only a portion of the necessary data to record revenue according to ASC 606 correctly, unlike some other billing/payment tools. See Figure 1 for a summary of accounting that can be achieved from Google, compared to other common Billing and Payment systems used in the Subscription/SaaS industry.

Understanding Google Play Store Commissions

Before you can accurately record journal entries, you need a firm grasp of Google's commission structure. Unlike a simple flat fee, Google uses a tiered system that changes based on your earnings and the type of product you sell. These fees directly impact your gross revenue, so getting them right is the first step to clean, compliant accounting. Understanding these nuances ensures your financial statements reflect the true cost of selling on the platform and helps you forecast profitability more accurately. Let's break down the different fees you'll encounter.

Tiered Commission Structure

Google offers a tiered commission model to support developers as they grow. Through its Play Store Small Business Program, Google charges a 15% commission on the first $1 million of your earnings each year. Once your revenue surpasses that threshold, the commission rate for any subsequent earnings increases to 30%. This structure means you need to diligently track your annual revenue to know exactly when the higher rate applies. For finance teams, this creates a variable that must be monitored closely to ensure cost of goods sold is recorded correctly and your margins are calculated accurately throughout the year.

Subscription Commission Rate

If your business relies on a subscription model, Google simplifies things a bit. For all automatically renewing subscriptions, the platform charges a flat commission rate of 15% right from the start, regardless of your total earnings. This consistent fee applies from the very first day of the subscription and continues for its entire duration. This predictability is helpful for financial planning, as you can apply a standard rate to all your subscription-based recurring revenue. It's a critical detail for ensuring your deferred revenue and revenue recognition schedules are precise and compliant with ASC 606 standards.

One-Time Developer Account Fee

Getting started on the Google Play Store involves a straightforward, one-time cost. To register for a Google Play developer account, you'll need to pay a single $25 fee. Unlike some other platforms that require annual renewals, this is a one-and-done payment. Once you've paid it, your account is set for life without any recurring membership costs. While it's a relatively small expense in the grand scheme of app development and marketing, it's an important initial outlay to factor into your budget when you're preparing to launch your application on the platform.

Data Extraction

To compile all necessary data for accurate accounting, the Estimated Sales and Earnings reports need to be downloaded from your Play Console. 

  1. Estimated Sales Report: Contains the data needed to account for invoices, refunds, taxes, and payments. This is a daily report.
  2. Earnings Report: Contains the data needed to account for payment processor fees, refunded fees, and payouts/settlements. This is a monthly report.

Accounting - Journal Entries

Estimated Sales Report

Note: This is a daily report.

Journal Entries:

  • Revenue Deferral: Dr. Accounts Receivable (AR), Cr. Deferred Revenue
  • Revenue Recognition: Dr. Deferred Revenue, Cr. Revenue
  • Sales Tax Accrual: Dr. AR, Cr. Sales Tax Liability

Steps:

  1. Identify the invoices that need deferral and recognition by filtering for Financial Status = Charged; Best practice is to use the SKU as the driver for GL mapping. Use the Item Price as the amount to recognize.
  2. You can utilize the Taxes Collected field to drive the Sales Tax Accrual entries. 
  3. If volume is manageable, maintain each subscription on a line in Excel to create a detailed waterfall report; otherwise, summarize entries to a summarized waterfall.
  4. Sales tax jurisdictions can be found by using the Country of Buyer field.

  • Customer Pays: Dr. Cash in Transit (Google), Cr. AR 

Steps:

  1. Identify the payments that need recognition by filtering for Financial Status = Charged, Use the Charged amount as the amount to record.
  2. Only successful payments will be on this report. 

  • Refunds:
    • Dr. AR, Cr. Cash in Transit (Stripe)
    • Dr. Revenue/Contra Revenue, Cr. Deferred Revenue
    • Dr. Sales Tax Liability, Cr. AR

Steps:

  1. Identify refunds by filtering for Financial Status = Charged, Use the Item Price as the amount to recognize.
  2. You will need to VLOOKUP using the Order Number to determine which order the refund relates to and the correct revenue and deferred revenue accounts to offset.
  3. You can utilize the Taxes Collected field to drive the Sales Tax Accrual Reversal entries. 
  4. If volume is manageable, maintain each subscription on a line in Excel to create a detailed waterfall report; otherwise, summarize entries to a summarized waterfall.

Earning Report Report

Note: This is a monthly report and only available 4-5 days after the end of the month.

Journal Entries:

  • Google Settlements/Payouts: Dr. Cash - Bank, Cr. Cash in Transit (Google)

Steps:

  1. Identify settlements by filtering for transaction type =/= Fee; use the Amount (Merchant Currency) as the amount to recognize.
  2. Note this report contains settlements for payouts and refunds. As such, Transaction Type = Charge is a standard settlement, and Transaction Type = Refund is a refund settlement.

  • Payment Processor Fees: Dr. Payment Processor (PSP) Fees, Cr. Cash in Transit (Google) 
  • Fee Refunds: Dr. Cash in Transit (Stripe), Cr. PSP Fees 

Steps:

  1. Identify settlements by filtering for transaction type = Fee; use the Amount (Merchant Currency) as the amount to recognize. Negative values are fee refunds and positive standard refunds.

Key Insights and Best Practices

Revenue Completeness

The best identifier for revenue lines in Google is the SKU on your reports. SKU should map to a revenue stream. Review monthly to ensure all SKUs are accounted for.

Settlement Dates

Although Google provides the settlement date for payouts/settlements on the Earnings report, the actual settlement date of the record is the 15th day of the following month from the report date. As such, the Report Date + 1 month + 15 days is the way to derive the correct accounting date for settlements. This is supported by Google’s Payment Policy found in the Play Console. 

How Regional Regulations Impact Commissions

App store commission rates aren't set in stone; they can change significantly based on where your customers are located. Global regulations are constantly evolving, and major markets are introducing rules that directly impact how much of your revenue you get to keep. For finance teams, this means that a single subscription price can result in different net revenue depending on the buyer's region, adding another layer of complexity to your accounting. Staying on top of these regional nuances is critical for accurate financial forecasting and ensuring compliance across all the markets you operate in.

Changes in the European Union (EU)

The European Union has been a major force in reshaping the digital marketplace, and its regulations have had a direct impact on app store commissions. The most significant piece of legislation is the Digital Markets Act (DMA), which aims to create a more level playing field for developers. As a result of the DMA, platforms like Apple have been compelled to adjust their fee structures for users within the EU. This has led to lower standard rates but has also introduced new, more complex fee arrangements that require careful tracking and calculation to understand your true net revenue from the region.

The Digital Markets Act (DMA) and Lower Rates

Under the Digital Markets Act (DMA), Apple introduced a lower standard commission rate of around 17% for in-app purchases in the EU. This is a noticeable reduction from the typical 30% rate seen elsewhere. However, this change isn't a simple discount. The new structure also includes additional fees, such as a Core Technology Fee, that can apply under certain conditions. This means your finance team can't just apply a single new rate to all EU transactions; you have to analyze each transaction to determine the correct combination of fees, making manual revenue reconciliation even more prone to error.

Apple's Core Technology Fee

The introduction of the Core Technology Fee (CTF) in the EU adds another variable to the equation. For larger developers who choose to use alternative payment systems, the total commission can still be substantial. The fee structure might break down into multiple parts, such as a 13% charge for "store services," a 5% "Core Technology Commission," and another 2% for customer acquisition. When combined, these fees could bring the total commission to around 20%. This multi-part fee structure complicates revenue recognition, as you now have several different cost line items to track against a single sale, all depending on the payment method and your app's distribution model.

Rules for Alternative Payment Systems

A key component of the EU's regulatory changes involves the use of alternative payment systems. The rules now state that platforms like Apple cannot charge their standard commission when a user is directed to an external website to complete a payment. This gives developers more control over their payment processing and can potentially lower costs. However, it also creates a new revenue stream that must be tracked separately from in-app purchases. Your accounting system needs to be able to differentiate between revenue processed through the App Store and revenue from third-party processors, each with its own fee structure and reporting format.

What's Exempt from App Store Commissions?

Not every dollar that flows through your app is subject to a commission from Apple or Google. Understanding which revenue streams are exempt is crucial for accurate financial reporting and can have a major impact on your bottom line. The platforms generally draw a line between digital goods and services consumed within the app and other types of transactions. By correctly categorizing your revenue, you can ensure you aren't overpaying on commissions and that your financial statements accurately reflect your different business activities, from selling physical products to earning from ad placements.

Sales of Physical Goods

If your app facilitates the sale of physical goods or services that are consumed outside the app, you're generally in the clear. For example, if you have a retail app where customers buy clothing or an app for booking in-person fitness classes, the revenue from these sales is typically not subject to the standard 15-30% commission. This is a critical distinction for e-commerce and service-based businesses using an app as a sales channel. However, you still need to account for the payment processing fees from your chosen provider, like Stripe or PayPal, and ensure these revenue streams are properly segregated in your accounting.

In-App Advertising Revenue

For many apps, advertising is a primary source of income. The good news is that most in-app advertising revenue is also exempt from app store commissions. Whether you're earning from banner ads, interstitial videos, or rewarded ads, this income is considered separate from the sale of digital goods and is not part of the commission base for Apple or Google. This allows you to keep a much larger portion of your ad earnings. The challenge for finance teams is accurately tracking and reconciling this revenue from various ad networks, each with its own payment cycles and reporting dashboards.

How Other App Stores Compare

While Apple and Google dominate the market, they aren't the only app stores available to developers. Other platforms like the Amazon Appstore, Microsoft Store, and Epic Games Store offer alternative distribution channels, each with its own unique commission structure. For businesses looking to maximize their reach, publishing on multiple stores can be a smart strategy. However, this also means your finance team must manage and reconcile revenue from several different sources, each with different rates, fees, and reporting standards. An automated revenue recognition system is key to managing this complexity without manual spreadsheets.

Amazon Appstore and Microsoft Store

The Amazon Appstore provides another significant marketplace, particularly for Android devices like the Fire tablet. Amazon offers a Small Business Program similar to Apple and Google, where developers earning less than $1 million in annual revenue pay a reduced commission. For these developers, the rate is 20% on paid apps and in-app purchases. This is higher than the 15% offered by the major players for small businesses but still provides a reduction from the standard rate. The Microsoft Store also has its own fee structure, which you'll need to factor into your financial models if you develop for Windows devices.

Epic Games Store and Samsung Galaxy Store

The Epic Games Store has made waves by offering one of the most developer-friendly commission rates in the industry. Epic charges a flat 12% commission on all sales, allowing developers to keep 88% of their revenue. This aggressive pricing has made it an attractive platform, especially for game developers. Similarly, the Samsung Galaxy Store, which comes pre-installed on all Samsung devices, provides another major distribution channel with its own set of fees and policies. Managing these varied rates across platforms is essential for accurately calculating your gross margins and overall profitability for each channel.

Conclusion

Accurately accounting for subscription revenue through Google requires a comprehensive approach to data extraction and journal entries and is highly manual. By following this guide, finance teams can ensure compliance with ASC 606/GAAP and achieve as detailed a margin analysis as possible. 

Hubifi can significantly simplify this process by automating the data gathering, data cleaning, reconciliation, and eliminating the need for all the manual file creation entirely - automatically generating your journal entries and enrichment needed to analyze the data. Contact us to learn more about automating this process, or schedule a demo with your Google data to get started today.

This white paper is designed to serve as a practical guide for accounting professionals navigating subscription revenue accounting.

Frequently Asked Questions

Why can't I just use the final payout amount from Apple or Google as my revenue? That's a common question, and it gets to the heart of proper accounting. The payout you receive is a net figure, meaning the platform has already deducted its commissions, certain taxes, and other fees. For accurate financial reporting under standards like ASC 606, you need to record the gross revenue—the full amount the customer paid—and then separately account for the app store commissions as a cost of sales. This gives you a true picture of your top-line performance before expenses.

What's the biggest data gap in the standard reports that I need to watch out for? The most significant challenge is the lack of a clear link between an original sale, a subsequent refund, and the final payout at the individual subscriber level. Apple's reports, in particular, make it nearly impossible to tie a refund directly back to the specific subscription it belongs to. This forces you to make assumptions when reversing revenue, which complicates your accounting and can be a major point of scrutiny during an audit.

The commission rates seem to change based on my earnings and subscription length. How do I track this accurately? Tracking these variable rates is one of the most difficult parts of doing this manually. You have to constantly monitor your annual revenue to know when you cross thresholds, like Google's $1 million mark where the rate changes. For Apple, you also need to track each subscriber's tenure to know when their commission drops from 30% to 15%. This typically requires maintaining a complex and error-prone spreadsheet system that becomes harder to manage as your business grows.

My company operates in the EU. How do new regulations like the DMA affect my accounting? The Digital Markets Act (DMA) has made revenue accounting in the EU more complex. While some commission rates are lower, platforms have introduced new, multi-part fee structures, like Apple's Core Technology Fee. This means you can no longer apply a single rate to all EU sales. Your team must analyze transactions to determine which combination of fees applies and create a separate process to account for revenue coming from any alternative payment systems you use.

When does it make sense to stop doing this manually and look for an automated solution? The tipping point is usually when the hours your team spends downloading, cleaning, and reconciling spreadsheets start to feel unsustainable. If you're struggling to close the books on time, if you're concerned about audit readiness because of the data gaps, or if you can't get clear answers about your profitability by product or region, it's a strong sign that your manual process is holding you back from making strategic decisions.

Key Takeaways

  • Master the Complex Commission Rules to Protect Your Margins: App store fees are not a simple flat rate; they vary based on your revenue, subscription length, and even regional laws like the EU's DMA. Understanding these details is the first step to accurately forecasting your net revenue and avoiding costly miscalculations.
  • Standard Financial Reports Create Audit Risks: The default reports from Apple and Google are notoriously opaque, lacking the subscriber-level detail needed to easily connect sales to payouts. Relying on these reports alone forces manual workarounds that are difficult to defend during an audit and can hide the true financial health of your business.
  • Automate Data Collection for Accurate, Compliant Accounting: The most reliable way to handle incomplete platform data is to bypass the standard reports entirely. Using an automated solution to pull data directly from the APIs gives you the granular detail required for true ASC 606 compliance and a clear, auditable financial record.

Related Articles

Cody Leach, CPA

Accounting Automation | Product | Technical Accounting | Accounting Systems Nerd

A technology and automation focused CPA helping finance leaders bring their processes into the 21st century.If you're interested in talking finance systems - https://calendly.com/cody-hubifi Feel free to set up some time on my calendar. I like talking about this stuff too much