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 · Customs and regulatory

GOVCBR Government Cross Border Regulatory

The UN/EDIFACT message a declarant uses to submit legally required declarations or regulatory information to cross-border agencies.

Sent by
Declarant
Received by
Cross-border regulatory agency, typically through a single window
Standard
UN/EDIFACT · Batch message
X12 equivalent
No direct equivalent

What is the EDIFACT GOVCBR message?

GOVCBR is the UN/EDIFACT government cross border regulatory message. The directory explains that, for cross-border transactions, it lets a declarant submit a legally required declaration or other regulatory information to a cross-border regulatory agency, typically operating in a single window environment, and lets agencies exchange such information among themselves.

A single window lets traders submit data once for customs, health, agriculture and other agencies. GOVCBR is designed as a general regulatory message for that environment, based on harmonized data models rather than one agency's form.

How the EDIFACT GOVCBR message worksDiagram of the UN/EDIFACT GOVCBR Government Cross Border Regulatory message. Declarant sends it to cross-border regulatory agency, typically through a single window. It usually starts the exchange. It is usually followed by CUSRES. Inside the UNB and UNH envelopes, the directory D.21A requires, in the start of message: BGM (Beginning of message), body and segment groups: UNS (Section control) and HYN (Hierarchy information) and end of message: UNS (Section control). 16 conditional segment groups are listed by their trigger segment.How the EDIFACT GOVCBR message worksGovernment Cross Border Regulatory: who sends it, where it fits and what the directory marks mandatory1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeGOVCBRSENDERDeclarantRECEIVERCross-borderregulatory agency,typically through asingle windowCONTRL syntax report back, if agreedUSUALLY FOLLOWED BYCUSRESCustoms response2 WHAT DIRECTORY D.21A REQUIRESInterchange: sender and recipient IDsUNB … UNZMessage GOVCBRUNH … UNTSTART OF MESSAGEBGMBeginning of messageBODY AND SEGMENT GROUPSUNSSection controlHYNHierarchy information+ 16 conditional groups, starting with:LOCGORSTSNADDOCRCSAJTERCINPGIRTAXPACTMPTDTSEQCNIEND OF MESSAGEUNSSection controlBlue 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 GOVCBR. Your trading partner's implementation guide adds itsown requirements.
How the EDIFACT GOVCBR message worksDiagram of the UN/EDIFACT GOVCBR Government Cross Border Regulatory message. Declarant sends it to cross-border regulatory agency, typically through a single window. It usually starts the exchange. It is usually followed by CUSRES. Inside the UNB and UNH envelopes, the directory D.21A requires, in the start of message: BGM (Beginning of message), body and segment groups: UNS (Section control) and HYN (Hierarchy information) and end of message: UNS (Section control). 16 conditional segment groups are listed by their trigger segment.How the EDIFACT GOVCBRmessage worksGovernment Cross Border Regulatory: whosends it, where it fits and what the directorymarks mandatory1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeGOVCBRSENDERDeclarantRECEIVERCross-borderregulatoryagency,typicallythrough a singlewindowCONTRL syntax report back, if agreedUSUALLY FOLLOWED BYCUSRESCustoms response2 WHAT DIRECTORY D.21A REQUIRESInterchange: sender and recipient IDs(UNB … UNZ)Message GOVCBR (UNH … UNT)START OF MESSAGEBGMBeginning of messageBODY AND SEGMENT GROUPSUNSSection controlHYNHierarchy information+ 16 conditional groups, starting with:LOCGORSTSNADDOCRCSAJTERCINPGIRTAXPAC…END OF MESSAGEUNSSection controlBlue 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 GOVCBR.Your trading partner's implementation guide adds itsown requirements.

How to read this diagram: the top row shows who sends GOVCBR, 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 GOVCBR 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

  • Submitting declarations to a national single window
  • Providing data required by several border agencies at once
  • Exchanging regulatory data between agencies

Where it fits in the message flow

This message GOVCBR Government Cross Border Regulatory
Usually followed by CUSRES Customs response

Structure

Mandatory segments in GOVCBR (directory D.21A)

In UN/EDIFACT directory D.21A, the GOVCBR message has 1147 segment positions arranged in 312 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
  • UNS
  • HYN
  • UNS
  • UNT

Practical example

GOVCBR in practice

An importer of food products submits its import data through a national single window. Its broker sends one GOVCBR with the consignment, the goods, origin, health certificates and customs details. The single window passes the relevant data to customs and the food safety agency, which each return their decisions.

Implementation

Implementation considerations for GOVCBR

  • Check whether the single window accepts GOVCBR or another format.
  • Map data to the harmonized data model the agencies use.
  • Include all agencies' required data in one submission.
  • Track decisions from each agency separately.

How ECOM helps

Automate GOVCBR with ECOM

Industry

Trucking and Transportation

Load tenders, responses, status and freight invoices for carriers, brokers and shippers, integrated with the TMS.

Industry

Food and Beverage

Grocery and foodservice EDI for food and beverage manufacturers, with lot, date and inventory data.

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 customs and regulatory messages

All 14 customs and regulatory messages

Need help with GOVCBR?

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

Request a Demo Contact us