Auto Sales Validation - DOC

Document Sample
Auto Sales Validation - DOC Powered By Docstoc
					IATA Software for Industry Settlement
               (ISIS)

            RET Validation Guide




 Date:      24 January 2012
 Version:   1.8
ISIS RET Validation Guide



                                       REVISION HISTORY

 Version       Date           Author   Summary of changes

   0.1      25 Nov 03       M Cozens   Original Draft

   0.2      26 Nov 03       A Casey    Change to Error Description for 246,259, 280 and 281 to include CANX
                                       and CANN

   1.0      26 Nov 03       R Cole     Expand introduction; miscellaneous cosmetic corrections, restructuring,
                                       clarifications

   1.1      10 Dec 03       G. Braun   Changed Refund Validation Description + Description for errors R17, R24,
                                       R28 and R41.

   1.2      15 Dec 03       G. Braun   Changed Standard R24 Validation. Check now includes amounts from
                                       other refunds refunding the same ticket.

   1.3      17 Dec 03       G. Braun   Changed Standard R11 Validation. No error due to payment type
                                       difference, if due to pseudo cash on original and no cash on a credit
                                       refund.

   1.4      18 Dec 03       G. Braun   Removed comment in some 8nn errors regarding they will cause a ticket
                                       to be converted to cash. This happens if error is set to be Billing Critical
                                       and a CC error, and the BSP is set to convert them to cash.

   1.5      17 Mar 04       G. Braun   Added new error 529.

   1.6      24 Mar 04       G. Braun   Modified errors 502 and R24 due to ISIS5.0 Germany Enhancements. 502
                                       has more validation, R24 has more validation and error description
                                       change.

   1.7      29 Apr 04       G. Braun   Modified R11. Assume CA payment of archived NR ticket is pseudo cash.
              th
   1.8     18 May 04        G. Braun   Fixed up description of blank error type setting. Fixed up description of
                                       error 301.




                                               Page 2 of 23
ISIS RET Validation Guide



INTRODUCTION

ISIS RET error validation was developed according to DISH validation requirements, and applies to both
automated and manual transactions. In addition, ISIS has the capability of reporting and controlling RET
validation errors on several levels, which can be controlled by each BSP based on local data processing
requirement.
As per DISH Section 4.2, error reports with the corresponding transactions can be provided to GDS, agents,
airlines, and BSP (RPRETERR report).

Error levels that may be applied to each error code are:

   B = Billing Critical – This setting indicates all errors that should normally be corrected prior to processing
    (e.g. invalid agent or airline code). For CC transactions, this status will stop the transactions from being
    invoiced. The transactions will automatically be displayed in the ISIS data correction screen. If nothing is
    done to correct or delete the Billing Critical transactions, they will be billed (if the Agents are released for
    Billing).
    o Delete = Y or N – indicates whether the Billing Critical transaction should be automatically deleted or
         not. Deleted transactions can still be later undeleted, corrected and processed.
    o CC Error = Y or N – Indicates whether an error is considered a credit card error. If set to Y and BSP
         option is to convert billing critical credit card errors to cash (Separate option for Sales and Refunds) then
         credit card tickets with the error will have the CC payment converted to cash.

   W = Warning: This setting will report the error but not take any action (e.g. agent has no CIP for the airline).

   N = Not Validated: This setting will ignore the error and not check or report it at all (e.g. TOTL not
    provided).

   Blank = Default ISIS Setting: The error is reported according to the default setting if left blank. The
    default validation setting is listed in the second column in the tables below.


The following tables describe:

1. Standard errors.
2. Refund errors (standard + optional).
3. Variable commission errors (optional).




                                                   Page 3 of 23
ISIS RET Validation Guide

1. Standard errors
Error   Default   Description
Code     ISIS
        Setting
102       B       IT05 RECORD MISSING
                  The IT05 record of this transaction, containing monetary amounts, is missing.
                  Note: this does not apply to Cancelled transactions.
103       B       IT08 RECORD MISSING
                  The IT08 record of this transaction, containing the Form of Payment types and Amounts, is missing.
                  Note: this does not apply to Cancelled transactions.
104       B       TDAM - TOTAL DOC AMT NOT EQUAL TO FPAM
                  The Ticket/Document amount on this transaction (TDAM in IT05 record) does not equal the Form of
                  Payment Amount (FPAM in IT08 record).
108       B       NON-NUMERIC COMMISSION AMOUNT
                  The commission amount field on this transaction (COAM in the IT02 record) is a numeric field, but
                  contains a non-numeric entry.
109       B       INVALID TAX AMOUNT
                  All Tax Types (TMFT) are reported in the IT05 record and must have a corresponding Tax Amount
                  (TMFA). There is no Tax Amount reported for a Tax Type in this transaction (excluding the XF
                  types).
111       B       TDAM DOES NOT COVER TAX AMOUNT
                  This transaction has reported incorrect amounts. The sum of the Taxes (TMFA‟s in the IT05 record)
                  is greater than the Ticket Document Amount (TDAM).
112       B       SUSPICIOUSLY HIGH VALUE FOR TAX
                  Warning Feature: If the BSP has set up Tax Limits in ISIS, then this transaction is reporting a tax
                  value that exceeds the expected value.
                  Set Up SCREEN: OPERATIONS >REF> BSP>Amounts Limits
115       B       IT05 RECORD FOUND FOR CANCELLATION
                  A cancelled transaction should not report an IT05 record which contains monetary amounts.
116       B       SUSPICIOUSLY HIGH VALUE FOR COAM
                  Warning Feature: If the BSP has set up Commission Amount Limits, then this transaction is
                  reporting a Commission Amount (COAM) that exceeds the expected level.
                  Set Up Screen: OPERATIONS >REF> BSP>Amounts Limits
117       B       SUSPICIOUSLY HIGH VALUE FOR TDAM
                  Warning Feature: If the BSP has set up a Ticket Document Amount Limit, then this transaction is
                  reporting a Ticket Document amount (TDAM) that exceeds the expected level.
                  Set Up Screen: OPERATIONS >REF> BSP>Amounts Limits
118       B       NON-PRINTABLE CHARACTER IN RETLOAD FILE
                  The RET file can not be loaded or has been loaded but has located non printable characters eg
                  hash, asterix etc. This error may cause problems with some transactions if not fixed.
119       W       IT02 RESERVED SPACE BEING USED
                  Revision 20 and higher: A reserved space in the IT02 Basic Sale record has an entry where it
                  should be blank. This error is normally set to Warning only.
120       W       IT03 RESERVED SPACE BEING USED
                  Revision 20 and higher: A reserved space in the IT03 Related Tkt Document information record
                  has an entry where it should be blank. This error is normally set to Warning only.
121       W       IT04 RESERVED SPACE BEING USED
                  Revision 20 and higher: A reserved space in the IT04 Additional Sale information record has an
                  entry where it should be blank. This error is normally set to Warning only.
122       W       IT05 RESERVED SPACE BEING USED
                  Revision 20 and higher: A reserved space in the IT05 Monetary Amounts record has an entry
                  where it should be blank. This error is normally set to Warning only.
123       W       IT06 RESERVED SPACE BEING USED
                  Revision 20 and higher: A reserved space in the IT06 Itinerary record has an entry where it should
                  be blank. This error is normally set to Warning only.
124       W       IT07 RESERVED SPACE BEING USED
                  Revision 20 and higher: A reserved space in the IT07 Fare Calculation record has an entry where it
                  should be blank. This error is normally set to Warning only.
125       W       IT08 RESERVED SPACE BEING USED
                  Revision 20 and higher: A reserved space in the IT08 Form of Payment record has an entry where
                  it should be blank. This error is normally set to Warning only.


                                                 Page 4 of 23
ISIS RET Validation Guide
1. Standard errors
Error   Default   Description
Code     ISIS
        Setting
126       W       IT09 RESERVED SPACE BEING USED
                  Revision 20 and higher: A reserved space in the IT09 Additional Information record has an entry
                  where it should be blank. This error is normally set to Warning only.
127       W       IT0A RESERVED SPACE BEING USED
                  Revision 20 and higher: A reserved space in the IT0A Miscellaneous Document Information record
                  has an entry where it should be blank. This error is normally set to Warning only.
128       W       IT0B RESERVED SPACE BEING USED
                  Revision 20 and higher: A reserved space in the IT0B Additional Miscellaneous Doc information
                  record has an entry where it should be blank. This error is normally set to Warning only.
129       W       IT0C RESERVED SPACE BEING USED
                  Revision 20 and higher: A reserved space in the IT0C Miscellaneous Document Information-
                  additional lines record has an entry where it should be blank. This error is normally set to Warning
                  only.
130       W       IT0D RESERVED SPACE BEING USED
                  Revision 20 and higher: A reserved space in the IT0D Miscellaneous Document Information –
                  additional lines record has an entry where it should be blank. This error is normally set to Warning
                  only.
131       W       IT0E RESERVED SPACE BEING USED
                  Revision 20 and higher: A reserved space in the IT0E Automated PTA Sponsor Information record
                  has an entry where it should be blank. This error is normally set to Warning only.
132       W       IT0S RESERVED SPACE BEING USED
                  Revision 20 and higher: A reserved space in the IT0S Stock Control Number record has an entry
                  where it should be blank. This error is normally set to Warning only.
133       W       IT0Y RESERVED SPACE BEING USED
                  Revision 20 and higher: A reserved space in the IT0S Agency Data record has an entry where it
                  should be blank. This error is normally set to Warning only.
134       W       OAAI NOT PROVIDED
                  Revision 20 and over:
                  This transaction has not reported any information in the Optional Agency/Airline Information field
                  (OAAI in the IT0B record). This information comes from print line „A‟ of ATB2 type documents.
