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

DGRECA Dangerous goods recapitulation

The UN/EDIFACT message that gives a recapitulation of the dangerous goods on board a means of transport, such as a vessel.

Sent by
Carrier, vessel operator or agent
Received by
Port authority, terminal or other authority
Standard
UN/EDIFACT · Batch message
X12 equivalent
No direct equivalent

What is the EDIFACT DGRECA message?

DGRECA is the UN/EDIFACT dangerous goods recapitulation message. The directory defines it as a message specifying recapitulations of the dangerous goods on board a means of transport, for example a vessel.

A recapitulation summarizes the dangerous cargo on board, such as quantities by class and stowage, rather than declaring each consignment in detail. Ports and authorities use it to understand the overall hazard on a vessel, plan emergency response and check segregation, alongside the detailed notification sent with IFTDGN. It is typically used in port notifications.

How the EDIFACT DGRECA message worksDiagram of the UN/EDIFACT DGRECA Dangerous goods recapitulation message. Carrier, vessel operator or agent sends it to port authority, terminal or other authority. 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 body and segment groups: the required SG2 loop with TDT (Transport information), DTM (Date/time/period) and LOC (Place/location identification), the required SG3 loop with NAD (Name and address) and the required SG5 loop with DGS (Dangerous goods), FTX (Free text) and MEA (Measurements). 2 conditional segment groups are listed by their trigger segment.How the EDIFACT DGRECA message worksDangerous goods recapitulation: who sends it, where it fits and what the directory marks mandatory1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeDGRECASENDERCarrier, vesseloperator or agentRECEIVERPort authority,terminal or otherauthorityCONTRL syntax report back, if agreedUSUALLY FOLLOWED BYNo business reply expected2 WHAT DIRECTORY D.21A REQUIRESInterchange: sender and recipient IDsUNB … UNZMessage DGRECAUNH … UNTSTART OF MESSAGEBGMBeginning of messageBODY AND SEGMENT GROUPSMandatory group SG2 · repeats up to 1TDTTransport informationDTMDate/time/periodLOCPlace/location identificationMandatory group SG3 · repeats up to 1NADName and address+ required SG5 (DGS) and 2 conditional groups, starting with:RFFCTABlue 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 DGRECA. Your trading partner's implementation guide adds itsown requirements.
How the EDIFACT DGRECA message worksDiagram of the UN/EDIFACT DGRECA Dangerous goods recapitulation message. Carrier, vessel operator or agent sends it to port authority, terminal or other authority. 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 body and segment groups: the required SG2 loop with TDT (Transport information), DTM (Date/time/period) and LOC (Place/location identification), the required SG3 loop with NAD (Name and address) and the required SG5 loop with DGS (Dangerous goods), FTX (Free text) and MEA (Measurements). 2 conditional segment groups are listed by their trigger segment.How the EDIFACT DGRECAmessage worksDangerous goods recapitulation: who sends it,where it fits and what the directory marksmandatory1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeDGRECASENDERCarrier, vesseloperator oragentRECEIVERPort authority,terminal or otherauthorityCONTRL syntax report back, if agreedUSUALLY FOLLOWED BYNo business reply expected2 WHAT DIRECTORY D.21A REQUIRESInterchange: sender and recipient IDs(UNB … UNZ)Message DGRECA (UNH … UNT)START OF MESSAGEBGMBeginning of messageBODY AND SEGMENT GROUPSMandatory group SG2 · repeats upto 1TDTTransport informationDTMDate/time/periodLOCPlace/location identificationMandatory group SG3 · repeats upto 1NADName and address+ required SG5 (DGS) and 2 conditionalgroups, starting with:RFFCTABlue 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 DGRECA.Your trading partner's implementation guide adds itsown requirements.

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

  • Summarizing dangerous goods on board for a port call
  • Supporting emergency planning by authorities
  • Reporting totals by hazard class

Where it fits in the message flow

This message DGRECA Dangerous goods recapitulation

No other message routinely comes directly before or after DGRECA; 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 DGRECA (directory D.21A)

In UN/EDIFACT directory D.21A, the DGRECA message has 19 segment positions arranged in 5 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
  • SG2 (TDT)
  • SG3 (NAD)
  • SG5 (DGS)
  • UNT

Practical example

DGRECA in practice

Before a vessel arrives at a port, the carrier's agent sends the port authority a DGRECA summarizing the dangerous goods on board by class and quantity, with the stowage areas. The authority reviews the summary with the detailed notifications and confirms the berth and any special precautions.

Implementation

Implementation considerations for DGRECA

  • Keep the summary consistent with detailed dangerous goods notifications.
  • Follow each port's reporting rules and deadlines.
  • Use the hazard classes of the applicable dangerous goods regulations.
  • Update the recapitulation when cargo on board changes.

How ECOM helps

Automate DGRECA with ECOM

Industry

Trucking and Transportation

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

Solution

Logistics Automation

Automate tenders, status updates, freight invoices and warehouse orders with logistics partners.

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 DGRECA?

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

Request a Demo Contact us