- Global Reach Blog - http://globalreach.blogs.census.gov -

How to correct Fatal Error: 125 Conveyance Name Ineligible

Posted By rosannatorres On August 16, 2010 @ 7:00 am In Export Filing | 4 Comments

By: Rosanna Torres [1]

Lately, I have received many calls from customers indicating they have received a response from the Automated Export System (AES) of: Shipment Rejected: 125 Conveyance Name Ineligible [2]. Filers say they have always listed “unknown” in the past, and it has never triggered an error. Let me explain. There was an update in the AES that validates against the Conveyance Name field. It no longer allows a shipment to leave the U.S. without a valid description of the carrier that is moving the merchandise out of the country. If a filer submits ‘UNKNOWN’ as the conveyance name in the shipment information section, AES will reject the shipment. It will generate fatal error 125: ‘ Conveyance Name Ineligible’.

If you receive this error, here’s how to correct it:

  1. Retrieve the shipment.
  2. Locate Conveyance Name field and enter the transportation company’s name. If the shipment is leaving via vessel, indicate the vessel’s name.
  3. Verify all other fields are complete and resubmit.


Avoid other terms such as: airplane, train, rail, truck, vessel, barge, or international footbridge as these are also not acceptable.

You must indicate the name of the carrier transporting the goods out of the U.S. listed in the Electronic Export Information (EEI). According to the Foreign Trade Regulations (FTR) 30.6 (a)(7) [3], report the following as the Conveyance name:

“The conveyance name/carrier name is the name of the conveyance/carrier transporting the goods out of the United States as known at the time of exportation. For exports by sea, the conveyance name is the vessel name. For exports by air, rail, or truck, the carrier name is that which corresponds to the carrier identification…”

Though every Carrier Code (whether a SCAC or IATA code) is not in the system, the name of the company transporting the goods is known at the time of export. You may not list “unknown” in the Conveyance Name. If the corresponding Carrier Code for a carrier is not listed in the AES, then you may use the appropriate unknown code classified by the particular mode of transportation in the Carrier SCAC/IATA field.

For Carriers that do not have a valid SCAC or IATA code, indicate one of the following:

  • 99M — unknown mexican trucker
  • 99F — unknown foreign air carrier
  • 99U — unknown U.S. air carrier
  • 99C — unknown canadian air carrier
  • UNKN — unknown carrier (Only for ocean, rail and truck shipments)
  • 99O — Use this code if the aircraft is the item being exported. Indicate “Flyaway Aircraft” as the Conveyance Name.

* The Carrier Code tables are updated regularly. Check and make sure the carrier you are using is not in the list prior to utilizing an unknown code from the list above.


(Visited 9,089 times, 1 visits today)

4 Comments (Open | Close)

4 Comments To "How to correct Fatal Error: 125 Conveyance Name Ineligible"

#1 Comment By Taylor C On October 18, 2010 @ 12:27 pm

Since the amendment to the validation in the Conveyance name field we have changed the required information we must be supplied to file Mode 30 and 31(Truck). Due to this change we have continued to run into problems with SCAC’s when dealing with these modes. In an effort to try and report the actual SCAC and Carrier Name, and not 99M, we have been requiring the border agents (Mexico) to provide the information prior to our transmitting the EEI. This in and of it self has been a big undertaking because the feed back is always that they don’t have the information till the last minute. That said we have had some luck with getting them to comply but then from time to time we have problems with the SCAC’s.
Since we are both a forwarder and a broker we have the ability to query ABI (Customs Import System) to validate SCAC’s prior to transmission. We have always done this but with the border crossing we seem to find a lot of SCAC’s that are current and valid in ABI but expired or not valid in AES.
Just today we queried RLCA in ABI (Customs Import System) to validate it and get the actual carrier name. It came back as a valid SCAC showing “R & L Carriers” so queried the name to see if any other codes came back. The only one was RLCA… We then updated our file with RLCA and transmitted to AES only to have the shipment get rejected because the SCAC was expired. We then updated or EEI to show the Transporting Carrier as 99M and Conveyance Name to R & L Carriers and retransmitted. Once this amendment was done the shipment was accepted and we received or ITN.
My question is why does AES and Customs maintain two different carrier bases and how can you get AES fixed under both situations (invalid SCAC in AES but valid in ABI and an Expired SCAC in AES)

#2 Comment By Rosanna On October 21, 2010 @ 1:00 pm

Hi Taylor-
Thanks for your comment. First, I want to make clear that the validation made in AES does not forbid filers from entering valid “unknown” carrier identification codes that I mentioned in the post. If the transportation company does not have a valid Carrier Code that identifies them, then your last resort would be enter an acceptable “unknown” identifier; however, the name of the carrier should be known at the time of export and must be specified in the Conveyance Name field. “Unknown” will not be accepted in the Conveyance Name field.
In regards to the databases, you are correct. ABI and AES work independently from each other. They are managed separately and do not share information. The AES Mainframe is updated with the list of SCAC or IATA codes provided to us by the National Motor Freight Association.
If you are certain a SCAC code is valid, but AES does not accept it, we would need to receive a copy of the certification. We will then verify the information provided and update the system as well as our filing applications. Carriers can fax this document to 301-763-6638.

#3 Comment By Karina On July 8, 2014 @ 1:43 pm

Good morning,

I have a question, we received a list of few shippers that have this error, but those were made on April of this year, so we still can retransmit the shipper with the correct information of the conveyance? Or is not necessary, and the report is just to have the knowledge for future shipments?

I really appreciate your help.


#4 Comment By Global Reach Daniel On July 15, 2014 @ 8:25 am

All fatal errors must be corrected.

Article printed from Global Reach Blog: http://globalreach.blogs.census.gov

URL to article: http://globalreach.blogs.census.gov/2010/08/16/how-to-correct-fatal-error-125-conveyance-name-ineligible/

URLs in this post:

[1] Rosanna Torres: http://globalreach.blogs.census.gov/blogger-biographies/

[2] Shipment Rejected: 125 Conveyance Name Ineligible : http://www.census.gov/foreign-trade/redirects/aestir-appendix-a.html

[3] (FTR) 30.6 (a)(7): http://www.census.gov/foreign-trade/regulations/regs/regulations20080602-federalregister.html