eManifest Stakeholder Partnership Network

ARCHIVED - Design Working Group

Archived Content

Information identified as archived is provided for reference, research or recordkeeping purposes. It is not subject to the Government of Canada Web Standards and has not been altered or updated since it was archived. Please contact us to request a format other than those available.

September 12-14, 2012

The objective of this three-day meeting was to confirm the eManifest freight forwarder and importer designs.

On the first day of the meeting, the working group completed a review of the eManifest issue log.  The Canada Border Services Agency (CBSA) provided updates on highway carrier implementation uptake and solutions to issues identified through compliance monitoring activities.  Of note, the CBSA is working collaboratively with the Canadian Trucking Alliance and Private Motor Truck Council of Canada to hold conference calls with early adopters to share updates, best practices and identify and resolve highway carrier implementation issues.  The CBSA also reported the creation of an internal working group that provides a forum for the regions to raise and resolve implementation issues, as well as a mechanism for the eManifest project team to inform the regions of processing issues raised by the trade community.

The second day of the meeting included presentations and discussions on the eManifest deployment schedule, the Beyond the Border initiative and the new eManifest Portal functionality for freight forwarders, brokers and warehouse operators. The working group also reviewed the multi-modal cargo data elements and definitions, the eManifest freight forwarder design for house bills and the house bill close messages requirement.

On the third day of the meeting, the CBSA provided clarification on the process for transmitting Conveyance Arrival Certification messages and the cargo close model in the air and marine modes. In addition, the working group reviewed the importer design approach and re-manifest data elements.  The meeting concluded with trade members providing feedback on the eManifest implementation approach and thanking the CBSA for its outreach and consultation efforts.

September 12-14, 2011

The objectives of this two-and-a-half-day meeting were to complete the eManifest freight forwarder design consultations and begin discussions on the eManifest design for importers.

On the first day of the meeting, the working group completed a review of the eManifest multi-modal cargo data set. The Canada Border Services Agency (CBSA) presented policy decisions relating to: split shipments; generic Business Numbers; bar code requirements for presenting cargo and conveyance information at the Primary Inspection Line (PIL); bar-coded Conveyance Reference Number (CRN) requirements for empty conveyances; and consignee definitions. The working group also discussed the CBSA's proposed process for third-party service provider authorization and consent. The carrier and service provider representatives agreed to discuss the process with their membership and provide the CBSA with feedback.

The second day of the meeting focused on the eManifest importer design. Key discussion topics included: importer data elements and end-state processes for various scenarios, including the transmission of multiple data elements; the release of mixed-load shipments at the border; and the in-bond movement of goods. The working group also discussed preliminary eManifest Portal design options for importers. The CBSA will continue consultations on the importer design and will define other related policies.

On the third day of the meeting, the CBSA presented the design for enhanced electronic notifications and walked the members through notice generation processes. The working group also reviewed plans to sunset and replace some of the current Service Options (SO) for the release of imported commercial goods when eManifest becomes mandatory. The meeting concluded with a discussion on conceptual warehouse processes for end-state eManifest, which the working group will continue to discuss at future meetings.

June 22-23, 2011

The first day of the meeting began with an update on eManifest implementation. The CBSA then presented process options for linking cargo and conveyance data and proposed the introduction of a linkage document that each party may submit to identify their cargo. Ongoing discussions with the working group will be held to identify a workable linkage model for all modes. Trade members provided recommendations to better align the house bill design with business practices. The CBSA then provided a walkthrough of the Manifest Forward and notification processes. The day ended with a preliminary discussion on warehouse processing under eManifest, which the working group will continue to discuss at future meetings.

The second day of the meeting focused on a review of the eManifest issue log. The CBSA also presented policy decisions relating to:

  • Advance trade data requirements for hand-carried goods;
  • licence plate and vehicle identification number;
  • requirements for Instruments of International Trade;
  • auto-cancellation of unused cargo control numbers;
  • additions and repairs to commercial vehicles;
  • A8A forms for in-bond shipments;
  • commercial movement of a conveyance with a disabled tractor; and
  • dolly equipment.

The meeting concluded with trade members providing recommendations for discussion topics at the next meeting.

February 23-24, 2011

