Passenger Solutions

SITA Airfare Price

Introduction to SITA Airfare Reprice/Refund Including
Category 31, Voluntary Changes, and
Category 33, Voluntary Refunds

Revision 1.0
Revision Date: 2009-Nov-18

1
Copyright SITA Information Networking Computing

USA Inc 2009. Confidential. All Rights Reserved.

2
Copyright SITA Information Networking Computing

USA Inc 2009. Confidential. All Rights Reserved.

Copyright Notice
Copyright SITA Information Networking Computing USA Inc 2009
Confidential Information
All Rights Reserved

The information contained in this document is the property of SITA. No part of this
document may be reproduced, stored in a retrieval system, or transmitted in any form, or
by any means; mechanical, photocopying, recording, or otherwise, without the prior
written consent of SITA. Under the law, copying includes translating into another
language or format. Legal action will be taken against any infringement.
The information contained in this document is subject to change without notice and does
not carry any contractual obligation for SITA. SITA reserves the right to make changes
to any products or services described in this document at any time without notice. SITA
shall not be held responsible for the direct or indirect consequences of the use of the
information contained in this document.

3
Copyright SITA Information Networking Computing

USA Inc 2009. Confidential. All Rights Reserved.

Table of Contents
What is a voluntary change and refund?............................................................................................
SITA's Airfare Reprice/Refund (ARR) provides the following benefits:...........................................
SITA Airfare Reprice/Refund (ARR) contains 3 new transactions....................................................
ARR "Can my ticket be reissued/" Processing Details.....................................................................
ARR Reprice Processing Details.........................................................................................................
ARR Refund Processing Details..........................................................................................................
SITA ARR Requires the following data for Reprice/Refund............................................................
Lets break it down Category 31 and Category 33...........................................................................
Basic Reissue and Refund Processing............................................................................................
Processing Flow Chart for Category 31 Reissues...........................................................................
Voluntary change information can be divided into major sections as detailed below.................
Processing for Category 31...............................................................................................................
Currently Airfare Reprice Reissue processes the following tags:.................................................
Category 31 rules text mapped to bits/bytes....................................................................................
Processing Flow Chart for Category 33 Refund..............................................................................
Voluntary refund information can be divided into major sections as detailed below...................
SITA Airfare Reprice Refund processing options............................................................................

4
Copyright SITA Information Networking Computing

USA Inc 2009. Confidential. All Rights Reserved.

SITA Airfare Reprice/Refund (ARR)

SITA Airfare Price is pleased to present category 31, Voluntary Changes and
category 33 voluntary Refund.

What is a voluntary change and refund?

A voluntary change is a change in the ticketed itinerary:

That the passenger requested,

Where there is a replacement itinerary, and

Where the ticket is reissued/revalidated

A voluntary refund is a change in the ticketed itinerary:

That the passenger requested,

Where there is no replacement itinerary, and

Where the ticket is refunded or discarded (no value) -Or -

Where Category 31 (Voluntary Changes) has rendered the ticket invalid for
continuing transportation.

Category 31 (voluntary change) and category 33 (voluntary refund) will allow you to
file your carriers voluntary itinerary change and refund rule provisions. This allows
the Airfare Reprice/Refund (ARR) product to apply those rules to the customer's
previous ticket and determine the fares for the new ticket, the applicable change
fee or cancellation fee amount, and any resulting add-collect or refund amount.
This automation will allow the process of the reissue or refund to take less than 2
minutes instead of the 25-30 minutes that a manual reissue or refund would take.
Categories 31 and 33 contain data elements represented in your coding of
category 16 plus data elements that are not found within Category 16, such as
information contained within General Rules.
The automation of reissue and refund provisions allows airlines to perform complex
calculations quickly and efficiently when a passenger requests a change to his or
her itinerary. Automation ensures the proper add-collect, resulting in improved
revenue collection for the airline using Categories 31 and 33.
Also important to your carriers competitive edge is the fact that automation
ensures that the passenger has paid the lowest qualifying fare when requesting a
reissue or refund on a ticketed itinerary.
On average, 10% of all tickets are reissued or refunded at some point in their
lifetime. Agents processing a manual re-price calculation takes on average 25-30
minutes to complete the process. Due to the current manual process and the
pressure on front-line staff, this manual process is error prone.

5
Copyright SITA Information Networking Computing

USA Inc 2009. Confidential. All Rights Reserved.

These errors results in:

A lower than expected customer experience.

Potentially lengthy wait times at the ticket counter and long on-hold times at
call centres.

Revenue loss through the miss-application of penalties, errors in the fare

recalculation, and errors in tax collection

SITAs Airfare Reprice/Refund (ARR) product seeks to resolve these issues by

allowing the agent to reissue or refund tickets in a few automated steps insuring
accurate processing of the airlines reissue business rules.

SITA's Airfare Reprice/Refund (ARR) provides the following

benefits:

A reduction in the agents time spent repricing and processing a ticket

reissue.

Offer a better service to customers thus increasing your companys brand

satisfaction.

Enforce a global re-pricing policy by a worldwide deployment of ARR.

Protect revenue through the accurate application of penalties, taxes and

fare recalculation.

ARR can be customized to meet the customers business needs.

ARR handles public and private fares, multi-carrier, domestic, international,

and combined itineraries, and waiver scenarios.

ARR processes paper tickets, e-tickets, manually priced tickets and

previously reissued tickets.

Customer can define how fares on the new ticket are calculated.

Customer can define how refunds of partially flown portions are repriced.

SITA Airfare Price-Refund (ARR) is fully integrated with the Airfare Price
system
-

The reprice transaction uses the same database as all other Airfare
Price transactions.

All secondary and follow-on transactions will be available

Full 24 months of history available

Includes the incorporation of all customer specific Airfare BIT

settings

6
Copyright SITA Information Networking Computing

USA Inc 2009. Confidential. All Rights Reserved.

SITA Airfare Reprice/Refund (ARR) contains 3 new transactions

Transaction 1 Can my ticket be changed: provides a yes/no response

Transaction 2 Full re-pricing: response provides all details required to

process a ticket reissue

Transaction 3 Refund: response provides all the details required to

process a ticket refund

ARR "Can my ticket be reissued/" Processing Details

Following are the processing steps that ARR performs for Can my ticket be
reissued product:
1. Customer asks the question Can my ticket be reissued?
2. ARR identifies the fares on the previous ticket

Processing must find all the fare rules, including the Category 31 reissue
provisions, for each fare on the previous ticket
-

If processing does not find a Category 31 for a fare on the previous

ticket or if the Category 31 is coded to not allow an automated
reissue then a message is returned, VOLUNTARY CHANGE NOT
PERMITTED.
Or

if processing does find a category 31 that allows a reissue then a

message will return to the agent VOLUNTARY CHANGE MAY BE
PERMITTED.

ARR Reprice Processing Details

Following are the processing steps that ARR performs for reissue:
1. Customer requests an itinerary change
2. ARR identifies the fares on the previous ticket

Processing must find all the fare rules, including the Category 31 reissue
provisions, for each fare on the previous ticket

If processing does not find a Category 31 for a fare on the previous ticket,
an automated reissue is not available

3. ARR identifies what has changed

Processing compares the previous ticketed itinerary to the new itinerary. If a

carrier code, flight number, travel point, cabin, travel date, and/or travel time
differ between the two, it is considered an itinerary change.

7
Copyright SITA Information Networking Computing

USA Inc 2009. Confidential. All Rights Reserved.

4. ARR applies the applicable reissue rules of each fare on the previous ticket

To whom the reissue provisions apply

-

May be restricted to a specific passenger type

When the change may take place

-

Before or after passenger departure

Before or after flight departure

Before or after ticketing time limit

Within advance purchase requirements

Same day as previously ticketed

5. Determine how the new itinerary should be repriced

Are fare breaks changes allowed?

Are connections or stopovers changes allowed?

Are there specific portions of travel that may not be changed?

Will the first fare be changed?

Can the outbound portion be changed?

