App Store proceeds and payment reconciliation checklist
Revenue is not useful operational evidence until proceeds, payments, and bank deposits reconcile.
Reconcile proceeds through App Store Connect reports, payment timing, bank deposits, refunds, taxes, and currency context. Apple documents viewing payments and proceeds and explains payments and proceeds. AppReviewReady interpretation: product and growth teams should understand reconciliation enough to avoid false profit conclusions.
Start from reports, not memory
Collect the relevant financial report, payment view, product sales context, refund records, bank deposit, and expected reporting period. Do not reconcile from dashboard screenshots or a remembered gross sales number.
Separate gross sales, proceeds, adjustments, refunds, taxes, currency conversion, and bank timing. Each can explain a different mismatch.
AppReviewReady interpretation: reconciliation is a growth discipline because paid experiments should be judged on money that can be explained, not only purchase counts.
Compare deposits carefully
- Bank deposit date may differ from sale date.
- Report currency may differ from bank account currency.
- Refunds and adjustments can move after the original sale.
- Multiple storefronts can appear in different report contexts.
- Payment thresholds or account setup can affect timing.
Classify differences
When numbers differ, classify the cause before escalating: report period mismatch, product filter mismatch, refund timing, currency interpretation, bank delay, tax or agreement state, or missing finance access.
Product teams often overreact to normal payout timing. Finance teams often lack product context for experiments. Reconciliation should connect both views before pricing or acquisition decisions change.
Separate Apple reporting from AppReviewReady interpretation: Apple provides payment and proceeds tools; AppReviewReady recommends a close process that maps those tools to product decisions.
Run a monthly close loop
- Download financial reports for the period.
- Compare reported proceeds with expected paid events and bank deposits.
- Annotate refunds, major campaigns, price changes, and launch events.
- Resolve unexplained differences with finance owner.
- Feed findings into pricing, support, and product roadmap decisions.
Reconciliation record
The record keeps revenue interpretation honest. It also gives future operators an audit trail for why a campaign, price, or product line was considered profitable.
Review the record before changing paid CTA strategy. If paid reports sell but proceeds or refunds do not reconcile, the funnel may look healthier than it is.
After several periods, use reconciliation quality as an operating metric. A business that cannot explain cash cannot confidently scale SEO-driven paid acquisition.
Tie each major SEO or pricing experiment to a reconciliation note. A guide cluster may drive checkout starts, but the final decision should account for refunds, proceeds, support cost, and payment timing.
When reconciliation is unclear, pause interpretation rather than the whole business. Keep collecting traffic and product evidence while finance resolves the specific mismatch.
Over time, build a simple variance vocabulary. Teams should know the difference between expected timing variance, refund-driven variance, currency variance, and genuinely unexplained cash movement.
Reconciliation record: Period: [month] Reports used: [names] Expected proceeds: [value] Bank deposits: [value/date] Differences: [summary] Owner: [team] Decision impact: [pricing/support/product]
Primary references checked for this guide
Policy statements above are grounded in the linked Apple documentation. Operational recommendations are AppReviewReady's interpretation and should be tested against your app and the current guideline text.
Check revenue reconciliation
Review proceeds, deposits, reports, refunds, currency, and finance close readiness.
Open the tool