IBC. Inc.

IBC Manifest Test Request

Instructions
  • Please make sure that your manifest file contains the necessary field types.
  • See IBC Manifest Format for details.
  • Please limit your test data between 50-100 shipment records
  • You can only upload CSV or TXT files to this form

You can also use the Manifest Test API to submit your tests via JSON request.

IBC Air AMS Quick Reference

Synopsis

The IBC Air AMS manifest format is a CSV (Text based) file. On the standard format used for CFS and ECCF clearances, you will need to create 3 types of CSV records.

  • Email Records - at least 2 records
  • Manifest Record - at least 1 record
  • Shipment Records - at least 1 record

CSV files can be separeted with comma (,) TAB or other separator chars such as semicolon (;). IBC Air AAMS manifest only accepts fields separated with a comma (,).

Standard Air AMS Format

Email Records

You must declare at least 1 failure record with the form:

6,your_valid_email@domail.com

and at least one success email record with the form:

7,your_valid_email@domail.com

You can declare as many success or failure email records as you need. Once imported the system will respond to either the success or failure addresses with a confirmation or rejection message.

Manifest Record

After your email line declarations you must submit 1 manifest line record with the form:

1,MAN_ID,MANIFEST_DATE,ORIGIN,DESTINATION,FLIGHT,YOUR_MASTER_AWB

Please visit IBC Fullman Format - Manifest Records for the complete definition.

Shipment Records

After creating the master record you will need to report the shipment records associated with your import. Here is a sample record:

12,,123456789,,,,"LHR","USA",,,,,1,"0.44","P","APX",,10,,"ADHESIVE CHEMICALS",,,"P","P","ST",,,,,,"SOME COMPANY A","123 MAIN STREET",,"LONDON",,"LE4 6BW","GB","+442087594076","HUGO JORGE","COMPANY 1","211 BOSTON STREET","MIDDLETON","MASSACHUSETTS","MA","01949","US",5085551212,joe@example.com,"123-45-6789","THIS IS A COMMENT"

Please visit IBC Fullman Format - Shipment Records for the complete definition.

Handling CSV

