The BSP Auto Reconciliation is a powerful tool which compares what BSP expect to what your back office system expects, this can highlight any differences between the two, and allow the user to act upon those discrepancies.
To use this option it must be configured in a number of places.
Firstly in Options / Tools -> Global Options -> INOP0S, The highlighted options must be ticked.
Without leaving Global Options, switch to the Interface Tab (Shown Below)
On the interface tab toward the bottom of the form is the BSP Auto Reconciliation section. The options are described in detail below:
BSP
Reconciliation Available
This option MUST be used in conjunction with the INOP0S -> BSPRecon flag
to fully enable auto BSP processing. This feature should not be used without
prior consultation with Micros|Travel
File Mask (Free text)
Advanced feature for BSP reconciliation, the file mask will be applied by Micros|Travel
upon installation, an incorrect file mask will undoubtedly cause the BSP reconciliation
to cease working.
Test Mode
Initiates an advanced test / debug version of the Reconciliation.
Eire
Sets the BSP Recon to Ireland mode. Some changes like currency etc.. are included.
Ignore Date Mismatch
Allow dates of ticket payments and standard payments to not match, if this option
is not ticked
then any variances will be highlighted.
Number of Days to ignore
Linked to the above option "Ignore Date Mismatch" this is the amount
of time in days to accept
between ticket and standard payments. It is recommended that the User experiment
with this option to find a setting which suits the business procedures of the
company in question. Past experience has shown that often clerks will issue
the ticket a day or two later than BSP actually expect.
Once this has been configured, reboot Traveller and you will see that a new option is available at the top of the screen:
Selecting this option shows the following menu : (Click on an option to jump to the section)
If the user has allready
processed a file and saved it, then it may be recalled for reconciliation
again.
Return to menu
Processess a brand new hotfile ready for reconciliation, once this file has been created it can be saved. Steps to complete this procedure are explained below.
The screenshot above shows an example file being opened, by clicking on the [...] button you can define which hotfile to open. A hotfile is a file which BSP provide outlining all interactions between yourselves and them.
Once a file has been selected you have the option to process:
By clicking Process you ask Traveller to prepare the hotfile for it's reconciliation, once prepared the file can be saved:
Clicking Save will present you with a standard windows save dialog box:
Once saved you are ready
to reconcile. Remember to save the file in an area you can return to in order
to perform the reconciliation.
Return to menu
This option will reconcile the most recently processed hotfile and is a step which is normally carried out after processing a new file or loading an exisitng file. The steps involved are outlined below.
If you have just processed a file then you will see this file in the top section of the above window, clicking Process will begin the reconciliation, this may take some time dependant on the speed of your machines and network, please be patient.
Once the reconciliation process is complete a printout is presented and you will have a selection of views to choose from to dynamicly reorder the data. (shown below, click for zoomed view)
 |
 |
 |
| View
by Transaction Type |
View
by Ticket Number |
View
by Error |
Which view is suitable for you is something you will need to explore yourself, the simplest view to use is by error, as it breaks down each problem type and shows the tickets with the corrisponding problem. A list of such errors is shown below with a brief explination:
Commission Mismatch:
Commission mismatches are broken down into two sections, under £1 and
over £1, both sections are very self explanatory.
Credit Card
Number Mismatch:
The credit card number in the BSP hotfile does not match that which is stored
in Traveller, this, dependant on company procedure is not normally an issue.
Issue Date Mismatch:
Possibly the largest section in most scenarios. Without "Ignore
Payment Mismatches" unchecked then you may notice that many tickets
are returned, however this rule can be slackend to suit what the user deems
as an acceptable period of time.
Multiple Tickets Found:
If more than a single ticket is found in Traveller for a given ticket number
then this error is displayed, remove all but one of these tickets to resolve.
Payment Amount
Mismatch:
In most circumstances this will be the most important section of the reconciliation
for any company. This section highlights where BSP expect a particular amount
of money, and Traveller expects to be giving BSP a different amount, any discrepencies
in this area should be resolved immediatly. Check your booking, it's tickets,
payments and documentation to ensure everything is in order.
Payment Allocation
Mismatch:
Not as dire as the payment amount but could still be of concern, this section
highlights all bookings which although the payment amount could be ok, the allocation
of that amount is incorrect. For example, BSP may report that a ticket was paid
for £50 Cash and £100 Visa, this could then be reported as £75
Cash and £75 Visa in Traveller, this booking would appear under this section.
Tax Amount Mismatch:
Another important section, the BSP hotfile will outline that the company is
paying a particular amount of tax, if Traveller does not agree then the ticket
will appear under this section. As above check the ticket and documentation
carefully to ensure accuracy.
Tax Allocation
Mismatch:
As with payment allocation mismatches, a ticket under this section may have
a different tax breakdown to that which BSP report.
Ticket not found:
Quite simply a ticket outlined in the BSP hotfile does not exist within Traveller.
Return to menu
This option will load
a previously reconciled file, saved in this section.
Return to menu