135       W       PLID NOT PROVIDED
                  Revision 20 and over:
                  This transaction has reported the first PLID field (Print Line Identifier) in the MPD‟s IT0C, IT0D or
                  IT0E records as a blank. It must be in the alphabetic range of A-S and be presented in ascending
                  order.
136       W       SPIN NOT PROVIDED
                  Revision 20 and over:
                  This transaction is an MD40, but the ITOE record (Automated PTA Sponsor Information record)
                  does not contain information in the first SPIN field.
137       W       SSAC Reported Amount exceeds Maximum Amount
                  For BSPs where a SSAC (Sales Summary Adjustment Notice eg Canada or Minor Adjustment
                  Notice eg UK and IE) limit has been set up in ISIS:
                  Set up SCREEN: Limits are set up in OPERATIONS >REF> BSP>Amounts Limits

                  The Ticket Document Amount (TDAM) is greater than the setup SSAC limit. Note: SSAC is a
                  transaction type (TRNC).
138      N/A      FPAM – Reported Amt exceeds Maximum Amt
                  CYPRUS only:
                  If a Net Remit sale with a Credit value is reported in Form of Payment Amount field (FPAM in the
                  IT08 record), then it must equal the Amount Entered by Agent (AEBA in the IT05 record) value plus
                  total taxes.
139       W       Invalid Alpha Character
                  This transaction has reported an invalid alpha character in an alphanumeric field.
                  Note: There are exceptions to some fields eg TOTL must contain a decimal point, FPIN can have a
                  slash etc.
140       W       Invalid Alphanumeric Character
                  This transaction has reported an invalid alphanumeric character in an alphanumeric field.
                  Note: There are exceptions to some fields eg TOTL must contain a decimal point, FPIN can have a
                  slash etc.

                                                  Page 5 of 23
ISIS RET Validation Guide
1. Standard errors
Error   Default   Description
Code     ISIS
        Setting
201       B       AGENT CODE HAS INVALID CHECK DIGIT
                  Agent codes comprise 7 digits, followed by a modulus -7 check-digit. This transaction has reported
                  an invalid agent code whose check digit has failed the modulus-7 check.
202       B       AGENT CODE NOT ON MASTER FILE
                  The Agent code (AGTN reported in IT05 record) on this transaction is not present in the Agent
                  Master Table OR it has been set to Inactive (set to I in the Agent Screen).
203       B       CJCP - SHOULD BE BLANK FOR PRIMARY IT02
                  The Conjunction Indicator field (CJCP reported in the IT02 record) of this first or primary ticket must
                  be blank. It may only be filled in the secondary or conjunction ticket/s.
204       B       AGENT CODE ON CONJUNCTION/COMPANION
                  This transaction‟s Agent Code field (AGTN reported in the IT02 record) in the conjunction ticket is
                  different from the Agent code reported in the primary ticket.
205       B       CJCP - SHOULD BE CNJ OR CMP IF NOT PRIMARY
                  This transaction is reporting a second (or more than one IT02 record for a conjunction) but the
                  conjunction ticket/s details do not contain the entry CNJ (conjunction) in the CJCP field/s of the IT02
                  record.
                  DISH 10 – 11 inclusive: If CJCP is blank on the conjunction transaction, then the system will insert
                  CNJ indicator into the CJCP field.
                  DISH 20 and up: The system will NOT automatically correct this error. This error message is
                  generated instead.
                  COMPANIONS: If the Conjunction indicator field reports Companion (CJCP = CMP) and the RET
                  is not Revision 9, then it will be rejected with this error message.

207       W       AGTN - HOST APPROVED LOCATION INVALID
                  This transaction has reported an Agent code (AGTN in IT02 record) which is on the Master File and
                  Active, but the Agent location type in the Agent Master Table is not one of the following codes:
                  „AO‟, „BR‟, „HO‟, „SA‟, „SE‟.

208       B       CNJ PLATED TO DIFFERENT AIRLINE FROM PRI TCKT
                  The Ticketing Airline code (TACN) reported in this transaction‟s conjunction tickets/s is not the same
                  as the Primary ticket Airline code.
209       B       CORT - INVALID 1% ENTERED
                  AUSTRALIA ONLY:
                  If the Commission rate (CORT in IT05) is reported as 00001” then it will be rejected.
210       B       AGENT HAS NO CIP PLATE FOR AIRLINE
                  This transaction has reported an Airline code (TACN in IT02 record) but the Airline CIP (Carrier
                  Identification Plate) is not assigned by the Carrier to this Agent.
211       B       TICKET HAS INVALID AIRLINE NUMBER
                  For DISH 10.2 and up:
                  This transaction has reported an Airline Code with the ticket number in the field TDNR (Ticket
                  Document Number in IT02) which is different from the Ticketing Airline Code or TACN reported in
                  the IT02 record.
                  Note: This check excludes RSCN and VSCN and Refunds.
212       W       TICKET HAS INVALID CHECK DIGIT
                  The ticket number in this transaction‟s Ticket Document Number field (TDNR reported in the IT02
                  record), has failed the modulus-7 check digit verification.
                  Note: For ATB2s, the Airline code is also included in the mod-7 check.
215       B       TICKET HAS BEEN RELEASED TO BILLING
                  The system could not action a cancellation request (CANR) on this transaction as the ticket has
                  already been billed.
218       B       TICKET NUMBER IS MISSING
                  This transaction‟s ticket number reported in the Ticket/Document Number field (TDNR of the IT02
                  record) is missing.
                  Note: This check excludes VSCN (Voided Stock Control Number) transactions
219       B       CPUI - IS INVALID
                  This transaction has reported an invalid character in the Coupon Use Indicator field (CPUI of the
                  IT02 record). The values must be either „B‟, „F‟, „S‟, „V‟ or blank.
                  Note: For Revision 11 and up, „R‟ is not permitted.


                                                   Page 6 of 23
ISIS RET Validation Guide
1. Standard errors
Error   Default   Description
Code     ISIS
        Setting
220       B       CPUI CONTAINS REFUND COUPONS FOR TRNC
                  Revision 10 to 10.3 only:
                  This ticket has reported an „R‟ for refund in the Coupon Use Indicator field (CPUI of the IT02 record)
                  which is only valid for Refund transactions (RFND‟s).
226       B       TRANSACTION - IS UNRECOGNISED
                  The transaction code, which identifies what sort of transaction this is, eg TKTT = ET, and reported in
                  TRNC field of the IT02 record) is not a valid transaction code.
227       B       AIRLINE CODE IS INVALID
                  The Airline code (TACN reported in the IT02 record) for this transaction does not exist in the Airline
                  Master File and so can not be billed.
229       N       SUPPLIED COMMISSION RATE OVERWRITTEN BY DEFAULT RATE
                  For BSP‟s that have set up Default Commission rates:
                  The Commission rate on this transaction (CORT in IT05 record) has been overwritten by the
                  System as the reported rate was unacceptable.
                  Set up SCREEN: Data Corrections -> Ref -> Airline Default Commission Rates.
234       B       AGENT HAS INVALID BSP
                  Agent exist in agent master table but for a different BSP.
235       B       INVALID DATE OF ISSUE
                  The Date of Issue reported in this transaction (DAIS in the IT02 record) is not valid, ie the format is
                  not YYMMDD, or there are invalid characters.
                  Note: This check excludes ACM/ADMs and Refunds.
236       B       CONJUNCTION TICKET HAS DATE OF ISSUE NOT EQUAL TO PRIMARY
                  The date of issue (DAIS in the IT02 record) reported on this transaction‟s conjunction tickets, is not
                  the same as the date of issue on the primary ticket.
                  Note: This excludes ACM/ADM and Refunds.
239       B       DUPLICATE TICKET NO. FOUND, CHECK
                  This transaction is reporting a duplicate document number Checks are as follows:
                  a) If duplicate Refunds, ADM or ACMs are found with the same Agent, Airline and ticket number
                      then this error is reported..
                  b) Live Tkt / Live Tkt: When duplicate tickets are found in this and/or previous billing periods, and
                      the current one is not a cancellation (CANX or CANR), then report this error as the ticket is
                      reported twice.
                  c) Live / CANX: When a live ticket has been reported, and invoiced or billed (previous period), and
                      the ticket is reported again as a CANX or cancelled transaction, the system will generate Error
                      message 215 or 285
                  d) Live / CANR: If a live ticket has been reported, and invoiced or billed (previous period), and the
                      ticket is reported again as a CANR or cancellation request transaction, the system will generate
                      message 287.

240       B       MIXED TRNC CODES FOUND IN THIS TRANSACTION
                  This ticket has conjunction tickets and the transaction code/s in their IT02 records eg TKTA
                  (OPTAT), TKTT (ET) are different from the primary ticket‟s code.
244       B       DATE OF ISSUE OUT OF RPT PERIOD
                  The date of issue on this transaction (DAIS reported in the IT02 Record) is outside of the reporting
                  period. This error arises if you had for instance 2 reporting periods per billing period. The DAIS may
                  be within the billing period but may be outside the reporting period so becomes more of a warning.
245       B       DATE OF ISSUE OUT OF BILLING PERIOD
                  The date of issue on this transaction (DAIS reported in the IT02 Record) is outside of the Billing
                  period.
246       B       CANCELLED CONJUNCTION TICKETS
                  A Cancellation request has been reported for a conjunction ticket instead of the prime ticket. The
                  cancellation request (CANR, CANX or CANN) must be for the prime ticket only, and this will cancel
                  the conjunctions automatically.
247       B       STOCK NOT ON AGENTS FILE
                  This transaction number is not present in the Agents Stock on Hand.
                  Checks transaction types: TKTA, TKTB, TKTM, MCOA, MCOM, MPnn, CANX, CANR, CANN.




                                                  Page 7 of 23
