The Module Services Events

Following data is captured for each event service:

  • Station:*

Station to which this configuration applies; this column is only shown if you are logged in above station level.

  • Autoid:

Automatically generated, unique sequential number which is used as an identifier for the data record.

  • Name (*):

Name of non-flight-event in plain text

  • OT (*):

For flight events, the BTA/BTD is shown here. For non-flight events, the actual time they have taken place is displayed.

  • State:

Shows the state of the service

  • Contract:

Shows the kind of contract

  • Open Charges:

Shows the open charges

  • Imp. Recipient:

Recipient imported from the external system via interface.

  • Calc. Recipient:

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. Rec. If no recipient is stated in the contract or no aircraft owner can be identified, this field remains empty.

  • Capt. Recipient:

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.

  • Invoice Recipient:

The actual invoice recipient depending on the entries in the fields Calc. Rec. and Capt. Rec.

  • Rec. Cash:

This checkbox shows if a customer is liable to pay cash or is billed in the general invoicing procedure. This definition is set for each customer in the table Customer > Financial Profile master data module Contracts. Note that this mark must be available in order for a cash bill to be printed! If you have to create a cash invoice for an airline which is not marked as cash-paying, you first have to change the setting in the master data.

  • Pay on Spot:*
    (tab available depending on configuration)

If this flag is set to active, a credit customer is handled as a cash payer.

  • Rec. Prepaid:
    (tab available depending on configuration)

If this flag is set, the corresponding billing events get highlighted similar to the color of the cash payers.

  • Cash Hotrun Done:

This checkbox shows if the Hotrun was done

  • Invoice Date:

After a handling event has been paid by cash, the time and date when the cash invoice Hotrun has been performed is automatically entered here.

  • Mode of Payment:

In this pull-down menu the payment option the customer selects for a cash payment can be selected, i.e. cash, a variety of credit cards etc. The options available here can be defined in the table Mode of Payment in the master data module Billing.

  • Has Open Discr.:

Indicates if there are open discrepancies or not

  • Status Internal:

Internal (handling company) status of a discrepancy: May be Closed or In Progress.

  • Status Customer:

Airline status of a discrepancy. This status can only be set by the airline/customer via the Airline Web Portal. Two possibilities: Approved or Rejected.

  • Service Dependency Warning:*

Flag that is automatically set if a primary service with a quantity greater 0 has no associated service (with quantity greater 0).

  • Service Dependencies:

Each of the checked primary services of the flight event with their quantity and the associated service with its quantity is listed here (one line per service, multiline text field in edit panel).

  • Service Dependency Remark:

Remarks for the billing officer in the backoffice can be entered in the MSR. These remarks will be shown here.

  • Remark:

Freely definable comment

  • Blocked:*

The flag is set automatically by the system whenever an error occurs during the automatic price calculation procedure. In this case, the error is listed in the field Remark Calculation.
If you want to exclude an event from this automated procedure, you can mark the Block flag

  • Remark Calculation:

Freely definable comment for the calculation

  • Cash Payer c/o:

Care of (c/o) of cash payer (for invoice)

  • Cash Payer Name:

Name of cash payer (for invoice)

  • Cash Payer Street/P.O.Box:

Street or P.O. Box of cash payer

  • Cash Payer ZIP:

Zip code of cash payer (for invoice)

  • Cash Payer City:

City of cash payer (for invoice)

  • Cash Payer Country:

Country of cash payer (for invoice)

  • Reg:
    (tab available depending on configuration)

Registration of aircraft of the flight event

  • Cash Payer Contact Person:
    (tab available depending on configuration)

It is possible to override the default cash invoice contact by selecting a Cash Payer Contact Person. Only users with the Billing flag set can be selected, just like for the invoice cycle Contact Person.

  • Parkposition:
    (tab available depending on configuration)

Parking position (from table Master Data GeneralParking Positions)

  • Handling Type:
    (tab available depending on configuration)

Parking position (from table Master Data GeneralHandling Type)

  • 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)

Please also consider the following video:

MSR - Invoice-cycle and Non-flight-event: