midoco.de About us Jobs Support Contact
Midoco
Booking Sources & Data

GDS Remarks — Billing & invoicing

Remarks controlling invoice creation, billing information and print behaviour.

← All topics
Booking Sources & Data

GDS Remarks — Billing & invoicing

Remarks controlling invoice creation, billing information and print behaviour.

Show VAT Information on Invoice

This remark applies to lcr and DERPART orgunits. If it is present then the vat information will be shown on the invoice otherwise it will not be shown.

 AMADEUS

Prevent Printing Segment Remark

HIDESEGMENT will set the prevent printing flag for specified segments (if not specified for all segments)

AMADEUS

Travelport

SABRE

DBI - Descriptive Billing Information

The DBI information is saved into orders_dbi_infos table. These information are assigned to a booking(sell_item) and may be assigned to a traveller(sell_passenger), too.

The key of  the DBI is the word after the DBI/. (i.e. AE, AU,..). The DBI value must not exceed 64 characters length.

DBI/AE – Billing unit

AMADEUS

Travelport

SABRE

DBI/AK – Action number

AMADEUS

Travelport

SABRE

DBI/AU – Order number

AMADEUS

Travelport

SABRE

DBI/BD – Date processed

AMADEUS

Travelport

SABRE

DBI/DS – Office/Agency

AMADEUS

Travelport

SABRE

DBI/IK – Account number

AMADEUS

Travelport

SABRE

DBI/KS – Costcentre

AMADEUS

Travelport

SABRE

DBI/PK – Personal code

AMADEUS

Travelport

SABRE

DBI/PR – Project number

AMADEUS

Travelport

SABRE

DBI/RZ – Travel destination

AMADEUS

Travelport

SABRE

CCZU+ 

-> does not generally apply to Midoco´s FIBU mode

-> applies to FIBU units only which are using the FIBU business mode (e.g. with AMEX BT CCs with additional data)

The CCZU information is saved into orders_dbi_infos table. These information are assigned to a booking(sell_item) and may be assigned to a traveller(sell_passenger), too.

The value must not exceed 17 characters length.

AMADEUS

Travelport

SABRE

The number of the CCZU Remark will be mapped by midoco to the CC Reference Data Field Definitions delivered by Amex or Degussa or other parties, which Midoco shall deliver enhanced credit card information to.

VERK Billing Information

-> does not apply to Midoco´s FIBU mode

The VERK information is saved into orders_dbi_infos table. These information are assigned to a booking(sell_item) and may be assigned to a traveller(sell_passenger), too.

The key of  the DBI will be specified for each information. The DBI value must not exceed 64 characters length.

Internal cost centre

Saved as order dbi info with key : VERK_COST_CENTRE.

AMADEUS

Travelport

SABRE

Customer cost centre

Saved as order dbi info with key : VERK_CUST_COSTCENT

AMADEUS

Travelport

SABRE

or

Staff (Personal) number

Saved as order dbi info with key: VERK_CUST_PERS_NO

AMADEUS

Travelport

SABRE

or

Project number

Saved as order dbi info with key: VERK_CUST_PROJ_NO

AMADEUS

Travelport

SABRE

or

Funding

Saved as order dbi info with key: VERK_FUNDING

AMADEUS

Travelport

SABRE

Order date

Saved as order dbi info with key: VERK_ORDER_DATE

AMADEUS

Travelport

Remark Entry in Travelport:

Resulting Entry in MIR message

SABRE

Internal order number

Saved as order dbi info with key: VERK_ORDERER_NO

AMADEUS

Travelport

Remark Entry in Travelport:

Resulting Entry in MIR message

SABRE

Orderer

Saved as order dbi info with key: VERK_ORDERER

AMADEUS

Travelport

Remark Entry in Travelport:

Resulting Entry in MIR message

SABRE

Remark1

Saved as order dbi info with key: VERK_REMARK1

AMADEUS

Travelport

Remark Entry in Travelport:

Resulting Entry in MIR message

SABRE

Remark2

Saved as order dbi info with key: VERK_REMARK2

AMADEUS

Travelport

Remark Entry in Travelport:

Resulting Entry in MIR message

SABRE

Remark3

Saved as order dbi info with key: VERK_REMARK3

AMADEUS

Travelport

Remark Entry in Travelport:

Resulting Entry in MIR message

SABRE

Print Invoice Automatically

-> does not apply to Midoco´s FIBU mode

Prerequisites

a) The module GDS_AUTOM_INVOICE_PRINT is assigned to the orgunit

b) The customer is not using collective invoice print

c) Remark "VERK:VB:K" or "VERK:VB:R" or "SYS:VB:K" or "SYS:VB:R" is present in the AIR/MIR

d) At least a fee was generated for the flight or the remark TAF:N is present (to indicate that no fee present on purpose)

e) The importing user or its orgunit owns a print queue.

f)  If the Remark “VERK:VB:Z orSYS:VB:Z" orVB:Z" exists the receipt will not be sent / printed, but the document is generated. This does only work, if VAT documentation is provided is by creditcard company, Otherwise, the receipt will be sent or printed.

g) If a Remarks like "RMB*[.*]VB:R[.*]", "RMB(C)SYS+:VB:R[.*]", "RM B*VB:R[.*]" or "RMR(C)VB:R[.*]" are used, the automatic print will not take place.

AMADEUS

or(used only for LCR)

Travelport

Remark Entry in Travelport:

or

Resulting Entry in MIR message

or

SABRE

Resulting Entry in IUR message 

Prepare Invoice but do not print/send it, yet

To prepare the invoice. It creates billing positions for the order and already puts them on an invoice document. However, this invoice document needs to be printed/sent via email manually by the user.

AMADEUS

Travelport

Remark Entry in Travelport:

Resulting Entry in MIR message

SABRE

Add Billing Positions for an order onto a prepared Bulk Invoice

Using the following remark requires a bulk invoice setup for the respective customer in the Midoco CRM profile to be in place.

The remark takes care of putting the billing positions for this order to the matching bulk invoice (if already existing) or of creating a new bulk invoice placing the billing positions there.

AMADEUS

Travelport

Remark Entry in Travelport:

Resulting Entry in MIR message

SABRE

Stop invoice 

This Remark prevents automatic invoice creation as well as print and adds an automatic billing print lock (visible in the order).

AMADEUS 

Travelport 

Sabre 

Manage Content to be printed

Print passengers and segments

AMADEUS

Print only passengers and ticket number

AMADEUS

Print only segments and ticket number

AMADEUS