ISIS RET Validation Guide
1. Standard errors
Error   Default   Description
Code     ISIS
        Setting
250       B       AGENT SELLING TICKET FOR INCORRECT AIRLINE
                  Australia Only:
                  If the Airline is an international carrier, and the Agent is a DAPA agent, then report this transaction
                  as an error.
251       W       AIRLINE HAS INVALID CHECK DIGIT
                  The Airline Code (TACN) reported on this transaction does not have a valid check digit as verified
                  by the Modulus-7 check.
                  The CDGT associated with TACN reported in the IT02 record is verified by Mod-7 validation.
                  Note: This does not check VSCN / RSCN transactions.
252       W       TCNR - INVALID CHECK DIGIT
                  The Transmission Control Number (TCNR), generated by the GDS and reported in the IT02 record
                  of this transaction, has failed the Modulus-7 check digit test.
253       B       AGENT TERMINATED - PLS SEE COLLECTIONS OFFICER (DORA)
                  This transaction has been reported for an Agent that has been terminated, and the ticket issue date
                  and/or the Billing period is after the date of termination. Unless released to billing, these
                  transactions will not be billed by the System.
254       B       AGENT HAS NO DEFAULT COMMISSION RATE FOR AIRLINE
                  For BSP‟s that have set up Default Commissions for their Airlines:
                  The Commission rate (CORT) on this transaction, has been checked by the System to ensure it is
                  valid for this Airline but there is no Default Commission set up for this Airline.
                   Set up SCREEN: Data Corrections -> Ref -> Airline Default Commission Rates.
256       B       COMMISSION RATE INVALID
                  The Commission Rate (CORT in the IT05 record) on this ADM or ACM should be nil, as only
                  commission amounts should be reported.
257       B       TICKET NUMBER NOT SEQUENTIAL WITH PRIMARY
                  Each ticket in the RET file has a sequence number. A conjunction ticket must be sequentially
                  higher than its primary ticket, and must not skip a number. This transaction is not sequentially
                  higher. Eg, PRI = 1000000012, CNJ = 1000000013.
258       B       TICKET ALREADY CANCELLED CHECK IF VALID
                  A live ticket has been loaded that has already been reported as cancelled in a previous period in the
                  system.
                  If not corrected: If the tickets are in the same period, airline and agent, then the system assumes
                  the cancellation was loaded before the original and therefore will not load the original, leaving the
                  existing cancelled transaction for billing.
259       B       CANCELLATION HAS ERRORS, TRANSACTION NOT CANCELLED
                  A Cancellation Request (CANR, CANX or CANN) has been received, but could not be actioned due
                  to other critical errors with the ticket. The original ticket is not cancelled and the system will report
                  this error.
                  Note: Both the original and the cancellation will exist in the system until corrected.
260       B       CORT - INVALID 2% ENTERED
                  AUSTRALIA ONLY: The commission rate on the RET file was reported as „00002‟ in error.
261       B       CORT - INVALID 3% ENTERED
                  AUSTRALIA ONLY: The commission rate on the RET file was reported as „00003‟ in error.
262       B       STOCK CONTROL NUMBER REPORTED AS A TICKET NUMBER
                  The ATB2 Stock control numbers are already printed on the document and when the ticket is issued
                  the Ticket Number is also printed on the document. So there is a Stock Control Number and a
                  Ticket Number on the same document.
                  Excluding ACMs, ADMs, RSCN and VSCN, ie for Issues only, an ATB2 series number has been
                  reported in the TDNR field in error. These numbers should only be reported in the SCNF / SCNR /
                  SCNT fields.
263       B       SCNT - INVALID VALUES
                  The Stock Control Number „To‟ (SCNT in IT02 record) on this transaction was greater than zero
                  and/or less than the Stock Control Number „From‟ (SCNF in IT02 record).
264       B       DOCUMENT NUMBER NOT FOUND
                  This ticket document number (TDNR reported in the IT02 record) does not belong to a recognized
                  series for this BSP.
                  Note: Validation excludes: ACM, ADM, Refunds, RENx and VSCN / RSCN.



                                                   Page 8 of 23
ISIS RET Validation Guide
1. Standard errors
Error   Default   Description
Code     ISIS
        Setting
265       B       DOCUMENT TYPE NOT FOUND
                  This ticket document number (TDNR reported in IT02 record) does not have a recognized document
                  type set up, eg OPTAT, Manual 4 stage etc.
266       B       ATB2 - AGENT CODE NOT IN AGT TABLE
                  The Agent Code/s found in this ALNC (Approved Location Numeric Code) field of the IT02 record
                  are not found or have become inactive.
                  These numeric codes are Approved agents electronically connected to the Agent specified in the
                  AGTN field, and receive some or all of the coupons of this transaction.
267       B       DUPLICATE SCNR
                  This transaction‟s Stock Control Number Range (SCNR in IT02/IT0S record) is already present in
                  the system, so can not be duplicated.
268       B       STOCK CONTROL NO. MISSING
                  Applicable to ATB2‟s, VSCN or RSCN transactions:
                  There are no SCNs (Stock Control numbers) reported in the SCNF (Stock Control Number „From‟)
                  and SCNT (Stock Control Number „To‟) fields of the IT02 record.
269       B       STOCK NOT ON ATB2 AGENTS FILE
                  For ATB2s only: The Stock Control Numbers are not on the Agents Stock on Hand records.
272       W       INVALID ISO COUNTRY CODE
                  The ISO Country Code (ISOC in IT02 record) must be a valid ISO code for the BSP and the Agent
                  being processed.
273       B       INVALID FIELD LENGTH FOR TDNR
                  The Ticket document number component (removing the Airline Code), of the TDNR field in the IT02
                  record, must be no more than TEN characters.
                  The Ticket Document Number Field comprises of three parts:
                  Airline Code = 3 digits
                  Form Code = Max of 3 digits indicating type of document
                  Serial Number = Max of 8 digits allocated on a sequential basis and not exceeding 10 digits for both
                  Form and Serial combined.
                  Note: If VSCN or RSCN – extra characters may be 0, ie the field is zero filled.
274       B       SCNT - DIFFERENCE IN SCNT AND SCNF IS MORE THAN 8
                  The maximum number of SCNs (Stock Control Numbers in IT02 record) has been exceeded in the
                  RET. (8000 SCNs for a batch of 200 tickets).
275       W       INVALID AIRLINE CODE, IT HAS BEEN ASSIGNED TO 954
                  The Airline Code (TACN in IT02 record) has been reported as an invalid Airline, so the System has
                  changed it to Airline Code 954 (IATA).
276       B       INVALID CPUI FOR THIS SERIES AND THIS TRNC
                  This transaction has reported an invalid entry in the Coupon Use Indicator (CPUI in the IT02
                  record). Entries must be B (Boarding Pass), F (flight coupon), S (surface sector), V (void coupon)
                  and the number of entries must correspond to the type of document eg OPTATs require 4 entries.
277       W       CPUI IS NOT APPLICABLE FOR THIS TRANSACTION
                  This transaction has reported an invalid entry in the Coupon Use Indicator (CPUI in the IT02 record)
                  where it should be blank eg for ADMs and ACMs.
278       W       DISI - MUST CONTAIN F, L OR M for RFND
                  For DISH 20 and above:
                  All Refund transactions (RFNDs) must contain an entry in the DISI (Data Input Status Indicator) field
                  which indicates the mode of data capture. Acceptable entries are: F = Fully automated, L = Mixed
                  Automated and Manual data capture or M = Manual data capture. This transaction reported an
                  incorrect entry or none at all.
279       W       IF TRNC IS "ADMS" OR "ACMS", THE 4TH POSITION OF TDNR MUST BE "6" OR "8
                  When the Ticket Document Number (TDNR in IT02 record) is reported for ADM‟s and ACM‟s, the
                  fourth character (after the Airline Code), must be either 6 for ADM‟s or 8 for ACM‟s.
280       W       AGENT ON CANCELLATION DIFFERENT FROM ORIGINAL
                  The Agent Code (AGTN in IT02 record), reported on this Cancellation Request (CANR, CANX or
                  CANN) is different from the Agent code in the original ticket.
281       W       AIRLINE ON CANCELLATION DIFFERENT FROM ORIGINAL
                  The Airline Code (TACN in the IT02 record), reported on this Cancellation Request (CANR, CANX
                  or CANN), is different from the airline code in the original ticket.



                                                  Page 9 of 23
ISIS RET Validation Guide
1. Standard errors
Error   Default   Description
Code     ISIS
        Setting
282       W       ALNC NOT PROVIDED
                  Revision 20 and up:
                  When an IT0S or Stock Control Numbers record is reported to the BSP, the Approved Location
                  Numeric Code field (ALNC in IT0S record) must not be blank. This transaction did not report an
                  Approved Agent code.
283       W       SCNF NOT PROVIDED
                  Revision 20 and up:
                  When a Stock Control Numbers Record (IT0S) is reported to the BSP, the first SCNF or Stock
                  Control Number „From‟ field (SCNF in the IT0S record) must not be blank.
284       W       SCNT NOT PROVIDED
                  Revision 20 and up:
                  When an IT0S or Stock Control Numbers record is reported to the BSP, the first SCNT or Stock
                  Control Number „To‟ field (SCNT in the IT0S record) must not be blank.
285       B       ORIGINAL TICKET HAS BEEN INVOICED
                  The ticket could not be cancelled by a method other than a Cancellation Request record (CANR) ie
                  the Agent or Airline has reported a CANX or CANN transaction.
