Skip to content
All field notes
Measurement
Published
Oct 30, 2026
Updated
Nov 4, 2026
Reading time
12 min read

AdMob Earnings vs Payments: Reconcile the Difference

Reconcile AdMob estimated earnings, finalized transactions, deductions and bank receipts without confusing payment timing, mediation or currency differences.

AP
AdProof Research
Independent measurement desk
A publisher earnings estimate, finalized transaction, payment receipt and bank receipt occupy separate checkpoints, with an unresolved adjustment kept aside.
Earnings estimates, finalized transactions, payment issuance and bank receipt are separate records. Conceptual illustration, not customer figures.
In this guide (11 sections)

If your AdMob payment is lower than the earnings report, first identify which two records you are comparing. Estimated revenue, finalized earnings, the account balance, a payment issued and money received by a bank are different amounts. Match the earning period, ad-source payment route, timezone and currency before calling the difference a deduction.

A real older developer question about estimated earnings decreasing near month-end shows the confusion. Some replies discuss retrospective adjustments; another explains lower demand for new ads. Those are different problems. A lower price for today's inventory does not, by itself, explain a change to an earlier period's earnings.

This guide builds a reconciliation you can reproduce. It does not infer Google's undisclosed traffic decisions or promise reversal of a deduction.

Start with five separate records#

Google's earnings tracking instructions locate daily estimates on Home and finalized earnings under Payments. Save the actual record behind each number rather than copying unlabeled dashboard totals.

RecordWhat to captureWhat it does not establish
Earnings reportExact metric, dates, timezone, currency, apps and ad sources, retrieval timeThe final amount payable
Finalized earnings transactionStatement period, transaction date, amount and descriptionA payment has been issued
Account balanceObservation date, opening balance and posted transactionsEarnings from only one month
Payment recordIssue date, method, reference, amount and currencyThe bank has credited the same amount
Bank receiptValue date, credited currency, amount and disclosed charges or conversionThe cause of an earlier earnings adjustment

Keep the original export or private screenshot and a short source label beside every value. An updated report should be a new snapshot, not an overwrite of the evidence you are investigating.

Do not add the current month's estimate to last month's finalized earnings and expect the result to equal a payment. That combines different earning periods and states. Likewise, a balance can contain carried amounts and later adjustments, so it needs its own transaction bridge.

For your campaign

Match the earnings records first

Estimated revenue, finalized earnings, balance, issued payment and bank receipt are separate amounts. Discuss the records available for your comparison.

Discuss measurement scope

A short inquiry to scope relevant measurement options; financial adjustments are not promised.

Confirm whose revenue belongs in the payment#

Mediation reporting can show earnings that do not all travel through the same payer. In its bidding FAQ, Google says most bidding sources pay through AdMob, while some are direct pay. The direct-pay agreement determines that source's payment arrangement. Check the actual source setup rather than assuming every bidder uses the same route.

Build a small routing table: ad source, bidding or waterfall arrangement, payer, statement reference, currency and earning period. Mark an unknown route unresolved until the agreement or source account confirms it. A revenue row appearing in an AdMob report does not alone identify who owes that payment.

Google's AdMob glossary also describes estimates for custom events based on the manually configured eCPM. A modeled reporting amount is not a bank receivable validated by that custom event's payer. Preserve the rate's effective dates and distinguish calculated estimates from the source's actual statement.

Avoid two opposite errors: adding direct-pay earnings to an expected Google remittance, and excluding a bidding source simply because it is a third party. Make the route explicit for each source you include.

Match the calendar and the currency before subtracting#

Use a completed earning period and record its boundaries. Google's estimated-versus-finalized explanation says Home estimates use the account timezone, while finalized earnings and payments use the AdSense billing timezone, America/Los_Angeles. Local month boundaries can therefore differ.

Do not replace that named zone with a fixed UTC offset: daylight saving can change the offset. If you cannot produce an exactly aligned export, document the boundary difference rather than declaring every remaining dollar an unexplained deduction.

Keep three dates separate: when ads generated the reported activity, when earnings or an adjustment were posted, and when a payment was issued. A transaction posted this month can concern earlier activity. Do not assign it to the newest app release merely because their dates are close.

