972-836-7750 Request a demo Talk to an expert
Talk to an expert Request a demo Call sales 972-836-7750

EDIFACT message guide · Statistics and reporting

BOPBNK Bank transactions and portfolio transactions report

The UN/EDIFACT message banks use to report their own transactions, aggregated customer transactions and portfolio transactions to the balance of payments compiler.

Sent by
Bank
Received by
Balance of payments compiler, such as a central bank
Standard
UN/EDIFACT · Batch message
X12 equivalent
No direct equivalent

What is the EDIFACT BOPBNK message?

BOPBNK is the UN/EDIFACT bank transactions and portfolio transactions report. The directory defines it as a message banks can send to the balance of payments (BOP) compiler to report their own transactions, aggregated individual customer transactions and portfolio transactions, and it can also be used for reporting positions.

The balance of payments records a country's transactions with the rest of the world. Central banks or statistical offices compile it from reports by banks and other residents, and BOPBNK is the banks' channel for their part of that data.

How the EDIFACT BOPBNK message worksDiagram of the UN/EDIFACT BOPBNK Bank transactions and portfolio transactions report message. Bank sends it to balance of payments compiler, such as a central bank. It usually starts the exchange. Inside the UNB and UNH envelopes, the directory D.21A requires, in the start of message: BGM (Beginning of message) and DTM (Date/time/period) and body and segment groups: the required SG2 loop with NAD (Name and address) and the required SG3 loop with RFF (Reference) and the required SG4 loop with RCS (Requirements and conditions) and the required SG5 loop with MOA (Monetary amount) and LOC (Place/location identification). 3 conditional segment groups are listed by their trigger segment.How the EDIFACT BOPBNK message worksBank transactions and portfolio transactions report: who sends it, where it fits and what the directory marksmandatory1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeBOPBNKSENDERBankRECEIVERBalance of paymentscompiler, such as acentral bankCONTRL syntax report back, if agreedUSUALLY FOLLOWED BYNo business reply expected2 WHAT DIRECTORY D.21A REQUIRESInterchange: sender and recipient IDsUNB … UNZMessage BOPBNKUNH … UNTSTART OF MESSAGEBGMBeginning of messageDTMDate/time/periodBODY AND SEGMENT GROUPSMandatory group SG2 · repeats up to 9NADName and addressMandatory group SG3 · repeats up to 999RFFReferenceMandatory group SG4 · repeats up to 999RCSRequirements and conditionsMandatory group SG5 · repeats up to 9,999MOAMonetary amountLOCPlace/location identification+ 3 conditional groups, starting with:RFFGIRBlue box: mandatory segment group. Conditional groups are listed by the trigger segment that starts them; a group is sent only when its data applies.Conditional segments outside groups are not drawn.Structure: mandatory segments and groups in the UN/EDIFACT directory D.21A listing for BOPBNK. Your trading partner's implementation guide adds itsown requirements.
How the EDIFACT BOPBNK message worksDiagram of the UN/EDIFACT BOPBNK Bank transactions and portfolio transactions report message. Bank sends it to balance of payments compiler, such as a central bank. It usually starts the exchange. Inside the UNB and UNH envelopes, the directory D.21A requires, in the start of message: BGM (Beginning of message) and DTM (Date/time/period) and body and segment groups: the required SG2 loop with NAD (Name and address) and the required SG3 loop with RFF (Reference) and the required SG4 loop with RCS (Requirements and conditions) and the required SG5 loop with MOA (Monetary amount) and LOC (Place/location identification). 3 conditional segment groups are listed by their trigger segment.How the EDIFACT BOPBNKmessage worksBank transactions and portfolio transactionsreport: who sends it, where it fits and what thedirectory marks mandatory1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeBOPBNKSENDERBankRECEIVERBalance ofpaymentscompiler, suchas a centralbankCONTRL syntax report back, if agreedUSUALLY FOLLOWED BYNo business reply expected2 WHAT DIRECTORY D.21A REQUIRESInterchange: sender and recipient IDs(UNB … UNZ)Message BOPBNK (UNH … UNT)START OF MESSAGEBGMBeginning of messageDTMDate/time/periodBODY AND SEGMENT GROUPSMandatory group SG2 · repeats upto 9NADName and address+ required SG3 (RFF) and 3 conditionalgroups, starting with:RFFGIRBlue box: mandatory segment group. Conditionalgroups are listed by the trigger segment thatstarts them; a group is sent only when its dataapplies. Conditional segments outside groups arenot drawn.Structure: mandatory segments and groups in theUN/EDIFACT directory D.21A listing for BOPBNK.Your trading partner's implementation guide adds itsown requirements.

How to read this diagram: the top row shows who sends BOPBNK, to whom, and which messages usually come before and after it. The lower part shows what the directory D.21A itself requires: the envelopes around BOPBNK and the segments and segment groups it marks mandatory. Conditional groups are listed by their trigger segment rather than drawn in full. This is the directory's minimum, not a trading partner's requirement: a message implementation guide, such as an industry subset or a partner’s own guide, usually makes some conditional groups mandatory, restricts the codes and may use an older directory.

Expand diagram Download SVG

When it is used

  • Reporting banks' own cross-border transactions
  • Reporting aggregated customer transactions
  • Reporting portfolio transactions and positions

Where it fits in the message flow

This message BOPBNK Bank transactions and portfolio transactions report

No other message routinely comes directly before or after BOPBNK; it is exchanged when the business event occurs. If the partners agree, the receiver confirms each interchange with a CONTRL syntax and service report.

Structure

Mandatory segments in BOPBNK (directory D.21A)

In UN/EDIFACT directory D.21A, the BOPBNK message has 26 segment positions arranged in 7 segment groups. These are the segments and segment groups marked mandatory at message level, in order; a mandatory group is shown with the segment that starts it. Segments inside conditional groups are needed only when the group is used. This is the directory’s requirement, not your trading partner’s: each partner’s message implementation guide names the directory it uses, often an older one such as D.96A or D.01B where the structure can differ, makes some conditional segments mandatory and restricts the codes.

  • UNH
  • BGM
  • DTM
  • SG2 (NAD)
  • SG3 (RFF)
  • UNT

Practical example

BOPBNK in practice

A commercial bank compiles its monthly cross-border transactions, its customers' aggregated foreign payments by category and its securities portfolio movements. It sends the central bank a BOPBNK with the figures for the month, which the central bank combines with other reports to compile the national balance of payments.

Implementation

Implementation considerations for BOPBNK

  • Follow the compiler's reporting scheme and classifications.
  • Meet the reporting calendar set by the compiler.
  • Reconcile reported figures with accounting records.
  • Check whether the compiler still accepts EDIFACT or requires another format.

How ECOM helps

Automate BOPBNK with ECOM

Industry

Financial Services

Secure file transfer and B2B integration for banks and financial institutions.

Solution

Financial Document Automation

Automate invoices, remittances, payment files and bank statements from capture to posting.

Solution

EDI Integration

Exchange X12 and EDIFACT documents with partners and integrate them directly with your ERP.

Compare X12 and EDIFACT, or see answers to general questions in the EDI FAQ.

Related messages

Related statistics and reporting messages

All 8 statistics and reporting messages

Need help with BOPBNK?

ECOM maps, tests and monitors EDIFACT messages for your trading partners and integrates them with your ERP.

Request a Demo Contact us