286       B       AIRLINE TERMINATED
                  For Issues and ADMs only:
                  The Airline Code (TACN) reported on this transaction is for a terminated Airline, and so the
                  transaction can not be billed.
287       B       CANR: RELEASED TO BILLING - DIFFERENT BILLING PERIOD
                  The Agent has reported a Cancellation Request (CANR) for a transaction that was processed in a
                  previous billing period – so it can not be actioned.
288       W       REPORTED COMM RATE IS HIGHER THAN THE MAX RATE
                  Warning Feature based on Maximum Commission Rate set up:
                  Set Up SCREEN: Data Corrections -> Commission Rates (Single Agent)              OR
                                      Data Corrections -> Commission Rates (Multiple Agents).
                  The commission rate (CORT in IT05 record) for this transaction, has been reported with a rate
                  higher than the maximum rate set for this Agent.
289       B       AIRLINE CODE MUST BE 954 FOR TASF TRANSACTION
                  The Airline code (From TDNR) and the Ticketing airline code (TACN) must be 954 for TACN
                  transactions
290       B       CASH TASF TRANSACTION NOT APPLICABLE, AMOUNTS HAVE BEEN SET TO ZERO
                  If the payment record contains non-zero cash record, set all amounts fields to zero. Message will
                  appear with cash TASF transaction not applicable, amounts have been set to zero.
291       B       INVALID CPUI FOR TASF TRANSACTION
                  The TASF transaction does not have a CPUI that is “F” + 3 blanks
292       B       MULTIPLE CC PAYMENTS NOT ALLOWED FOR TASF TRANSACTIONS
                  For TASF transactions, multiple CC payments are not allowed.
293       B       ADMS VALUE CANNOT BE NEGATIVE
                  For ADMS, balance payable which is TDAM – Effective COAM – TOCA cannot be less than 0.
                  If the BSP parameter “Agent or Airline remits TOCA” is set to Airline the TOCA amount is negatively
                  signed else it is positively signed.
294       B       ACMS VALUE CANNOT BE NEGATIVE
                  For ACMS, balance payable which is TDAM – Effective COAM – TOCA cannot be less than 0.
                  If the BSP parameter “Agent or Airline remits TOCA” is set to Airline the TOCA amount is negatively
                  signed else it is positively signed.
301       B       RELATED TKT/DOC HAS INVALID AIRLINE NO.
                  For Refunds, ADMs and ACM‟s:
                  If Revision is < 20.0 It checks that the Related Ticket Document field (RTDN in IT03 record)
                  contains an Airline code.
                  If Revision is >= 20.0 It checks that it is numeric.
303       W       RELATED TKT NO. HAS INVALID CHECK DIGIT
                  This Refund, ADM or ACM Related Ticket Document number field (RTDN in the IT03 record) has
                  failed the modulus-7 check digit validation.
304       W       RTDN NOT PROVIDED
                  DISH 20 and above: For Refunds, ADM‟s and ACM‟s:
                  At least one Related Ticket document number must be reported in the RTDN field of the IT03
                  record. This transaction has not reported any related tickets.

                                                 Page 10 of 23
ISIS RET Validation Guide
1. Standard errors
Error   Default   Description
Code     ISIS
        Setting
305       W       IT03 RECORD NOT ALLOWED
                  DISH 20 and above:
                  This transaction contains an IT03 record, which reports information on the related ticket documents
                  for Refunds, ADM and ACMs, in error.
320       W       AGENT NOT AUTHORISED TO ISSUE ET
                  The Agent issuing this ET transaction is not authorised to issue ET sales.
321       W       CANR:CANCELLATION REQUEST NOT ACTIONED,TKT NOT IN THE SAME REPORTING
                  PERIOD
                  The Agent has reported a Cancellation Request (CANR) for an ET transaction that was processed
                  in a previous billing period – so it can not be actioned.
322       W       CANR:CANCELLATION REQUEST NOT ALLOWED FOR E TKTS
                  For selected BSPs ET Warning feature:
                  The system will not allow a Cancellation request to be actioned for any ET sales.
323       W       CANX: CANCELLATION NOT AUTHORISED BY CARRIER
                  ET Warning Feature: This cancelled ET sale does not have a Settlement Authorisation code
                  created by the Airline system to authorise or approve the transaction - (ESAC reported in the IT02
                  record).
                  Note: This information may be reported in the Unauthorised Transaction Report - RPETEXCP.
324       W       RE-ISSUE: RE-ISSUE NOT AUTHORISED BY CARRIER
                  ET Warning feature: When an ET sale is exchanged for a new ET sale, the Settlement
                  Authorisation Code (ESAC) should be copied from the original ticket into the new Form of Payment
                  Transaction information (FPTI in the IT08 record). This exchange ET transaction does not have that
                  information so is not authorised.
                  Note: This information may be reported to Airlines and Agents in the Unauthorised Transaction
                  Report - RPETEXCP.
325       W       REFUND: REFUND NOT AUTHORISED BY CARRIER
                  ET Warning Feature: This ET Refund does not have a Settlement Authorisation code created by
                  the Airline system to authorise or approve the transaction - (ESAC reported in the IT02 record).
                  Note: This information may be reported to Airlines and Agents in the Unauthorised Transaction
                  Report RPETEXCP.
326       W       UNAUTHORISED ISSUE OF STOCK
                  Warning Feature: This ticket is an ET sale, but is not currently on the Agent‟s Stock on Hand
                  information.
                  Note: This could be due to the TI files not being received or updated into the system.
401       W       BLANK FARE
                  Excluding ADM, ACM and Refunds, the FARE field (a facsimile field in the IT04 record) should not
                  be blank.
402       W       TOTL NOT PROVIDED
                  DISH 20 and above:
                  The TOTAL field (TOTL) reported in the IT04 record as a facsimile field, should not be blank.
502       B       INVALID CURRENCY TYPE FOR THIS COUNTRY (ITO5 CUTP)
                  The transaction contains a currency type field (CUTP) that reports both the currency code and the
                  number of decimal places to be applied to the amount, in the IT05 or Monetary Amounts record.
                  This transaction does not contain a valid code for this BSP.
                  From ISIS5.0 If airline does not accept secondary currency and the secondary currency is reported
                  then the error will also be reported.
503       N       INVALID TAX TYPE
                  All Tax/Miscellaneous Types (TMFT) are reported in the IT05 record and must have a
                  corresponding Tax Amount (TMFA). For this transaction there was one of the following problems:
                  - The tax code (TMFT) is not found in the list of valid tax types.
                  - There is a tax type and amount, but the tax type must only be 2 characters (exception being XF
                       which can be XF or XFLAX3 etc). This transaction has more than 2 characters in TMFT and is
                       not an XF tax.
                  - XF tax types may report more than 2 characters, eg XFLAX3, but may only do so when the
                       corresponding Tax Amount (TMFA) is zero
507       B       NON NUMERIC SUPPLEMENTARY COMMISSION AMOUNT
                  The Supplementary Commission amount field (SPAM in the IT05 record) should be a numeric field.
                  However this transaction has reported non numeric characters.


                                                 Page 11 of 23
ISIS RET Validation Guide
1. Standard errors
Error   Default   Description
Code     ISIS
        Setting
508       B       NON NUMERIC APBC
                  Used in some NR schemes:
                  The APBC field (Amount Paid by Customer) reported in the IT05 record should be numeric, but this
                  transaction contains non numeric characters.
509       B       NRID IS NOT "NR" FOR APBC > 0
                  Applicable in some NR schemes:
                  The APBC field (Amount Paid by Customer) reported in the IT05 record has a value greater than
                  zero, but this transaction does not report NR in the Net Reporting Indicator field (NRID of the IT05
                  record).
510       B       TCIN IS NOT 'Y' FOR APBC > 0
                  Used in some NR schemes and for DISH 10 –10.3 only:
                  When the APBC field (Amount Paid by Customer) reported in the IT05 record, is greater than zero,
                  then the TCIN field (Tax on Commission Indicator in the IT05 record) must be set to „Y‟ .
511       B       APBC NOT > AEBA
                  Used in some NR schemes and for DISH 10-10.3 only:
                  If the APBC field (Amount Paid by Customer) reported in the IT05 record is greater than zero, the
                  AEBA (Amount Entered by Agent in IT05 record) value must not be greater than or equal to the
                  APBC value.
                  Note: For DISH 11 and up refer to Error 520.
513       B       NON NUMERIC CORT
                  The Commission Rate field (CORT) reported in the IT05 record must not contain non numeric
                  characters.
514       B       NON NUMERIC TAX AMOUNT
                  The Tax/Miscellaneous Fee Amount field (TMFA) reported in the IT05 record must not contain non
                  numeric characters.
515       W       "XT" IS INVALID TAX TYPE
                  This transaction contains the tax type of XT and the transaction is Superlong (ie not manually data
                  captured), and is not permitted. The XT value should be separated into the individual tax types and
                  amounts.
516       W       TMFT - SUBSEQUENT "XF" TAX TYPE MISSING
                  When reporting PFC charges as XF taxes, the subsequent Tax Type fields (TMFT/TMFA) after the
                  first one reporting the total values of the XF taxes, should describe the city and amount collected eg
                  XFLAX3. This transaction does not report this detail.
517       W       TMFT - INVALID "XF" AIRPORT CODE
                  When reporting PFC charges as XF taxes, the subsequent Tax Type fields (TMFT) after the first
                  one reporting the total XF taxes, must contain a valid airport code. This transaction has an invalid
                  airport code in a TMFA field in the IT05 record.
518       B       NON-NUMERIC TOCA FOUND
                  For ADMs and ACMs only: The Tax on Commission Amount field (TOCA) reported in the IT05
                  record contains characters that are non numeric.