Use currency codes, not an ambiguous dollar symbol. Compare amounts in the same currency only after recording any actual conversion. A current online exchange rate is not evidence of the rate used in an earlier payment or bank credit.

Our publisher revenue diagnostic covers a different branch: comparable activity and revenue genuinely declining. Complete the state and scope checks here before reopening that delivery investigation.

Reconcile the estimate to finalized earnings#

For the same payment route and period, calculate a difference, not an automatically classified loss:

Estimate-to-final difference = comparable estimate − finalized earnings

Record both snapshot times. A positive result tells you the finalized amount is lower than that selected estimate. It does not identify an app, user, placement, traffic source or reason.

Google's record of invalid-activity deductions describes filtering during reporting, adjustments during finalization, and deductions discovered after payment. It also lists delayed processing and rounding among finalization factors. That is why the last estimate you saw is a snapshot, not a guaranteed settlement amount.

If a transaction is explicitly labeled invalid activity, preserve that classification. If you only observe an estimate-to-final gap, do not rename it invalid traffic. Google's deductions FAQ also covers policy-related activity and, in rare cases, advertiser payment defaults. Several documented explanations are possible; their existence does not establish which applies to your account.

The same FAQ states that deductions cannot be appealed and that detailed activity or app attribution is not disclosed. An appeal of an account action is a separate process from a deduction appeal. Do not turn a support packet into a promise of reimbursement or claim that an external detector can reconstruct Google's private adjudication.

For a disabled-account notice, follow the separate account-state and appeal evidence workflow. A final-payment hold is not the appeal turnaround.

Use a precise unresolved note: “Comparable estimate exceeded finalized earnings by X; statement provides no app-level allocation.” That remains useful evidence even when the platform does not disclose the missing breakdown.

Bridge finalized earnings to the account balance#

Create a transaction worksheet with one row per posted entry. Recommended columns are transaction reference, posting date, stated earning period if supplied, description, currency, signed amount, evidence path and reconciliation state.

Use a consistent sign convention. An earnings credit increases the balance; a deduction or issued payment reduces it. Follow the actual statement's signs rather than subtracting a negative value twice.

Closing balance = opening balance
                + posted earnings and other credits
                − posted deductions and other debits
                − payments issued against the balance

Include each entry exactly once. The finalized earnings line already incorporates the finalization outcome; do not subtract the estimate-to-final difference again. Similarly, do not deduct a fee from a reported amount if the documentation shows that amount is already net of that fee.

An adjustment without a disclosed earning period belongs in an unallocated-period row. Preserve its posting date and description. Forcing it into the nearest month's app totals may make a worksheet look tidy while introducing an unsupported explanation.

For a separately negotiated partner invoice or credit, use the invoice reconciliation workflow. An issued commercial credit and a Google earnings transaction are different records with different owners.

A worked example with three different gaps#

Hypothetical teaching example. These invented USD figures assume a documented, aligned earning period and payment route. They are not customer results, a typical deduction rate or evidence of any platform's decision.

ObservationUSDInterpretation
Total mediation estimate1,200Includes several payer routes
Documented direct-pay portion250Reconciled with that separate payer
Comparable Google-paid estimate9501,200 minus 250
Finalized earnings credit920Leaves a 30 estimate-to-final difference
Opening balance40Existing balance, not new earnings
Separately posted deduction10Its description and period need their own evidence
Payment issued95040 + 920 − 10
Closing balance0The statement bridge balances

Comparing the 1,200 report total with the 950 payment creates a misleading 250 “deduction.” That amount is the separately payable route under this example's explicit assumptions. The estimate-to-final difference is 30, and the separately posted deduction is 10. Subtracting 30 again from 920 would count the same finalization gap twice.

Suppose the bank then credits 940 USD and its advice explicitly documents a 10 USD receiving charge, with no conversion. That explains the issued-to-received difference in this hypothetical. It does not explain the 30 earnings difference. Without the bank advice, the 10 would remain unresolved; matching arithmetic is not proof of the cause.

These stages need not produce a payment that equals one month's finalized credit. The purpose is to explain each bridge using its own records, not to choose the most alarming subtraction.

Investigate issuance and bank receipt separately#

