> ## Knowledge Base Index
> Fetch the complete knowledge base index at: https://help.appfigures.com/sitemap.xml
> Use this file to discover available pages before exploring further.
> Pure-Markdown content can be obtained by appending a '.md' suffix to the content URLs listed in the sitemap (without the trailing slash).

# The Payments Report

Accounting for your app and ad network payments is a time-consuming task. Multiply that by several stores and ad networks + Apple's unfriendly fiscal calendar, and you've got a small headache on your hands.

The Payments report eliminates the headache by taking care of all of that for you. Automatically.

The Payments report aggregates all available information for all of your linked accounts into a single report. It automatically adjusts the date range to fit the data source's correct fiscal month (if applicable) and shows *estimated*, *actual*, **and paid** amounts (* where possible).

![](https://storage.crisp.chat/users/helpdesk/website/-/1/6/f/5/16f5957f6b3a4700/kb516paymentsreport1ewrwzl_6dymel.png =996xauto)

For Apple developers, in addition to showing total amount paid, the report also breaks down the paid amount into each app and in-app, using accurate Apple exchange rates.

### Apple (iOS and Mac)
* **Estimated:** derived from estimated daily reports
* **Actual:** derived from financial reports
* **Paid:** derived from payment reports (+ financial reports to break those down by app)

### Google Play
* **Estimated:** derived from the estimated reports.

### Amazon Appstore
* **Estimated:** derived from daily reports.

### Stripe
* Estimated: derived from daily reports 

### Ad networks
* **Estimated:** derived from estimated daily reports.
---

### Noteworthy

Tips to look at when looking to align data from the payments report to the sales report -> [Comparing Revenue from the Payments Report to the Sales Report](https://help.appfigures.com/en/article/comparing-revenue-from-the-payments-report-to-the-sales-report-1xkhhjl/)