> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://learn.nuwebgroup.com/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://learn.nuwebgroup.com/_mcp/server.

# How do multi-country ticketing teams standardise reporting without losing local detail?

> Shared reporting metrics across currencies, venues, taxes and operating models.

**Multi-country ticketing teams need common definitions for core metrics while preserving the currencies, tax treatments, event dates and operating entities that make each local transaction meaningful.** Central reporting can compare sales and demand across countries, but it should not flatten everything into a converted revenue figure with no audit trail.

## Which metrics should be standardised?

Agree whether sales mean completed paid orders, issued entitlements or transactions before refunds; these differ. Define inventory available versus held, tickets scanned versus sold, gross price including fees, net proceeds after refunds and processor costs, and sales date versus performance date.

| Shared field             | Local detail to retain                         |
| ------------------------ | ---------------------------------------------- |
| **Ticket count**         | Event, item, entitlement and status            |
| **Gross sales**          | Original currency, fee structure and tax       |
| **Refunds**              | Date, method and original sale reference       |
| **Net settlement**       | Processor, payout date and settlement currency |
| **Event demand**         | Venue time zone, onsale stage and capacity     |
| **Customer acquisition** | Consent and tracking policy by jurisdiction    |

## How should currency conversion be handled?

Keep original monetary values and record the rate, rate source and conversion date used for group-level reporting. Actual processor payouts may use a different rate. Do not confuse translated management dashboards with statutory accounts; local financial statements can require separate methods and controls.

## How can teams avoid duplicate counting?

A distributed ticket network can have imported allocations, reseller orders, cancellations and transfers. Define a unique transaction or ticket identifier and canonical event status. A transfer should not become a second sale; an external sale may need separate revenue recognition rules. Reconcile group aggregates back to local provider statements and event audit records.

**Example:** An international venue group runs a London exhibition and a Hong Kong arena event. Senior management can compare conversion, attendance and capacity utilisation, but currency-adjusted revenue should retain each original currency, applicable fees and event dates in the drill-down.

## How should multi-country ticketing reporting be governed?

Maintain one metric dictionary, ownership of data sources, versioned transforms, exception logs and scheduled finance sign-off. Decide which fields are accessible to group analysts and which require venue-level restrictions. Automate extraction only after source event and transaction definitions are stable.

**Related reading:** The existing event audit report, automated exports and transaction reconciliation articles explain the component workflows; this page focuses on cross-market standardisation.

## Related explanations

#### [What should a ticketing company consider before entering a new country?](/scale-reliability/what-should-a-ticketing-company-consider-before-entering-a-new-country)

Scale & Reliability · International operations

#### [How do international ticketing businesses manage data residency and cross-border access?](/scale-reliability/how-do-international-ticketing-businesses-manage-data-residency-and-cross-border-access)

Scale & Reliability · International operations

#### [How do ticketing platforms support different languages and locales?](/scale-reliability/how-do-ticketing-platforms-support-different-languages-and-locales)

Scale & Reliability · International operations

[More in Scale & Reliability →](/scale-reliability)