Google Play earnings report tool

Sign in with Google, load earnings reports, and download settlement results as Excel.

Open tool Back to tools
// about

About this Tool

A specialized reporting tool for Android app developers to process Google Play Console financial report archives and view monthly sales, refunds, taxes, and net payouts.

How to use it

  1. Connect your account or upload Google Play sales ZIP report archives.
  2. Select the report year and months you want to review.
  3. Click 'Process' to see your settlement summary and export to Excel.

Why people use this tool

  • Combines multiple monthly sales CSV report files in seconds.
  • Displays clear breakdowns of gross sales, Google fees, taxes, and actual payouts.
  • Exports structured Excel summaries ready for tax and accounting.

Frequently Asked Questions

Is my Google Play financial data safe?

Yes, processing happens securely in your active session and is never shared with third parties.

Which report files are supported?

Upload standard monthly earnings ZIP files downloaded from Google Play Console.

Can I export data to Excel?

Yes, you can download a formatted Excel spreadsheet with all monthly details.

Guides · Revenue · 8 min read

How Google AdSense and Google Play Payouts Work: Estimated vs Finalised Earnings, FX and Bookkeeping

Once Google revenue starts arriving, the question 'why doesn't the dashboard match my bank deposit?' soon follows. Understanding how earnings are finalised and paid makes monthly reconciliation much easier.

The amount you see in the AdSense dashboard in real time is estimated earnings. After the month ends, Google removes invalid traffic and reviews the figures, and the finalised earnings are usually added to your balance early the following month. Estimated and finalised amounts can therefore differ slightly.

1–31 October   estimated earnings accrue (dashboard)
Early November October earnings finalised → added to balance
~21 November   payment issued if balance ≥ threshold
Days later     funds arrive at the bank
Estimated vs finalised AdSense earnings, the monthly payment timeline and threshold, why payments get held, and how to record foreign-currency income.
Read guide →
Build it with AI

Build this tool yourself with AI

Want your own version of this tool? Copy the work-order prompt into an AI chat, or save the skill file for an AI coding agent. Both describe the features, edge cases and test cases we used when building it.

AI work-order prompt

Paste it as-is into an AI chat such as Claude, ChatGPT or Gemini.

You are an experienced full-stack web developer. Build a web tool called "Google Play earnings report" that meets the requirements below.

## Goal

Build a web tool that signs in with Google, reads Google Play earnings reports from Cloud Storage and exports monthly totals of sales, fees, refunds, taxes and payouts to Excel.

## Core features

- Google OAuth sign-in with the devstorage.read_only scope
- List the Play Console report bucket (gs://pubsite_prod_...)
- Download and parse yearly earnings ZIP/CSV files
- Totals by transaction type, month and currency
- Export to Excel (.xlsx)

## Inputs

- Google sign-in
- Bucket URI and year

## Outputs

- Monthly settlement summary
- Excel file

## Edge cases and handling rules

- Explain missing bucket permissions
- Handle CSV encoding and delimiter differences
- Aggregate refunds (negative rows) and tax rows separately
- Stream large files

## Implementation requirements

- Requires a server-side implementation. Request read-only scopes and use report files only temporarily during the session.
- State the purpose of data use on the OAuth consent screen and in the privacy policy.
- Make the UI responsive and easy to use on mobile; label every input and keep everything keyboard accessible.
- Add a Copy button for results and show clear, friendly error messages for invalid input.
- Keep the core logic in functions separate from the UI so it can be unit-tested.

## Definition of done (test cases)

- Monthly totals from a sample CSV match a manual calculation
- Refunds reduce sales
- Clear error for a bucket without access

First outline your implementation plan in at most five lines, then write the complete code, and finally explain how to check the test cases above.

Skill (SKILL.md)

Save it as .claude/skills/build-google-play-earning/SKILL.md for AI coding agents such as Claude Code to reuse whenever you build or change this tool.

---
name: build-google-play-earning
description: Use when building or changing a Google Play earnings report tool. Build a web tool that signs in with Google, reads Google Play earnings reports from Cloud Storage and exports monthly totals of sales, fees, refunds, taxes and payouts to Excel.
---

# Build: Google Play earnings report

## Goal

Build a web tool that signs in with Google, reads Google Play earnings reports from Cloud Storage and exports monthly totals of sales, fees, refunds, taxes and payouts to Excel.

## Workflow

1. Review the required features, inputs and outputs below and ask about anything missing first.
2. Implement the core logic as pure functions separate from the UI.
3. Check the logic against the test cases in the verification list.
4. Build a responsive UI with an input form, a result area and a Copy button.
5. Reproduce each edge case listed under Rules and refine the error messages.

## Core features

- Google OAuth sign-in with the devstorage.read_only scope
- List the Play Console report bucket (gs://pubsite_prod_...)
- Download and parse yearly earnings ZIP/CSV files
- Totals by transaction type, month and currency
- Export to Excel (.xlsx)

## Inputs

- Google sign-in
- Bucket URI and year

## Outputs

- Monthly settlement summary
- Excel file

## Rules

- Explain missing bucket permissions
- Handle CSV encoding and delimiter differences
- Aggregate refunds (negative rows) and tax rows separately
- Stream large files
- Requires a server-side implementation. Request read-only scopes and use report files only temporarily during the session.
- State the purpose of data use on the OAuth consent screen and in the privacy policy.

## Verification

- [ ] Monthly totals from a sample CSV match a manual calculation
- [ ] Refunds reduce sales
- [ ] Clear error for a bucket without access

Tips for working with AI

  • Tell the AI your stack (for example React, Vue or plain HTML) on the first line so the code matches your project.
  • Ask it to run the listed test cases and show the results before you accept the code.
  • Never paste real secrets, customer data or API keys into the prompt; use sample values instead.