972-836-7750 Request a demo Talk to an expert
Talk to an expert Request a demo Call sales 972-836-7750

X12 transaction guide · Transportation

EDI 359 Customs Customer Profile Management

The X12 document used between US Customs and Border Protection and ACE account holders to maintain profile data such as conveyances and crew.

Sent by
ACE account holder, such as a carrier
Received by
US Customs and Border Protection
Standard
ANSI ASC X12

What is an EDI 359?

The EDI 359 Customs Customer Profile Management is the ANSI X12 transaction set that may be used between US Customs and Border Protection and Automated Commercial Environment (ACE) account holders to add, change or delete profile information, such as the conveyances, equipment and personnel registered to an account.

Carriers that file electronic manifests reference these profiles in their filings. Keeping profiles current avoids rejected manifests and delays at the border when a truck, trailer or driver is not on record.

How the EDI 359 worksDiagram of the EDI 359 Customs Customer Profile Management. ACE account holder, such as a carrier sends it to uS Customs and Border Protection. It usually starts the exchange. It is usually followed by 997. Inside the ISA, GS and ST envelopes, X12 release 008010 requires, in the heading: CPM (Customs Profile Management Information). 3 optional loops are listed by their first segment.How the EDI 359 worksCustoms Customer Profile Management: who sends it, where it fits and what the standard marks required1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeEDI 359SENDERACE account holder,such as a carrierRECEIVERUS Customs andBorder Protection997 or 999 acknowledgment back, if the partners agreeUSUALLY FOLLOWED BY997FunctionalAcknowledgment2 WHAT X12 RELEASE 008010 REQUIRESInterchange: sender and receiver IDsISA … IEAFunctional group, ID code BGGS … GETransaction set 359ST … SEHEADINGCPMCustoms Profile Management Information+ 3 optional loops, starting with:NM1VEHVIDBlue box: required loop. Optional loops are listed by the segment that starts them; when a loop is used, that first segment is required. Optional segmentsoutside loops are not drawn.Structure: required segments and loops in the X12 008010 listing for the 359. Your trading partner's implementation guide adds its own requirements.
How the EDI 359 worksDiagram of the EDI 359 Customs Customer Profile Management. ACE account holder, such as a carrier sends it to uS Customs and Border Protection. It usually starts the exchange. It is usually followed by 997. Inside the ISA, GS and ST envelopes, X12 release 008010 requires, in the heading: CPM (Customs Profile Management Information). 3 optional loops are listed by their first segment.How the EDI 359 worksCustoms Customer Profile Management: whosends it, where it fits and what the standardmarks required1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeEDI 359SENDERACE accountholder, such asa carrierRECEIVERUS Customs andBorderProtection997 or 999 acknowledgment back, if the partnersagreeUSUALLY FOLLOWED BY997Functional Acknowledgment2 WHAT X12 RELEASE 008010 REQUIRESInterchange: sender and receiver IDs (ISA… IEA)Functional group, ID code BG (GS … GE)Transaction set 359 (ST … SE)HEADINGCPMCustoms Profile ManagementInformation+ 3 optional loops, starting with:NM1VEHVIDBlue box: required loop. Optional loops are listedby the segment that starts them; when a loop isused, that first segment is required. Optionalsegments outside loops are not drawn.Structure: required segments and loops in the X12008010 listing for the 359. Your trading partner'simplementation guide adds its own requirements.

How to read this diagram: the top row shows who sends the 359, to whom, and which documents usually come before and after it. The lower part shows what X12 release 008010 itself requires: the envelopes around the 359 and the segments and loops the standard marks as required, area by area. Optional loops are listed by the segment that starts them rather than drawn in full. This is the standard's minimum, not a trading partner's requirement: each partner's implementation guide usually makes some optional loops mandatory, restricts the codes and may use a different release.

Expand diagram Download SVG

When it is used

  • Registering trucks or trailers with customs
  • Updating driver or crew profiles
  • Removing equipment no longer in service

Where it fits in the document flow

This document 359 Customs Customer Profile Management
Usually followed by 997 Functional Acknowledgment

Structure

Mandatory segments in the 359 (X12 release 008010)

The segments X12 release 008010 marks as mandatory at their level, in order. Segments inside optional loops are needed only when the loop is used. This is the standard's requirement, not your trading partner's: each partner's implementation guide names the release it uses, adds the optional segments it requires and restricts the values. The requirement status comes from one published X12 reference listing and has not been checked against a second source.

  • ST
  • CPM
  • NM1
  • VEH
  • VID
  • SE

Practical example

The 359 in practice

A cross-border trucking company adds ten tractors to its fleet. Its compliance system sends a 359 to add each tractor, with its identification and registration details, to the company's customs profile. When the company files manifests for loads hauled by the new tractors, customs recognizes them.

Implementation

Implementation considerations for the 359

  • Update profiles before equipment or drivers are used in filings.
  • Remove retired equipment to keep profiles accurate.
  • Protect personal data in driver and crew profiles.
  • Follow current Customs and Border Protection implementation guidance.

How ECOM helps

Automate the 359 with ECOM

Industry

Trucking and Transportation

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

Solution

EDI Integration

Exchange X12 and EDIFACT documents with partners and integrate them directly with your ERP.

Solution

Logistics Automation

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

More general questions about EDI are answered in the EDI FAQ.

Related transactions

Related transportation documents

All 80 transportation documents

Need help with the EDI 359?

ECOM maps, tests and monitors X12 documents for your trading partners and integrates them with your ERP.

Request a Demo Contact us