Report currency and FX for app revenue data

What report currency means

In Netice app revenue outputs, report currency is the configured presentation currency used for selected analytics or finance fields. For example, a task may use EUR as the report currency so downstream teams can compare Apple App Store and Google Play revenue in one reporting currency.

Report currency is not the same thing as the provider’s source currency, payout currency, merchant currency or customer charge currency. Netice keeps native/source context visible where the output family supports it. This matters because app stores can report amounts in different currencies, with different fee visibility, different tax behavior and different report families.

A safe mental model is: native values preserve provider context; report-currency values support analysis and presentation. You should not use report-currency fields without reading the source report, method fields, FX fields and output-family boundary.

Native currency vs report currency

Native/source currency is the currency context coming from the platform report or the platform-side economic event. Report currency is the currency selected for customer-facing presentation fields. Both can be useful, but they answer different questions.

Daily App Sales currency fields

Daily App Sales uses the google_apple_app_sales workflow. It is the daily operational analytics layer for Apple App Store and Google Play sales-style reporting. The current daily schema evidence uses fields such as report_currency, estimated_gross, estimated_net, estimated_tax and estimated_fee for report-currency analytics.

Daily App Sales also preserves native/local context through fields such as native_currency, gross_local, net_local, tax_local and fee_local. Apple-specific proceeds context can appear in apple_proceeds_currency and apple_proceeds_native. These Apple fields should not be flattened into Google rows.

The current daily layer uses component-specific FX fields: gross_fx, net_fx, tax_fx and fee_fx. It should not be documented as having one generic public daily fx_rate column.

Apple and Google daily source differences

Apple and Google Play do not expose identical daily report facts. Netice keeps that difference visible instead of pretending that every amount has the same source truth.

Apple Summary Sales does not itemize commission and tax in the same way a finance ledger would. Daily Apple fee and tax values therefore need method context. Google Play Estimated Sales does not itemize service fee like Google Play monthly Earnings. Google tax can be source-truth when taxes collected are present and tax_method says so, but that should not be generalized to every tax value.

Finance Unified currency fields

Finance Unified is separate from Daily App Sales. It is the monthly platform finance output for Apple financeReports and Google Play Earnings where configured. Its rows use source_kind = 'FINANCE' and preserve native finance values separately from report-currency presentation fields.

In Finance Unified, unknown finance values remain null. Real zero remains zero. Missing cross-currency FX does not become rate 1. That distinction matters because fake zeros and fake FX rates can corrupt finance review logic.

Same-currency and missing cross-currency FX

Same-currency conversion is straightforward: if the native currency and report currency are the same, the finance FX rate can be 1. Cross-currency conversion is different. If a required FX rate is not available, finance report-currency fields should remain null or be surfaced as a quality issue rather than silently producing fake amounts.

Raw reports do not use report currency or FX conversion

Raw Reports are provider-native artifacts. They are separate from Daily App Sales and Finance Unified. Raw report output does not apply report currency, currency normalization, FX conversion, fee methods or tax methods.

This is an important product boundary. If you need source-native provider files, use Raw Reports. If you need daily report-currency analytics, use Daily App Sales. If you need monthly finance-period rows with native and report currency fields, use Finance Unified where configured.

Null-not-zero behavior

In finance output, null is not zero. Null can mean unknown, unavailable, unsupported, not disclosed or not applicable. Zero means a known zero. Treating these as the same can create false finance facts.

Google Play Earnings fee or tax rows can have null customer-charge fields because those rows are not customer charge events. Apple finance output should not fabricate separate Apple commission or tax rows when Apple does not disclose those as separate finance facts. Missing cross-currency FX should not become a fake zero amount.

Safe synthetic examples

The examples below are synthetic. They show the relationship between report currency, native currency, FX and null handling without using real app IDs, SKUs, source rows, object paths, datasets, tables, hashes, task IDs, logs or customer data.

Daily App Sales example row

revenue_date,platform,app_id,source_kind,source,country,report_currency,estimated_gross,estimated_net,estimated_tax,estimated_fee,native_currency,gross_local,net_local,tax_local,fee_local,gross_fx,net_fx,tax_fx,fee_fx,net_method,fee_method,tax_method,data_completeness,source_report,event_has_revenue,item_id,source_row_hash
2026-02-10,ANDROID,com.example.app,SALES,GOOGLE_PLAY,US,EUR,9.990000,6.990000,1.500000,1.500000,USD,10.990000,7.690000,1.650000,1.650000,0.909000,0.909000,0.909000,0.909000,GOOGLE_ESTIMATED_NET_FROM_CHARGED_AMOUNT_MINUS_ESTIMATED_FEE,GOOGLE_ESTIMATED_FEE_30PCT_FROM_SOURCE_STANDARD,GOOGLE_TAXES_COLLECTED,T_PLUS_2_STABILIZED,GP_ESTIMATED_SALES,true,premium_monthly,synthetic_hash_google_001

Finance Unified same-currency example

platform,source,source_kind,source_report,fiscal_period,app_id,sku,event_type,native_currency,native_net_proceeds,native_customer_charge,report_currency,report_net_proceeds,report_customer_charge,fx_rate,source_row_hash
ANDROID,GOOGLE_PLAY,FINANCE,GOOGLE_PLAY_EARNINGS,2026-02-01,com.example.app,premium_monthly,SALE,EUR,7.000000,7.000000,EUR,7.000000,7.000000,1.000000,synthetic_finance_hash_001

Finance Unified missing cross-currency FX example

platform,source,source_kind,source_report,fiscal_period,app_id,sku,event_type,native_currency,native_net_proceeds,native_customer_charge,report_currency,report_net_proceeds,report_customer_charge,fx_rate,source_row_hash
IOS,APPLE_APP_STORE,FINANCE,APPLE_FINANCE_DETAIL,2026-02-01,com.example.app,premium_monthly,SALE,USD,6.990000,9.990000,EUR,,,,synthetic_finance_hash_002

Daily report-currency analytics query

SELECT
  revenue_date,
  platform,
  report_currency,
  source_report,
  SUM(estimated_net) AS estimated_net_report_currency
FROM `example_project.example_dataset.app_sales_daily`
WHERE revenue_date BETWEEN DATE '2026-02-01' AND DATE '2026-02-28'
  AND source_kind = 'SALES'
GROUP BY revenue_date, platform, report_currency, source_report
ORDER BY revenue_date, platform, source_report;

Finance FX coverage query

SELECT
  fiscal_period,
  platform,
  report_currency,
  COUNTIF(native_net_proceeds IS NOT NULL AND report_net_proceeds IS NULL) AS rows_missing_report_net
FROM `example_project.example_dataset.finance_unified`
GROUP BY fiscal_period, platform, report_currency
ORDER BY fiscal_period, platform;

The daily query is for operational analytics. The finance query is a coverage check. Neither query is accounting close, payout reconciliation, tax advice or audit evidence.