For cross border taxation to function correctly, it must be configured in 3 sections within the backoffice before it can be used.

The Enable cross-border taxation (Optional) is for multi country operators that only apply taxes in one jurisdiction, but is considered experimental at this time.

If you disable the product it means it will not be available in any of the sales pages, but the name will still show up in some combo boxes across the application to allow you to access historical data.

Is border: See Cross border taxation config section.

The simulation includes all vehicles that departed prior to the date of travel and which will cross over into the date of travel.

Locate the service type you want to delete using the list and click the red cross at the right.

This options will allow to scan open tickets for the reverse O & D. Cross product redemption must be enabled.

This will help avoid cross site scripting attacks.

Para usar esta configuración, debe [** Habilitar los impuestos a la borda transversal **] (/content/admin/10_account_preferences#habilitar-cross-border-taxation), una vez hecho, aparecerá 3 nuevas opciones. Después de eso, debe seleccionar la opción Configuración básica de impuestos a transmisión transfronteriza.

Para usar esta configuración necesitas Enable cross border taxation, una vez hecho esto aparecerán 2 nuevas opciones:

Click on the "RED" cross on an associated terminal and it will remove the association.

The name will also be used in combo boxes across the application (for example: report filters).

If you disable the product it means it will not be available in any of the sales pages, but the name will still show up in some combo boxes across the application to allow you to access historical data.

• Create a bucket. This name has to be unique across S3. DNS name is recommended (e.g com.mydomain.betterezbucket). You can select many advance option, but for this tutorial, leave all as is (use default).

You can also filter tickets and journeys by product. Notice that across the top of the transactions and tickets graph, you see 3 metrics: Number of items sold in the selected duration, Total revenue collected in the selected duration, Average price per Ticket or per Transaction. For the Tickets per Channel chart, you will see the total revenue for each channel, for the selected duration, and product.

Closing the sales confirmation page too quickly in Web Sales does not prevent the confirmation email from being sent. Tests across different email providers, including Outlook (Personal & Corporate) and Gmail (Personal & Corporate), confirmed that the email is received normally even when the page is closed immediately after purchase.

The name will also be used in combo boxes across the application (for example: report filters).

• This is an example of the report filtered with the “Toronto – NYC 06:00” schedule, it shows 4 no shows across all the tickets on the selected period of time.

The name will also be used in combo boxes across the application (for example: report filters).