EDIFACT message guide · Transport

VERMAS Verified gross mass

The UN/EDIFACT message used to submit the verified gross mass of packed containers to carriers and terminals.

Sent by
Shipper, forwarder or weighing party
Received by
Ocean carrier or terminal
Standard
UN/EDIFACT · Batch message
X12 equivalent
No direct equivalent

What is the EDIFACT VERMAS message?

VERMAS is the UN/EDIFACT verified gross mass message. The directory explains that it can be used by different parties at different points in a transport chain and is not tied to one process step; for a packed container shipped by sea, it lets parties submit the container's verified gross mass.

Under the SOLAS convention, a packed export container may not be loaded onto a ship without a verified gross mass provided by the shipper. VERMAS carries the weight, the method used to obtain it, the responsible party and the signature, so carriers and terminals can confirm compliance before loading.

How the EDIFACT VERMAS message worksDiagram of the UN/EDIFACT VERMAS Verified gross mass message. Shipper, forwarder or weighing party sends it to ocean carrier or terminal. It usually follows IFTMBC. It is usually followed by COPRAR. Inside the UNB and UNH envelopes, the directory D.21A requires, in the start of message: BGM (Beginning of message). 3 conditional segment groups are listed by their trigger segment.How the EDIFACT VERMAS message worksVerified gross mass: who sends it, where it fits and what the directory marks mandatory1 WHERE IT FITSUSUALLY FOLLOWSIFTMBCBooking confirmationVERMASSENDERShipper, forwarder orweighing partyRECEIVEROcean carrier orterminalCONTRL syntax report back, if agreedUSUALLY FOLLOWED BYCOPRARContainerdischarge/loadingorder2 WHAT DIRECTORY D.21A REQUIRESInterchange: sender and recipient IDsUNB … UNZMessage VERMASUNH … UNTSTART OF MESSAGEBGMBeginning of messageBODY AND SEGMENT GROUPS+ 3 conditional groups, starting with:RFFNADEQDBlue 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 VERMAS. Your trading partner's implementation guide adds itsown requirements.
How the EDIFACT VERMAS message worksDiagram of the UN/EDIFACT VERMAS Verified gross mass message. Shipper, forwarder or weighing party sends it to ocean carrier or terminal. It usually follows IFTMBC. It is usually followed by COPRAR. Inside the UNB and UNH envelopes, the directory D.21A requires, in the start of message: BGM (Beginning of message). 3 conditional segment groups are listed by their trigger segment.How the EDIFACT VERMASmessage worksVerified gross mass: who sends it, where it fitsand what the directory marks mandatory1 WHERE IT FITSUSUALLY FOLLOWSIFTMBCBooking confirmationVERMASSENDERShipper,forwarder orweighing partyRECEIVEROcean carrier orterminalCONTRL syntax report back, if agreedUSUALLY FOLLOWED BYCOPRARContainer discharge/loading order2 WHAT DIRECTORY D.21A REQUIRESInterchange: sender and recipient IDs(UNB … UNZ)Message VERMAS (UNH … UNT)START OF MESSAGEBGMBeginning of messageBODY AND SEGMENT GROUPS+ 3 conditional groups, starting with:RFFNADEQDBlue 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 VERMAS.Your trading partner's implementation guide adds itsown requirements.

How to read this diagram: the top row shows who sends VERMAS, 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 VERMAS 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 verified gross mass for an export container
  • Passing weights from forwarders to carriers
  • Correcting a previously submitted weight

Where it fits in the message flow

Usually follows IFTMBC Booking confirmation
This message VERMAS Verified gross mass

Structure

Mandatory segments in VERMAS (directory D.21A)

In UN/EDIFACT directory D.21A, the VERMAS message has 22 segment positions arranged in 9 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
  • UNT

Practical example

VERMAS in practice

An exporter loads a container at its plant and weighs it on a certified scale. Its forwarder sends the carrier a VERMAS with the container number, the booking, the verified gross mass, the weighing method and the name of the responsible person. The carrier passes the weight to the terminal, which includes the container in the vessel loading plan.

Implementation

Implementation considerations for VERMAS

  • Submit weights before the carrier's VGM cut-off.
  • State the weighing method and responsible party as SOLAS requires.
  • Keep weights consistent with shipping instructions.
  • Track acknowledgments, since containers without a VGM are not loaded.

Need help with VERMAS?

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