Documentation code: bsplink.acdmmassloader.usermanual.2.0.57
Last changed by:
Reviewed and approved by:
BSPlink Support
Documentation Team
Reference:
Date: 26/08/2013
Page: 1 of 47
SF 00001089
ADM/ACM Interface
File Layout Specifications
2.0.57
Documentation code: bsplink.acdmmassloader.usermanual.2.0.57
Last changed by:
Reviewed and approved by:
BSPlink Support
Documentation Team
Reference:
Date: 26/08/2013
Page: 2 of 47
SF 00001089
1
Global overview __________________________________________________ 3
2
RET File Format version 2.0 ________________________________________ 4
2.1
2.1.1
2.1.2
2.1.3
2.2
2.2.1
2.2.2
Upload ADM/ACM Files version 2.0 ______________________________ 5
Basic Configuration Table for ADMs/ACMs loaded in RET format v.2.0 ________ 9
Technical Description ______________________________________________ 11
Errors Description _________________________________________________ 24
Download ADM/ACM Files version 2.0___________________________ 30
Basic Configuration for ADMs/ACMs downloaded in RET format v.2.0 ________ 31
Technical Description ______________________________________________ 33
3
Upload Attached Files to BSPlink ADM/ACM Transactions _____________ 34
4
Annex 1: Mapping/Cross References _______________________________ 36
4.1
ADM/ACM Form based on an issue _____________________________ 36
4.2
ADM/ACM Form based on a refund _____________________________ 38
5
Annex 2: Sample Files in RET File Format version 2.0 _________________ 40
6
Revision Control Chart ___________________________________________ 41
Documentation code: bsplink.acdmmassloader.usermanual.2.0.57
Last changed by:
Reviewed and approved by:
BSPlink Support
Documentation Team
Reference:
Date: 26/08/2013
Page: 3 of 47
SF 00001089
1 Global overview
The aim of this interface is to provide BSPlink with a different way of issuing ADMs/ACMs. The
participant Airlines, BSP Airlines, BSP Agents and Third Parties, can upload a file with the
contents of the ADMs and/or ACMs through BSPlink, avoiding filling in the current forms for
every ADM/ACM.
The ADMs/ACMs received through file will have the same treatment as if they were manually
inserted through the BSPlink Web-based application.
These specifications are based on new ADM/ACM forms in BSPlink version 1.6, and this is the
only file format that currently contains all additional information needed to populate all fields in
the ADM/ACM online forms thus providing agents with as much details as possible.
In this manual, we are dealing with RET file format version 2.0 to send ADM/ACM files to
BSPlink. There are three ways to upload these files, depending on the file descriptor used in
the file name:



Via BSPlink web-based application, Upload ADM/ACM Files option, whenever the file
descriptor is “ec”.
Via BSPlink web-based application, Files – Upload option, whenever the file is within an
1
“ez” file, i.e. a zipped file.
Via SFTP, whenever the users have already created an SFTP account via the Secure
FTP Account option, within the Sub-Users Management module, in BSPlink web-based
2
application. The two files, “ec” and “ez” including ”ec” files can be sent via SFTP.
There are two different kinds of errors:

Syntactic: Those related to format file –length, alphanumeric/numeric/alphabetic
fields... As previously said, the RET File Format version 2.0 can be sent either via
BSPlink web-based application or via SFTP. In both cases, an ei file will be generated
indicating the user the syntactic errors that have been found. In both cases, the name of
the error file is as follows:
XXeiRECIPIENT_YYYYMMDD_sequence
RECIPIENT = Airline Code + check digit, if the user that previously sent the
file were an airline.
RECIPIENT= TTTuser id, if the user that previously sent the file were a Third
Party user.
However, if the error found when processing the file is about the existence of
another file already processed with the same file name or if the user who has
generated the file does not correspond to the sender:
 For files sent via SFTP, an e2 file will be generated to inform the user about
it. The file name would be
Xxe2RECIPIENT_YYYYMMDD_sender_sequence
1
An “ez” file can contain “ec” files and be sent to BSPlink Centre via the Upload option or via
SFTP. Such file will be uncompressed and the “ed” or “ec” file will be processed the same way
as the rest of “ed” and “ec” files individually sent. The only difference is that there would not be
a pre-evaluation process, i.e. as if it were sent via SFTP.
2
BSPlink secure FTP accounts expire after 3 months of inactivity.
Documentation code: bsplink.acdmmassloader.usermanual.2.0.57
Last changed by:
Reviewed and approved by:
BSPlink Support
Documentation Team
Reference:
Date: 26/08/2013
Page: 4 of 47
SF 00001089
However, please be informed that when an ADM/ACM file with an
incorrect name is sent through SFTP, the file will be moved to a folder
named BAD_FILES. This folder is created the first time the user uploads
through SFTP an ADM/ACM file with an incorrect name. From this moment,
all subsequent ADM/ACM files with incorrect name will be automatically
moved to the BAD_FILES folder, and therefore no e2 file will be
generated in this particular case. The files contained in the BAD_FILES
folder will not be processed unless the user correct the files names and
upload them again. Therefore, when uploading ADM/ACM files, users
should check if the BAD_FILES folder has been created and/or verify if the
files they just uploaded are contained in this folder. Files contained in the
BAD_FILES folder will be erased after two months.


For files sent via BSPlink web-based application, an error message will be
displayed on the screen.
Semantic: Those related to the content of the file. This is the file name:
XXeiRECIPIENT_YYYYMMDD_sequence
For further information on the content of this, please refer to 2.1.3 Errors Description
section for RET file format version 2.0.
Finally, it is worth mentioning that if the Airline and Third Party users have configured the E-mail
Alert parameter Errors in mass upload file in their corresponding e-mail alert menu within
BSPlink, the system will send them an e-mail message whenever “ei” or “e2” files are available
for downloading. Also, if the Airline and Third Party users have configured the E-mail Alert
parameter Successful Mass Upload in their corresponding e-mail alert menu within BSPlink, the
system will send them an e-mail message whenever an ‘ec’ file is successfully processed via
BSPlink option Files-Upload ADM/ACM Files or through SFTP service.
Airlines can retrieve their ei, e2 and eh (see section 2) files in three different ways:
- Via the Download Files option, where they will appear together with all the other files the
airline received.
- Via the Download ADM/ACM Files option, where only the ADM/ACM files generated by the
BSPlink system will appear.
- For enhanced airlines, also using an SFTP client, whenever they have activated an SFTP
account via the Mass Download Secure FTP Account (just one account per airline, managed by
any enhanced user or sub-user) or Secure FTP Account (available for the main user) options.
2 RET File Format version 2.0
Users are able to upload and download files containing ADM/ACM transactions, that is, send
and receive files to and from BSPlink Centre in an additional format.
This means that users are able to:
-
-
Upload a file to both, issue new ADM/ACM and carry out any modification on the
already issued transactions, such as dispute, reject or delete them. The related file
descriptor is “ec”. These files can be sent via the Upload ADM/ACM Files option in
BSPlink or via SFTP, if the user has an SFTP account.
Download a file containing online issues and modifications. The related file descriptor is
“eh”.
Documentation code: bsplink.acdmmassloader.usermanual.2.0.57
Last changed by:
Reviewed and approved by:
BSPlink Support
Documentation Team
Reference:
Date: 26/08/2013
Page: 5 of 47
SF 00001089
As far as possible, standard DISH fields have been used for the file records. Therefore, any
further doubt about the content or validation in these records can be queried in DISH
documentation, (DISH 20.1 and 20.3, Chapter 5 – Agent Reporting Data (RET)), although
please take into account that DISH 20.3 IT0G record has no relation whatsoever to massupload
IT0G.
The participants will send the ADMs/ACMs to BSPlink in order to notify agents, via BSPlink, of
the issue of these documents. Therefore, airlines will not have to perform the notification by
other means. These ADMs/ACMs could also wait for the latency days, set by BSP, in order to
be settled.
BSPlink will include these ADMs/ACMs in the RET to be sent to the DPC in the corresponding
settlement period, as it is done with the rest of ADM/ACM manually issued. The ADMs/ACMs
sent to BSPlink in a file will not be sent to the DPC or the agents again.
2.1
Upload ADM/ACM Files version 2.0
The uploading file version 2.0 is based on current DISH 20.1 and DISH 20.3 specifications. As
previously mentioned, users will be able to send to BSPlink Centre files containing both new
and modified transactions so that they are loaded in BSPlink web-based application.
Each file should contain transactions for one unique airline, if the user is an airline. External
party providers will be able to upload a file with transactions for several airlines.
Figure 1: Upload ADM/ACM Files
Documentation code: bsplink.acdmmassloader.usermanual.2.0.57
Last changed by:
Reviewed and approved by:
BSPlink Support
Documentation Team
Reference:
Date: 26/08/2013
Page: 6 of 47
SF 00001089
File Name Checking: When uploading an ADM/ACM file, the system will check that the file
name follows the BSPlink File Naming Convention. The file should have the following format.
XXecEARS_YYYYMMDD_sender_sequence
Where:
NAME
XX
ec
EARS
YYYYMMDD
Sender
Sequence
DESCRIPTION
ISO Country Code
File descriptor
Recipient. In this case, it is the BSPlink Centre,
which identifying code is EARS.
File generation date
BSPlink user who uploads the file. For airlines,
it should include the check digit. Note that for
Third Parties it is case sensitive.
000 if it is the first file uploaded for this user in
that date. An incremental number for next files
sent for the same user at the same date.
NOTE! The File Descriptor for these files would be ‘ec’.
In case the file does not follow the format above, the system will not allow the file to be
uploaded; a message will inform the user about it, and, therefore, the user should correct the file
name and upload it again. There will be no limit in the sending of files as well as in the
frequency of the sending. However, two files with the same name CANNOT be sent.
Example:
• The first file sent by 001 airline on 17/08/2004 would have the name:
XXecEARS_20040817_0011_000
• The second file sent by that airline on 17/08/2004 should then have the following name:
XXecEARS_20040817_0011_001
The system also checks that the user loading the file is the same as that in the file name. In
case it were not the same, a message about incorrect file name would inform the user about the
problem.
Please note that the “ec” files are processed in the following order: date-sequence-issuer.
Syntactic and Semantic Evaluation: Once the file has been correctly loaded, the system will
carry out a semantic and a syntactic evaluation to check that everything in the file has been
correctly defined. Note that we assume that the file contains documents only for a BSP (The
BSP which is indicated in the File Name).
After the evaluation, a new file is generated, containing the results of the evaluation. The file will
be available in no more than 24 hours, in the Files option in BSPlink Web-based application.
The correctly issued ADMs/ACMs can, then, be queried by the airline in ADM/ACM Queries in
BSPlink Web-based application.
Documentation code: bsplink.acdmmassloader.usermanual.2.0.57
Last changed by:
Reviewed and approved by:
BSPlink Support
Documentation Team
Reference:
Date: 26/08/2013
Page: 7 of 47
SF 00001089
The file, generated after the syntactic and semantic evaluation, will also follow the BSPlink File
Naming Conventions. The name will have the following structure:
XXeiRECIPIENT_YYYYMMDD_sequence
NAME
XX
ei
RECIPIENT
YYYYMMDD
Sequence
DESCRIPTION
ISO Country Code
File descriptor
It is the file recipient, and it corresponds to the
user who previously sent the file to BSPlink
Centre. If the user is an airline, the check digit
should also be included.
File generation date
000, if it is the first file uploaded for this user in
that date. An incremental number for next files
sent for the same user at the same date.
Note that it is a new file and, therefore, the file descriptor will change from ‘ec’ to ‘ei’
The next figure shows the process:
Documentation code: bsplink.acdmmassloader.usermanual.2.0.57
Last changed by:
Reviewed and approved by:
BSPlink Support
Documentation Team
Reference:
Date: 26/08/2013
Page: 8 of 47
SF 00001089
The user (AAAA) uploads through
BSPlink the ADMs/ACMS file.
XXecEARS_YYYYMMDD_AAAA_000
File correctly
loaded
File with incorrect name: The user
should correct it and load it again.
BSPlink Centre EVALUATES
the file in no more than 24 hours
BSPlink Centre generates a file with the results of the
EVALUATION of the file sent by the user:
XXeiAAAA_YYYYMMDD_SSS
This file can be DOWNLOADED by the user, via BSPlink in
order to check the evaluation made.
ADMs/ACMs with errors
will not be issued via
BSPlink. Those erroneous
transactions may be
corrected and can be
uploaded again in another
file
ADMs/ACMs without
errors:
BSPlink NOTIFIES the
issue of these
documents via BSPlink
browser.
ADMs/ACMs ‘wait’ for the
“latency/disputing period” to be settled
BSPlink includes these ADMs/ACMs in
the RET to be sent to the DPC in the
corresponding settlement period
Flow chart 1: Global process
Documentation code: bsplink.acdmmassloader.usermanual.2.0.57
Last changed by:
Reviewed and approved by:
BSPlink Support
Documentation Team
Reference:
Date: 26/08/2013
Page: 9 of 47
SF 00001089
2.1.1
Basic Configuration Table for ADMs/ACMs loaded in RET format v.2.0
There are two options in BSPlink web application for Airlines and BSP that configure certain
parameters related to ADM/ACM and that affect this functionality. Some of the parameters are
the following:
1. Airlines: Within Basic Configuration – Basic Parameters option:




Reject whole file or transactions with errors only?: The airline decides whether the
whole file should be rejected when an error is detected or only the incorrect transactions
should not be processed.
- If Errors is set, the correct transactions will be processed. The user should
correct the wrong transactions and send the file again, including only the
modified transactions.
- If File is set, no transaction will be processed. The user should modify the
wrong transactions and send the file again, including both, the correct and the
3
modified transactions
Third Party Authorization: Through this option airlines can select each third party per
BSP and assign a separate permission for ADM and ACM issue on their behalf.
Handling Fee & Penalty Charge: These two fields are related to ADMs/ACMs that are
being issued on a refund. If Yes value has been previously selected, the user can enter
CP and MF taxes in the corresponding fields in IT0G.
CP/MF on ADMs/ACMs concerning issue: if the BSP has set to Yes these
parameters in the Basic Configuration, CP and MF taxes are allowed for ADMs/ACMs
issued concerning STDs.
2. BSP:
Within Master Tables – Basic Configuration option:





ADM/ACM Latency Days: This parameter is set by the BSP and is always taken into
account. Please note that there will not be latency days for SPCDR.
ADM/ACM Capture Mode: This parameter is not taken into account. ADM/ACM will be
loaded with the number included in the corresponding TDNR. The only control that is
carried out over the document number is that there is a series registered in the system
for such ADM/ACM numbers included in the file.
ADM/ACM TOCA: If set to ‘No’, the TOCA field in IT05 and TCOC/TCYC in IT0G will
not be applicable. Therefore, if entered, the transaction will be rejected.
ADM/ACM SPAM: If set to ‘No’, the second occurrence of CORT, COAM and NRID in
IT05 and SPOC/SPYC in IT0G will not be applicable. Therefore, if any value is entered,
the transaction will be rejected. If set to ‘Yes’ and there is any value in these fields, the
system will check that NRID value is NR, in IT05.
Positive VAT: This field can be set to ‘Yes’ or ‘No’. Depending on the value selected,
the TCOC/TCYC and COOC/COYC fields in IT0G will have different sign.
-

3
If Yes is selected, the TCOC/TCYC and COOC/COYC fields have different
sign.
If No is selected, the TCOC/TCYC and COOC/COYC fields have the same
sign.
Free Stat: This parameter, along with the document type configuration, affects to the
definition of the STAT field in IT02. It may have two values: No or Yes. Please refer to
the following table for further information:
If the user loading the file is a Third Party, the system will not take into account the value of
this parameter, and only the incorrect transactions will be rejected.
Documentation code: bsplink.acdmmassloader.usermanual.2.0.57
Last changed by:
Reviewed and approved by:
BSPlink Support
Documentation Team
Reference:
Date: 26/08/2013
Page: 10 of 47
SF 00001089
Document Type
International
Domestic
Neutral



Free Stat
No
Yes
No
Yes
No
Yes
IT02 – STAT
I
I + two additional characters in upper case
D
D + two additional characters in upper case
D or I
D or I + two additional characters in upper case
Blank
Duplicated ADM/ACM Numbers: If set to Yes, the system will accept duplicated
document numbers. Please note, however, that this parameter can only be activated in
the environments where the DPC accepts duplicated ADM/ACM numbers.
Also note that no duplicated numbers will be accepted if they have been previously
issued by the same airline (unless they have previously deleted the ADM/ACM or it has
been automatically deleted after being in the system for 13 months).
STP controls and validations: If set to Yes certain controls and validations over
Satellite Ticket Printer agents (STP) must be carried out when issuing mass loader
transactions. The system will reject the transactions issued to STP agents.
CP/MF Airline Configuration: Decide whether to allow the Handling Fee on Refunds,
Penalty Charge on Refunds and Commission on CP and MF parameters to be
managed by the airlines. When the BSP decides to change the value of the parameter
from ‘No’ to ‘Yes’, the airlines would be able to manage the three parameters in their
basic configuration, being the default value ‘No’. When the BSP changes the value of
the parameter from ‘Yes’ to ‘No’, the airlines will not be able to see the parameters in
their basic configuration anymore, and the value of these parameters would be
automatically reset to ‘No’ for all the airlines.
Within Master Tables:

