Transcription
Documentation l.1.04.14Last changed by:Reviewed and approved by:BSPlink SupportBSPlink Production TeamReference: 00001109Date:Page: 1 of 2023/05/2013BSPlink Refund ApplicationsMassive download & upload1.04.14
Documentation l.1.04.14Last changed by:Reviewed and approved by:BSPlink SupportBSPlink Production TeamReference: 00001109Date:Page: 2 of 2023/05/2013INDEX1 Global Overview32 Daily Refund Application Download File53 Refund Application Action File63.1Upload Refund Application Action File63.2Basic Configuration Table for Refund Application Action File83.3Technical Aspects to take into consideration94 Refund Application Evaluation File115 Revision Control Chart15
Documentation l.1.04.14Last changed by:Reviewed and approved by:BSPlink SupportBSPlink Production TeamReference: 00001109Date:Page: 3 of 2023/05/20131 Global overviewThe aim of this interface is to provide BSPlink with a different way to massively update RefundApplications and massively download Refund Applications issued the day before. Theparticipants (enhanced Airlines only) may upload a file containing Refund Applications thatalready exist in BSPlink to update their status, in this way avoiding to fill out the current webforms for every Refund Application. In the same way, participants can download a file containingRefund Applications that have been issued the day before avoiding then to run a manual query.The Refund Applications received through file will fall under the same process as if they weremanually updated through the BSPlink Web-based application. Refund Notices should still haveto be sent to BSPlink in RET file format. Please, take into account that in this manual, we aredealing with DISH RET file format.There are two ways to load files, depending on the file descriptor used in the file name: Via BSPlink Web-based application, through Upload Refund Application Approval Fileoption, whenever the file descriptor is “e9”.Via SFTP, whenever the users have already created an SFTP account via the SecureFTP Account option, within the Sub-Users Management module, in BSPlink Web-based1application. The “e9” files can be sent via SFTP.Once an “e9” file gets loaded, BSPlink will proceed to process it. When it is done, BSPlink willsend a file with descriptor “e8” reporting whether all transactions have been processedsuccessfully or not. Please note that the “e9” files are processed in the following order: datesequence-issuer.The name of the error file is as follows:XXe8AAAA YYYYMMDD sequenceoAAAA: IATA Airline Code Check DigitThere are two different kinds of errors: 1Syntactic: Those related to the format of the file, length of the records and fields, andtype of fields (alphanumeric, numeric or alphabetic fields). The way to inform about theseerrors, when the file is sent either via BSPlink Web-based application or via SFTP, is bymeans of a response file denoted with the e8 file identifier, which will be generatedindicating the user the syntactic errors that have been found.BSPlink secure FTP accounts expire after 3 months of inactivity.
Documentation l.1.04.14Last changed by:Reviewed and approved by:BSPlink SupportBSPlink Production TeamReference: 00001109Date:Page: 4 of 2023/05/2013Likewise, if the file name is the same as that of another file already processed or the usersending the file is not the same as that in the file name; the system will inform the userabout it, by means of a message within an e8 file. Semantic: Those related to the content of the file.For further information on the content of the error file, please refer to section 4 – RefundApplication Evaluation File section.For both kinds of errors, syntactic and semantic, Airlines will receive a file with same filedescriptor. Airlines can retrieve their e8 files in four different ways: Via the Download Files option, where they will appear together with all the other files theAirline received.Mass Download Secure FTP account (for enhanced airlines).Through a SFTP client (for enhanced airlines), whenever they have activated arespective Download Secure FTP Account (only available for the main BSPlink user).Mass Loaded Files Download option.
Documentation l.1.04.14Last changed by:Reviewed and approved by:BSPlink SupportBSPlink Production TeamReference: 00001109Date:Page: 5 of 2023/05/20132 Daily Refund Application Download FileIf the airline wants to receive on a daily basis the results of querying pending Refund Applicationsissued the day before (i.e. only new ones) and their corresponding attachments, there is aparameter to set up this option in BSPlink web application for Airlines within Basic Configuration –Basic Parameters module: Receive Daily Refund Application File? To define whether the airline wants to receivea file that includes the results of pending Refund Application query on a daily basis. Bydefault, it will have the No value.Note that the attachments within the file will be included in folders named after the RefundApplication number they belong to. (See test file Vve69995 20110519.zip attached to thismanual).This downloadable file will have the following file naming convention:Xxe6AAAA YYYYMMDD.zipWhere,ooooXX: ISO Country Codee6: File DescriptorAAAA: IATA Airline Code Check DigitYYYYMMDD: Application DateThe file will contain file Xxe6AAAA YYYYMMDD with the following fields delimited by “pipes” ( ):ElementNumber1234Data Field NameData DescriptionFormatCountry CodeRefund Application NumberISO Country CodeBSPlink Refund Application Number,including check digitNumber of ticket being refundedShows refunded coupon number(s) ofthe refunded ticketIATA Code of Agent issuing RefundApplication (including check digit)Date of Refund ApplicationCurrency Code of Refunded TicketForm of Payment Type (e.g. CASH,CREDIT)Refunded Fare (exclusive of taxes)2ANNNNNNNNNNN10N4N5Refunded Ticket NumberRefund Ticket CouponNumber IdentifierAgent IATA Code678Refund Application DateCurrency CodeForm of Payment9Refunded Fare Amount8NDD/MM/YYYY3ADecimal point
Documentation l.1.04.14Last changed by:Reviewed and approved by:BSPlink SupportBSPlink Production TeamReference: 00001109Date:Page: 6 of 2023/05/2013separator1011Passenger NameET Indicator121314Agent CommentFirst Conjunction TicketFirst Conjunction TicketCoupon Number IdentifierName of PassengerTo indicate whether Refunded Ticketwas an E-Ticket (values Y or blank)Free format text for AgentShows the first conjunction ticketShows refunded coupon number(s) offirst Conjunction Ticket1516Second Conjunction TicketSecond Conjunction TicketCoupon Number IdentifierShows the second conjunction ticketShows refunded coupon number(s) ofthe second Conjunction Ticket10N4N1718Third Conjunction TicketThird Conjunction TicketCoupon Number IdentifierShows the third conjunction ticketShows refunded coupon number(s) ofthe third Conjunction Ticket10N4N1920Fourth Conjunction TicketFourth Conjunction TicketCoupon Number IdentifierShows the fourth conjunction ticketShows refunded coupon number(s) ofthe fourth Conjunction Ticket10N4N2122Fifth Conjunction TicketFifth Conjunction TicketCoupon Number IdentifierShows the fifth conjunction ticketShows refunded coupon number(s) ofthe fifth Conjunction Ticket10N4N2324Airline CodeIndicator for AttachmentsShows the airline code of the ticketsShows if there are attachments25E-Mail address provided inthe Refund ApplicationShows the agent email entered in theRefund Application form3N1AN (Y orblank)Up to 200AN26Tax codes and Amounts ofall Taxes27Waiver CodeAll Refund Application taxes includingCP and MF separated by blankspacesA code given by the validating carrierto be entered by the refunding agent.For example, a code that uthorizedthe waiver of cancellation penalty.Up to 450AN10N4NUp to 500AN14ANAirlines can retrieve their e6 files in 4 different ways: Via the Download Files option, where they will appear together with all the other files theAirline received.Mass Download Secure FTP account (for enhanced airlines).Through a Secure FTP client (for enhanced airlines), whenever they have activated arespective Download Secure FTP Account (only available for the main BSPlink user).
Documentation l.1.04.14Last changed by:Reviewed and approved by:BSPlink SupportBSPlink Production TeamReference: 00001109Date:Page: 7 of 2023/05/2013 Mass Loaded Files Download option.3 Refund Application Action File3.1 Upload Refund Application Action FilePlease, refer to DISH versions equal to or greater than 20.0, in order to correctly generate theRFND file to be loaded into BSPlink. (DISH 20, DISH 20.1, and DISH 20.3 Chapter 5 – AgentReporting Data).Enhanced Airlines users may upload, via BSPlink, as much files as they want, via the ‘UploadRefund Application Approval File’ option.The refund applications included in a file sent by an airline should have been previously issued inBSPlink by agent users.Below there is a brief explanation about each additional control that is carried out and conditionsthat should be fulfilled for the correct loading of the file:1. These files will be loaded into BSPlink via the ‘Upload Refund Application Approval File’option.2. There are three conditions that are checked in BSPlink web-based application, before the fileis finally posted to BSPlink Centre:
Documentation l.1.04.14Last changed by:Reviewed and approved by:BSPlink SupportBSPlink Production TeamReference: 00001109Date:Page: 8 of 2023/05/2013 The file name should observe the following file naming convention:Xxe9EARS YYYYMMDD AAAC sequenceWhere,AAAC should contain the IATA airline code plus the check digit. The user loading the file should be the same as that in the file name. The RPSI should always be MASS, thus indicating that the loaded file is a massivelyuploaded RET file. Note that when BSPlink Center generates the respective RET withuthorized refund applications to be sent to the corresponding DPC, the reportingsystem will be EARS, i.e. the same as the rest of documents issued via BSPlink.3. One of the first controls that the BSPlink Centre carries out on this kind of files is related toREVN field in IT01. DISH versions that are supported by the system are equal to or greaterthan 20.04. All the transactions included in the file must have TRNC field in IT02 set to RFND.5. The system will check that all the refunds in the file had been previously issued throughBSPlink.6.Note that the FPTP field is compared with the credit card types free of Luhn check validationpreviously selected by the BSP, and whenever there’s a match, the credit card will beexempted from check digit validation.3.2 Basic Configuration Table for Refund Application Action FileThere are a few options in BSPlink web application for Airlines and BSP that configure certainparameters related to Indirect Refunds and that affect this functionality:Airline: Within Basic Configuration – Basic Parameters – Refund Settings option:
Documentation l.1.04.14Last changed by:Reviewed and approved by:BSPlink SupportBSPlink Production TeamReference: 00001109Date:Page: 9 of 2023/05/2013 Are all agents allowed to issue online Refund Notices via BSPlink?: To allowall agents registered in the system to issue RN via BSPlink. By default is setto No, which means that the airline will have to decide individually whichagents are able to issue Refund Notice for such airline via BSPlink throughthe Document Settings option, within the Basic Configuration module in theairline main menu. If set to Yes, all agents will be able to issue RN viaBSPlink.Are all agents allowed to issue online Refund Applications via BSPlink? Toallow all agents registered in the system to issue RA via BSPlink. By defaultis set to No, which means that the airline will have to decide individuallywhich agents are able to issue RA for such airline via BSPlink through theDocument Settings option, within the Basic Configuration module in theairline main menu. If set to Yes, all agents will be able to issue RA viaBSPlink.Are E-Ticket Refund issues permitted? To define whether to refund E-ticketsis allowed.o Yes: Default value. No validation for E-tickets will be carried outwhen issuing refunds. For RN issues a message will be displayedinforming the user that the refunded document is defined as E-ticket.o No: The refunded document number will be validated against thedocument series and types defined in BSPlink in order to assure thatit is not an E-ticket. RN Issue: If the refunded ticket number is defined as Eticket, the issue is not saved. The user will, then, have theoption to issue a Refund Application instead. Note that theagent may have restrictions to issue indirect refunds. In suchcase, the document cannot be refunded via BSPlink. RA Issue: If the refunded ticket number is defined as Eticket, the issue will only be saved if the ET check box isselected.Are CCNR Refunds allowed?: This parameter indicates whether the airlineallows the issuance of credit refunds of NR tickets.Receive Daily Refund Application File?: To define whether the airline wantsto receive a file that includes the results of Refund Application query on dailybasis. By default, it will have the No value.Handling fee on Refunds (only when allowed by BSP): Define whether MFtaxes are allowed on refunds or not. This parameter affects Refund Notice,Refund Application/Authority issue and ADM/ACM issue concerning refunds.Penalty charge on refunds (only when allowed by BSP): Define whether CPtaxes are allowed on refunds or not. This parameter affects Refund Notice,Refund Application/Authority issue and ADM/ACM issue concerning refunds.Commission on CP and MF (only when allowed by BSP): To activate the fieldCommission on CP and MF in Refund Application / Authorisation. Note thatthis parameter applies only if CP in Refunds are allowed, i.e. if the Penaltycharge on refunds is set to Yes.
Documentation l.1.04.14Last changed by:Reviewed and approved by:BSPlink SupportBSPlink Production TeamReference: 00001109Date:Page: 10 of23/05/201320BSP: Within Basic Configuration – BRW REFUNDS option: CC allowed on Refund Application/Authority: Decide whether indirect creditcard refunds are allowed in such BSP or not.o If Yes: value by default, indicating that credit refunds are allowed.o If No: Only cash refunds are allowed. Mixed Taxes in Refunds: Decide if the refund application issued via BSPlinkcan have mixed taxes, that is, if taxes can be paid by cash and credit at thesame time.NR Refunds permitted?: Allows the airline to decide whether to permit Rason credit NR documents. If set to Yes, the Net Remit field will be displayed inthe Refund Application forms. Fare Adjustment Amount: To indicate whether Fare Adjustment Amount ispermitted in the Refund Application form. It can only be activated if the “NRRefunds Permitted” parameter is set to YES, and “Include SPAM onCommission” set to NO; by default is set to NO. TCTP for VAT on CP: To define the TCTP (Tax on Commission type) forVAT on CP, if applicable. As per DISH, the TCTP (Tax On CommissionType) can be filled with 6 alphanumeric characters. TCTP for VAT on MF: To define the TCTP (Tax on Commission type) forVAT on MF, if applicable. As per DISH, the TCTP (Tax On CommissionType) can be filled with 6 alphanumeric characters. VAT on MF/VAT on CP: To activate VAT on MF and CP fields in RefundApplication. Only applicable in case that MF or CP taxes are allowed inrefund issues. i.e. if the Handling fee on Refunds and Penalty Charge inRefunds parameters are set to Yes. Issue Refunds without coupons: Define if the refunds can be issued withoutcoupons.ooNo: value by default, indicating that refunds should be issuedindicating the refunded coupons.Yes: BSP will allow users to issue refunds via BSPlink withoutcoupons, if so desired.
Documentation l.1.04.14Last changed by:Reviewed and approved by:BSPlink SupportBSPlink Production TeamReference: 00001109Date:Page: 11 of23/05/2013203.3 Technical Aspects to take into consideration:3.3.1Changes into Refund Application when it is authorized:Airlines may make changes into Refund Applications through mass-upload file ifnecessary. Fields that can be modified are: IT02.ESAC IT03.WAVR IT03.RCPN IT03.RTDN IT03.DIRD IT05.TDAM IT05.CORT IT05.COAM IT05. COTP IT05.TMFT IT05.TMFA IT08.FPAM IT08.FPTC IT08.FPAC IT08.CSTF (Only if there is a FPTP CC)3.3.2No-DISH compliant field “IT02.RFAS”:The purpose of this field, located into IT02 line, position 255, is to change RefundApplication status. The admitted values are: A Authorized U Under Investigation R Rejected3.3.3IT02.STAT, IT02.TRNC, IT02.PXNMletters:and IT05.TMFTs in uppercaseThe fields STAT, TRNC, PXNM and TMFTs only accept uppercase letters.3.3.4The value in IT02.PXNM depends on IT01.REVN:When IT01.REVN 200, the PXNM may not be blank, for REVN greaterthan 200, it could be blank.
Documentation l.1.04.14Last changed by:Reviewed and approved by:BSPlink SupportBSPlink Production TeamReference: 00001109Date:Page: 12 of23/05/2013203.3.5 RTDN modification when authorizing Ras:Airlines can modify the IT02.ESAC and IT03.RTDN fields and its CNJs thru massupload (e9). The RTDN field will correspond to that of the first occurrence in theIT03 field, and then the rest to that of the CNJs. RTDN and its CNJs are to beconsecutives in positioning and numbering; up to 6 documents (RTDN 5 CNJs)will be accepted, just as in the form.Airlines are able to change the associated document number when authorizingRefund Applications i.e. when field IT02.RFAS is “A”. The transaction will berejected if the next RTDN is not the same as the first inserted.3.3.6IT05 CORT, COAM and COTPThe first CORT/COAM pair is strictly reserved to the “Standard Commission”; ifthere is no such commission, the fields must be completed with zeroes. Thesecond COAM will always be the supplementary commission “SPAM” wheneverit is a Net Remit transaction. When a transaction includes CP and/or MF taxes, itwill be possible to include a ‘Commission on CP and MF’ (if so defined by theBSP), in the second (if it is not a NR transaction) or third CORT/COAM, identifiedby COTP XLP, where 0 COAM CP MF and 0 CORT 100.“3.3.7IT0H records for Remarks:Airlines have the possibility to add an IT0H record to be able to insert remarks inthe accepted or rejected refunds form. The content of IT0H will be inserted in the“Airline Remarks” box for “authorize” and “under investigation” transactions andin the “Rejection Reason” box for “reject” transactions.Two IT0H records will be permitted with 5 RMIN per IT0H containing 45characters (the allowable characters are Ç, ü, é, â, ä, à, å, ç, ê, ë, è, ï, î, ì, Ä, Å,É, æ, Æ, ô,ö, ò, û, ù, Ö, Ü, , , á, í, ó, ú, ñ, Ñ, ª, º, ¿, ¡, ß, Ø, , as well asPortuguese characters ( ã, Ã, õ, Õ, Ô, Ó, ), and the EURO symbol ( ) and theat sign (@). This corresponds to the American Standard Code for InformationInterchange (ASCII) characters from 32 to 126, 128 to 151, 153 to 157, 159 to165 and 225) per RMIN, which corresponds to the maximum characters allowedin the BSPlink RA form (10 lines of 45 characters each). Please, see below:Refund Remarks Information Records
Documentation l.1.04.14Last changed by:Reviewed and approved by:BSPlink SupportBSPlink Production TeamReference: 00001109Date:Page: 13 of23/05/201320Format/El.No. Rec. Lvl Element Description12345678910111213SSSSSSSSSSSSSGlossary Element StartReference Attribute PositionRecord IdentifierTransaction NumberReason for Memo Line IdentifierReason for Memo InformationReason for Memo Line IdentifierReason for Memo InformationReason for Memo Line IdentifierReason for Memo InformationReason for Memo Line IdentifierReason for Memo InformationReason for Memo Line IdentifierReason for Memo InformationReserved 5659104107152155200203248StatusMMMMCCCCCCCCM4 Refund Application Evaluation FileOnce the file processing has finished, BSPlink Centre generates a file with the results of theprocessing. This file has the following file name:Xxe8AAAC YYYYMMDD sequenceoAAAA: IATA Airline Code Check DigitThis file includes the transactions that have not been loaded due to errors that are explainedfurther down.The content of the “e8” file would be as follows:Line: n TRNN: xxxxxxxx Record.Field Element.Number Glossary.ReferenceError.DescriptionWhere,n is the line number where the error is found.TRNN is the transaction number where the error is found.Record is the record id.Field the field within the record.Description is the error explanation about the error.
Documentation l.1.04.14Last changed by:Reviewed and approved by:BSPlink SupportBSPlink Production TeamReference: 00001109Date:Page: 14 of23/05/201320Element.Number & Glossary.Reference correspond to DISH RET specifications.Example:Line: 30TRNN: 000008Error: The Refund does not exist.Record: IT02Element: # 8TDNRThe errors can be divided into 3 groups:1. Specific errors per register and field:ErrorDescription12IT01 expected in the first line.More that one IT01.RPSI1The RPSI has to be equal to MASS.REVN1Invalid REVN.ISOC1Invalid ISO Country Code.RCID1The Record Identifier must be 2TRNN123The transaction numbering must be sequential.The first transaction number must be 000001.Record is not in a transactionAGTN123The agent code is incorrect.The agent does not exist.The agency is not the one of the application.STAT123STAT expected to be blank or to start with I or D.STAT should indicate international/ domestic the same way as indicated in the refundissue.STAT expected to be equal to that of the refunded issue.TDNR1234567The ticket document number must be preceded by the airline code.There is no a corresponding series of documents.There is no a document with the indicated ticket document number.The refund has already been billed.Duplicated TDNR.TDNR does not match TACN.The refund does not exist.CDGT1The ticket document number control digit is incorrect.IT*FieldType1RCID2
Documentation l.1.04.14Last changed by:Reviewed and approved by:BSPlink SupportBSPlink Production TeamReference: 00001109Date:Page: 15 of23/05/201320TRNC12The document is not an RFND.Incorrect transaction code.TACN12345678The ticketing airline code must contain the airline code.The airline does not exist.The airline is not the owner of the document.Invalid Ticketing Airline Code Number (TACN)The airline is not a user of BSPlink.The BSPlink Account of the airline has expired.The value must be equal to the first 3 characters of TDNRThe airline is not the same that appears in the file name.CDGT1The airline code control digit is incorrect.ISOC1The ISO Country Code must be the same as the reported in the file name.RFAS12Invalid RFAS.The requested operation does not comply with the actual status of the refund.3RCPN123Invalid RCPN.You have not reported any coupon.An ADM/ACM does not have coupons.5TMFT123456789101112Incorrect format for the Tax Fee Type.XT not allowed as Tax Fee Type.For the Tax Fee Type a Tax Amount has to be reported.For the Tax Fee Type XFAAAdd no Tax Amount has to be reported.The Tax Fee Type should only be reported once.The Tax Fee Type XF should be reported before the first Tax Fee Type XFAAAdd.A Tax Fee Type XFAAAdd should follow the Tax Fee Type XF.No CP allowedNo MF allowedYou are not allowed to issue Refunds with mixed taxes.The Tax Fee Types XFAAAdd should be reported successively after a first XF.Invalid commission typeTMFA1234Tax on CP expected to be reported in corresponding TMFA.Reported Tax on CP value is inferior to the existing value.Tax on MF expected to be reported in corresponding TMFA.Reported Tax on MF value is inferior to the existing value.TDAM123The ticket/document amount has to be reported.Ticket/Document Amount only has to be reported on the first IT05.Ticket/Document Amount has to be a positive amount.
Documentation l.1.04.14Last changed by:Reviewed and approved by:BSPlink SupportBSPlink Production TeamReference: 00001109Date:Page: 16 of23/05/2013208HCOTP1234567Invalid XLP commission.Only one commission allowed.No XLP allowed.Invalid Commission Type.XLP Commission Amount has to be less than the sum of Tax on CP and MFIf XLP Commission is reported, a Tax on CP or MF is expected to be reportedCommission Type only has to be reported on the first IT05CORT12Invalid CORTCommission Rate only has to be reported on the first IT05COAM123456The Commission has to be less than the fare amount.No Discount Amount allowed.When Discount Amount is reported the value for NRID has to be NRInvalid COAMCommission Amount or Rate for XLP has to be reportedCommission Amount only has to be reported on the first IT05FPAC123The Form of Payment Account Number is not a valid credit card numberFPAC has to be reportedThe reported value is not correctFPAM12The sum of Form of Payment Amount has to be equal to the Ticket/DocumentAmount.FPAM has to be reported.CUTP123The CUTP is incorrect.CUTP has be the same one in all CUTP of the transaction.CUTP has to be reported.FPTP1234It is not possible to issue Credit Indirect Refunds.Only one CA FPTP allowed.Only CC and CA allowed for Form of Payment TypeInvalid FPTP for CC.RCID1The IT0H record is not in the correct position.RMLI1The reason for memo line identifier cannot be 0, if reason for memo information hasbeen reported in the corresponding line.The reason for memo line identifier numbering must be consecutive.2345The maximum reason for memo line identifier cannot exceed 10.A reason for memo line identifier equal to 0 has been reported, so no more IT0Hrecords can be reported.Please note the agent is basic and will not see in BSPlink any information entered bythe airline (warning, not error).
Documentation l.1.04.14Last changed by:Reviewed and approved by:BSPlink SupportBSPlink Production TeamReference: 00001109Date:Page: 17 of23/05/201320ZRCID1IT0Z expected in the last line.RRDC1Reported Record Counter does not report correct number of lines.2. Errors that may affect several registers at the same time:IT* Type1FieldSPEDPRDA2DAIS3DIRDErrorDescription12The reported value cannot be zero.The date is not a valid calendar date.3. Errors common to all registers that do not refer to specific fields:Error1234567DescriptionEmpty lines are not allowed.The record identifier is not an identifier of the allowed records.The reported value is not correct.The record has more than 255 characters.The record has less than 255 characters.Non-numeric characters in numeric fields.The record is not in the correct format.4. Errors while checking the file and transaction format:Error123456789DescriptionThe transaction cannot be processed.The record is not in the correct transaction.The reported transaction number is not correct.Only two Records with this RCID allowed.The record element has to be left blank.The record element has to be zero.The record element is mandatory.Record is not in a transaction.The transaction numbering must be sequential.
Documentation l.1.04.14Last changed by:Reviewed and approved by:BSPlink SupportBSPlink Production TeamReference: 00001109Date:Page: 18 of23/05/20132010There cannot be more than 70 IT03 records.5 Revision Control ChartRevision Nº1.00.00Issue date28/02/08ChangesFirst version.1.01.0026/05/08Elements 12, 13, 14, 15, 16 & 17 added into table on section 2Daily Refund Application Download File1.02.0001/07/08IT0H records for Remarks added on Section 3.3Specific errors for IT0H record added on Section 4.1.03.0001/08/08“Modify the RTDN when authorizing Ras” added on Section 3.3“RTDN” removed on Section 0091.04.0321/01/20101 Global Overview: P4: Note on upper case conversion.3.3.4 IT0H records for remarks: P10: Title changed from Reasonfor Memo Information Records to Refund Remarks InformationRecords, and removal of Reason for Memo Issuance Code fromthe remark records.1 Specific errors per register and field: P 13 and 14inclusion oftwo new errors by register field (COAM), and one for RTDN.3.3.1 and 3.3.1.3 Refund Application Action File: inclusion ofDISH 20. 2.3.2 Refund Validations text for e tickets removedsince no longer applies and Fare Adjustment Amount included.3.3.1Technical Aspects to take into consideration: adding twomore fields to be modified. 3.3.3 RTDN modification whenauthorizing Ras.3.3.6IT05 CORT and COAM values reported in COAMand CORT.3.3.1 Changes into Refund Application when it is authorized:Adding IT03.DIRD
Documentation l.1.04.14Last changed by:Reviewed and approved by:BSPlink SupportBSPlink Production TeamReference: 00001109Date:Page: 19 of23/05/2013201.04.0414/04/20101 Specific errors per register and field: RMLI. Adding newwarning related to basic agents.1.04.0528/05/20101.04.0628/12/2010Note added to “Global overview” stating the order of processingof the “e9” files.1.04.0724/05/20112.Daily Refund Application Download File: Including newenhancements information (p5 and 6)1.04.0807/07/2011Section 1 Specific errors per register and field: Adding ErrorInvalid commission type, 3.2 Basic Config for
3 Refunded Ticket Number Number of ticket being refunded 10N 4 Refund Ticket Coupon Number Identifier Shows refunded coupon number(s) of the refunded ticket 4N 5 Agent IATA Code IATA Code of Agent issuing Refund . system will be EARS, i.e.