May fully flown fare components be extended for further travel?

Should the replacement fares be historical fares, current fares, or the same
as the previously ticketed fare, or a combination there of?

Are the replacement fares required to be a:

-

specific tariff

specific rule

specified carrier(s)

specific fare type

specific fare class

specific fare family

Normal or Special fares

One Way or Round Trip

Does the fare amount have to remain the same?

Determine the any restrictions on who may reissue the ticket?

6. Amount

Calculate the difference in base fare and taxes

8
Copyright SITA Information Networking Computing

USA Inc 2009. Confidential. All Rights Reserved.

Calculate the change fee or percentage

Application of change fee when the fares on the previous ticket carry
change fees of differing amounts

Whether residual value, if any, is refunded or forfeited

Form of refund, when applicable

Waiver conditions

Discounts to change fee for infant, children, youth, or seniors

Endorsement box requirements for new ticket

7. Final result returned to passenger

Add-collect, if any, is collected from the customer

New ticket (and residual value refund, if applicable) issued

ARR Refund Processing Details

Following are the processing steps that ARR performs for refunds:
1. Customer requests a refund
2. ARR identifies the fares on the previous ticket

Processing must find all the fare rules, including the Category 33 refund
provisions, for each fare on the previous ticket

If processing does not find a Category 33 for any fare on the previous
ticket, an automated refund is not available

3. ARR applies the applicable refund rules of each fare on the previous ticket

To whom the refund provisions apply

-

May be restricted to a specific passenger type

When the refund may take place

-

Before or after passenger departure

Before or after flight departure

Before or after ticketing time limit

Within advance purchase requirements

Same day as previously ticketed

4. How flown portions of the previous itinerary should be re-priced

Are fare breaks allowed?

Should the replacement fares be selected from those available on the

original ticket issue date or on the travel commencement date?

Are the replacement fares required to be a:

9
Copyright SITA Information Networking Computing

USA Inc 2009. Confidential. All Rights Reserved.

specific tariff

specific rule

specific fare type

specific fare class

specific fare family

Normal or Special fares

Higher RBD

5. Amount

If flown portions exist, calculate the difference in base fare and taxes

Calculate the cancellation fee amount or percentage

Application of cancellation fee when the fares on the previous ticket carry
penalties of differing amounts

Form of refund, when applicable

Waiver conditions

Discounts to change fee for infant, children, youth, or seniors

6. Final result returned to passenger

Refund, if applicable, is issued

When done manually the above transactions can take up to 30 minutes of an agents
time in recalculating the old and new itinerary. Often assistance is needed from a
support desk. With ARR, the agent now can process a ticket reissue or refund in less
than 2 minutes. ARR is ideal for use at an airport kiosk or over the internet without the
use of a ticketing agent.
Following is a high level customer flow for the ticket Reissue and Refund process.

10
Copyright SITA Information Networking Computing

USA Inc 2009. Confidential. All Rights Reserved.

11
Copyright SITA Information Networking Computing

USA Inc 2009. Confidential. All Rights Reserved.

SITA ARR Requires the following data for Reprice/Refund

Historical fares database

SITA Airfare Price offers 24 months of history

Historical rules database

SITA Airfare Price offers 24 months of history

Ability to auto price itineraries using Current Fares, Historical Fares or a

combination of Historical and Current Fares.
ARR processes Current, Historical and a combination of Historical and Current
fares.

Ability to auto price using current or historical fare construction/pricing logic.

SITA Airfare Price uses historical pricing logic

Ability to access data relevant to the previous ticketed itinerary: TCN data,
Electronic data, etc.
Provided by the ARR user

The design of Voluntary Changes includes all the elements necessary to automate a
refund or reissue transaction. The following list outlines the data elements included in
Voluntary Changes:

Who (to whom the voluntary change data applies)

When (when the reissue transaction may take place)

Number of changes permitted (whether the change is permitted)

Provided (applies data if specified change conditions are met)

Itinerary re-pricing rules (provisions for re-pricing the fares and revalidating the rules)

Itinerary re-pricing amount (additional surcharges)

Amount (penalty amount and application)

Ticket reissue (reissue provisions)

The Data returned by SITA ARR consists of the following data elements:

Passenger type reprice message

Waiver application indicator

Historical or current fare message

Base fare difference refund

Reissue fare difference refund

Reissue TFC difference

Reissue ticket difference

12
Copyright SITA Information Networking Computing

USA Inc 2009. Confidential. All Rights Reserved.

Reissue grand total

Form of refund

Example:
REPRICE BASED ON DIFF PTC

WAIVER 01 NOT APPLIED

ITINERARY REPRICED USING HISTORICAL FARES

BASE FARE DIFF

USD

-250.00 REFUND

REISSUE FARE DIFF

GBP

-125.00 REFUND

REISSUE TFC DIFF

GBP

+40.00 ADC

REISSUE TICKET DIFF

GBP

-85.00 REFUND

REISSUE SVC FEE

GBP

+25.00 ADC

REISSUE GRAND TOTAL

GBP

-60.00 REFUND

FORM OF REFUND

ORIGINAL FOP

Lets break it down Category 31 and Category 33

Terminology needed to understand the aspects of Voluntary changes provisions.
Base Fare - The fare amount excluding taxes and other charges. Any charge resulting from
Stopovers (Category 8), Transfers (Category 9), and/or Surcharges (Category 12) processing is
included in the base fare.
Current Fares - Fare and applicable rule information valid for sale at the time of reissue or
refund. Current fares are not mutually exclusive with historical fares. Same fares and rules may
possibly still be in effect.
Historical Fares - Fares and applicable rule information valid for sale at the time of the original
ticketing date.
Keeping Fares - Any attempt to re-price the itinerary using the same fare and rule information as
previously ticketed.
Original Ticket - The first ticketed itinerary. If reissues have already occurred, the latest reissued
ticket is not the original ticket.
Previous Ticket - The current ticketed itinerary (latest ticketed itinerary). If reissues have already
occurred, then the latest reissued ticket is the previous ticket. When processing the first reissue,
the original ticket and previous ticket are the same.
Process Tag - A number indicating the method of how to process the reissue transaction.
Second and subsequent reissues - Tickets that are presented for reissue that contain both an
original ticketing date AND a reissued ticketing date.
Terminal Points - Fare break point; the ends of a fare component. Typically used when a fare
has not yet been assessed for the fare component.
Ticketed Points - Locations that will be reflected within the From/To points of the passengers
coupon of the ticket (connection, fare break points, stopovers).

13
Copyright SITA Information Networking Computing

USA Inc 2009. Confidential. All Rights Reserved.

Validating Carrier - The carrier whose ticket stock was used to issue the ticket. This carrier is
commonly the holder of the money for the ticket. Also know as plating carrier.
Voluntary Change - A change in the ticketed itinerary
1
2
3

That the passenger requested

Where there is a replacement itinerary
Where the ticket is reissued/revalidated

Voluntary Refund - A change in the ticketed itinerary:

that the passenger requested; and

where there is no replacement itinerary; and

where the ticket is refunded or discarded (no value)

- or

where Category 31 Voluntary Changes has rendered the ticket invalid for
continuing transportation

14
Copyright SITA Information Networking Computing

USA Inc 2009. Confidential. All Rights Reserved.

Basic Reissue and Refund Processing

Determine/Retrieve the
original ticketed itinerary

Determine/Retrieve the new

(desired) itinerary

Does a new itinerary exist?

Yes

No

Transaction is Change (Cat 31 & 32)

Transaction is Refund (Cat 33 & 34)

Is the transaction requested by the customer?

Is the transaction requested by the customer?

Yes

Quo
te
Process Cat 31
pass
(Voluntary Change)
eng
er
low
est
addi
tioncancel and
Assume
al as an
start over
coll
option
ecti
on /
grea
test
refu
nd
amo
unt

No

Yes
s

No

Process Cat 32

Process Cat 33

Process Cat 34

(Involuntary Change)

