How Commission Reconciliation Finds Matches
Commission Reconciliation provides a standard matching method using a set list of fields, and an optional method where you select which fields to match on. If you want to use the optional method, it is recommended that you first reconcile using the standard method, and then select fields to reconcile the remaining ones.
Generally, standard matching checks Traveler last name, chain code, and confirmation number; then Traveler last name, chain code, and start date. Items that are voided or already marked received are always excluded from standard and option matching. Details about matching are provided below.
Optional Matching
Optional matching is useful for situations such as:
- The GDS sends one chain code to GlobalWare (for example, SI for Sheraton), but the reconciliation company sends a different one in the file (4P for Sheraton Four Points) for the same booking.
- The traveler name in GlobalWare is in lastname/firstname format, but the reconciliation company does not require chains to use a standard format and so some names are in firstname lastname format.
Notes:
- If you want to use the optional method, it is strongly recommended that you first reconcile using the standard method. Then, use optional matching then select fields to reconcile those left.
- When using optional matching, select as many fields to match on as possible. For example, if you match on only chain and start date, the likelihood of incorrect matches is much higher.
With optional matching, you can select from the following list of fields ("Chain" through "Traveler last name"):
This list of fields appears when you select Reconcile Transactions and Optional Match on the Commission Reconciliation screen. To access the Commission Reconciliation screen, see Using the Commission Reconciliation Screen.
To match on a field, select it and click the > button. You must select at least two fields.
For confirmation number, you can use an exact match (the fields in GlobalWare and the file must be exactly the same) or an inexact match (*xxx*). For example, if the GlobalWare confirmation number is 123456 and the file confirmation number is 123456GOLD, an inexact match will consider them as matching.
Standard Matching Cars and Hotels, Onyx HCC, Paymode-X, and TACS
For cars and hotels, Commission Reconciliation selects GlobalWare items with settle type T (tracking), status <> V (not void), and no commission received and then attempts to match the following information:
GlobalWare | Onyx/Paymode-X |
---|---|
Traveler |
Client Name |
Chain Code |
Chain Code |
Confirmation Number (ticket number field) |
Confirmation Number |
If a match is not found, GlobalWare tries again using the following information:
GlobalWare | Onyx/Paymode-X |
---|---|
Traveler |
Client Name |
Chain Code |
Chain Code |
Departure Date |
Departure Date |
For information about how GlobalWare matches Onyx ERTS transactions, see Import and Reconcile Onyx (ERTS).
Standard Matching Tours and Cruises, Paymode-X
For tours and cruises, Commission Reconciliation selects GlobalWare items with settle type I (invoice) or T (tracking), status <> V (not void), form of payment P (plastic), and no commission received, and then attempts to match the following information:
GlobalWare | Paymode-X |
---|---|
Traveler |
Client Name |
Provider |
Chain Code |
Confirmation Number (ticket number field) |
Confirmation Number |
If a match is not found, GlobalWare tries again using the following information:
GlobalWare | Paymode-X |
---|---|
Traveler |
Client Name |
Provider |
Chain Code |
Departure Date |
Departure Date |
Standard Matching Air, Paymode-X
For air, Commission Reconciliation selects GlobalWare items with settle type I (invoice) or T (tracking), status <> V (not void), form of payment P (plastic), and no commission received and then attempts to match the following information:
GlobalWare | Paymode-X |
---|---|
Traveler |
Client Name |
Airline |
Chain Code |
Ticket Number |
Confirmation Number |
If a match is not found, and the airline is Southwest, another attempt is made using the following information:
GlobalWare | Paymode-X |
---|---|
Traveler |
Client Name |
Airline |
Chain Code |
Ticket Number |
PNR Locator |
(When you book Southwest e-tickets directly with Southwest and interface through Apollo using the handwritten ticket procedure, you enter the Southwest "confirmation number", which is actually the ticket’s PNR locator in Southwest’s system.)
If a match is not found, GlobalWare tries again using the following information:
GlobalWare | Paymode-X |
---|---|
Traveler |
Client Name |
Airline |
Chain Code |
Invoice Date |
Departure Date (for airlines, ticketing date is stored in this field) |
Base fare |
Revenue |
After reconciling Paymode-X air items with GlobalWare tickets, Commission Reconciliation looks for Paymode-X items with the same ticket number and offsetting commissions (for example, $4.73 and -4.73) and marks them reconciled. These appear on the reconciled report with status "OF" in the "no location" section (the location is the GlobalWare item location, and these do not match to a GlobalWare item).
Standard Matching, Generic
For all travel types, Commission Reconciliation selects GlobalWare items with settle type I (invoice) or T (tracking), status <> V (not void), form of payment P (plastic), and no commission received, and then attempts to match the following information:
GlobalWare | Generic |
---|---|
Traveler |
Traveler |
Provider |
Provider |
Confirmation Number (ticket number field) |
Confirmation Number |
If a match is not found, GlobalWare tries again using the following information:
GlobalWare | Generic |
---|---|
Traveler |
Traveler |
Provider |
Provider |
Departure Date |
Start Date |