The first day of the one and a half-day meeting began with an update on the CBSA's eManifest Technical Support Unit. Updates were provided on client testing as well as on support being provided to highway carriers who are transmitting data via electronic data interchange (EDI).

A carrier representative presented feedback on the company's recent experiences with the eManifest highway processing. Overall, the company's experience has been positive and CBSA officers have been supportive. Some areas for improvement were also identified which the CBSA will review.

The working group then discussed the end-state business process for "flying trucks" (goods that are shipped by air, but then are transported across the border by truck). The CBSA also provided updates on eManifest design and development, the carrier code revitalization project and policies for some eManifest exemptions. The meeting ended with a presentation from a broker representative on an end-state conceptual model for release of eManifest shipments at the first point of arrival. After considerable discussion, trade members agreed that the concept would be further vetted by the trade community.

On the second day, the CBSA presented a draft eManifest deployment plan, confirmed freight forwarder liability-related processes and discussed Manifest Forward, Secondary Notify Party and Notices functionality. The meeting ended with an update on the CBSA's review of the house bill data elements.

November 9–10, 2010

The first day of the two-day meeting began with the Canada Border Services Agency's (CBSA) update on the implementation of eManifest in highway mode, announced on October 31, 2010. The CBSA also reported on the progress of the Other Government Department (OGD) Single Window Initiative and its Pathfinder project, as well as plans for the restructuring of the eSPN. Discussions then focused on eManifest program directions for the interim procedures for in-bond movements; the end-state process for determining liability for duties and taxes; the desire to have all warehouse operators process electronic Release Notification System (RNS) arrival messages; the bar-coded Conveyance Reference Number (CRN) requirement for empty trailers; and Advance Trade Data (ATD) requirements for importers.

The second day focused on eManifest house bill design. The CBSA provided a high-level overview of the house bill Electronic Commerce Client Requirements Document (ECCRD) for freight forwarders and corresponding data elements, on which trade members provided significant feedback. The CBSA consulted trade members on the first iteration of eManifest Portal concepts for freight forwarders, warehouse operators, brokers and Manifest Forward functionality. Further consultations on Portal concepts are being planned through Webinars.

The eSPN Design Working Group will continue discussions on eManifest policy and freight forwarder requirements at future meetings.

September 21―22, 2010

The first day of the two-day meeting was held by teleconference using WebEx. The working group discussed notices, including: Manifest Forward's enhanced notification feature (formerly referred to as "broker download"); and carrier, freight forwarder and broker identification for Secondary Notify Party. The group also discussed the status of the October 31, 2010 eManifest highway implementation and overall project roll-out.

The second day, which participants attended in person, focused on policy discussions. Program direction on "flying trucks" (goods that are shipped by air, but then are transported across the border by truck) was presented and accepted by trade members. It was decided that the current paper process for cargo will remain in place until retrofits to air mode electronic systems are implemented. Highway carriers will transmit an exception code for flying trucks with conveyance data.

The CBSA also consulted with trade members on policies relating to the liability for reporting pre-arrival data, use of letters of authorization, application of Administrative Monetary Penalty System (AMPS) for voluntary reporting of non-compliance with pre-arrival data requirements and in-bond movement of goods.

The meeting concluded with a review of the eManifest Bring Forward Log – a tracking tool for various discussions. The next eSPN Design Working Group meeting will focus on freight forwarder house bill requirements and further policy discussions.

March 30–31, 2010

The first day of the two-day meeting opened with a review of the March 11, 2010 eSPN Plenary and the Record of Discussion and Decision from the January 12–13, 2010 eSPN Design Working Group meeting. Participants held significant discussions on eManifest program direction relating to: data submission for distribution and deconsolidation of shipments by importers and carriers; in-bond movement of goods; the "Shared Secret" code for the eManifest Portal; and "flying trucks" (goods are shipped by air, but then are transported across the border by truck).

Members also reviewed additional changes to the Electronic Commerce Client Requirements Document (ECCRD) for the highway mode. The Canada Border Services Agency (CBSA) will inform trade members when the ECCRD will be available on the CBSA Web site. In addition, the CBSA informed trade members that the "one-step message" approach for clients to submit conveyance and cargo data to the CBSA will be discussed at the next eSPN Technical Design Working Group meeting.

