BOPCUS Balance of payment customer transaction report message (D03B)

This is the standard EDIFACT D03B spec, with 8 loops and 29 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 (68 KB) Generate classes
The ediFabric .NET template, class TSBOPCUS. It needs the common segments, composites and codes of EDIFACT D03B, 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 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 D03B 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.

IDNameUsageMax use
UNHMessage HeaderOptional1
BGMBEGINNING OF MESSAGEMandatory1
DTMDATE/TIME/PERIODMandatory9
Loop RFFREFERENCEOptional9
RFFREFERENCEMandatory1
DTMDATE/TIME/PERIODOptional1
Loop NADNAME AND ADDRESSMandatory9
NADNAME AND ADDRESSMandatory1
CTACONTACT INFORMATIONOptional1
COMCOMMUNICATION CONTACTOptional9
FTXFREE TEXTOptional99
Loop LINLINE ITEMMandatory99999
LINLINE ITEMMandatory1
ATTATTRIBUTEOptional1
FIIFINANCIAL INSTITUTION INFORMATIONOptional9
DTMDATE/TIME/PERIODOptional1
Loop RFFREFERENCEOptional9
RFFREFERENCEMandatory1
DTMDATE/TIME/PERIODOptional1
Loop NADNAME AND ADDRESSOptional9
NADNAME AND ADDRESSMandatory1
CTACONTACT INFORMATIONOptional1
COMCOMMUNICATION CONTACTOptional9
Loop MOAMONETARY AMOUNTOptional1
MOAMONETARY AMOUNTMandatory1
CUXCURRENCIESOptional1
Loop RCSREQUIREMENTS AND CONDITIONSOptional99
RCSREQUIREMENTS AND CONDITIONSMandatory1
FTXFREE TEXTOptional99
MOAMONETARY AMOUNTOptional1
LOCPLACE/LOCATION IDENTIFICATIONOptional9
Loop GIRRELATED IDENTIFICATION NUMBERSOptional1
GIRRELATED IDENTIFICATION NUMBERSMandatory1
QTYQUANTITYOptional1
PRIPRICE DETAILSOptional1
CNTCONTROL TOTALOptional9
UNTMessage TrailerOptional1