- Introduction
This document describes the workflow for the development/new feature "SIC - New BSP Reconciliation".
- Ticket Error List
The ticket error list is a kind of control tool to find out if the prices in DaVinci correspond with the price information of the tickets. In generally it has no direct influence on the BSP reconciliation, but should be used to check the consistence of the data entered in DaVinci. Bewotec recommends checking this list on a daily basis, by ticketing date as a kind of queue.
<Bookings> <Ticket error list>
As the SIC deals with purchase prices it is very important to use the ticket error list for identifying any issues between ticket information and booking information.
With choosing this menu the following window will be opened:
Ticket-data for visualization purposes:
The following prices will be compared:
DaVinci/Genesis Prices |
Ticket Data |
Sales Fare |
Equivalent Fare |
Sales Tax |
Tax |
Purchase Fare |
Net Fare |
Purchase Tax |
Tax |
The following errors are possible within the ticket error list:
Error Message |
Description |
Duplicated ticket |
Ticket Number with same ticket type has been found more than once in DV database |
Missing previous ticket |
If ticket stock is used, sequence of ticket number is not correct (NEW selection criteria) |
No participant assignment |
Passenger Assignment missing, passenger not entered |
Invalid participant assignment |
Passenger Assignment invalid, passenger does not match with passenger in Genesis |
No sales price found |
No sales price found in Genesis |
No purchase price found |
No purchase price found in Genesis |
No sales tax found |
No sales tax found in Genesis |
No purchase tax found |
No purchase tax found in Genesis |
Ticket Fare unequal sales price |
Either ticket fare higher than sales fare or less than sales fare (variance) |
Ticket tax unequal sales tax |
Either ticket tax higher than sales tax or less than sales tax (variance) |
Ticket Net Fare unequal purchase price |
Either ticket net fare higher than purchase fare or less than purchase fare (variance) |
Ticket tax unequal purchase tax |
Either ticket tax higher than purchase tax or less than purchase tax (variance) |
Too many purchase prices found |
More purchase prices in Genesis with same ticket assignment than in ticket. (either same booking or different bookings) |
Too many sales prices found |
More sales prices in Genesis with same ticket assignment than in ticket. (either same booking or different bookings) |
Too many purchase taxes found |
More purchase taxes in Genesis with same ticket assignment than in ticket. (either same booking or different bookings) |
Too many sales taxes found |
More sales taxes in Genesis with same ticket assignment than in ticket. (either same booking or different bookings) |
All errors which will be found in the ticket error list should be corrected. As DaVinci recognizes the fare and tax information by a database flag called "Price_is_Tax" it is absolutely necessary that this flag will be set correctly by Netrom/POS.
Please note: The flag can not manually entered/changed via Genesis!
- Import of BSP Data
Before anything can be reconciled the BSP invoice needs to be imported to DaVinci. To do so, please chose the following menu: <Import/Export> <Import BSP Data...>
You will get to the following screen:
Chose <Import data>
Please fill in all necessary data and chose the file name and path and click on import.
For test purposes the BSP invoice of CNX has been split so that just a few invoice lines have been imported:
With chosing the button <Report> you get a statistic of the BSP and ticket information:
The amount on the tab total will be used for the creation of the supplier invoice:
With chosing the button <Change error> you will get to the BSP error list. Within this feature Bewotec compares the invoice information of BSP with the entered ticket information in DaVinci.
- BSP error list
The following errors are possible within the BSP error list:
Error Message |
Description |
Ticket not found |
Ticket can not be found in DaVinci |
Fare unequal |
Fare of BSP invoice and DaVinci ticket information does not match |
Tax unequal |
Tax of BSP invoice and DaVinci ticket information does not match |
Commission unequal |
Commission of BSP invoice and DaVinci ticket information does not match |
Amount of conjunctions unequal |
Amount of conjunctions of BSP invoice and DaVinci ticket information does not match |
Currency unequal |
Currency of BSP invoice and DaVinci ticket information does not match |
Cash unequal |
Cash amount of BSP invoice and DaVinci ticket information does not match |
Credit unequal |
Credit amount of BSP invoice and DaVinci ticket information does not match |
Tax on Commission unequal |
Tax on commission of BSP invoice and DaVinci ticket information does not match |
Airline does not match |
Airline of BSP invoice and DaVinci ticket information does not match less than sales tax (variance) |
Ticket type unknown |
Ticket type of BSP invoice unknown |
Ticket type might be different (Booking xxx) |
Ticket type of BSP invoice and DaVinci ticket different, booking number will be mentioned. |
Wrong reconciliation period |
Ticket issuing date does not match with the reconciliation period. |
Once all errors have either been corrected or accepted, the BSP error list can be closed and the data handed over to SIC.
As we discussed in one of our last meetings, up to this point "Operations" will deal with the ticket error list and the BSP error list. As soon as "Accounts" will get the <OK> from "Operations" they will take over.
- Supplier Invoice Control
With highlighting one invoice and choosing the menu <Supplier Invoice Control> the system will automatically create a supplier invoice and hand over the corresponding data to the SIC.
The amount of EUR 3.164,43 will be suggested by the system automatically (Statistic, payable amount).
With pressing the <OK> button the invoice will be entered and the matching of the purchase prices will be done. This might take a while as the matching and assignment will be done for each single fare and tax of a ticket.
The system matches the fare and tax line. If there is a difference for each single ticket and fare or tax line a DIF line will be generated. Additionally a NEW price line will be generated if the invoice amount does not match with the ticket, fare and DIF amounts.
E.g. a ticket is not entered in DaVinci. Matching can not be made, therefore NEW price line.
In this example the NEW amount is quite high as the test has been made several times already...
Posting part needs to be added: BEDEV00034823