520       B       IF APBC = 0, IT MUST BE GREATER THAN AEBA + TMFA
                  Used in some NR schemes and for DISH 10 inclusive only:
                  If the APBC field (Amount Paid by Customer) reported in the IT05 record is zero, the AEBA (Amount
                  Entered by Agent in IT05 record which is the agreed net fare) value must not be greater than or
                  equal to the APBC value.
521       W       TMFT MAY NOT BE XT
                  For DISH 11 and up:
                  This transaction contains the tax type of XT in the TMFT field (IT05 record) which is not permitted.
                  The XT value should be separated out into the individual tax type and amounts for both automated
                  and manually captured transactions.
522       W       TCIN APPLIES TO STD'S ONLY
                  For DISH 10 and under:
                  The Tax on Commission Indicator (TCIN in the IT05 record) only applies to issues/refunds and not
                  ADMs and ACMs. This ADM/ACM transaction should report TOCA (Tax on Commission Amount)
                  instead.




                                                  Page 12 of 23
ISIS RET Validation Guide
1. Standard errors
Error   Default   Description
Code     ISIS
        Setting
524       B       ACTUAL COMMISSION < 0 (FPAM – AEBA – TAX)
                  When the BSP is set up to use Actual Commission:
                  This transaction does not have an actual commission value due to the following calculation:
                  The Form of Payment amount (FPAM in IT08 record) less the net remit value in the Amount Entered
                  by Agent (AEBA field) less the taxes (TMFA‟s) shouldn‟t be less than zero. However, it is on this
                  transaction.
525       B       CORT IS GREATER THAN (OR =) 100%”
                  DISH 20 and up:
                  This transaction has reported a Commission rate (CORT in IT05 record) which is greater than or
                  equal to 100 percent.
526       B       COAM IS GREATER THAN FARE
                  This transaction has reported a Commission Amount (COAM in IT05 record) that is greater than the
                  FARE Amount.
527       B       TASF AMOUNT EXCEEDS MAXIMUM AMOUNT
                  Warning Feature: If the BSP has set up Maximum TASF Amount Limit in ISIS, then this transaction
                  is reporting a TDAM value that exceeds the expected value.
                  Set Up SCREEN: OPERATIONS >REF> BSP>BSP Param 6
528       B       TASF AMOUNT EXCEEDS MINIMUM AMOUNT
                  Warning Feature: If the BSP has set up Minumum TASF Amount Limit in ISIS, then this transaction
                  is reporting a TDAM value that is less than the expected value.
                  Set Up SCREEN: OPERATIONS >REF> BSP>BSP Param 6
529       B       TCTP MUST HAVE A VALUE IF TOCA IS REPORTED
                  Introduced in ISIS 5 (retloadv50)
                  For ACMs/ADMs if TOCA is reported TCTP must be non blank else this error is reported.
601       W       MISSING VALUE FOR FBTD
                  This transaction has a Fare Basis field (FBTD reported in the IT06 record) for a valid flight coupon,
                  which is blank in error.
602       W       MISSING VALUE FOR CLSC
                  The Reservation Booking Designator (RBKD in IT06 record which replaced the CLSC) does not
                  report the information entered in the “Flight/Class” box on the ticket for this flight coupon.
603       W       "VALUE" COUPON MISSING IN ITINERY
                  The itinerary data is reported in the IT06 record and reflects the same number of flight coupons that
                  are designated in the Coupon Use Indicator field (CPUI). This transaction has more flight coupons
                  („F‟s in CPUI) than there are itinerary transactions in the IT06 record – so one or more flight
                  coupon‟s information is missing.
604       W       SEGI MUST HAVE VALUE BETWEEN 0 TO 4
                  The Segment Identifier (SEGI reported in IT06 record), which is a number to identify each flight
                  coupon corresponding to the segment in the “Good For Passage” itinerary of the ticket, must be
                  between 0 and 4 in the RET file. This transaction has a SEGI that is not 0-4.
605       W       "NON-VALUE" COUPON FOUND IN ITINERARY
                  The itinerary data is reported in the IT06 record and reflects the flight coupons that are designated
                  in the Coupon Use Indicator (CPUI) eg „F‟ for flight, „V‟ for Void etc. This transaction has an
                  itinerary in the IT06 record which does not correspond to an „F‟ in the Coupon Use indicator field. .
606       W       SEGI VALUE MUST BE IN LOGICAL SEQUENCE
                  The itinerary data is reported in the IT06 record. The Segment Identifier (SEGI reported in IT06
                  record), which is a number to identify each flight coupon corresponding to the segment in the “Good
                  For Passage” itinerary of the ticket, must be in a logical sequence, ie it can not report flight coupon
                  3 before flight coupon 2 etc. This transactions segment identifiers are out of sequence.
701       W       FRCS IS INVALID
                  The Fare Calculation Sequence Number (FRCS) identifies each line of the Fare Calculation Area on
                  an automated ticket and is reported in the IT07 record.
                  This transaction contains a sequence (or line) number that is either not in numerical sequence, OR
                  is greater than 4.




                                                  Page 13 of 23
ISIS RET Validation Guide
1. Standard errors
Error   Default   Description
Code     ISIS
        Setting
702       W       FCMI NOT PROVIDED
                  DISH 20 and upwards: The Fare Calculation Mode Indicator (FCMI), which is reported in the IT07
                  record, and shows the method of pricing as entered on the ticket has been reported as blank on this
                  transaction. Entries should be:
                  0 - System Computer priced
                  1 - Manually Priced
                  2-9 - For individual Airlien/System provider use
                  A-Z - Undefined industry use.
801       B       INVALID CURRENCY TYPE FOR THIS COUNTRY (ITO8 CUTP)
                  The transaction should contain a currency type field (CUTP) that reports both the currency code and
                  the number of decimal places to be applied to the amount in the IT08 record. This transaction has
                  reported either a blank currency type (CUTP), or a currency type different from that reported in the
                  Monetary amounts record (IT05).
                  Note: If the IT08 Currency Type is different from that in the IT05 record, the System will change it to
                  match.
802       B       CREDIT CARD WITH INVALID CHECK DIGIT
                  The Credit Card number, as reported in the FPAM (Form of Payment Account Number) field in the
                  IT08 record, has failed the modulus-10 check digit verification.
                  Note: If Error is set to Billing Critical, the transaction will be rejected to cash.
803       B       CREDIT CARD WITH INVALID LENGTH
                  The Credit card number, as reported in the FPAM (Form of Payment Account Number) field in the
                  IT08 record, does not match the required card length parameter set up in the System.
813       B       FPTP – UNRECOGNISED
                  The Form of Payment Type (FPTP) is reported in the IT08 record and the first two characters
                  denote the type of payment the transaction will be. The accepted values are:
                  CA (Cash), CC (Credit Card), CM (Credit turned to Cash), EX (Exchange), MS (Miscellaneous), RF
                  (Exchange with cash Refund) and TC (Exchange with credit refund).
                  This transaction has reported a payment code that does not match the accepted values above.
814       B       FPTP - FOUND WITH NO FPAM
                  This transaction contains a Credit Card payment type (FPTP in IT08), but does not report a
                  corresponding Payment Amount in the FPAM field of the same record.
815       B       FPAM - EXCHANGE VALUE NOT FOUND TOGETHER WITH PAYMENT AMOUNT
                  If the Form of Payment Type (FPTP) as reported in the IT08 record denotes the ticket is an
                  Exchange, then the Form of Payment Amount (FPAM) field associated with it must be zero.
                  Note: If the ticket has Additional Collect, this is reported in a secondary occasion of the Form of
                  Payment Amount and Type.
819       B       INVALID CC PREFIX
                  Each BSP has preset up accepted Credit Card Prefixes. This transaction has reported an invalid
                  CC prefix in the Form of Payment Type (FPTP) field of the IT08 record.
821       B       INVALID PAYMENT TYPE
                  This transaction has reported VD as a payment type in the Form of Payment Type field (FPTP in
                  IT08 record), which is only valid for Voids and not live transactions.
822       W       APLC – REQUIRED
                  For BSPs where the CC Approval limits have been set up:
                  The Credit card Approval Code (APLC in the IT08 record) field should report a value as the ticket
                  value has exceeded the CC limit as set up in the System.
823       B       MORE THAN ONE CA PAYMENT
                  This transaction has reported more than one CA Form of Payment Type and Amount in error. This
                  includes either CA or MSCA (Miscellaneous Cash) in the IT08 record.
824       B       INVALID CCO_CODE
                  The Credit Card Organisations (eg AX, VI etc) are preset up in the system as accepted by the BSP.
                  This transaction has reported a CCO that does not match this list.
825       B       NON NUMERIC CC PREFIX
                  The Credit card prefix (a four numeric cc code as listed in Reso 728, section 7) is reported in the
                  Form of Payment Type (FPTP) field of the IT08 record. This transaction has reported a credit card
                  prefix that contains a character/s which is not numeric.




                                                  Page 14 of 23
ISIS RET Validation Guide
1. Standard errors
Error   Default   Description
Code     ISIS
        Setting
826       B       FPTP - "MS" MUST BE FOLLOWED BY EITHER "CA" OR "CC"
                  The Form of Payment Type (FPTP) is reported in the IT08 record and the first two characters
                  denote the type of payment the transaction will be. When it is reported as MS (Miscellaneous), then
                  there is a requirement for this to be followed by CA or CC to indicate how it should be billed.
                  This transaction has reported MS, but not the payment type of either CA or CC.
828       B       NON PARTICIPATING AIRLINE OR AUTHORISED AGENT
                  If the BSP is set up for NRCC validation including Airline and Agent participation parameters::
                  This transaction is not a valid NRCC sale due to either:
                  - The Agent is not authorised to issue NRCC for this Airline and CCO
                  - The Airline on this transaction does not accept NRCC sales.