(Voluntary Cancel)

(Involuntary Cancel)

Assume cancel
and start over as
an option

Quote passenger
lowest additional
collection /
greatest refund
amount

Quote passenger
lowest additional
collection /
greatest refund
amount

15
Copyright SITA Information Networking Computing

USA Inc 2009. Confidential. All Rights Reserved.

Processing Flow Chart for Category 31 Reissues

General Rule
Not Permitted

Original Fare
Published or Constructed

Foot Note
Not Permitted

Fare Class Application

Record 1

Alternate General
Rule sequence list
for:
Tariff Rule Category
31

Record 2
Match to fare from record 1
indicator

Category Data Table

Data stringing referenced
by the sequence list
Attempt multiple tables
matching for each fare
component
Resulting Provisions from
rule or alt general rule

16
Copyright SITA Information Networking Computing

USA Inc 2009. Confidential. All Rights Reserved.

Voluntary change information can be divided into major sections

as detailed below.
Section

Source
Location

WHO

CATEGORY 31

WHEN

CATEGORY 31

Number of Changes
Permitted

CATEGORY 31

Provided

TABLE 988

Itinerary
Re-pricing
Rules

TABLE 988

Section

Source
Location

Itinerary Repricing
Rules
cont.
Itinerary Repricing
Amount

TABLE 988

Amount
Multiple Reissues

CATEGORY 31
CATEGORY 31

TABLE 988

CATEGORY 31
Ticket Reissue

TABLE 988

Bytes
byte 8-10
bytes 40-43
byte 14
bytes 15-17
bytes 18-37
byte 38
bytes 104-106

Field Name
Passenger Type Code
Passenger Occurrence first / last
Ticket Validity
Journey / Pricing Unit / Fare Component
Advance Reservation
Ticketing Time Limit
Override Date Table 994

byte 31
byte 14, 15-21
byte 22
byte 32
byte 59
bytes 12 - 13
bytes 24 - 31
bytes 33 - 58
bytes 60 - 61
bytes 62 - 80
byte 91

Change Indicator
Travel limit, stop / transfer / portion
Outbound portion of travel
Originally scheduled flight
Date
Process tag
Fare break limitations
Fares
Measure Advance reservation
Revalidate rules
Revalidate booking codes

Bytes
bytes 107 - 121
byte 154
byte 155
byte 156

Field Name
Minimum stay
Stop
Reissue to a lower fare
New Ticket equal or higher

bytes 136 - 153

bytes 47 - 75
byte 76
byte 77
byte 78
byte 80 - 83
byte 87
byte 79
byte 84
byte 85
byte 86
bytes 92 - 106
bytes 122 - 135

Surcharge
Charges - amount/percent/low/high/min
J/PU/FC
Fee Application
Type of Service text tag
Discount
Multiple Reissues
Type of ticket transaction
Residual penalty
Form of refund
Endorsement Requirements
Advance Ticketing
Transaction Restrictions

Processing for Category 31

17
Copyright SITA Information Networking Computing

USA Inc 2009. Confidential. All Rights Reserved.

The Airfare Reprice transaction will attempt to match to a record 2 in order to find the category 31
provisions that apply to the fare component being validated. Once a record 2 is matched the
itinerary will be compared to a category 31 record 3 table based on the category 31 match fields.
Once a match is made to the category 31 match fields the system will then compare the itinerary
to the table 988 match fields. When a match is made to the table 988 processing will apply the
repricing, charge amounts and reissue restrictions contained in category 31 and table 988.

When the fare component being validate does match to the category 31 record 3:
1. Processing will attempt to match the first table 988 sequence.

If the first table 988 sequence is matched then apply the repricing, charge
amounts, and reissue restrictions contained within the category 31 record 3 and
table 988 sequence. Continue processing to the next table 988 sequence
number attempting to match and apply the provisions.

If the first table 988 sequence is not matched, then continue processing to the
next table 988 sequence attempting to match and apply the provisions.

Processing will attempt to match all table 988 sequences. The repricing charge
amounts and reissue restrictions that produce the best result for the passenger
will be applied. (When table 988 stop field byte 154 is value X, then processing
will continue to the next table988 sequence that contains a different process tag
value in table 988 bytes 12-13. Processing may still continue to another category
31 record 3 table and process any table 988 sequences.)

2. Once all table 988 sequences have been processed continue processing to the
next category 31 record 3 table in the string.

Note: Relational indicator AND is not valid for category 31. If a record table is
received with relational indicator AND, then processing should ignore the entire
category 31 set containing the

AND table and continue processing to the next set.

18
Copyright SITA Information Networking Computing

USA Inc 2009. Confidential. All Rights Reserved.

When the fare component being validated does not match to the category 31
record 3:
1. Processing will continue to the next category 31 record 3 table in the string.
Note: Relational indicator AND is not valid for category 31. If a record table is
received with relational indicator AND, then processing should ignore the entire
category 31 set containing the AND table and continue processing to the next set.

MATCHING THE VOLUNTARY CHANGE DATA

1. Itinerary Analysis for Historical Record 2 retrieval:

Determine the previous ticketed itinerary: (fare components, fare combinations,

ticket issuance date, and ticketed fare classes.)

Determine the new itinerary

Identify all points of change (i.e. carrier code, class of service, ticketed travel
points, travel dates, flights).

Retrieve the record 2(s) for categories 31 & 5 for each fare component on the
previous ticket.

2. Match the applicable category 31 record 3 table (based on Who, Waiver, and When
fields):

Passenger Type code (bytes 8-10)

Waiver table 987 (bytes 11-13)

Ticket Validity (byte 14)

Departure of Journey/Pricing Unit/Fare Component (bytes 15-17)

Advance Reservations (bytes 18-37)

Ticketing Time Limit (byte 38)

Passenger Occurrence (bytes 40-43)

Override Date Table 994 (bytes 104-106)

19
Copyright SITA Information Networking Computing

USA Inc 2009. Confidential. All Rights Reserved.

3. Determine whether changes are permitted:

Change indicator (byte 39)

4. Match the applicable table 988 based on provided fields:

Travel limitations (bytes 14-21)

Originally scheduled flight (byte 32)

Date (date 59)

5. Reprice the new itinerary as directed by the table 988 Itinerary reprice rules fields.

Process tag (bytes 12-13)*

Fare break limitations (bytes 24-31)

Fares (bytes 33-58)

Revalidating rule / RBD conditions (bytes 60-80, 91, 107-121)

Stop (byte 154)

6. Calculate the applicable charges

Table 988 Itinerary repricing amount fields

Category 31 amount fields

7. Reissue the ticket as directed by the ticket reissue fields. The system should return
the smallest additional collection / largest refund as determined from the
processing steps above.
*Process Tags generalize the conditions under which passengers may request a change
to their itinerary. Depending on the process tag passengers may use the original fare,
historical fares or current fares when reissuing their ticket. The process tag must be
identified and retrieved for all fare components in the itinerary before the reprice process
begins. Voluntary changes has unique processing in which it is possible to match to
multiple tables or multiple entries in the reissue table 988. Thus process tags and the

20
Copyright SITA Information Networking Computing

USA Inc 2009. Confidential. All Rights Reserved.

reissue table 988 work together to identify multiple repricing methods that may apply on
an itinerary.

21
Copyright SITA Information Networking Computing

USA Inc 2009. Confidential. All Rights Reserved.

Currently Airfare Reprice Reissue processes the following tags:

Process

Description

Tag
1
2
3
5
6
7
8
11

Percentage of
usage in the

Keep the Fares

Guaranteed Air Fare
Keep fares for traveled fare components
No guaranteed fares
IATA Reissue provisions
Reissue down to a lower fare
Cancel and start over
Keep the fares up to the first changed fare component,

industry
8.45%
49.54%
.18%
22.47%
1.00%
2.66%
13.83%
.81%

historical fares for changed fare components

Note: Tags 1, 2, 5, 7, 8 are used by International Carriers

