Messages | EDIFACTORY

Leave a message

Messages of standard D97B

Following a list of all messages defined in the standard release D97B.

Show entries

Search:

Message	Description
APERAK	Application error and acknowledgement message The function of this message is: a) to inform a message issuer that his message has been received by the addressee's application and has been rejected due to errors encountered during its processing in the application. b) to acknowledge to a message issuer the receipt of his message by the addressee's application.
AUTHOR	Authorization message An Authorization Message is sent by the Ordering Customer (or Payor or Agent on behalf of the Ordering Customer) or by a third party having authority on the Ordering Customer's payments to the Ordered Bank, to authorize the Ordered Bank to execute a given financial transaction. This financial transaction might relate to both multiple messages like PAYMUL and DIRDEB, and single instruction messages like PAYORD and PAYEXT. An Authorization Message could also be sent from the Ordered Bank to the Ordering Customer or its Authorization Authority to request authorization for a given financial transaction. Throughout this document the term 'Original Message' refers to the message to be authorized.
BANSTA	Banking status message A BANSTA message is sent by a financial institution to its customer and/or vice versa and among financial institutions. It is used for all kind of enquiries, answers and status information at application level.
BAPLIE	Bayplan/stowage plan occupied and empty locations message A message to transmit information about equipment and goods on a means of transport, including their location on the means of transport. The message can be exchanged between (liner's) agents, tonnage centers, stevedores and ships masters/operators (see section 1.3 for more details).
BAPLTE	Bayplan/stowage plan total numbers message A message to transmit information about the total numbers of equipment and quantity of goods on a means of transport. The message can be exchanged between (liner's) agents, tonnage centers, stevedores and ships masters/operators (see section 1.3 for more details).
BOPBNK	Bank transactions and portfolio transactions report message The message could be sent by banks to BOP compiler for reporting of the banks' own transactions, aggregated individual customer transactions and portfolio transactions. The message could also be used for reporting the assets and liabilities positions of the banks.
BOPCUS	Balance of payment customer transaction report message Message sent by banks to the Balance of payment (BOP) compiler for reporting - one by one - individual customer transactions (debit and credit) processed during a specific time period. Actually, this transaction information can be distilled - one by one- from PAYORD / PAYMUL / PAYEXT and BOPINF messages respectively.
BOPDIR	Direct balance of payment declaration message The message can be sent by non-bank residents to report directly to the Balance of Payments (BOP) compiler on: . transactions via bank accounts held at a resident bank . transactions via bank accounts held at a non-resident bank . transactions and clearing via accounts with non-bank non-residents . foreign assets and liabilities . information in the context of a BOP-related survey (stocks and flows); for those countries which base their compilation of the BOP on surveys.
BOPINF	Balance of payment information from customer message Message sent by a payee to its bank on receipt of one specified amount as a settlement of a transaction with a non-resident. The Balance of Payment (BOP) compiler has to be informed of the transaction via the payee's bank.
CALINF	Vessel call information message Notice from a liner agent to a stevedore providing information concerning the expected arrival of a vessel and the expected cargo operations. This message is part of a total set of container-related messages. These messages serve to facilitate the intermodal handling of containers by streamlining the information exchange. The business scenario for the container messages is clarified in a separate document, called: 'Guide to the scenario of EDIFACT container messages'.

Showing 1 to 10 of 146 entries