829       W       CREDIT CARD COMPANY CODE IS NOT ACCEPTED BY THIS AIRLINE
                  If BSP set up is „Airline Accepts Specified Credit Card = Y‟:
                  The CCO 2 character vendor code (eg AX) is reported in the Form of Payment Type (FPTP) field of
                  the IT08 record. Based on Airline Acceptance setup – this transaction has a credit card
                  organisation code that is not valid for this Airline.
830       W       CREDIT CARD PREFIX NUMBER IS NOT ACCEPTED BY THIS AIRLINE
                  If BSP set up is „Airline Accepts Specified Credit Card = Y‟:
                  The CC 4 numeric credit card code (eg 3758 for AX) is reported in the Form of Payment Type
                  (FPTP) field of the IT08 record. Based on Airline Acceptance setup - this transaction has a credit
                  card prefix that is not valid for this Airline.
831       B       ALNC IS NOT A STP LOCATION
                  The Approved Location Numeric Code (ALNC), reported in this transaction in the IT02/IT0S record,
                  refers to the approved Agency Location electronically connected to the Agent specified on the ticket,
                  and who received on or more of the coupons. However, the Approved agent code does not have a
                  corresponding satellite agent Code in the Agent Master Table.
832       B       AGTN IS NOT THE PARENT OFFICE OF ALNC
                  The ticketing Agent (AGTN in IT02 record) in this transaction, is not the parent office of the Agency
                  Location nominated in the Agency Location Numeric Code (ALNC) field of the IT02/IT0S record.
833       B       CCO NOT VALID FOR PREFIX
                  The Credit Card Organisation code and Card Numeric Prefix is preset up in the System. This
                  transaction has reported a CC vendor code eg AX that does not match to the CC 4-numeric credit
                  card prefix eg 5440.
900       W       FPIN NOT PROVIDED
                  The Form of Payment Information (FPIN) field provides a facsimile copy of the information printed in
                  the Form of Payment box on the primary ticket. This transaction did not have any information
                  reported for FPIN.
A01       W       MISSING IT0A FOR MPNN OR MD51
                  The IT0A or Miscellaneous Document Information record is required for automated reporting of
                  MD51 or MPnn documents. The record is missing for this transaction.
A02       W       ICDN IS INVALID
                  For DISH 10-11 only:
                  This transaction has reported an invalid „In Connection with Document Number‟ or ICDN field
                  reported in the IT0A record for MPDs. The Airline code part of the ICDN field must be the same as
                  the primary tickets TDNR information (Ticket Document Number field in IT02).
D01       B       AEBA > 0, NOT NET REMIT TICKET
                  NR METHOD 2A: This transaction has reported an Amount Entered By Agent (AEBA in the IT05
                  record). This amount is the agreed settlement amount (exclusive of taxes) between the Agent and
                  the Airline for a net sale. However, the transaction must also be reported as a NR ticket (with NR in
                  the NRID field or IT05) and was not.
D02       B       AEBA > (TDAM - TMFA)
                  NR METHOD 2A: The Amount Entered by Agent (AEBA in IT05 record) field denotes the agreed
                  settlement amount, exclusive of taxes, between the agent and the airline for a net sale. This value
                  must NOT be greater than the Total Document Amount (TDAM) less the total taxes as it is deducted
                  from this figure to provide the supplementary commission.




                                                 Page 15 of 23
ISIS RET Validation Guide
1. Standard errors
Error   Default   Description
Code     ISIS
        Setting
D03       W       ALTP - INVALID VALUE
                  The Approved Location Type field (ALTP in IT02 or IT0S record) reports a code that identifies the
                  type of Location receiving some or all of the STD coupons. This transaction failed one of the
                  following checks:
                  - The first occurrence of ALTP in the IT02 record must be “A” or blank.
                  - If the transaction code (TRNC) = CANX, CANN or VSCN, then the first occurrence may also be
                       “E” .
                  - Subsequent occurrences of ALTP may take values of A, E, O or S.
                  - If the corresponding ALNC field is zeros, then ALTP may be blank.
D04       W       AVCD - SHOULD BE BLANK FOR NON CC
                  The Address Verification Code (AVCD) field reported in the IT08 record should be blank for any non
                  CC transactions. This transaction was not a CC sale, and contained information in this field.
D05       W       CPNR - INVALID VALUE
                  The Coupon Number or CPNR, reported in the IT0D record is reported for MD30 transactions only.
                  This automated MPD contained values that were not between 1 – 4.
D07       W       DIRD - MAY NOT BE LATER THAN DAIS
                  The Date of Issue of the Refunded Document (DIRD) field, reported in the IT03 record, should
                  contain either zeros or a date that is no later than the date reported in the Date of Issue (DAIS in
                  IT02 record). This Refund did not meet this requirement.
D08       W       SAPP - SHOULD BE BLANK FOR NON CC, ELSE F,M,S
                  For DISH 10 only:
                  The Source of Approval Code (SAPP), obtained when the Form of Payment is CC or MSCC for
                  OPTATs only, is reported in the IT08 record. The transaction must report one of the following
                  codes: F, M, S or blank.
                  For DISH 11 and up:
                  If the transaction is CC then the field entries must be one of the following: C, M, S or blank.
D09       W       FRCA - FARE CALCULATION AREA NOT PRESENT FOR CNJ/EX TKT
                  The Fare Calculation Area (FRCA) reported in the IT07 record contains all the data printed in the
                  Fare Construction area of the ticket.
                  This transaction was an Exchange or contained conjunction tickets and did not report the Fare
                  Calculation area data.
D10       W       SCNF - INVALID VALUE
                  The Stock Control Number “From” field (SCNF reported in the IT02/IT0S record) on this transaction
                  contains information, but does not start with „TX‟ which is mandatory.
D11       W       COTP - INVALID COMMISSION TYPE
                  The Commission Type field (COTP reported in the IT05 record) indicates the type of commission
                  applicable to the transaction and is associated with the corresponding commission rate or amount.
                  This transaction reported data that does not match the acceptable codes for this field:
                  - For Non NR sales, the Commission Type field must report: NEW, OLD, XLP or Blank
                  - For Net Sales (NRID = NR), the Commission Type must report: Blank or „G‟ , „N‟, or „G/NEW‟,
                       „G/OLD‟, „G/XLP‟, „N/NEW‟, „N/OLD‟, „N/XLP‟.
D12       B       AEBA - NON-NUMERIC VALUE ENTERED
                  NR METHOD 2A: The Amount Entered by Agent (AEBA in IT05 record) field denotes the agreed
                  settlement amount, exclusive of taxes, between the agent and the airline for a net sale. This
                  transaction has reported non numeric characters in this field in error.
D13       W       AUTA - NON NUMERIC VALUE
                  For DISH 10-10.3 only:
                  The Authorised Amount (AUTA reported in the IT08 record) provides the total amount authorised by
                  one CCO for all transactions approved simultaneously with a single authorisation code.
                  This transaction has reported a non numeric character in the Authorised Amount field in error.

D14       B       AUTO - UNABLE TO DETERMINE AUTO FLAG
                  AUSTRALIA Only: The Auto Flag has not been set up for this transaction.
E01       W       MISSING IT0E RECORD FOR “MD40” DOCUMENT
                  The IT0E record reports the Automated Prepaid Ticket Advice Sponsor information for an
                  automated MPD.. This record is missing for this MD40 transaction.




                                                 Page 16 of 23
ISIS RET Validation Guide
1. Standard errors
Error   Default   Description
Code     ISIS
        Setting
E13       B       CUTP - CURRENCY TYPE
                  The Currency Type (CUTP) field reported in the IT05,IT08 or IT0Yrecords represents the currency
                  code and the number of decimal places associated with the amounts in the transaction.
                  This transaction has reported the number of decimal places component with a non numeric entry.
E15       W       DSTC - DESTINATION AIRPORT/CITY CODE
                  For DISH 10 – 11.1 and where the BSP performs Variable Commission validation, or TOCA
                  Indicator is “C”:
                  The Destination Airport/City Code (DSTC) reported in the IT06 record, is the airport or city code for
                  the point of disembarkation of the flight segment.
                  This transaction has reported a destination code that is not matched in the system‟s Airport Table.
E18       W       EXDA - EXPIRY DATE
                  The Expiry Date (EXDA) reported in the IT08 record for CC transactions, should be reported as
                  MMYY.
                  This transaction has reported an invalid date format OR the Date of Issue (DAIS) on the ticket falls
                  after the Expiry date.
                  Note: If Error is set to Billing Critical, the transaction will be rejected to cash.
E20       W       FARE – FARE
                  The FARE field (IT04) reports the information printed in the FARE box of the ticket. Excluding the
                  entries BT and IT, the first three characters should be a valid currency code.
                  This transaction has reported an invalid currency code in the FARE field.
E25       W       FORM - FORMAT IDENTIFIER
                  The FORM field (Format Identifier in the IT02 record) indicates the lowest record level provided for
                  the transaction. This field should report either X for Superlong, L for Long data, S for Short record
                  data or Blank (for Refs, ADCM‟s and Manual MCO‟s) Only certain codes are acceptable for each
                  transaction type as described in the DISH.
                  This transaction has reported an incorrect format code (FORM) for the type of transaction reported
                  in the TRNC field.
E38       W       INLS - INTERNATIONAL SALE INDICATOR
                  The International Sale Indicator (INLS reported in the IT04 record) reports the SITI, SITO etc codes.
                  This transaction has reported an incorrect code in this field. Codes must be one of the following:
                  SITI, SITO, SOTI, SOTO, or blank (for domestic transport).
