This table lists all services which are included in a contract. In addition to offering a concise overview of the contents, contractual details for all services can be edited here.

In order to access the services for a specific contract, mark its record in the table Contract and switch to the table Contract -> Contract Items. Here, all services contained in the contract are listed and new ones can be added.

In addition to standard services, you can also define conditional services, which are included in a contract but only rendered upon special request by the customer. These optional services allow you to include non-standard yet often required services at more favourable conditions in a contract.

Furthermore, you can define if a service is to be printed out on worksheets or optionally forwarded to mobile computing devices for service recording for the operative apron staff. This is done by marking the checkbox OPS. Please note that the printout on worksheets / forwarding to mobile devices also takes the different organisation units into account (see chapter The Table Organisation Units).

The price for a service is initially imported from the service catalogue defined in the master data module Contracts. It is displayed in the field Item Price. Although the price can be changed here if desired, this is usually not necessary, because the price for all standard services included in a contract is normally subsumed in a flat price defined in the table Contract -> Price Configurations (see chapter The Table Contract -> Contract Items -> Price Configurations) which ignores the individual service prices. This function allows the simple definition of a flat price without having to modify individual service prices.

Nevertheless, the flat price includes only standard services. Additional/optional services, i.e. those contractual services which are only rendered upon special request by the customer, are not included in the flat price. Thus, these service prices must be defined in the table Contract -> Contract Items if they differ from the master data standard pricing.
Following data is used to define contractual services (note that some data fields cannot be edited because they are defined in the master data and are displayed here for informational purposes only):

Station:	Station for which the corresponding contract is valid.
Contract:	Field that shows the No.* of the contract as defined in the corresponding table
Service:*	Combination of the service name definitions from the fields ID* and Service Name is displayed as it has been defined in the table Services of the master data module Contract. For newly added service records, the pull-down menu can be used to select the service.
Additional:	Marking a service is defined as a conditional service, i.e. a service, which is not rendered always and automatically, but has to be explicitly requested by the customer for each flight. Important: Conditional services are not taken into account for the automatic flat price calculation of a standard contract (see table Contract).
Quantity:*	Amount of units of the service to be provided is entered here. The unit each service is calculated in is assigned in the table Services of the master data module Contract (e.g. the provision of cooling liquid could be measured per litre).
Default Unit:	Lists the unit the service is accounted in (e.g. litre, hour, minute etc.) as defined in the master data
Unit (Customer):	Overwrites the Default Unit the service is accounted in (e.g. litre, hour, minute etc.). If a unit differing from the Default Unit is specified here, this unit is taken into account in the contract printout instead of the Default Unit.
Item Price:	Basic price for one unit of the service is displayed automatically. This price is imported from the field Actual Price in the table Services (master data module Contract) multiplied by the Quantity (see above).
Disbursement [%]:	A disbursement percentage can be defined here that differs from the default entry of the master data. This percentage will automatically apply in case the service is rendered and has to be invoiced.
VAT:	Applicable value added tax rate for the service can be selected. Note: The VAT entry here defines the final rate to be taken into account for the invoicing!
Invoice Recipient:	If for any reason the invoice recipient for a special service differs from the general invoice recipient of the contract, the alternative recipient can be defined here.
Service Name (Customer):	Overwrites the Service Name (as defined in the master data module Contracts -> Services) on the invoice. If an alternative service name is specified here, this service name is taken into account in the contract printout.
Remark (2):	Up to two freely-definable text remarks for the service.

The Table Contract -> Contract Items -> Price Configurations

This table serves the definition of price configurations for a contract. Price configurations are used to define variants of a contract which include the definition of conditions which have to apply for a price configuration to be applicable to a specific event (e.g. a flight). This allows, for example, adapting the scope of services and prices included in a contract for specific aircraft types, to define surcharges for contractual services to be applied at bank holidays etc. For a detailed description of price configurations, please refer to chapter Summary of Creating a Contract with Price configurations.
Following data is available for the definition of price configurations for a contract:

ID:*	Service ID definition from the field ID is displayed as it has been defined in the table Services of the master data module Contract.
Active:*	Set if the price configuration has to be applied to the service(s).
No.:*	Service name definition from the field Price Configurations is displayed as it has been defined in the table Services of the master data module Contract.
Active:*	Set if the price configuration has to be applied to the service(s).
Package ID:	Text field to enter the ID of a package (e.g SV13P). This is the identifier of a package. At the same time, it indicates that this price configuration is the package, if this attribute contains any value.
ARR:	Flag if the configuration is applicable for a single-leg arrival.
DEP:	Flag if the configuration is applicable for a single-leg departure.
ROT:	Flag if the configuration is applicable for a rotation.
Others:*	Flag if the configuration is applicable for other.
Parameter:*	Select the type of Price/Value (e.g. Unit Price for a standard price, Percentage for cancellation or for surcharge, etc.)
Price/Value:	Depending on the entry selected from the pull-down menu Price catalogue, a standard price or any other calculation value (e.g. a Percentage for cancellation) is entered here.
Value 2:	A second value can be entered here.
Surcharge/Discount [%]:	Surcharge or discount (negative number) in percent
Valid From/Until:	Starting/End date and time of validity for a contract item. If no date is entered in the Until field, the contract is valid open-ended.
Invoice Recipient:	The current invoice recipient is derived from the field Calc. Recipient unless a manually set Capt. Recipient exists.
Position:	Numerical value entered here defines the position in the order in which the Price values of the associated price catalogue parameter is checked in the calculation process (see introduction above). Generally, the highest values are assigned the most conditions. Also generally, for each service at least a default price (Unit Price) without any conditions (rules) has to be entered with the position 0.
Remark:	Individual remark for the indication of the price configuration

The Table Contract -> Contract Items -> Price Configurations -> Rules

Following data is available for the detail table Contract -> Contract Items -> Price Configurations -> Rules:

Price Configuration ID:	Eternal identifier for the contract price configuration is displayed as it has been defined in the table Contract -> Price Configurations.
Price Configuration Name:	Price configuration name for the contract price configuration is displayed as it has been defined in the table Contract -> Price Configurations.
Rule:*	Pull-down menu for the rule to be applied as a condition is selected (see description above). The entries available for selection are defined in the master data module Price Formula and include variants such as MTOW, Aircraft Type, Position Type etc. The rules available here are customized in cooperation with topsystem and can thus not be listed completely here.
Operation:*	Corresponding to the selected rule and to the values to be entered select an operation from the pull-down menu. The list displayed is a pre-selection of possible entries in accordance to the rule.
Low/High Level:	Enter the values, e.g. B777300 (if rule Aircraft Type) or TURN (if rule Handling Type). The entries correspond to the IDs in the master data.
Group:	Numerical values. Entering identical numerical values for multiple rules records (i.e. lines) connects these to combine their conditions. All conditions thus defined have to apply in order for a price configuration to be valid. Conversely, this means that different values in the field Group act as an OR condition. This means that only one of the rules has to apply for the price configuration to be valid.
Remark:	Individual remark for the indication of the price configuration
Contract/Service:	Contract/service to which the rule applies

Note that more than only one rule can be used to define conditions for price configurations. In addition to the rule Aircraft type used in Example 1 a-c, another parameter could be used for example to modify the price for a handling of a certain aircraft type if a delay exceeds 4 hours: An additional Rule entry 'ATA of the rotation' would define the additional rule 'Delay fee more than 4 h'. If the condition is matched, a surcharge would be added to the price defined for the handling of this aircraft type.

In the field Low Level, the delay time in hours is given in the format 0400. Note that time spans are always entered without a colon, while actual times of the day are entered with colon e.g. 04:00 would define four o'clock in the morning.

The definition of a condition is started by selecting the appropriate condition type from the pull-down menu Rules, e.g. aircraft type, MTOW, parking position etc. Then the mathematical operator to be applied is selected from the pull-down menu Operation (less than, more than, between etc.). If the Operation refers to one or more single values (e.g. less than, equal), these are entered in the field Low Level. Multiple entries are entered comma-separated. If the operation refers to a range of values (e.g. between), the two thresholds are entered in the fields Low Level and High Level.

Example: The procedure to restrict the validity of a price configuration to two specific aircraft types would be as follows. First, the entry Aircraft Type is selected from the pull-down menu Rules. As mathematical Operation, the option equal is selected. Finally, the two aircraft types (i.e. the aircraft type ID from the corresponding table) are entered in the field Low Level, separated by a comma.

It is, of course, also possible to define multiple conditions for a price configuration. This is done by creating and defining multiple data records. Please note that a price configuration only becomes valid if all defined conditions apply. Additional information about the complete price configuration functions can be found in chapter Summary of Creating a Contract with Price configurations.

The Table Contract -> Contract Items -> Price Configurations -> Package Breakdown

Only for price configurations with the parameter Unit Price it is possible to create entries in this detail table.

Following data is available for the detail table Contract -> Contract Items -> Price Configurations -> Package Breakdown:

Service:*	Dropdown box of Services of active services at this station (same as in Contract Items).
Package Item Price:*	If such a price is administered for the contract item, this contract item gets exported over the ERP interface with its quantity and the value of the Package Price.
Package Item Quantity:	Purely for information and reporting purposes
Remark:	Individual remark for the package breakdown

Concept of "Packages":

Several additional services (up to certain quantities) are combined into one package with a dedicated "package price". The services of the packages are captured as any other additional service.

If all quantities of these services (part of the package) are less or equal to the free quantity, then only the package appears on the invoice. Any quantities of such services beyond the included quantity get billed as always.

For packages, there will not be an invoice export, but the content of the package plus the package service will be exported. This appears on the invoice.

Operating principle:

The services of a package are exported even if they don't appear on the invoice, i.e. no quantity was rendered at all or the rendered quantity is within the quantity included in the package. In such a situation the unit price to be exported is the Package Item Price.
The package Service is exported, which appears at the invoice – including its VAT, if applicable.
Any rendered quantity of the same service beyond the quantity included in the package is calculated and exported with the normal unit price of this service – plus surcharges, discounts and VAT if applicable.

All prices will be interpreted as "Contract Currency" – same as for the contract items.

A new button is introduced in module Contract: Pushing it will trigger a crosscheck if the sum of all Package Item Prices equals the unit price of the package. The result of the check will be presented to the user in a pop-up window. The same check will be done by setting a contract to "Approved" (or any status with the contract state "Invoicing allowed"). This check will not block the contract from being set to "Approved" – it will only provide a warning to the user.

With this "concept of packages" the ERP interface will

1. ... continue to export packages (attribute Package ID contains a value). But in this case a "P" will be exported as Account 3 on the ERP interface irrespective of any value in Account 3 in the master data.

2. ... export all services defined in the package breakdown with price 0. The quantity is set to "1", the unit price to be exported in the attribute Unit Price on ERP interface is the Package Price. An "I" ("included in package") will be exported as Account 3 on the ERP Interface irrespective of any value in Account 3 in the master data. No surcharges/discounts or VAT will be calculated and exported.

3. ... export the items in the invoice currency and in local currency (in attribute Local Currency of the ERP interface).

4. ... continue to export all services with a price greater than 0 with their calculated unit price and surcharges/discounts (and VAT).

Example:

Contract -> Contract Item "Basic Handling" -> Price Configuration "Basic Handling B787": Unit Price 909.440, Package Id "SV13P"

Contract --> Contract Item "Basic Handling" --> Price Configuration "Basic Handling B787" --> Package Breakdown:

Package Item (Service)	Package Item Price	Remark
BTFC	225.000
WCHR	5.000
PAXS	13.000

909.440 is the total package price. 225.000, 5.000, 13.000 are the fixed package item prices (breakdown from the total price).

Note:
The invoice will remain as it is, i.e. it will show only those services with a price greater then 0: Any service with a quantity, which is included in the package, will not be shown on the invoice. So in the above example Basic Handling would appear on the invoice (incl. VAT if defined so), while WCHR, PAXS etc. would only appear at the invoice, if the quantities inside the packages are exceeded for a flight.

The quantities included in a package are configured using the "Free Quantity ..." or "Quantity for free ..." parameters.

The Table Contract -> Contract Items -> Rollout Configurations

This table combined with the detail table Contract -> Contract Items -> Rollout Configurations -> Rules allows to define per service under which conditions a service will be displayed (rolled out) to a flight event in module Services Flights.
For a detailed description of the available data fields please refer to chapter The Table Contract -> Contract Items -> Price Configurations.

The Table Contract -> Contract Items -> Rollout Configurations -> Rules

For a detailed description of the available data fields please refer to chapter The Table Contract -> Contract Items -> Price Configurations -> Rules.