In this table, the optional contract services actually provided for an event are recorded and edited.

The table displays a list of all services included in the contract(s) assigned to an event which are marked as Additional. These services are included in a contract, but are rendered and accounted for only if actually provided for a customer.

Please note that the recording of optional services is subject to influences which are sometimes not openly visible at first glance: Depending on the definition in the master data, an optional service can be subject to a "price formula" which influences the recording and price calculation. Please keep this in mind when reading the following descriptions.

An optional service is generally recorded by entering the actual Captured Quantity of service Units in the corresponding data field. After the Captured Quantity for an optional services has been entered, you can click the button Save followed by Calculate Charges to calculate the total cost for this service (note that all service charges are calculated if you use this button in the table Events > Contracts). This automated calculation process not only takes the basic pricing (amount x single unit price) into account, but also regards optional "price formulas" which might apply to the service. Details about price formulas can be found in chapter Services, Price Calculation and Internal Accounting – Interaction of the Tables).

Example: One of the typical optional services is de-icing, which is only requested by the customer if weather conditions make it necessary. Generally, de-icing consists of two cost factors, namely the basic rendering of the service and the litres of de-icing fluid used in the process. Thus, a price formula including "basic price + litres*litre price" is normally used for the background calculation process.

Note that there is a decisive difference between the automatically filled Calc. Quantity and the manually recorded Captured Quantity. The Calc. Quantity always refers to the number of individual services, while the Captured Amount always refers to the number of units referenced to the service.

Example: Referring to the example above, the de-icing process is counted as a Calc. Quantity of one (1) service, although the manually Captured Quantity may be any number of units (litres in this case) provided for this service.

In contrast to this, other services might be defined as a single Amount for each Unit in the Price Formula master data.

Example: A simple handling charge "per unaccompanied minor" might be defined as one single service without any price formula behind it. Thus, a Captured Quantity of 50 unaccompanied minor "units" would result also in an Amount of 50 after the calculation process.

This means that the relation of Calc. Quantity and Captured Quantity always depends on a potential price formula. Note that some services are recorded automatically from data already captured elsewhere.

Example: The number of passengers is recorded in the flight planning module and automatically imported to the service recording during the calculation process.

Finally, it is important to keep in mind that price formula mechanisms often influence the recording of optional services. Nevertheless, the logic behind the process becomes immediately obvious when looking at the service master data.

Following data is available for recording optional services (note that some of the data cannot be edited because it is part of the corresponding contract):

Station:	Station to which this entry applies; this column is only shown if you are logged in above station level.
Contract:	Complete name of the service as defined in the master data module Contract
Autoid Charge:	An automatically assigned identification marker uniquely defining an event for software processing
Additional Service:	Name of the Additional Service
Service Name (Customer):	Overwrites the service name (as defined in the master data module Contracts > Services) on the invoice
Begin/End:	Period of validity for the contract
Rendered Quantity:	Manual entry that will take into consideration possible free quantities defined in the contract.
Imp. Quantity:	Quantity imported from the external system via interface.
Calc. Quantity:	Automatically calculated quantity of the service
Capt. Quantity:	Captured quantity. This entry overwrites all other quantities
Quantity:	Quantity with all given changes is displayed here. Actual quantity of the service
Unit:	Unit of service
Calc. Surch./Disc.:	Automatically calculated Percentage for cancellation /surcharge from the contract
Capt. Surch./Disc.:	Captured surcharge/Percentage for cancellation. This entry overwrites all other surcharges and Percentage for cancellation s.
Surch./Disc.:	Surcharge/Percentage for cancellation with all given changes is displayed here. This is the actual surcharge/Percentage for cancellation of the contract
Calc. Price:	Automatically calculated price of the contract
Capt. Price:	Captured price. This price overwrites all other prices
Single:	Single price of the service
Total:	Price with all given surcharges and Percentage for cancellations. This is the actual price of the service.
Disbursement [%]:	Disbursement % is either defined at the service in master data or at contract level and displayed here. It is also possible to overwrite the predefinition by entering a new value.
Calc. VAT:	If a VAT has been included in a service, it is listed here.
Capt. VAT:	If applicable, a VAT percentage is entered here. Entry overwrites all other VATs.
VAT:	Actual VAT of the service.
Inv. Rec. Charge:	Invoice recipient
Charge State:	Current charge status of the service. This status is assigned automatically depending on the processes which have been performed. Following states are available: Initial – basic status after the contract has been assigned, Calculated – the service price has been calculated for the event (after the Calculate Charges has been used), Invoiced – the event and the contract charges have already been invoiced in the module Billing.
Inv.-Type:*	Type of the invoice. Following variants are available: Initial Invoice – normal billing procedure, Credit – an erroneously recorded item has been credited to the customer, Debit – the customer is charged with an item which has been rendered but was not accounted for an invoice.
Doc. No.:	In case the monitoring of rendered services is done via printed work order it is then possible to enter manually in this field the reference number of the corresponding document.
IATA Charge Code:	Code as defined for the IATA SIS interface, e.g. Baggage, De-icing, Ramp handling
Internal Status:	Either set in the Airline Web Portal or directly in the application. Two possibilities: In Progress or Closed.
Airline Status:	This status can only be set by the airline/customer via the Airline Web Portal. Two possibilities: Approved or Rejected.
Invoice:	Invoice number
Invoice Cycle:	Reference number of the Invoice Cycle
Internal Remark:	Remark for internal use only. In contrast to the entry under Remark, the Internal Remark is not printed out anywhere.
Invoice Remark:	Freely definable remark can be entered here
Free Quantity:	Number of free quantities defined in the contract
Calc. Inv. Rec. Charge:	In this field the software automatically shows the invoice recipient defined in a handling contract which is assigned to a flight event. If no contract is assigned or an assigned contract does not include an invoice recipient, the software enters the aircraft owner here. Note that it is possible to manually change the recipient in the pull-down menu Capt. Inv. Rec. Charge. If no recipient is stated in the contract or no aircraft owner can be identified, this field remains empty.
Capt. Inv. Rec. Charge:	This pull-down menu can be used to manually change the invoice recipient if necessary, or to enter a recipient if no invoice recipient could be identified from a handling contract or aircraft. Manually entered recipients always have priority over automatically identified recipients. Note that invoice recipients available here for selection are defined in the master data table Customer of the master data module Contract.
Last Changed:	Date and time when the data record was changed last (filled automatically)
Modified By:	Name of the last user who changed the data record (filled automatically)

The Table Flight Events -> Additional Services -> Discrepancies

This table is dedicated to the discrepancies raised either by the customer in the Airline Web Portal or internally at the Flight Event level. Each entry represents one statement in the discussion.
To start an approval flow it is necessary to generate first a discrepancy note by clicking on function button Generate Discrepancy Note.
For a detailed description of the data fields please refer to chapter The Table Flight Events -> Discrepancies.