Current (03, 05, 06, 07) When the process tag require using current fares
processing will reprice using fares that are in effect on the date of the new ticket
issuance. Effective/discontinue date validation for fare selection is based on the
date of departure from the origin of the new journey.
Note1: in system processing if current is found for any of the fare components in
the permutation, then the data base access date/time for revised pricing
transaction will be set to current date/time for the entire journey for this
permutation. Current date/time is defined as the date/time of reissue. If data base
access date/time is already set, it will not be modified and is used in the re-pricing.
If it is not already set, data base access date/time must be set to the ticketing
date/time that exists in the input revised pricing transaction.
Note 2: Tag 3, 6 will be processed if all fares are current and itineraries that are
completely unflown.
Keep (01, 11) When the process tag requires keeping the fares, processing will
use the exact fare level, fare basis and historical rules that were applicable at the
time of the original ticket issuance. When handling Process Tag 01, changes are
not permitted on the first fare component, requires to keep the fare break points.
When encountering Process Tag 11, it should apply to all fare components up to
first changed fare component.
Note 1: Data base access date/time for revised pricing transaction will be set to the
date/time of the original pricing transaction. If Data base access date/time in the
original pricing transaction is set, then Data base access date/time for the revised
pricing transaction must be set to be the same. If original Data base access
date/time is not set, then Data base access date/time for revised pricing
transaction must be set to the ticketing date/time that exists in the input original
pricing transaction.
Historical (02, 06) When the process tag requires using historical fares,
processing will reprice using fares that were in effect on the date of the previous

22
Copyright SITA Information Networking Computing

USA Inc 2009. Confidential. All Rights Reserved.

ticket issuance. Effective/discontinue date validation for fare selection is based on

the date of departure from the origin of the new journey.
Note1: If Historical (02) is found, Data base access date/time for revised pricing
transaction must be set to the date/time of the original pricing transaction. If Data
base access date/time in the original pricing transaction is set, then Data base
access date/time for the revised pricing transaction must be set to be the same. If
original Data base access date/time is not set, then Data base access date/time for
revised pricing transaction must be set to the ticketing date/time that exists in the
input original pricing transaction.
Note2: Historical Commencement (06) If Historical commencement is found, then
data base access date/time must be set to the travel commencement date/time on
the original pricing itinerary.
Note: Will only process all historical tag 6. There is no mix of historical and current.
Cancel (08) The category 33 development will include tag 8 processing. Until
category 33 development is completed when tag 8, cancel is found for any of the
fare components in the permutation, then this permutation should be skipped and a
warning message will be asserted (MANUAL REISSUE REQUIRED - CANCEL
AND START OVER). Process tags for all other fare components will be ignored.
Tag Details
TAG 1 Keep the Fares
Tag 1 indicates that the itinerary should be repriced using the same fares that were in
effect when the itinerary was originally ticketed.
Applies before or after departure

Must keep the same fare break points

Must keep travel as directed by the travel limitations fields

Must keep the original ticketed fare for all fare break points (same fare breaks,
rule and amount as those in effect on the ticket issue date).

Must use the original ticketed category 31 provisions

Cannot change any portion of the first fare component flown on the ticket
(change means flight, dates, time, carrier, or booking code).

The process applies regardless of whether the change in made before or after departure
from the origination journey. When validating the change, processing will use the original
fare and category 31 rule provisions for all fare components and revalidate all provisions
against the new itinerary.

Example:

23
Copyright SITA Information Networking Computing

USA Inc 2009. Confidential. All Rights Reserved.

MAD
ATL
ORL

1. no changes allowed between ATL MAD component (first

component)
2. no changes allowed at ATL MAD ORL break points
3. only previously ticketed fares can be used for calculation
Example Original Itinerary
Fare Component
Date
ATL MAD
12MAY10
MAD ATL
09JUL10
New Revised Itinerary
Fare Component
Date
ATL MAD
12MAY10
MAD ATL
14JUL10

Fare Class
V7NR
B7NR

AMT
$100
$200

Fare Class
V7NR
B7NR

Change Fee
$50 Highest in PU
$75 Highest in PU

Fare Amount
$100
$200

Scenario
No change to travel on the fist fare component (ATL MAD).

Change to the second fare component (MAD ATL). Return segment changed to
14JUL10.

No change to fare break points.

Travel is kept as directed in the travel limitation fields.

The original rule provisions are revalidated.

Calculation
Original ticketed value
($100 + $200) =
-Value of desired itinerary
($100 + $200) =
-change fee
$75 > $50
----------------------------------------Amount of Additional Collection

$300
$300
$ 75
------($75)

Explanation
The new itinerary met all the originally ticketed voluntary change rules provisions.
The change was allowed using the same fares as originally ticketed. Same fare
calculation occurred, $300.

24
Copyright SITA Information Networking Computing

USA Inc 2009. Confidential. All Rights Reserved.

The $75 change fee was applied because it was the highest change fee on the
pricing unit.

Repricing allowed the change and add/collect $75 ($0 difference in fares +$75
change).

TAG 2 Guaranteed Air Fare

Tag 2 requires that the itinerary should be repriced using historical fares.
Applies before or after departure.

Must keep the fare component or fare break points as further defined by fare
limitation fields in the reissue table 988.

Must keep the same travel as defined by the travel limitations fields in the reissue
table 988.

Repricing using historical fares.

This processing applies before or after the origin of the journey. Processing will reissue
by using historical fare and rule provisions for all fare components unless a waiver tag
has been set.

ATL

NY
C
op
ov
er
s

LON

PAR

NYC is a stopover point thus the fare break points are ATL, LON, PAR.
Processing Tag 2 applies the following:
If the first fare component field does not allow changes, the first fare component
cannot be changed (ATL-LON).

If the first fare component field allows changes, the first fare component (ATLLON) can be changed.

Historical fares and rules data must be used (from the previously issued ticket).

If the first fare break field does not allow changes then the fare break points
cannot be changed. Therefore, the reissue ticket must have the exact same fare
break points (ATL, LON and PAR).

Example Original Itinerary

Fare Component
Date
ATL MAD
12MAY10

Fare Class
V7NR

AMT
$250

Change Fee
$50 Highest in PU

25
Copyright SITA Information Networking Computing

USA Inc 2009. Confidential. All Rights Reserved.

MAD ATL

09JUL10

New Revised Itinerary

Fare Component
Date
ATL MAD
12MAY10
MAD ATL
05JUL10

B14NR

$200

Fare Class
V7NR
B7NR

$75 Highest in PU

Fare Amount
$250
$250

Scenario
No change to travel on the first fare component (ATL MAD).

Change to the second fare component (MAD ATL). Return segment changed to
05JUL10.

No change to fare break points.

Travel is kept as directed in the travel limitation fields.

Second fare component does not meet the origin ticketed rule provisions

Entire itinerary is now repriced using historical fares (this includes the ability to
use originally ticketed fares).

Calculation
Original ticketed value
($250 + $200) =
-Value of desired itinerary
($250 + $250) =
-change fee
$75 > $50
----------------------------------------Amount of Additional Collection

$450
$500
$ 75
------($125)

Explanation
The new itinerary did not meet the minimum stay requirements. The itinerary was
repriced using historical fares.

The fare and rule that applied resulted in a B7NR fare class equal to $500 RT.
The new itinerary met the rule provisions of the B7NR fare class.

The $75 change fee was applied because it was the highest change fee on the
pricing unit.

Repricing allowed the change and add/collect $125 (+$50 difference in fares and
+$75 change fee).

TAG 3 Keep fares for traveled fare components

26
Copyright SITA Information Networking Computing

USA Inc 2009. Confidential. All Rights Reserved.

Tag 3 requires that previously ticketed fares are used when repricing fare components
that have been traveled.
Applies before or after departure (when used before departure, all fare
components are repriced using current fares).

Keep the original ticketed fare for any fare component that has been fully
traveled. (Fare break limitations fields have no application).

Use current fares and rules for any fare component that has not been fully
traveled. (Validate according to the fare break limitations fields).