Google's payments and transactions guide describes a monthly cycle, with prior-month earnings finalized at the beginning of the following month and eligible payments generally issued around the 21st. Eligibility depends on the applicable threshold and holds. Issuance is not a universal same-day bank-credit guarantee.

If there is no payment entry, inspect the actual balance, account threshold and outstanding actions first. If there is an issued payment, preserve the payment number, date, method, amount and currency before investigating receipt.

The current missing-payment troubleshooting guide specifies a 15-business-day threshold from the listed payment date for an EFT or wire inquiry. That is an inquiry/reissue condition, not a promise that every transfer takes 15 days. Use the instructions applicable to your payment method and current status; do not generalize a check's timetable to an electronic transfer.

For a wire that arrives at a different value, Google's wire-transfer FAQ directs publishers to their bank about bank fees and exchange rates. Obtain the issued currency and amount, any intermediary or receiving charges actually exposed, and the bank's conversion advice. Do not infer a fee from an unexplained shortfall or apply another product's exchange-rate rules to AdMob.

Choose the next action from the unresolved boundary#

FindingNext useful evidenceAvoid
Report includes another payerSource agreement and separate statementCalling the whole gap a deduction
Period or timezone differsAligned dates or documented cutoff limitationAssigning a false precise cause
Estimate changed before finalizationDated report snapshotsTreating an estimate as a settled balance
Explicit deductionExact transaction description and disclosed scopeInventing an app-level allocation
No issued paymentThreshold, holds and required account actionsAsking the bank to locate an unsent transfer
Issued but unreceivedPayment reference and method-specific waiting periodRequesting premature reissue
Bank credit differsPayment advice, charges and actual conversionBlaming impression counting from a bank amount

Preserve a useful review packet#

Keep the report exports, payer routing table, transaction bridge, payment reference and bank advice together. Label absent fields unavailable. Share redacted evidence through the relevant official private channel; public forum posts should not expose account identifiers, bank details or user-level records.

If the evidence suggests a placement or traffic-quality concern, investigate the affected app version and traffic scope using the AdMob placement and IVT checklist. A high CTR, a revenue callback or an independent event exclusion cannot establish the network's final payable amount.

When the discrepancy is between SDK revenue callbacks and Analytics instead of a finalized payment, trace callback values into Analytics reporting. Verify the collection path and revenue population before applying a settlement explanation to that separate report comparison.

For a rewarded-ad server callback count that differs from impressions, separate SSV requests, verified reward transactions and fulfilled credits. That reconciliation answers a reward-processing question; a verified callback does not establish the final payable amount.

For campaigns already measured with AdProof, retain supported campaign-event or aggregate exports with explicit dates, timezone and filters alongside that packet. The anonymized FMCG in-app count-once case concerns delivery-count evidence, not a recovered payment or AdMob deduction explanation. Request a demo to review the supported measurement workflow; keep settlement decisions with the statement's issuer.

Frequently asked questions#

Does lower finalized revenue prove invalid traffic?

No. Preserve an explicit transaction label where one exists. A difference alone does not establish its cause or identify an affected app.

Should all mediation earnings equal my Google payment?

No. Confirm the payer for each included source. Most bidding sources pay through AdMob, while direct-pay arrangements and other separately settled revenue need their own records.

Can a finalized amount change after payment?

Google documents later deductions for invalid activity discovered after payment. Preserve the new transaction and its disclosed scope rather than silently rewriting your original payment record.

Can AdProof recover the deduction or reveal its hidden cause?

No such outcome is established here. Supported campaign measurements can contribute scoped delivery evidence, but they do not reveal Google's private detection decisions or guarantee a settlement change.

Research and scope#

Reviewed 30 October 2026. The linked question is an older evergreen discussion. Its anecdotes and claimed percentages are not adopted as benchmarks. Official references were opened during research. The worksheet, sequence and examples are recommended diagnostics, not an executed account audit, accounting determination or payment guarantee.

Your next step

Match the earnings records first

Estimated revenue, finalized earnings, balance, issued payment and bank receipt are separate amounts. Discuss the records available for your comparison.

Discuss measurement scope

A short inquiry to scope relevant measurement options; financial adjustments are not promised.

Back to all field notes