BOPCUS Balance of payment customer transaction report message (D95A)

This is the standard EDIFACT D95A spec, with 9 loops and 27 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 (43 KB) Generate classes

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

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

Use the BOPCUS 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 BOPCUS files into TSBOPCUS objects. See ediFabric .NET.

ediFabric Native

Native supports X12 today, and EDIFACT is coming. When it's available, map version D95A to this Native model with set_map to parse BOPCUS 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 BOPCUS classes in Python, Java, Node.js, Go, Rust or C

The OpenEDI file describes each BOPCUS as JSON. To work with BOPCUS data as typed objects, generate classes from the OpenEDI file in your language; the root class is TSBOPCUS. 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.

BOPCUS structure

Loops and segments of the standard BOPCUS, 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	3
Loop RFF	REFERENCE	Optional	2
RFF	REFERENCE	Mandatory	1
DTM	DATE/TIME/PERIOD	Optional	1
Loop NAD	NAME AND ADDRESS	Mandatory	2
NAD	NAME AND ADDRESS	Mandatory	1
CTA	CONTACT INFORMATION	Optional	1
COM	COMMUNICATION CONTACT	Optional	5
Loop LIN	LINE ITEM	Mandatory	9999
LIN	LINE ITEM	Mandatory	1
FII	FINANCIAL INSTITUTION INFORMATION	Optional	1
DTM	DATE/TIME/PERIOD	Optional	1
Loop RFF	REFERENCE	Optional	2
RFF	REFERENCE	Mandatory	1
DTM	DATE/TIME/PERIOD	Optional	1
Loop NAD	NAME AND ADDRESS	Optional	4
NAD	NAME AND ADDRESS	Mandatory	1
CTA	CONTACT INFORMATION	Optional	1
COM	COMMUNICATION CONTACT	Optional	5
Loop MOA	MONETARY AMOUNT	Optional	1
MOA	MONETARY AMOUNT	Mandatory	1
CUX	CURRENCIES	Optional	1
Loop DOC	DOCUMENT/MESSAGE DETAILS	Optional	10
DOC	DOCUMENT/MESSAGE DETAILS	Mandatory	1
DTM	DATE/TIME/PERIOD	Optional	1
Loop RCS	REQUIREMENTS AND CONDITIONS	Mandatory	10
RCS	REQUIREMENTS AND CONDITIONS	Mandatory	1
FTX	FREE TEXT	Optional	10
MOA	MONETARY AMOUNT	Optional	1
LOC	PLACE/LOCATION IDENTIFICATION	Optional	4
Loop AUT	AUTHENTICATION RESULT	Optional	1
AUT	AUTHENTICATION RESULT	Mandatory	1
DTM	DATE/TIME/PERIOD	Optional	1
UNT	Message Trailer	Optional	1