You can use the standard convention CSV format described here: RFC4180 and we recommend the following conventions

  • Enclose all string with (") double quotes, specially if it is possible that a comma (,) is part of the text field.
  • Numeric values don't need to be closed in quotes. You can if you must.
  • Beware that viewing CSV files in Excel, will truncate large numbers (such as your house airwaybill field) and change yuor declared value to a different format. We recommend viewing your files in Notepad or other text editors.

Sample Files

Section 321 Clearances

In order to transmit Section 321 Clearances please ensure that your account has been approved for this type of transmission. Please check with your IBC Sales manager.

Additional Entry Records

To successfully transmit Section 321 Entries, your Air AMS file will need:

  • The standard Air AMS lines
  • A Section 321 record line
  • After each Shipment Record line you can define one or multiple Package lines, in turn each Package line can have 1 or multiple Goods lines - Definition below

Section 321 Record Line

Once approved by US CBP, you will receive an Section 321 Filer ID. You will report it to IBC in the following manner

misc,1,section-321-originator-code,YOUR_ASSIGNED_CODE

This line should be reported before the Manifest Record Line and after your Email Record lines.

Package and Goods Line Definition

The Package Line has the following definition schema:


            COL   NUM   FIELD_NAME             NOTES
            ---   ---   ---------------------  -------------
            A      1    record_type ("package")
            B      2    record_version ("1")
            C      3    quantity
            D      4    package_awb
            E      5    barcode
            F      6    reference
            G      7    incoming_container
            H      8    vendor_code
            I      9    vendor_awb
            J     10    packaging
            K     11    description
            L     12    declared_value
            M     13    declared_value_currency
            N     14    weight
            O     15    weight_units            lb/kg/g
            P     16    dim_l
            Q     17    dim_w
            R     18    dim_h
            S     19    dim_units               in/m/cm/mm
            

The Goods Line has the following definition schema:


            COL   NUM   FIELD NAME               NOTES
            ---   ---   ---------------------    -------------
            A     1   record_type                always "good"
            B     2   record_version             always "2"
            C     3   quantity
            D     4   description
            E     5   good_url
            F     6   hts_code
            G     7   origin_country
            H     8   declared_value_per_quantity
            I     9   declared_value_currency
            J    10   weight_per_quantity
            K    11   weight_units
            L    12   order_id
            M    13   order_date
            N    14   list_price_per_quantity
            O    15   list_price_currency
            P    16   retail_price_per_quantity
            Q    17   retail_price_currency
            

The Goods Entity Line has the following definition schema:


            COL   NUM   FIELD NAME              NOTES
            ---   ---   ---------------------   -------------
            A     1   record_type               always "good_entity" or "hawb_entity"
            B     2   record_version            always "1"
            C     3   role_name	                See Entity Role Section below
            D     4   name
            E     5   address
            F     6   city
            G     7   state
            H     8   postal_code
            I     9   country
            J    10   phone
            K    11   email
            L    12   url

            Entity Role Section
            ---------------------------------------------------------------------------------
            The Entity role_name should be one of the following (defined by CBP)

            ROLE
            ---------------------
            carrier
            buyer
            consignee
            seller
            finalRecipient
            shipmentInitiator
            onlineMarketplace
            other
            broker
            shipper
            forwarder

            

These are definitions applied by CBP to the Entity Roles:



            Definitions
            ------------------------------------------------------------------------------
            Shipment Initiator Name and Address (e.g., the entity that causes the movement
            of a shipment, which may be a seller, shipper, or manufacturer, but not a
            foreign consolidator).

            Final Deliver to Party Name and Address (e.g., the final entity to receive the
            shipment once it arrives in the United States, which may be a final purchaser
            or a warehouse, but not a domestic deconsolidator)

            Seller Name and Address (e.g., an international or domestic company that sells
            products on marketplaces and other websites)

            Buyer Name and Address, if applicable (e.g., the purchaser of a good from an
            online marketplace. This entity is not always the same as the final deliver to
            party.)

            Further details would come from CBP, please review the documentation
            provided by CBP for the section 321 pilot program.
            

Manifest Reference

Here is a summarized manifest for an order reference


        6,bad.news@mydomain.com
        7,good.news@mydomain.com
        misc,1,section-321-originator-code,MY_ASSIGNED_CODE
        1,1234567,20200601,HKG,LAX,CN011,18026132411
        12,,123464797,1464477,,,HKG,LAX,,,,,1,1.35,P,APX,USD,23,,"Candles",,,P,P,ST,,,,,,"The Candle Maker","13 West Shop Addr",...
        package,1,1,...
        goods,2,1,"Sweet Scented Candle - 100% Was",https://www.thecandlemaker.com/item/1234456.html,......
        12,,123464899,1464721,,,HKG,LAX,,,,,1,1.15,P,APX,USD,18,,"Candle Holder",,,P,P,ST,,,,,,"The Candle Maker","13 West Shop Addr",...
        package,1,1,...
        goods,2,1,"Candle Holder - brass",https://www.thecandlemaker.com/item/2646547.html,.......
        good_entity,1,seller,...    info about the first good's seller
        good_entity,1,shipper,...   info about the first good's shipper
        goods,2,1,"War Craddle- Fabric+Charcoal",https://thecandlemaker.com/item/1246543.html,......
        good_entity,1,seller,...    info about the second good's seller
        good_entity,1,shipper,...   info about the second good's shipper
        package,1,1,...
        goods,2,1,"Candle",https://www.thecandelmaker.com/item/12245.html,...........
        12,,123465412,.........
        package,1,1,......
        goods,2,..........
        good_entity,1,seller,...    info about the good's seller
            

Type 86 Entries

Type 86 Entry processing requires the following steps to be completed:

  • The standard Air AMS lines with the HTS code reported
  • Submit normally
  • Send your prealert to the IBC port import team that this is a type-86 submsission - This step is part of the SOP instructions handed to you by your sales manager.

HTS references

The HTS column is column number 21 (colum U in Excel) of the type line 12 record.

Don't report the period char (.) in the IBC Air Manifest. For example if your HTS is code is: 6104.23.00.10 reported as: 6104230010 in the IBC HTS code column.

If you don't know your product's HTC code use this link: HTS Search tool, using your product description to retrieve the HTS code from US Trade Commision Site.

Type 92 Entries - Shipment Returns

In order to transmit Type 92 Entries please ensure that your account has been approved for these type of transmission. Please check with your IBC Sales manager.

Additional Entry Records

To successfully transmit Type 92 Entries, your Air AMS file will need:

  • The standard Air AMS lines
  • A Type 92 Record line to declare the entire manifest or a Type 92 post shipment line to declare a single shipment line
  • Each Shipment record be delared with the HTS (Harmonized Tariff Schedule) code: 9801.00.2600

HTS Code declaration

Use the code 9801002600 on each shipment line that is being declared as a return. If declaring the entire manifest each line should have this HTS code.

Type 92 Record Line - To declare an entire manifest

You will report it to IBC in the following manner:

file_misc,1,entry_type,92

This line should be reported before the Manifest Record Line and after your Email Record lines.

Entire Manifest Example

Here is a sample of an entire master declaration.


        6,bad.news@mydomain.com
        7,good.news@mydomain.com
        file_misc,1,entry_type,92
        1,1234567,20200601,HKG,LAX,CN011,18026132411
        12,,123464797,1464477,,,HKG,LAX,,,,,1,1.35,P,APX,USD,23,,"Candles",,,P,P,ST,,,,,,"The Candle Maker","13 West Shop Addr",...
        12,,123464899,1464721,,,HKG,LAX,,,,,1,1.15,P,APX,USD,18,,"Candle Holder",,,P,P,ST,,,,,,"The Candle Maker","13 West Shop Addr",...
        12,,123465412,.........
            

Type 92 Post Shipment Record Line - To declare only some shipments as returns

If you need to report only some shipments in the manifest as Type 92 use this format:

hawb_misc,1,entry_type,92

This line should be reported after any type 12 shipment line to declare that shipment line as a return.

Only Some Manifest Example

In the following example only the shipment line with track 123464899 is reported as a return.


        6,bad.news@mydomain.com
        7,good.news@mydomain.com
        1,1234567,20200601,HKG,LAX,CN011,18026132411
        12,,123464797,1464477,,,HKG,LAX,,,,,1,1.35,P,APX,USD,23,,"Candles",,,P,P,ST,,,,,,"The Candle Maker","13 West Shop Addr",...
        12,,123464899,1464721,,,HKG,LAX,,,,,1,1.15,P,APX,USD,18,,"Candle Holder",,,P,P,ST,,,,,,"The Candle Maker","13 West Shop Addr",...
        hawb_misc,1,entry_type,92
        12,,123465412,.........
        12,,123456377,.........