October 7, 2026

Revenue Attribution Discrepancy: Which Number to Report

A revenue attribution discrepancy does not change which figure belongs in the financial total: report the revenue measure approved in your accounting records…

A revenue attribution discrepancy does not change which figure belongs in the financial total: report the revenue measure approved in your accounting records, and use the attribution report to evaluate paid-channel performance. A measurement tool answers which campaign receives credit under its attribution rules; finance records revenue using the accounting policy and period your company applies. A gap of about 15% is a reason to reconcile the measures, not a reason to swap one number for the other.

Separate lines make each figure’s reporting purpose clear to finance and growth readers. Label the source, definition, and reporting period beside each figure. Airbridge Core can support the channel view for eligible paid campaigns and connected subscription events.

1. Use finance’s revenue measure for the financial total

For financial statements and company-wide revenue updates, use the measure finance approves and records in the general ledger.

Under FASB’s ASC 606 guidance, an entity recognizes revenue when or as it satisfies a performance obligation by transferring a promised good or service to a customer. The recognized amount is the amount allocated to that satisfied obligation. In a subscription business, the financial treatment therefore follows the company’s accounting policy for the service promised and the period in which the obligation is satisfied; cash arriving in a bank account is a separate event.

Under FASB’s ASC 606 guidance, a nonrefundable upfront fee is an advance payment when the fee-related activity does not itself transfer a promised service, and revenue is recognized as the future services are provided. A subscription company’s controller applies the relevant accounting treatment to its contracts, so a charge date, a store settlement date, and the revenue-recognition period can fall in different periods.

Name the accounting measure explicitly. A report can say “GAAP-recognized subscription revenue” when that is the approved measure, or use the company’s specific management-reporting label when finance has approved another definition.

Apple’s monthly App Store Connect financial reports show proceeds and final unit sales by country or region and order type. Apple’s consolidated report is based on transactions processed and settled during its fiscal month, while its detailed report includes transaction and settlement dates. Those records help explain store payouts and sales activity; the financial statement measure remains the one your accounting policy defines.

Billing and analytics dashboards also define revenue fields in particular ways. RevenueCat’s Revenue Chart documentation defines period revenue as revenue generated in that period less refunds and downward subscription-payment adjustments recorded in that period, regardless of the original transaction period. It separately defines revenue net of taxes and proceeds, with store tax and commission deductions estimated. A RevenueCat chart, an app-store proceeds report, and the general ledger can therefore each be internally consistent while showing different totals.

Keep source records available to explain how each reported value was calculated. Use billing-platform and app-store records to trace transactions and proceeds, then compare the resulting events with the attribution report when investigating a variance. If the business has a recognized-revenue rule for refunds, deferred subscription service, taxes, or platform fees, use the finance-approved treatment rather than substituting a dashboard’s label.

Airbridge Core Plan belongs in the channel-attribution row, not in the accounting-total row. It connects campaign spend to subscription revenue for Google, Meta, TikTok, and Apple campaigns; with a supported integration for RevenueCat, Adapty, or Superwall, trial conversions, first payments, renewals, and refunds can tie back to the campaign that acquired the user. That gives a growth lead a channel view of subscription outcomes while finance keeps the company’s accounting measure distinct.

2. Why both systems can be right

The two systems have different jobs. A financial record represents an accounting measure or billing transaction under its stated rules; an attribution report assigns eligible subscription events or revenue to campaigns using event collection, identity matching, attribution windows, and model settings.

The reports may use different gross, net, refund, or proceeds fields. One report may show gross customer charges, while another shows proceeds after store commission or taxes, or a net amount after refunds. RevenueCat’s documentation for refunds also shows why dates matter: its Refunds chart assigns refunds to the period when they are processed, rather than the purchase period. The original-purchase period and refund-processing period can therefore show different revenue effects even though they refer to the same transaction.

The reports also need a shared time basis. The Government Accountability Office’s data-reliability guidance tells auditors combining datasets to examine differences in timeframes, variable meanings, populations, units, and data availability. For your report, check the date the subscription event occurred, the date the system received it, the date a refund was processed, and the date each report was exported. Also align the time zone and currency before treating a percentage gap as meaningful.