E42       W       NRID - NET REMIT INDICATOR
                  This transaction has reported the Net Remit Indicator field (NRID in IT05 record) with data that is
                  not either „NR‟ or a blank.
E43       W       NTSI - NEUTRAL TICKETING SYSTEM IDENTIFIER
                  This transaction has reported a Neutral Ticketing System Identifier code (NTSI in the IT04 record)
                  which is not in the NTSI Master Table. These codes indicate which Ticketing System has controlled
                  the issuance of the transaction.
E45       W       ORAC - ORIGINAL AIRPORT/CITY CODE
                  For DISH 10-11 and when TOCA Indicator is “C” :
                  For BSP‟s completing Variable Commission Validation (see Separate Section on V Errors)
                  This transaction has reported an invalid Origin Airport/City code (ORAC in IT06 record), as it does
                  not match to any entries in the Airport Table.
E47       W       OTDN - ORIGINAL ISSUE TICKET/DOCUMENT NUMBER
                  For DISH 10-10.3 only:
                  This transaction has reported an invalid airline code in the Original Issue Ticket/Document Number
                  (OTDN) when compared to the Airline Master Table.
E50       W       PXNM - PASSENGER NAME
                  For DISH 20 and above:
                  This transaction has reported a blank passenger name (PXNM in the IT02 record) for a superlong
                  transaction (FORM = X). Superlong data should report every field in the ticket.
E52       B       RCID - RECORD IDENTIFIER
                  This Transaction has reported an invalid entry for the Record Identifier field (RCID which is reported
                  in every record).
                  Each transaction record has a corresponding Identifier, eg the IT02 record for Basic Sale
                  information would report “2” as the ID. Codes accepted are: 1-9, A – E, S, Y, or Z




                                                  Page 17 of 23
ISIS RET Validation Guide
1. Standard errors
Error   Default   Description
Code     ISIS
        Setting
E53       W       RCPN - INVALID RELATED TICKET/DOCUMENT COUPON NUMBER IDENTIFIER
                  For Refunds, ADM and ACM‟s only:
                  This transaction has reported an invalid Related Ticket Document Coupon Number. The values
                  must be from 0 to 4 and occupy it‟s relative position (eg 0204 for coupons 2 and 4) Zeros are in
                  positions when the related RTDN does not have coupons.
E60       W       SASI - SERVICING AIRLINE/SYSTEM PROVIDER IDENTIFIER
                  This transaction has reported an invalid Servicing Airline/System Provider Identification code that
                  does not satisfy the modulus-7 check digit validation. The code must be three numeric plus a check
                  digit.
E68       W       STPO - STOPOVER CODE
                  This transaction has reported an invalid stopover code (STOP in the IT06 record). Codes may only
                  be X or O or blank.
E71       W       TCIN - TAX ON COMMISSION INDICATOR
                  For DISH 10-11only:
                  The Tax on Commission indicator in this transaction should only report either Y or blank.
E73       W       TCNR - TRANSMISSION CONTROL NUMBER
                  This transaction has reported a Transmission Control Number (TCNR in the IT02 record) which
                  does not match the SASI field (Servicing Airline /System Provider Identifier code) in the first four
                  characters.
E74       B       NO AMOUNT KEYED IN TDAM/FPAM/COAM - DELETE DOCUMENT
                  AUSTRALIA ONLY:
                  For ADM, ACM or Refunds, the Ticket Document Amount (TDAM in IT05) and Commission Amount
                  (COAM) must not be zero.
E76       W       TKMI - TICKETING CODE INDICATOR
                  The Ticketing Code Indicator (TKMI in the IT04 record) reported for this transaction does not
                  contain the mandatory entries, ie must be either „/‟ or „X‟ or „A‟. These codes indicate the method of
                  ticketing eg Airline or System provider system, Agent system etc.
E85       B       ALPHA CHARACTER IN NUMERIC FIELD
                  DISH 10-11 and ARC use only:
                  The Exchanged Ticket Total Sale Amount reported in this transaction contains a non numeric entry.
Rxx               (see Section 2 / Refund errors)
Vxx               (see Section 3 / Variable commission errors)
W21       W       FBAL - FREE BAGGAGE ALLOWANCE
                  For DISH 10-10.3 only:
                  This transaction has reported an incorrect format or entry in the Free Baggage Allowance field
                  (FBAL in IT06 record). It should report either „PC‟, „K‟ or „L‟ preceded by 2 numerics indicating the
                  weight. Also permitted are: „NIL‟, „NO‟, „XX‟ or blank.
W22       W       FBST - INVALID FLIGHT BOOKING STATUS
                  The Flight Booking Status (FBST in the IT06 record) has been reported incorrectly for this
                  transaction. The field should contain either: „OK‟, „NS‟, „RQ‟, „SA‟ or blanks.
W34       W       FTDA - FLIGHT DATE
                  For DISH 10-11 only:
                  The Flight Date (FTDA in IT06 record) has been reported incorrectly. This transaction has reported
                  either an incorrect date OR the field contained data when the flight number is OPEN.
W35       W       FTDT - FLIGHT DEPARTURE TIME
                  For DISH 10-11 only:
                  The Flight Departure Time (FTDT reported in the IT06 record) for this transaction has failed the
                  format check. The field should contain 4 numerics (range = 0000 to 2400), followed by „A‟, „P‟ or
                  „12‟, followed by „M‟ or „N‟. This field should also be blank if the FTNR (Flight Number) is OPEN. .
W40       W       NADA - 'NOT VALID AFTER' DATE
                  For DISH 10-11 only:
                  The last date on which travel is permitted is reported in the NADA or „Not Valid After‟ Date field in
                  the IT06 record. This transaction has reported either an incorrect date OR the field contained data
                  when the flight number is OPEN.
W41       W       NBDA - 'NOT VALID BEFORE' DATE
                  For DISH 10-11 only:
                  The first date on which travel is permitted is reported in the NBDA or „Not Valid Before‟ Date field in
                  the IT06 record. This transaction has reported either an incorrect date OR the field contained data
                  when the flight number is OPEN.

                                                  Page 18 of 23
ISIS RET Validation Guide
1. Standard errors
Error   Default   Description
Code     ISIS
        Setting
W92       W       EXCHANGE COUPONS
                  Exchange Tkts: The Form of Payment Account Number details (FPAC in IT08 record) for this
                  transaction are reporting the Exchanged ticket coupons incorrectly. The format requires each
                  coupon number to occupy it‟s relative position, with any unused coupons being blank, eg “bb34” is
                  reporting only coupons 3 and 4. Four Blanks is invalid.
W95       W       AGENT BILL AREA NOT SET UP
                  For those BSPs who have Area Billing parameters set up: (OPS/REF/BSP/Parameter 3)
                  This Agent does not have any area set up in the Agent Bill Area field in the Agent Master Tables.
Y01       B       NON-NUMERIC SFAM FOUND
                  The Signed For Amount (SFAM in the IT0Y record) has been reported on this transaction with a non
                  numeric entry.




                                                Page 19 of 23
ISIS RET Validation Guide

2. Refund errors:
Some of these validations are standard(*) and will have descriptions if validation differs, but others are optional
depending if airline tables are involved, as follows:
a) An Airline table is set up with the acceptance (or non acceptance) or refund payment types, ie CA, CC, Partial
    CA, Partial CC and Mixed FOP. Authorities may be for All agents and/or specific agents.
b) During loading all Agent refunds are checked against the Airline Refund Acceptance table, and also against the
    Original ticket, nominated in the Refund, for accuracy.
c) Refunds that fail the validation based on the above set up, are automatically deleted. The system copies the
    Refund details and the reason for rejection to a report: RPAIRFRJ for Airlines and RPAGRFRJ for Agents.
Set up Parameters are in BSP Param4 screen and also denote the numeric prefix used by Agents for the Refunds.

2. Refund errors – standard(*) + optional
Error   Default   Description
Code     ISIS
        Setting
R01       W       TOTAL CASH REFUNDS NOT ALLOWED
                  This Airline (as reported in TACN of the IT02 record) does not accept full Cash refunds.
R02       W       PARTIAL CASH REFUNDS NOT ALLOWED
                  This Airline (as reported in TACN of the IT02 record) does not accept partial Cash refunds.
R03       W       TOTAL CREDIT REFUNDS NOT ALLOWED
                  This Airline (as reported in TACN of the IT02 record) does not accept full Credit refunds.
R04       W       PARTIAL CREDIT REFUNDS NOT ALLOWED
                  This Airline (as reported in TACN of the IT02 record) does not accept partial credit refunds.
R05       W       NOT ALLOWED THIS FORM OF PAYMENT
                  This Airline (as reported in TACN of the IT02 record) does not accept mixed payment refunds (CA
                  and CC).
R06       W       AGENT REFUND AUTHORITY NOT ASSIGNED BY THE AIRLINE
                  This Airline does not have a Refund Authority Acceptance table entry for this Agent so no refunds
                  are allowed.
R07       W       ORIGINAL TICKET NOT FOUND (AGENT SUBMITTED)
*                 This Refund is for a ticket (as reported in the RTDN field of IT03 record) that is not in the Processing
                  System‟s ticket history database
R08       W       AGENTS DO NOT MATCH (AGENT SUBMITTED)
*                 This Agent has reported a refund for a ticket that was issued by another Agent Code. ( The AGTN
                  code is different from the original ticket AGTN code).
R09       W       AIRLINES DO NOT MATCH (AGENT SUBMITTED)
*                 This Agent has reported a refund with the Airline Code (TACN in IT02 record) that is not the same
                  as the Airline code on the original ticket.
R10       W       COMISSION RATES DIFFER
                  The Commission rate (CORT in the IT05 record) is not the same as the commission rate of the
                  original ticket.