TCTP (Tax on commission type): The BSP will be able to define up to 5 possible
TCTP values along with their corresponding descriptions as long as the Basic
Configuration parameter ADM/ACM TOCA is enabled in BSPlink. The fields are
alphanumeric and can admit up to 6 characters for TCTP and up to 50 for the
description.
Documentation code: bsplink.acdmmassloader.usermanual.2.0.57
Last changed by:
Reviewed and approved by:
BSPlink Support
Documentation Team
Reference:
Date: 26/08/2013
Page: 11 of 47
SF 00001089
2.1.2
Technical Description
ADM/ACM RET File Structure version 2.0 – Upload
Record
Description
Transaction Type 4
A
D/
C
M
B
AD
/C
SB
A
D/
C
P
B
AD
/C
DB
AD
/C
DT
AD/C
JB
AD/C
RB
AD/C
RT
AD
/C
WB
AD
/C
WT
A
D/
C
N
T
SP
DR
/SP
CR
SP
DR
/SP
CR
***
AD
MD
/A
CM
D
IT01
File header
1
1
1
1
1
1
1
1
1
1
1
IT02
Basic sale
transaction
record
Related
ticket/document
information
record
Monetary
amount record
1
1
1
1
1
1
1
1
1
1
1
(070)
n/a
n/a
n/a
n/a
n/a
n/a
n/a
(070)
(070)
(070)
(0n)
n/a
n/a
n/a
n/a
n/a
n/a
(0n)
1
(0n)
1
IT08
Form of
payment record
(01)
n/a
n/a
n/a
n/a
n/a
n/a
(01)
1
(01)
1
IT0G
ADM/ACM
calculation
information
record
ADM/ACM
reason for
memo
information
record
ADM/ACM
airline contact
information
record
File trailer
(01)
n/a
n/a
n/a
n/a
n/a
n/a
(01)
n/a
(01)
n/a
(099)
(01)
(02)
(01)
(0-1)
n/a
(01)
(099)
(099)
(099)
(099)
1
n/a
n/a
n/a
n/a
n/a
n/a
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
IT03
IT05
IT0H
IT0I
IT0Z
Note: It is not possible to carry out more than one modification over the same transaction in the
same file for the same airline (TACN), i.e., it is not possible to issue a document and within the
same file, to dispute it. Both transactions will be rejected.
4
These codes will correspond to the TRNC in IT02: ADMB: ADM Issue; ADPB: ADM Dispute; ADJB:
Reject an ADM Dispute; ADSB: Approve an ADM Dispute; ADDB: Deactivate ADM/SPDR/ADMD; ADRB:
Reactivate ADM/SPDR/ADMD; ADWB: Delete ADM/SPDR/ADMD; ACMB: ACM Issue; ACPB: ACM
Dispute; ACJB: Reject an ACM Dispute; ACSB: Approve an ACM Dispute; ACDB: Deactivate
ACM/SPCR/ACMD; ACRB: Reactivate ACM/SPCR/ACMD; ACWB: Delete ACM/SPCR/ACMD, ADNT:
Non-ticket related debit Issue, ACNT: Non-ticket related credit Issue, ADDT: Deactivate ADNT, ACDT:
Deactivate ACNT, ADRT: Reactivate ADNT, ACRT: Reactivate ACNT, ADWT: Delete ADNT, ACWT:
Delete ACNT, SPCR: Settlement Plan Credit issue, SPDR: Settlement Plan Debit issue, ADMD:
Agent Debit Memo Default issue, ACMD: Agent Credit Memo Default issue.
Documentation code: bsplink.acdmmassloader.usermanual.2.0.57
Last changed by:
Reviewed and approved by:
BSPlink Support
Documentation Team
Reference:
Date: 26/08/2013
Page: 12 of 47
SF 00001089
All records, if present, can never be blank due to numeric and mandatory status.
*** Note that the same standard controls that apply for ADMs/ACMs will apply for SPDR/SPCR
if the BSP parameter “Standard ADM/ACM form for SPDR/SPCR Issuance” is set to Yes
IT01 – File Header Record
El. Format/
No. Rec.Lvl Element Description
1
2
3
4
5
6
7
8
9
10
11
S
S
S
S
S
S
S
S
S
Record Identifier
System Provider Reporting Period Ending Date
Reporting System Identifier
Handbook Revision Number
Test/Production Status
Processing Date
Processing Time (HHMM)
Reserved Space
File Type
File Type Sequence Number
Reserved Space
Glossary Element
Start
Status Reference Attribute Position
M
M
M
M
M
M
M
M
C
C
M
RCID
SPED
RPSI
REVN
TPST
PRDA
TIME
RESD
FTYP
FTSN
RESD
1AN
6N
4AN
3N
4AN
6N
4N
8AN
1AN
2AN
216AN
Notes:
It is important to bear in mind that any error in this register will imply the rejection of the file.
2) SPED: The SPED reported is the date of file generation. The date, in format YYMMDD,
cannot be superior to the date when the file is sent + 1, i.e., to the processing date.
If there is no IT0I, the billing period will correspond to the period of the file processing date + the
latency days. For further information, please refer to REBP field in IT0I register.
3) RPSI: If the sender is an airline, the RPSI will be the airline code plus the check digit
(example: 1256). If the sender is a Third Party user, the RPSI will contain TTTT.
4) REVN for this file corresponds to 200, 201 or 203.
5) TPST is either PROD or TEST.
6) PRDA in format YYMMDD.
1
2
8
12
15
19
25
29
37
38
40
Documentation code: bsplink.acdmmassloader.usermanual.2.0.57
Last changed by:
Reviewed and approved by:
BSPlink Support
Documentation Team
Reference:
Date: 26/08/2013
Page: 13 of 47
SF 00001089
IT025 – Basic Sale Transaction Records
El.N Format/R
o.
ec. Lvl Element Description
1
2
3
S
S
S
Record Identifier
Transaction Number
Agent Numeric Code
RCID
TRNN
AGTN
1AN
6N
8N
1
2
8
4
5
6
7
8
9
10
11
S
S
S
X
X
S
S
S
CJCP
CPUI
DAIS
STAT
TDNR
CDGT
TRNC
TCNR
3AN
4AN
6N
3AN
15AN
1N
4AN
15AN
16
19
23
29
32
47
48
52
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
S
S
S
S
S
S
Conjunction Ticket Indicator
Coupon Use Indicator
Date of Issue
Statistical Code
Ticket/Document Number
Check-Digit
Transaction Code
Transmission Control Number
Transmission Control Number
Check-Digit
Ticketing Airline Code Number
Check-Digit
Format Identifier
Passenger Name
Approved Location Type
Stock Control Number or
Stock Control Number “From”
Stock Control Number “To”
Approved Location Numeric Code
Approved Location Type
Stock Control Number “From”
Stock Control Number “To”
Approved Location Numeric Code
Approved Location Type
Stock Control Number “From”
Stock Control Number “To”
Approved Location Numeric Code
Approved Location Type
Stock Control Number “From”
Stock Control Number “To”
Settlement Authorization Code
TCND
TACN
CDGT
FORM
PXNM
ALTP
SCNR
SCNF
SCNT
ALNC
ALTP
SCNF
SCNT
ALNC
ALTP
SCNF
SCNT
ALNC
ALTP
SCNF
SCNT
ESAC
1N
5AN
1N
1AN
49AN
1AN
16AN
16AN
4N
8N
1AN
16AN
4N
8N
1AN
16AN
4N
8N
1AN
16AN
4N
14AN
67
68
73
74
75
124
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
5
A
D/C
D
B
A
D/
C
J
B
A
D/C
R
B
A
AD
A
A D/ SP MD
D/C D/C C DR/ /AC
W
S N SP MD
B
B T CR
M M M
M M M
M M M
n/a n/a n/a
M
M
M
n/a
M
M
M
n/a
M M M M M
M M M M M
M M M M M
n/a n/a n/a n/a n/a
Glossar Eleme Start A A
y
nt
D/C D/C
Referen Attribu Posit M P
ce
te ion
B B
125
141
145
153
154
170
174
182
183
199
203
211
212
228
232
n/a n/a n/a n/a n/a n/a n/a n/a n/a
M n/a n/a n/a n/a n/a n/a M M
C n/a n/a n/a n/a n/a n/a C C
M M M M M M M M M
n/a n/a n/a n/a n/a n/a n/a n/a n/a
n/a
M
C
M
n/a
M M M M M M M M M M
n/a n/a n/a n/a n/a n/a n/a n/a n/a n/a
n/a n/a n/a n/a n/a n/a n/a n/a n/a n/a
M M
M M
n/a n/a
C n/a
n/a n/a
n/a n/a
n/a n/a
n/a n/a
n/a n/a
n/a n/a
n/a n/a
n/a n/a
n/a n/a
n/a n/a
n/a n/a
n/a n/a
n/a n/a
n/a n/a
n/a n/a
n/a n/a
n/a n/a
M
M
n/a
n/a
n/a
n/a
n/a
n/a
n/a
n/a
n/a
n/a
n/a
n/a
n/a
n/a
n/a
n/a
n/a
n/a
n/a
M
M
n/a
n/a
n/a
n/a
n/a
n/a
n/a
n/a
n/a
n/a
n/a
n/a
n/a
n/a
n/a
n/a
n/a
n/a
n/a
M
M
n/a
n/a
n/a
n/a
n/a
n/a
n/a
n/a
n/a
n/a
n/a
n/a
n/a
n/a
n/a
n/a
n/a
n/a
n/a
M
M
n/a
n/a
n/a
n/a
n/a
n/a
n/a
n/a
n/a
n/a
n/a
n/a
n/a
n/a
n/a
n/a
n/a
n/a
n/a
M
M
n/a
n/a
n/a
n/a
n/a
n/a
n/a
n/a
n/a
n/a
n/a
n/a
n/a
n/a
n/a
n/a
n/a
n/a
n/a
The following accepted TRNC are not added in the IT02 record table to simplify the reading:
ADST: Approve ADNT Dispute, ACST: Approve ACNT Dispute, ADJT: Reject ADNT Dispute,
ACJT: Reject an ACNT Dispute, ADDT: Deactivate ADNT, ACDT: Deactivate ACNT, ADRT:
Reactivate ADNT, ACRT: Reactivate ACNT, ADWT: Delete ADNT, ACWT: Delete ACNT
M M M
M M M
n/a n/a n/a
C C C
n/a n/a n/a
n/a n/a n/a
n/a n/a n/a
n/a n/a n/a
n/a n/a n/a
n/a n/a n/a
n/a n/a n/a
n/a n/a n/a
n/a n/a n/a
n/a n/a n/a
n/a n/a n/a
n/a n/a n/a
n/a n/a n/a
n/a n/a n/a
n/a n/a n/a
n/a n/a n/a
n/a n/a n/a
Documentation code: bsplink.acdmmassloader.usermanual.2.0.57
Last changed by:
Reviewed and approved by:
BSPlink Support
Documentation Team
Reference:
Date: 26/08/2013
Page: 14 of 47
SF 00001089
34
35
36
S
S
Data Input Status Indicator
ISO Country Code
Reserved Space
DISI
ISOC
RESD
1AN
2A
7AN
246
247
249
n/a n/a n/a n/a n/a n/a n/a n/a n/a n/a
M
M
M
M
M
M
M M
M M
M
M
M
M
Notes:
2) TRNN: When TRNNs are not sequential; the whole file will be rejected.
3) AGTN: Please be informed that when an agent is not active in the agent’s master table, an
error message will be displayed in the evaluation ‘ei’ file in order to inform the user about it. The
transaction will be rejected. Note that for SPDR/SPCR and ADMD/ACMD, AGTN must
correspond to that of a BSP Agent when TACN does not correspond to that of BSP airline.
6) DAIS: if the date reported in DAIS is previous to the file processing date and TRNC is
reported as ADMB or ACMB, the issue date of the transaction will correspond to the date the file
was processed. In this way, agents are able to dispute the transaction during the latency period.
7) STAT field depends on both the document type configuration and the value of the Free Stat
parameter set by BSP. For further information, please refer to 2.1.1 Basic Configuration Table
for ADMs/ACMs loaded in RET format v.2.0. Only uppercase letters are accepted.
8) TDNR field is formed by TACN+ ‘adm-acm number code’. The TACN will be the same as that
in field 13, in IT02. If the user sending the file is a Third Party user, there can be duplicated
TDNR for different airlines within the same file. Note that ADM/ACM transactions are rejected
when the capture mode is set to 8 or 9 and the TDNR field contains a document number
comprised within the series corresponding to the prefix assigned for the ADM/ACM on-line
issues. For SPDR/SPCR and ADMD/ACMD, the TDNR must coincide with the ADM/ACM series
defined for mass upload.
10) TRNC: Find below a list with the TRNC accepted:
-
ADMB: ADM Issue
ADPB: ADM Dispute
ADJB: Reject an ADM Dispute
ADSB: Approve an ADM Dispute
ADDB: Deactivate ADM/SPDR/ADMD
ADRB: Reactivate ADM/SPDR/ADMD
ADWB: Delete ADM/SPDR/ADMD
ACMB: ACM Issue
ACPB: ACM Dispute
ACJB: Reject an ACM Dispute
ACSB: Approve an ACM Dispute
ACDB: Deactivate ACM/SPCR/ACMD
ACRB: Reactivate ACM/SPCR/ACMD
ACWB: Delete ACM/SPCR/ACMD
ADNT: Non-ticket related debit Issue
ACNT: Non-ticket related credit Issue
ADDT: Deactivate ADNT
ADRT: Reactivate ADNT
ADWT: Delete ADNT
ACDT: Deactivate ACNT
ACRT: Reactivate ACNT
ACWT: Delete ACNT
SPCR: Settlement Plan Credit issue
SPDR: Settlement Plan Debit issue
ADMD: Agent Debit Memo Default issue
M M
M M
M
M
Documentation code: bsplink.acdmmassloader.usermanual.2.0.57
Last changed by:
Reviewed and approved by:
BSPlink Support
Documentation Team
Reference:
Date: 26/08/2013
Page: 15 of 47
SF 00001089
-
ACMD: Agent Credit Memo Default issue
Note 1: If the TRNC is ADMB or ACMB, the PEAU in IT0I is equal to ‘N’ and the BSP has
deactivated the options ‘ADM Issues’ and ‘ACM Issues’ for the airline, the transaction will be
rejected. Also, note that BSP Adjustment transaction codes (SPDR, SPCR, ADMD and ACMD)
can be issued, deleted, or modified ,as long as the TACN in IT02 correspond to that of a BSP
Airline or the AGTN to that of a BSP Agent.
Note 2: Due IATA Resolutions concerning disputes, Airlines should only have the possibility to
modify or reject a dispute for a period of 60 days from date of dispute. After those 60 days,
disputed ADM/ACMs in BSPlink will have status “deleted” i.e. dispute cannot be modified or
rejected.
Note 3: Only uppercase letters are accepted in this field.
13) TACN: Please be informed that the airline issuing the document must be an active BSPlink
user the day the file is being processed. Note that for SPDR/SPCR and ADMD/ACMD, TACN
must correspond to that of a BSP Airline when AGTN does not correspond to that of BSP agent.
16) PXNM: The mass-upload process is designed to convert the PXNM field to uppercase
characters in RET file format ver. 2.0 (“ec” files for all ACDM type transactions).
Documentation code: bsplink.acdmmassloader.usermanual.2.0.57
Last changed by:
Reviewed and approved by:
BSPlink Support
Documentation Team
Reference:
Date: 26/08/2013
Page: 16 of 47
SF 00001089
IT03 – Related Ticket/Document Information Records
Format/
El.No. Rec. Lvl Element Description
Record Identifier
1
S
Transaction Number
2
S
Related Ticket/Document Coupon
3
S
Number Identifier
Related Ticket/Document Number
4
S
Check-Digit
5
S
Related Ticket/Document Coupon
6
S
Number Identifier
Related Ticket/Document Number
7
S
Check-Digit
8
S
Related Ticket/Document Coupon
9
S
Number Identifier
Related Ticket/Document Number
10
S
Check-Digit
11
S
Related Ticket/Document Coupon
12
S
Number Identifier
Related Ticket/Document Number
13
S
Check-Digit
14
S
Related Ticket/Document Coupon
15
S
Number Identifier
Related Ticket/Document Number
16
S
Check-Digit
17
S
Related Ticket/Document Coupon
18
S
Number Identifier
Related Ticket/Document Number
19
S
Check-Digit
20
S
Related Ticket/Document Coupon
21
S
Number Identifier
Related Ticket/Document Number
22
S
Check-Digit
23
S
Date of Issue Refunded
Document
24
S
25
S
Tour Code
26
S
Waiver Code
27
S
Reason for Memo Issuance Code
28
S
Reserved Space
Glossary
Reference
RCID
TRNN
Start
Element Positio
Attribute
n
1AN
1
6N
2
A
D/C
M
B
M
M
SP ADM
DR/SP D/AC
CR MD
M
M
M
M
RCPN
RTDN
CDGT
4N
15AN
1N
8
12
27
n/a
M
M
n/a
M
M
n/a
M
M
RCPN
RTDN
CDGT
4N
15AN
1N
28
32
47
n/a
C
C
n/a
C
C
n/a
C
C
RCPN
RTDN
CDGT
4N
15AN
1N
48
52
67
n/a
C
C
n/a
C
C
n/a
C
C
RCPN
RTDN
CDGT
4N
15AN
1N
68
72
87
n/a
C
C
n/a
C
C
n/a
C
C
RCPN
RTDN
CDGT
4N
15AN
1N
88
92
107
n/a
C
C
n/a
C
C
n/a
C
C
RCPN
RTDN
CDGT
4N
15AN
1N
108
112
127
n/a
C
C
n/a
C
C
n/a
C
C
RCPN
RTDN
CDGT
4N
15AN
1N
128
132
147
n/a
C
C
n/a
C
C
n/a
C
C
DIRD
TOUR
WAVR
RMIC
RESD
6N
15AN
14AN
5AN
68AN
148
154
169
183
188
C
n/a
n/a
n/a
M
C
n/a
n/a
n/a
M
C
n/a
n/a
C
M
Note 1: The IT03 record can be repeated 70 times giving a maximum number of related tickets
of 490. The 20 first ticket numbers will be displayed in the corresponding boxes on the BSPlink
form. The rest will be available for viewing in a new window that is opened by clicking a link /
button in the form.
Note 2: RMIC in IT03 will only be accepted whenever REVN is 203. For lower REVN values,
RMIC will be taken from the IT0H record (please refer to IT0H for more information).
Documentation code: bsplink.acdmmassloader.usermanual.2.0.57
Last changed by:
Reviewed and approved by:
BSPlink Support
Documentation Team
Reference:
Date: 26/08/2013
Page: 17 of 47
SF 00001089
IT05 – Monetary Amounts Record
El. Format/
No. Rec.Lvl Element Description
SP
A SP DR/ AD
D/C DR/ SP MD
Glossary Element
Start
M SP CR /AC
Reference Attribute Position B CR *** MD
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
Record Identifier
Transaction Number
Amount Entered by Agent
Reserved Space
Tax/Miscellaneous Fee Type
Tax/Miscellaneous Fee Amount
Tax/Miscellaneous Fee Type
Tax/Miscellaneous Fee Amount
Tax/Miscellaneous Fee Type
Tax/Miscellaneous Fee Amount
Ticket/Document Amount
Currency Type
Tax on Commission Amount
Reserved Space
Tax/Miscellaneous Fee Type
Tax/Miscellaneous Fee Amount
Tax/Miscellaneous Fee Type
Tax/Miscellaneous Fee Amount
Tax/Miscellaneous Fee Type
Tax/Miscellaneous Fee Amount
Commission Type
Commission Rate
Commission Amount
Commission Type
Commission Rate
Commission Amount
Commission Type
Commission Rate
Commission Amount
Net-Reporting Indicator
Amount Paid by Customer
RCID
TRNN
AEBA
RESD
TMFT
TMFA
TMFT
TMFA
TMFT
TMFA
TDAM
CUTP
TOCA
RESD
TMFT
TMFA
TMFT
TMFA
TMFT
TMFA
COTP
CORT
COAM
COTP
CORT
COAM
COTP
CORT
COAM
NRID
APBC
1AN
6N
11N
11AN
8AN
11N
8AN
11N
8AN
11N
11N
4AN
11N
1AN
8AN
11N
8AN
11N
8AN
11N
6AN
5N
11N
6AN
5N
11N
6AN
5N
11N
2AN
11N
1
2
8
19
30
38
49
57
68
76
87
98
102
113
114
122
133
141
152
160
171
177
182
193
199
204
215
221
226
237
239
S
Tax on Commission Type
TCTP
6AN
250
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
S
S
S
32
S
S
S
S
S
S
S
S
S
Notes:
5/7/9/15/17/19) TMFT fields cannot include XT taxes. It should have two characters or the
format XFAAAN, where: AAA refers to the Airport Acronym; it can be any alphabetical
character; N refers to a code reflecting the amount collected in the currency of the country
where the Airport is located.
M M
M M
C n/a
M M
C n/a
C n/a
C n/a
C n/a
C n/a
C n/a
M M
M M
C n/a
M M
C n/a
C n/a
C n/a
C n/a
C n/a
C n/a
C n/a
C n/a
C n/a
C n/a
C n/a
C n/a
C n/a
C n/a
C n/a
C n/a
C n/a
n/a
C n/a C
M
M
C
M
C
C
C
C
C
C
M
M
C
M
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
M
M
n/a
M
n/a
n/a
n/a
n/a
n/a
n/a
M
M
n/a
M
n/a
n/a
n/a
n/a
n/a
n/a
n/a
n/a
n/a
n/a
n/a
n/a
n/a
n/a
n/a
n/a
n/a
Documentation code: bsplink.acdmmassloader.usermanual.2.0.57
Last changed by:
Reviewed and approved by:
BSPlink Support
Documentation Team
Reference:
Date: 26/08/2013
Page: 18 of 47
SF 00001089
It is possible to enter more than one tax with the same ISO tax code in the ‘ec’ file. The ISO tax
code that can only be entered once is the XF tax.
Carrier Service Fee taxes will be identified as two character code (OA/OB/OC) followed by up to
6 valid characters (A-Z, 0-9,’.’, ‘/’, ‘-‘ or blank).
Only uppercase letters are accepted in TMFT fields.
6/8/10/16/18/20) If TMFA is different from 0, there should be a value in TMFT, except when the
TMFT is a tax with format XFAAAN
If the BSP has set to Yes the CP/MF on ADMs/ACMs concerning issue parameter in the Basic
Configuration according to market practice, CP and MF taxes are allowed for ADMs/ACMs
issued concerning STDs.
12) CUTP. The 3-character ISO Currency Code and the number of decimals for that currency
must be valid for the country of issue.
13) TOCA: If the BSP has set to No the ADM/ACM TOCA in the Basic Configuration and any
value is entered, the transaction will be rejected.
24) COTP POS/NEG will apply whenever DISH version 20.3 is used.
25/26) CORT/COAM: Second occurrence of these fields can only have a value when the BSP
has set to Yes the ADM/ACM SPAM in the Basic Configuration.30) NRID: The value is NR and
can only be entered whenever the ADM/ACM SPAM in Basic Configuration is set to Yes by the
BSP. Note that for SPDR/SPCR and ADMD/ACMD NRID must be blank.
*** Note that the same standard controls that apply for ADMs/ACMs will apply for SPDR/SPCR
as well in IT05, if the BSP parameter “Standard ADM/ACM form for SPDR/SPCR Issuance” is
set to Yes.
13/32) TOCA/TCTP: A TCTP value must be reported when TOCA’s value differs from zero.
Documentation code: bsplink.acdmmassloader.usermanual.2.0.57
Last changed by:
Reviewed and approved by:
BSPlink Support
Documentation Team
Reference:
Date: 26/08/2013
Page: 19 of 47
SF 00001089
IT08 – ADM/ACM Form of Payment Record
El. Format/
No. Rec.Lvl Element Description
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
to
28
29
S
S
Record Identifier
Transaction Number
First Form of Payment:
Form of Payment Account Number
S
Form of Payment Amount
S
Approval Code
S
CURRENCY TYPE
S
Extended Payment Code
S
FORM OF PAYMENT TYPE
S
Expiry Date
S
Customer File Reference
S
Credit Card Corporate Contract
S
Address Verification Code
S
Source of Approval Code
S
Form of Payment Transaction
S
Information
Authorised Amount
S
Glossary Element
Start
Reference Attribute Position
A
SPD ADM
D/C R/S D/A
M PCR CM
B
D
RCID
TRNN
1AN
6N
1
2
M
M
M
M
M
M
FPAC
FPAM
APLC
CUTP
EXPC
FPTP
EXDA
CSTF
CRCC
AVCD
SAPP
19AN
11N
6AN
4AN
2AN
10AN
4AN
27AN
1AN
2AN
1AN
8
27
38
44
48
50
60
64
91
92
94
C
M
C
M
C
M
C
C
C
C
C
C
M
C
M
C
M
C
C
C
C
C
C
M
C
M
C
M
C
C
C
C
C
FPTI
AUTA
25AN
11AN
95
120
C
C
C
C
C
C
Second Form of Payment:
S
Form of Payment Account Number
FPAC
19AN
131
C
C
C
S
Authorised Amount
AUTA
11AN
243
C
C
C
Reserved Space
RESD
2AN
M
M
M
254
Notes:
This record will be validated against IT05. It will only appear whenever the previous record is
IT05.
4) FPAM must be the same as TDAM field in IT05 for the same transaction.
6) CUTP. The 3-character ISO Currency Code and the number of decimals for that currency
must be valid for the country of issue. It must be the same value as that in IT05 for the same
transaction.
Documentation code: bsplink.acdmmassloader.usermanual.2.0.57
Last changed by:
Reviewed and approved by:
BSPlink Support
Documentation Team
Reference:
Date: 26/08/2013
Page: 20 of 47
SF 00001089
IT0G – ADM/ACM Calculation Information Record
Format/
Rec.
El.No. Lvl Element Description
1
2
3
4
5
6
7
8
9
10
S
S
S
S
S
S
S
S
S
S
11
S
12
13
14
15
16
17
18
19
20
21
S
S
S
S
S
S
S
S
S
S
Record Identifier
Transaction Number
Fare Our Calculation
Fare Your Calculation
Tax Our Calculation
Tax Your Calculation
Commission Our Calculation
Commission Your Calculation
SPAM Our Calculation
SPAM Your Calculation
Tax on Commission Our
Calculation
Tax On Commission Your
Calculation
CP Our calculation
CP Your calculation
MF Our calculation
MF Your calculation
Total Difference
Currency Type
Concerns Indicator
Dispute Indicator
Reserved Space
Glossary
Reference
Element
Attribute
Start
Position
A
D/C
M
B
RCID
TRNN
FOCA
FYCA
TAOC
TAYC
COOC
COYC
SPOC
SPYC
1AN
6N
11N
11N
11N
11N
11N
11N
11N
11N
1
2
8
19
30
41
52
63
74
85
M
M
C
C
C
C
C
C
C
C
M
M
C
C
C
C
C
C
C
C
TCOC
11N
96
C
C
TCYC
CPOC
CPYC
MFOC
MFYC
TOTD
CUTP
COIN
DIIN
RESD
11N
11N
11N
11N
11N
11N
4AN
1AN
1AN
77AN
107
118
129
140
151
162
173
177
178
179
C
C
C
C
C
C
M
C
M
M
C
C
C
C
C
C
M
C
M
M
Notes:
In general, if amounts in IT0G do not match those in IT05, the transaction will be rejected.
Nevertheless there are four more specific scenarios where IT05, IT08 and IT0G are validated:
1. no IT05, no IT08 and 1 IT0G, for those airlines that will not follow DISH. However, if there is
a difference between TAOC and TAYC within IT0G, an IT05 must be reported reflecting this
difference.
2. 1 IT05, 1 IT08 and no IT0G, for those airlines that will follow DISH.
3. 1 IT05, 1 IT08 and 1 IT0G, for those airlines that will fully use RET file format version 2.0.
4. 1 IT05, no IT08 and 1 IT0G, for those airlines that will fully use RET file format version 2.0
without IT08.
9/10) If BSP has set to Yes the ADM/ACM SPAM parameter and NRID in IT05 is NR,
SPOC/SPYC in IT0G must be different from 0.
11/12) If BSP has set to No the ADM/ACM TOCA parameter, the TCOC/TCYC will not be
applicable. Therefore, if entered, the transaction will be rejected.
SPDR/S
PCR
Documentation code: bsplink.acdmmassloader.usermanual.2.0.57
Last changed by:
Reviewed and approved by:
BSPlink Support
Documentation Team
Reference:
Date: 26/08/2013
Page: 21 of 47
SF 00001089
13/14/15/16) CPOC, CPYC, MFOC, MFYC will be allowed, whenever the parameters Handling
Fee and Penalty Charge are set to Yes by BSP. Please note that CPOC, CPYC, MFOC and
MFYC only apply when the transaction is a refund, that is, when the field COIN=R.
17) TOTD: Total difference when fields from 3 to 16 are equal to 0.
18) CUTP. The 3-character ISO Currency Code and the number of decimals for that currency
must be valid for the country of issue. It must be the same value as that in IT05 for the same
transaction.
19) COIN: I, when the transaction is concerning an issue; R when it concerns a Refund. If this
field is left blank, the system will assume that the document concerns an issue, that is, as if “I”
value has been entered. Note that this field should be reported blank for ADNT/ACNT.
20) DIIN: The DIIN field will no longer be taken into account. Its value will be considered always
as “Y”
Note that SPDR/SPCR will report an IT0G, with the same controls applied for ADMs/ACMs, only
when the BSP Basic Configuration parameter “Standard ADM/ACM form for SPDR/SPCR
Issuance” is set to Yes.
21) When the difference between IT0G.TCOC and IT0G.TCYC is not 0, it is necessary to
include an IT05 record reporting a non empty TCTP value, together with the rest of the IT05
applicable fields.
Documentation code: bsplink.acdmmassloader.usermanual.2.0.57
Last changed by:
Reviewed and approved by:
BSPlink Support
Documentation Team
Reference:
Date: 26/08/2013
Page: 22 of 47
SF 00001089
IT0H – ADM/ACM Reason for Memo Information Records
Format/
El.No. Rec. Lvl Element Description
1
2
3
4
5
6
7
8
9
10
11
12
13
14
S
S
S
S
S
S
S
S
S
S
S
S
S
S
Record Identifier
Transaction Number
Reason for Memo Line Identifier
Reason for Memo Information
Reason for Memo Line Identifier
Reason for Memo Information
Reason for Memo Line Identifier
Reason for Memo Information
Reason for Memo Line Identifier
Reason for Memo Information
Reason for Memo Line Identifier
Reason for Memo Information
Reason for Memo Issuance Code
Reserved Space
Glossary Element Start
Reference Attribute Position
RCID
TRNN
RMLI
RMIN
RMLI
RMIN
RMLI
RMIN
RMLI
RMIN
RMLI
RMIN
RMIC
RESD
1AN
6N
3N
45AN
3N
45AN
3N
45AN
3N
45AN
3N
45AN
5AN
3AN
1
2
8
11
56
59
104
107
152
155
200
203
248
253
Status
M
M
M
M
C
C
C
C
C
C
C
C
C
M
Note: The IT0H record can, depending on the TRNC (please refer to structure grid at the
beginning of this section), be repeated 99 times giving a maximum number of reason for memo
lines of 495. The 20 first lines will be displayed in the corresponding box on the BSPlink form. If
more than 20 lines are required, a hyperlink will be available in the reason for memo box in
order to open a new window containing all the reason for memo.
It will include either reason for memo or any kind of remarks when deactivating, disputing or
deleting documents.
Please be informed that decimal ASCII codes permitted are 32 to 126. Also, note that other
ASCII characters permitted in field RMIN are 128-151, 153-157, 159-165 and 225 (Ç, ü, é, â, ä,
à, å, ç, ê, ë, è, ï, î, ì, Ä, Å, É, æ, Æ, ô, ö, ò, û, ù, Ö, Ü, £, ¥, á, í, ó, ú, ñ, Ñ, ª, º, ¿, ¡, ß, Ø, ±).
Also Portuguese characters ã, Ã, õ, Õ, Ô, Ó, ~ and EURO character (€) and the at character (@)
are allowed in RMIN field.
Documentation code: bsplink.acdmmassloader.usermanual.2.0.57
Last changed by:
Reviewed and approved by:
BSPlink Support
Documentation Team
Reference:
Date: 26/08/2013
Page: 23 of 47
SF 00001089
IT0I – ADM/ACM Contact Information Record
El. Format/
No. Rec.Lvl Element Description
Glossary
Reference
Element
Start
Attribute Position Status
1
2
3
4
5
S
S
S
S
S
Record Identifier
Transaction Number
Airline Contact Name
Airline Phone/Fax Number
Airline E-Mail Address
RCID
TRNN
ACNA
ACPH
ACEM
1AN
6N
49AN
30AN
100AN
1
2
8
57
87
M
M
M
M
M
6
S
Pending Authorization Indicator
PEAU
1AN
187
C
7
S
Required Billing Period
REBP
5AN
188
C
8
S
Reserved Space
RESD
63AN
193
M
Note:
It is important to mention that in case there is no IT0I, the billing period will be the period
corresponding to the issue date + latency days.
st
3, 4, 5) ACNA, ACPH, ACEM: From October 1 2012 onwards all transactions with missing
contact information in the ACNA (Airline Contact Name), ACPH (Airline Phone/Fax Number)
and ACEM (Airline E-Mail Address) fields will be rejected. Note that these controls do not apply
to SPDRs, SPCRs, ADMDs y ACMDs issued by IATA.
6) PEAU: Y or blank, depending on whether the transaction must be reviewed by a supervisor
or not. Note that when the BSP has deactivated the options ‘Issue ADM pending authorization’
and ‘Issue ACM pending authorization’ for an airline, any document uploaded by the airline/third
party with the PEAU field set to ‘Y’ will be rejected.
7) REBP shows the period when the ADM/ACM is to be billed. This field will only consider
periods equal or greater to the issue date + latency days. In case it is not correct, i.e., the field is
null, the format is invalid (different from PMMYY, where P is the period), and so on, the system
will ignore the entered value and will consider the current date + latency days (this parameter
is set in the ‘Basic Configuration’ table, by BSP).
Documentation code: bsplink.acdmmassloader.usermanual.2.0.57
Last changed by:
Reviewed and approved by:
BSPlink Support
Documentation Team
Reference:
Date: 26/08/2013
Page: 24 of 47
SF 00001089
IT0Z – File Trailer Record
Format/
Rec.
El.No. Lvl Element Description
1
2
3
S
S
Record Identifier
Report Record Counter
Reserved Space
Glossary Element Start
Reference Attribute Position Status
RCID
RRDC
RESD
1AN
11N
243AN
1
2
13
M
M
M
Note: It is important to bear in mind that any error in this register will imply the rejection of the
file.
2.1.3
Errors Description
Once the ADM/ACM transactions are included in a RET file format version 2.0, BSPlink Centre
will process the file in order to load the content to be available in BSPlink web-based
application.
Once the file processing has finished, BSPlink Centre generates a file with the results of the
processing. This file has the following file name:
XXeiRECIPIENT_YYYYMMDD_sequence
RECIPIENT = Airline Code + check digit, if the user that previously sent the
file were an airline.
RECIPIENT= TTTuser id, if the user that previously sent the file were a Third
Party user.
This file includes the incorrect transactions, so that the user modifies and loads them again. If
everything is correct, the file informs the user about it.
The content of the “ei” file would be as follows:
Line: n TRNN: xxxxxx TRNC: xxxx TDNR: xxxxxxxxxxxxx x Record.Field
Description
Where,
n is the line number where the error is found.
TRNN is the transaction number where the error is found.
TRNC is the transaction code.
TDNR is the ticket document number including the check digit.
Record is the record id.
Field is the field within the record.
Description is the explanation about the error.
Example:
Line: 266 TRNN: 000044 TRNC: ADMB TDNR: 0996405527830 0 IT0G.TAOC/TAYC
The tax amount difference differs from the tax fee amount reported in the IT05 record.
Documentation code: bsplink.acdmmassloader.usermanual.2.0.57
Last changed by:
Reviewed and approved by:
BSPlink Support
Documentation Team
Reference:
Date: 26/08/2013
Page: 25 of 47
SF 00001089
The errors can be divided into five groups:
1. Specific errors per register and field:
IT*
Field
Type
1
RCID
2
Error
Description
1
2
The IT01 record must be the first record of the file.
The IT01 record must appear only in the first line.
SPED
1
The system provider reporting period ending date cannot be a future date.
RPSI
1
2
The reporting system identifier must be TTTT.
The reporting system identifier must be the airline code with control digit.
REVN
1
2
The handbook revision number must be 200 or 201.
The handbook revision number must be 200, 201, or 203. The whole file has been
rejected.
TRNN
1
2
The transaction numbering must be sequential.
The first transaction’s number must be 000001.
AGTN
1
2
3
4
5
6
7
8
The agent code’s control digit is not correct.
The agent does not exist.
The agency is not the one of the memo.
Agent Code is an STP and cannot accept the transaction.
The transaction has been rejected since the agent is closed.
The Transaction for a BSP Adjustment is only allowed for BSP Airlines/ Agents.
It is not possible to issue an ADM against the IATA agent code.
It is not possible to issue an ADNT against the IATA agent code.
STAT
1
2
3
4
5
6
The statistical code is not correct.
The statistical code should begin with ‘I’.
The statistical code should begin with ‘D’.
The statistical code should be ‘I’.
The statistical code should be ‘D’.
The statistical code should be ‘I ‘ or ‘D’.
TDNR
1
2
3
4
5
6
7
The 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.
There cannot be more than one transaction for the same document.
There is already a document with the indicated ticket document number.
Transaction not allowed for BSP Adjustments.
It is not possible to issue documents for the BSPlink online series.
TRNC
1
2
3
4
5
The document is not an ADM.
The document is not an ACM.
The document is disputed or deactivated.
The document is activated or disputed.
ADM cannot be disputed (it is already disputed or deactivated or out of disputing
period).
ADMs dispute cannot be rejected (it is already rejected or has not been disputed).
ADMs dispute cannot be approved (it has not been disputed).
ACM cannot be disputed (it is already disputed or deactivated or out of disputing
period).
6
7
8
Documentation code: bsplink.acdmmassloader.usermanual.2.0.57
Last changed by:
Reviewed and approved by:
BSPlink Support
Documentation Team
Reference:
Date: 26/08/2013
Page: 26 of 47
SF 00001089
09
10
11
12
13
14
15
16
17
ACMs dispute cannot be rejected (it is already rejected or has not been disputed).
ACMs dispute cannot be approved (it has not been disputed).
There are no access permissions for the transaction.
Transaction code not allowed.
Only BSP Airlines/ Agents can report BSP Adjustments.
BSP Airlines can only report BSP Adjustments transactions.
The Third Party user is not authorized to issue ADMs for this airline.
The Third Party user is not authorized to issue ACMs for this airline.
Invalid transaction code for suspended airlines.
1
2
3
4
5
6
7
The ticketing airline code must contain the airline code.
The airline does not exist.
The airline is not the owner of the document.
The Transaction for a BSP Adjustment is only allowed for BSP Airlines/ Agents.
Suspended Airline
The airline for which the document is being issued is not registered as a BSPlink user
or has expired.
Airline is not suspended
CDGT
1
The airline code’s control digit is incorrect.
ISOC
1
2
The ISO country code is incorrect.
The issue date of the refunded documents must be reported in an IT03 record.
RCID
1
2
3
An IT03 record must follow an IT02 or another IT03 record.
The IT03 record is only allowed for ADM/ACM issues (ACMB, ADMB).
There cannot be more than 70 IT03 records.
RTDN
1
2
3
A related ticket/document number has been reported more than once.
There is no airline with the code that precedes the related ticket/document number.
RTDN not allowed for this transaction type.
DIRD
1
2
3
The issue date is to be reported only in the first IT03 record of the transaction.
The issue date cannot be a future date.
Warning! Please note that this ADM is not aligned with resolution 850m as the related
document was issued more than 9 months ago.
Warning! Please note that this ADM may not be aligned with resolution 850m as some
of the related documents may have been issued more than 9 months ago.
TACN
3
4
5
RMIC
1
Reason for memo issuance code must be reported only in the first IT03 record.
RCID
1
2
3
The IT05 record is not in the correct position.
The IT05 record is only allowed for ADM/ACM issues (ACMB, ADMB).
There is only one IT05 to be reported in BSP Adjustments.
TMFT
1
2
3
4
5
6
7
‘XT’ is not an allowed tax fee type.
XF tax fee type format is not correct.
For the tax fee type reported the tax fee amount cannot be 0.
The ‘XF’ tax fee type with the total XF tax fee amount is expected to be reported.
The ‘XF’ tax fee type has already been reported.
The XF tax fee types must be reported consecutively.
There are no taxes to be reported in BSP Adjustments.
Documentation code: bsplink.acdmmassloader.usermanual.2.0.57
Last changed by:
Reviewed and approved by:
BSPlink Support
Documentation Team
Reference:
Date: 26/08/2013
Page: 27 of 47
SF 00001089
TMFA
1
2
3
4
If the tax fee amount has been reported, the corresponding tax fee type must be
reported as well.
The tax fee amount for the tax fee type XF must be 0.
If the tax difference is not equal to 0, the taxes must be reported in an IT05 record.
There are no taxes to be reported in BSP Adjustments.
TDAM
1
2
3
The ticket/document amount must be reported only in the first IT05 record.
The ticket/document amount cannot be inferior to the total tax fee amount.
A Document Amount has to be reported for a BSP Adjustment issue.
CUTP
1
2
3
4
There is no currency type.
The reported currency type differs from the one reported in the first IT05 record.
The currency will expire before the end of the billing period.
The currency is not a valid one for the airline.
TOCA
1
2
3
The tax on commission amount must be reported only in the first IT05 record.
The tax on commission amount cannot be reported.
There is no tax on commission to be reported in BSP Adjustments.
CORT
1
2
The commission rate must be reported only in the first IT05 record.
There is no commission to be reported in BSP Adjustments.
COAM
1
2
The commission amount must be reported only in the first IT05 record.
There is no commission to be reported in BSP Adjustments.
CORT
1
The supplementary commission rate must be reported only in the first IT05 record.
2
3
The supplementary commission rate cannot be reported.
If supplementary commission rate is reported, the net-reporting indicator must be set.
4
There is no commission to be reported in BSP Adjustments.
1
The supplementary commission amount must be reported only in the first IT05 record.
2
3
4
The supplementary commission amount cannot be reported.
If supplementary commission amount is reported, the net-reporting indicator must be
set.
There is no commission to be reported in BSP Adjustments.
COTP
1
2
3
4
The commission type must be reported only in the first IT05 record.
The reported commission type POS/NEG is not correct.
If the reported commission type is POS/NEG, a value for TDAM has to be reported.
If the reported commission type is POS/NEG, a commission has to be reported.
NRID
1
2
3
The net-reporting indicator must be reported only in the first IT05 record.
NR was not indicated in the IT05 record, so supplementary amount cannot be
reported.
There is no NRID to be reported in BSP Adjustments.
TCTP
1
Invalid Tax on Commission Type value
RCID
1
The IT08 record can only follow an IT05 record.
(position
199)
COAM
(2nd )
8
Documentation code: bsplink.acdmmassloader.usermanual.2.0.57
Last changed by:
Reviewed and approved by:
BSPlink Support
Documentation Team
Reference:
Date: 26/08/2013
Page: 28 of 47
SF 00001089
G
2
3
The IT08 record is only allowed in for ADM/ACM issues (ACMB, ADMB).
An IT05 record must be reported if an IT08 record is reported.
FPAM
1
The form of payment amount must be equal to the ticket/document amount reported in
the IT05 record.
CUTP
1
2
The currency type must be the same as the type reported in the IT05 record.
The currency is not a valid one for the airline.
RCID
1
2
3
The IT0G record is not in the correct position.
The IT0G record is only allowed for ADM/ACM issues (ACMB, ADMB).
A Document Amount has to be reported for a BSP Adjustment issue.
1
The fare and tax amount differ from the ticket/document amount reported in the IT05
record.
1
The tax amount difference differs from the tax fee amount reported in the IT05 record.
1
The commission amount difference differs from the commission amount reported in
the IT05 record.
FOCA
FYCA
TAOC
TAYC
TAOC
TAYC
COOC
COYC
SPOC
1
2
It is not allowed to issue ADMs/ACMs concerning issue with supplementary amount
The supplementary amount difference differs from the supplementary commission
amount reported in the IT05 record.
NR was indicated in the IT05 record, so supplementary amount must be reported.
SPYC
3
TCOC
1
TCYC
2
CPOC
CPYC
1
2
3
It is not allowed to issue ADMs/ACMs concerning refund with penalty charge amount.
It is not allowed to issue ADMs/ACMs concerning issue with CP.
The CP amount difference differs from the CP fee amount reported in the IT05 record.
MFOC
MFYC
1
2
3
It is not allowed to issue ADMs/ACMs concerning refund with handling fee amount.
It is not allowed to issue ADMs/ACMs concerning issue with MF.
The MF amount difference differs from the MF fee amount reported in the IT05 record.
TOTD
1
The total difference must be 0.
CUTP
1
2
The currency type must be the same as the type reported in the IT05 record.
The currency is not a valid one for the airline.
COIN
1
Value not allowed.
It is not allowed to issue ADMs/ACMs concerning issue with tax on commission
amount.
The tax on commission amount difference differs from the tax on commission amount
reported in the IT05 record.
Documentation code: bsplink.acdmmassloader.usermanual.2.0.57
Last changed by:
Reviewed and approved by:
BSPlink Support
Documentation Team
Reference:
Date: 26/08/2013
Page: 29 of 47
SF 00001089
H
RCID
1
2
3
RMLI
1
2
3
4
I
Z
The IT0H record is not in the correct position.
Only one IT0H allowed for the following transactions: ACDB, ACJB, ACWB, ACSB,
ADDB, ADJB, ADWB, and ADSB.
No IT0H allowed in the following transactions: ACRB, ADRB.
The reason for memo line identifier cannot be 0, if reason for memo information has
been reported in the corresponding line.
The reason for memo line identifier numbering must be consecutive.
The maximum reason for memo line identifier cannot exceed 10.
A reason for memo line identifier equal to 0 has been reported, so no more IT0H
records can be reported.
RCID
1
2
3
Only one IT0I record allowed in a transaction.
The IT0I record is only allowed for ADM/ACM issues (ACMB, ADMB).
No IT0I record has been reported.
ACNA
1
The name of the contact has not been reported.
PEAU
1
2
There are no access permissions for the transaction.
BSP Adjustments cannot be issued pending authorization.
ACPH
1
The telephone number of the contact has not been reported.
ACEM
1
The email address of the contact has not been reported.
RCID
1
2
The IT0Z record must be the last record in the file.
The IT0Z record must be reported.
RRDC
1
The report record counter differs from the number of reported records.
2. Errors that may affect several registers at the same time:
IT*
Field
Type
1
SPED
PRDA
2
Error
Description
2
The date is not a valid calendar date.
DAIS
3
DIRD
8
EXDA
I
REBP
5
N.A
Documentation code: bsplink.acdmmassloader.usermanual.2.0.57
Last changed by:
Reviewed and approved by:
BSPlink Support
Documentation Team
Reference:
Date: 26/08/2013
Page: 30 of 47
SF 00001089
8
N.A
G
N.A
1
2
3
4
The remittance data is inconsistent for an ADM concerning an issue.
The remittance data is inconsistent for an ACM concerning a refund.
The remittance data is inconsistent for an ACM concerning an issue.
The remittance data is inconsistent for an ADM concerning a refund.
3. Errors common to all registers that do not refer to specific fields:
Error
1
2
3
4
5
6
Description
Empty 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.
The record is not in the correct format.
4. Errors while checking the file and transaction format:
Error
1
2
3
4
5
6
7
8
9
10
Description
The transaction cannot be processed.
The IT03 is only allowed for issuance transactions (ACMB, ADMB).
The record is not in the correct transaction.
The reported transaction number is not correct.
There cannot be more than 70 IT03 records.
An IT05 or IT0G record must be reported for ADM/ACM issues.
An IT08 record must be reported if there is no IT0G record.
No more than two IT0H are allowed for the dispute reason.
No more than 99 IT0H are allowed for the reason for memo.
An IT05 must be reported for BSP Adjustment issues.
5. Errors that check the file name and certain tables in database:
Error
1
2
3
2.2
Description
The file was not reported by an active BSPlink user.
The periods are not correctly configured by your BSP.
The transaction cannot be carried out, because its billing period is over.
Download ADM/ACM Files version 2.0
Users will be able to download the modifications carried out on the different transactions and
their corresponding attachments via the BSPlink web-based application. This means that
modifications carried out in transactions via the Mass Loader version 2.0 will not be taken into
account in the downloadable file.
The file name is as follows:
XXehRECIPIENT_YYYYMMDD.zip
Documentation code: bsplink.acdmmassloader.usermanual.2.0.57
Last changed by:
Reviewed and approved by:
BSPlink Support
Documentation Team
Reference:
Date: 26/08/2013
Page: 31 of 47
SF 00001089
Where,
eh is the file descriptor that identifies these files.
RECIPIENT refers to the airline code plus the check digit.
Note that this file will contain file XXehRECIPIENT_YYYYMMDD with the following
transactions: ADM/ACM, ADM/ACM Requests, Minor Adjustment Notices (MAN) Debit/Credit,
and BSP Adjustments: SPDR/SPCR and ADMD/ACMD, also, note that the attachments within
the file will be included in folders named after the transaction number they belong to. (See test
file VVehXXXD_20041209.ZIP attached to this manual).
The generation of the downloadable files will depend on certain parameters that should be
configured by the airline user. Please, refer to 2.2.1 Basic Configuration for ADMs/ACMs
downloaded in RET format v.2.0 for further information.
If so decided by the airline, these files are automatically generated everyday including all the
modifications carried out via BSPlink web-based application. The file will include all the
modifications made in each transaction during the day. However, if the last modification has
been the deletion of the transaction (TRNC = ADW/ACW), the rest of modifications will not be
included. The transaction information will be that at the moment of the file generation. For
example, if the originally issued document amount is modified during the same day the
ADM/ACM was issued, the amount included in the file would be that of the modification.
These files can be retrieved in three different ways:
- Via the Download Files option, where they will appear together with all the other files the
airline received.
- Via the Download ADM/ACM Files option, where only the ADM/ACM files generated by the
BSPlink system will appear.
- For enhanced airlines, also using an SFTP client, whenever they have activated an SFTP
account via the Mass Download Secure FTP Account (just one account per airline, managed by
any enhanced user or sub-user) or Secure FTP Account (available for the main user) options.
In case a file is attached to a transaction when modifying or issuing it, the “eh” file will also
include the attached files.
In case of ADM/ACM disputes (TRNC=ADPB/ACPB), an IT0I record will also be included in the
“eh” files whenever there is any Airline contact information available or if there is any document
attached at the time of dispute. The presence of the attached document would be indicated
through a flag indicator “A” in the position 193 of IT0I.
2.2.1
Basic Configuration for ADMs/ACMs downloaded in RET format v.2.0
The downloadable files are automatically generated on a daily basis whenever the value of one
of the following parameters in the Basic Parameters for airlines is set to Yes:








Daily download of ADMs/ACMs issued online
Daily download of ADMs/ACMs issued by BSP on behalf of the airline
Daily download of status changes made online
Daily download of online disputed ADMs/ACMs
Daily download of ADM/ACM requests
Daily download of Minor Adjustment Notices
Daily download of ADNT/ACNT status changes made online.
Documentation code: bsplink.acdmmassloader.usermanual.2.0.57
Last changed by:
Reviewed and approved by:
BSPlink Support
Documentation Team
Reference:
Date: 26/08/2013
Page: 32 of 47
SF 00001089
There is another parameter within the Basic Parameters for airlines that will affect the content of
the “eh” file:
 Download Attachments? To decide whether the “eh” file includes the files attached to
the issued documents or not.
The “eh” file will contain the transactions within one of the categories above whenever they
have the value Yes configured.
Documentation code: bsplink.acdmmassloader.usermanual.2.0.57
Last changed by:
Reviewed and approved by:
BSPlink Support
Documentation Team
Reference:
Date: 26/08/2013
Page: 33 of 47
SF 00001089
2.2.2
Technical Description
ADM/ACM RET File Structure version 2.0 – Download
Record
IT01
IT02
IT03
IT05
IT08
IT0G
IT0H
IT0I
IT0Z
Description
File header
Basic sale
transaction
record
Related
ticket/docume
nt information
record
Monetary
amount
record
Form of
payment
record
ADM/ACM
calculation
information
record
ADM/ACM
reason for
memo
information
record
ADM/ACM
airline contact
information
record
File trailer
Transaction Type
A
D/
C
M
B
A
D/
C
M
Q
S
S
A
D/
C
A
D/
C
P
B
AD/
CDB
AD/
CDT
AD/
CJ
B
1
1
1
1
1
1
1
1
1
1
1
1
(070)
(070)
(070)
n/a
n/a
(1n)
(1n)
(1n)
n/a
1
1
1
1
1
(099)
6
AD/
CR
B
AD/
CR
T
1
1
AD/C
WB
AC/D
WT
AD/C
SB
AD/C
ST
A
D/C
P
N
AD/C
SB
SPD
R/SP
CR
SP
DR
/SP
CR
***
ADMD/
ACMD
1
1
1
1
1
1
1
1
1
1
1
1
1
1
n/a
(070)
n/a
n/a
n/a
n/a
(070)
(070)
(0-70)
n/a
n/a
(1n)
n/a
n/a
(1n)
(1-n)
1
(1n)
1
n/a
n/a
n/a
1
n/a
n/a
1
n/a
1
1
1
1
n/a
n/a
n/a
1
n/a
n/a
1
n/a
C
1
n/a
(099)
(099)
(03)
(0-1)
(01)
(099)
(0-1)
(0-1)
(099)
n/a
(099)
(099)
(0-99)
1
1
1
(01)
n/a
n/a
1
n/a
n/a
1
n/a
(0-1)
1
(0-1)
1
1
1
1
1
1
1
1
1
1
1
1
1
1
6
These codes will correspond to the TRNC in IT02: ADMB: ADM Issue; ADMQ: ADM Request; SSAD:
Minor Adjustment Notice (MAN) Debit; ADPB: ADM Dispute; ADJB: Reject an ADM Dispute; ADSB:
Approve an ADM Dispute; ADDB: Deactivate ADM/SPDR/ADMD; ADRB: Reactivate ADM/SPDR/ADMD;
ADWB: Delete ADM/SPDR/ADMD; ACMB: ACM Issue; ACMQ: ACM Request; SSAC: Minor Adjustment
Notice (MAN) Credit; ACPB: ACM Dispute; ACJB: Reject an ACM Dispute; ACSB: Approve an ACM
Dispute; ACDB: Deactivate ACM/SPCR/ACMD; ACRB: Reactivate ACM/SPCR/ACMD; ACWB: Delete
ACM/SPCR/ACMD, ADNT: Non-ticket related debit Issue, ACNT: Non-ticket related credit Issue, ADPN:
Non-ticket related debit document dispute, ACPN: Non-ticket related credit document dispute, ADDT:
Deactivate ADNT, ACDT: Deactivate ACNT, ADRT: Reactivate ADNT, ACRT: Reactivate ACNT, ADWT:
Delete ADNT, ACWT: Delete ACNT, SPCR: Settlement Plan Credit issue, SPDR: Settlement
Plan Debit issue, ADMD: Agent Debit Memo Default issue, ACMD: Agent Credit Memo Default
issue.
Documentation code: bsplink.acdmmassloader.usermanual.2.0.57
Last changed by:
Reviewed and approved by:
BSPlink Support
Documentation Team
Reference:
Date: 26/08/2013
Page: 34 of 47
SF 00001089
*** Note that the same standard controls that apply for ADMs/ACMs will apply for SPDR/SPCR
if the BSP parameter “Standard ADM/ACM form for SPDR/SPCR Issuance” is set to Yes.
Please, refer to 2.1.2 Technical Description for further information about the different records.
There are, however, certain differences in the content of some records:


IT01: RPSI field is EARS.
IT03: It will only contain information whenever there are related documents.
3 Upload Attached Files to BSPlink ADM/ACM
Transactions
Airlines and Third Parties can send files to be attached to the uploaded ADM/ACM transactions.
The files to be attached can either be sent before or after the ADM/ACMs are uploaded and are
matched to the ADM/ACMs via the document number. All attached files must be zipped.
The file naming convention for these files is:
XXevRECIPIENT_YYYYMMDD_ACDMnumber[_TTT + Third Party User Id][.
Extension].zip
where,
ev is the file descriptor that identifies this attached documents.
RECIPIENT is the airline code plus the check digit of the airline the ADM/ACM
belongs to.
ACDMnumber is the ADM/ACM number to which the “ev” file will be attached.
[_TTT + Third Party User Id] only applicable when the sender is a Third Party
user. In such case, TTT plus the Third Party user identification should be added
to the file name.
[.extension]: although the ev file is a .zip file, the user may enter any additional
extension in the file name, if so required (.doc.zip, .pdf.zip, .xls.zip ...).
These files are sent via the Upload ACM/ADM Files option within the user’s main menu. If the
airline and Third Party users sending these files have an active SFTP account, they will also be
able to send “ev” files via SFTP.
Only one “ev” file per transaction is allowed per upload date. If the user sends a file with the
same name as the name of another file already uploaded, the second file will overwrite the first
one. Likewise, if the file has been sent via SFTP and the name is not correct or the file
extension is not “zip” in lower case, the file will be moved to the BAD_FILES folder, meaning
that the file has not been processed and that the user will have to rename the file and upload it
again. Files contained in the BAD_FILES folder will be erased after two months.
Please note that “ev” files can be sent within an “ez” file. In this case, if the “ev” file is uploaded
via SFTP within an “ez” file and the “ev” file name is incorrect, an “e2” file will be generated
informing the user about it.
Once an ADM/ACM is available in BSPlink (correctly processed via mass upload, or issued
through BSPlink), the “ev” file sent for this ADM/ACM is linked to the transaction by means of a
hyperlink in the reason for memo field of the online form.
Documentation code: bsplink.acdmmassloader.usermanual.2.0.57
Last changed by:
Reviewed and approved by:
BSPlink Support
Documentation Team
Reference:
Date: 26/08/2013
Page: 35 of 47
SF 00001089
Note that “ev” files are not available in the Download Files option in the airline’s main menu but
remain accessible via the hyperlink on the memo nine (9) months.
Note as well that Zip compressed files can be managed with free programs such as ‘7-zip’ from
http://www.7-zip.org
Documentation code: bsplink.acdmmassloader.usermanual.2.0.57
Last changed by:
Reviewed and approved by:
BSPlink Support
Documentation Team
Reference:
Date: 26/08/2013
Page: 36 of 47
SF 00001089
4 Annex 1: Mapping/Cross References
4.1
ADM/ACM Form based on an issue
Documentation code: bsplink.acdmmassloader.usermanual.2.0.57
Last changed by:
Reviewed and approved by:
BSPlink Support
Documentation Team
Reference:
Date: 26/08/2013
Page: 37 of 47
SF 00001089
Documentation code: bsplink.acdmmassloader.usermanual.2.0.57
Last changed by:
Reviewed and approved by:
BSPlink Support
Documentation Team
Reference:
Date: 26/08/2013
Page: 38 of 47
SF 00001089
4.2
ADM/ACM Form based on a refund
Documentation code: bsplink.acdmmassloader.usermanual.2.0.57
Last changed by:
Reviewed and approved by:
BSPlink Support
Documentation Team
Reference:
Date: 26/08/2013
Page: 39 of 47
SF 00001089
Note: The ADM/ACM number will be taken from the TDNR (IT02) regardless of the ADM/ACM
Capture Mode.
Documentation code: bsplink.acdmmassloader.usermanual.2.0.57
Last changed by:
Reviewed and approved by:
BSPlink Support
Documentation Team
Reference:
Date: 26/08/2013
Page: 40 of 47
SF 00001089
5 Annex 2: Sample Files in RET File Format version 2.0
Please, see included sample files BSPLINK.EC_EISAMPLEFILES.ZIP, VVehXXXD_20041209.ZIP and
VVevXXXD_20041210_6450000001.ZIP.
Documentation code: bsplink.acdmmassloader.usermanual.2.0.57
Last changed by:
Reviewed and approved by:
BSPlink Support
Documentation Team
Reference:
Date: 26/08/2013
Page: 41 of 47
SF 00001089
6 Revision Control Chart
Revision Nº
2.0
Issue date
29/06/04
Changes
Manual updated with the new download and upload file
formats (version 2.0).
Section 1, e-mail notification about errors in “ed” and “ec”
files note added at the end of the section.
2.0.1
27/07/04
Section 4.4.1, new parameter included in the Basic
Parameters for airlines.
Section 4.2.2, scenario 4 updated.
Section 4.2.2, fields 19 and 20 in IT0G updated.
Section 4.2.2, note added at the beginning of IT0I
description.
Section 5, ev file information updated.
2.0.2
31/08/04
Section 4.3, the “eh” file now includes a record of all the
modifications carried out during the same day.
2.0.3
28/09/04
Section 5, note added at the end of the section to indicate
that files are available for two months.
2.0.4
30/11/04
Section 1, the options to find the ei file has been added.
Section 2.1.2, note added to IT03 in AD/CMB
transactions.
Section 2.2.1, Free Stat field modified to be easily
understood.
Section 2.2.2, IT01, note added about the rejection of the
file.
Section 2.2.2, IT01, note added to SPED field about the
billing period.
Section 2.2.2, IT02 – TRNN note added.
Section 2.2.2, IT02 – STAT field modified to be easily
understood.
Section 2.2.2, IT03, note 4 added to DIRD field.
Section 2.2.2, IT0G, note added to DIIN field.
Section 2.2.2, IT0I, note added to REBP field when
dealing with ADM billing period.
Section 2.2.2, IT0Z, note added about the rejection of the
file.
Section 2.2, the options to find the eh file have been
added.
2.0.5
28/12/04
Section 2.1.1, new parameter added in Basic
Configuration for BSP: Duplicated ADM/ACM Numbers
2.0.6
25/01/05
Section 2.1.2, IT0H updated for ADPB transactions (0-2)
Section 2.1.3, error list added.
2.0.7
22/02/05
Section 2.1.1, new parameter added to BSP Basic
configuration, related to controls and validations over STP
agents.
2.1.3, new errors: 1 added to IT01 – REVN; 4 to IT02 –
Documentation code: bsplink.acdmmassloader.usermanual.2.0.57
Last changed by:
Reviewed and approved by:
BSPlink Support
Documentation Team
Reference:
Date: 26/08/2013
Page: 42 of 47
SF 00001089
AGTN and 8 to IT02 – TRNC.
New section 3 about the pure RET file format.
2.0.8
29/03/05
Section 2.1.1, BSP parameter about non-disputable ADMs
modified to include the ACM dispute.
Section 2.1.2, ADM/ACM File Structure Chart updated to
include new TRNC related to ACM dispute.
Section 2.1.2, IT02 – TRNC; IT0G – DIIN; IT0I – REBP
fields updated to include ACM dispute.
Section 2.1.3, new errors added: IT02 – TRNC: 9, 10, 11;
IT0G – DIIN: 2.
Section 2.1.3, IT0H – RCID: error 2 updated.
Section 2.2.1, Daily download of online disputed ADMs
parameter changed to Daily download of online disputed
ADMs/ACMs.
Section 2.2.2, ADM/ACM File Structure Chart updated to
include new TRNC related to ACM dispute.
2.0.9
26/04/05
Document review to change ACM/ADM for ADM/ACM.
Section 1, note 2 added to SFTP.
References to FTP server to SFTP.
2.0.10
31/05/05
2.0.11
28/06/05
Section 2.1.2, the note before the register description has
been updated.
Section 2.1.2, IT02 – TDNR updated to point out the
possibility of duplicate transactions for different airlines
when the user sending the file is a Third Party user.
Section 1 updated to include the new E-mail alert
Successful Mass Upload.
Section 2.1.1, paragraph Non-Disputable ADMs
parameter of the BSP Basic Configuration has been
eliminated.
Section 2.1.2, IT0G record table: field DIIN has been
updated to ‘M’ (Mandatory) in column AD/CMB
Section 2.1.2., IT0G – Note 20 (DIIN) updated to eliminate
the reference to Non-Disputable ADMs setting of BSP
Basic Configuration.
Section 2.1.2, IT0I – Note 7 (REBP) updated to eliminate
the reference to Non-Disputable ADMs setting of BSP
Basic Configuration
Section 2.1.2, page 10, comment added to paragraph
Note to inform that records, if present, cannot be blank
due to numeric and mandatory status.
Section 2.1.3, errors deleted: IT0G – DIIN: 1 and 2.
2.0.12
26/07/05
Section 4, extension zip always in lower case in ev files.
Section 2.1.2, note added to TMFT field in IT05 record.
2.0.13
25/10/05
Section 1 Global Overview: Footnote 2 has been modified.
Section 4 Upload Attached Files to BSPlink ADM/ACM
Transactions: comment related to File Naming Convention
has been modified (extension). Also a note has been
added at the end of this section related to Zip compressed
files.
Documentation code: bsplink.acdmmassloader.usermanual.2.0.57
Last changed by:
Reviewed and approved by:
BSPlink Support
Documentation Team
Reference:
Date: 26/08/2013
Page: 43 of 47
SF 00001089
2.0.14
29/11/05
Section 1 Global overview: a comment has been added
with reference to ADM/ACM files with incorrect names
uploaded through sFTP.
Section 1 Global overview: a comment has been added to
the Semantic errors paragraph to inform that if activated
the Email Alert parameter Errors in mass upload file, the
Airline/Third Party will receive an e-mail with the names of
‘eq’ and ‘e2’ files generated, if any.
Section 2.1.2 Technical Description. For IT02 record, a
note has been added with reference to DAIS field.
Section 3 Upload Attached Files to BSPlink ADM/ACM
Transactions: a comment has been added to indicate that
‘ev’ files can be sent within an ‘ez’ file.
Section 3: Pure RET file format. A note has been added
with reference to DAIS field.
2.0.15
31/01/06
Section 2.1.2 Technical Description: a note has been
removed with reference to field DIRD in IT03 record to
indicate that this field is now conditional for all countries.
Section 3 Upload Attached Files to BSPlink ADM/ACM
Transactions: this section has been updated to indicate a
comment about “ev” files and “ez” files containing “ev” files
sent through sFTP.
2.0.16
28/02/06
Section 2.2 Download ADM/ACM Files version 2.0: A note
has been added to mention the transactions that can be
contained in eh files.
Section 2.2.2 Technical Description: the ADM/ACM RET
File Structure version 2.0 – Download Table has been
updated with ADM/ACM Requests and Debit/Credit MAN
transaction types.
2.0.17
28/03/06
Section 1 Global overview and section 3 Upload Attached
Files to BSPlink ADM/ACM Transactions: a comment has
been added with reference to the BAD_FILES folder.
Section 2.1.1 Basic Configuration Table for ADMs/ACMs
loaded in RET format v.2.0: For BSP parameters, the
comment with reference to ADM/ACM Latency Days
parameter has been updated.
Section 2.1.2 Technical Description: In IT01, the note
about SPED field has been modified. In IT02 table, the
note about DAIS field has been modified, a comment has
been added to Note 8 (TDNR), and a note has been
added for field TRNC. In IT0G table, the note about DIIN
field has been modified. In IT0I table, the note about
REBP has been modified and a comment has been added
to Note 6 (PEAU).
Section 2.1.3 Errors Description: in Table 1, error 6 has
been added for TDNR field (IT02), error 12 has been
added for TRNC (IT02), and error 1 has been added for
PEAU field (IT0I).
Section 3.1: Error 2 has been added to TRNC (IT02).
Errors Description in pure RET file format – error 2.
2.0.18
25/04/06
Section 2.1.2 Technical Description: In IT02 table, the
Documentation code: bsplink.acdmmassloader.usermanual.2.0.57
Last changed by:
Reviewed and approved by:
BSPlink Support
Documentation Team
Reference:
Date: 26/08/2013
Page: 44 of 47
SF 00001089
comment for TDNR field has been modified.
Section 2.1.3 Errors Description: in Table 1, error 6 has
been removed for TDNR field (IT02).
2.0.19
30/05/06
Section 2.1.2 Technical Description: In IT0G table, a
comment has been added to the note corresponding to
elements 13/14/15/16 (CPOC, CPYC, MFOC and MFYC).
Section 2.1.3 Errors Description: the text of the following
error message number 2 for register RCID has been
updated for IT03, IT05, IT08, IT0G and IT0I records.
Section 2.1.2 Technical Description: In IT02 table, a
comment has been added for TACN field. In IT0I table, a
comment has been added for fields ACNA, ACPH and
ACEM.
2.0.20
27/06/06
2.0.21
25/07/06
Section 2.1.2 Technical Description:
 In IT02 register, a comment has been added for
