Currency Reporting

Kaptio Travel can report on a variety of monetary data across multiple selling currencies with different currency settings and conversion rates.

Business Unit Currency & Corporate Currency reporting fields in Kaptio Travel

In Kaptio Travel the Business Unit Currency (BCY) fields represent the currency amount in he Business Unit’s base currency (BCY). The Corporate Currency (CCY) fields represent the currency amount in the Global Reporting Currency (CCY).

All fields related to an Itinerary, costings line or payment transaction have these special reporting fields, so you can report on all Itineraries in a base currency based on the conversion rates at the time of quoting, booking or travelling.

BCY fields are useful for reporting on all Itineraries linked to a specific Business Unit or across multiple Business Units with the same base currency.

CCY fields are useful for reporting on Itineraries relating to a single reporting currency, even though they are linked to different Business Units with different base currencies.

The BCY and CCY fields are part of Kaptio Travel’s currency framework that allows a more advanced setup of currency rules for travel businesses. Included are live currency support, buffering, currency settings and using conversion rates based on the quotation or travel date. Salesforce does not support these features by default.

Salesforce static currency reporting

Salesforce’s default currency support is based around static conversion rates that change each time conversion rate data is updated in the Conversion Rates setup: Setup > Manage Currencies > Conversion Rates. This means that businesses cannot accurately report on any selling prices in other currencies based on the conversion rates on the day of collecting payment for a booking.

Salesforce’s static currency reporting can be useful for analysis of selected booking data using static conversion rate assumptions, but it is not accurate enough for financial reporting. For more information on Salesforce currency reporting, please refer to the following Salesforce help articles: