Exchanging Tickets

You can exchange one or more old tickets for a new ticket if the exchange was not created by the Interface.

GlobalWare processes an exchange by changing the new ticket item into a ticket less the exchange item (thus only one item). If there is a penalty on the exchange, it is added to the Penalty field on the exchanged invoice item.

  1. Before beginning the exchange process, make sure the new ticket has interfaced in from the CRS. If not, manually enter the new ticket. The new ticket should be entered as any new ticket that is not being exchanged (fares should not be net of old ticket being exchanged).

  2. With the new ticket being displayed, click EXCHANGE to begin the exchange process.

    The Refund/Exchange dialog box appears.

  3. Complete the old ticket number(s), the penalty, and the penalty commission (if applicable). The new ticket number, passenger, Account ID, Agency #, Form of Payment, Submit Date, and new ticket number and costs are filled out for you on the Refund/Exchange dialog box. For information about the Refund/Exchange dialog box, see Using the Refund/Exchange Dialog Box.
  4. Enter the old ticket number(s) for the exchange. The amounts are automatically calculated for you based on the old ticket’s fares. If the old ticket was non-refundable, adjust the amount of the net exchange and net commission manually by adjusting the Penalty Fee amount and the Penalty Commission. For instance, if there is a lost fare of $100.00 and a penalty of $50.00, enter $150.00 as the Penalty Fee amount.
  5. After completing the exchange, click OK.

After you exchange, GlobalWare changes the status of the invoice item for the original ticket to E (exchanged) and stores the new ticket number in comment line 116. On the new ticket, the original ticket number is stored in the Savings Comment field.

Note: Because a ticket can be exchanged more than once, multiple ticket numbers can be stored in comment line 116. Up to 5 ticket numbers will be stored. If you change the new ticket number, comment line 116 on the original ticket is not updated; you must change this manually.