This process tag usually applies after departure from the point of origin. Processing will
re-ticket any flown fare components using the previously ticketed fare (keeping fares)
and reticket any unflown fare components using current fare levels in the market for the
fare component being repriced. Fare break points cannot be changed for fully traveled
fare components. If coded, fare break points can be changed for any fare component
that has not been fully traveled.

LON
ATL
MA
N
PAR

MAN is a transit point. Processing Tag 3 applies the following:

A change to LON-MAN is not allowed because the fare break points are ATL,
LON, PAR.

The passenger cannot make a change to the ATL-LON fare component (applies
after departure).

In processing the traveled portions will retain the ticketed fare. The reissue
portions of travel will be validated by using current fare and rule levels.

Example Original Itinerary

Fare Component
Date
Fare Class
ATL MAD
12MAY10
V7NR
MAD ATL
09JUL10
B14NR

AMT
$120
$200

Change Fee
$50 Highest in PU
$75 Highest in PU

27
Copyright SITA Information Networking Computing

USA Inc 2009. Confidential. All Rights Reserved.

New Revised Itinerary

Fare Component
Date
ATL MAD
12MAY10
MAD ATL
05JUL10

Fare Class
V7NR
Y

Fare Amount Minimum Stay

$120
First Sunday
$700
None

Scenario
Assume today is 05July. The first fare component has been traveled. Return
travel is now desired on 05July.

The second fare component does not meet the originally ticketed rule
provisions.

The itinerary is repriced using the original ticketed fare for the first fare
component (V7NR, $120, traveled) and using current fare and rule
information for the second fare component (not traveled).

Calculation
Original ticketed value
($120 + $200) =
-Value of desired itinerary
($120 + $700) =
-change fee
$75 > $50
----------------------------------------Amount of Additional Collection

$320
$820
$ 75
------($575)

Explanation
The second fare component did not meet the rule provisions in the originally
ticketed voluntary changes category.

The first fare component was priced keeping the original ticketed fare because it
was already traveled.

The second fare component was priced using current fares and rule information.

The fare and rule that applied resulted in a Y fare class (equal to $700 for the
second fare component).

The $75 change fee was applied because it was the highest change fee on the
pricing unit.

Repricing allowed the change and add/collect $575 (+$500 difference in fare and
+$75 change fee).

TAG 5 No Guaranteed Fares

28
Copyright SITA Information Networking Computing

USA Inc 2009. Confidential. All Rights Reserved.

Tag 5 requires that processing must reprice the entire itinerary using current fare levels
and rules for all fare components.
Applies before or after departure.

Reprice the entire itinerary using current fares and rules for all fare components.

Reprice the itinerary with the based on the travel limitation fields.

Processing will reprice the itinerary using fare and rule provisions regardless of the
change made from the current fares for each changed fare component. Also changes
will be applied according to the fare break limitation fields and the travel limitation fields.

LON
ATL
MA
N
PAR

MAN is a transit point. Processing Tag 5 applies the following:

Tag 5 allows the fare break points to be changed based on the fare break
limitation fields coded.

The itinerary is allowed to be changed based on the coding of the travel

limitations fields.

Will use current fares for any changes taking place.

Example Original Itinerary

Fare Component
Date
Fare Class
ATL MAD
12MAY10 V7NR
MAD ATL
19MAY10 B14NR

AMT
$350
$250

New Revised Itinerary

Fare Component
Date
ATL MAD
12APR10
MAD ATL
19APR10

Fare Amount
$540
$540

Fare Class
N7NR
N7NR

Change Fee
$50 Highest in PU
$75 Highest in PU

Scenario
Entire itinerary is being changed. Travel is now April 12 19th.

The itinerary is repriced using current fares and rules

The new itinerary is repriced using the N7NR $1080 RT ($540 + $540).

Calculation

29
Copyright SITA Information Networking Computing

USA Inc 2009. Confidential. All Rights Reserved.

Original ticketed value

($350 + $250) = $600
-Value of desired itinerary
($540 + $540) = $1080
-change fee
$75 > $50
$75
----------------------------------------------Additional Collection
($555)

Explanation
The complete itinerary was repriced using current fare and rule provisions.

This resulted in a new fare N7NR fare of $1080 RT.

The $75 change fee was applied because it was the highest change fee on the
pricing unit.

Repricing allowed the change and add/collect $555 (+$480 difference in fare and
+$75 change fee).

TAG 6 IATA Reissue Provisions

Process tag 6 directs the subscriber to employ IATA reissue provisions for an changes
as described in IATA resolution 017f. There are no agreed industry processing
applications for tag 6.
Airfare Reprice / Refund will process tag 6 if all fares are current and itineraries are
completely unflown. If a historical commencement is found then processing will set the
database access date/time to the travel commencement date/time on the orginial pricing
itinerary.
There is no mix of historical and current processing.
TAG 7 Reissue Down to a Lower Fare
Tag 7 processing will reticket the fare using current fares of lower fare amounts for the
requested change.
Applies before departure.

Booking class may change.

No changes to flights (including terminal points, carrier, times or date) on the

itinerary.

Reprice the entire itinerary using current level fares for all fare components.

Tag 7 must be present on all components for the issue to be valid (in case one is
different, retickting must be done manually.)

Processing my not reissue to a higher fare.

30
Copyright SITA Information Networking Computing

USA Inc 2009. Confidential. All Rights Reserved.

Tag 8 Cancel and Start Over

Airfare Reprice / refund will process tag 8 temporally as follows: If Cancel is found for
any of the fare components in the permutation, then this permutation should be skipped
and a warning message will be returned MANUAL REISSUE REQUIRED - CANCEL
AND START OVER). Process tags for all other fare components will be ignored. Tag 8
development to fall to category 33 will be completed with the category 33 development.
Tag 8 specifies what to do when the fare is canceled entirely and the repriced using
current fares. Tag 8 should be present for most voluntary changes data tables.
Applies before or after departure.

Cancel the fare and start over.

Apply applicable cancellation fee.

Tag 8 will be included in most voluntary change provisions. Tag 8 applies regardless of
the itinerary changes. When processing tag 8 you will cancel and start over using a new
current fare.
Example Original Itinerary
Fare Component
Date
Fare Class
ATL MAD
12MAY10 V
MAD ATL
21MAY10 Y

AMT
$100
$300

New Revised Itinerary

Fare Component
MAD NYC

Fare Amount
$900

Date
24MAY10

Fare Class
Y

Change Fee
50% Highest in FC
No change fee

Scenario
It is 17May09 and the first fare component is already traveled. (first FC was a
one-way fare.)

Second fare component is being changed.

Calculation
Previous ticketed value
($100 + $300) = $400
-Value of portion used
$100
$100
-Cancel Fee
($100 x 50%)
$ 50
- Value of new ticket
$900
----------------------------------------------Amount of Additional Collection
$650
Explanation
The new itinerary was repriced using current fare and rule information.

The result was a new $900 fare (OW).

31
Copyright SITA Information Networking Computing

USA Inc 2009. Confidential. All Rights Reserved.

A 50% change fee was applied to the first fare component. There was no change
fee on the second fare component.

The $250 refund from the cancellation was applied towards the purchase of the
new ticket.

Repricing result: Allow the change. Treat as a cancellation and purchase new
ticket. Collect $650.

Tag 11 Keep the fares up to the first changed fare component, historical fares for
changed fare components.
Processing will reprice the itinerary using the same faers as previously applied up to the
first change in the fare component; historical fares are to be used for all subsequent fare
components.

Applies before or after departure

Reprice the itinerary as directed by the travel limitations fields.

For fare components that are instructed to Keep the Fares, the travel limitation
fields have no applications.

Keep the previously ticketed fares and rules for all unchanged fare components
up to the point of change.

Reprice all other components using fares and rules that existed on the date of
the previous ticket issuance (historical).

Example Original Itinerary

Fare Component
Date
ATL MAD
12MAY10
MAD ATL
21MAY10