R11       W       FORM OF PAYMENT TYPE DIFFER
*                 The Form of Payment reported on this Refund (FPTP in IT08 record) is different from the payment
                  type on the original ticket. Eg original is cash, refund is for credit card.

                  Standard Validation: As above but also ignore matching cash payments if created pseudo cash on
                  original not on a credit refund. (i.e. CA payment created to balance FPAM and TDAM)
                  (e.g. Original CC + Pseudo CA, Refund CC, won‟t be an error as CA on original is pseudo.)
                  As pseudo cash can‟t be determined on archived data, assume if archived and NR that the CA
                  payment is psuedo.
R12       W       MANUAL REFUND OF NET REMIT TICKET (AGENT SUBMITTED)
                  A manual refund (keyed by the DPC), may not be submitted for net remit tickets.
R13       W       MANUAL REFUND OF ET TICKET (AGENT SUBMITTED)
                  A manual refund (keyed by the DPC) may not be submitted for ET sales as the Airline system must
                  review and provide the Settlement Authority Code (ESAC).
R14       W       AUTO REFUND FOR MANUAL TICKET (AGENT SUBMITTED)
                  An automated refund (generated by a CRS system) may not be submitted for a manual ticket.
R15       W       REFUND OF A REJECTED NET TICKET
                  A refund may not be presented for a rejected net remit sale. The Agent should submit this refund
                  directly to the Airline.



                                                  Page 20 of 23
ISIS RET Validation Guide
2. Refund errors – standard(*) + optional
Error   Default   Description
Code     ISIS
        Setting
R16       W       ESAC NOT PRESENT (AGENT SUBMITTED)
                  This ET refund does not have an Settlement Authority Code (ESAC in the IT02 record) generated
                  by the Airline system indicating approval.
R17       W       REFUND OF EXCHANGE TICKET (AGENT SUBMITTED)
*                 The original ticket this Refund is based on (excluding multiple exchange MCO transactions), as
                  reported in the RTDN, was an Exchange document. The Agent should submit this refund directly to
                  the Airline.

                  Standard Validation: As above but check also includes coupon. (i.e. RTDN+COUPON)
R18       W       PAYMENT AMOUNTS DIFFER
                  For Full Mixed FOP Refunds only: The mixed payment amounts on this refund, as reported in the
                  FPAM of the IT08 record, are different from the mixed payment amounts of the original ticket.
R19       W       ORIGINAL TICKET CC REJECTED TO CASH (AGENT SUBMITTED)
                  This refund is reporting an original ticket (RTDN) that was a credit sale rejected to cash due to CC
                  detail errors. The Agent should submit this refund directly to the Airline.
R20       W       DEAL NOT FOUND
                  NR Refunds: The Net Deal for this refund is not present in the System. The Agent should submit
                  this refund directly to the Airline.
R21       W       REFUND AFTER DEAL SALES LIMIT (AGENT SUBMITTED)
                  NR Refunds only: This net remit refund is for a ticket whose deal has expired. The Agent should
                  submit this refund directly to the Airline.
R22       W       DEAL DOES NOT ALLOW REFUNDS
                  NR Refunds only: This Deal does not permit Refunds. The Agent should submit this refund directly
                  to the Airline.
R23       W       ACM OR ADM FOUND WITH MULTIPLE RELATED TICKETS
                  This refund‟s original ticket has a related ADM or ACM which refers to more than the original ticket
                  under investigation. Due to this issue, the total value of the original ticket and its related documents
                  can not be established. The Agent should submit this refund directly to the Airline.
R24       W       TOTAL DOCUMENT AMOUNTS DIFFER (TDAM)                         (Pre ISIS5.0)
*                 SUM OF REFUND COUPONS GREATER THAN ORIGINAL                          (ISIS5.0)
                  This Refund has been reported with a Ticket Document Amount (TDAM in IT05 record) which is
                  greater than the Original ticket plus it‟s related tickets TDAM eg the original ticket plus an exchange,
                  ADM or ACM or another partial refund.

                  Standard Validation: Checks that the refund‟s TDAM – TAX + (TDAM-TAX of other refunds
                  refunding the same ticket) does not exceed the TDAM – TAX of the related ticket.
R25       W       PARTIAL REFUND OF A NET REMIT TICKET
                  A partial refund may not be submitted for a net remit ticket. The Agent should submit this refund
                  directly to the Airline.
R26       W       RATIO OF CASH/CREDIT NOT MAINTAINED ON PARTIAL REFUND
                  If the original ticket is a mixed form of payment, then check that the values on the Refund are
                  proportionally reduced, ie by the same percentage. If not then reject refund.
R27       W       CANCEL PENALTY EXISTS ON A MIXED FOP REFUND
                  This refund is a mixed form of payment refund, and also contains a cancellation penalty (CP), so will
                  not be processed as it needs airline checking. The Agent should submit this refund directly to the
                  Airline.
R28       W       ANOTHER REFUND FOUND
*                 The Related Ticket Document Number (RTDN in the IT03 record) reported in this refund has been
                  refunded before.

                  Standard Validation: As above but check also includes coupon. (i.e. RTDN+COUPON)
R29       W       AN EXCHANGE TICKET WAS FOUND RELATED TO THE ORIGINAL
                  This original ticket from this Refund as reported in the RTDN of the IT03 record, has an exchange
                  ticket as one of its related documents and will therefore require Airline review. The Agent should
                  submit this refund directly to the Airline.
R30       W       NO RELATED DOCUMENT WAS REPORT ON REFUND NOTICE
                  This refund did not report a Related Ticket Document Number or RTDN in the IT03 record.
R31       W       CREDIT SALE NOT YET INVOICED
                  The original ticket being refunded is a credit card sale, but has not been invoiced yet.

                                                  Page 21 of 23
ISIS RET Validation Guide
2. Refund errors – standard(*) + optional
Error   Default   Description
Code     ISIS
        Setting
R32       W       CP HIGHER THAN REFUND VALUE
                  The Cancellation penalty reported in this refund has a value that is higher than the Refund value.
R33       W       CC TICKET 90 DAYS OLD ( AGENT SUBMITTED )
                  This refund is for a credit card sale that was invoiced more than 90 days (3 months) ago.
R34       W       ORIGINAL DOCUMENT IS NOT A TICKET SALE, EG AN ADM OR ACM *
                  The Refund‟s original document as reported in the RTDN field of the IT03 record is not a recognized
                  ticket number.
R35       W       CC NUMBER IS NOT THE SAME AS THAT OF THE ORIGINAL SALE *
                  The Credit card Refund has reported a Card number (FPAM field of the IT08 record) that is not the
                  same as the Card number in the original ticket.
R36       W       TAXES DIFFER
                  For FULL refunds only: The Refund‟s tax values, as reported in the TMFA and TMFT fields of the
                  IT05 record, are different from the taxes reported in the original ticket.
R37       W       NO ADMS/ACMS ALLOWED AS TICKET HAS BEEN REFUNDED
                  For Airline submitted ADMs and ACMs: This transaction is rejected as the Agent has submitted a
                  Refund for the same original ticket in this processing period which may impact on the ADM or ACM
                  value.
R38       W       CREDIT CARD DETAILS DIFFER
                  This refund has reported credit card details that are different from the original ticket card details.
R39       W       AGENT REFUND REJECTED DUE TO CREDIT CARD ERRORS
                  This CC refund has reported an expiry date that is invalid.
R40       W       AIRLINE REFUND REJECTED DUE TO CREDIT CARD ERRORS
                  This Airline submitted Refund has reported an invalid expiry date.
R41       W       COUPON NUMBER NOT ISSUED FOR TRAVEL
*                 Standard Validation: This refund has reported Related ticket Document Coupon Numbers (RTDN in
                  IT03 record) which do not refer to a valid coupon issued for travel, ie no void or surface.




                                                  Page 22 of 23
ISIS RET Validation Guide

3. Variable commission errors:
These optional validations will check the commission rates on the ticket issues against a Variable Commission matrix
which may be set up for each Carrier, and which provides:
a) Commission rates for each document type, eg ET, OPTATs, Manuals
b) Commission rates to be applied to specific preset up Country routings, eg domestic, Europe to USA, etc.
c) Commission rates that may be applied to specific agents or groups as different from All agents.
d) All values include commission rates, and or a CAP, with optional break points plus CH and IN prorated amounts.

3. Variable commission errors – optional
Error   Default   Description
Code     ISIS
        Setting
V01       W       SC CONVERTED TO CORRECT %
                  This transaction‟s standard commission rate (CORT reported in the IT05 record) has been
                  converted to the commission rate or dollar value required for this routing as set by the Airline.
V02       W       SC CONVERTED TO CORRECT % AND CAP VALUE
                  This transaction‟s standard commission rate (CORT reported in the IT05 record) has been
                  converted to the commission rate required for this routing and maximum dollar value as set by the
                  Airline
V03       W       SC CONVERTED TO CORRECT % AND PENALTY
                  . This transaction‟s standard commission rate (CORT reported in the IT05 record) has been
                  converted to the commission rate/$ value as set by the Airline, including a penalty fee adjustment.
V04      N/A      DEAL_CODE, COMM RATE NOT VALIDATED
                  As this transaction is a valid NR sale, the Commission rate has NOT been validated.
V05      N/A      NET-REJ: DEAL_CODE, COMM RATE CHANGED
                  As this transaction is a rejected Net remit sale, the commission rate (CORT in IT05 record) has
                  been adjusted to revised value according to the Airline Commission table.




                                                 Page 23 of 23

				
DOCUMENT INFO
Shared By:
Categories:
Tags:
Stats:
views:1
posted:1/24/2012
language:English
pages:23
Description: Auto Sales Validation document sample