Subscription revenue can cross reporting periods even when the subscriber relationship stays the same. A first payment may be followed by a trial conversion, monthly renewals, and later refunds or adjustments; a campaign report may connect several of those events with the original acquisition touchpoint. A calendar-month finance report and a campaign cohort view can therefore answer different time questions: “What revenue was recognized this month?” and “What revenue is associated with users acquired by campaigns in this cohort?” Label the view’s date basis before comparing its total with a monthly financial amount.

Airbridge’s data-discrepancy guide identifies attribution-model, data-collection, and fraud-validation differences as causes of discrepancies between Airbridge and ad channels or app stores. For app-store comparisons, app stores use user IDs such as Apple ID or Google Play ID, while Airbridge uses Airbridge Device IDs to connect ad interactions with installs. A ledger review instead traces transaction amounts and timing against billing and accounting records.

In Google Ads’ guidance on attribution-model changes, non-last-click models distribute fractional credit across contributing interactions, and conversions are reported by the date of the ad interaction. When credit is shared across interactions from different dates, campaign reports can move or spread conversions across reporting periods.

Google Ads’ conversion-window guidance allows windows from 1 to 90 days depending on the conversion source; Search and Display campaigns use a 30-day default when the window is not customized. Airbridge’s window-setup guide separates a lookback window before a target event from an attribution window after it.

On iOS, attribution postbacks add timing and data-availability conditions. Apple’s SKAdNetwork conversion-window documentation sets three windows from first app launch: days 0 to 2, days 3 to 7, and days 8 to 35. A postback, a message that reports attribution data to an ad network, can arrive in up to three rounds for a winning ad attribution. A channel view that depends on postbacks can settle on a different schedule from a billing ledger that records a purchase or renewal.

State the denominator whenever you quote a variance percentage, because the same dollar gap produces different percentages against different bases. If finance’s reference amount is $100,000 and the attributed figure is $85,000, the gap is $15,000, or 15% of the finance amount. If the same $15,000 is measured against $85,000, it is about 17.6%; state the denominator whenever the report gives a percentage.

3. Show finance revenue and channel revenue on separate lines

Give each amount a precise label, source, purpose, and reporting basis. This lets a finance reader follow the total to accounting records and lets a growth reader use campaign credit without presenting it as the company’s financial total.

A small table note can make the boundary clear: “Finance revenue is the finance-approved recognized-revenue measure for the month. Channel revenue is subscription revenue attributed to eligible acquisition campaigns under the stated attribution settings. The two rows use separate sources and purposes.” Adjust the wording to the actual company policy and report settings.

For example, assume finance reports $100,000 of recognized subscription revenue for a month and the campaign report shows $85,000 of subscription revenue credited to paid channels. Present each amount under its own label, then report a $15,000 variance, equal to 15% of finance revenue. Include the time zone, currency, event range, and refund treatment in the table note; a rounded percentage without those details can hide a denominator or period mismatch.

Choose a calendar-period view when the question is how much revenue finance recognized during that period. Choose a campaign-cohort view when the question is how acquisition from a defined campaign period performed as those users produced later subscription events. The cohort view can include later renewals, while the calendar view groups revenue by its own accounting period; use the view that fits the decision and name its date basis in the report.

Avoid adding attributed channel revenue to the finance total. The campaign number assigns credit to a channel under a model; it is not an additional sale. Paid-campaign rows cover eligible events attributed under their campaign rules; a finance total can also include subscription revenue from sources outside those paid-campaign rows.

Label the line “Airbridge-attributed subscription revenue,” and state its campaign scope and reporting period separately from finance revenue.

4. Reconcile the gap before changing budget

Run the checks in this order. Start with report definitions, then verify the underlying payment and refund events, and finally examine campaign credit and timing. This sequence separates accounting or billing mismatches from attribution differences.

1. Freeze the comparison period and currency. Write down the start and end dates, time zone, currency, app or product scope, and export time for both reports. Compare matching calendar periods or a consistent subscription cohort, and use the same currency conversion basis in both reports.

2. Name the revenue basis on each side. Record the finance-approved measure by its exact label. Select billing or store fields that match the comparison’s purpose, and note their treatment of taxes, fees, refunds, and adjustments.

3. Align event and refund dates. Record whether each figure follows purchase, service, settlement, event-received, or report-export dates, and note the refund treatment used by each report. Apple’s App Store financial-report guide distinguishes transaction dates from settlement dates. Place each refund in the period assigned by the selected report definition, and record that basis beside the variance.

