BOPINF Balance of payment information from customer message (D05A)

This is the standard EDIFACT D05A spec, with 4 loops and 17 segment positions, as OpenEDI JSON, an ediFabric C# template and an ediFabric Native model. To change it for a trading partner, customize it in the EDI Spec Builder.

Loading the spec…

The spec as an OpenAPI 3 schema with x-openedi-* extensions, for ediFabric Native, ediFabric Cloud and the EDI Spec Builder. Download OpenEDI (50 KB) Generate classes

The ediFabric .NET template, class TSBOPINF. It needs the common segments, composites and codes of EDIFACT D05A, one download for every transaction in the version. Download C# (1 KB) Common files (57 KB)

The intermediary model ediFabric Native loads with set_map. Native supports X12 today, and EDIFACT is coming. Download Native (1 KB)

Use the BOPINF spec in your code

ediFabric .NET

Add the C# template and its common files to your project, or reference the template NuGet package, and read BOPINF files into TSBOPINF objects. See ediFabric .NET.

ediFabric Native

Native supports X12 today, and EDIFACT is coming. When it's available, map version D05A to this Native model with set_map to parse BOPINF files to JSON from Python, Java, C or C#. See ediFabric Native.

OpenEDI

Select Customize in Spec Builder to copy the spec under your own name, change it for your partner, and parse files against it in EdiNation, ediFabric Native or ediFabric Cloud. Read about OpenEDI.

Generate BOPINF classes in Python, Java, Node.js, Go, Rust or C

The OpenEDI file describes each BOPINF as JSON. To work with BOPINF data as typed objects, generate classes from the OpenEDI file in your language; the root class is TSBOPINF. The classes keep the loops, segments, lengths and code lists, but not the EDI data formats. Read more in Generate a class from OpenEDI.

Python: datamodel-code-generator. Node.js: openapi-typescript. Java, Go, Rust and C: OpenAPI Generator.

BOPINF structure

Loops and segments of the standard BOPINF, with their usage and maximum repeats.

ID	Name	Usage	Max use
UNH	Message Header	Optional	1
BGM	BEGINNING OF MESSAGE	Mandatory	1
DTM	DATE/TIME/PERIOD	Mandatory	9
Loop RFF	REFERENCE	Optional	9
RFF	REFERENCE	Mandatory	1
DTM	DATE/TIME/PERIOD	Optional	1
Loop NAD	NAME AND ADDRESS	Mandatory	9
NAD	NAME AND ADDRESS	Mandatory	1
CTA	CONTACT INFORMATION	Optional	1
COM	COMMUNICATION CONTACT	Optional	9
FTX	FREE TEXT	Optional	99
Loop RFF	REFERENCE	Optional	999
RFF	REFERENCE	Mandatory	1
DTM	DATE/TIME/PERIOD	Optional	1
Loop RCS	REQUIREMENTS AND CONDITIONS	Mandatory	99
RCS	REQUIREMENTS AND CONDITIONS	Mandatory	1
FTX	FREE TEXT	Optional	99
MOA	MONETARY AMOUNT	Optional	1
LOC	PLACE/LOCATION IDENTIFICATION	Optional	9
CNT	CONTROL TOTAL	Optional	9
UNT	Message Trailer	Optional	1