Docs / Capability guide
Fees, invoices, payouts and reconciliation
Compare publisher revenue, demand costs, and platform charges.
All capabilities · Related guide · Agent prompt for this capability
When to use this example
Before closing a statement period, finance teams need to understand why revenue, fees and amounts due differ. Compare records for the same currency and period so a timing mismatch is not mistaken for a pricing error.
What the example gives you
The inspector reads fee schedules, usage records and invoices as JSON. These are inputs for your reconciliation; statement comparisons and financial adjustments use the authorized workflows described below.
Before you start
Billing/report permissions and known statement periods/currencies. Settlements and financial mutations need the designated authorized operator.
Run the example
Extract the archive and follow README.md for setup, commands, and expected results. Start with workspace_inspect.py. Local tests use sample data.
Python tools accept --help. To connect to your workspace, supply the deployment URLs, credentials and resource IDs required by the tool.
Connect it to your application
Inspect fee schedules and use previewFeeSchedule on proposed terms before saving them. Keep money as decimal strings and distinguish publisher payouts from demand-side fees.
Read usage, invoices and payout statements for the same period. Check prepaid/quota state separately from delivery metrics; reseller rollups must not double-invoice children.
Import counterparty statements into reconciliation, run a comparison and review adjustments. Settlement and credit creation are financial actions; the inspector only reads configuration and results.
Check the result
Revenue, fees and payable amounts reconcile in one currency and period. Flag unexplained differences for review before adding adjustments.