General Information Information on the transmitted data. Business unit Location of a branch office. Place/ Location code UN/Locode; e.g. the location of the user's branch office. Location name. If there is no UN/LoCode available for this place, alternatively the name can be set. Communication information. Contains information on sender, recipients and creation time. Communication participants Up to 11 entries can be sent: SENDER - mandatory with DAKOSY-code EDI_PROVIDER - optional; 'DAKOSY', if message should be processed by DAKOSY RECIPIENT - mandatory with DAKOSY-Code. Maximum of nine entries is possible. Date and time of message creation. automatic processing the customer can a number of automatic processing features for the transport order rcv = automatic receiving fwd = automatic forwarding (requires automatic receiving) qst = automatic retrieval of the quay status (requires a specification of the loading /discharge location) cfd = automatic forwarding depending on a positive quay status (requires automatic receiving and retrieval of the quay status) type type of invoice B = bill C = credit item customer number container number Format: bytes content 1 - 4 Prefix 5 - 12 Number dispatch date dispatch date or date the service was rendered currency currencey used in the invoice data gross amount sum of the individual invoice line items including tax total amount sales tax total amount of sales tax (sum of the invoice line items sales tax) reference type type of reference used TransportOrder Invoice reference version version of the message / message element ascending sequence (not necassarily continuous) starting with version 01 (new transport order etc) - all versions above 01 are interpreted as a revision of previously communicated data type type of invoice line item F = fee R = rebate code coded description of the invoice line item mutually agreed codes description textual description of the invoice line item percentage sales tax percentage of sales tax to be added to the amount specified in the invoice line item value in percent amount amount of the invoice line item invoice number invoice date General Message definition Describes the contents of a message (metainfo and data) User information Information on the user who sent the message. Metainfo Contains information concerning transaction type, communication parties etc. Transaction type Specifies the transaction type (GM01, AB01 etc.). Only one transaction per file is allowed. Different types must be sent in separate files. Application name Name of the application served by the interface. E.g. SEEDOS, ATLAS Testflag 0 - false (default); 1- true; transmission for test purpose Number of messages Number of messages (elements) that are collected in the transmitted file. DAKOSY-code 4-letter code identifying the participant application usage Alias code. Describes how the participant is identified in another system, e.g. DAK as DAKOSY-code. Other identifiers are not specified yet. participant name just for informal use Password Needs only to be set if required by the specified role. SENDER RECIPIENT EDI_PROVIDER Transaction name IncoiceData Message provider name of the party who is responsible for the underlying scheme. Version of message definition Message type Code defined by the provider for the specified transaction, e.g. GM01 = customs declaration AC02 = transport order Transaction information Phone number plain text without validation. Either phone number or e-mail address must be filled if the user-element is transmitted.