...

There are many different possible configurations for season tickets. Not all of them are available for season tickets imports.

For fixed prices imports, the pricing information must be given in the first part (red part).
For calculated pricing, the pricing information must be given in the second file (yellow part) and will remain empty in the first file.

The data to be imported needs to be described on two files

The first file describes the season ticket itself.
The optional second file describes each performance included in each season ticket.

Note

When you need a standard import, please use the template as example.
Please keep all columns, all 4 first rows, event if there’s no data.
Please keep the order of all columns and all rows. Don’t move or change them.
Please keep the headers/titles as they are, especially the 4th row.
If you want to send us *.csv file, please keep columns, rows and their order also.
Please use option “Comma delimited” for .csv file.

Examples

Attachments

File format for Season Tickets

Field code	Field type	Mandatory	Description
INSTITUTION	Code	Yes	Institution code owning the data to be imported.
ORGANIZATION	Code

Yes

No	Organization code owning the data to be imported.

By default, the organization code is the same as the institution code

If leave it empty, the institution code will be used.
ORDER_NR	Number	No

Order number.

Will be set by import package while importing if left empty.

If leave it empty, order number will be set while importing by default. One line is one ticket. So each line is a unique order number if leave it empty. Many tickets can be in an order if leave them the same order number. This number can be started from 1 in a new data file. Then it will be given new one while importing. This will be file number also.
ORDER_DATE	Date

Yes

No

Order

Buying date.

By default, order date is importing date

If leave it empty, it will be imported date by default.
OPERATION_TYPE	Enum	Yes

Operation type.

It can be started from 1

Allowed values: SALE or RESERVATION.

REMARKTextNoOrder remark.BUYING_CONTACT_NRNumberYesBuying contact number.CULTURAL_CONTACT_NRNumberNo

Cultural contact number.

By default it is identical to the buying contact number.

FIRST_NAMEText 50NoBeneficiary first name. Set this info only for sold tickets.LAST_NAMEText 50NoBeneficiary last name. Set this info only for sold tickets.ST_NUMBERNumberYes if calculated price

Season ticket number is a unique number for each ticket.

Mandatory when calculated price because this number will be used to map data in the sheet for season ticket lines.

CONFIRMATION_DATE	Date	No	Expiration date to confirm reservation.
REMARK	Text 2000	No	Internal remark of order.
BUYING_CONTACT_NR	Number	Yes	Contact number who buys the order. Mandatory because a sstk needs a contact.
SEASON	Code	Yes	Season code of season ticket.

ST

SEASON_

CODE

TICKET	Code	Yes	Product code of season ticket.
PRICE_LEVEL	Code	No	Price level code.

SEAT_NUMBER

TARIFF

SeatNumber

Code

Yes

if

Seat number if the ticket holder is seated at the same place for all performances included in the season ticket.

Mandatory when SSTK is fixed price.

	Tariff code.
CONTINGENT	Code	No	Contingent code.

SEATCAT

SEAT_

CODE

CATEGORY

Code

Yes

Seat category code.

TARIFF

PRICE

Code

Amount

Yes

Tariff code

Price of ticket * 100 (so that 25$ = 2500).

PRICE

CHARGE

Amount

Yes

No

Price

Charge of

season

ticket 100 (so that 1$ = 100).
VAT	Percentage

Yes

No	If leave it empty, it will be 0 while importing by default. Vat rate in percent * 100 (so that 1% = 100). Choose the rate that active and valid following this: Valid from date of vat rate <=

ORDERMandatory when

ORDER_DATE <= Valid to date of vat rate.
PAYMENT_DATE	Date

Yes if SALE

No	If leave it empty, the operation type is SALE and the price is not 0

.Default value: Order date

, the order date will be used by default. Means it can be imported date if the order date is not given.
SEASON_TICKET_NR	Number	No	Each season ticket has a unique number to know how many season tickets have been published. In importation, it helps to define ticket to check between data excel file and database system after importing. This number can be started from 1 in a new data file. Then it will be given new one while importing.
SEAT_NUMBER	SeatNumber	Yes	Seat number if the ticket holder is seated at the same place for all performances included in the season ticket.
CULTURAL_CONTACT_NR	Number	No	Contact number wh If leave it empty and first/last name are empty, the buying contact number will be used by default.
BENEFICIARY_FIRSTNAME	Text 50	No	Beneficiary first name (only if cultural contact is not specified).
BENEFICIARY_LASTNAME	Text 50	No	Beneficiary last name (only if cultural contact is not specified).
TICKET_STATE	Enum	Yes if SALE

The state of ticket.

Mandatory when the operation type is SALE.
Allowed values: NOT_PRINTED, PRINTED

or

Generation date.

Mandatory if

, CONTROLLED.

GENERATION_DATE

TimestampYes if PRINTED or CONTROLLED

Date

No

If leave it empty and the ticket has been printed or controlled

.Default value: Order dateBar code of the season ticket. Mandatory if the ticket

