To start the BSP reconciliation process, you need to import a BSP file.
You can also search for tickets in existing BSP files.
Requires activation. After the file is imported, if relevant, you can export the data for a specific branch.
Exporting data for a specific branch requires that the users in the file be correctly mapped to the users in Travel Booster. If there are users who are not mapped correctly, tickets belonging to those users will not be included in the exported file. |
Go to Financial – BSP Reconciliation - BSP Data.
Next to the File field, click Browse.
Open the file you want to import.
To import only BSP tickets that belong to a specific branch with a IATA number: In the IATA No. field, enter the IATA number of the branch.
In the File Date field, select the file import date.
If you are importing a file retroactively, or importing multiple files in the same day, you can select a different date for each file, allowing you to use the File Date parameter to search for records from different files. |
Click Import.
The BSP data is imported and automatically compared to the data in the system.
After the import, an e-mail is sent to the user logged into the system that the import is completed and the number of rows imported. If there are any tickets that the system fails to match, a *.txt file is created by the system listing the tickets and the reason they could not be fully matched.
When importaing a BSP file in the BSP reconciliation module, the system initializes the IATA number and file date according to the BSP file parameters. When clicking the Browse button and choosing a BSP file, the system checks the IATA number and date period in the file and initializes it accordingly. As the BSP file is received once a week, it contains a week period parameter such as "190201". This means that the file period is for the first week of February 2019. Therefore, when importing it into the system, the File Date parameter in Travel Booster is set to 01FEB19. Similarly, the value "190202" means that the file period is for the second week of February and therefore the File Date value is set to 08FEB19 and so on. |
Go to Financial – BSP Reconciliation - BSP Data.
Use one or more of the following search parameters:
Field |
Description |
Value date/Until |
Select the date range of the vouchers. |
File Date/Until |
Select the date range of the BSP statements file dates. |
From Ticket |
Enter the first ticket number in the range. |
To Ticket |
Enter the last ticket number in the range. |
Supplier |
Select the airline from the drop-down list. |
Select one of the following ticket statuses:
Option |
Description |
All |
Display all tickets |
Matched Only |
Display only tickets in which all amounts and the currency match |
Pending |
Display tickets that are not matched |
Click Find.
The BSP data and the corresponding system data is displayed in the results section.
The following values are displayed in the results section:
Values |
Description |
Date |
Date of the voucher as indicated by BSP |
AL #/AL code |
In this column you can select to display the following information:
|
Ticket # |
Number of the ticket as indicated by BSP |
Currency |
Currency of the transaction as indicated by BSP |
Amount Cash |
Amount of the ticket as indicated by BSP |
Amount Credit |
Credit amount deducted from the amount as indicated by BSP |
Tax Cash |
Amount of tax charged for the service as indicated by BSP |
Tax Credit |
Amount of tax credit as indicated by BSP |
% Commission/ |
Percentage or absolute amount of commission granted for selling the service as indicated by BSP |
Net to Remit |
Net amount of remittance payment as indicated by BSP |
Type |
Type of ticket as indicated by BSP |
Go to Financial – BSP Reconciliation - BSP Data.
In the Export BSP File section:
In the File Date fields, enter the date range of the information you want to export.
In the Branch field, select the branch for which you want to export data.
Click Export.
A BSP file is exported with the data for the branch you selected. This file can be imported into the database of that branch and be used for that branch's local reconciliation purposes.