Day two of the meeting focused on discussions regarding broker download features (a functionality that will allow trade partners to identify other parties, e.g. carrier, freight forwarder, importer/broker, to whom the CBSA will forward eManifest information); eManifest Portal functionality for freight forwarders; and housebills. Trade members recommended additional features that the CBSA will consider in the development of the broker download. The CBSA also agreed to gather further feedback on the eManifest Portal from freight forwarders using online communication methods. In considering members' suggestions, the CBSA will further review the time frames for sending advance messages on a housebill.

Other topics of discussion included the eSPN Design Working Group's list of action items, the eManifest Stakeholder Issues Log and enhanced notifications.

January 12–13, 2010

The CBSA provided trade members with updates from the eSPN Steering Committee meeting that took place the morning of January 12, 2010. This was followed by a walkthrough of the highway process that focused on the changes that will occur after the initial implementation of eManifest.

The CBSA delivered a presentation explaining the current process for remanifests* and the proposed process for eManifest end-state. Action items from the November 18, 2009 meeting were also reviewed. The CBSA also presented the updated Advance Commercial Information (ACI) Secondary Cargo data elements chart for trade members' feedback. Once feedback is received, a revised house bill data element chart will be distributed.

The meeting concluded with the CBSA sharing the issues discussed with eSPN Steering Committee members on January 12, 2010. It was noted that, moving forward, policy and design issues will be separated and a revised issue log will be presented to trade members at the next Design Working Group meeting, to be scheduled following the eSPN Plenary on March 11, 2010.

* Remanifest is a new cargo control document, with a new cargo control number, which is presented to change a cargo control document that had previously been submitted to the CBSA. Remanifests are generally presented to change the destination office or carrier code that identifies when there is a change in carrier liability (where a subsequent carrier accepts responsibility and liability of the unreleased cargo moving under CBSA control) or when goods are split for furtherance.

November 18, 2009

The primary focus of this meeting was electronic house bills; particularly to define and clarify their use and to demonstrate how they will connect other documents.

Members reviewed the supplementary data elements, where the new Advance Commercial Information (ACI) highway data elements set was adjusted for freight forwarders submitting house bills. The CBSA will further review the data elements and their definitions, and trade members will provide the CBSA with additional data fields that will support broker download.

The working group also held preliminary discussions regarding the house bill process, which the CBSA will further develop in collaboration with the members.

The meeting concluded with the CBSA confirming that discussions are continuing on the issue of arrivals. The proposed changes to the arrival process will be discussed at the next meeting, including how these changes are to be implemented. The working group's next meeting will focus on key issues, process flows and the updated data elements chart for secondary reporting.

October 14, 2009

The Canada Border Services Agency (CBSA) provided an update on its recent meetings with trade chain partners, the status of action items from the working group meeting in June 2009 and on the implementation timelines for highway carriers. The working group also discussed the requirement for carrier codes for end-state eManifest, and letters of authorization for carriers.

The working group meeting focused on the review of the Electronic Commerce Client Requirements Document (ECCRD) for the highway mode. Members examined several sections of the ECCRD, including eManifest process exception codes, amendment codes, as well as the issues surrounding the filing of amendments. The working group also reviewed highway cargo and conveyance scenarios.

The CBSA informed members that the ECCRD for the highway mode is scheduled to be completed by the end of October 2009. Future meetings of the working group will focus on house bills, and the CBSA will seek additional freight forwarder representation on this working group for these discussions.

June 16-17, 2009

The first day of the two-day meeting began with a review of the eSPN Design Issue Log and the Electronic Commerce Client Requirements Document (ECCRD) for the highway mode. The working group discussed the issue log in detail, and trade members recommended further revisions to the ECCRD.

CBSA members presented preliminary findings from recent eManifest Portal prototype consultations, and provided a brief demonstration of the prototype. Overall, participants in the consultations were satisfied with the prototype and expressed that they were pleased to have the opportunity to provide usability feedback.

The eManifest Implementation and Client Support Strategy was presented to members, who offered feedback in terms of policy/operational, technical and on-site client support.

