Frames | No Frames
Return to Stylus Studio EDIFACT home page.|
Return to Stylus Studio EDIFACT D96A Messages page.
Bank transactions and portfolio transactions report message
This specification provides the definition of the Bank transactions and portfolio transactions report message (BOPBNK) to be used in Electronic Data Interchange (EDI) between trading partners involved in administration, commerce and transport.
1.1. Functional Definition
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.
1.2. | Field of Application
The Bank transactions and portfolio transactions report message may be used for both national and international trade. It is based on universal commercial practice and is not dependent on the type of business or industry.
The message intends to enable a resident bank to report on:
. their own transactions (including portfolio transactions) . the aggregated customer transactions . their own assets and liabilities position
All those reports are handled within the same structure. The difference stands only in the meanings of the segments. A clear distinction between them is simply realized by an adequate and simple use of qualifiers.
In consequence the message is structured in nested loops giving successively all the requested reports one after the other. The first loop giving the type of report, the nested loops giving the relevant details.
See UNTDID, Part 4, Chapter 2.6 UN/ECE UNSM - General Introduction, Section 1.
3. TERMS AND DEFINITIONS
See UNTDID, Part 4, Chapter 2.6 UN/ECE UNSM - General Introduction, Section 2.
4. MESSAGE DEFINITION
4.1. Data Segment Clarification
This section should be read in conjunction with the Branching Diagram and the Segment Table which indicate mandatory, conditional and repeating requirements.
0010 | UNH, Message header
A service segment starting and uniquely identifying a message. The message type code for the Bank transactions and portfolio transactions report message is BOPBNK.
Note: Bank transactions and portfolio transactions report messages conforming to this document must contain the following data in segment UNH, composite S009:
0020 BGM, Beginning of message
A segment to indicate the type and function of the message and to transmit its identifying number.
0030 DTM, Date/time/period
A segment to specify the date and, when required, the time at which the message has been created as well as specification of other process dates.
A group of segments to give auxiliary references and the relevant dates for the message itself.
0050 RFF, Reference
A segment to give another reference for the message.
0060 DTM, Date/time/period
A segment to give the period reported in the message (for example day/month/year).
A group of segments to give the identification of the reporting agent (generally the bank) or, possibly with a second occurrence, the identification of the bank on behalf of which the declaration is made.
0080 NAD, Name and address
A segment to identify the resident bank.
0090 CTA, Contact information
A segment to identify a person or a department for the party specified in the NAD segment and to whom communication should be directed.
0100 COM, Communication contact
A segment to give a communication number for the party identified in the NAD segment.
A group of segments to accommodate the details relevant to the transactions performed in one currency.
0120 LIN, Line item
A segment identifying the report line item by a current line number.
0130 MOA, Monetary amount
A segment to give the opening balance and the closing balance of the account and the currency.
A group of segments to give for each currency the relevant information.
0150 RCS, Requirements and conditions
A segment to give the nature of transaction or the type of position. A qualifier allows a clear distinction.
0160 FTX, Free text
A segment to give information in clear and free form to provide explanations about the nature of the transaction or about the position.
A group of segments to give the amount and details of each different nature of the transaction or the amount and details related to the position.
0180 MOA, Monetary amount
A segment to give the amount, and if necessary the currency, of the transaction or of the position.
A group of segments to give the identification and the quantity of security.
0200 GIR, Related identification numbers
A segment to identify the type of security (shares, bonds, etc).
0210 QTY, Quantity
A segment to specify the quantity of security.
0220 PRI, Price details
A segment to give the face value of the security.
A group of segments to give the references and dates of the transaction.
0240 RFF, Reference
A segment to give the serial number of the transaction.
0250 DTM, Date/time/period
A segment to give the day, month and year of the transaction.
0260 NAD, Name and address
A segment to give the identification of 2nd party (either the Payor, the Payee or another party). A second occurrence allows the identification of a 3rd party.
0270 LOC, Place/location identification
A segment to indicate one of the different countries involved.
A group of segments to specify the details of authentication.
0290 AUT, Authentication result
A segment to specify the details of any authentication (validation) procedure applied to the BOPBNK message.
0300 DTM, Date/time/period
A segment to identify the date and if necessary, the time of validation.
0310 UNT, Message trailer
A service segment ending a message, giving the total number of segments in the message and the control reference number of the message.
4.2. Data segment index (Alphabetical sequence by tag)
4.3. Message structure
4.3.1. Segment table
Return to Stylus Studio EDIFACT D96A Messages page.