Professional Documents
Culture Documents
Application :
With effect from 1 May 2002
Railway undertakings (RUs) that bring their tickets to account in accordance with point 3 of UIC Leaflet
301-1 and that wish to adopt the "shares apportioned" accounting standard, and RUs that bring their
tickets to account in accordance with point 4 of UIC Leaflet 301-1 and that wish to apply electronic
accounting procedures, must do so using the message described in this leaflet and with effect from
1.5.2002 at the earliest*. They may not use the messages described in UIC Leaflets 301-0 or 301-1.
RUs that bring their "reservation", "ticket + reservation" and "ticket" issues to account using the mes-
sage specified in UIC Leaflets 301-0 or 301-2 must bring these documents to account using the mes-
sage specified in UIC Leaflet 301 under the following conditions:
- from 1.5.2002 at the earliest*
- by 1.12.2002 at the latest.
Consequently, all RUs must be able to accept the accounting message format specified in this leaflet
with effect from 1.5.2002**.
* exceptionnally the RUs RENFE and FS may apply the provisions of the present leaflet from 1.1.2002
** as from 1.1.2002 for messages received from the RUs RENFE and FS
Record of updates
1st edition, December 2002 First issue
The person responsible for this leaflet is named in the UIC Code
301
O
Contents
Summary ..............................................................................................................................1
301
O
2.8.1 - Despatch of statements ................................................................................... 13
2.8.2 - Request for information about the statement................................................... 13
2.8.3 - Keeping of accounting data ............................................................................. 14
2.9 - Delay in the compilation of statements of account ............................................. 14
2.9.1 - General provisions ........................................................................................... 14
2.9.2 - Measures to be applied in the event of delays exceeding three months
(major delays) .................................................................................................. 14
2.10 -Measures to prevent and combat travel document fraud................................... 16
2.10.1 - General ............................................................................................................ 16
2.10.2 - Checks required ............................................................................................... 16
2.10.3 - Request for tickets collected by destination RUs ............................................. 16
2.10.4 - Comparison of refunded tickets ....................................................................... 16
2.10.5 - Reporting of anomalies .................................................................................... 16
301
O
4.5 - Provision of data by the issuing RU.................................................................... 26
301
O
Appendix H - Conditions regarding compilation of advice notes -
General checklists ...................................................................................... 94
H.1 - Structure of the advice note - Checklist .............................................................. 95
H.2 - Example of how to complete an advice note ...................................................... 96
H.3 - Example of how to complete a general checklist................................................ 97
Glossary ...........................................................................................................................116
Bibliography .....................................................................................................................119
301
O
Summary
The regulations set out in UIC Leaflet 301 define the provisions to be applied between railway
undertakings (RUs) for bringing to account international passenger traffic services when an RU other
than the RU receiving the request from the passenger is involved either as a service-providing RU or
as an allocating RU.
- allocated or cancelled during the month in question, in the case of accounting upon allocation,
- sold or cancelled during the month in question, in the case of accounting upon issue,
- collected during the month in question, for accounting based on collected tickets.
The RU that compiles the statement of account, whether on allocation, on issue or on the basis of
collected tickets, is required to apportion to the RUs involved the shares to which they are entitled
based on all the travel documents processed. It shall send the statement to the RUs concerned by the
following deadlines at the latest:
- the 20th of the month following the statement month (month of issue, allocation or cancellation)
for all services (tickets or supplements) issued and brought to account by electronic means and
for all services (tickets or supplements) allocated electronically,
- the 10th of the third month following the statement month for all other travel documents.
Electronic accounts data may be exchanged using the IT media listed in point G.1 to this leaflet.
1 301
O
1 - Purpose of the leaflet
1.1 - General
These regulations define the provisions that apply between RUs (see List of abbreviations - page 118)
for bringing to acc ount amounts relating to passenger services when an RU, other than that which
receives the passenger's request, is involved either as a service-provider (see Glossary - page 116)
or as an allocator (see Glossary - page 116).
- reservations for seats including payment of a supplement, for couchette berths and sleeper
berths,
- supplements for the use of certain trains, sold without seat reference allocations,
- services provided by companies other than RUs (catering, boat, taxi, car without chauffeur, hotel)
which are included in an RU's electronic seat "product" range.
- seated accommodation when only the reservation fee is payable or when the reservation fee is
payable in addition to a supplement. The reservation charge is not shared out and remains with
the RU to which it was paid.
1.2.1 - On allocation
- Services for which a seat/berth reference has been allocated using an electronic reservations
system,
- tickets the price of which has been sent to other RUs by real-time message by the RU managing
the product,
- tickets included in a product that is accessible to foreign RUs by means of real-time messages
and the price of which has been sent by the managing RU to its own offices,
shall be brought to account by the allocating RU on the basis of the records generated by its own
central system under the conditions set out in points 2 - page 5 and 3 - page 17 for electronic
accounting. Point A.1 - page 30 indicates which services are brought to account on allocation for each
RU.
2 301
O
1.2.2 - On issue or on the basis of collected tickets
"Ticket" services other than those listed under point 1.2.1 - page 2 shall be brought to account by the
issuing RU on the basis of the records generated by its system or the data entered in its system under
the conditions set out in points 2 - page 5 and 3 - page 17 for electronic accounting.
Point A.2 - page 31 indicates which services are covered by accounting on issue for each RU.
"Supplement" services:
- for which a seat/berth reference has been allocated manually without the use of an electronic
reservations system, particularly sleeper and couchette services sold on board the train, or in
some cases on the platform prior to departure,
- for which a seat/berth reference has been allocated using an electronic system but without the
amounts having been recorded by the system (cases such as these, which result from tariff-
related or technical constraints, should remain exceptional and the other RUs should be informed
accordingly),
- from quotas exceptionally taken from an electronic reservations system for allocation without
reference numbers (i.e. not electronically managed) and without the amounts being recorded by
the system,
shall be:
- either brought to account by the issuing RU using the counterfoils, the lists of pre-printed
supplements or the data provided by the system, under the conditions set out in points 2, 3 or 4 -
page 25 depending on whether an electronic or manual accounting procedure is employed,
- or brought to account by the service-providing RU on the basis of the tickets collected (the case
for couchettes and some sleepers) under the conditions set out in points 2 and 4 for manual
accounting.
NB : when tickets issued without a price for individual passengers are to be incorporated in the
statement of account (for example when the RUs receive compensation from their supervisory
authorities), the tariff documents shall contain a reference to this fact in the accounting
regulations.
The allocating or issuing RU, as appropriate, may entrust the compilation of all or part of its statements
of account to a Third Party. The RU shall however remain solely responsible vis-à-vis the RUs
that receive the statements. It must inform them of all future statements compiled by the Third Party,
specifying the travel documents brought to account and the first statement month handled in this way.
Any modification to or termination of a contract concluded with a Third Party must be notified in similar
manner.
A model contract for conclusion with Third Parties, to which all the provisions of this leaflet shall apply
without restriction, is enclosed in Appendix E - page 64.
3 301
O
1.4 - Services allocated by private transport companies
4 301
O
2 - Regulations common to electronic and manual
accounting
2.1.1 - On issue
The issuing RU shall be responsible for processing all the travel documents issued by the offices
belonging to it, whether situated in its own country or abroad.
To this end it shall lay down the accounting regulations to be applied by its issuing offices (see
Glossary - page 116) which must bring the travel documents to account in the month of their issue.
However, because the accounting procedures of some offices are such that the books cannot always
be closed at the end of the last day of the month, the tickets issued in the course of a given month may
not all be brought to account in that month.
The safeguards to be applied by an RU to which a travel agency submits a request to issue and bring
to account travel documents on an autonomous basis using electronic means are set out in Appendix
F - page 69.
2.1.2 - On allocation
The allocating RU shall be responsible for processing all the allocations and cancellations performed
by its system. To this end, it shall ensure that all the operations carried out within a given month are
brought to account under that month.
2.2.1 - Principle
For those services that are brought to account on allocation (supplements or charged tickets),
the accounting procedure involves:
- debiting the requesting RU for the gross amount of the services allocated,
- crediting the service-providing RUs for the shares of the supplements or tickets to which they are
entitled,
- debiting the service-providing RUs for the agreed commission, in relation to the shares of the
supplements or tickets to which they are entitled.
Requests for services purchased in stations by travel agencies are handled in the same way as
requests from agencies.
5 301
O
For those services that are brought to account on issue, the accounting procedure involves:
- crediting the service-providing RUs for the shares to which they are entitled,
- debiting the service-providing RUs for the agreed commission in relation to the shares to which
they are entitled.
For those services that are brought to account on the basis of collected travel documents, the
accounting procedure involves:
- debiting the issuing RU for the amount of the travel document collected,
RUs that compile statements of account on allocation, on issue or on the basis of collected travel
documents shall be responsible for apportioning to the railways concerned the shares to which they
are entitled for all the tickets processed (see point 2.1 - page 5). The rail shares to which each RU is
entitled are calculated on the basis of the tariffs.
When several transport companies are concerned in a given country, all shares are apportioned to the
lead RU which shall then redistribute them. This RU, which is identified by a UIC code, shall provide
one address only, to which the statements of account are to be sent. Different addresses are,
however, authorised for documents in computerised form on the one hand and in paper form on the
other (the contact details of the various departments are listed in Appendix B - page 32).
For services provided by third parties, the RU that is in contact with the service-providing company
shall be credited with the shares and debited for any commission relating to the service-provider. The
RU shall make the necessary arrangements with the service-providing company.
In some cases these services do not currently involve an exchange of messages or amounts between
RUs. The associated accounting regulations are in abeyance.
A statement of account may only contain services or tickets that have been processed in identical
fashion, i.e.:
- either by computer,
- or manually using the counterfoils, the lists of pre-printed supplements or data supplied by the
system,
- or lists for each type of service together with a checklist recapitulating the types of service
processed in identical fashion and any additional accounting documents that the RU compiling the
statement is required to submit in accordance with the provisions of this leaflet (see point 2.8 -
page 13).
6 301
O
They may be compiled on the basis of:
- sales records for tickets and pre-printed supplements (see Glossary - page 116),
- counterfoils of blank-to-blank coupons and supplement vouchers (see Glossary - page 116),
- data recorded by the system when the issuing operation was performed by an electronic machine,
whether or not connected to an electronic management system,
- services allocated or cancelled during the month in question, for accounting on allocation,
- services sold or cancelled during the month in question, for accounting on issue,
- services collected during the month in question, for accounting on the basis of collected travel
documents,
- exceptionally, travel documents brought to account in previous months and not yet entered in
statements of account by the RU (for example, accounts received late, when statements are
compiled by the issuing RU).
Any time lag between the statement month (see Glossary - page 116) and the accounting month (see
Glossary - page 116) should be avoided insofar as possible.
As a principle, service-providing RUs always receive their exact shares. Any surplus in the amounts
paid shall be kept by the RU that issued the ticket. The same applies to any shortfall. However, blank-
to-blank section coupons (see Glossary - page 116) can be brought to account for the amount actually
collected.
If a clear error has been made in the preparation of blank-to-blank tickets (wrongly made out or
incomplete), the issuing RU is authorised to modify the counterfoils for these tickets and allocate the
shares resulting from the modifications made.
- tickets issued at reduced fare without a reference allowing the reduction to be justified,
- fare calculated for a lower class of accommodation or category of train, with the ticket made out
for the higher class or category.
7 301
O
Naturally, the RU that makes the modification must have proof that the conditions for granting the
reduction were satisfied or that the passenger only used the lower class of accommodation or train
category.
When fares are altered in line with a timetable changeover in the course of a given month, the
statement of account includes tickets for the whole month. The statement in question therefore
includes tickets issued at both the old and the new prices, and the accounting month remains
unchanged. When for technical reasons the issuing RU is obliged to associate a fare alteration with a
monthly book closure, the tickets issued at the former prices are brought to account under the
statement month that precedes the book closure, and those issued at the new prices under the
statement month that follows the book closure.
In the event of a change of route, when the price for the new route is lower than for the old route, the
RU that issues the supplement voucher shall keep the difference (see UIC Leaflet 301-1, point 4.3.2.1
and point D.1, element 11).
When a tariff is modified, statements of account compiled on allocation are drawn up based on the
prices applicable when the seats/berths were allocated or the tickets charged for.
For accounting on allocation, any differences between the price collected and the price brought to
account (when "supplement" requests are sent using the forms in UIC Leaflet 170 before the date the
prices were changed and reach the allocating RU after that date or, exceptionally, when the new prices
for supplements on a RU's domestic services are notified late) may be adjusted by the issuing RU vis-
à-vis the service-providing RU or RUs.
When an RU notices that the price sent in an answer message is wrong, it must:
- issue a manual travel document to the passenger for the correct amount if the RU is able to do so
(see point 4.1 - page 25, for supplements),
- immediately inform the allocating RU so it can correct its files as rapidly as possible.
- the "services allocated" statement on the basis of the prices indicated in the messages allocating
the seats/berths or tickets,
- the "shares apportioned / allocations" statement on the basis of the exact shares (making an
adjustment if necessary).
Any losses or gains that may result shall always be to the credit or debit of the allocating RU. As such,
the following operations are necessary:
- the issuing RU shall bring to account and apportion the manual replacement travel documents that
may have been issued.
8 301
O
NB : for couchette or sleeper services brought to account on the basis of collected travel documents,
the service-providing RU shall debit the issuing RU.
- the issuing RU shall debit the allocating RU for the amount of the corresponding electronic travel
documents (the erroneous amounts).
When an RU notices that the price sent in a message agreeing to a cancellation request is different
from the price given in the agreement message to the initial request, it shall:
- immediately inform the allocating RU so it can make the necessary alterations to its system as
rapidly as possible,
The allocating RU must take the necessary measures to ensure that the cancellations are brought to
account for the exact amounts.
However, if errors persisted in the accounts over a period of time, it would then be up to the allocating
RU to carry out the necessary adjustments vis-à-vis the RUs that requested the cancellations and the
service-providing RUs for each of the transactions concerned.
In the event of a change of tariff, the statement of account shall be compiled using the prices
applicable when the ticket was issued (i.e. price shown on the ticket).
Statements shall be drawn up in the tariff currency. Notifications or book entries shall also be made in
this same currency.
The amounts relating to a given statement month shall be considered due on an average date known
as the fixed value date (see UIC Leaflet 311). RU revenue accounting centres shall calculate agios for
the following periods:
- in multilateral arrangements, between the value date and the date of the BCC (see List of
abbreviations - page 118) clearing operation in which the amounts are notified,
- in bilateral arrangements, between the value date and the date of the current account closure in
which the corresponding entry is made.
However, when the statement is compiled by an allocating RU, the period for which agios are
calculated on the amounts due by the issuing RU ("allocated seats/berths" statements as per point 3.6
- page 19) may not be greater than the period between the value date and the date of the first BCC
clearing operation or the first current account closure following the normal date for compilation of
statements of account (20 M + 1).
9 301
O
This provision does not dispense the allocating RU from its obligation to pay agios to the service-
providing RUs for the whole of the period between the value date and the actual date of the clearing
operation or the current account entry for the corresponding amounts ("shares apportioned"
statements).
NB : when adjustments to statements are made a posteriori or when operations from a given month
are entered as "late" in the statement for a later month, the value date to be used for calculating
agios shall be the date applicable for the accounting month of the initial statement, irrespective
of the month of the statement in which these operations are actually entered.
2.5 - Commission
RUs shall be free to agree on the commission rates applied between one another. When a commission
rate is changed, the rate to be used for the statements shall be that applicable when the seats/berths
were allocated or when the tickets were charged for.
2.6.1 - General
UIC Leaflet 311, point 4.2.1 sets out the special measures that apply in the event of currency
manipulations or similar measures.
When the BCC requests that accounts be split as provided for in UIC Leaflet 311, points 4.2.1.1 and
4.2.1.2, this shall entail a separation in the statements of account affected by the currency in question
(currencies other than the euro). This separation shall be carried out within the deadlines stipulated in
UIC Leaflet 311, point 4.2.1.2. Special arrangements for electronic accounting are given under point
3.3.1.3 - page 18.
In general, adjustments are not affected by the splitting of statements. However, any RU receiving a
statement and suffering a significant loss as a result shall be entitled to claim compensation from the
issuing RU.
2.7 - Adjustments
- if fraud is committed by third parties (passengers in particular), the amounts recovered shall be
shared out.
10 301
O
2.7.2 - Adjustments following loss of tickets
If tickets are lost for reasons beyond the control of those concerned (fire, flooding, theft, etc.) there
shall be no apportionment.
If tickets are lost for any other reason, the following action shall be taken:
- Pre-printed tickets ü
ý each RU shall receive its exact share
- Other tickets lost after issue þ
The RU on whose territory the accounting data has been lost (counterfoils, records, diskettes, etc.) or
data carriers damaged (erroneous data, faulty diskette reading, etc.) must endeavour to share out the
amounts concerned accurately with the aid of other available documents (copy of counterfoils,
records, diskettes, receipts, invoices, data listings, etc.).
If it proves impossible to calculate exact shares, and solely in the case of those tickets for which the
shares cannot be apportioned, the RU responsible shall allocate the shares due as accurately as
possible. In so doing, it shall make use of all the information available, and as a last resort shall apply
coefficients derived from results for previous comparable months and from the apportionment based
on these (as well as data from the issuing RUs' internal encashment lists). Since this procedure is
time-consuming, it does not need to be repeated for each month, rather the missing elements for
previous months should be incorporated.
With re-release
When services are being brought to account on allocation and are cancelled or re-released, the
adjustment operations shall be performed by the allocating RU's system in the conditions set out in
point 3.6.6 - page 23.
Without re-release
When services brought to account on allocation are not cancelled or re-released, the RU which gives
the refund shall perform the necessary adjustment manually in the conditions set out in Volume I of
the TCV (see List of abbreviations - page 118) and its special appendices, in the AIV (see List of
abbreviations - page 118) or in certain specific tariffs applicable on given railway routes. These
provisions shall also apply to supplement services that have been allocated without a price at the
origin and in connection with tickets bearing the distinctive M sign (see point 4.1 - page 25).
These manual adjustments must be made at the latest 15 months after the month when the sale took
place.
11 301
O
If an allocating RU is able to carry out these adjustment operations in its system on an a posteriori
basis, this procedure may be used subject to the following conditions:
- it must not be imposed upon the refunding RU but must be agreed between the parties,
- it then becomes the rule between the RUs bound by the agreement,
- the agreement must state explicitly the deadline for the allocating RU to make the adjustment,
- the allocating RU must inform the refunding RU of the follow-up action taken (date when the
statement was adjusted or reason for not processing the adjustment).
When a reservation service other than an ordinary seat not re-released has been allocated by an
electronic system without a ticket being issued because the service was requested by telephone or at
a domestic terminal by a passenger but was not collected, the requesting RU shall debit the service-
providing RU for the gross amount, having deducted any agreed commission as appropriate. In this
case, proof for the adjustment is provided by the computer listing containing the same information as
would have been printed on the ticket.
Tickets that are issued and cancelled in the same month may not be included in the statement of
account. Furthermore, tickets from previous months can be cancelled automatically within twelve
calendar months of the month of issue of the ticket. Beyond this date, the adjustment may only be
effected if all the RUs concerned agree.
The amounts refunded must be adjusted no later than 15 months after the month during which the sale
took place.
Errors that are noted during verification of a statement received shall be notified to the RU that
compiled the statement at the latest 6 months after receipt of the statement. However, errors of
30 euro or less shall not be considered, unless they are recurrent (for example, errors in unit shares,
procedure or programming).
Errors that have been notified shall be entered on an "adjustment note" (see Appendix K - page 105).
A note must be compiled for each statement month and each type of issuing office. The "situation" part
of this document shall be used to indicate, as appropriate, either errors in the amounts credited under
"shares apportioned", or errors in the amounts debited under "services allocated" or "travel documents
collected".
Corrections that are subsequently necessary shall be made by the RU that compiled the statement.
The amounts to be adjusted shall be entered as credit or debit for all the RUs affected by the error
notified. A copy of the adjustment note shall be attached to the statement of account. For electronic
accounting, see point 3.5 - page 19.
Similarly, when the RU compiling the statement notices errors in its own statement, it shall make the
corrections within 6 months of sending out the statement by compiling an "adjustment note" that is
attached to the statement of account in which the adjustment has been made. However, in the first
case mentioned under point 3.5 - page 19, there is no obligation to attach an adjustment note.
12 301
O
An RU that has made a request for an adjustment is entitled to carry out the adjustment automatically
if it has not received a reply after two months have passed and it has confirmed its request by
registered mail with acknowledgement of receipt and still received no reply 30 days later.
If, six months after making its initial request, the RU has not received what it considers to be an
acceptable response, it may call on the RCF sector to arbitrate if the amount to be adjusted for this
request or for all the requests resulting from the same anomaly exceed 5 000 euro.
The arbitration ruling made by the RCF sector shall then be binding on the revenue accounting centres
of the RUs concerned.
NB : adjustments that bear no relation to passenger traffic revenue accounting may not be made in
the statement.
The RU that compiles the statement of account shall send it to the RUs concerned at the latest:
- by the 20th of the month following the statement month (whether accounting on issue or on
allocation), for services (tickets or supplements) that are issued and brought to account by
computerised means and for services (tickets or supplements) that are allocated or cancelled
electronically;
- by the 10th of the third month following the statement month for all other tickets.
If for a given month an RU has no statement to send to another RU, a NIL return shall be despatched
for information.
Statements may be sent out directly by the third party responsible for compiling them providing they
represent a uniform set, in other words:
- all the statements covering a single traffic type (see Glossary - page 116),
Accounting documents (with the exception of data carriers) shall be sent to the revenue accounting
centre of the lead RU (see Appendix B - page 32) if possible by registered service despatch or by
ordinary service despatch or by post if service consignments are no longer operational.
In addition to the measures contained in UIC Leaflet 361, an RU receiving a statement of account may
in exceptional cases ask the RU that compiled the statement for information about a given ticket or
service, for which it must send the RU in question the travel document or a photocopy of it, or failing
13 301
O
that quote the necessary references (issuing office, number, etc.). This request must be made no later
than six months following receipt of the corresponding statement.
The RUs which compile statements of account must keep the documents and media carrying the
accounting data for a period of seven months at least counting from the date on which the
corresponding statement was sent out.
Any RU which, for whatever reason, cannot meet the despatch deadline stipulated in point 2.8.1 -
page 13 shall be required to inform the other RUs of this fact. When this delay is longer than one
month, the written advice shall state the cause of the delay, its foreseeable duration as well as the
sales months likely to be brought to account late. The RU responsible for the delay shall take every
possible step to ensure the delay is made good as soon as possible.
When an RU experiences an unexpected and protracted computer system breakdown, it can ask
other RUs which compile their statements in accordance with the provisions of point 3 - page 17 to
send it settlement details on a data carrier together with the corresponding lists. This entitlement is
valid solely during the computer system breakdown and concerns statements that have not yet been
compiled.
2.9.2 - Measures to be applied in the event of delays exceeding three months (major
delays)
2.9.2.1 - Principle
Any RU despatching all or some of its statements of account more than three months after the normal
date for bringing transactions in a month of issue (or allocation) to account shall be liable to make a
compensation payment for the major delay incurred on each late statement of account, to each RU
receiving a statement of account.
The aim of this payment is to compensate the RU which suffers the delay for the extra work incurred
and for being deprived of information. The compensation shall range from 2 % to 10 % of the gross
sum of shares due (i.e. before deduction of commission) depending on the length of the period during
which there is a major delay in sending out statements of account.
The compensation payment shall be decided upon, calculated and paid as specified below without
prejudice to payment of the agios (pertaining to cash flow costs) provided for in point 2.4 - page 9, nor
to application of UIC Leaflet 311, point 5.1.4 on financial on-account payments, nor to any exceptional
measures which the Economics, Finance and Environment Committee might take to settle the
accounts should it prove impossible to make up the delay within a reasonable timeframe.
For the purposes of these provisions, the delay in issuing the statement of account shall be calculated
as the period of time elapsing between the date of the BCC clearance operation (or current account
closure) in which the statement should have figured had it been compiled within the normal timeframe
for the actual accounting month (issue or allocation) and the date of the BCC clearance operation
(or current account closure) in which the statement of account actually figures.
14 301
O
Should the RU compiling statements late wish to challenge the decisions taken, it may appeal to the
plenary assembly of the Economics, Finance and Environment Committee.
The RU responsible for the major delay shall be liable to compensate each penalised RU, with effect
from the date on which the Economics, Finance and Environment Committee Steering Committee
decides to impose compensation. All the RUs concerned shall be notified by the Chairman of the
Steering Committee by letter of the RU at fault, the date from which the measures apply and the rate
for calculating the compensation.
2.9.2.3 - Procedure for bringing compensation payments for major delay to account
Once the decision to impose compensation has been notified to the parties concerned as stated in
point 2.9.2.2, each RU penalised by the delay is entitled to debit the defaulting RU directly for the
compensation owed, through notification to the BCC (or entering the sum in the bilateral account),
provided that the delay in compilation of statements exceeds three months.
Thus the compensation payment may be brought to account immediately: there is no obligation to wait
until a statement of account is received. In so doing, the compensation due shall be estimated on the
basis of the equivalent statement of account for the previous year and later adjusted, if need be, when
the actual statement of account for the period is received, by means of a supplementary debit or credit
statement.
The RCF sector shall inform the Economics, Finance and Environment Committee Steering
Committee as soon as the delay in despatching all or part of a statement of account exceeds three
months. The latter shall then request that the defaulting railway submit a remedial plan within ten days.
The Economics, Finance and Environment Committee Steering Committee may decide to impose
compensation payments equating to 2 % of the gross total for each statement of account notified or
entered in the current account over three months late.
If the delay in compiling certain statements of account continues to exceed three months at the end of
the sixth month following submission of the first remedial plan or following referral of the matter by RCF
to the Steering Committee should no plan have been submitted, the Steering Committee may decide
to raise the rate of compensation for those statements of account to 5 %. Such a decision shall
authorise an adjustment to be made on all statements of account previously compiled on the basis of
2 % not yet notified or entered in a current account.
If at the end of the ninth month calculated as stipulated above there are still delays exceeding three
months in the compilation of certain statements of account, the Steering Committee may decide to
raise the compensation rate for those statements of account to 10 %. Such a decision authorises an
adjustment of all statements of account previously compiled on the basis of 5 % not yet notified or
entered in a current account.
15 301
O
Should the delays on certain statements of account continue to exceed three months at the end of the
twelfth month as defined above, the Steering Committee may decide upon exceptional measures to
clear the accounts and to put an end to the situation.
2.10.1 - General
The procedures for combating and preventing fraud in international traffic are set out in UIC
Leaflet 361. The references to this leaflet as given below concern the main measures to be taken by
revenue accounting departments.
The issuing RU shall keep a tight control on stocks of blank-to-blank tickets (including pre-printed and
blank stock for electronic issue), as well as of pre-printed tickets, to prevent tickets being issued
without the corresponding amounts being brought to account (see UIC Leaflet 361, point 2.6). It may
sub-contract the supply and management of stocks to a third party, but nonetheless remains
answerable to the other RUs.
The other mandatory checks are to be made by issuing RUs (see UIC Leaflet 361, point 3.4).
16 301
O
3 - Accounting regulations applicable to electronic
accounting
3.1 - General
RUs wishing to computerise their accounting procedures must give the other RUs involved at least
three months' notice of their intentions, stating the date when their plans will take effect (statement
month), the type of accounting procedure (on allocation and/or issue), and the issues concerned. They
must ask the RUs which formats they wish to receive:
- data carriers with the lists generated from them (in which case the RU receiving the statement
shall state for how long the latter are required. The period should be limited),
Any extension in the issues concerned must be notified to the RUs concerned.
A specific statement of account data carrier shall be compiled for a given RU. It shall only contain data
relating to a given statement month for the railway to which it is addressed.
Given that their despatch deadlines are different, statements for electronic issues and for manual
issues shall be provided on separate data carriers.
RUs compiling electronic statements of account must be able to guarantee the traceability of the
operations performed from the generation of the ticket to the compilation of the statement of account.
This traceability must permit verification of compliance with the actual accounting month.
Constituting electronic accounting message phrases directly by inputting information straight from
travel documents issued manually, i.e. without first processing it by computer and carrying out checks
on calculations of shares, must remain an exceptional and limited practice. Such phrases must be
identified by the special code provided to that end.
3.2 - Interval before entry in the accounts: special case for shares
apportioned/issues
If a travel document is ordered from a call centre, it may be brought to account in the accounting month
in which it is issued even if it was requested from the system at a date in a previous accounting month.
Apart from the exception indicated in point 3.3.2 - page 18, data for the statement of account shall be
exchanged by one single electronic means: direct file transfer by secure e-mail (PGP) or with FTP or
CFT (see point G.1 - page 70).
17 301
O
3.3.1.2 - Form of messages
The elements of the "services allocated" and "shares apportioned" messages to be exchanged for
"supplement" or "ticket" services are listed in points G.4 - page 78 and G.5 - page 85. The technical
specifications for the data carriers are given in point G.2 - page 70.
When accounts are compiled on issue, only the "shares apportioned" message is used. At least one
detail phrase shall be compiled for each travel document concerned. Because of the way the
accounting message is structured, the RU that compiles the statement may create, for a given RU,
several detail phrases for the same travel document (e.g. for round trips (see Glossary - page 116),
collective tickets, transport slips for accompanied-car services).
The distinction between travel documents issued before and after the date of splitting shall be based
on the currency period code (see element 11 of the "detail" phrase, points G.4, G.5 and element 6 of
the "totals" phrase, points G.4, G.5).
In addition to despatching the accounting information on data carrier, the RU compiling the statements
must give the revenue accounting department of each RU concerned advance notice of the total gross
and net amounts for which they will be credited and debited in each accounting currency. These
amounts shall be indicated on a paper document entitled "notification slip", the structure of which is
specified in point H.1 - page 95.
These records must include all the details specified for the accounting message as indicated in point
3.3.1.2.
The totals from the records for "shares apportioned/issues", "shares apportioned/allocations" and
"services allocated/cancellations requested" shall be entered on a general checklist, the structure of
which is specified in points H.1 - page 95 and H.3 - page 97.
Appendix C - page 41 lists the different tariff codes to be used between RUs in accounting messages
or records for:
- single price tickets that can be broken down into their component parts,
18 301
O
- travel documents (as per TCV Volume 1; special appendices to the TCV; FIP agreements; special
agreements).
When, as specified in point 2.7.5 - page 12, there are errors for which an adjustment must be made,
the following measures shall apply.
Incorporation of adjustments:
- in the "shares apportioned" accounting message or in the corresponding list, if the adjustments
are known prior to the generation of the message or list and correct the difference relating to a
transaction already performed - adjustment code = 2. Errors of this kind can only have been
detected by the RU compiling the statement.
- on the notification slip or the general checklist, if the adjustments have not been included in the
messages or lists - statement type = 3. These may be errors detected by the RU compiling the
statement or errors notified by another RU in a previous statement.
Whenever an error is notified by a recipient RU using an adjustment note, proof of the adjustment
made must be provided by annotating and returning the adjustment note with the statement of
account.
When the error has not been notified by the RU that receives the statement, an adjustment note must
still be enclosed with the statement of account in which the adjustment has been made, by way of
proof. The recipient RU is then entitled to request additional information from the RU that compiled the
statement if it so wishes.
When it is the RU issuing the statement that notices errors in its own statement, it must make the
correction within six months of despatch of the statement, drawing up an "adjustment note" as
indicated above. However, for adjustments made in the form of contra-entries - code = 1 - there
is no obligation to enclose an adjustment note.
When the error that is notified points to an anomaly that has led this same error to recur over a period
prior to the statement month in question, the RUs concerned shall determine by common agreement
the period and rules to apply to the adjustment.
In order to be able to carry out subsequent calculations and apportionment, the central system needs
to be able to identify the type of requesting office.
19 301
O
There are four possible cases:
- the call terminal is in a station, and no further information is given. The seat/berth is considered
allocated to a station or the ticket requested by a station,
- the call terminal is in a station, but its identifier indicates that the seat/berth or ticket have been
ordered by an accredited travel agency. The seat/berth is then considered to have been allocated
to an agency or the ticket requested by an agency,
- the call terminal is in an agency, linked directly to the central system. The seat/berth is considered
to have been allocated to an agency or the ticket requested by an agency,
- the call terminal is in an agency, but its identifier indicates that the seat/berth or the ticket has been
ordered by a station. The seat/berth is considered to have been allocated to a station or the ticket
requested by a station.
In each case, the central system shall calculate and share out the agreed commissions.
The central system that allocates the seats/berths or replies to a ticket request must:
- indicate in the reply message the value in the tariff currency of the service provided, assuming it
is not a free reservation, a reservation sent without a price for tariff-related or technical reasons,
or free tickets,
- indicate in the reply message the reference number generated by the system. This number, which
identifies the service unambiguously, must be printed on the ticket issued to the passenger,
- save in its memory all the information needed to apportion the charges and commission that is
due, in addition to the data specified above.
Seat/berth requests submitted using the form in UIC Leaflet 170 are sent to the office designated in
the reservation list, which then provides the central system with all the details it needs to obtain the
references for the seats/berths requested and to effect the apportionment. The references of the
seats/berths allocated are sent to the requesting office again in the conditions set out in UIC
Leaflet 170.
These forms must if appropriate include the reduction code (see point 3.6.4) and the number of
reduced-fare seats/berths concerned, so as to enable the allocating RU to bring the exact amounts to
account.
The different types of free or reduced-rate fares applicable in international or domestic traffic are listed
in Appendix L - page 106, which specifies:
20 301
O
- the reduction codes to be used in the accounting message,
3.6.5.1 - Origin
- exchange,
Cancellation requests must be accepted by the allocating RU during the period stipulated in the
regulations.
Seat/berth cancellation requests submitted in accordance with UIC Leaflet 170 shall be sent to the
office designated in the reservation list, which shall provide the central system with all the information
needed to cancel the seat/berth and make any adjustments as appropriate.
In the case of a partial cancellation, the revenue accounting operations are conducted as if the seats/
berths were being completely cancelled and a new request entered in the reservation system for the
seats/berths retained.
When an exchange is made, or couchette berths are changed to sleeper berths, or a sleeper service
is upgraded for a higher class of accommodation, the revenue accounting operations are conducted
as if two consecutive operations were being done, a cancellation and a request.
The reply message exchanged between the allocating RU's central system and that of the RU that is
requesting the cancellation must indicate the following information:
- for the re-released seats/berths, the gross amount for the corresponding services, calculated on
the basis of the tariff in force on the day they were allocated,
- for the seats/berths held in reservation, in the case of partial cancellations, the gross amount
calculated on the basis of the tariff in force on the day the initial seats/berths were allocated.
This same amount is used to bring to account the seats/berths held in reservation. Furthermore,
21 301
O
to justify any discrepancy between the tariff applied and the date of issue of the new voucher
issued following a partial cancellation, the words "partial cancellation" must be entered on the
voucher,
- for the new seats/berths allocated in the case of an exchange, of a change from couchette to
sleeper berths or of a sleeper upgrade, the gross amount calculated on the basis of the tariff in
force on the day of their allocation (new tariff).
The cancellation message means that aside from re-releasing the seats/berths for use by the central
system the allocating RU has the following operations to carry out:
• keep the initial data from the "shares apportioned" part of the statement of account,
• record the data, in order to debit the RU for the gross amount of its share and credit it for the
agreed amount of commission,
- vis-à-vis the initial issuing RU: keep the data from the "services allocated" part of the statement of
account,
- vis-à-vis the RU requesting the cancellation: record the data, in order to credit the RU for the gross
amount of the service in a "seats/berths allocated" statement and debit it for the agreed amount
of commission.
Comments
- The cancellation of a seat without a supplement does not trigger an accounting operation.
- The term "data" should be understood to mean both the amounts, for the RUs that record the sums
immediately, and the information that permits the calculation of the amounts to be brought to
account, for the RUs that carry out these operations all together at the end of a period.
- If there are special commercial agreements that specify that for certain "all-inclusive" price
products a refund is not granted in full and that the non-refundable part is paid to the service-
provider, the allocating RU must, in addition to the systematic operations indicated above, do the
following: debit the RU requesting the cancellation to recover the (non-refundable) part of the
refund accruing to the service-providing RU; credit the service-providing RU for the same amount
(elements 7 - page 79 and 29 - page 82 of the "services allocated" accounting message; elements
7 - page 87 and 30 - page 91 of the "shares apportioned" accounting message).
- Cancellation requests for travel documents once accepted by the central system shall not be
subject to manual adjustment. However, for services that have been allocated without a price, see
point 2.7.4.1 - page 11.
22 301
O
3.6.5.6 - Cancellations using the form in UIC Leaflet 170 that can no longer be accepted
by the central system
Cancellation requests submitted using the form in UIC Leaflet 170 - or possibly by telex - and which
can no longer be accommodated by the central system shall, when the initial seat/berth is brought to
account electronically, be subject to manual adjustment by the allocating RU, using sheet B of the
cancellation request or telex.
- debiting the service-providing RU for the net amount, i.e. after deduction of the agreed
commission,
- crediting the RU requesting the cancellation for the net amount, i.e. after deduction of the agreed
commission. Sheet B of the cancellation request - or telex - shall be kept by the allocating RU as
proof to be supplied to any RU on request.
3.6.5.7 - Cancellations using messages that cannot be accepted by the central system
When a cancellation message that is sent within the normal deadlines reaches the allocating RU too
late to be accepted by the central system, the provisions of point 2.7.4.1 - page 11 shall apply for the
seats/berths that have not been re-released.
When a train or coach is cancelled and no replacement service provided, the accounting data remains
in place.
The RU that refunds either a seat/berth allocated in that train or coach, or a combined service, shall
then debit the RU(s) that would normally have provided the service.
3.6.5.9 - Refund made by an RU other than that which re-released the seat/berth
When services that are normally brought to account electronically have been re-released by an RU
within the normal deadlines and a refund is exceptionally requested from a different RU, the latter shall
debit, under the conditions set out in Volume I of the TCV or its special appendices, the RU that
requested the cancellation and which is identified by the stamp and the cancellation note that must
feature on the back of the travel document.
When incidents arise in the transmission of messages between interconnected RUs, the adjustments
are to be made in accordance with the conditions set out in points M.1 - page 110 to M.3 - page 113.
Links between a central system and terminals situated in offices that are not part of the RU that owns
the system are covered by agreements between the two RUs concerned.
23 301
O
Comments
The agreement of third party RUs shall be required to the extent that they are concerned as allocating
RUs for seats/berths.
These agreements shall specify in particular the type of accounting relations that shall apply between
the RU using the terminals and the RU that owns the central system.
The reference number supplied by the system must, in all cases, be printed or marked on the travel
documents specified in UIC Leaflet 918-2 or on Sheets A and B of the request forms specified in UIC
Leaflet 170. On the latter sheets, the distinctive marking "T" must precede the reference number.
The RU that owns the system shall bring to account all the services it has allocated via the terminals
under the same conditions as for seats/berths allocated to its own offices.
The RU using the terminals shall not carry out any revenue accounting operations for the seats/berths
or ticket services that it has requested via these terminals.
Seat/berth cancellation messages that are sent via the terminals must be processed as specified in
point 3.6.5 - page 21.
When the agreement provides that the links between the RU using the terminals and an
interconnected third party RU can take place via the RU that owns the central system, requests for
seats/berths or tickets and cancellation requests from these terminals must be identified as originating
with the RU on whose behalf the request is being made (the RU actually making the request).
In this case, the third party RUs shall bring the services allocated to these terminals to account and
make the adjustments for the services cancelled by the terminals, considering that the seats/berths or
tickets are allocated to the offices of the RU using the terminal or are cancelled by the same.
The RU that owns the central system must notify all the RUs in writing, at least two months in advance,
of the installation of terminals in an office belonging to another RU and specifying whether or not these
terminals have access to a third party RU.
These tests are designed to ensure that between the allocating RU in question and an issuing RU to
be defined all transactions for two given accounting days, at the least, are correctly processed. The
tests must concern data which is real and representative.
The practical arrangements for carrying out the tests shall be determined on a case-by-case basis by
the RCF1 group (see List of abbreviations - page 118) at the appropriate time.
When an RU is planning to apply the principles set out in UIC Leaflet 301, it must immediately inform
the RU leading the RCF 1 Group. The latter will then apprise the former of the procedure to be
followed.
Furthermore, the RCF1 group may decide that similar tests, or other tests, are to be carried out when
differences arise that one or more RU consider out of step with their expectations.
24 301
O
4 - Accounting regulations applicable to manual
accounting for supplements
4.1 - General
Electronic revenue accounting has been obligatory since 1.1.1995. RUs which for exceptional
technical reasons still bring certain tickets to account manually must compile their statements in
accordance with the regulations of UIC Leaflet 301-1, point 4.
The provisions of this point therefore only apply to the following supplement services (train, couchette
and sleeper supplements):
- those allocated by a reservations system other than an electronic seat/berth reservations system.
Requests for seats/berths sent to RUs that do not have an electronic reservations system and the
replies received from those RUs shall be sent as specified in UIC Leaflet 170,
- those for which a seat/berth reference was not allocated (payment of a supplement without a
reservation),
• electronic accounting procedures are not applied by the allocating RU in accordance with
point A.1 - page 30,
• computerised records are not generated for the amounts concerned,
• a replacement travel document has been issued manually because of a mistake in the price
charged.
To facilitate the revenue accounting operations, the following conditions shall apply to manually-
issued priced travel documents:
- those replacing electronic travel documents without a price must carry the distinctive "M" marking
in front of the reference number,
- those replacing electronic travel documents for which the price was wrong (see point 2.2.4.2.1 -
page 8) must bear the distinctive "E" marking in front of the reference number.
The accounting regulations applicable to the services listed under point 4.1 above are set out in the
TCV special appendices entitled "Seat reservations", "Berths", "Chartering of trains and coaches",
subject to the specific provisions of points 4.3, 4.4 and 4.5 - page 26.
The statements produced by issuing RUs shall be compiled on the basis of travel document
counterfoils or pre-printed supplement records.
The statements produced by service-providing RUs shall be compiled on the basis of collected travel
documents.
25 301
O
4.4 - Structure of the statements of account
When the accounting regulations in the TCV special appendix for a given service make no provision
for the use of specific accounting records, the models in points J.1 - page 102 and J.2 - page 103 shall
be used.
RUs that receive the statements of account may ask the issuing RUs to send them the documents that
were used to compile the statements. Such requests must not, however, be systematic.
RUs receiving the statements are given 6 months maximum from the date they receive the statements
to request information from the issuing RUs.
These requests, which must be made in writing, should specify the type of service(s) to which the
request relates.
26 301
O
5 - Regulations applicable for the transition from a
manual accounting system to an electronic
accounting system for supplement services
5.1 - Principle
The following rules shall apply for services when a change of system of accounting occurs:
- tickets issued up until the day preceding introduction of the new system shall be accounted for on
the basis of counterfoils or tickets collected according to the old method (point 4 - page 25 or UIC
Leaflet 301-1),
- seats/berths allocated (or tickets charged) from the day the new system is introduced shall be
brought to account on allocation (point 3 - page 17), subject to the special provisions in point 5.2.1
below for requests sent in using the forms shown in UIC Leaflet 170,
- railways reimbursing services after the day on which the new system is introduced shall make the
manual adjustments referred to in point 2.7.4 - page 11 if the tickets in question were issued
before that date.
Allocating RUs shall record in their system, for accounting purposes, requests received from the day
on which the new system was introduced.
For seat/berth requests sent in using the forms in UIC Leaflet 170, because of the time required to
forward these forms, the allocating RU shall not bring to account the seats/berths allocated on the day
the new system went into operation or thereafter, if the written request preceded that date.
- adjust its electronic accounts manually using parts B of the form with an issue date prior to the
date fixed for the introduction of the new system,
- allocate seats/berths using the national "free" code, thereby enabling it not to record the
corresponding amounts in the system.
Only cancellations concerning reservations initially brought to account by the allocating RU during this
month and subsequent months shall be taken into account in the statement of account for the first
month of allocation in which the new system was applied and subsequent months.
The service-providing RUs shall continue to bring to account forms collected after the date on which
the new system went into operation, but issued before that same date.
27 301
O
6 - Regulations applicable to accounting of services
allocated by private transport companies
(In abeyance).
28 301
O
7 - Temporary regulations
If an RU decides to apply this leaflet, it shall inform all the RUs in writing at least three months in
advance, indicating in particular on what date the new provisions are to be introduced. It must also
send the RUs and the secretariat of the RCF1 group all the data that is needed to complete
Appendix A - page 30 to this leaflet.
All operations (i.e. allocations, issues and cancellations) that are performed with effect from that date
shall be brought to account in accordance with this leaflet.
29 301
O
Appendices
30 301
O
Appendices
a. in excess of the quotas indicated in the table, the statement for services sold (including market prices) is compiled by the issuing RU,
unless a specific agreement is made with the allocator.
31 301
O
Appendices
32 301
O
Appendices
33 301
O
Appendices
34 301
O
Appendices
35 301
O
Appendices
36 301
O
Appendices
37 301
O
Appendices
38 301
O
Appendices
39 301
O
Appendices
40 301
O
Appendices
A standard five-position code shall be allocated to each travel document issued in accordance with:
- FIP agreements.
As a rule the standard codes are to be applied to the journey as a whole. The RU which is moderator
of the RCF1 group manages a list of these codes (see points C.3 - page 42 and C.4 - page 45).
- special agreements,
are identified by a five-position code the first position of which shall always be "2". They only apply on
the routes operated by the RUs concerned, the latter manage their list of codes. Positions 2 to 5 can
in particular be used to give the code of the RU. These codes must be supplied to issuing railway
undertakings which request them.
41 301
O
Appendices
Positions Titles
1 2 3 4/5
6 . . . Market price
6 . . 07 Group 3 or Group Saver (Ad)
6 . . 08 Group 3 or Group Saver (Ch)
6 . . 09 Escapade or Fixed day return
6 . . 10 Group 1 or "Séduction" (Ad)
6 . . 11 Season ticket
6 . . 12 Group 1 or "Séduction" (Enf)
6 . . 13 RIT Ad - Medium level or RIT2
6 . . 14 RIT Ad - Low level or RIT2 TGB
6 . . 16 Réduction Entreprise or Corporate Reduced Price
42 301
O
Appendices
Positions Titles
1 2 3 4/5
6 . . 18 Bahncard AD
6 . . 19 Pass 2 or partial pass
6 . . 21 Eurodomino Pass or Free Pass
6 . . 22 Affaire Ad TGB or Trade Fair /Congress or Business
6 . . 23 Affaire Ch TGB or Business
6 . . 24 Loisir Ad TGB or Leisure AD/Weekend
6 . . 25 FIP or SNCF travel permit
6 . . 27 Loisir Ch TGB or Leisure Ch/Weekend
6 . . 28 Senior Ad TGB
6 . . 30 Entreprise TGB or TCP Ad TGB
6 . . 31 Bahncard Ch
6 . . 34 RIT 2 Ad or RIT 1 Ad TGB
6 . . 35 RIT 2 Ch or RIT 1 Ch TGB
6 . . 36 Promo jeune TGB or Youth Ad TGB
6 . . 37 Mini Ad TGB
6 . . 39 Mini Ch TGB
6 . . 41 Week end Ad TGB
6 . . 43 Séjour or Promo/Supersaver or Mini
6 . . 44 Pass
6 . . 45 Pass InterRail or Parliament
6 . . 46 Enfant + Jeunes or Child + Youth
6 . . 47 Multi
6 . . 48 Mini group (2 to 5 people)
6 . . 49 Pass 3 or partial pass
6 . . 51 Connexion 2
6 . . 52 Connexion 1 or Free global price
6 . . 53 DUO or Découverte à 2 or Escapade à 2
6 . . 54 Adulte aller or Global Price Ad
6 . . 55 T4 Complète AS (TTTP)
6 . . 56 Enfant aller or Global Price Ch
6 . . 57 RIT Disney TGB
43 301
O
Appendices
Positions Titles
1 2 3 4/5
6 . . 58 RIT neige ski Ad
6 . . 59 RIT neige ski Ch
6 . . 60 RIT 2 Ch (Thalys)
6 . . 69 RES (SNCF local traffic)
6 . . 71 First premium (Eurostar) or Second Plus (Eurostar)
6 . . 72 Normal Ad or Business Ad
6 . . 73 Normal Ch or Business Ch
6 . . 74 Loisir Ad
6 . . 75 Weekend
6 . . 76 Découverte J30 or RIT OM or Super Apex
6 . . 77 Loisir Ch
6 . . 78 Senior or Découverte Senior or RES
6 . . 79 Enfant + Senior
6 . . 86 Youth -26 years or Découverte 12-25
6 . . 87 Séduction (Eurostar) or Apex 1 or Super Saver Apex
6 . . 88 Excursion or Partenaire Expo
6 . . 89 Enfant or Séjour Child or Super Saver Child
6 . . 90 Promo Ad or Droit d’accès (Thalys) or Séduction (TGV Ligne
de Coeur)
6 . . 91 Promo Ch or Mini Child
6 . . 92 Group Ad or Group 2
6 . . 93 Group Ch or Group 2
6 . . 94 RIT Ad or RIT 1
6 . . 95 RIT Child or RIT 1
6 . . 96 Handicapé or fauteuil roulant or Wheelchair Ad
6 . . 97 Accompagnateur/guide handicapé or Accompanying person
6 . . 98 FIP loisir/leisure
6 . . 99 FIP service/duty
44 301
O
Appendices
Positions
1 2 3 4 5
1 . . . . TCV Section 1
1 0 0 0 1 Individual passengers
1 0 2 . . Reserved
1 0 3 . . Reserved
1 0 4 . . Reserved
↓ ↓ ↓
1 2 0 . .
↓ ↓ ↓ The last two digits indicate the reduction rate granted by the RU
concerned depending on the number of fare-paying adults
(2 children = 1 adult)
. . . 8 0 120XX
Position 2 to 5 shall be agreed upon for each tariff category by each RU involved in
the traffic concerned.
The issuing RU shall be responsible for requesting these codes from the RUs
concerned.
45 301
O
Appendices
Positions
1 2 3 4 5
3 . . . . TCV special appendices and (BIJ and RIT) special tariffs (see List of
abbreviations - page 118)
3 0 . . . Inter-Rail
NB : for all the IR codes that follow, no distinction is made between the - 26 years,
+ 26 years and child products. To make that distinction, use the following
codes for element 33 "passenger category" of the "shares apportioned"
accounting message: 11 "adult" for + 26 years; 12 "young person" for
- 26 years; 13 "child" for children.
3 0 . 0 1 zone A 22 days
3 0 . 0 2 zone B 22 days
3 0 . 0 3 zone C 22 days
3 0 . 0 4 zone D 22 days
3 0 . 0 5 zone E 22 days
3 0 . 0 6 zone C 22 days
3 0 . 0 7 zone G 22 days
3 0 . 0 8 zones A + B
3 0 . 0 9 zones A + C
3 0 . 1 0 zones A + D
3 0 . 1 1 zones A + E
3 0 . 1 2 zones A + C
3 0 . 1 3 zones A + G
3 0 . 1 4 zones B + C
3 0 . 1 5 zones B + D
3 0 . 1 6 zones B + E
3 0 . 1 7 zones B + C
3 0 . 1 8 zones B + G
3 0 . 1 9 zones C + D
3 0 . 2 0 zones C + E
3 0 . 2 1 zones C + C
3 0 . 2 2 zones C + G
46 301
O
Appendices
Positions
1 2 3 4 5
3 0 . 2 3 zones D + E
3 0 . 2 4 zones D + C
3 0 . 2 5 zones D + G
3 0 . 2 6 zones E + C
3 0 . 2 7 zones E + G
3 0 . 2 8 zones C + G
3 0 . 2 9 zones A + B + C
3 0 . 3 0 zones A + B + D
3 0 . 3 1 zones A + B + E
3 0 . 3 2 zones A + B + C
3 0 . 3 3 zones A + B + G
3 0 . 3 4 zones A + C + D
3 0 . 3 5 zones A + C + E
3 0 . 3 6 zones A + C + C
3 0 . 3 7 zones A + C + G
3 0 . 3 8 zones A + D + E
3 0 . 3 9 zones A + D + C
3 0 . 4 0 zones A + D + G
3 0 . 4 1 zones A + E + C
3 0 . 4 2 zones A + E + G
3 0 . 4 3 zones A + C + G
3 0 . 4 4 zones B + C + D
3 0 . 4 5 zones B + C + E
3 0 . 4 6 zones B + C + C
3 0 . 4 7 zones B + C + G
3 0 . 4 8 zones B + D + E
3 0 . 4 9 zones B + D + C
3 0 . 5 0 zones B + D + G
3 0 . 5 1 zones B + E + C
3 0 . 5 2 zones B + E + G
3 0 . 5 3 zones B + C + G
3 0 . 5 4 zones C + D + E
3 0 . 5 5 zones C + D + C
47 301
O
Appendices
Positions
1 2 3 4 5
3 0 . 5 6 zones C + D + G
3 0 . 5 7 zones C + E + C
3 0 . 5 8 zones C + E + G
3 0 . 5 9 zones C + C + G
3 0 . 6 0 zones D + E + C
3 0 . 6 1 zones D + E + G
3 0 . 6 2 zones D + C + G
3 0 . 6 3 zones E + C + G
3 0 . 6 4 zone H 22 days
3 0 . 6 5 zones A + H
3 0 . 6 6 zones B + H
3 0 . 6 7 zones C+ H
3 0 . 6 8 zones D+ H
3 0 . 6 9 zones E+ H
3 0 . 7 0 zones C + H
3 0 . 7 1 zones G + H
3 0 . 7 2 zones A + B + H
3 0 . 7 3 zones A + C+ H
3 0 . 7 4 zones A + D + H
3 0 . 7 5 zones A + E+ H
3 0 . 7 6 zones A + C+ H
3 0 . 7 7 zones A + G+ H
3 0 . 7 8 zones B + C + H
3 0 . 7 9 zones B + D + H
3 0 . 8 0 zones B + E+ H
3 0 . 8 1 zones B + C+ H
3 0 . 8 2 zones B + G+ H
3 0 . 8 3 zones C + D + H
3 0 . 8 4 zones C + E+ H
3 0 . 8 5 zones C + C+ H
3 0 . 8 6 zones C + G+ H
3 0 . 8 7 zones D + E+ H
3 0 . 8 8 zones D + C+ H
48 301
O
Appendices
Positions
1 2 3 4 5
3 0 . 8 9 zones D + G+ H
3 0 . 9 0 zones E + C + H
3 0 . 9 1 zones E + G + H
3 0 . 9 2 zones C + G + H
3 0 . 0 1 Zone A 12 days
3 0 . 0 2 Zone B 12 days
3 0 . 0 3 Zone C 12 days
3 0 . 0 4 Zone D 12 days
3 0 . 0 5 Zone E 12 days
3 0 . 0 6 Zone F 12 days
3 0 . 0 7 Zone G 12 days
3 0 . 0 8 Zone H 12 days
3 0 4 . .
↓ Reserved
3 0 9 . .
3 2 . . . Accompanied-car trains
3 2 0 . . Vehicles
3 2 0 0 2 Car or camping-car or minibus tariff class 1 (< 3,81 m and < 3,15 m for Messina Strait
crossing)
3 2 0 0 3 Car or camping-car or minibus tariff class 2 (3,81 m to 4,42 m and 3,51 m to 4,50 m
for Messina Strait crossing)
3 2 0 0 4 Car or camping-car or minibus tariff class 3 (> 4,42 m and 4,51 m to 5,50 m for
Messina Strait crossing)
49 301
O
Appendices
Positions
1 2 3 4 5
3 2 1 . . Car-accompanying passengers
50 301
O
Appendices
Positions
1 2 3 4 5
3 3 0 . . Charter trains/coaches
3 3 0 0 1
3 3 0 9 9
3 3 9 5 1 MDI-type supplement vouchers issued for port taxes in traffic with Great Britain
51 301
O
Appendices
Positions
1 2 3 4 5
3 6 9 0 1 EC/IC supplement
3 7 1 . . BIJ
↓ ↓ )↓
3 7 1 . . ) .nth contract
3 8 . . . RIT
↓ ↓ )↓
3 8 0 . . ) .nth contract
52 301
O
Appendices
Positions
1 2 3 4 5
↓ ↓ )↓
3 8 2 . . ) .nth contract
3 . . 0 2 1 person
3 . . 0 3 1 1/2 persons
3 . . 0 4 2 persons
3 . . 0 5 2 1/2 persons
3 . . 0 6 3 persons
3 . . 0 7 3 1/2 persons
3 . . 0 8 4 persons
3 . . 0 9 4 1/2 persons
3 . . 1 0 5 persons
3 . . 1 1 5 1/2 persons
3 . . 2 2 1 person
3 . . 2 3 1 1/2 persons
3 . . 2 4 2 persons
3 . . 2 5 2 1/2 persons
3 . . 2 6 3 persons
3 . . 2 7 3 1/2 persons
3 . . 2 8 4 persons
3 . . 2 9 4 1/2 persons
3 . . 3 0 5 persons
3 . . 3 1 5 1/2 persons
53 301
O
Appendices
Positions
1 2 3 4 5
5 . . . . EURAIL
5 0 0 . . Eurailpass : the figures in the 2nd and 3rd position show the geographical sales zone
↓ ↓ ↓
54 301
O
Appendices
Positions
1 2 3 4 5
5 3 0 . .
5 . . 0 2 Eurailpass 15 days
5 . . 0 3 Eurailpass 21 days
5 . . 0 4 Eurailpass 1 month
5 . . 0 5 Eurailpass 2 months
5 . . 0 6 Eurailpass 3 months
55 301
O
Appendices
Positions
1 2 3 4 5
5 9 0 . . EURAILTICKET : the figures in the 4th position show the geographical sales zone
5 9 0 2 . Reserved
56 301
O
Appendices
Positions
1 2 3 4 5
7 0 . . . Europass
7 0 . 0 2 Reserved
7 0 . 0 4 Reserved
7 0 . 0 6 Reserved
7 0 . 0 7 Reserved
7 0 . 0 8 Reserved
7 0 . 0 9 Reserved
7 0 . 1 3 Reserved
7 0 . 1 5 Reserved
7 0 . 1 7 Reserved
57 301
O
Appendices
Positions
1 2 3 4 5
7 0 . 1 8 Reserved
7 0 . 1 9 Reserved
7 0 . 2 0 Reserved
7 0 . 2 4 Reserved
7 0 . 2 6 Reserved
7 0 . 2 8 Reserved
7 0 . 2 9 Reserved
7 0 . 3 0 Reserved
7 0 . 3 1 Reserved
7 0 . 3 3 Reserved
7 0 . 3 4 Reserved
7 0 . 3 5 Reserved
7 0 . 3 6 Reserved
7 0 . 3 7 Reserved
7 0 . 3 8 Reserved
7 0 . 3 9 Reserved
7 1 . . . Europass Youth
58 301
O
Appendices
Positions
1 2 3 4 5
7 1 . 0 2 Reserved
7 1 . 0 4 Reserved
7 1 . 0 6 Reserved
7 1 . 0 7 Reserved
7 1 . 0 8 Reserved
7 1 . 0 9 Reserved
7 1 . 1 3 Reserved
7 1 . 1 5 Reserved
7 1 . 1 7 Reserved
7 1 . 1 8 Reserved
7 1 . 1 9 Reserved
7 1 . 2 0 Reserved
7 1 . 2 4 Reserved
7 1 . 2 6 Reserved
7 1 . 2 8 Reserved
7 1 . 2 9 Reserved
7 1 . 3 0 Reserved
7 1 . 3 1 Reserved
7 1 . 3 3 Reserved
7 1 . 3 4 Reserved
59 301
O
Appendices
Positions
1 2 3 4 5
7 1 . 3 5 Reserved
7 1 . 3 6 Reserved
7 1 . 3 7 Reserved
7 1 . 3 8 Reserved
7 1 . 3 9 Reserved
7 2 . . . Reserved
7 3 . . . Europass AD 75
7 3 0 . . Reserved
7 3 . 0 0 AD 75 5 countries 5 days
7 3 . 0 1 AD 75 5 countries 6 days
7 3 . 0 2 AD 75 5 countries 8 days
7 3 . 0 3 AD 75 5 countries + 2 5 days
7 3 . 0 4 AD 75 5 countries + 2 6 days
7 3 . 0 5 AD 75 5 countries + 2 8 days
7 4 . . . Europass Tourpass
7 4 0 . . Reserved
60 301
O
Appendices
Positions
1 2 3 4 5
7 5 . . . Europass Saver
7 5 0 . . Reserved
61 301
O
Appendices
Positions
1 2 3 4 5
8 Reserved
9 Travel documents for which the statements are on media other than electronic media
or lists generated from electronic media (see point G.5, element 6 - page 87 of the
detail phrase, code 09).
Positions 2 to 5 of the code are established by the issuing RU which informs
participating RUs (these positions should identify the traffic and the type of manual
statement involved).
62 301
O
Appendices
Rules to be used in applying percentage rates to figures expressed in the statement currency
Half price :
- FIP
Statement Reductions other
- AR/2 (round-trip ticket) Rebate Commission
currency than FIP
- child
- dog
EUR 0,01± 0,01± 0,01± 0,01±
ATS 2+/10+ 1± 0,01+ 0,01+
BEF 1+ 1+ 1+ 1+
BGL
BYB
CHF 0,2+ 0,1+ 0,1± 0,1±
CZK 1+ 1+ 0,1+ 0,1±
DEM 1+/0,2+ 0,01+ 0,01+ 0,01+
DKK 1± 1± 0,01± 0,01±
EEK
ESP 1+ 1+ 1+ 1+
FIM 1± 1± 0,01± 0,01±
FRF 0,1+/1+ 0,1+/1+ 0,01± 0,01±
GBP 0,01+ 0,01+ 0,01- 0,01-
GRD
HRK 1± 1± 1± 1±
HUF 1± 1± 1± 1±
IEP 0,1+ 0,1+ 0,1+ 0,1+
ITL 100+ 100+ 10+ 10+
LTL
LUF 1± 1± 1± 1±
LVL
MAD 0,5± 0,5± 0,01± 0,01±
MDL
NLG 0,1+ 0,1+ 0,1± 0,01±
NOK 1± 1± 1± 1±
PLZ 1± 1± 1± 0,01-
PTE 5+ 5+ 1+ 1+
ROL 0,01+ 1±
RUR
SEK 1± 1± 1± 1±
SIT 0,5± 0,5± 0,5± 0,5±
SKK 1+ 1+ 0,1+ 0,1±
TND
TRL
UAK 0,01 0,01 0,01 0,01
USD 1± 0,5± (sans FIP) 0,01± 0,01±
YUN 1± 1± 1± 1±
2 +/10 + = to be rounded up to the next even unit number (up to 400 km) or next ten unit numbers (over 400 m)
1+= to be rounded up to the next unit number
1±= to be rounded off to the nearest unit number (for 0,5 round up)
0,5 ± = to be rounded up or down to the half unit as follows:
from 0 to 0,24, round down
from 0,25 to 0,75, round off to 0,5
from 0,76 to 0,99, round up to the next unit number
0,1 + = to be rounded up to the next tenth of a unit
0,1 ± = to be rounded off to the nearest tenth of a unit (for 0,05 round up)
0,2 + = to be rounded up to the next even tenth of a unit
0,01 + = to be rounded up to the next hundredth of a unit
0,01 - = to be rounded down to the next hundredth of a unit
0,01 ± = to be rounded off to the nearest hundredth of a unit (for 0,05 round up to the next hundredth of a unit)
1 +/0,2 + = to be rounded up to the next unit number (over 100 km) or next even tenth of a unit (up to 100 km)
0,1 +/1 + = to be rounded up to the next tenth of a unit (amount less than 10 units) or next unit number (amount over
10 units)
100 + = to be rounded up to the next hundred units
10 + = to be rounded up to the next ten units
5+= to be rounded up to the next unit which is a multiple of 5
63 301
O
Appendices
(name of third party to which specific accounting work is sub-contracted) hereinafter referred
to as "third party"
Art. 1.1 - The present contract specifies the tasks to be performed by the third party:
- stock supply/management2,
Art. 1.2 - The "RU" shall unilaterally compile the list of services in Appendix A to the present contract.
Art. 1.3 - All the appendices are an integral part of the present contract.
Art. 2.1 - The third party shall keep all the records, data carriers (sales records, counterfoils, etc.) and
documents used for performing the following tasks available to the "RU" for a period of ………..:
- stock supply/management,
- billing,
- collection of payment.
64 301
O
Appendices
Art. 2.2 - The third party shall compile, on request from the "RU", the check list stipulated in Appendix
C to the present contract.
Art. 2.3 - The third party shall immediately report to the "RU" any factor liable to hinder the:
- thoroughness,
- accuracy,
- punctuality
Art. 2.4 - The third party shall authorise the "RU" to carry out any checks it wishes to perform at any
time to ensure the quality and accuracy of the operations sub-contracted to it.
The "RU" shall provide the third party with all the instructions and information it needs to conduct the
operations sub-contracted to it.
Accounting regulations
When several RUs are involved in a given country, all the shares shall be allocated to the lead RU
except in cases explicitly provided for in UIC Leaflet 301.
The statement of account (apportionment or allocation of shares) shall be compiled based on the
calendar month and shall incorporate all the services covered by UIC Leaflet 301, table 1 of
Appendix A apportioned or allocated during the accounting month concerned.
Shares shall be apportioned or allocated taking into account the provisions governing the granting of
commission between RUs.
65 301
O
Appendices
The deadline for compiling the statements of account and apportioning or allocating shares for a given
month shall be set at ......................
(to be decided on a case-by-case basis in other instances).
Art. 4.2 - Direct despatch of statements (depending on the purpose of the contract)
Principle
The statement data carriers shall be despatched directly to the "RU" by the third party. The type of
data carrier used shall be specified by the "RU".
Date of despatch
The statements of account shall be despatched to the RUs concerned at the latest on ………….(date
as per UIC Leaflet 301).
Principle
The stocks of blank-to-blank travel documents (including stock destined for electronic issues whether
pre-printed or not) and pre-printed travel documents must be strictly controlled to prevent tickets being
issued without the corresponding amounts being brought to account.
1. checks on continuity of the chain from point of production to delivery at point of sale,
The "RU" shall supply the third party with a list of procedures to be observed (see Article 2 to the
present contract).
Art. 4.4 - Billing to the issuing office (depending on the purpose of this contract)
Art. 4.5 - Accounting controls on issuing office (depending on the purpose of this contract)
Art. 4.6 - Collection of payment from issuing office (depending on the purpose of this contract)
66 301
O
Appendices
Article 5 - Remuneration
The "RU" shall remunerate the third party in accordance with the provisions in Appendix D to this
contract.
Article 6 - Penalties1
If the third party or "RU" fails to comply with its obligations, the penalties set out in Appendix E to this
contract shall be applied.
The third party shall not be authorised to sub-contract all or any of the activities covered by the present
contract.
The present contract shall take force on ............................. as from the accounting month of
........................... It shall be valid for an indefinite period and may be terminated at the earliest on
31 December ....
This contract may be denounced at any time by either of the parties subject to minimum prior notice
of .......... months, notified by registered letter.
The "RU" shall reserve the right, in the cases provided for in Appendix F to the present contract, to
denounce the present contract without prior notice and without compensation.
67 301
O
Appendices
Appendices 1 :
68 301
O
Appendices
When an RU receives a request from a travel organisation for authorisation to issue travel documents
and keep the corresponding accounts electronically, it shall ensure that the following provisions are
observed:
- The travel organisation shall duly submit an application with full information to the RU which
accredited it. The latter shall take all the necessary measures to ensure that all travel documents
are properly issued and accounted for.
In particular, no issue of tickets shall be possible without a corresponding entry in the accounts.
In addition, the data on each travel document must be recorded on a data carrier permitting a
permanent record of all entries to be kept.
- An obligatory serial number shall be pre-printed on the travel documents for stock-checking
purposes.
- The RU having accredited the travel organisation shall check the programs and files used for
issuing and bringing travel documents to account. This check shall be repeated subsequently,
especially after any modification of programs or files.
For this purpose, test tickets shall be issued under the supervision of the issuing railway. Travel
documents may not be issued for sale until the results of the tests are all satisfactory.
- When the accrediting RU has made sure that the EDP system provides all the safeguards
necessary, it shall inform the other RUs concerned and supply them with all the relevant
particulars.
- The accrediting RU shall keep the data carriers for one year from the date of despatch of the
statement of account, so that the provisions in UIC Leaflet 361 (fraud prevention in passenger
traffic) may be applied.
69 301
O
Appendices
G.1 - General
- the "services allocated" message covering accounting transactions involving the RU which
requested the service or its cancellation,
- "header" phrase,
- "detail" phrase,
- "totals" phrase.
The conditions for structuring each of these phrases are set out in point G.3 - page 72.
Messages to any one RU only contain the services concerning that RU.
- or FTP,
- or CFT.
The method chosen shall be bilaterally agreed between RUs. Failing this the standard electronic
medium shall be PGP secure e-mail.
Whatever the medium used, it must mandatorily be ensured that the message structure as given in
points G.4 - page 78 and G.5 - page 85 is complied with.
The RU compiling the statement may use a single medium, or separate media, for "services allocated"
and "shares apportioned", labelling them using the coding given in point G.2 below.
When separate media are use, the "shares apportioned/allocations" and "seats allocated" messages
must be despatched at the same time.
The technical specifications for HERMES messages and magnetic-tape recordings are given in UIC
Leaflet 912.
70 301
O
Appendices
In points G.1 and G.2, the identifier element defined in UIC Leaflet 912, point 2.2 must be coded as
follows:
The last four positions of the "identifier" element, which are generally reserved for the topographical
label, are systematically filled out with noughts as the label in question is never in fact used.
Messages fields containing no information shall be filled out with noughts. Message fields which are
not filled completely by the information they contain shall be filled out with noughts to the left. No
alphabetical characters are authorised, only numerical characters are to be used, with the exception
of the "statement currency" element.
Each data carrier or direct transfer must include an 18-position label with the following information:
71 301
O
Appendices
NB : the possible combinations of "allocation" and "issuing" codes for a single medium are:
AI + V1 or AI + V2 or AI + 00
A1 + V1 or A1 + V2 or A1 + 00
A2 + V1 or A2 + V2 or A2 + 00
00 + V1 or 00 + V2 or 00 + V3 or 00 + V4
The list, sequence and structure of elements are given in point G.4 - page 78.
G.3.1.1.1 - General
At least one detail phrase shall be established per transaction, each transaction being allocated a
reference number.
A transaction (and consequently a reference number) can require several detail phrases (several
types of services, several tariff categories, etc. are possible for any one transaction). Conversely,
there can only be a single currency for any one transaction). No particular order is imposed for detail
phrases.
If the different components of a transaction cannot be identified separately (e.g. inclusive price), only
one detail phrase should be created.
In the event of a statement of account including elements 28 to 40 for more than one service provider,
as many detail phrases as service providers shall be created:
- the detail phrase regarding the first service provider shall obligatorily contain all the elements from
1 to 27 as it is the main phrase;
- the detail phrases regarding other service providers (the secondary phases) shall obligatorily
contain all the elements from 1 to 23, plus element 25. However, elements 24, 26 and 27 shall be
filled out with noughts.
G.3.1.1.2 - Elements
03: when an additional comfort connected with the quality of the train is concerned,
04: when the transport part of a travel package with divisible price is concerned,
05 or 07: when the services involved are based on a non-divisible price and are subject to compulsory
reservation.
72 301
O
Appendices
If this element is coded 2, it shall represent the non-refundable share debited to the RU requesting the
cancellation. The share shall be retained by the RU providing the service.
Element 25 - Adjustments
The term adjustment shall be taken to mean the correction of errors detected by the allocating RU in
the current statement of account after doing the accounting calculations but prior to the constitution of
the messages or of errors connected with earlier statements notified by other RUs. These adjustments
shall be effected by means of contra-entries: cancellation of an incorrect transaction - detail phrase
already generated in the same month or in a previous month - and creation where appropriate of a
new, correct transaction. Element 25 identifies the phrase cancelling the incorrect phrase.
This shall be the gross amount (i.e. before deduction of commission) payable by the issuing RU for a
service requested.
If element 7 is coded 2, it shall represent the non-refundable share debited to the RU requesting the
cancellation. The share shall be kept by the service-providing RU.
This shall be the gross amount (i.e. before deduction of commission) payable to a RU which requested
cancellation of a service.
This shall be the gross amount of the share which is debited to the service-providing RU (identified in
element 28), following a service cancellation request.
This shall be the amount of the share which is credited to the service-providing RU (identified in
element 28), following allocation of a service or apportionment of the non-refundable share (element
7, coded 2).
This element shall be filled in in all cases, whether the commission is calculated on a percentage basis
or fixed-rate basis. It represents the amount of commission which will be debited to the service-
providing RU and credited to the issuing RU.
This element shall be filled in in all cases, whether the commission is calculated on a percentage basis
or fixed-rate basis. It represents the amount of commission which will be credited to the service-
73 301
O
Appendices
providing RU in the wake of a cancellation request, the same amount being debited to the RU that
requested the cancellation.
This shall be the amount of commission on cancelled services that is debited to the RU that requested
cancellation of a service to offset the amount credited to the service-providing RU.
This shall be the amount of commission payable on services allocated and which is credited to the
issuing RU to offset the amount debited to the service-providing RU.
The list, order and structure of elements are given in point G.5 - page 85.
G.3.2.1.1 - General
At least, one detail phrase shall be created per transaction, each transaction being allocated a
reference number.
A transaction (therefore a single given reference number) may require several detail phrases (several
types of services, several tariff categories, etc.) are possible for one and the same transaction.
Conversely, there can only be a single currency for any one transaction. No particular order is imposed
for detail phrases.
When no distinction can be made between the different components of a given transaction (inclusive
prices, for example) only one detail phrase shall be created.
G.3.2.1.2 - Elements
03: when an additional comfort connected with the quality of the train is concerned,
04: when the transport part of a travel package with divisible price is concerned,
05 or 07: when the services involved are based on a non-divisible price and are subject to compulsory
reservation.
If this element is coded 2, this shall be the non-refundable share debited from the RU requesting the
cancellation. This share shall be retained by the service-providing RU.
74 301
O
Appendices
For tickets only, the RU can choose to include tickets reimbursed by using either this element or
element 27.
This element is to be filled in systematically (even if the service concerns a single ticket issued without
a message being exchanged with the RU).
This element is to be filled out systematically if the RU which compiles the statement is the issuing RU
and the element is not in a summary phrase of a paper statement of account.
This element is linked to element 23 in that it explains what one finds there. It enables the type of
transport document to be identified and thus to identify the source of the issue.
Code 3 = the phrase originates from information from an accounts processing system.
Code 4 = the phrase originates from information taken directly from the counterfoil. This situation must
remain the exception.
The principle underpinning UIC Leaflet 301 is that the statement of account submitted is detailed and
identifies each ticket or supplement separately. This element serves to relay:
- either the reference number, if a message has been exchanged in line with UIC Leaflet 918-1
(code 1),
- or the electronic issue number (code 2). To avoid the problem of duplication of information, when
the issue number is specific to a sales terminal, elements 9 and 10 need simply be filled out first
to identify the terminal concerned,
75 301
O
Appendices
Element 27 - Adjustment
The term adjustment shall be taken to mean the correction of errors detected by the allocating RU in
the current statement of account after the accounting calculations but before establishment of the
messages, of errors in respect of previous statements of account notified by other RUs, and of
corrections required subsequently (revision of coefficients).
• cancellation of an erroneous operation (detail phrase already implemented during the same
month or previous month),
• and setting up as necessary of a correct, new operation. Element 27 marks the cancellation
phrase of the inaccurate phrase,
- for code 2, through debit or credit of an amount to rectify the difference between an operation
already carried out during the same month or during a previous month. The errors can only be
ones detected by the RU that compiles the statement of account. This operation must mandatorily
be justified by means of an adjustment note.
This shall be the gross amount debited to the service-providing RU following a cancellation request.
This element is used if element 7 is coded 2. It is an indication of the percentage of the non-refundable
share which is due to the service-provider (justification for the corresponding "shares apportioned"
phrase).
76 301
O
Appendices
This element shall be filled out in all cases irrespective of whether commission is calculated on a
percentage basis or as a fixed amount. The amount involved is the commission credited to the issuing
RU specified in element 31.
This element shall be filled out in all cases irrespective of whether commission is calculated on a
percentage basis or as a fixed amount. The amount involved is the commission credited to the service-
providing RU in the event of a cancellation request.
The amount involved shall relate to commission on services allocated which is debited to the service-
providing RUs, to offset the amount credited to the issuing RU.
The amount involved shall relate to commission on cancelled services which is credited to the service-
providing RU, to offset the amount debited to the RU that requested the cancellation.
77 301
O
Appendices
Header phrase
Serial C No.
No. Nr of or Reference
Element of Remarks
in pos. Code
phrase Oa pos.
a. Compulsory or Optional
Detail phrase
Serial C No.
No. Nr of or Reference
Element of Remarks
in pos. Code
phrase Oa pos.
5 Reserved 1 - - 23
78 301
O
Appendices
Serial C No.
No. Nr of or Reference
Element of Remarks
in pos. Code
phrase Oa pos.
79 301
O
Appendices
Serial C No.
No. Nr of or Reference
Element of Remarks
in pos. Code
phrase Oa pos.
80 301
O
Appendices
Serial C No.
No. Nr of or Reference
Element of Remarks
in pos. Code
phrase Oa pos.
15 Coach number 3 C UIC 65-67 This element is given when element 6 of the
Leaflet 918-1 detail phrase is coded 06 or 40 (as an
exception, ATOC identifies its coaches
using alphabetical letters).
16 Day of travel 6 C UIC 68-73 This element does not appear when
Leaflet 920-4 element 6 of the detail phrase is coded 01 or
02. The day of travel is the departure date of
the coach at the start of its journey.
17 Departure location
- RU 4 C UIC 74-77
Leaflet 920-1
- Station 5 C UIC 78-82
Leaflet 920-2
18 In reserve 1 83
19 Destination
location
- RU 4 C UIC 84-87
Leaflet 920-1
- Station 5 C UIC
Leaflet 920-2 88-92
20 In reserve 1 93
81 301
O
Appendices
Serial C No.
No. Nr of or Reference
Element of Remarks
in pos. Code
phrase Oa pos.
82 301
O
Appendices
Serial C No.
No. Nr of or Reference
Element of Remarks
in pos. Code
phrase Oa pos.
a. Compulsory or Optional
b. 1st class = 1st class boat = boat tourist A = boat "de luxe" class
2nd class = 2nd class boat = boat tourist B = boat "economic" class
83 301
O
Appendices
Totals phrase
Serial C No.
No. Nr of or Reference
Element of Remarks
in pos. Code
phrase Oa pos.
5 In reserve 1 - - 23
a. Compulsory or Optional
84 301
O
Appendices
Header phrase
Serial C No.
No. Nr of or Reference
Element of Remarks
in pos. Code
phrase Oa pos.
a. Compulsory or Optional
Detail phrase
Serial C No.
No. Nr of or Reference
Element of Remarks
in pos. Code
phrase Oa pos.
85 301
O
Appendices
Serial C No.
No. Nr of or Reference
Element of Remarks
in pos. Code
phrase Oa pos.
5 In reserve 1 23
03 = train supplements
04 = ticket part of a combined service
05 = sectional coupons coupled with a
reservation
06 = couchettes
07 = through tickets coupled with a
reservation
86 301
O
Appendices
Serial C No.
No. Nr of or Reference
Element of Remarks
in pos. Code
phrase Oa pos.
40 = sleeping cars
50 = reservation of on-board amenities
(cabins, berths, etc.) for a sea crossing
60 = meal
87 301
O
Appendices
Serial C No.
No. Nr of or Reference
Element of Remarks
in pos. Code
phrase Oa pos.
88 301
O
Appendices
Serial C No.
No. Nr of or Reference
Element of Remarks
in pos. Code
phrase Oa pos.
14 Class or category 3 C UIC 51-53 017 = single "Gran Class" compartment with
Leaflet 301 shower + WC
018 = double "Gran Class" compartment
with shower + WC
019 = in reserve
021 to 061 = in reserve
062 = 1st class reclining seat
063 = 2nd class reclining seat
064 = 1st class special cabin
065 = 1st class de luxe cabin
066 = 1st class 1-berth cabin
067 = 2nd class 1-berth cabin
068 = 1st class 2-berth cabin
069 = 2nd class 2-berth cabin
070 = 1st class 3-berth cabin
071 = 2nd class 3-berth cabin
072 = 1st class 4-berth cabin
073 = 2nd class 4-berth cabin
074 = 1st class 6-berth cabin
075 = 2nd class 6-berth cabin
076 = executive compartment
077 = video compartment
078 = 4-berth couchette compartment
079 = bicycle compartment
080 = sleeper + shower compartment
081 = breakfast
082 = lunch
083 = dinner
084 = "panoramic seats" compartment
085 = EURAFFAIRES compartment
086 = reclining seats
087 = CLUB compartment
088 = PREFERENTE compartment
089 = TURISTA compartment
090 = bicycle only
101 to 120 = codes set aside for charter
agreements to specify the type of coach if
element 12 is coded 33000 to 33900
17 Coach number 3 C UIC 67-69 This element is given when element 6 of the
Leaflet 918-1 detail phrase is coded 06 or 40 (as an
exception, ATOC identifies its coaches
using alphabetical letters).
89 301
O
Appendices
Serial C No.
No. Nr of or Reference
Element of Remarks
in pos. Code
phrase Oa pos.
18 Travel day 6 C UIC 70-75 This element is not given when element 6 of
Leaflet 920-4 the detail phrase is coded: 01, 02, 08 , 09,
or 11. The day of travel is the departure date
of the coach at the start of its journey.
19 Departure location
- RU 4 C UIC 76-79 RU on which the first journey section is
Leaflet 920-1 worked. If the departure RU has not been
specified (for example InterRail card or
Eurailpass), four noughts should be entered
(0000).
20 In reserve 1 85
21 Destination
location
- RU 4 C UIC 86-89 RU on which the last journey section is
Leaflet 920-1 worked (see element 19).
90 301
O
Appendices
Serial C No.
No. Nr of or Reference
Element of Remarks
in pos. Code
phrase Oa pos.
25 Issue date 6 C UIC 115-120 When the day of the month is not known, the
Leaflet 920-4 last two positions are to be completed by
noughts.
91 301
O
Appendices
Serial C No.
No. Nr of or Reference
Element of Remarks
in pos. Code
phrase Oa pos.
37 Primary route 9 O UIC 188-196 This element shall be given when element 6
code 2nd section Leaflet 920-9 is coded: 01, 02 or 04. For codes 05 and 07,
this element shall be given when it is used
by the allocating RU for charging purposes.
a. Compulsory or Optional
b. 1st class = 1st class boat = boat tourist A = boat "de luxe" class
2nd class = 2nd class boat = boat tourist B = boat "economic" class
92 301
O
Appendices
Totals phrase
Serial C No.
No. Nr of or Reference
Element of Remarks
in pos. Code
phrase Oa pos.
5 In reserve 1 - - 23
a. Compulsory or Optional
93 301
O
Appendices
The elements to be entered in columns 7 to 12 on the lines for statement type No. 1, 2 and 5 This checklist sets out, by currency, type of statement, by accounting month, by type of office and by type of service
correspond respectively to elements 7 to 12 of the totals phrases of the accounting messages in (for the statement types No. 1, 2 and 5), the gross amounts to be debited and credited, the amount of commission
question (see points G.4 - page 78 and G.5 - page 85). to be debited and credited and the net debit and credit balance of the railway undertaking receiving the statement
of account.
NB: statement type 1 = services allocated/cancellations requested There must be a line for statement type No. 4 ("total brought to account") for each currency and each
statement type 2 = shares apportioned/allocations accounting month.
statement type 3 = accounting adjustments (only concerns adjustments not
handled through messages or detailed lists). The amounts to be indicated on the lines for statement type No. 1, 2 and 5 in columns 7 to 12 are specified in the
statement type 4 = total brought to account following table which shows how the columns in the records correspond with those of the general checklist:
statement type 5 = shares apportioned/issues
Columns in the Columns in the Columns in the Shares Columns in the Shares
general checklist Service allocated records apportioned/Allocations records apportioned/Issues records
(point H.1) (point I.1) (point J.1) (point J.1)
7 17 17 17
8 18 18 18
9 29 23 23
10 28 24 24
11
Net balance to be determined on the general checklist
12
94 301
O
Appendices
1 2 3 4 5 6 7 8 9 10 11 12 13
a. Delete as applicable
b. XX YY ZZ ( XX = accounting year; YY = statement month; ZZ = statement period)
c. 1 = Services allocated/Cancellations requested
2 = Shares apportioned/Allocations
3 = Accounting adjustments (only concerns adjustments not contained in messages or detailed lists)
4 = Total brought to account
5 = Shares apportioned/Issues
d. As required (this column is only filled out when the form is used as a "general checklist").
1 = Stations and equivalent offices
2 = Travel agencies and equivalent offices
e. As necessary (this column is not filled out when the form is used as a "general checklist").
Enter the codes given in points G.4 and G.5, element 6 of the detail phrase.
f. 1 = Debit
2 = Credit
95 301
O
Appendices
1 2 3 4 5 6 7 8 9 10 11 12 13
96 301
O
Appendices
1 2 3 4 5 6 7 8 9 10 11 12 13
97 301
O
Appendices
- statement period,
- statement currency,
When a given RU both requests and cancels a service at the same time, either separate or joint records may be compiled for the two types of transaction
(see points I.1 - page 99 and I.2 - page 100).
and/or
- the total number of services cancelled (column 14),
and/or
- the total, per rate, of the commission to be debited to the service-providing RU(s) (column 28),
and/or
- the total, per rate, of the commission to be credited to the service-providing RU(s) (column 29),
- the net total to be debited, which shall be equal to the difference between the gross total to be debited (column 17) and the sum of the amounts of
commission to be debited to the service-providing RUs irrespective of the rates applied (column 28).
and/or
- the net total to be credited, which shall be equal to the difference between the gross total to be credited (column 18) and the sum of the amounts of
commission to be credited to the service-providing RUs irrespective of the rates applied (column 29).
When no entry has been made, fields should be filled out with 0.
When entries have not used all the available positions in a field, the remaining spaces should be filled with 0 to the left.
98 301
O
Appendices
service provider
service provider
Gross amount
Gross amount
Gross amount
Gross amount
Reference No.
Adjustements
debited to the
Cancellations
Primary code
Primary code
providing RU
Dialogue No.
Commission
organisation
commission
commission
2nd section
Category of
Requesting
destination
1st section
the service
Number of
passenger
Amount of
Amount of
Coach No.
Travel day
Unit share
requested
requested
departure
Unit price
cancelled
Train No.
recovery
category
services
services
provider
Class or
Service-
terminal
location
location
Code of
Code of
request
journey
Type of
Date of
(credit)
(credit)
Rate of
(debit)
(debit)
Travel
(D)
(E)
E1 D1
E1 D2
xx xx
E1 Dn
E2 D1
E2 D2
xx xx
E2 Dn
↓ ↓ ↓ ↓ ↓ ↓ ↓ ↓
GROSS TOTAL .............................................................................. .................................
NB : - Information given in columns 1 to 3 and column 6, shall be classified in rising numerical order (alphabetical for ATOC for column 2).
- Information regarding "journeys" in columns 4 and 5 should be classified in accordance with the following system:
E1 → D1 ; E1 → D2 ; E1 → ... ; E1 → Dn
E2 → D1 ; E2 → D2 ; E2 → ... ; E2 → Dn
- Information given in columns 19 to 30 should be repeated for each service-providing RU by using several lines for the same transaction.
- NET TOTAL to be debited = total Col 17 - total Col 28
- NET TOTAL to be credited = total Col 18 - total Col 29
a. Delete as applicable when separate lists are compiled for allocations and cancellations.
b. 1 = stations and equivalent offices.
2 = travel agencies and equivalent offices.
c. A separate list shall be compiled with its balances per currency and per currency period.
d. Enter the codes and wording stipulated in point G.4, element 6 of the detail phrase.
e. Exceptionally, ATOC indicates the time of departure from the station in which the passenger boarded the train.
f. Exceptionally, ATOC identifies coaches by an alphabetical letter.
g. Enter the codes stipulated in point G.4, element 12 of the detail phrase.
h. This element is only shown for "agency" statements.
i. Adjustments of accounting errors not adjustments for cancelled services.
j. Enter the codes stipulated in Appendix C.
k. Enter the codes stipulated in point G.5, element 33 of the detail phrase
l. Indicate the recovery percentage for non-refundable shares
99 301
O
Appendices
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
service provider
service provider
Gross amount
Gross amount
Gross amount
Gross amount
Reference No.
debited to the
Cancellations
Primary code
Primary code
providing RU
Dialogue No.
Adjustments
Commission
organisation
commission
commission
2nd section
Category of
Requesting
destination
credited to
Tariff code
Number of
Number of
passenger
Amount of
Amount of
Coach No.
Travel day
Unit share
requested
requested
departure
Unit price
cancelled
Train No.
recovery
category
services
services
provider
Class or
terminal
Service-
location
location
Code of
Code of
request
journey
Type of
Date of
(credit)
(credit)
Rate of
(debit)
(debit)
Travel
00250 010 281102 850000101 830000001 001 021102 87000000000001 83000000110 00000 00001 00030000 00001 00000 0 0 0000030000 0000000000 8500 34211 1 11 830000001 000000000 00010000 0000000000 0000010000 0000001000 0000000000 1000 0000
8300 34211 1 11 830000001 000000000 00020000 0000000000 0000020000 0000002000 0000000000 1000 0000
00251 011 051202 850000102 830000002 001 031102 87000000000002 83000000111 00000 00002 00050000 00001 00000 0 0 0000050000 0000000000 8500 34212 1 11 830000002 000000000 00020000 0000000000 0000020000 0000002000 0000000000 1000 0000
8300 34212 1 11 830000003 000000000 00030000 0000000000 0000030000 0000003000 0000000000 1000 0000
00251 011 101202 850000102 830000002 002 041102 87000000000004 83000000111 00000 00003 00050000 00000 00001 0 1 0000000000 0000050000 8500 34212 1 11 830000002 000000000 00020000 0000020000 0000000000 0000000000 0000002000 1000 0000
8300 34212 1 11 830000003 000000000 00030000 0000030000 0000000000 0000000000 0000003000 1000 0000
00252 008 031202 850010090 830000005 002 051102 87000000000011 83000000112 00000 00004 00080000 00001 00000 0 0 0000080000 0000000000 8300 10001 1 11 830000005 000000000 00080000 0000000000 0000080000 0000008000 0000000000 1000 0000
↓ ↓ ↓ ↓ ↓ ↓ ↓ ↓
GROSS TOTAL 00003 00001 0 1 0000160000 0000050000 ↓ ↓
100 301
O
Appendices
As record of "shares apportioned/allocations" and a record of "shares apportioned/issues" shall be compiled for each service-providing RU per:
- type of service,
- statement period,
- statement currency,
- commission rate,
- the net total to be debited, which shall be equal to the difference between the gross total to be debited (column 17) and the total commission to be
credited (column 24),
- the net total to be credited, which shall be equal to the difference between the gross total to be credited (column 18) and the total commission to be
debited (column 23).
Fields where no entry has been made should be filled out with 0.
Where entries have not used all the available positions, the remaining spaces in the field should be filled out by the requisite number of 0 to the left.
101 301
O
Appendices
Gross amount
Gross amount
Cancellations
organisation
commission
commission
2nd section
Accounting
the request
destination
1st section
Passenger
Number of
Amount of
Amount of
Travel day
Unit share
requested
departure
Recovery
identifier
category
category
services
Class or
credited
location
location
Primary
Primary
Code of
Code of
journey
debited
(yymm)
Type of
Issuing
Adjust-
Date of
(credit)
Coach
(debit)
Travel
ments
No. of
Tariff
Train
to be
to be
code
code
code
rate
No.
No.
RU
(D)
(E)
E1 D1
E1 D2
xx xx
E1 Dn
E2 D1
E2 D2
xx xx
E2 Dn
↓ ↓
GROSS TOTAL ..........................................
TOTAL OF COMMISSION PER RATE ..........................................
NET TOTAL ..........................................
NB : - Columns 2 to 4 and column 11 are filled out if necessary. When they are filled out, the information in columns 2 to 4 and column 8 should be classified in rising numerical order (alphabetical for ATOC in column 3) and information regarding the "journey",
entered in columns 5 and 6 is to classified based on the following system:
E1 → D1 ; E1 → D2 ; E1 → ... ; E1 → Dn
E2 → D1 ; E2 → D2 ; E2 → ... ; E2 → Dn
- NET TOTAL to be debited = total Col 17 - total Col 24
- NET TOTAL to be credited = total Col 18 - total Col 23
a. Delete as applicable (a separate record is compiled for "shares apportioned/issues" and "shares apportioned/allocations").
b. 1 = stations and equivalent offices - 2 = travel agencies and equivalent offices.
c. A separate list shall be compiled with its balances per currency and per currency period.
d. Enter the codes and wording stipulated in element 6 of the detail phrase in point G.5.
e. The calendar month in which the passenger services were allocated, issued, re-released or refunded. A total shall be compiled per accounting month for the "shares apportioned/issues" record.
f. Exceptionally, ATOC indicates the time of departure from the station in which the passenger boarded the train.
g. Exceptionally, ATOC identifies coaches by an alphabetical letter.
h. Enter the codes stipulated in Appendix C.
i. Enter the codes provided in element 14 of point G.5.
j. Enter the codes provided in element 33 of point G.5.
k. Enter the codes provided in element 13 of point G.5.
l. The type of identifier is coded as indicated in element 22 of point G.5. The number of the identifier should be the same as the reference number (as per UIC Leaflet 918-1) in the case of messages exchanged between RUs and the same as the number of the accounting issue (as per UIC Leaflet 918-1) in
the case of an electronic sale not involving the messages being exchanged, and the same as the physical number of the transport document in the case of manual issues.
m. Adjustment of accounting errors not adjustments for cancelled services.
n. This element only appears on "agency" statements.
o. Indicate the recovery percentage for non-refundable shares.
102 301
O
Appendices
Statement period: 02 11 00
Type of office requesting
Statement currency: EUR 01
the service: 1
Commission rate: 1000
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
year and month
Gross amount
Gross amount
Cancellations
organisation
commission
commission
2nd section
Accounting
the request
destination
1st section
Passenger
Number of
Amount of
Amount of
Travel day
Unit share
requested
departure
Recovery
identifier
category
category
services
Class or
credited
location
location
Primary
Primary
Code of
Code of
journey
debited
(yymm)
Type of
Issuing
Adjust-
Date of
(credit)
(debit)
Coach
Travel
ments
No. of
Tariff
Train
to be
to be
code
code
code
rate
No.
No.
RU
0211 850009369 850009000 40050 002 11 6 87000000453411 0001500 1 0 0 0000000000 0000001500 8700 00000 850060715 0000000150 0000000000
0211 850001008 850000010 40075 002 11 1 87000000036822 0001200 1 0 0 0000000000 0000001200 8700 00000 850001057 0000000120 0000000000
0211 850001120 850003000 40075 002 11 1 87000000052574 0001100 2 0 0 0000000000 0000002200 8700 00000 850031112 0000000220 0000000000
↓ ↓
GROSS TOTAL 0000000000 0000004900
103 301
O
Appendices
Statement period: 02 11 00
Type of office requesting
Statement currency: EUR 01
the service: 1
Commission rate: 1000
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
year and month
Gross amount
Gross amount
Cancellations
organisation
commission
commission
2nd section
Accounting
the request
destination
1st section
Passenger
Number of
Amount of
Amount of
Travel day
Unit share
requested
departure
Recovery
identifier
category
category
services
Class or
credited
location
location
Primary
Primary
Code of
Code of
journey
debited
(yymm)
Type of
Issuing
Adjust-
Date of
(credit)
(debit)
Coach
Travel
ments
No. of
Tariff
Train
to be
to be
code
code
code
rate
No.
No.
RU
0211 00250 010 020201 850000101 830000001 34211 001 11 1 020101 87000000000001 00010000 1 0 0 0000000000 0000010000 8300 00000 850000001 0000001000 0000000000
0211 00251 011 050201 850000102 830000002 34212 001 11 1 030101 87000000000002 00020000 1 0 0 0000000000 0000020000 8300 00000 850000002 0000002000 0000000000
0211 00251 011 100201 850000102 830000002 34212 002 11 1 040101 87000000000004 00020000 1 0 1 0000020000 0000000000 8300 00000 850000002 0000000000 0000002000
↓ ↓
GROSS TOTAL 0000020000 0000030000
104 301
O
Appendices
Railway undertaking
Code of recipient railway undertaking.....
compiling the note
Address of recipient railway undertaking
(initials and code)
................................................................
..................
Station issue
Travel agency issuea
TOTAL
a. Delete as applicable.
b. Comply with the deadlines stipulated in point 2.7.5 of this leaflet.
c. If the RU to which the note is addressed is the RU which compiled the statement.
105 301
O
Appendices
Processing of requests for free or reduced-rate reservation services sent to an electronic system normally responsible for accounting operations as per point 3 - page 17
106 301
O
Appendices
Half-price ICE reservation The amount of supplement Collection of amount of 35019 Normal Nil Half-price ICE reservation for
for BAHNCARD holders reduced by 50 % is shown supplement reduced by 50 % apportionment BAHNCARD holders
a. The series of codes from 35047 to 35049 and 35080 to 35085 are reserved for the purposes of EPA partners.
b. When the allocation concerns a combined service, the fee exemption or reduction code in the request enables the allocating RU to proceed as stated in column 3 for the service(s) in respect of which such a code is mentioned in this table.
Example:
- sleeper + train supplement request with code 35050 = reply with charged sleeper and free (or reduced-price) train supplement.
- sleeper + train supplement request with code 35052 = reply with free sleeper and train supplement
c. When codes 35020 and 35021 only apply to part of the journey covered by the service, the request message from UIC Leaflet 918-1 must include in the "tariff" element the code of the RU concerned; if exceptionally two RUs are concerned, the two tariff elements of the message shall be used.
d. Codes 35053 to 35071 are reserved for services of this type requiring special monitoring by agreement between the RUs concerned. These codes, which fulfil the same function as code 35052, are allocated by the RU responsible for managing the leaflet.
107 301
O
Appendices
108 301
O
Appendices
109 301
O
Appendices
Computer
Issuing Allocating
system
Case No. Terminal computer computer
handling
system system
transit
110 301
O
Appendices
111 301
O
Appendices
a. This list should comprise the following items at least: transit RU producing the list, requesting RU, allocating RU, train, coach, type of
service (see codes provided in point G.4, element 6), departure date, name of boarding station, name of alighting station, class of travel,
reference number, dialogue number, type of requesting office, tariff code, number of seats/berths, amount. This list shall be compiled
for each month during which an incident has been recorded. The elements shall be classified according to the conditions contained in
point M.4.
b. If this message is received: no adjustment by the issuing RU; the allocating RU deletes the relevant data for the statement.
If this message cannot be transmitted or if it is returned by a transit RU because transmission is impossible or, when using HERMES
network protocols a negative response is obtained or a request for synchronisation shows that the correction message has not been
processed by the allocating RU, the issuing RU shall make a manual adjustment, if it sees fit, in accordance with point 2.7.4.1 on the
basis of a list supplied by its central system, which shall serve as reference document.
When the list concerns several service-providing RUs, photocopies shall be made of the items relevant to each service-provider. The
list shall contain in addition to the name of the issuing RU, the total amount for each transaction in euro, the reduction code, elements
6,8,14,16,17,19,21,24,25,26,27 in the detail phrase of the accounting message (see point G.4). This list is drawn up per issuing month
on the basis of the elements in the request messages. These elements shall be classified according to the stipulations contained in
point M.4. In the event of doubt as to the RU providing the service, the issuing RU shall consult the allocating RU beforehand.
If this message can neither be sent on to its destination nor returned owing to an incident on the transit RU or if the synchronisation
request for which provision is made in the HERMES protocols gives no indication about action taken in respect of the correction
message, no adjustment can be made.
112 301
O
Appendices
113 301
O
Appendices
114 301
O
Appendices
1 2 3 4 5 6 7 8 9 10 11 12 13 14
Depar- Destina- Class or Dia- Day of Number
Type of Train Coach Day of Ref. Tariff Amount Type of
ture lo- tion loca- type of logue reserva- of seats/
service no. no. travel no. code in euro office
cation tion sleeper no. tion berths
P1 T1 V1 J1 E1 D1 C1 XX XX XX XX XX XX XX
C2 XX XX XX XX XX XX XX
C3
same classification as above
CX
E1 D2
En Dn
same classification as above
J2 E1 D1
En Dn
J8
J31
same classification as above
V2 J1
J31
V3
VX
same classification as above
T2 V1
VX
T3
same classification as above
TX
Total "service P1" XXXX
P1
same classification as above
PX
Total XXXX
NB : data given in columns 1 to 4 and 7 shall be classified in rising numerical order (alphabetical for ATOC in the case
of column 3).
Journey data in columns 5 and 6 shall be classified as follows:
E1 → D1, E1 → D2, E1…, E1 → Dn
E2 → D1, E2 → D2, E2…, E2 → Dn, etc.
P = code of service (see point G.4, element 6)
T = train no. (ATOC specifies the time of departure from the station where the passenger boarded)
V = coach no. (ATOC uses letters of the alphabet to identify its coaches)
J = day of travel
C = code for class or category (see point G.4, element 12)
E = code of departure location
D = code of destination location
115 301
O
Glossary
Accompanied-car train Train carrying road cars plus their occupants (Motorail-type service)
Accounting month Calendar month during which passenger services were allocated/
issued, re-released or refunded
Railway undertaking Any transport company, irrespective of its status, coded by UIC, to which
the provisions of this leaflet apply. See also UIC Leaflet 306.
Section coupon Ticket issued for one or more sections of a journey ensured solely by a
given railway undertaking, which appears in Volume II (or II/III) for that
railway undertaking
Statement month Month for which the railway undertaking compiles a statement of
account covering the transactions which as a general rule took place
during the corresponding accounting month
116 301
O
Statement period This consists of the year, the month and the period within the month if
the statement of account is compiled with a frequency other than
monthly, in line with the agreement in place between the railway
undertakings concerned.
Supplement voucher A document issued in addition to the travel document entitling the
passenger to specific services (e.g. change of class, change of route,
etc.)
Through coupon Ticket issued for a one-way, return or any other journey (round trip for
instance) for one of the types of traffic named in Annex II to Volume I of
the TCV.
Ticket Term used to denote certain travel documents (pre-printed ticket; blank-
to-blank ticket; electronic ticket; pass, etc.)
Travel organisation Organisation with one or more offices, commonly called travel agencies,
accredited (in general by a railway undertaking in the country in which it
is located) to issue railway travel documents
117 301
O
List of abbreviations
FIP Association dealing with International Travel Facilities for Railway Staff
RU Railway Undertaking
118 301
O
Bibliography
1. UIC leaflets
Leaflet 301-0: Accounting regulations applicable to: - international reservations traffic, - international
passenger traffic for services included in a computerised product which may be accessed by message
in real time by foreign railways, 4th edition, May 2002
Leaflet 301-1: Accountancy regulations for international passenger traffic, 6th edition, April 2002
Leaflet 301-2: Accountancy regulations applicable to international reservations traffic (application lim-
ited to certain railway undertakings), 2nd edition, January 1986 and 11 amendments
Leaflet 306: Framework principles and conventions governing relationships between parties involved
in passenger rail transport with respect to accounting and financial arrangements for international
transport services and ancillary services, 1st edition, December 2000
Leaflet 311: Financial relations between railways - Principles and terms of application, 20th edition,
September 2000
Leaflet 361: Prevention of fraud on travel tickets in passenger traffic, 4th edition, April 2001
Leaflet 912: Principles governing standard messages for data exchange at international level,
2nd edition, July 1994 and 2 Amendments
Leaflet 918-1: Electronic seat/berth reservation and electronic production of transport documents -
Message exchange, 1st edition to be published
Leaflet 918-2: Electronic seat/berth reservation and electronic production of transport documents
(RCT 2 standard), restricted dissemination, 1st edition to be published
119 301
O
Warning
No part of this publication may be copied, reproduced or distributed by any means whatsoever, including
electronic, except for private and individual use, without the express permission of the International Union of
Railways (UIC). The same applies for translation, adaptation or transformation, arrangement or reproduction by
any method or procedure whatsoever. The sole exceptions - noting the author's name and the source - are
"analyses and brief quotations justified by the critical, argumentative, educational, scientific or informative nature
of the publication into which they are incorporated".
(Articles L 122-4 and L122-5 of the French Intellectual Property Code).
International Union of Railways (UIC) - Paris, 2002
301
O