, the order date will be used by default. Means it can be imported date if the order date is not given.
BARCODE	Text 50

Yes if PRINTED or CONTROLLEDThe tax number of the season ticket. Mandatory if the ticket

No	If leave it empty and the ticket has been printed or controlled, it will be generated following import rules by default.
TAX_NUMBER	Text 50

Yes if PRINTED or CONTROLLED

Shipment date of the season ticket.

Default value: Order date

No	If leave it empty and the ticket has been printed or controlled, it will be generated following import rules by default.
SHIPMENT_DATE	Date

Yes

Shipment mode of the season ticket.

Allowed values: TBD.

Mandatory if

No	If leave it empty, the order date will be used by default. Means it can be imported date if the order date is not given.
SHIPMENT_MODE	Code

Yes if PRINTED or CONTROLLED

No	If leave it empty and the ticket has been printed or controlled, it will be imported following import rules by default.

File format for Season Ticket Lines

Each row describes one performance included in a season ticket. The rows are linked to the first file using INSTITUTION and ST_NUMBER.

Field code	Field type	Mandatory	Description
INSTITUTION	Code	Yes	Institution code owning the data to be imported.
ORGANIZATION	Code

Yes

No	Organization code owning the data to be imported.

By default, the organization code is the same as

If leave it empty, the institution code will be used.

ST

SEASON_TICKET_

NUMBER

NR

Number

Yes

Season

Each season ticket

number which is de

has a unique number to know how many season tickets have been published. This is also used to link season ticket with season ticket lines. This number can be started from 1 in a new data file. Then it will be given new one while importing.
SEASON	Code	Yes	Season code of single entry (event/competition).

ST_CODECodeYesProduct code of season ticket.

EVENT

_CODE

Code

Yes

Product code of single entry (event/competition

in the season ticketSEAT_NUMBERSeatNumberYes

Seat number for each performance in the season ticket.

Mandatory when season ticket is calculated price

).
START_TIME	Timestamp	Yes

The performance start time of the event or the match start time of the competition.

Start date time of performance.
TARIFF	Code	Yes	Tariff code.
CONTINGENT	Code	No	Contingent code.

SEATCAT

SEAT_

CODE

CATEGORY

Code

Yes

Seat category code.

TARIFF

PRICE

Code

Amount

Yes

Tarif code

Price of ticket * 100 (so that 25$ = 2500).

PRICE

CHARGE

Amount

Yes

No

Price

Charge of

the seat * 100

ticket * 100 (so that 1$ = 100).
VAT	Percentage

Yes

No	If leave it empty, it will be 0 while importing by default. Vat rate in percent * 100 (so that 1% = 100). Choose the rate that active and valid following this: Valid from date of vat rate <=

ORDERMandatory when

ORDER_DATE <= Valid to date of vat rate.
PAYMENT_DATE	Date

Yes if SALE

No	If leave it empty, the operation type is SALE and the price is not 0, the order date will be used by default.

Default value: Order date

Means it can be imported date if the order date is not given.
SEAT_NUMBER	SeatNumber	Yes	Seat number for each performance in the season ticket.
BENEFICIARY_FIRSTNAME	Text 50	No	Beneficiary first name (only if cultural contact is not specified).
BENEFICIARY_LASTNAME	Text 50	No	Beneficiary last name (only if cultural contact is not specified).
TICKET_STATE	Enum	Yes if SALE

The state of ticket.

Mandatory when the operation type is SALE.
Allowed values: NOT_PR

or

Generation date.

Mandatory if

, CONTROLLED.

GENERATION_DATE

TimestampYes if PRINTED or CONTROLLED

Date

No

If leave it empty and the ticket has been printed or controlled

.Default value: Order date code of the ticket. Mandatory if the ticket

, the order date will be used by default. Means it can be imported date if the order date is not given.
BARCODE	Text 50

Yes if Bar The tax number of the ticket. Mandatory if the ticket

No	If leave it empty and the ticket has been printed or controlled, it will be generated following import rules by default.
TAX_NUMBER	Text 50

Yes if PRINTED or CONTROLLED

Shipment date of the ticket.

Default value: Order date

No	If leave it empty and the ticket has been printed or controlled, it will be generated following import rules by default.
SHIPMENT_DATE	Date

Yes

Shipment mode of the ticket.

Allowed value

Mandatory if the ticket

No	If leave it empty, the order date will be used by default. Means it can be imported date if the order date is not given.
SHIPMENT_MODE	Code

Yes if PRINTED or CONTROLLED

No	If leave it empty and the ticket has been printed or controlled, it will be imported following import rules by default.

Version	Old Version 46	New Version Current
Changes made by	rks (Unlicensed)	Kho SA
Saved on	Dec 16, 2021	Jun 23, 2025

Versions Compared

Key

Examples

File format for Season Tickets

File format for Season Ticket Lines

Content Comparison

Versions Compared

Key

Examples

File format for Season Tickets

File format for Season Ticket Lines