Fare Class
VL21NR
HL21NR

AMT
$100
$200

New Revised Itinerary

Fare Component
Date
ATL MAD
12MAY10
MAD ATL
10JUN10

Fare Class
VL21NR
HSPSCL

Fare Amount
$100 (Keep)
$150 (Historical)

Change Fee
$50 Highest in PU
$50 Highest in PU

Scenario
The first fare component is VL21NR ($100 value); the second fare
component is HL21NR ($200 value).

The first fare component is not being changed.

Second fare component is being changed with a later return travel of

10Jun10.

Travel is kept as directed in the travel and fare break limitation fields.

32
Copyright SITA Information Networking Computing

USA Inc 2009. Confidential. All Rights Reserved.

Itinerary is repriced by using the same fares and rules as previously ticketed
for the first fare component. Historical fare and rule information is used to
reprice the second fare component.

Calculation
Original ticketed value
($100 + $200)
-Value of desired itinerary
($100 + $150)
-Change Fee
$ 50
----------------------------------------Amount of Additional Collection

$300
$250
$ 50
------$0

Explanation
The first fare component was unchanged; thus it was priced using the same fares
and rules as previously ticketed (Keep).

The second fare component (change) was repriced using historical fares and rule
information.

VL21NR was kept from the original first fare component. The new fare class
HSPSCL equal to $150 is used for pricing the second fare component.

The 50 changed fee was applied (highest of the pricing unit).

The repricing result was to allow the change, applying the $50 change fee and
add/collect the difference in fare.

Tag processing steps

1. System processing will determine the process tags for all fare components in the
itinerary.

Multiple entries can exist with the same process tag on the reissue
sequence screen. Processing will review in sequential order each
recurring segment of the process tag(s).

The relationship between the process tag definition and the remainder of
the repricing rules fields is AND.

Processing must meet all repricing rules conditions (including process tag
processing) in order for it to be used to reprice the itinerary.

2. If the process tag values are not the same for all fare components within the
itinerary determine all possible process tag permutations. Determine the fares to
be selected by applying the process tag value definition. Then apply the most
restrictive condition as follows:

Cancel (Tag 8)

Current (Tag 5 and 7)

Keep (Tag 1, 3, 11)

Historical (Tag 2)

33
Copyright SITA Information Networking Computing

USA Inc 2009. Confidential. All Rights Reserved.

3. Validate the data within the reissue table for the applicable process tag for each
fare component.
4. Once the validation has occurred apply the best pricing solution for the
passenger.

34
Copyright SITA Information Networking Computing

USA Inc 2009. Confidential. All Rights Reserved.

Category 31 rules text mapped to bits/bytes

FARE RULES TEXT
ORIGINATING AREA 1 - Sequence 8905000 Rule Record 2 locs coded Loc 1Area 1 Loc 2 = GB, with directionality of 3-orgin loc 1 or Area 1
Rec 3 tables
= 00158987 with 988 rec 3 00107290, proc tags 02, 05
/ 00050289 with waiver table 987 00000003 waiver 01-Death and 988 rec
3 00028517, proc tags 02, 05
= 00158990 with 988 rec 3 00107291 proc tag 02
/ 00050291 with waiver table 987 00000003 waiver 01-Death and with 988
rec 3 00028519 proc tag 02
/

00149828 0010410 proc tag 07

IN THE EVENT OF CHANGES TO TICKETED FLIGHTS

jny field

(U26)

= b before journey departure

BEFORE DEPARTURE OF JOURNEY AND WITHIN TKT VALIDITY

tktval field (U25) =X within tkt val
CERTAIN DOMESTIC REISSUE PROVISIONS MAY BE OVERRIDDEN
Cat 31Rec3 dom/intl combo=blank (U116)
BY THOSE OF US INTERNATIONAL FARES CHARGE USD 200.00 OR HIGHEST FEE OF
ANY FARE
Cat 31 Rec 3 Amt,Cur,Dec = 200.00USD (U63-73);
feeappl field = 2 (U105) highest
COMPONENT WITHIN PRICING UNIT - INFANT/CHILD DISCOUNT
Cat 31 Rec 3 field jopufc = p (U104)
APPLIES AND
Cat 31 Rec 3 field disc = 12 (U108-111)
Reissue 988 table 00107290
REPRICE USING FARES IN EFFECT WHEN TKT WAS ISSUED 988 Rec 3 process

tag 02 (U21-22)

PROVIDED ALL OF THE FOLLOWING CONDITIONS ARE MET1. NO CHANGE TO 1ST FLIGHT COUPON 988 Rec 3 tvl portion = f (U24)
2. US FARES ARE USED 988 Rec 3 cxrappl table 0000000028 = US (U58-

65)

3. PRIVATE TARIFFS ARE INCLUDED 988 Rec 3 Priv = blank (U111)

4. ALL RULE AND BOOKING CODE PROVISIONS ARE MET 988 Rec 3 revalrule =
blank (U92)
5

35
Copyright SITA Information Networking Computing

USA Inc 2009. Confidential. All Rights Reserved.

. VALIDATE ADVANCE RES REQUIREMENTS WHEN BOOKING DATE KNOWN

988 Rec 3

Revalappl adv (U92, 97)

6. ADV RES IS MEASURED FROM ORIGINAL TKT DATE TO 988 Rec 3 measure from
= o (U90)
DEPARTURE OF PRICING UNIT

988 Rec 3 measure to = blank (U91)

OR REPRICE USING FARES IN EFFECT TODAY

22)

988 Rec 3 process tag 05 (U21-

PROVIDED ALL OF THE FOLLOWING CONDITIONS ARE MET1. US FARES ARE USED

988 Rec 3 cxrappl table 0000000028 = US (U58-65)

2. PRIVATE TARIFFS ARE INCLUDED

988 Rec 3 Priv = blank (U111)

3. VALIDATE ADVANCE RES REQUIREMENTS WHEN BOOKING DATE KNOWN 988 Rec 3
Revalappl adv (U92, 97)
4. ADV RES IS MEASURED FROM REISSUE DATE TO 988 Rec 3 measure from =
blank (U90)
DEPARTURE OF PRICING UNIT

988 Rec 3 measure to = blank (U91)

WHEN CHANGE RESULTS IN LOWER FARE SUBTRACT RESIDUAL Cat 31 Rec 3 respen
= s (U112) subtract
FROM THE PENALTY THEN ADD-COLLECT/REFUND - REFUND VIA VOUCHER Cat 31
Rec 3 formofref=v (U113) voucher
ENDORSEMENT BOX- HIGHER NON-REF AMT AND NEW ENDORSEMENTS.
end = blank (U114)

Cat 31 Rec 3

OR - Cat 31 Rec 3 table 00050289

BEFORE DEPARTURE OF JOURNEY AND WITHIN TKT jny field
journey departure
VALIDITY

(U26)

= b before

tktval field (U25) =X within tkt val

IN THE CASE OF DEATH OF PASSENGER OR FAMILY Waiver table 987 table

00000003= 01 death
MEMBER - CERTAIN DOMESTIC REISSUE PROVISIONS MAY Cat 31Rec3 dom/intl
combo=blank(U116)
BE OVERRIDDEN BY THOSE OF US INTERNATIONAL FARES Reissue 988 table
00028517
REPRICE USING FARES IN EFFECT WHEN TKT WAS ISSUED 988 Rec 3 process tag
02 (U21-22) [historical]
PROVIDED ALL OF THE FOLLOWING CONDITIONS ARE MET1. NO CHANGE TO 1ST FLIGHT COUPON

988 Rec 3 tvl portion = f (U24)

2. ANY CARRIER FARES ARE USED

$$ any cxr (U58-65)

988 Rec 3 cxrappl 990 table 00000019 =

3. PRIVATE TARIFFS ARE INCLUDED

988 Rec 3 Priv = blank (U111)

4. ALL RULE AND BOOKING CODE PROVISIONS ARE MET 988 Rec 3 revalrule =
blank (U92)

36
Copyright SITA Information Networking Computing

USA Inc 2009. Confidential. All Rights Reserved.

5. VALIDATE ADVANCE RES REQUIREMENTS WHEN BOOKING DATE KNOWN

Revalappl adv (U92, 97)
6. ADV RES IS MEASURED FROM ORIGINAL TKT DATE
blank (U90)
TO DEPARTURE OF PRICING UNIT
OR -

00050289

988 Rec 3

988 Rec 3 measure from =

988 Rec 3 measure to = blank (U91)

Same Reissue 988 table 00028517 for cat 3 rec 3

REPRICE USING FARES IN EFFECT TODAY

22) [current]

988 Rec 3 process tag 05 (U21-

PROVIDED ALL OF THE FOLLOWING CONDITIONS ARE MET1. US FARES ARE USED

988 Rec 3 cxrappl 990 table = blank

2. PRIVATE TARIFFS ARE INCLUDED

988 Rec 3 Priv = blank (U111)

3. VALIDATE ADVANCE RES REQUIREMENTS WHEN BOOKING DATE KNOWN 988 Rec 3
Revalappl adv (U92, 97)
4. ADV RES IS MEASURED FROM REISSUE DATE TO 988 Rec 3 measure from =
blank (U90)
DEPARTURE OF PRICING UNIT 988 Rec 3 measure to = blank (U91)
WHEN CHANGE RESULTS IN LOWER FARE SUBTRACT Cat 31 Rec 3 respen = s
(U112) subtract
RESIDUAL FROM THE PENALTY THEN ADD-COLLECT/REFUND-REFUND VIA VOUCHER
Cat 31 Rec 3 formofref = v (U113) voucher
ENDORSEMENT BOX- HIGHER NON-REF AMT AND NEW ENDORSEMENTS. Cat 31 Rec 3
end = blank (U114)
The next set of cat 31 coded records and the text that is generated
begins at this next
ORIGINATING AREA 1
= 00158990 with 988 rec 3 00107291 proc tag 02 [current]
/ 00050291 with waiver table 987 00000003 waiver 01-Death and
with 988 rec 3 00028519 proc tag 02 [current]
/ 00149828 with 988 rec 3 00100410 proc tag 07 [current,
pricing down to a lower fare)
ORIGINATING AREA 1 IN THE EVENT OF CHANGES TO TICKETED FLIGHTS
cat 31 rec 3 table 0158990
AFTER DEPARTURE OF JOURNEY AND WITHIN TKT VALIDITY
CERTAIN DOMESTIC REISSUE PROVISIONS MAY BE OVERRIDDEN
BY THOSE OF US INTERNATIONAL FARES
CHARGE USD 200.00 OR HIGHEST FEE OF ANY FARE
COMPONENT WITHIN PRICING UNIT - INFANT/CHILD DISCOUNT
APPLIES AND

37
Copyright SITA Information Networking Computing

USA Inc 2009. Confidential. All Rights Reserved.

REPRICE USING FARES IN EFFECT WHEN TKT WAS ISSUED 988 Rec 3 table
00107291 proc tag 02
PROVIDED ALL OF THE FOLLOWING CONDITIONS ARE MET1. NO CHANGE TO 1ST FLIGHT COUPON
2. WHEN NO INTL COUPONS REMAIN - ALL NEW TRAVEL MUST BE DOMESTIC
3. CHANGE IS ON/BEFORE DAY OF ORIGINAL SCHEDULED FLIGHT
4. US FARES ARE USED
5. PRIVATE TARIFFS ARE INCLUDED
6. ALL RULE AND BOOKING CODE PROVISIONS ARE MET
7. VALIDATE ADVANCE RES REQUIREMENTS WHEN BOOKING
DATE KNOWN
8. ADV RES IS MEASURED FROM ORIGINAL TKT DATE TO
DEPARTURE OF PRICING UNIT
WHEN CHANGE RESULTS IN LOWER FARE SUBTRACT RESIDUAL
FROM THE PENALTY THEN ADD-COLLECT/REFUND - REFUND VIA
VOUCHER
ENDORSEMENT BOX- HIGHER NON-REF AMT AND NEW
ENDORSEMENTS.
OR - Cat 31 rec 3 table 00050291
AFTER DEPARTURE OF JOURNEY AND WITHIN TKT VALIDITY 988 rec 3
00028519 proc tag 02[current]
IN THE CASE OF DEATH OF PASSENGER OR FAMILY
987 table 00000003= 01 death

Waiver table

MEMBER - CERTAIN DOMESTIC REISSUE PROVISIONS MAY

BE OVERRIDDEN BY THOSE OF US INTERNATIONAL FARES
REPRICE USING FARES IN EFFECT WHEN TKT WAS
ISSUED
PROVIDED ALL OF THE FOLLOWING CONDITIONS ARE
MET1. NO CHANGE TO 1ST FLIGHT COUPON
2. WHEN NO INTL COUPONS REMAIN - ALL NEW TRAVEL
MUST BE DOMESTIC
3. CHANGE IS ON/BEFORE DAY OF ORIGINAL
SCHEDULED FLIGHT
4. ANY CARRIER FARES ARE USED
5. PRIVATE TARIFFS ARE INCLUDED
6. ALL RULE AND BOOKING CODE PROVISIONS ARE MET
7. VALIDATE ADVANCE RES REQUIREMENTS WHEN

38
Copyright SITA Information Networking Computing

USA Inc 2009. Confidential. All Rights Reserved.

BOOKING DATE KNOWN

8. ADV RES IS MEASURED FROM ORIGINAL TKT DATE
TO DEPARTURE OF PRICING UNIT
WHEN CHANGE RESULTS IN LOWER FARE SUBTRACT
RESIDUAL FROM THE PENALTY THEN ADD-COLLECT/REFUNDREFUND VIA VOUCHER
ENDORSEMENT BOX- HIGHER NON-REF AMT AND NEW
ENDORSEMENTS.

39
Copyright SITA Information Networking Computing

USA Inc 2009. Confidential. All Rights Reserved.

Processing Flow Chart for Category 33 Refund

General Rule
Not Permitted

Original Fare
Published and Constructed

Foot Note
Not Permitted

Fare Class Application

Record 1

Alternate General
Rule sequence list
for:
Tariff Rule Category
33

Record 2
Match to fare from record 1
indicator

Record 3
Data string referenced by
record 2. Attempt multiple
table matching for each fare
component

Resulting Provisions from

general rule or alt general
rule

40
Copyright SITA Information Networking Computing

USA Inc 2009. Confidential. All Rights Reserved.

Voluntary refund information can be divided into major sections

as detailed below.

Section
WHO

Source
Location
CATEGORY 33

WHEN

CATEGORY 33

PROVIDED
REFUNDS
PERMITTED

CATEGORY 33
CATEGORY 33

REPRICING FLOWN
PORTIONS

CATEGORY 33

REFUND CHARGES
AND APPLICATION

CATEGORY 33

Bytes
bytes 8 - 10
bytes 14 - 19
bytes 20 - 22
bytes 23 - 40
byte 41
byte 42
bytes 44 - 49
bytes 114 - 119
bytes 143 - 145
bytes 11 - 13
byte 43

Field Name
Passenger type code
Ticket validity
J/PU/FC
Advance cancellation
Ticketing time limit
Advance reservation validation
Originally scheduled flight
Customer first
Override date table 994
Waiver Table 987
Fully Flown

byte 50
byte 51
byte 52
bytes 53 - 54
byte 55
bytes 56 - 59
bytes 60 - 68
bytes 69 - 71
byte 72
byte 73
byte 74
byte 75
byte 76
bytes 77 - 105
byte 106
byte 107
byte 108 - 111
byte 112
byte 113
byte 120 - 122

Cancellation Indicator
Fare break points
Reprice indicator
Tariff
Tariff Indicator
Rule Number
Fare class / family / type
fare type table 974
Same fare class / family
Normal / Special
OW / RT
Fare Amount
RBD
Charges - amount/percent/low/high/min
PU / FC
Calculation Option
Discounts
Form of Refund
Tax is Non Refundable
Carrier Table 990

41
Copyright SITA Information Networking Computing

USA Inc 2009. Confidential. All Rights Reserved.

SITA Airfare Reprice Refund processing options

SITA has optional processing that is available to customers who would like to enhance
their Airfare Reprice Refund product.
Backdating
Reissue/Refund data via Category 31/33 is captured at the time of ticket issuance, which
requires that the fare owning carriers Category 31/33 data must be in place prior to
ticketing.
ARR processing uses the ticket issue date of the original ticket as match criteria when
searching for the correct Cat31/33 data.
Backdating will allow ARR to process tickets which have already been issued, by
allowing carriers to code 31/33 data retroactively and choose a historical previous
effective date.
ARR Backdating table will allow the airline customer to begin coding category 31 by trial
and error with the ability to capture the final coding solution as the version of coding that
should be used in production.
This will allow the carrier to benefit from ARR as if they had been coding Category 31
since the chosen date in the past (the backdate). Any new Category 31 criteria can then
be coded going forward for tickets issued on after the real time current date. Backdated
data will be retained in history with the backdated effective date just as is all rule data.
Variance Table
In order to correctly re-price the original ticket, ARR processing must retrieve the
associated Category 31 data of the originally ticketed fare(s).
This is achieved via a search using fare basis code as the match criteria. When there
are different fare levels with the same fare basis code, to ensure the correct one is
chosen, the CRT owner can set the Variance table to also match by fare amount, with a
variance, set at a percentage, 5% for example. This process will eliminate fares outside
of the variance range. If a fare amount does not match then an error message will be
returned: unable to reprice.
Variance Options:
1. If no variance percentage is set then select the fare that matches the original fare
amount. In the case that there is not a match select the closest fare to the original fare
amount. If there are two fares that are the same difference from the original fare amount
then choose the lowest fare amount.
Example:
The original Y fare is $1000. Three Y fares are returned based on a fare class match of
Y. The Three Y fare amounts are; Y $50, Y $900, Y $1100.
Since there is not an exact match of Y $1000, processing will select the closest fare to
the original fare amount. In this example there are two fares that are the same difference

42
Copyright SITA Information Networking Computing

USA Inc 2009. Confidential. All Rights Reserved.

from the original Y $1000 fare; Y $900 and Y $1100. Processing will then select the
lowest fare amount Y $900.
2. If variance percentage is set to zero (0) then there must be an exact match of the
original fare amount to the available matching fare.
Example:
The original Y fare is $1000. Three Y fares are returned based on a fare class match of
Y. The Three Y fare amounts are; Y $50, Y $900, Y $1000.
Since there is an exact match of Y $1000 that fare will be returned.
3. If a variance percentage is set (i.e. 5%) then the process will eliminate fares outside of
the variance range. Processing will then select the fare that matches the original fare
amount. In the case that there is not a match to the original fare amount then the fare will
be selected that is closest to the original fare amount. If there are two fares that are the
same difference from the original fare amount then the lowest fare amount will be
returned.
Example:
The original Y fare is $1000. Variance is set at 15 percent = range $850 - $1150. Three
Y fares are returned based on a fare class match of Y. The three Y fare amounts are;
Y $50, Y $900, Y $1000.
In this example the Y $50 fare will be discarded due to the fact that the fare amount is
outside the variance range of $850 - $1150. There are two fares that are the same
difference from the original Y $1000 fare and both fares are in the variance range; Y
$900 and Y $1100. Processing will select the lowest fare amount Y $900.
Bypass Security Table
In order to correctly re-price the ticket, ARR processing must retrieve the associated
Category 31 data of the originally ticketed fare(s). When the originally ticketed fares are
secured private fares, processing must be able to Bypass Security in order to find the
correct fare(s) and the associated Category 31 data of the secured private fare.
This Bypass of Security table is only valid when the CTR/owner is the same as fare
owning Carrier. Essentially, this table is for when a carrier is reissuing its own
fares/ticket.
BIT 31 Processing
BIT 31 is designed to return an additional fare offer in the ARR Reprice response, which
is outside of the input RBD on the itinerary in question.
A technical description of BIT 31 processing is as follows:

43
Copyright SITA Information Networking Computing

USA Inc 2009. Confidential. All Rights Reserved.

With Bit 31 = 0 (ie. BIT 31 turned off) ARR will only produce a repricing response if valid
RBD's are entered. If RBD's entered cannot generate a repricing response, no
alternative fare offer will be returned.
With Bit 31 = 1 (ie. BIT 31 turned on) if valid RBD's are entered, ARR will produce a
repricing response (same as value zero). However, if invalid RBD's
are entered, ARR will produce one (lowest) repricing response plus a warning message
*NO FARES/RBD/CARRIER
*ATTN VERIFY BOOKING CLASS SEE FSS
Example Reprice output with BIT 31 activated:
Itinerary is booked with RBD U, and a GLIMBO fare is offered as an alternate; as there
are no valid fare offers using RBD U
FSRE
********************** REPRICE SUMMARY *********************
NO WAIVER
ITINERARY REPRICED USING CURRENT FARES
BASE FARE DIFF

USD

+122.00

ADC

REISSUE FARE DIFF

USD

+122.00

ADC

TFC DIFF

USD

+18.90

ADC

TICKET DIFF

USD

+140.90

ADC

SVC FEE

USD

+125.00

ADC

GRAND TOTAL

USD

+265.90

ADC

*************** REVISED ITINERARY INFORMATION **************

FSICD///POS*POS.07MAY10
U*BW

U28OCT POS

NYC0S

EQP

#OBW #FY

U*BW

U15MAY NYC

POS0S

EQP

#OBW #FN

*NO FARES/RBD/CARRIER
*ATTN VERIFY BOOKING CLASS SEE FSS
*SYSTEM DEFAULT-CHECK EQUIPMENT
*ATTN*PFC MAY APPLY/USE DEP ARPT SEG 2
*US FLT SGMNT TAX MAY APPLY. SEE FXT/US/ZP
*CONFIRMED RESERV NEEDED ON SEG 1,2
*TICKETS ARE NON-REFUNDABLE
*ATTN REPRICED ON 07MAY10*1344

44
Copyright SITA Information Networking Computing

USA Inc 2009. Confidential. All Rights Reserved.

********************* FARE CALCULATION *********************

POS
NYC GLIMBO

CD10

NVB28OCT NVA28OCT PC

POS GLIMBO

CD10

NVB15MAY NVA15MAY PC

FARE

USD

350.00 EQUIV

TTD USD

NEW TFC USD 18.90

TOTAL USD

140.90A

POS BW NYC Q5.00 170.10BW POS Q5.00 170.10NUC350.20END ROE1.

000000
PAID TAX/FEE/CHARGE
PD TTD 4800.00DD PD TTD 10000.00KT PD TTD 21500.00TT
PD TTD 1600.00AY PD TTD 20400.00US PD TTD 3200.00XA
PD TTD 4400.00XY PD TTD 25200.00YQ TFC END
NEW TAX/FEE/CHARGE
USD 18.40TT USD 0.50XA TFC END
ENDOS CANCEL/CHANGE FEE APPLIES
RATE USED 1USD=6.302000TTD
TKT/TL28OCT09

Example Reprice output without BIT 31 activated:

No alternate fare offers are returned, as itinerary is booked in RBD U, however no valid
fares are offered using RBD U
FSRE
********************** REPRICE SUMMARY *********************
MANUAL REISSUE REQUIRED - UNABLE TO AUTOMATE PROCESS
*************** REVISED ITINERARY INFORMATION **************
FSICD///POS*POS.07MAY10
U*BW

U28OCT POS

NYC0S

EQP

#OBW #FY

U*BW

U10MAY NYC

POS0S

EQP

#OBW #FN

45
Copyright SITA Information Networking Computing

USA Inc 2009. Confidential. All Rights Reserved.