The second day of the meeting began with a review of the data elements chart for carriers. Discussion topics included the possibility of moving the Container Stuffing Location and Freight Forwarder/Consolidator data elements from the importer requirements to the freight forwarder data set, as freight forwarders are better positioned to provide this information.

An updated version of the secondary process flow options and the new data elements required for secondary reporting were shared with members. The new data elements include Port of Manifest Origin, Port of Destination (rather than just city), Sub-Location Code, Consolidated Freight Indicator, Freight Forwarder (Stuffer) and Container Stuffing Location.

The meeting concluded with trade members providing suggestions for future topics of discussion.

April 14-15, 2009

The first day of this two-day meeting began with a presentation by the CBSA outlining the Agency's response to feedback from the trade community on importer admissibility data (IAD) requirements. The requirements were revised as follows:

  • The Manufacturer Name and Address data elements are no longer required for trans-border shipments (in the highway and rail modes of transportation) but are still required for offshore shipments (in the marine and air modes).
  • The Consignee Name and Address data elements must now only be provided if the Consignee Number is not provided.
  • The Harmonized System Code (HS Code) data element (at the six-digit level) is not required for every invoice line but is required for every commodity.
  • The Fumigation, Special Handling and Dangerous Cargo data elements have been removed from the importer list of requirements.
  • The Exporter Name and Address data elements are only required if they differ from the Seller/Vendor.

In consideration of these IAD requirements, the CBSA shared the revised border process that will allow for greater alignment with trusted trader programs (the Customs Self Assessment (CSA) program / the Free and Secure Trade (FAST) program / the Partners in Protection (PIP) program) and additional harmonization with U.S. Customs and Border Protection. Goods will be permitted to move in-bond when not all IAD can be provided pre-arrival by program members. It was also noted that risk assessments will continue to be conducted based on available information.

Design working group members reviewed and provided feedback on a walk-through of eManifest end-state process flow options. This included clarifying and discussing the required crew information, the use of letters of authorization from carriers to the CBSA, and compliance and penalty issues.

During the second day, discussions focussed on secondary cargo reporting, specifically the provision of house bills, the challenges associated with providing and amending pre-arrival secondary cargo data and the availability of the cargo control numbers used in transmission.

The meeting concluded with an update of upcoming events and future topics of discussion, including the establishment of a technical design working group, the development of the eManifest Portal, the finalization of permitted changes to shipment information post-arrival for highway carriers, changes to the CSA program and the reporting of crew data.

February 17, 2009

The CBSA informed members that it recently met with the International Air Transport Association and the Canadian Courier and Logistics Association, as well as with the Railway Association of Canada's EDI (electronic data interchange) Rail Customs Task Force. Discussion topics at those meetings included "flying trucks" (goods are shipped by air but then are transported across the border by truck) and aligning data processes with U.S. processes in the rail mode.

Members were debriefed on past meetings of the eSPN communications working group and the eSPN steering committee, and on the February 2009 eSPN plenary.

Members provided feedback on the Electronic Commerce Client Requirements Document and made suggestions on the internal and external eManifest business process flows.

eManifest program design issues were discussed, including importer admissibility data, data elements and exceptions, as well as implementation approaches and proposals.

November 6, 2008

The CBSA updated members on the project's status and briefed them on the Association of American Railroads/Railway Association of Canada's EDI (electronic data interchange) Rail Customs Task Force meeting held in September.

Members reviewed and provided feedback on the draft eManifest end state process flow charts.

The working group reviewed and discussed proposed amendments to the Customs Act regarding pre-arrival information time frames and data requirements.

The CBSA indicated that once eManifest system functionality is in place, there will be an implementation window to give the trade community time to comply with the requirements. Following this, the CBSA will implement a period of informed compliance before non-compliance becomes subject to monetary penalties.

The CBSA provided members with new rail notification options and the draft highway Electronic Commerce Client Requirements Document for review.

June 25–26, 2008

Feedback was provided to the CBSA on proposed pre-arrival conveyance, cargo and supplementary data elements for highway and rail modes.

The 34 proposed importer admissibility data (IAD) elements were compared with the existing data elements requested for the Pre-Arrival Release System (PARS) electronic data interchange (EDI) service option. Twenty-seven of the proposed IAD elements are currently required under PARS.