4. Check that billing events arrive and map correctly. Sample several records from each meaningful event type: initial paid subscriptions, trial conversions, renewals, refunds, and any downward adjustments. Trace a sample transaction from billing through app-event data into the measurement report by comparing its event name, amount, currency, timestamp, transaction ID, and order or refund status; Google Play’s order-management guide documents how developers view order status and issue refunds. A “Processed” order means the buyer was charged, while order statuses also distinguish pending refunds, refunded orders, and partial refunds. Match the order and its status to the event record before classifying a difference as missing revenue.

5. Compare attribution settings for each channel. Record the campaign touchpoints, active model, and event settings used for each channel beside the report period. In Airbridge, open Rules > Attribution Rules > Install for lookback settings and In-App Event for attribution settings. Compare each channel’s settings with Global, which applies when a channel has no separate value.

6. Confirm the app, event source, and identity match. Record the effective date of any integration or attribution-setting change beside the report period.

7. Allow the reporting process to catch up. Compare exports made at similar times and rerun the channel report after known data refreshes. Google Ads’ reporting guidance recommends waiting until the average time to conversion has passed before evaluating performance after an attribution-model change.

8. Trace unmatched amounts to source records. Sort the variance by platform, event type, date, currency, and refund status, then inspect representative records on both sides. The GAO’s record-tracing guidance recommends comparing sampled records with source documents to assess accuracy and completeness; matching records can quantify the size of an error. Use that approach to distinguish missing or duplicated billing events from campaign credit assigned under different rules.

For a sampled test, trace billing or store documents into app-event records when checking for omitted transactions, and trace reported events back to billing documents when checking for ineligible or incorrectly entered records. The GAO’s data-reliability guidance recommends a random sample large enough to estimate the error rate with reasonable precision; matching records can quantify the error amount.

For Apple purchases, Apple’s Get Refund History endpoint retrieves a customer’s complete refund history for the app using the transaction ID of any in-app purchase. Its transaction payload includes a refund’s revocation date and reason code, which can help investigate a missing or differently dated refund event.

9. Write the finding beside the number. State the dollar gap, the denominator for the percentage, the checks completed, and whether the cause is confirmed, still being investigated, or explained by definitions and timing. Keep finance’s reporting figure in place while the review proceeds, and use the channel view for channel decisions only when its event coverage and reporting lag suit that decision. When a discrepancy reflects model settings, add those settings to the reporting note so the next month is compared on the same basis.

A simple reconciliation log makes the next review faster. For each sampled record, capture a privacy-safe transaction reference, source platform, event type, amount and currency, event date, processing or settlement date, refund status, campaign match, and the report row where it appears. Mark each check as matched, amount mismatch, period mismatch, attribution-only, or unresolved, then total the dollars in each category; the categories describe investigation results rather than new accounting measures.

The pattern can point to the next useful check. A gap concentrated in tax or commission differences calls for a gross-versus-net definition check; a gap concentrated in refunds calls for refund dates and treatment; a gap in later renewals calls for event mapping and reporting periods; and a gap that changes across campaign settings calls for attribution-window and credit rules.

Preserve the versions used for the two reporting cutoffs. Finance can publish a monthly amount after its close process, while growth can date its channel report by the export time. Record each later channel refresh as a dated update, preserving the report version and the attribution settings in effect at that time.

5. Define the measures in plain language

Revenue attribution assigns credit for a recorded revenue event to a campaign or acquisition touchpoint under a named attribution model, event rule, identity match, and time window. An attributed-revenue report is useful for asking which paid channel is associated with the subscriptions and subscription payments represented by that report.

A data discrepancy is a difference between two reported values that appears when the values are compared. To explain it, compare what each value measures, which records and time periods it includes, and how the source applies timing, refunds, and attribution. Reconciliation compares definitions, time periods, source records, and attribution settings to locate the cause of the difference.

For the monthly report, keep the distinction short and repeatable: finance owns the approved financial measure, and the attribution view supports campaign-performance analysis. Name each figure, show the reporting basis, and document the variance until the records and rules explain it.

Related reading

When Does an App Need an MMP? Mobile Attribution Guide

September 18, 2026

Adjust Alternatives for Lean App Teams (2026): Self-Serve Plans, Monthly Billing, and Low-Volume Pricing

September 18, 2026

Subscription Revenue Attribution: How to Connect In-App Purchases, Trials, and Renewals to Ad Campaigns

September 18, 2026