AGTN field.
 In IT0G register, note added to the first comment in
the general note.
 In IT0H register, extended ASCII characters permitted
for RMIN field have been added.
Section 2.1.3 Errors Description: a warning message has
been added for AGTN field in IT02 register.
2.0.22
29/08/06
Section 2.1.2 Technical Description: new characters
allowed in RMIN field in IT0H.
2.0.23
26/09/06
2.1 A comment has been added informing that the sender
id is case sensitive in case of third party.
2.1.2 Technical Description: In IT0G table, a comment has
been modified corresponding to elements 13/14/15/16
(CPOC, CPYC, MFOC and MFYC).
2.0.24
31/10/06
2 Basic Configuration Table for ADMs/ACMs loaded in
RET format v.2.0: A comment has been added to explain
SPDR and SPCR transactions.
2.0.25
30/11/06
2.2 Download ADM/ACM Files version 2.0: A comment
has been added to explain that IT0I for disputed
transactions could also be present in ‘eh’ files.
2.0.26
22/12/06
Section 4 Attachments: Change of wording in the
introduction in sake of clarity.
2.0.27
30/01/07
Section 2.1.3 Errors Description: Updated the warning
message for the field AGTN.
2.0.28
30/04/2007
New transaction codes ADNT/ACNT added in Sections
2.1.2, 2.1.3, 2.2.1 and 2.2.2.
2.0.29
31/07/2007
The handbook revision number must be 200 or 201.
2.0.30
25/09/2007
New transaction codes ADPN/ACPN added in section
2.2.2
Documentation code: bsplink.acdmmassloader.usermanual.2.0.57
Last changed by:
Reviewed and approved by:
BSPlink Support
Documentation Team
Reference:
Date: 26/08/2013
Page: 45 of 47
SF 00001089
Global overview: Reference to version 1.01 deleted.
2.0.31
30/10/2007
Element RMIC added in record IT0H under section 2.1.2
2.0.32
27/11/2007
General Revision.
Added new TRNC related to ADCNT in Section: 2.1.2 and
Section 2.2.2
2.0.33
28/02/2008
Added Note 10.2 in IT02 Record description about
disputes.
2.0.34
29/07/2008
New fields on “ei” file: TRNC & TDNR added on Section
2.1.3.
2.0.35
22/09/2008
Section 1 Global overview: Language file revision
Section 2 RET file format Version 2.0: Language file
revision.
Section 2.1.1 With in User Administration – User
Maintenance option: Removed.
Section 2.0, 2.1.and 2.2.2: New transaction codes,
SPDR/SPCR, ADMD/ACMD added.
New notes added to AGTN, TDNR, TACN and NRID
concerning SPDR/SPCR, ADMD/ACMD.
Section 2.1.3 – 1 Errors Description: New errors added
concerning SPDR/SPCR, ADMD/ACMD in IT0G, IT02,
IT05 and IT0I.
Section 2.1.3 – 4 Errors while checking the file and
transaction format: New error added concerning IT05.
Section 4 Upload Attached Files to BSPlink ADM/ACM
Transactions, Language file revision.
Section 7 Revision Control Chart 2.0.4: language file
revision.
2.0.36
27/10/2008
Section 2.1.2 Technical Description:
ADM/ACM RET File Structure version 2.0 – Inclusion of
SPDR/SPCR*** and a note
IT05 – Inclusion of SPDR/SPCR*** and a note
IT0G – Inclusion of SPDR/SPCR*** and a note
Section 2.2.2 Technical Description ADM/ACM RET File
Structure version 2.0 – Download: Inclusion of
SPDR/SPCR*** and a note.
2.0.37
30/01/2009
2..0.38
23/07/2009
Section 1 Global Overview: P4
Note on upper case conversion.
2.1.2 Technical Description: ADCM RET structure,
removing SPDCR, ADCMD,
ADCNT. Correction of accepted TRNC.2.2.1 Basic
Configuration
for ADCM downloaded in RET v 2.0: removed daily
download of disputed non-ticket
debits and credits. Removing of SPDCR, ADCMD,
ADCNT as TRNC. Correction of accepted TRNC
2.0.39
07/09/2009
1 Specific error per register and field: 2 new errors added
to the field TACN: Suspended Airline / The airline for
which the document is being issued is not registered as a
Documentation code: bsplink.acdmmassloader.usermanual.2.0.57
Last changed by:
Reviewed and approved by:
BSPlink Support
Documentation Team
Reference:
Date: 26/08/2013
Page: 46 of 47
SF 00001089
BSPlink user or has expired. 2.2.2 Technical Description:
removal of duplicated column (ADCPN).
Errors that may affect several registers at the same
time: Removing of “The year is not in the allowed range
(20-40)” error since it does no longer apply.
2.0.40
30/11/2009
2.0.41
18/01/2010
1 Global Overview, 2.2 Download ADM/ACM Files
version 2.0: Renaming the option from ‘ADM/ACM Secure
FTP Account’ to ‘Mass Download Secure FTP Account’
2.0.42
06/04/2010
2.1.1 Basic Configuration Table for ADMs/ACMs loaded
in RET format v.2.0. 2 BSP: note on not having latency
days for SPCDR.
2.1.2 Technical Description, IT05– Monetary Amounts
Record, including note on TCTP related to TOCA (p19).
2.1.3 Errors Description, specific errors per register and
field; new error added to IT05 TCTP (p28).
2.0.43
01/06/2010
2.0.44
19/07/2010
2.1.2 Technical Description, IT05– Monetary Amounts
Record, (p19) including carrier service fees tax
information, and a note on a need for an IT05 when the
difference between IT0G.TCOC and IT0G. TCYC differs
from 0. (p22)
3.1. Added errors related to issuance of ADMs or ADNTs
to IATA’s agent.
2.1.3 (1). Specific errors per register and field: Adding new
error ‘AGTN’ related to agent’s being closed and removing
old warning about document maybe rejected due to
location being closed (p26).
26/10/2010
2.0.45
30/01/2011
Modified note 3 on IT02.AGTN:The transaction will be
rejected if the agent is not active in the agent’s master
table.
2.1.2 IT03, including RMIC plus footnote (p16) and note
24 on (p18) related to COTP.
2.1.3 Specific errors per register and field: Adding new
errors pertaining to DISH 20.3 (REVN p25, 34), (RMIC
p26), (COTP p27).
2.0.46
20/04/2011
2.0.47
18/07/2011
2.0.48
20/12/2011
2.0.49
20/03/2012
2.0.50
20/04/2012
4 Upload Attached Files to BSPlink ADM/ACM
Transactions: Storage period upgraded to 9 months.(p35)
2.1.1 Basic Configuration Table for ADMs/ACMs loaded in
RET format v.2.0:Third Party authorization (p9).
1.Specific errors per register and field: errors related to
Third Party authorization (p26).
Basic Configuration Table for ADMs/ACMs loaded in RET
format v.2.0: CP/MF Airline configuration.
2.1.3 (1). Specific errors per register and field: Adding new
errors related to airline suspension.
2.1.3 (1). Specific errors per register and field: Adding new
errors related to secondary currency.
4 Upload Attached Files to BSPlink ADM/ACM
Transactions, informing that the ‘ev’ files can be uploaded
Documentation code: bsplink.acdmmassloader.usermanual.2.0.57
Last changed by:
Reviewed and approved by:
BSPlink Support
Documentation Team
Reference:
Date: 26/08/2013
Page: 47 of 47
SF 00001089
2.0.51
20/07/2012
2.0.52
24/09/2012
2.0.53
16/10/2012
2.0.54
19/12/2012
2.0.55
12/02/2013
2.0.56
25/03/2013
2.0.57
26/08/2013
thru the Upload ACM/ADM Files (p34).
2.1.3 (1). Specific errors per register and field: Adding
warning on resolution 850m regarding 9 months of final
travel date and IT0I contact information.
2.1.3 (1) Specific errors per register and field: Errors on
resolution 850m 1 and 2. 2.1.2 Technical Description IT0I
mandatory.
Removing PURE RET file format information since it is no
longer accepted. 2.1.3 (1) Specific errors per register field:
Updating DIRD errors by removing ‘The issue date must
be reported.’
IT0I ADM/ACM Contact Information Record: Exclude IATA
internal transactions from IT0I validations (p23).
2.1.2 STAT, TRNC and TMFTs fields only accept
uppercase letters. The PXNM field is converted to
uppercase letters.
2.1.2 Technical descriptions: IT0H records for remark:
adding new accepted characters (p22)
2.1.2 Adding element 18 RCPN