Trade-chain partners were asked to identify the types of notices they need before their shipments arrive at the border.

The group divided into two sub-groups — importers/brokers and carriers/freight forwarders — to provide input on the proposed data structure and data looping for highway mode requirements on pre-arrival conveyance and cargo information. The CBSA will follow up on the questions raised.

Members discussed the use of bar codes and transponders including today's practices, possible interim measures and options when eManifest is fully implemented. Members also discussed the challenges of multiple cross-border trips with transponder technology.

A representative of the trade community discussed the challenges of having to report intermodal movements. Currently, there is no requirement to resubmit pre-arrival information when goods are transferred to another mode. Some members of the trade community recommended that this flexibility be maintained under the end state of eManifest.

Members provided feedback on the concepts and initial design of the eManifest portal including findings from the consultations that had occurred during the cross-Canada portal design sessions.

May 13–14, 2008

The trade community outlined business impacts of eliminating the current practice of moving in-bond goods on a manifest. They also suggested possible alternatives to help them manage this change in policy such as maintaining in-bond processes for FAST-approved carriers.

Members offered comments on data looping, contingency plans and liabilities in that process. Alternatives to bar code trip numbers, such as scanning a PARS bar code or using transponders, were also discussed.

Trade-chain partners talked about their previous experience with the U.S. Customs and Border Protection's Automated Customs Environment and would like the CBSA to take that information into consideration when developing an "implementation window" for eManifest.

Members requested that service providers attend meetings and it was agreed that they would attend as guests of the working group members. In addition, all members agreed that key issues should be resolved before advancing with the multi-modal consultations; the decision was made to invite rail and ocean carriers to the next working group meeting.

April 1–2, 2008

Most of the participants preferred the longer two-day meeting and requested that, going forward, the design working group use the two-day format.

Two new members were introduced: a rotational member of the communications working group and a representative from the Private Motor Truck Council of Canada.

Participants identified their concerns with the IAD elements and the carrier data element requirements, and highlighted those that they would like the CBSA to re-examine. The CBSA will take these data elements back for further internal discussion.

Trade community members discussed situations where, for reasons outside their control, they would be unable to provide all the advance data information. A list of identified situations was discussed to determine what type of pre-arrival information could be sent and which of the situations needed to be sent back to the CBSA for further consideration.

First point of arrival (FPOA) discussions revolved around where the release of goods or examinations would be conducted. Questions were raised about facilities and the number of staff required to meet FPOA conditions for release and examination. The CBSA will take back the comments and questions on FPOA to facilitate further internal discussion.

January 22, 2008

The definitions and transportation mode requirements for data elements were reviewed. Trade community members also offered feedback and suggestions in regard to the format of the meeting and the next steps of the eSPN, including a refocus of the plenary on broad communications to ensure all members can participate, holding plenaries more frequently (twice a year) and having a working group conference call before the February 2008 plenary. Members asked that advance copies of the issue log be circulated before the meeting.

November 26–27, 2007

Members discussed a number of scenarios for the eManifest Web portal from what reporting and query functions would be available to allowing companies to have multiple users with levels of controlled access. The trade community highlighted the types of notification messages that they would find most useful. Best methods were also presented and discussed to gather carriers' input and to find out which carrier audiences should be targeted during consultations on the initial Web portal design. The trade community noted that there will be a need for 24/7 support and proper training once the portal is ready for testing. Working group members were approached to help organize a cross-Canada consultation with truck carriers on the initial portal design concept.

October 3, 2007

Members offered input and raised questions on the Advance Commercial Initiative/eManifest process flows for highway, air, marine and rail modes and the type of data that specific trade-chain partners must submit. Members were particularly interested in further discussing the following topics: Harmonized System codes, data definitions and options for identifying account identification numbers, and potential triggers for the one-hour time frame.

August 16, 2007

At the inaugural meeting of the design working group, the CBSA presented an overview of the eManifest end state and initiated a discussion with trade community representatives. Key points of interest for the trade community were the data elements that would be required, the examination and release at the FPOA and implementation. Some key features of the projected initial deployments of eManifest were discussed, including EDI reporting, in-transit movements and the Web portal and passage process.

Date modified: