{"id":2715,"date":"2025-08-06T18:25:11","date_gmt":"2025-08-06T18:25:11","guid":{"rendered":"https:\/\/www.customs-declarations.uk\/?p=2715"},"modified":"2026-05-28T09:26:22","modified_gmt":"2026-05-28T09:26:22","slug":"hmrc-safety-security-gb-entry-summary-declaration-ens-data-entry-field-requirement-guidelines","status":"publish","type":"post","link":"https:\/\/www.customs-declarations.uk\/hmrc-safety-security-gb-entry-summary-declaration-ens-data-entry-field-requirement-guidelines\/","title":{"rendered":"HMRC Safety &#038; Security \/ GB Entry Summary Declaration (ENS) Data Entry &#038; Fields Requirement Guidelines"},"content":{"rendered":"<p>[vc_row][vc_column][vc_text_separator title=&#8221;&#8221;][vc_column_text]<\/p>\n<h3><strong>Introduction<\/strong><\/h3>\n<p>An <strong>Entry Summary Declaration (ENS)<\/strong> is a pre-arrival electronic notification required for most goods entering Great Britain. It provides UK customs authorities with essential information about the goods, allowing them to assess safety and security risks before the goods arrive. The ENS is submitted via HMRC\u2019s <strong>Safety &amp; Security GB (S&amp;S GB)<\/strong> system and is separate from the import customs declaration \u2013 it contains no duty\/tax assessment, focusing only on safety and security data.<\/p>\n<p>Effective <strong>31 January 2025<\/strong>, HMRC has <strong>reduced<\/strong> the ENS data requirements. The dataset now consists of <strong>20 mandatory fields<\/strong> (always required) and <strong>8 conditional fields<\/strong> (required only in specific circumstances). The remaining fields are optional. This guide, intended for freight forwarders, customs agents, logistics professionals, and software providers, explains each data element field-by-field, including its purpose, required format, examples, common mistakes, and validation rules.<\/p>\n<p><strong>How to use this guide:<\/strong> The fields are grouped into mandatory, conditional, and optional sections. Under each field name, we outline key details:<\/p>\n<p><strong>Requirement<\/strong> (whether the field is Mandatory \u201cM\u201d, Conditional \u201cC\u201d, or Optional \u201cO\u201d)<br \/><strong>Level<\/strong> (whether it\u2019s provided at the declaration header or for each goods item)<br \/><strong>Format<\/strong> (allowed data format\/length)<br \/><strong>Guidelines<\/strong> for optimal completion<br \/><strong>Examples<\/strong><br \/><strong>Common mistakes<\/strong> to avoid.<\/p>\n<p>Tables and code lists are referenced for fields that require specific coded values. Following these guidelines will help ensure your ENS submissions are correct and avoid delays or rejections.<\/p>\n<p>[\/vc_column_text][vc_text_separator title=&#8221;&#8221;][vc_column_text]<\/p>\n<h2><span style=\"color: #ff0000;\"><strong>Mandatory Fields (Core ENS Data Elements)<\/strong><\/span><\/h2>\n<p>These 20 fields <strong>must<\/strong> be provided in all ENS submissions for S&amp;S GB (Great Britain). They cover critical information about the consignment, parties, transport, and goods. Accurate completion of these fields is required for every ENS declaration.<\/p>\n<p>[\/vc_column_text][vc_text_separator title=&#8221;&#8221;][vc_column_text]<\/p>\n<h3><strong>Local Reference Number (LRN)<\/strong><\/h3>\n<ul>\n<li><strong>Requirement:<\/strong> Mandatory (each ENS must have one LRN).<\/li>\n<li><strong>Level:<\/strong> Header-level (one per declaration).<\/li>\n<li><strong>Format:<\/strong> Up to 22 characters, alphanumeric (an..22).<\/li>\n<li><strong>Guidelines:<\/strong> The LRN is a <strong>unique reference<\/strong> you, as the declarant, assign to the declaration. It is used by HMRC to identify the ENS prior to issuing an MRN (Movement Reference Number). Each ENS you submit should have a unique LRN (unique per \u201cPerson Lodging\u201d\/declarant EORI) \u2013 do not reuse LRNs for different declarations. If you later send an <strong>amendment<\/strong>, use the original declaration\u2019s MRN as the LRN in the amendment message.<\/li>\n<li><strong>Example:<\/strong> GB20250701ABC12345 (e.g. incorporating date and a unique sequence).<\/li>\n<li><strong>Common mistakes:<\/strong> Re-using an LRN for multiple ENS filings (violates uniqueness), or not recording the LRN. Remember that if you need support or to query a submission, you\u2019ll be asked for the LRN, so ensure you keep a record of it. Avoid including spaces or special characters; use a simple alphanumeric string.<\/li>\n<\/ul>\n<p>&nbsp;<\/p>\n<p><strong>Note:<\/strong><strong> <em>If you are filing your declaration via the <\/em><\/strong><a href=\"https:\/\/www.customs-declarations.uk\/safety-and-security-declarations-ens-service\/\" target=\"_blank\" rel=\"noopener\"><strong>Customs Declarations UK platform<\/strong><\/a><em><strong>, LRN is automatically generated or populated by the system. You do not need to enter this manually, as the platform ensures it aligns with HMRC&#8217;s technical and regulatory requirements.<\/strong><\/em><\/p>\n<p>[\/vc_column_text][vc_text_separator title=&#8221;&#8221;][vc_column_text]<\/p>\n<h3><strong>Consignor (Sender)<\/strong><\/h3>\n<ul>\n<li><strong>Requirement:<\/strong> Mandatory (must be provided for each consignment).<\/li>\n<li><strong>Level:<\/strong> Provided at <strong>header and item level<\/strong>. You must always declare the \u201ctrue\u201d consignor for the goods. If there are multiple consignors in a consolidated shipment, list each at the item level for the relevant goods item.<\/li>\n<li><strong>Format:<\/strong> <strong>Name<\/strong> (an..35), <strong>Address<\/strong>: Street (an..35), City (an..35), Postcode (an..9), Country (a2), and <strong>EORI\/TIN<\/strong> (an..17) if available.<\/li>\n<li><strong>Guidelines:<\/strong> The consignor is the party <strong>dispatching or selling<\/strong> the goods, as listed on the transport document (e.g. lowest level of Bill of Lading, Air Waybill, CMR). Provide the full name and address of the consignor in the format: <em>Name\/Company, Building Number and Street, City, Region (if applicable), Postcode, Country<\/em>. Include the consignor\u2019s <strong>EORI<\/strong> (Economic Operator Registration and Identification number) or other Trader Identification Number if you have it. If a <strong>GB EORI<\/strong> is provided for the consignor, then the name and address become optional (the system can derive details from the EORI). However, for non-GB EORI or if no EORI is given, you <strong>must<\/strong> provide the full name and address. Always use the <em>actual exporter\/sender\u2019s<\/em> details; do not use a freight forwarder or agent as consignor.<\/li>\n<li><strong>Example:<\/strong><br \/><strong>Name:<\/strong> XYZ Trading Ltd.<br \/><strong>Address:<\/strong> 10 King&#8217;s Road, London, W1 5AB, GB<br \/><strong>EORI:<\/strong> GB123456789000<\/li>\n<li><strong>Common mistakes:<\/strong> Providing incomplete addresses or using a forwarding agent\u2019s details instead of the true consignor. If the consignor has a GB EORI, it\u2019s best practice to include it \u2013 this simplifies validation and you may omit the address (though including both is fine). Ensure no spelling errors in names and that country codes are correct (use the ISO 2-letter country code, e.g. \u201cGB\u201d for United Kingdom).<\/li>\n<\/ul>\n<p>[\/vc_column_text][vc_single_image image=&#8221;2748&#8243; img_size=&#8221;full&#8221;][vc_text_separator title=&#8221;&#8221;][vc_column_text]<\/p>\n<h3><strong>Consignee (Receiver)<\/strong><\/h3>\n<ul>\n<li><strong>Requirement:<\/strong> Mandatory (must be provided for each consignment).<\/li>\n<li><strong>Level:<\/strong> <strong>Header and item level.<\/strong> If multiple consignees exist for different items in a consolidated load, provide each at item level.<\/li>\n<li><strong>Format:<\/strong> <strong>Name<\/strong> (an..35), <strong>Address<\/strong>: Street (an..35), City (an..35), Postcode (an..9), Country (a2), and <strong>EORI\/TIN<\/strong> (an..17) if available.<\/li>\n<li><strong>Guidelines:<\/strong> The consignee is the <strong>party receiving<\/strong> the goods (often the buyer), as per the transport document (B\/L, AWB, etc.). Provide the true consignee\u2019s name and address in full (same format as consignor: Name, Street, City, Postcode, Country). If the consignee has an EORI or TIN, include it \u2013 especially if it\u2019s a <strong>GB EORI<\/strong>, because then the name\/address becomes optional (the ENS can be accepted with just the EORI and country code in that case). If there are multiple consignees (for different items), ensure each item entry shows the correct consignee.<\/li>\n<li><strong>Example:<\/strong><br \/><strong>Name:<\/strong> ABC Imports GmbH<br \/><strong>Address:<\/strong> 55 Berliner Strasse, 10117 Berlin, DE<br \/><strong>EORI:<\/strong> DE987654321000<\/li>\n<li><strong>Common mistakes:<\/strong> Not providing the <strong>actual buyer\/receiver\u2019s<\/strong> details (for example, listing a broker or agent instead of the real consignee). Always list the end recipient if known. If the consignee\u2019s EORI is known (especially a GB or EU EORI), include it for accuracy. As with consignor, avoid typos and use correct country codes (e.g. \u201cDE\u201d for Germany). Remember that if the consignee is unspecified (e.g. a negotiable \u201cTo Order\u201d bill of lading), you will need to use a special procedure (see <strong>Notify Party<\/strong> and special mentions).<\/li>\n<\/ul>\n<p>[\/vc_column_text][vc_single_image image=&#8221;2750&#8243; img_size=&#8221;full&#8221;][vc_text_separator title=&#8221;&#8221;][vc_column_text]<\/p>\n<h3><strong>Person Lodging the Summary Declaration<\/strong><\/h3>\n<ul>\n<li><strong>Requirement:<\/strong> Mandatory (must always be provided).<\/li>\n<li><strong>Level:<\/strong> Header-level (single identification of the lodger).<\/li>\n<li><strong>Format:<\/strong> <strong>EORI number<\/strong> of the person lodging (an..17, typically 12-15 characters including country code). Must be a <strong>GB EORI<\/strong> for S&amp;S GB.<\/li>\n<li><strong>Guidelines:<\/strong> This is the party submitting the ENS \u2013 often the carrier or its representative. You must enter the <strong>GB EORI<\/strong> of the entity lodging the declaration. (For goods into NI via ICS, an XI or EU EORI would be used, but for S&amp;S GB it must be GB.) Ensure the EORI is valid and belongs to the entity authorized to lodge the ENS. The S&amp;S GB system will validate that the LRN is unique under this EORI, and certain fields (like Specific Circumstance \u201cE\u201d for AEO) depend on this party\u2019s status. No name or address is needed here \u2013 just the EORI.<\/li>\n<li><strong>Common mistakes:<\/strong> Using an incorrect EORI (e.g. an EU EORI or a GB EORI that isn\u2019t associated with the carrier\/filing company). Also, ensure you have the carrier\u2019s <strong>knowledge and consent<\/strong> if you (as an agent) are lodging on their behalf, and that the EORI you use is that of the actual carrier or agreed filer.<\/li>\n<\/ul>\n<p>&nbsp;<\/p>\n<p><strong>Note:<\/strong><strong> <em>If you are filing your declaration via the <\/em><\/strong><a href=\"https:\/\/www.customs-declarations.uk\/safety-and-security-declarations-ens-service\/\" target=\"_blank\" rel=\"noopener\"><strong>Customs Declarations UK platform<\/strong><\/a><em><strong>, this field is automatically populated by the system based on your user profile. You do not need to enter this manually.<\/strong><\/em><\/p>\n<p>[\/vc_column_text][vc_text_separator title=&#8221;&#8221;][vc_column_text]<\/p>\n<h3><strong>Country(ies) of Routing Codes<\/strong><\/h3>\n<ul>\n<li><strong>Requirement:<\/strong> Mandatory (required for all declarations).<\/li>\n<li><strong>Level:<\/strong> Header-level (one consolidated list per ENS).<\/li>\n<li><strong>Format:<\/strong> One or more country codes (each 2-letter ISO country code) in <strong>chronological order<\/strong> of transit. Each code is two letters (e.g. \u201cFR\u201d for France).<\/li>\n<li><strong>Guidelines:<\/strong> List <strong>all countries through which the goods will transit<\/strong> between the country of original departure and the final destination. This includes the country of <strong>departure<\/strong> (origin) and <strong>destination<\/strong>. The codes should be in the exact order of travel. For example, if goods depart China (CN), stop in Singapore (SG) en route, then enter GB, and final destination is Ireland (IE), you might list: CN, SG, GB, IE. <strong>All consignments in the declaration must share the same routing sequence<\/strong>, since this field is only declared once at header level. Use official country codes as per the HMRC country code list (ISO 3166-1 alpha-2).<\/li>\n<li><strong>Example:<\/strong> CN, RU, PL, DE, GB (goods from China, transiting Russia and Poland, arriving in Germany then trucked to Great Britain).<\/li>\n<li><strong>Common mistakes:<\/strong> Omitting either the origin or destination country in the list. Ensure the <strong>first code is the origin country<\/strong> and the <strong>last code is the final destination<\/strong>. Do not include the UK <strong>if the UK is the destination<\/strong> \u2013 it <em>should<\/em> be included (as shown above with GB) because it\u2019s the final destination. Another mistake is listing countries out of order or including countries where the goods did not actually transit. Consistency is key: if multiple ENS filings are made for consignments on the same route, the routing should be identical on each.<\/li>\n<\/ul>\n<p>[\/vc_column_text][vc_single_image image=&#8221;2756&#8243; img_size=&#8221;full&#8221;][vc_text_separator title=&#8221;&#8221;][vc_column_text]<\/p>\n<h3><strong>Mode of Transport at the Border<\/strong><\/h3>\n<ul>\n<li><strong>Requirement:<\/strong> Mandatory (always required).<\/li>\n<li><strong>Level:<\/strong> Header-level (one mode per ENS, representing the active transport into GB).<\/li>\n<li><strong>Format:<\/strong> <strong>Numeric code (n1 or n2)<\/strong> \u2013 use the appropriate code for the mode of transport used to <strong>cross the UK border<\/strong> (i.e. into Great Britain). Common codes include 1 = Sea, 4 = Air, 3 = Road (for Channel Tunnel or other road), 10 = Ro-Ro accompanied (ferry with driver), 11 = Ro-Ro unaccompanied, 2 = Rail, 8 = Inland waterway\u301022\u2020\u3011. <em>(Refer to the official HMRC list for all codes.)<\/em><\/li>\n<li><strong>Guidelines:<\/strong> Enter the code corresponding to the <strong>active means of transport crossing into GB<\/strong>. For example, a container on a vessel = 1 (Maritime). A truck on a ferry = 10 (Ro-Ro accompanied if driver with it, or 11 if unaccompanied trailer). An aircraft = 4 (Air). Note special cases: For accompanied movements through the Channel Tunnel (train shuttle carrying trucks), use code 3 (Road). If air cargo is <strong>transported by another mode<\/strong> before entry (e.g. an air shipment carried by truck into GB under a transit), declare the actual mode (road, etc.) rather than air. Also, note that if mode is Air (4), you will need to supply the flight number in the Conveyance Reference Number field, and the Air Waybill number as a transport document reference.<\/li>\n<li><strong>Example:<\/strong> 1 (Sea), 4 (Air), 3 (Road via tunnel), 10 (Accompanied RoRo by ferry).<\/li>\n<li><strong>Common mistakes:<\/strong> Using the wrong mode code \u2013 e.g. selecting \u201cRoad\u201d when goods actually arrive by sea ferry. Always consider how the goods <em>enter<\/em> GB customs territory. If uncertain, refer to the carrier: e.g. if a truck is on a ferry, it\u2019s RoRo (10 or 11) <strong>not purely road<\/strong>. Also, forgetting the special Channel Tunnel rule (treat as road) is a common error.<\/li>\n<\/ul>\n<p>[\/vc_column_text][vc_single_image image=&#8221;2752&#8243; img_size=&#8221;full&#8221;][vc_text_separator title=&#8221;&#8221;][vc_text_separator title=&#8221;&#8221;][vc_column_text]<\/p>\n<h3><strong>Identity of Means of Transport Crossing the Border<\/strong><\/h3>\n<ul>\n<li><strong>Requirement:<\/strong> Mandatory for all modes <strong>except Air<\/strong> (not required for air shipments).<\/li>\n<li><strong>Level:<\/strong> Can be provided at header or item level (generally header-level suffices if one conveyance for the whole ENS).<\/li>\n<li><strong>Format:<\/strong> Up to 27 characters, alphanumeric (an..27). This is typically an identifier like a vessel IMO number, vehicle registration, etc. No spaces or special characters should be included (use only letters and numbers).<\/li>\n<li><strong>Guidelines:<\/strong> Provide the <strong>unique identifier of the vessel\/vehicle\/aircraft<\/strong> that will carry the goods into the UK. The required identifier depends on mode:\n<ul>\n<li><strong>Sea (Maritime):<\/strong> Use the ship\u2019s <strong>IMO number<\/strong> (7 digits).<\/li>\n<li><strong>Rail:<\/strong> Use the <strong>train or wagon number<\/strong> (train ID or wagon ID).<\/li>\n<li><strong>Road \u2013 Accompanied RoRo or road via Tunnel:<\/strong> Use the <strong>vehicle registration number (license plate)<\/strong> of the truck\/tractor unit. For the Channel Tunnel, the vehicle reg is used similarly.<\/li>\n<li><strong>Road \u2013 Unaccompanied trailer on ferry:<\/strong> Use the <strong>IMO number of the ferry<\/strong> (since the trailer has no motor, the ferry is the active transport).<\/li>\n<li><strong>Air:<\/strong> <em>Not used.<\/em> <strong>Do not put the flight number here for air shipments<\/strong> \u2013 instead, the airline flight number goes in Conveyance Reference Number (see conditional fields).<br \/>If the transport is containerized, <strong>do not<\/strong> use the container number in this field \u2013 container numbers are declared separately (see <em>Container Number<\/em> field). This field is for the primary transport unit. Ensure the format is correct: e.g., vessel IMO is usually seven digits (e.g. \u201c9303801\u201d), vehicle registrations should be entered without spaces or hyphers (e.g. \u201cAB12CDE\u201d) and in full.<\/li>\n<\/ul>\n<\/li>\n<li><strong>Example:<\/strong> IMO 931nakli \u2013 <strong>Incorrect<\/strong> (this is not purely numeric; IMO should be numeric only). Correct example: 9312345 for a ship\u2019s IMO. For a truck: AB12CDE (UK license plate), or 123XYZ456 for a non-UK plate (format varies by country). For a train: 746-555 (if the wagon number is 746-555, enter as given without additional text).<\/li>\n<li><strong>Common mistakes:<\/strong> Providing the wrong identifier (e.g. container number or an internal reference instead of the actual conveyance ID). For air shipments, a common error is putting the flight number here \u2013 do not do that (it belongs in Conveyance Reference). Also, including spaces or special characters is usually not allowed; follow the exact format (letters\/numbers only). If a vehicle has a trailer, do <strong>not<\/strong> list the trailer plate here for accompanied transport \u2013 only the tractor unit\u2019s reg is needed in this field for accompanied RoRo.<\/li>\n<\/ul>\n<p>[\/vc_column_text][vc_single_image image=&#8221;2755&#8243; img_size=&#8221;full&#8221;][vc_text_separator title=&#8221;&#8221;][vc_column_text]<\/p>\n<h3><strong>Customs Office of First Entry<\/strong><\/h3>\n<ul>\n<li><strong>Requirement:<\/strong> Mandatory (always required).<\/li>\n<li><strong>Level:<\/strong> Header-level (one code for the first place of arrival in GB).<\/li>\n<li><strong>Format:<\/strong> <strong>8-character code<\/strong> (an8) for the customs office\/port. The code structure is: first 2 characters = country code (e.g. GB), next up to 6 = specific port\/office identifier. All UK ports of entry have designated codes (for example, Dover might be GB000060, Felixstowe GB000103, etc.). A list of valid S&amp;S GB office codes is published by HMRC.<\/li>\n<li><strong>Guidelines:<\/strong> Enter the code of the <strong>first customs office of entry<\/strong> where the goods will arrive in Great Britain. This is typically the port, airport, or terminal where the goods are offloaded or enter GB\u2019s jurisdiction. For goods arriving by sea, it\u2019s the port of arrival; for air, the airport; for the Channel Tunnel, the code for the Eurotunnel terminal (e.g. Cheriton\/Dollands Moor). Ensure you use an <strong>official location code<\/strong> from HMRC\u2019s list \u2013 do not enter a free-text name of the port. The code must be exactly 8 characters (GB + 6 digits\/letters). <strong>Note:<\/strong> The list was updated in June 2025 with new codes, so ensure your reference data is up-to-date.<\/li>\n<li><strong>Example:<\/strong> GB000142 (London Heathrow Airport), GB000434 (Aberdeen seaport) \u2013 these codes uniquely identify the location.<\/li>\n<li><strong>Common mistakes:<\/strong> Using an incorrect or outdated code, or mixing up similar port names. Always double-check the code against the official list. Do not use a generic code (like \u201cGB000000\u201d) \u2013 each actual entry point has its own code. Also, do not confuse \u201cfirst office of entry\u201d in GB with any subsequent offices (if goods move onwards inland \u2013 those would be handled under separate optional data if applicable). Only the first entry point into GB goes here.<\/li>\n<\/ul>\n<p>[\/vc_column_text][vc_single_image image=&#8221;2753&#8243; img_size=&#8221;full&#8221;][vc_text_separator title=&#8221;&#8221;][vc_column_text]<\/p>\n<h3><strong>Expected Arrival Date and Time (at First Place of Arrival)<\/strong><\/h3>\n<ul>\n<li><strong>Requirement:<\/strong> Mandatory (always required) (denoted as \u201cExpected date and time of arrival at customs office of first entry\u201d).<\/li>\n<li><strong>Level:<\/strong> Header-level (one timestamp for the whole declaration).<\/li>\n<li><strong>Format:<\/strong> <strong>12 numeric digits<\/strong> (n12) in <em>YYYYMMDDHHMM<\/em> format. This represents a date and time in GMT (UTC). For example, 2025-08-15 14:30 GMT would be 202508151430.<\/li>\n<li><strong>Guidelines:<\/strong> Provide the <strong>scheduled date and time of arrival<\/strong> of the means of transport at the first place of entry (the customs office of first entry). This timestamp should be in <strong>Greenwich Mean Time (GMT)<\/strong> (note: UK local time may be BST in summer, but still provide GMT\/UTC). The required timing depends on mode:\n<ul>\n<li>For <strong>air<\/strong>: the time the aircraft is expected to land at the first UK airport.<\/li>\n<li>For <strong>sea (maritime)<\/strong>, including unaccompanied RoRo: the time the vessel is expected to arrive at the first UK port.<\/li>\n<li>For <strong>accompanied RoRo (ferry)<\/strong>: the time the ferry is expected to arrive at the port.<\/li>\n<li>For <strong>rail<\/strong> (e.g. Channel Tunnel freight train): the time the train is expected at the UK terminal (Dollands Moor for Channel Tunnel freight).<\/li>\n<li>For <strong>road via Channel Tunnel (accompanied)<\/strong>: the arrival time at the <em>Coquelles, France<\/em> Eurotunnel terminal is used as the reference (since that is the last control before entry).<br \/>This field acts as a consistent reference point for risk assessment. <strong>All ENS declarations for consignments on the same conveyance should use the exact same arrival time<\/strong>. In practice, carriers or ferry operators will publish an expected arrival time \u2013 use that so that all filings match. Do <strong>not<\/strong> adjust this time per consignment; it must remain consistent across all ENS for that journey.<\/li>\n<\/ul>\n<\/li>\n<li><strong>Example:<\/strong> For a vessel due on 5th March 2025 at 06:00 GMT, enter 202503050600. For a short-haul flight arriving 10 July 2025 18:45 GMT, enter 202507101845.<\/li>\n<li><strong>Common mistakes:<\/strong> Using local time or another time zone by mistake \u2013 <strong>always use GMT (UTC)<\/strong>. Also, providing an incorrect format (e.g. missing digits or using a different format) will cause errors \u2013 it must be exactly 12 numeric characters, YYYYMMDDHHMM. Another pitfall is not updating this if schedules change \u2013 if you know the scheduled arrival has significantly changed <strong>before<\/strong> departure, you should amend the ENS with the new time. Finally, ensure consistency: if you are an agent filing multiple ENS for shipments on one vessel\/flight, use the same date\/time on all to avoid discrepancies in the risk analysis process.<\/li>\n<\/ul>\n<p>[\/vc_column_text][vc_single_image image=&#8221;2758&#8243; img_size=&#8221;full&#8221;][vc_text_separator title=&#8221;&#8221;][vc_column_text]<\/p>\n<h3><strong>Place of Loading<\/strong><\/h3>\n<ul>\n<li><strong>Requirement:<\/strong> Mandatory (always required).<\/li>\n<li><strong>Level:<\/strong> This can be provided <strong>either at header or at each item<\/strong>, depending on your data. If all goods in the ENS were loaded at the same place, you can declare it once at header level. If different items have different loading places (in a consolidated ENS), you must provide it at item level for each item. (If you provide a header-level Place of Loading, you should not repeat it at item level, and vice versa.)<\/li>\n<li><strong>Format:<\/strong> Up to 35 characters, alphanumeric (an..35). This is a <strong>free-text<\/strong> field but with a required structure: it should begin with a 2-letter country code, followed by the name of the place. For RoRo accompanied and similar cases, include a postcode as well.<\/li>\n<li><strong>Guidelines:<\/strong> Indicate <strong>where the goods were loaded onto the active means of transport<\/strong> that is bringing them to the UK. The format and meaning differ by scenario:\n<ul>\n<li>For <strong>unaccompanied goods<\/strong> (e.g. a container shipped by sea, or goods in an unmanned trailer), the Place of Loading is the <strong>port or airport of departure<\/strong>. <strong>Begin with the country code<\/strong> of that location, then the name of the port\/airport\/terminal where the goods were loaded onto the vessel\/aircraft. <em>Example:<\/em> CNShanghai for Shanghai, China (though ideally include a space or hyphen for readability, e.g. CN Shanghai Pudong Airport). If it\u2019s a lesser-known location, spelling it out is fine (the field is free text but limited to 35 chars).<\/li>\n<li>For <strong>accompanied RoRo<\/strong> or <strong>road (Channel Tunnel)<\/strong> movements, the Place of Loading refers to the <strong>origin point where the goods were loaded onto the vehicle or trailer<\/strong> (since the vehicle itself is the means crossing the border). In these cases, provide the country code of that place, followed by the name of the warehouse, terminal, or address, and <strong>include the postcode<\/strong> if available. For instance, a truck loaded in a warehouse in Paris, France that then drives to Calais ferry: you might put FR Paris 75015 (FR + City + postcode) as the place of loading. If an exact facility name is known, include it for precision (e.g. FR Roissy CDG Cargo Terminal).<\/li>\n<\/ul>\n<\/li>\n<li><strong>Example:<\/strong> DE Hamburg (goods loaded at Hamburg, Germany port), CN Shenzhen Yantian (goods loaded at Yantian port in China), GB Leeds LS10 (for an accompanied truck loaded in Leeds, GB, going out and returning \u2013 rare inbound scenario).<\/li>\n<li><strong>Common mistakes:<\/strong> Not starting with the <strong>country code<\/strong> \u2013 this is required. Also, exceeding 35 characters with overly long descriptions \u2013 keep it concise (you might omit some detail if it doesn\u2019t fit). Avoid using only a country name without a specific place (e.g. just \u201cCN\u201d or \u201cChina\u201d is not sufficient; include city\/port). For road\/RoRo, not including a postcode or sufficient detail of the loading location is a common mistake \u2013 you should give as much detail as fits (country code + city or site + postcode). Remember that \u201cPlace of Loading\u201d is about where goods are put onto the <em>means of transport<\/em> that comes to UK, not necessarily the origin factory if that is inland \u2013 usually it coincides, but use the last loading point onto the actual outbound transport.<\/li>\n<\/ul>\n<p>[\/vc_column_text][vc_single_image image=&#8221;2759&#8243; img_size=&#8221;full&#8221;][vc_text_separator title=&#8221;&#8221;][vc_column_text]<\/p>\n<h3><strong>Place of Unloading<\/strong><\/h3>\n<ul>\n<li><strong>Requirement:<\/strong> Mandatory (always required).<\/li>\n<li><strong>Level:<\/strong> Header or item level (similar logic to Place of Loading). Use header-level if all goods share the same first unloading point; otherwise specify per item if different goods have different final discharge points in UK.<\/li>\n<li><strong>Format:<\/strong> Up to 35 characters, alphanumeric (an..35). Format is free text but must start with country code followed by location name\/postcode, as for Place of Loading.<\/li>\n<li><strong>Guidelines:<\/strong> Indicate the <strong>location where the goods will be unloaded from the active means of transport<\/strong> in Great Britain. Typically, this is the first place the goods are offloaded and presented to customs:\n<ul>\n<li>For <strong>unaccompanied goods (sea, air, unaccompanied RoRo):<\/strong> use the country code GB followed by the name of the port, airport, or terminal in Great Britain where the goods will be unloaded from the vessel\/aircraft. This is usually the same as the Customs Office of First Entry if that office code corresponds to a port. For example, GB Felixstowe or GB Southampton. If known, you can include a more specific terminal name or code within the port (keeping within length).<\/li>\n<li>For <strong>accompanied RoRo or road (Channel Tunnel):<\/strong> since the vehicle itself is the transport, the \u201cplace of unloading\u201d refers to where the goods are taken off the vehicle\/trailer. Often this will be an inland depot, warehouse, or distribution center. In these cases, start with GB and then the place name and postcode where the trailer will be unloaded. <em>Example:<\/em> GB Daventry NN6 for a warehouse in Daventry with postcode NN6\u2026, or GB Birmingham B6 7PR. Essentially, provide the country and city\/area for final unloading in the UK.<\/li>\n<\/ul>\n<\/li>\n<li><strong>Example:<\/strong> GB Liverpool (unloading at the Port of Liverpool), GB London Heathrow (air cargo unloaded at Heathrow Airport), GB Swindon SN4 8YZ (truck unloading at a Swindon depot).<\/li>\n<li><strong>Common mistakes:<\/strong> As with Place of Loading, forgetting the <strong>country code prefix<\/strong> \u201cGB\u201d. Also, some filers mistakenly put the final delivery destination if it\u2019s in another country (e.g. an ENS for transit through GB to Ireland might incorrectly put \u201cIE Dublin\u201d as place of unloading \u2013 that would be wrong because the ENS is only for GB entry; the place of unloading should still be a GB location where the goods are discharged\/presented to GB customs). If goods will immediately transit to another country without unloading in GB, still put the first point in GB (where they enter customs supervision) as unloading. Keep within 35 characters and include postcode for inland locations if possible.<\/li>\n<\/ul>\n<p>[\/vc_column_text][vc_single_image image=&#8221;2760&#8243; img_size=&#8221;full&#8221;][vc_text_separator title=&#8221;&#8221;][vc_column_text]<\/p>\n<h3><strong>Goods Description<\/strong><\/h3>\n<ul>\n<li><strong>Requirement:<\/strong> Mandatory for each goods item.<\/li>\n<li><strong>Level:<\/strong> Item-level (a description must be provided for each goods item in the ENS).<\/li>\n<li><strong>Format:<\/strong> Free text up to 280 characters (an..280). Language should be English (or at least understandable to customs in English). Avoid only numeric or code content \u2013 it should be plain language.<\/li>\n<li><strong>Guidelines:<\/strong> Provide a <strong>precise and plain language description of the goods<\/strong> sufficient for customs risk assessment. This description should clearly identify the goods <strong>without needing to refer to any codes or attached documents<\/strong>. <strong>Do NOT use vague or generic terms<\/strong> such as \u201cmiscellaneous\u201d, \u201cgeneral cargo\u201d, \u201cparts\u201d, \u201caccessories\u201d, \u201celectronics\u201d etc. \u2013 those are unacceptable. If you use overly general descriptions, customs may not be able to assess risk, potentially triggering delays or even physical examinations. Instead, use specific terms: for example, say \u201cmen\u2019s cotton shirts\u201d instead of \u201capparel\u201d; \u201cmobile phone accessories (chargers and cases)\u201d instead of just \u201caccessories\u201d. <strong>Never use the tariff HS code alone<\/strong> or technical codes as the description \u2013 you may include the HS code separately (commodity code field), but the description must be understandable text. HMRC provides an \u201cAcceptable goods description\u201d guide with examples: for instance, \u201c<em>Apparel<\/em>\u201d is too general, whereas \u201c<em>Men\u2019s shirts and women\u2019s blouses<\/em>\u201d is acceptable. \u201c<em>Electronics<\/em>\u201d is too broad; \u201c<em>Laptop computers and accessories<\/em>\u201d would be better.<\/li>\n<li><strong>Example:<\/strong>\n<ul>\n<li><strong>Good description:<\/strong> <em>\u201cStainless steel cutlery sets (forks, knives, spoons) \u2013 500 pieces\u201d<\/em>.<\/li>\n<li><strong>Poor description:<\/strong> <em>\u201cHousehold goods\u201d<\/em> or <em>\u201cKitchen items\u201d<\/em>.<\/li>\n<li><strong>Good description:<\/strong> <em>\u201c16\u201d alloy automotive wheels, brand XYZ\u201d<\/em>.<\/li>\n<li><strong>Poor:<\/strong> <em>\u201cCar parts\u201d<\/em>.<\/li>\n<li><strong>Common mistakes:<\/strong> Using freight shorthand or internal terms like \u201cFAK\u201d (\u201cFreight of All Kinds\u201d) \u2013 <strong>never use \u201cFAK\u201d<\/strong> or similar in ENS. Also, do not list only an HS code (e.g. \u201c6402.20 Footwear\u201d) without plain words \u2013 codes are optional elsewhere, not a substitute for description. Avoid languages other than English or overly technical product codes. If the item is a known dangerous good or sensitive item, be clear (and also use the UN Dangerous Goods Code field if applicable). A helpful tip is to ask: <em>If I only had this description, would I as a customs officer know roughly what the item is?<\/em> If not, make it more specific.<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<p>[\/vc_column_text][vc_single_image image=&#8221;2761&#8243; img_size=&#8221;full&#8221;][vc_text_separator title=&#8221;&#8221;][vc_column_text]<\/p>\n<h3><strong>Type of Packages (Packaging Kind Code)<\/strong><\/h3>\n<ul>\n<li><strong>Requirement:<\/strong> Mandatory for each goods item.<\/li>\n<li><strong>Level:<\/strong> Item-level (each goods item needs a packaging type code).<\/li>\n<li><strong>Format:<\/strong> A 2-letter code (an2) from the official \u201cKind of Packages\u201d code list. These are standard international codes (based on UN\/EU code lists) describing the packaging. For example, CT = Carton, PL = Pallet, BX = Box, BG = Bag, NE = unpackaged (unpacked or naked).<\/li>\n<li><strong>Guidelines:<\/strong> Choose the code that best describes how the goods are packaged. Refer to the <strong>HMRC \u201cKinds of Package\u201d code list<\/strong> for allowable codes. Common codes include: PK (Package, not otherwise specified), CT (Carton), PL (Pallet), BX (Box), BG (Bag), DR (Drum), VA (Van \u2013 for vehicles), LO (Loose, if no packaging but loaded in bulk or container), etc. The code NE (No packaging) is used for unpackaged items (bulk commodities, or items like machinery that aren\u2019t boxed). Ensure the code matches the actual physical state: e.g., if 100 boxes on 2 pallets, you might list package type as PL with number of packages as 2 (if you treat pallet as the handling unit), or possibly itemize as 100 BX \u2013 but normally, declare the <strong>exterior packaging unit count and type<\/strong> (see \u201cNumber of packages\u201d next).<\/li>\n<li><strong>Example:<\/strong> CT (Cartons), PL (Pallets), NE (No packaging \u2013 bulk cargo), AE (Aerosol), BB (Bags in big bag), etc. For instance, 10 pallets of goods would be type PL.<\/li>\n<li><strong>Common mistakes:<\/strong> Using a non-standard or invalid code (the system will reject unrecognized codes). <strong>Do not enter a description here<\/strong> \u2013 it must be the code, not \u201cboxes\u201d or \u201cpallet\u201d text. Also, ensure consistency with the <strong>Number of packages<\/strong> field: if you say type PL (pallet), the number of packages should correspond to number of pallets (not the items on them). If goods are truly bulk (no packages), use an appropriate code like NE and then use the \u201cNumber of pieces\u201d field if needed for loose pieces, or treat containers as packages per guidance.<\/li>\n<\/ul>\n<p>[\/vc_column_text][vc_single_image image=&#8221;2762&#8243; img_size=&#8221;full&#8221;][vc_text_separator title=&#8221;&#8221;][vc_column_text]<\/p>\n<h3><strong>Number of Packages<\/strong><\/h3>\n<ul>\n<li><strong>Requirement:<\/strong> Mandatory for each goods item, <em>except<\/em> in case of bulk goods.<\/li>\n<li><strong>Level:<\/strong> Item-level.<\/li>\n<li><strong>Format:<\/strong> Numeric, up to 5 digits (n..5).<\/li>\n<li><strong>Guidelines:<\/strong> Enter the <strong>quantity of packages<\/strong> for the item, based on the packaging unit declared. Essentially, how many packages of the type indicated contain the goods in this item. For example, if an item consists of 50 cartons (boxes) on a pallet, you might either declare \u201cNumber of packages = 50\u201d with type \u201cCT\u201d (cartons), or \u201c1\u201d with type \u201cPL\u201d (pallet) depending on how you choose to report (typically, customs wants the smallest external packages count). The number entered should reflect <em>the count of individual packages or pieces that cannot be divided without unboxing<\/em>.\n<ul>\n<li>If goods are in packages (boxes, pallets, drums, etc.), put the count of those packages.<\/li>\n<li>If goods are <strong>unpackaged (bulk or loose)<\/strong>, this field may not apply; instead use <strong>Number of Pieces<\/strong> (next field) for loose pieces, or if bulk liquid\/solid with no count, you can leave Number of Packages blank\/zero and use just the Gross Mass and possibly container count.<\/li>\n<li>If goods are in bulk but loaded in containers or vehicles, they are considered unpackaged in terms of shipping units; you might then not provide a package number but would provide container numbers.<\/li>\n<li>If more than one type of bulk cargo is present, and you need to specify count of \u201cpieces\u201d of bulk (e.g. two bulk items like two large machinery pieces that are not boxed), you can either use Number of Packages = 2 with an appropriate code (maybe NE) or use Number of Pieces = 2. The guidance indicates bulk goods don\u2019t require a number of packages, except if <strong>multiple distinct bulk units<\/strong> in one item, then you should state that number.<br \/>In summary, for <strong>most shipments<\/strong> you will put a positive integer here corresponding to packages. Only omit\/zero it for true bulk commodities that have no countable packages (then use \u201cNumber of pieces\u201d or nothing as appropriate).<\/li>\n<\/ul>\n<\/li>\n<li><strong>Example:<\/strong> 10 (meaning 10 packages of the type given, e.g. 10 pallets if type=PL, or 10 boxes if type=BX). If a container contains 100 loose items not boxed, you might use \u201cNumber of packages: 0\u201d with type NE and then use Number of Pieces for the 100 loose items. For bulk liquid in a tank, you would likely have Number of Packages not provided (bulk).<\/li>\n<li><strong>Common mistakes:<\/strong> Confusing \u201cNumber of packages\u201d with total pieces. For example, if you have 5 pallets each containing 50 boxes, you should not list 250 packages <em>if you are declaring the pallets as the package unit<\/em> (that would be contradictory). Decide on the level: either declare 5 pallets (PL) or 250 boxes (BX), but not both. Another mistake is providing this for bulk goods \u2013 if the goods are truly bulk (like oil, grain in bulk), <strong>do not fill a package count<\/strong> (use pieces or leave blank), since bulk by definition has no discrete packages. Lastly, avoid leading zeros (don\u2019t write \u201c005\u201d \u2013 just \u201c5\u201d), and ensure the number here aligns with the <strong>Total Number of Packages<\/strong> at header (if you use that optional field, see later).<\/li>\n<\/ul>\n<p>[\/vc_column_text][vc_single_image image=&#8221;2763&#8243; img_size=&#8221;full&#8221;][vc_text_separator title=&#8221;&#8221;][vc_column_text]<\/p>\n<h3><strong>Goods Item Number<\/strong><\/h3>\n<ul>\n<li><strong>Requirement:<\/strong> Mandatory (for each item).<\/li>\n<li><strong>Level:<\/strong> Item-level (each goods item in the ENS is numbered).<\/li>\n<li><strong>Format:<\/strong> Numeric, up to 5 digits (n..5). Typically this will be a simple integer like 1, 2, 3, etc.<\/li>\n<li><strong>Guidelines:<\/strong> This is the <strong>sequential count of the item within the declaration<\/strong>. Every ENS can contain multiple \u201citems\u201d (goods items), each representing a distinct commodity or consignment under the declaration. The first item is numbered \u201c1\u201d, the second \u201c2\u201d, and so on, up to the total number of items. The item number in each item\u2019s data should correspond to its sequence. In practice, if you\u2019re submitting an ENS with, say, 3 distinct items (perhaps 3 house bills in one master or 3 different types of goods), you will have item 1, item 2, item 3. The <strong>\u201cTotal number of items\u201d<\/strong> (a header field, if provided) should equal the highest item number. Each item\u2019s data block in the ENS message will include this item number. It\u2019s mostly for structure and reference (e.g., if an error is reported on item 2, you know which item\u2019s data to check).<\/li>\n<li><strong>Example:<\/strong> If an ENS contains two items \u2013 one for electronics and one for furniture \u2013 the first would have Goods item number = 1, the second = 2. If you have 10 items, they should be numbered 1 through 10. (Typically the software will handle numbering automatically, but you should ensure no duplicates or gaps.)<\/li>\n<li><strong>Common mistakes:<\/strong> Skipping or duplicating item numbers when constructing the ENS message. Each item must have a unique sequential number. Another mistake is misunderstanding this field\u2019s purpose \u2013 it\u2019s <em>not<\/em> a count of pieces or packages, just an index. Users don\u2019t manually enter this in forms (software usually assigns it), but if building an XML, ensure you number properly. Inconsistent numbering can lead to rejections or misinterpretation of \u201cNumber of items\u201d vs \u201cItem number concerned\u201d. For clarity, always also double-check the <strong>Total Number of Items<\/strong> field (if used) matches the count of item numbers provided.<\/li>\n<\/ul>\n<p>&nbsp;<\/p>\n<p><strong>Note:<\/strong><strong> <em>If you are filing your declaration via the <\/em><\/strong><a href=\"https:\/\/www.customs-declarations.uk\/safety-and-security-declarations-ens-service\/\" target=\"_blank\" rel=\"noopener\"><strong>Customs Declarations UK platform<\/strong><\/a><em><strong>, this field is automatically populated by the system. You do not need to enter this manually.<\/strong><\/em><\/p>\n<p>[\/vc_column_text][vc_text_separator title=&#8221;&#8221;][vc_column_text]<\/p>\n<h3><strong>Gross Mass (Total Gross Weight)<\/strong><\/h3>\n<ul>\n<li><strong>Requirement:<\/strong> Mandatory for each goods item <strong>and<\/strong> at the declaration header.<\/li>\n<li><strong>Level:<\/strong> Provide at item level (weight per item) and also the total gross weight at header level.<\/li>\n<li><strong>Format:<\/strong> Numeric, up to 11 digits before the decimal and up to 3 decimal places (n..11,3). This is measured in <strong>kilograms (kg)<\/strong>. Decimals (to 3 places) are allowed for precision (e.g. 1234.5 or 50.125).<\/li>\n<li><strong>Guidelines:<\/strong> <strong>Gross mass<\/strong> is the weight of the goods including all packaging, but excluding the carrier\u2019s transport equipment weight. In other words, the weight of the cargo plus its packaging\/pallets, etc., but <em>not<\/em> including the container or vehicle. State the weight in kilograms. You must provide a gross mass for each item, and it\u2019s recommended to also provide the total gross mass of all items at the declaration header (the system typically expects the header total = sum of item weights).\n<ul>\n<li>If you have a very small weight (under 1 kg), you might express it with decimals (e.g. 0.5 kg as \u201c0.5\u201d).<\/li>\n<li>Up to 3 decimal places can be used for fine precision (e.g. 1.275 for 1.275 kg).<\/li>\n<li>Do not include unit letters (\u201ckg\u201d) \u2013 just the number.<br \/>Ensure that the sum of all item gross masses equals the total gross mass at header (if the header total is required by system; some systems auto-calc, but as data it should match).<br \/>For bulk commodities, give the best estimate of weight.<\/li>\n<\/ul>\n<\/li>\n<li><strong>Example:<\/strong> 10000 (for 10,000 kg), 1234.56 (for 1,234.56 kg). If a shipment of 50 boxes weighs 200 kg net and packaging 20 kg, gross might be 220 kg, so you enter 220. The header total for two such items (say 220 kg + 180 kg) would be 400 kg.<\/li>\n<li><strong>Common mistakes:<\/strong> Using pounds or other units \u2013 <strong>always convert to kilograms<\/strong>. Including the weight of containers: e.g., if a container and goods weigh 5,000 kg but goods alone are 4,500 kg, you should use 4,500 kg (excluding the container tare). Also, not providing a header total when required \u2013 while the new \u201creduced dataset\u201d doesn\u2019t explicitly call for a separate field if item-level provided, ensure compliance with whatever the system expects. Rounding issues: if using decimals, be sensible (3 decimal places max). Do not add \u201ckg\u201d or other text. And double-check the values: unrealistic weights (like extremely low or high for the goods described) can raise queries; provide accurate weight to three significant digits if exact weight is unknown.<\/li>\n<\/ul>\n<p>[\/vc_column_text][vc_single_image image=&#8221;2764&#8243; img_size=&#8221;full&#8221;][vc_text_separator title=&#8221;&#8221;][vc_column_text]<\/p>\n<h3><strong>Seal Number<\/strong><\/h3>\n<ul>\n<li><strong>Requirement:<\/strong> Mandatory (if applicable; see below).<\/li>\n<li><strong>Level:<\/strong> Header-level (seals associated with the overall container\/trailer\/vessel at import).<\/li>\n<li><strong>Format:<\/strong> Up to 20 characters, alphanumeric (an..20). Free text allowed (letters and numbers). If multiple seals, multiple entries can be provided (depending on system, either space-separated or as repeating field). Each seal identifier should be given in full.<\/li>\n<li><strong>Guidelines:<\/strong> Provide the <strong>identification numbers of all seals<\/strong> affixed to the transport equipment (containers, trailers, etc.) or transport unit. Typically, if a container is sealed, it has a seal number (e.g., an alpha-numeric code on the bolt seal). If a truck trailer has a customs seal, provide that. If there are multiple containers or multiple seals, include each seal\u2019s number. If <strong>no seal is attached<\/strong>, you must explicitly indicate that by stating &#8220;No Seal&#8221; in this field. (The system expects either a seal ID or the text \u201cNo Seal\u201d if none.)\n<ul>\n<li>Make sure the seal number is exactly as affixed (case-sensitive usually, and include any prefixes).<\/li>\n<li>Do not use this field for lock numbers or other references \u2013 it is specifically for customs seals or transport seals.<\/li>\n<li>If multiple seals: depending on the ENS format, you might have to enter them separated by commas or as separate segments. In an HMRC API context, you may repeat the seal object for each seal. In a manual context, listing them separated by commas or spaces is typical.<\/li>\n<\/ul>\n<\/li>\n<li><strong>Example:<\/strong> ABC1234567 (a typical container bolt seal number), or No Seal (if the container\/trailer had no seal). If two seals: e.g. SEAL1001, SEAL1002.<\/li>\n<li><strong>Common mistakes:<\/strong> Not providing any indication when there are no seals \u2013 <strong>always put \u201cNo Seal\u201d if none are used<\/strong>, rather than leaving it blank (a blank might be interpreted as missing data rather than no seal). Also, giving an incorrect seal number (double-check against the physical seal). If a seal was broken and replaced in transit and you have the new number, use the latest seal number applicable upon arrival. Do not confuse container number with seal number \u2013 container identification goes in a different field. Seal number is usually shorter and purely identifies the sealing element.<\/li>\n<\/ul>\n<p>[\/vc_column_text][vc_single_image image=&#8221;2765&#8243; img_size=&#8221;full&#8221;][vc_text_separator title=&#8221;&#8221;][vc_column_text]<\/p>\n<h3><strong>Transport Document Number \/ Produced Documents and Certificates<\/strong><\/h3>\n<ul>\n<li><strong>Requirement:<\/strong> Mandatory (at least one transport document reference must be provided for each goods item).<\/li>\n<li><strong>Level:<\/strong> Item-level (each goods item should include references to its transport document(s) or supporting documents).<\/li>\n<li><strong>Format:<\/strong> Two parts \u2013 <strong>Document Type<\/strong> code (an..4) and <strong>Document Reference<\/strong> (an..35). The document type is a code from the official list (e.g., a code for Bill of Lading, Air Waybill, CMR, etc.), and the reference is the number or identifier of that document. Together, these identify the transport contract document or other required certificates for the consignment. You may have multiple such entries if more than one document applies.<\/li>\n<li><strong>Guidelines:<\/strong> For each item, you <strong>must provide all applicable transport document numbers<\/strong> and any required certificates or authorization references. This typically includes:\n<ul>\n<li>The primary <strong>transport document<\/strong> for the goods: e.g., the Bill of Lading number for sea freight, the Air Waybill (AWB) number for air freight, or the CMR number for road, etc. Use the appropriate <strong>document type code<\/strong> from HMRC\u2019s list (see the \u201cDocument Type\u201d appendix) and the document\u2019s reference number. For example, Bill of Lading might be coded 20 (hypothetical code) and reference \u201cOOLU1234567890\u201d. Air Waybill might be code 740 with reference the 11-digit AWB number.<\/li>\n<li>Any other <strong>international or national certificates or authorisations<\/strong> relevant to the shipment, if applicable, along with their references. For instance, if there is a phytosanitary certificate, export license, ATA carnet, etc., include those (each has a code in the document type list).<\/li>\n<li>The <strong>format<\/strong> is usually entered as a pair: \u201c \u201d. For example: 740-12345678901 could represent AWB number 12345678901 (if code 740 = Air Waybill). Some systems might have you enter them as separate fields.<\/li>\n<li><strong>Special rule (Carrier\u2019s document number):<\/strong> If <em>you<\/em> (the person lodging) are <strong>not the carrier<\/strong>, then in addition to the house bill or other references you provide, you must also provide the <strong>carrier\u2019s primary transport document number<\/strong>. For example, in consolidation: a freight forwarder lodging ENS for consolidated air freight must include each house AWB and also the master AWB of the carrier if different. In maritime, if a freight forwarder lodges for an LCL container, they include their house B\/L and also the vessel operator\u2019s master B\/L as another document reference. Essentially, <strong>\u201cWhere the person lodging the declaration is different from the carrier, the transport document number of the carrier shall also be provided.\u201d<\/strong>. This ensures customs can identify the shipment on the carrier\u2019s manifest.<\/li>\n<li>Use the HMRC <strong>Document Type code list<\/strong> (provided in the ENS dataset guidance) to find the right code for each document. For example, common codes: <strong>Bill of Lading<\/strong> = MAB, <strong>Master Air Waybill<\/strong> = 740, <strong>House Air Waybill<\/strong> = 741, <strong>CMR Road Waybill<\/strong> = 820, etc. <em>(These codes are illustrative; refer to the actual list for exact values.)<\/em><\/li>\n<\/ul>\n<\/li>\n<li><strong>Example:<\/strong> Suppose a sea freight shipment: you would enter something like Document Type \u2015 <strong>\u201cBill of lading\u201d code<\/strong> + <strong>B\/L number<\/strong>. E.g., EUR1 12345 (if an EUR1 certificate is present with reference 12345) as an additional document, or C501 999999 for a customs form if needed. For an air freight by a forwarder: Type 741 (House AWB) ref HAWB1234567, and also Type 740 (Master AWB) ref 156-12345678.<\/li>\n<li><strong>Common mistakes:<\/strong> Missing the carrier\u2019s document reference when filing as a third party. This is critical \u2013 if you are not the carrier, always include the carrier\u2019s main transport document number (otherwise the carrier\u2019s ENS or manifest may not match and could cause a query). Another mistake is using the wrong document type code, or a code that doesn\u2019t match the reference. For instance, using an AWB code but providing a sea container number is incorrect. Also ensure no typos in document numbers \u2013 they should exactly match the issued documents (including any prefixes like airline code in AWB, etc.). If multiple documents apply, provide them all; don\u2019t assume one is enough if several exist (e.g. both a B\/L and a phyto certificate). Finally, do not exceed the 35 character limit for references; if a reference is longer, check if perhaps only part of it is needed or if multiple references should be split.<\/li>\n<\/ul>\n<p>[\/vc_column_text][vc_single_image image=&#8221;2766&#8243; img_size=&#8221;full&#8221;][vc_text_separator title=&#8221;&#8221;][vc_column_text]<\/p>\n<h3><strong>Transport Charges Method of Payment<\/strong><\/h3>\n<ul>\n<li><strong>Requirement:<\/strong> Mandatory (always required).<\/li>\n<li><strong>Level:<\/strong> Provided at header and\/or item level. (In practice, the charge payment method often applies to the whole consignment, but can be itemized if different for different items \u2013 usually it\u2019s uniform.)<\/li>\n<li><strong>Format:<\/strong> A single-letter code (a1). There is a specific code list for <strong>method of payment for transport charges<\/strong>. Examples of these codes: A = Cash, B = Credit card, C = Cheque, D = Other, H = Electronic credit transfer, Y = Paid by other means, etc..<\/li>\n<li><strong>Guidelines:<\/strong> Enter the code that specifies how the <strong>transport (freight) costs are paid<\/strong> for the consignment. This refers to the payment of the carrier\u2019s freight charge. It\u2019s essentially who or how the freight is paid: e.g., prepaid, collect, etc., but given as method. The available codes are defined in the ENS data set (Method of Payment tab). For instance:\n<ul>\n<li>A \u2013 Payment in cash<\/li>\n<li>B \u2013 Payment by credit card<\/li>\n<li>C \u2013 Payment by cheque<\/li>\n<li>D \u2013 Other (any method not covered, possibly account or barter etc.)<\/li>\n<li>H \u2013 Electronic credit transfer (bank transfer)<\/li>\n<li>Y \u2013 (Often used for \u201cnot applicable\u201d or if transport is provided free of charge by an arrangement, etc. Some systems have Y for \u201cno charge\u201d).<br \/>Use the one that applies. If you\u2019re unsure (e.g. for large commercial shipments it might be paid by invoice which could be considered electronic transfer, so H), ask the carrier or look at the contract of carriage. <strong>All<\/strong> ENS must have this field \u2013 even if it seems not particularly critical, it\u2019s a safety\/security requirement under EU\/UK rules to indicate whether freight was paid and how.<\/li>\n<\/ul>\n<\/li>\n<li><strong>Example:<\/strong> For prepaid freight by bank transfer: use H. For freight to be paid on delivery by cash: A. For a DHL\/express consignment where shipping is billed to account (treated as other): could use D or if a known specific code for account, use it.<\/li>\n<li><strong>Common mistakes:<\/strong> Selecting a random code due to uncertainty \u2013 it\u2019s better to make an educated guess (e.g. most B2B shipments are via account\/invoice which equates to an electronic transfer, code H). Do not leave it blank. Also, not aligning with incoterms sometimes confuses people \u2013 but this field is <em>not<\/em> incoterms, it\u2019s strictly how freight charges are paid, not who pays (there\u2019s no field for payer, just method). Another mistake is using outdated codes \u2013 use the latest list provided (the ones above are current as per HMRC). Ensure only <strong>one letter<\/strong> is entered, no additional description.<\/li>\n<\/ul>\n<p>[\/vc_column_text][vc_single_image image=&#8221;2779&#8243; img_size=&#8221;full&#8221;][vc_text_separator title=&#8221;&#8221;][vc_column_text]<\/p>\n<h3><strong>Declaration Date and Time<\/strong><\/h3>\n<ul>\n<li><strong>Requirement:<\/strong> Mandatory (system-provided by declarant\u2019s software).<\/li>\n<li><strong>Level:<\/strong> Header-level.<\/li>\n<li><strong>Format:<\/strong> 12 numeric digits, YYYYMMDDHHMM (same format as arrival time). GMT time zone.<\/li>\n<li><strong>Guidelines:<\/strong> This is the <strong>date\/time when the ENS is issued (lodged)<\/strong> by you. Effectively, it\u2019s the timestamp of when your system created\/sent the declaration. It serves as a digital \u201csignature\u201d timestamp. Your software or the HMRC system will often populate this automatically, but if you need to provide it, use the current date\/time (in GMT) at the moment of submission. It must be in the specified format and in GMT.\n<ul>\n<li>Ensure this time is equal to or earlier than the actual submission time (you wouldn\u2019t post-date it).<\/li>\n<li>This field is largely for record and to fulfill the requirement that the declaration be \u201csigned or otherwise authenticated\u201d with date\/time.<\/li>\n<li>In amendments, a separate amendment timestamp is used, but for the original ENS, this is the one.<\/li>\n<li>If you are using the HMRC API or system, it will likely insert this for you. If manually filing (via a third-party interface), it might be filled behind the scenes. Just be aware it exists.<\/li>\n<\/ul>\n<\/li>\n<li><strong>Example:<\/strong> If submitting on 2025-07-03 at 02:30 GMT, the field would be 202507030230.<\/li>\n<li><strong>Common mistakes:<\/strong> Time zone confusion \u2013 it must be GMT, not local time (especially important if you\u2019re filing from a different time zone). Another mistake is not updating this field on each new declaration (re-using an old timestamp or a static value can cause errors). Generally, let your software handle it if possible. Also, the format is strict, so ensure zero-padding (e.g. January is \u201c01\u201d for month, 1 AM is \u201c01\u201d for hour, etc.). Missing this field will lead to rejection as it\u2019s mandatory that each ENS has a date\/time of declaration.<\/li>\n<\/ul>\n<p>&nbsp;<\/p>\n<p><strong>Note:<\/strong><strong> <em>If you are filing your declaration via the <\/em><\/strong><a href=\"https:\/\/www.customs-declarations.uk\/safety-and-security-declarations-ens-service\/\" target=\"_blank\" rel=\"noopener\"><strong>Customs Declarations UK platform<\/strong><\/a><em><strong>, this field is automatically populated by the system. You do not need to enter this manually.<\/strong><\/em><\/p>\n<p>[\/vc_column_text][vc_text_separator title=&#8221;&#8221;][vc_column_text]<\/p>\n<h2><span style=\"color: #ff0000;\"><strong>Conditional Fields (Required in Specific Situations)<\/strong><\/span><\/h2>\n<p>The following 8 fields are <strong>only required if certain conditions apply<\/strong> to the shipment. If the conditions are met, these fields become mandatory; otherwise they can be omitted. It\u2019s important to understand when to include them to ensure compliance:<\/p>\n<p>[\/vc_column_text][vc_text_separator title=&#8221;&#8221;][vc_column_text]<\/p>\n<h3><strong>Unique Consignment Reference Number (UCR) \u2013 Commercial Reference<\/strong><\/h3>\n<ul>\n<li><strong>Requirement:<\/strong> <strong>Conditional.<\/strong> Must be provided <strong>if you are a fast parcel operator or express carrier<\/strong>, or in similar scenarios where a UCR is used to identify a consignment. Optional for others.<\/li>\n<li><strong>Level:<\/strong> Header <em>and<\/em> item level (it may be provided once per declaration or per item if different per item, depending on usage). In many cases, a single UCR at header can cover all items if they are part of one consolidated consignment.<\/li>\n<li><strong>Format:<\/strong> Up to 70 characters (an..70). This is often structured following the <strong>WCO UCR format<\/strong>: ideally, it includes the year, the owner\u2019s EORI, and an internal reference. For example: 23GBABCDE1234567890 (year 2023, GB EORI prefix, plus internal ref). The WCO format recommendation is: <strong>YY + EORI + reference<\/strong>.<\/li>\n<li><strong>Guidelines:<\/strong> The UCR (also called UCN \u2013 Unique Consignment Reference) is a reference that uniquely identifies a consignment across supply chains. <strong>Fast parcel and express operators are required to provide a UCR<\/strong> for each consignment. This is because they often consolidate many small packages under one master transport document, and customs risk assessment can use the UCR to pinpoint a package. If you have a UCR, enter it here. If you are not an express carrier, you can still use this field to provide an additional commercial reference (like an internal tracking or invoice number) to help identify the goods.\n<ul>\n<li>A key advantage: If a UCR is provided, <strong>you do not need to provide individual transport document numbers for each consignment<\/strong> (because the UCR itself links to those details). However, many traders still provide both to be safe.<\/li>\n<li>Only use a UCR if it indeed is unique and follows the proper format; it should ideally be globally unique to that shipment.<\/li>\n<li>For example, express carriers often use a form of UCR that starts with the year and their company identifier.<\/li>\n<li>If you provide multiple ENS items each with their own UCR, that\u2019s possible too (each item\u2019s UCR must then be unique).<\/li>\n<\/ul>\n<\/li>\n<li><strong>Example:<\/strong> 25GBEORI123456789XYZ could be a UCR issued in 2025 by a company with EORI \u201cGBEORI123456789\u201d and reference \u201cXYZ\u201d. Another example: DHL might use something like 23GBDHLA1B2C3D4E5F as a UCR for a package.<\/li>\n<li><strong>Common mistakes:<\/strong> Using UCR improperly \u2013 e.g., putting a house bill number here thinking it\u2019s the UCR when it doesn\u2019t follow the format or isn\u2019t truly unique beyond that shipment. If you\u2019re not in the express parcel business, ensure the \u201cUCR\u201d you provide is indeed a unique reference that won\u2019t conflict with others. Don\u2019t confuse UCR with MRN or LRN; the UCR is more of a commercial tracking ID, not something assigned by customs (the MRN is assigned by customs <em>after<\/em> you file). If you don\u2019t have a UCR, you can leave this field blank \u2013 do <strong>not<\/strong> invent one just to fill it. Only use it when it adds value (e.g., to avoid listing many documents or to link shipments). Remember, if you use a UCR and skip transport document numbers on that basis, ensure that\u2019s acceptable \u2013 the HMRC guidance suggests if UCR is present, transport document numbers are not needed, but this might mainly apply in certain systems. It might be safer to include both UCR and transport docs unless you are certain.<\/li>\n<\/ul>\n<p>[\/vc_column_text][vc_text_separator title=&#8221;&#8221;][vc_column_text]<\/p>\n<h3><strong>Carrier (Entry Carrier Details)<\/strong><\/h3>\n<ul>\n<li><strong>Requirement:<\/strong> Conditional. Required if the <strong>carrier is different from the person lodging the ENS<\/strong>. If you (the filer) <em>are<\/em> the carrier, then you do not need to separately provide carrier details (since the \u201cPerson Lodging\u201d already identifies the carrier in that case). If you are filing on behalf of the carrier (e.g., a freight forwarder or agent), then you must provide the carrier\u2019s details here.<\/li>\n<li><strong>Level:<\/strong> Header-level.<\/li>\n<li><strong>Format:<\/strong> <strong>EORI\/TIN<\/strong> (an..17) plus <strong>Name and Address<\/strong> as needed. Specifically: Carrier EORI (if GB or non-GB), and if a non-GB EORI or no EORI is given, then the <strong>Name<\/strong> (an..35) and <strong>Address<\/strong> (Street, City, Postcode, Country \u2013 each field with similar length limits as consignor\/consignee) must be provided. If a <strong>GB EORI<\/strong> for the carrier is provided, name\/address are <em>optional<\/em> (not required). If an EU or other (non-GB) EORI is provided, name\/address must accompany it, as UK customs won\u2019t have those details on file.<\/li>\n<li><strong>Guidelines:<\/strong> The \u201cEntry Carrier\u201d is the <strong>party physically transporting the goods into the UK<\/strong> (e.g., the shipping line, airline, trucking company for accompanied, ferry operator for unaccompanied trailer, etc.). This section of the ENS must be completed by third-party filers to identify that actual carrier. Provide the carrier\u2019s <strong>legal name and address<\/strong> (if needed) and their <strong>EORI number<\/strong>. It\u2019s crucial that you have the carrier\u2019s <strong>knowledge and consent<\/strong> to lodge the ENS on their behalf; part of that is obtaining their EORI and info.\n<ul>\n<li><strong>EORI:<\/strong> Ideally, the carrier will have a GB EORI (especially if they operate in UK regularly). If so, include that; then you need not fill address.<\/li>\n<li>If the carrier only has an EU EORI or other identifier, include that as TIN and supply the name\/address fields as well.<\/li>\n<li>The data format is similar to consignor\/consignee: Name (35 char), Street (35), City (35), Postcode (9), Country (2).<\/li>\n<li><strong>Who is carrier?<\/strong> For sea, the ocean line or feeder operator. For air, the airline (though in air, often the carrier does their own ENS, but if not, then this is needed). For accompanied truck on ferry, the road haulage firm (truck owner) is the carrier at entry; for unaccompanied trailer on a ferry, the ferry operator is considered the carrier. Rail \u2013 the rail freight operator. Provide accordingly.<\/li>\n<\/ul>\n<\/li>\n<li><strong>Example:<\/strong> If you are a forwarder filing for a shipment arriving by Maersk Line vessel: Person lodging = you (forwarder\u2019s EORI), Carrier = Maersk Line\u2019s EORI GBMAERSK0000\u2026 plus maybe name \u201cMaersk Line A\/S\u201d if needed. If you are an express courier filing and you are the carrier, then Person Lodging is same as Carrier, so you wouldn\u2019t fill separate carrier. Another example: for an accompanied truck, if the haulage company is ABC Haulage Ltd (GB EORI GB123456789000), and you file on their behalf, provide that EORI as Carrier and you need not give their address (since GB EORI covers it).<\/li>\n<li><strong>Common mistakes:<\/strong> Not providing carrier info when you are not the carrier \u2013 this is a frequent error. Customs needs the carrier\u2019s identity; failing to include it could lead to rejection or compliance issues. Conversely, providing carrier details when not needed (like duplicating your own info if you <em>are<\/em> the carrier) isn\u2019t harmful per se, but could confuse the data. Also ensure the EORI is correct and active; using an incorrect carrier EORI might break the link for \u201cDo Not Load\u201d messages (which go to carrier\u2019s EORI). If the carrier has no EORI (unlikely for regular carriers, but if say a foreign airline that hasn\u2019t registered), use whatever TIN they have and definitely provide name\/address. Always double-check spelling of the carrier name and use the registered business name (matching EORI records).<\/li>\n<\/ul>\n<p>[\/vc_column_text][vc_single_image image=&#8221;2767&#8243; img_size=&#8221;full&#8221;][vc_text_separator title=&#8221;&#8221;][vc_column_text]<\/p>\n<h3><strong>Notify Party<\/strong><\/h3>\n<ul>\n<li><strong>Requirement:<\/strong> Conditional. Provide if there is a party who needs to be notified upon arrival <strong>and<\/strong> the information is available. <strong>Always<\/strong> required in the special case where the consignee is not named due to a negotiable <strong>\u201cto order\u201d<\/strong> bill of lading (blank endorsed) together with special mention code 10600. In that scenario, Notify Party becomes mandatory (since consignee is essentially \u201cTo Order\u201d). In other cases, if a notify party is listed on the B\/L or known in the shipping instructions, include it (though not strictly mandatory unless per contract it\u2019s needed).<\/li>\n<li><strong>Level:<\/strong> Can be provided at header or item (or both) \u2013 generally, if one notify party applies to the whole ENS, put at header; if different items have different notify parties, specify per item.<\/li>\n<li><strong>Format:<\/strong> <strong>Name<\/strong> (an..35), <strong>Address<\/strong> (Street an..35, City an..35, Postcode an..9, Country a2), and <strong>EORI\/TIN<\/strong> if available (an..17). Essentially same structure as consignor\/consignee. If a GB EORI is provided for the notify party, name\/address become optional (like with others) \u2013 but usually notify parties might not have GB EORI unless they are a UK entity.<\/li>\n<li><strong>Guidelines:<\/strong> The Notify Party is an entity (usually the buyer\u2019s agent, freight forwarder, or other interested party) who should be <strong>informed when the goods arrive<\/strong>. On some Bills of Lading, there\u2019s a \u201cNotify Party\u201d field (often used if the consignee is \u201cTo Order\u201d or if a third party like a warehouse or broker needs the arrival notice). Include these details if they exist. If goods are under a negotiable <em>to-order<\/em> B\/L with no fixed consignee, <strong>you must provide a notify party<\/strong> (someone to contact) \u2013 in fact, ENS in that case requires special mention code and notify party by law.\n<ul>\n<li>Provide the notify party\u2019s full name and address in the same format as other parties.<\/li>\n<li>If they have an EORI or trader ID and you know it, include it (especially if it\u2019s an EU\/GB EORI). That can help in linking data. However, it\u2019s not mandatory to have an EORI for notify.<\/li>\n<li>Only include one notify party per item ideally (if multiple, it complicates things \u2013 usually only one notify is listed on transport docs). If multiple are needed, use the one primarily responsible for reception of notice.<\/li>\n<li>If no notify party is applicable (e.g., consignee is a direct named party and no one else needs notice), you can omit this field.<\/li>\n<\/ul>\n<\/li>\n<li><strong>Example:<\/strong> A shipment\u2019s B\/L shows \u201cConsignee: To Order of XYZ Bank\u201d and \u201cNotify: ABC Imports Ltd, 22 Market St, London, GB\u201d. In ENS, since consignee isn\u2019t real (to order), you <em>must<\/em> put ABC Imports Ltd as Notify Party with their address and possibly EORI. Another example: Some forwarders list themselves as notify for house B\/L \u2013 if you as forwarder are to be notified, you could put your details.<\/li>\n<li><strong>Common mistakes:<\/strong> Not providing notify details when the B\/L is \u201cto order\u201d. This is a compliance requirement \u2013 customs want to know who will take delivery in such cases. Also, providing notify party when it\u2019s not needed can clutter data (though it won\u2019t usually cause rejection). If you do provide it, ensure the address is complete and formatted correctly (Name, address, country). Do not confuse \u201cNotify Party\u201d with \u201cRepresentative\u201d or declarant \u2013 it\u2019s specifically about who gets arrival notifications. Another mistake: forgetting to include notify when code 10600 (consignee unknown) special mention is used \u2013 remember those go hand-in-hand. If a notify party has an EORI, include it to simplify identification; if they don\u2019t, that\u2019s fine.<\/li>\n<\/ul>\n<p>[\/vc_column_text][vc_single_image image=&#8221;2768&#8243; img_size=&#8221;full&#8221;][vc_text_separator title=&#8221;&#8221;][vc_column_text]<\/p>\n<h3><strong>Conveyance Reference Number<\/strong><\/h3>\n<ul>\n<li><strong>Requirement:<\/strong> Conditional. <strong>Required for all modes EXCEPT<\/strong>: <strong>accompanied RoRo, unaccompanied RoRo, and road freight<\/strong>. In other words, you must provide this for Sea, Air, and Rail shipments. You should omit it (or it\u2019s not needed) for pure road movements (like EU to GB by truck through tunnel with driver) and for RoRo scenarios where the vessel\/vehicle info is captured elsewhere.<\/li>\n<li><strong>Level:<\/strong> Header-level (one per ENS, identifying the journey).<\/li>\n<li><strong>Format:<\/strong> Up to 35 characters, alphanumeric (an..35). This is typically a <strong>voyage or flight number, or train number<\/strong>. Format specifics:\n<ul>\n<li>For <strong>Air:<\/strong> Must be the flight number in a specific format: 2-3 letter airline code + 1-4 digit flight number + optional 1-letter suffix, with no spaces. Example: BA1234 or BA1234A. (Total up to 8 characters.)<\/li>\n<li>For <strong>Sea:<\/strong> Usually the vessel\u2019s voyage number (e.g., a service voyage code). Often an alphanumeric code assigned by the carrier like \u201cOA123E\u201d. However, HMRC has a special rule: if a sea conveyance reference begins with \u201cXFER\u201d, then it is indicating a Channel Tunnel <em>transfer<\/em> and must be followed by the lorry plate. In general for deep sea, just use the voyage number (without including vessel name here).<\/li>\n<li>For <strong>Rail:<\/strong> Use the train number or train identification for that journey.<\/li>\n<li>For <strong>Short sea RoRo ferries (unaccompanied):<\/strong> If needed, ferry operators might have voyage numbers, but since unaccompanied RoRo is exempt from requiring it, you typically don\u2019t put it.<\/li>\n<li><strong>No separators<\/strong> like hyphens except those that are part of the official number. For example, flight \u201cBA 123\u201d should be entered as BA123 (no space).<\/li>\n<\/ul>\n<\/li>\n<li><strong>Guidelines:<\/strong> This field identifies the <strong>specific journey of the means of transport<\/strong> into the UK. Provide:\n<ul>\n<li><strong>For Sea (vessel voyage):<\/strong> The official voyage number. E.g., if the ship\u2019s voyage is 2105W, put that. <strong>Special case \u2013 Channel Tunnel through freight (also coded as sea in some contexts)<\/strong>: The rule mentioned is if you use \u201cXFER\u201d prefix (indicating a truck transferred via ferry perhaps), you must directly append the truck\u2019s registration without spaces. Actually, \u201cXFER\u201d usage is a bit niche \u2013 likely for mixed mode (ferry + road) scenarios. In general, avoid starting a conveyance ref with \u201cXFER\u201d unless instructed and you include the reg plate right after it (like XFERAB12CDE).<\/li>\n<li><strong>For Air:<\/strong> Use the flight number exactly as assigned. Include the airline code (e.g., BA, KL, CX) and the numeric. If there is a suffix (like A, B for multi-segment flights), include it. Do <em>not<\/em> include route info or date, just the flight ID.<\/li>\n<li><strong>For Rail:<\/strong> Use the train number that the rail operator uses for that service on that date.<br \/>This field is crucial for customs to link all ENS for one voyage\/flight together.<\/li>\n<\/ul>\n<\/li>\n<li><strong>Example:<\/strong>\n<ul>\n<li>Sea: HOEG1234 (voyage number of a container ship).<\/li>\n<li>Air: BA431 for British Airways flight 431.<\/li>\n<li>Air with suffix: CK257A for Cathay Pacific flight 257A.<\/li>\n<li>Rail: EUR123 for a Eurotunnel freight train.<\/li>\n<li>Special: XFERAB12CDE (if a code \u201cXFER\u201d is used followed by a truck reg AB12CDE to indicate a transfer).<\/li>\n<\/ul>\n<\/li>\n<li><strong>Common mistakes:<\/strong> Providing this for modes where not required (like putting a truck reg here for a road movement \u2013 that actually should not be here because accompanied RoRo and pure road have it elsewhere). For air, a common mistake is including the flight date or airport, e.g. \u201cBA431\/10JUL\u201d \u2013 do <strong>not<\/strong> include date or slash, only the flight code. For sea, sometimes people put the vessel name here; do not put \u201cMV MSC Example\u201d \u2013 vessel name is not requested here (the identity is given in the \u201cIdentity of transport\u201d field via IMO). Use the voyage or schedule number. Also ensure no spaces or special characters; the entire string is alphanumeric continuous. If the voyage number isn\u2019t known (rare, carriers always have one), you must get it from the carrier. Not providing this for an Air or Sea shipment is a serious omission \u2013 customs use it to issue \u201cDo Not Load\u201d messages for high-risk shipments (especially for deep-sea, where they send DNL by referencing voyage and document number). So make sure it\u2019s accurate.<\/li>\n<\/ul>\n<p>[\/vc_column_text][vc_single_image image=&#8221;2769&#8243; img_size=&#8221;full&#8221;][vc_text_separator title=&#8221;&#8221;][vc_column_text]<\/p>\n<h3><strong>Number of Pieces (Unpackaged Goods)<\/strong><\/h3>\n<ul>\n<li><strong>Requirement:<\/strong> Conditional. Required <strong>if goods are unpackaged<\/strong> (i.e., no \u201cpackages\u201d to count, but you have individual pieces). If you indicated a package type of \u201cNE\u201d (No packaging) or otherwise have loose items, then you should provide the count of pieces here. Not required if Number of Packages already covers the count (for packaged goods) or for bulk commodities measured by mass\/volume.<\/li>\n<li><strong>Level:<\/strong> Item-level.<\/li>\n<li><strong>Format:<\/strong> Numeric, up to 5 digits (n..5).<\/li>\n<li><strong>Guidelines:<\/strong> This field captures the <strong>count of individual pieces<\/strong> when goods are not packaged in defined packages. Use it in scenarios like: vehicles being shipped (each vehicle is a piece, unpackaged), machinery not on pallets, bulk items counted by piece (e.g., logs, steel beams \u2013 they might be unpackaged but you can count them), or empty containers, etc. If you have already given a \u201cNumber of packages,\u201d you normally wouldn\u2019t give \u201cnumber of pieces\u201d as well, <em>unless<\/em> some items in that goods item are unpackaged in addition to packaged (which would be unusual). Essentially:\n<ul>\n<li>If <strong>Kind of Packages<\/strong> = NE (unpacked) or similar, provide the total number of individual items. For example, 5 vehicles on a RoRo ship might be kind NE and number of pieces = 5.<\/li>\n<li>If bulk liquid or grain, you don\u2019t really have \u201cpieces\u201d (that would be measured by volume\/weight, not count), so you would not use this field \u2013 bulk is just bulk (no packages, no pieces).<\/li>\n<li>For goods like large machinery or project cargo that are not in crates, count each unit as a piece.<\/li>\n<li>If goods are palletized or in packages, this field stays blank because you use Number of Packages instead.<\/li>\n<\/ul>\n<\/li>\n<li><strong>Example:<\/strong> A car carrier ship ENS item for 100 cars: Number of packages = (blank or 0, since no packages), Number of pieces = 100. Another example: a large industrial machine not crated: Number of pieces = 1 (one item, unpackaged). If you had, say, 3 big turbines not in crates, pieces = 3.<\/li>\n<li><strong>Common mistakes:<\/strong> Providing a number here when you\u2019ve already provided a number of packages \u2013 this could double count if misunderstood. Use one or the other as appropriate. Another mistake is failing to provide this when it actually should be (e.g., listing package type \u201cNE\u201d and leaving piece count empty \u2013 customs won\u2019t know how many items that covers). Also, people sometimes confuse \u201cNumber of pieces\u201d with \u201cNumber of packages\u201d \u2013 remember pieces is only for unpackaged scenarios. Don\u2019t put \u201c1\u201d piece for bulk liquid; that doesn\u2019t make sense. Bulk commodities typically have neither packages nor pieces (just weight).<\/li>\n<\/ul>\n<p>[\/vc_column_text][vc_single_image image=&#8221;2770&#8243; img_size=&#8221;full&#8221;][vc_text_separator title=&#8221;&#8221;][vc_column_text]<\/p>\n<h3><strong>Shipping Marks and Numbers of Packages<\/strong><\/h3>\n<ul>\n<li><strong>Requirement:<\/strong> Conditional. <strong>Must be provided for all packaged goods<\/strong> (i.e., if the goods are in packages that have markings). Not required if goods are unpackaged or if they are containerized loose bulk inside (see below).<\/li>\n<li><strong>Level:<\/strong> Item-level.<\/li>\n<li><strong>Format:<\/strong> Free text, up to 140 characters (an..140).<\/li>\n<li><strong>Guidelines:<\/strong> This field is for the <strong>marks and numbers<\/strong> on packages, which help identify them externally. Typically, for ocean freight, it refers to the stenciled or labeled markings on crates, bags, boxes, etc. For example, a shipment might have packages labeled \u201c1 of 10, 2 of 10, \u2026 10 of 10, ACME Co. Ltd.\u201d \u2013 those are the shipping marks. You should provide a <strong>brief description of the marks and numbers<\/strong> on the packages. If packages are simply numbered, you can state the range (e.g., \u201cPackages numbered 1-10\u201d). If they are unmarked, you can state \u201cNo marks and numbers\u201d. If the goods are containerized <em>and the packages inside have no separate marks<\/em>, and especially if goods are loose in a container, this field can be skipped <strong>only if<\/strong> container number is provided instead (since the container number then identifies it). Specifically:\n<ul>\n<li><strong>For all packaged goods<\/strong> not in a freight container: provide whatever is written on the packages \u2013 e.g., \u201cBrown cartons on 10 pallets, marked \u2018ACME Electronics\u2019\u201d.<\/li>\n<li><strong>If goods are loose in a container or vehicle (unpackaged bulk in container)<\/strong>: you don\u2019t need marks (since none on bulk), but <strong>you must provide the Container Number<\/strong> in that case and you can leave marks empty.<\/li>\n<li>Essentially, customs wants either \u201cmarks and numbers\u201d or a container number to identify the cargo units. If you have a container, focus on container number; if break-bulk (not containerized), provide marks on packages.<\/li>\n<li>When providing marks, be concise but clear. It can include any alphanumeric sequences or descriptions that appear on packaging.<\/li>\n<\/ul>\n<\/li>\n<li><strong>Example:<\/strong> \u201cCases labeled \u2018Machine Parts, ABC Corp\u2019 numbered 001-050\u201d, or \u201cBags marked \u2018Product of Kenya\u2019, lot 2025, 20 bags\u201d. If no marks: \u201cNo marks\u201d (though strictly, if truly no marks, the field shouldn\u2019t be empty \u2013 explicitly say no marks or similar). In container shipments where the container is sealed and used as package: you could leave it blank and ensure container number is given.<\/li>\n<li><strong>Common mistakes:<\/strong> Not providing this for break-bulk or LCL cargo \u2013 if goods aren\u2019t in a full container or are in crates, etc., you need to fill this. Another mistake is writing generic things like \u201cN\/M\u201d (no marks) for everything out of habit \u2013 only use \u201cNo marks\u201d if genuinely the packages have no identifying marks. If the package has a customer name or code, that should be put. Also, do not confuse this with the goods description; marks and numbers are typically identifiers, not a description of contents. And do not list the container number here \u2013 container has its own field. If packages have serial numbers, you can list those as marks too. Ensure not to exceed 140 chars; if marks are very long (some shipments have lengthy markings), summarize as needed.<\/li>\n<\/ul>\n<p>[\/vc_column_text][vc_single_image image=&#8221;2771&#8243; img_size=&#8221;full&#8221;][vc_text_separator title=&#8221;&#8221;][vc_column_text]<\/p>\n<h3><strong>Container Number \/ Trailer Number<\/strong><\/h3>\n<ul>\n<li><strong>Requirement:<\/strong> Conditional. Must be provided <strong>when the goods are containerized or moved in a transport unit identified by a trailer number<\/strong>. Specifically, if goods are in a shipping container, or in an unaccompanied trailer, or any similar unit load device that has an ID, you need this. Not required for bulk or break-bulk that is not in a container\/trailer.<\/li>\n<li><strong>Level:<\/strong> Item-level (each goods item can have one or more container numbers if applicable; if one item spans multiple containers, list each; if multiple items in one container, each item entry can repeat the same container number).<\/li>\n<li><strong>Format:<\/strong> Up to 17 characters, alphanumeric (an..17). Typically, ISO container numbers are 11 characters (e.g., MSCU1234567), but trailers or other equipment might have different formats. Provide the identifier without spaces. For ISO containers: four letters + seven digits (with an optional check digit as last digit). For road trailers: often a license plate or unit number.<\/li>\n<li><strong>Guidelines:<\/strong> Enter the <strong>unique identifier of the container or trailer<\/strong> that the goods are transported in.\n<ul>\n<li>For standard shipping <strong>containers<\/strong>, use the container number (e.g., ABCD1234567). This must match the format registered (letters and digits, usually 4 letters + 7 digits).<\/li>\n<li>For <strong>road trailers (unaccompanied RoRo)<\/strong>, if a trailer (with no truck) is put on a ferry, provide the trailer registration number here. Use the format as per national registration (for example, a UK trailer might have a plate, or the ferry might assign a trailer ID \u2013 but generally use the number on the trailer). Ensure to follow any specifics (the guidance notes that the trailer number provided should be the one <strong>registered with the national authority<\/strong> in that country of registration).<\/li>\n<li>If a container is on a trailer, <strong>prefer the container number<\/strong> over the trailer number in this field (because container is a more specific identifier of the goods). So, if you have a container on a chassis, give container number, not the chassis plate.<\/li>\n<li>If multiple containers\/trailers are under one ENS item, include each (many systems allow repeating the field or listing multiple separated by commas).<\/li>\n<li>This field is critical for enabling customs to tie the ENS to physical units at the port. If goods are containerized, do not omit the container number.<\/li>\n<li>Note: If goods are loose in a container (LCL or bulk in container), you <strong>must<\/strong> have container number and you might skip marks as discussed. Also, if multiple consignments in one container, they all share container number but have distinct ENS, which is fine.<\/li>\n<\/ul>\n<\/li>\n<li><strong>Example:<\/strong> MSCU1234567 (container number), TLLU8899001, TRLU2233445 etc. For a trailer: maybe TRL-12345 if that\u2019s the trailer ID (but typically just the plate like \u201cXYZ123\u201d). Always double-check container numbers for accuracy (they are often mis-typed; ensure check digit is correct).<\/li>\n<li><strong>Common mistakes:<\/strong> Forgetting to include container numbers on FCL (full container) shipments \u2013 a serious omission that will be flagged. Also, mixing up trailer vs container: e.g., putting a truck\u2019s tractor plate here for accompanied transport (don\u2019t do that; accompanied truck\u2019s identity is captured as vehicle reg in Identity of means of transport, not here). Only use this for actual standalone transport units carrying goods:\n<ul>\n<li>Unaccompanied trailer on ferry \u2192 trailer reg here.<\/li>\n<li>Container on ship (or on rail, or on road) \u2192 container number here.<\/li>\n<li>ULD (air cargo Unit Load Device) \u2013 interestingly, ULD numbers are not usually required in ENS, but some might put in this field if treating a ULD like a container. However, generally, air doesn\u2019t require container numbers, so not needed.<\/li>\n<li>Another mistake: including spaces or lowercases in container numbers. Use upper-case letters and no spaces (e.g., write MSCU1234567, not \u201cMSCU 123456-7\u201d or such).<\/li>\n<li>If one consignment spans multiple containers, be sure to list all container numbers for that item (some might erroneously only list one). And if one container has multiple items, ensure each item record gets the container number.<\/li>\n<li>Also note, if goods are out-of-gauge or no container (just on flatbed), you wouldn\u2019t have a container number \u2013 that\u2019s fine, then this field is not applicable.<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<p>[\/vc_column_text][vc_single_image image=&#8221;2772&#8243; img_size=&#8221;full&#8221;][vc_text_separator title=&#8221;&#8221;][vc_column_text]<\/p>\n<h3><strong>UN Dangerous Goods Code<\/strong><\/h3>\n<ul>\n<li><strong>Requirement:<\/strong> Conditional. Required if the goods being shipped are classified as <strong>dangerous goods under the UN ADR\/IMDG\/IATA codes<\/strong>. In practice, if the commodity has a UN number (UN 4-digit code for hazardous materials), you must declare it. If no part of the shipment is dangerous, you omit this field.<\/li>\n<li><strong>Level:<\/strong> Item-level (only for the items that are dangerous).<\/li>\n<li><strong>Format:<\/strong> 4-digit numeric code (n4). This is the <strong>UN Number<\/strong> assigned to the hazardous substance (from the UN dangerous goods list, e.g., UN1203 for gasoline, UN1993 for flammable liquid n.o.s., etc.). It should be exactly four digits (include leading zeros if any, e.g., UN0082 should be \u201c0082\u201d).<\/li>\n<li><strong>Guidelines:<\/strong> If the goods item is classified as <strong>hazardous<\/strong>, provide the UN Dangerous Goods code (UN number) that corresponds to the substance or article. This allows customs and emergency authorities to know the nature of dangerous cargo. You should also ensure any required <em>additional info or documents<\/em> (like special certificates) are in the ENS if needed, but code-wise:\n<ul>\n<li>Use the primary UN number. If an item contains multiple hazardous materials with different UN numbers, ideally each would be declared as separate items with their respective codes. If they are mixed packing, list the most appropriate or multiple if allowed.<\/li>\n<li>The code must be valid from the UN list (1 to 4 digits, often 4 digits with leading zeros up to 4). For example: explosives UN 0335, flammable liquids UN 1263, etc.<\/li>\n<li>There\u2019s typically no need to prefix with &#8220;UN&#8221;, just the number (some systems accept with \u201cUN\u201d but here guidance implies just numeric).<\/li>\n<li>This field is only for substances that have a UN number. It\u2019s not used for other hazardous indicators (like class only \u2013 the actual UN number is required).<\/li>\n<\/ul>\n<\/li>\n<li><strong>Example:<\/strong> If shipping paint that is flammable, UN1263 is the code (would enter 1263). If shipping lithium batteries, UN3480 perhaps. If multiple hazard codes apply, you might have multiple entries or separate items. If shipping non-dangerous goods, leave blank.<\/li>\n<li><strong>Common mistakes:<\/strong> Not providing the UN code when shipping declared dangerous goods \u2013 for instance, if you have indicated on the manifest that it\u2019s haz cargo but forgot to put the code here, that\u2019s an error. Another mistake is putting an IMO Class or packing group instead of the UN number (the ENS specifically wants the UN four-digit code, not \u201cClass 3\u201d etc.). Also be careful to use the updated UN code if it changed (sometimes new substances get new UN numbers). If an item like \u201cPerfumes\u201d is flammable and has UN1266, you must include 1266. If you\u2019re unsure whether something is classified, check transport documents or MSDS \u2013 if a UN number is assigned there, use it. Avoid leading\/trailing spaces or adding \u201cUN\u201d letters. And ensure it\u2019s 4 digits (if you have a three-digit one, pad with a zero in front, though most are 4). Omission of a required UNDG code could result in fines or safety issues, so be diligent if any hazardous materials are involved.<\/li>\n<\/ul>\n<p>[\/vc_column_text][vc_single_image image=&#8221;2773&#8243; img_size=&#8221;full&#8221;][vc_text_separator title=&#8221;&#8221;][vc_column_text]<\/p>\n<h2><span style=\"color: #ff0000;\"><strong>Optional Fields (Additional Information, Provided If Available)<\/strong><\/span><\/h2>\n<p>These 9 fields are <strong>optional<\/strong> \u2013 you are not required to supply them for ENS acceptance, but providing them when relevant can add clarity or fulfill specific business needs. If you have the information readily, it can be good practice to include it. However, leaving them blank has no negative effect on compliance (except where their absence might lose some benefit, like identifying special status).<\/p>\n<p>[\/vc_column_text][vc_text_separator title=&#8221;&#8221;][vc_column_text]<\/p>\n<h3><strong>Commodity Code<\/strong><\/h3>\n<ul>\n<li><strong>Requirement:<\/strong> Optional.<\/li>\n<li><strong>Level:<\/strong> Item-level.<\/li>\n<li><strong>Format:<\/strong> Up to 8 digits (an..8, usually numeric). This corresponds to the HS (Harmonized System) tariff code of the goods, typically the first 4 or 6 or 8 digits of the commodity\u2019s tariff classification.<\/li>\n<li><strong>Guidelines:<\/strong> You may provide the commodity\u2019s tariff code to help describe the goods. It is <strong>not mandatory for ENS<\/strong> in GB, but traders sometimes include it. If provided, HMRC allows you to use the <strong>first 4 digits of the 8-digit commodity code<\/strong> (i.e., the HS chapter and heading) if you don\u2019t want to give the full code. The rationale is that a 4-digit HS chapter can give a general idea of goods type. Of course, you can give the full 8-digit UK commodity code if you wish (or presumably even 10-digit if known, though the data element says 8).\n<ul>\n<li>Use only valid HS codes as per the UK Tariff. For example, 8517 for telephone equipment (first 4 digits of an 8-digit code like 85177000).<\/li>\n<li>This field supplements the goods description; it should align with it (for instance, if your description says \u201cmen\u2019s cotton shirts\u201d, a commodity code might be 6105 for men\u2019s shirts).<\/li>\n<li>Including the code can assist customs in risk analysis (certain high-risk goods might be flagged by code), but it\u2019s optional because the description is primary.<\/li>\n<\/ul>\n<\/li>\n<li><strong>Example:<\/strong> 8542 (for electronic integrated circuits), 100630 (for semi-milled or wholly milled rice \u2013 6 digits), or 87032390 (8-digit for certain motor cars). If you choose 4 digits: just 8703 would indicate motor cars generally.<\/li>\n<li><strong>Common mistakes:<\/strong> If provided, ensure the code matches the description. A mismatch (like description \u201ctextiles\u201d but code is for \u201celectronics\u201d) could confuse or raise questions. Also, don\u2019t exceed 8 digits or include decimal points\/spaces (some people format HS codes with periods like \u201c85.17\u201d \u2013 do not do that, just continuous digits). Another mistake is thinking this replaces a proper description \u2013 it does not. Always still give a good description; the code is supplementary. If unsure of the exact code, it might be better to omit than to guess incorrectly, since an incorrect code could mislead (though optional, it\u2019s not validated for accuracy at ENS stage, but still).<\/li>\n<\/ul>\n<p>[\/vc_column_text][vc_single_image image=&#8221;2774&#8243; img_size=&#8221;full&#8221;][vc_text_separator title=&#8221;&#8221;][vc_column_text]<\/p>\n<h3><strong>Total Number of Packages (Header)<\/strong><\/h3>\n<ul>\n<li><strong>Requirement:<\/strong> Optional.<\/li>\n<li><strong>Level:<\/strong> Header-level.<\/li>\n<li><strong>Format:<\/strong> Numeric, up to 7 digits (n..7).<\/li>\n<li><strong>Guidelines:<\/strong> This is the <strong>aggregate count of all packages<\/strong> in the entire ENS declaration (summing across all items). If you choose to provide it, it should equal the sum of the \u201cNumber of packages\u201d (and pieces, where applicable) of all items on the declaration. Specifically, if you have 3 items with 10, 5, and 2 packages respectively, the total number of packages would be 17 (assuming none are bulk). If some items are bulk with no packages, see bullet two:\n<ul>\n<li>When calculating, for bulk items (no packages) that are in containers or such, count each unit of transport or grouping as per guidance. HMRC notes: <em>if present, this number must equal the sum of all \u2018Number of packages\u2019 + \u2018Number of pieces\u2019 at item level, <strong>+1 for any goods declared as bulk<\/strong><\/em>. This implies if you had an item declared as bulk (no packages, no pieces, just bulk weight), you still count that as 1 for the purpose of total packages count. So bulk item counts as one \u201cpackage\u201d conceptually.<\/li>\n<li>Also, no leading zeros allowed (don\u2019t do 00017, just 17).<\/li>\n<li>Providing this field can be a nice cross-check; customs or your own system can verify the consistency. The system might throw an error if the total doesn\u2019t match the sum of items when it is provided. If you\u2019re not confident to maintain it, you can omit it since it\u2019s optional. Many modern systems auto-calculate it if needed.<\/li>\n<\/ul>\n<\/li>\n<li><strong>Example:<\/strong> If ENS contains items with package counts 5, 3, and one bulk item, total number of packages = 5 + 3 + (bulk counts as 1) = 9. If just two items with 100 and 50 packages, total = 150.<\/li>\n<li><strong>Common mistakes:<\/strong> Providing a total that doesn\u2019t match the detail. If you put a total, double-check sums. Another mistake is misunderstanding the \u201c+1 for bulk\u201d rule \u2013 it\u2019s a bit counterintuitive, but basically bulk still occupies space so they count it as a unit. If you had all bulk and you put 0, that would conflict (they expect at least 1 if an item exists). If you omit this field entirely, then no issue arises. If your software auto-fills it, ensure it updates when you add\/remove items. And do not include containers or vehicles in this count (only packages\/pieces as defined). If you had provided Number of Pieces for unpackaged items, include those in sum.<\/li>\n<\/ul>\n<p>&nbsp;<\/p>\n<p><strong>Note:<\/strong><strong> <em>If you are filing your declaration via the <\/em><\/strong><a href=\"https:\/\/www.customs-declarations.uk\/safety-and-security-declarations-ens-service\/\" target=\"_blank\" rel=\"noopener\"><strong>Customs Declarations UK platform<\/strong><\/a><em><strong>, this field is automatically populated by the system. You do not need to enter this manually.<\/strong><\/em><\/p>\n<p>[\/vc_column_text][vc_single_image image=&#8221;2775&#8243; img_size=&#8221;full&#8221;][vc_text_separator title=&#8221;&#8221;][vc_column_text]<\/p>\n<h3><strong>Total Number of Items<\/strong><\/h3>\n<ul>\n<li><strong>Requirement:<\/strong> Optional.<\/li>\n<li><strong>Level:<\/strong> Header-level.<\/li>\n<li><strong>Format:<\/strong> Numeric, up to 5 digits (n..5).<\/li>\n<li><strong>Guidelines:<\/strong> This is simply the <strong>count of goods items<\/strong> declared in the ENS. In other words, how many separate item entries (with their own descriptions etc.) are in the declaration. If provided, it must equal the actual number of item data groups included and have no leading zeros. Typically, if you have item 1, item 2, item 3 in the ENS, Total number of items = 3. This is usually obvious from the structure of the message, so providing it is redundant but can serve as a check. Many systems automatically derive it. It\u2019s optional to explicitly state it.<\/li>\n<li><strong>Example:<\/strong> If you\u2019re declaring a consolidated ENS with 10 items (perhaps 10 House bills), you could put 10. If a single-consignment ENS, you could put 1.<\/li>\n<li><strong>Common mistakes:<\/strong> Not matching the actual count. If you list 5 items but mistakenly put 6, that\u2019s an inconsistency. This might cause an error or at least confusion. Another trivial mistake could be including leading zeros (\u201c05\u201d instead of \u201c5\u201d). Given it\u2019s optional, some choose not to include this field at all; that avoids any risk of mismatch. If you do include it, update it whenever items are added or removed prior to submission.<\/li>\n<\/ul>\n<p>&nbsp;<\/p>\n<p><strong>Note:<\/strong><strong> <em>If you are filing your declaration via the <\/em><\/strong><a href=\"https:\/\/www.customs-declarations.uk\/safety-and-security-declarations-ens-service\/\" target=\"_blank\" rel=\"noopener\"><strong>Customs Declarations UK platform<\/strong><\/a><em><strong>, this field is automatically populated by the system. You do not need to enter this manually.<\/strong><\/em><\/p>\n<p>[\/vc_column_text][vc_text_separator title=&#8221;&#8221;][vc_column_text]<\/p>\n<h3><strong>Specific Circumstance Indicator<\/strong><\/h3>\n<ul>\n<li><strong>Requirement:<\/strong> Optional.<\/li>\n<li><strong>Level:<\/strong> Header-level.<\/li>\n<li><strong>Format:<\/strong> 1-letter code (a1). Possible values are defined in the \u201cSpecific Circumstance Indicator\u201d code list, such as:\n<ul>\n<li>A \u2013 Postal\/Express consignments<\/li>\n<li>B \u2013 (Not listed above, but possibly reserved)<\/li>\n<li>C \u2013 Road mode of transport<\/li>\n<li>D \u2013 Rail mode of transport<\/li>\n<li>E \u2013 AEO (Authorized Economic Operator) consignment<br \/><em>(These codes come from the list: A, C, D, E\u2026)<\/em><\/li>\n<\/ul>\n<\/li>\n<li><strong>Guidelines:<\/strong> This indicator is used to signal special handling or circumstances of the shipment. In UK ENS context:\n<ul>\n<li><strong>A (Postal and express consignments):<\/strong> Use if the ENS is for postal packets or express parcels. This might group those under certain risk rules.<\/li>\n<li><strong>C (Road mode):<\/strong> Possibly used if goods are accompanied road shipments (though mode is anyway road, this flag might distinguish something, but given the code list description, it&#8217;s likely meant for something like &#8220;Inland waterways or road from particular places&#8221;? Actually the list specifically says C = Road mode, D = Rail mode. This likely originated from EU ICS where for road and rail, entry summary declarations had waivers or special handling).<\/li>\n<li><strong>D (Rail mode):<\/strong> Use if goods arrive by rail (perhaps to indicate a special simplified process for rail?).<\/li>\n<li><strong>E (AEO):<\/strong> Use this to indicate that the consignment is covered by AEO security arrangements \u2013 <strong>but crucially, HMRC notes that you can only use <\/strong><strong>E<\/strong><strong> if the Person Lodging AND all Consignees have AEO certificates (AEOS or AEOF).<\/strong> If a representative is lodging, they must also be AEO if this is an amendment by rep, according to notes.<\/li>\n<li>If conditions for E are met (all parties are AEO), setting this flag might expedite or reduce intervention, as it tells customs this is an AEO-to-AEO movement.<\/li>\n<li>If none of these specific scenarios apply or you\u2019re not sure, leave it blank. Many ENS filings will have no specific indicator.<\/li>\n<\/ul>\n<\/li>\n<li><strong>Example:<\/strong> A courier company filing a bulk ENS of parcels may put A to indicate it&#8217;s express consignments. A freight train arrival from the Channel Tunnel might use D. If a certified AEO importer is receiving goods from an AEO exporter and an AEO carrier lodges the ENS, they might use E (ensuring all have that status).<\/li>\n<li><strong>Common mistakes:<\/strong> Misusing E without meeting the criteria \u2013 this is a validation rule. If you put E but, say, one of your consignees is not AEO, you would be in breach of the rule. Customs could cross-check AEO status and your ENS could be flagged or considered non-compliant. Only use E if you <em>know<\/em> everyone involved holds AEO(Safety) status. The other codes (A, C, D) are less critical but still only use them in the correct context (e.g., don\u2019t randomly use C or D unless it\u2019s indeed road or rail import under some special program). Since these indicators might tie into waived or simplified processes, using them incorrectly could cause issues (for example, code C and D might relate to movements that don\u2019t need ENS under certain agreements, etc., but in GB post-Brexit context, road\/rail from EU do need ENS, so not entirely clear \u2013 they might keep these codes for legacy or analysis). When in doubt, leaving it blank is safe.<\/li>\n<\/ul>\n<p>[\/vc_column_text][vc_text_separator title=&#8221;&#8221;][vc_column_text]<\/p>\n<h3><strong>Special Mentions (Additional Information Codes)<\/strong><\/h3>\n<ul>\n<li><strong>Requirement:<\/strong> Optional.<\/li>\n<li><strong>Level:<\/strong> Item-level.<\/li>\n<li><strong>Format:<\/strong> Alphanumeric code up to 5 characters (an..5). These codes correspond to predefined \u201cAdditional Information\u201d or \u201cSpecial Mentions\u201d code list entries. For example, one known code is <strong>\u201c10600\u201d<\/strong> which indicates a \u201cConsignee not known \u2013 to order BL\u201d scenario. There are likely other codes for things like diplomatic shipment, military, humanitarian aid, etc., if applicable.<\/li>\n<li><strong>Guidelines:<\/strong> Special mentions are used to convey certain standard additional information to customs in code form. If a particular situation applies, you enter the relevant code from the <strong>Additional Information (AI) code list<\/strong>. Some scenarios where an AI code might be used in ENS:\n<ul>\n<li><strong>Consignee unknown (Negotiable B\/L)<\/strong>: Code 10600 should be used when a negotiable <strong>\u201cTo Order\u201d<\/strong> bill of lading is present and thus consignee isn\u2019t named. In that case, as mentioned earlier, Notify Party must be provided. The presence of code 10600 alerts customs that consignee is \u201cTo Order\u201d.<\/li>\n<li>Other possible codes might relate to goods under certain treaties or other special status (the actual list would define them).<\/li>\n<li>The ENS data guidance suggests to refer to the Additional Information tab for codes. It\u2019s optional, so if no special mention applies, leave blank.<\/li>\n<li>Use the code exactly as given (usually numeric or alphanumeric). If multiple codes apply to one item, you might list multiple occurrences of this field or combine if format allows.<\/li>\n<\/ul>\n<\/li>\n<li><strong>Example:<\/strong> For a shipment on a bill of lading \u201cto order\u201d, you would include special mention code 10600 on that item, and provide Notify Party. Another example: if there were a code for \u201cEU transit under TIR\u201d or something (just hypothetical), you could include that if relevant. But common ENS AI codes in UK are few; 10600 is a key one.<\/li>\n<li><strong>Common mistakes:<\/strong> Forgetting to include 10600 when required \u2013 if consignee is blank and you have a notify party because of a to-order B\/L, you should include that code to formally indicate why consignee is blank. Conversely, do not use 10600 if you actually have a named consignee (it\u2019s only for to-order). If you don\u2019t know any special codes, you likely don\u2019t need this field. Also, do not confuse these codes with other code lists (document codes, etc.). They are a distinct list purely for extra info. Ensure any code used is from the official list \u2013 an arbitrary text here won\u2019t be recognized.<\/li>\n<\/ul>\n<p>[\/vc_column_text][vc_text_separator title=&#8221;&#8221;][vc_column_text]<\/p>\n<h3><strong>Signature and Authentication<\/strong><\/h3>\n<ul>\n<li><strong>Requirement:<\/strong> Optional (often system-generated).<\/li>\n<li><strong>Level:<\/strong> Header-level (represents declaration authentication overall).<\/li>\n<li><strong>Format:<\/strong> This isn\u2019t a user-entered data element per se, but conceptually it\u2019s an indication of signature. Some systems might have a code or digital signature. Often, simply submitting via your credentials is considered an electronic signature.<\/li>\n<li><strong>Guidelines:<\/strong> In the context of ENS filings, <strong>signature and authentication<\/strong> refers to the legal requirement that the declaration is authenticated by the person lodging. In practice, when you submit the ENS through the S&amp;S GB system (whether via API or a third-party platform), that action serves as your \u201csignature\u201d. The ENS message structure contains fields like \u201cDeclaration date and time\u201d (which we provided) and possibly an electronic signature field, but <strong>for the trader there is no additional data you must input<\/strong> beyond using your EORI credentials. If an explicit field exists in the format (for example in some EDIFACT message versions, a declarant&#8217;s signature code might exist), the system usually populates it or it&#8217;s left blank if not required.\n<ul>\n<li>Since the user specifically asked to include this: one can note that <strong>no physical or scanned signature is required<\/strong>. Instead, ensure you have provided all authentication details per system (like your login, digital certificate, etc.).<\/li>\n<li>If the platform asks for a \u201cDeclarant\u2019s reference or signature code\u201d, you can use your name or a simple text, but generally it\u2019s not needed in S&amp;S GB API.<\/li>\n<\/ul>\n<\/li>\n<li><strong>Example:<\/strong> <em>N\/A.<\/em> (There isn\u2019t an example value as such; it\u2019s implicitly covered by the declaration submission process). If it were an EDIFACT message, it might carry a code like \u201c\/SIGN\/\u201d segment or similar, but with modern API it\u2019s behind the scenes.<\/li>\n<li><strong>Common mistakes:<\/strong> Not applicable, since nothing explicit to fill. Just remember that the act of submission is legally binding \u2013 ensure the information is true and complete to the best of your knowledge, as that is effectively your attestation. If using a third-party, you as the carrier still carry the responsibility, so proper delegation is important.<\/li>\n<\/ul>\n<p>[\/vc_column_text][vc_text_separator title=&#8221;&#8221;][vc_column_text]<\/p>\n<h3><strong>Declaration Place<\/strong><\/h3>\n<ul>\n<li><strong>Requirement:<\/strong> Optional.<\/li>\n<li><strong>Level:<\/strong> Header-level.<\/li>\n<li><strong>Format:<\/strong> Free text, up to 35 characters (an..35).<\/li>\n<li><strong>Guidelines:<\/strong> This is a brief text indicating <strong>where the declaration was made<\/strong> (for example, the office or city from which you, the declarant, are lodging it). It\u2019s an old-style data element primarily carried over from customs forms where you\u2019d write the place of signing. In electronic submissions, it\u2019s less significant. If provided, it might be your company\u2019s location or \u201cOffice of [Company], [City]\u201d. The guidance says it should be specific, e.g., an EU country name rather than just \u201cEU\u201d \u2013 but since now it\u2019s GB, you can put a city and country.\n<ul>\n<li>It\u2019s completely fine to leave blank. If you want to use it, you could put the city\/country from which you\u2019re filing or where your office is.<\/li>\n<li>Could also be used if someone is filing on behalf of someone else from a different location, to indicate origin of the declaration.<\/li>\n<\/ul>\n<\/li>\n<li><strong>Example:<\/strong> London, GB or Manchester, UK or ABC Ltd, Glasgow. Or a full address of office if you wanted (but 35 char limit means keep it short). For instance: \u201cBelfast GB\u201d.<\/li>\n<li><strong>Common mistakes:<\/strong> Almost none, since it\u2019s rarely used. If using, don\u2019t just say \u201cGB\u201d or \u201cEU\u201d \u2013 be a bit more specific as note suggests. Also, do not confuse this with Office of Entry or anything \u2013 it literally is just the place of filling out the form. Many leave it blank in digital age.<\/li>\n<\/ul>\n<p>[\/vc_column_text][vc_text_separator title=&#8221;&#8221;][vc_column_text]<\/p>\n<h3><strong>Nationality of Active Means of Transport (Crossing the Border)<\/strong><\/h3>\n<ul>\n<li><strong>Requirement:<\/strong> Optional (only relevant for certain modes).<\/li>\n<li><strong>Level:<\/strong> Provided at header or item (likely header) when applicable.<\/li>\n<li><strong>Format:<\/strong> 2-letter country code (a2).<\/li>\n<li><strong>Guidelines:<\/strong> This denotes the <strong>country of registration of the active means of transport<\/strong> entering the UK. In practice, it&#8217;s meaningful for certain modes like road vehicles, maybe aircraft or vessels if needed, but usually:\n<ul>\n<li>It\u2019s particularly noted as applicable when transport mode is <strong>3 (Road)<\/strong>, <strong>10 (RoRo accompanied)<\/strong>, or <strong>11 (RoRo unaccompanied)<\/strong>. For these, the nationality of the truck (for road) or the ferry (for unaccompanied, which might already be known from vessel ID, but anyway) might be of interest.<\/li>\n<li>For example, a truck with Polish plates might put PL as nationality of vehicle. For an accompanied truck on a ferry, the active means is the truck (driving), so its nationality could be given (though not required). For an unaccompanied trailer, the \u201cactive means\u201d is the ferry (which is sea mode, usually we would use vessel IMO and maybe flag, but the note specifically lists road and ro-ro codes for using this field).<\/li>\n<li>For other modes like sea and air, the vessel\/aircraft flag state is typically not needed in ENS (the IMO or flight covers identity). So it seems HMRC expects usage mostly for surface transport.<\/li>\n<li>If provided, just use the country code of the vehicle\u2019s registration country.<\/li>\n<\/ul>\n<\/li>\n<li><strong>Example:<\/strong> A UK truck -&gt; GB. A truck with license plate registered in France -&gt; FR. If a ferry\u2019s active means for unaccompanied, ferry\u2019s flag maybe, but since they said for 10 and 11 as well, maybe the trailer reg country? Actually, for unaccompanied trailer, the active means is the ferry (sea), but they still list code 11 in applicability. Possibly they mean if an unaccompanied trailer, put nationality of trailer reg (since trailer is kind of passive though). It\u2019s a bit ambiguous, but you can provide if known. For example, trailer registered in Germany, code DE.<\/li>\n<li><strong>Common mistakes:<\/strong> Not really critical if omitted (since optional). If used, ensure it\u2019s a valid country code. Don\u2019t confuse this with nationality of crew or anything \u2013 it\u2019s specifically the vehicle\/vessel registration country. Some might think to always put something here for vessels; that\u2019s usually not needed (vessel flag is not required in ENS by code, though if you did, it wouldn\u2019t harm likely). Only provide for modes specified if you want. Given it\u2019s optional, many ENS filings skip it. If you operate a large fleet through UK, you might use it for data analysis or something. Just ensure it matches the actual registration; e.g. an Irish truck = IE, not UK.<\/li>\n<\/ul>\n<p>[\/vc_column_text][vc_text_separator title=&#8221;&#8221;][vc_column_text]<\/p>\n<h3><strong>Office of Subsequent Entry<\/strong><\/h3>\n<ul>\n<li><strong>Requirement:<\/strong> Optional.<\/li>\n<li><strong>Level:<\/strong> Header-level, likely as a structured data object (if goods will travel to another customs territory after GB).<\/li>\n<li><strong>Format:<\/strong> Customs Office Code, 8 characters (an..8) for the subsequent entry point.<\/li>\n<li><strong>Guidelines:<\/strong> This field is used <strong>if some of the goods in the ENS are destined to be transported onward to another customs office of entry after GB<\/strong>. In EU ICS, this is used when goods, after first entry, will enter another member state. In UK context, this could be relevant if goods are continuing to Northern Ireland or EU after arriving in GB, or possibly if an ENS is covering multiple legs. For Great Britain ENS, normally the journey ends in GB, so subsequent entry might not commonly apply except for transit cases. However, if you know that part of the consignment will move under transit to, say, an EU country, you could optionally inform a subsequent office.\n<ul>\n<li>Essentially, you\u2019d provide the customs office code of the next entry point beyond the UK. For example, if goods after UK will go to Ireland, you might put IE\u2019s port code. Or if some of the goods go to Northern Ireland after arriving in GB (though NI ENS is separate, so this is less likely needed here).<\/li>\n<li>If provided, it should be the same format of code (country+6 digits) as other office codes. It\u2019s an indicator for multi-stop routes.<\/li>\n<li>If you have multiple subsequent entries (goods splitting to different destinations), you might have a complex scenario; typically not covered in a single ENS since ENS is arrival-based.<\/li>\n<\/ul>\n<\/li>\n<li><strong>Example:<\/strong> After arriving at GB, goods will also officially enter EU at Rotterdam, you might put NL000001 for Port of Rotterdam as subsequent entry. Or goods destined to Dublin after Holyhead, put IEXXXXX (the code for Dublin port). This is hypothetical because usually those would have their own ENS in EU side. Possibly more relevant if UK had an arrangement. It\u2019s optional so rarely used.<\/li>\n<li><strong>Common mistakes:<\/strong> This field is seldom used; a mistake would be to fill it thinking of final destination country erroneously. Only use if you truly are coordinating multi-territory entry. Given GB is a single customs territory, and if goods leave GB for EU, an EU ENS is needed separately \u2013 so from GB ENS perspective, you typically don\u2019t need to list subsequent entry. Including such might confuse if not correct. If unsure, it\u2019s best left blank.<\/li>\n<\/ul>\n<p>[\/vc_column_text][vc_text_separator title=&#8221;&#8221;][vc_column_text]<\/p>\n<h3><strong>Conclusion and Best Practices<\/strong><\/h3>\n<p>Filing an ENS accurately is crucial for compliance with UK safety and security regulations. By completing all <strong>mandatory fields<\/strong> and the relevant <strong>conditional fields<\/strong> (only when required), and using the <strong>optional fields<\/strong> to provide additional clarity when available, carriers and filers can ensure smooth processing of their Entry Summary Declarations. Remember the following best practices:<\/p>\n<ul>\n<li><strong>Double-check codes and references:<\/strong> Ensure all codes (country codes, document type codes, package codes, etc.) are valid and up-to-date from HMRC\u2019s published lists. Small typos (e.g., using \u201cUK\u201d vs \u201cGB\u201d, transposing letters in container or EORI numbers) can lead to rejections or misrouting.<\/li>\n<li><strong>Use specific and accurate information:<\/strong> The more precise your data (goods description, routing, etc.), the better customs can assess risk without needing to intervene. Avoid generic terms that could trigger manual checks.<\/li>\n<li><strong>Consistency is key:<\/strong> Totals should match the sum of parts (items vs. total items, packages vs. total packages) whenever those optional fields are used. Also, information in ENS should be consistent with other documents (for example, the MRN you receive back will tie to the info provided \u2013 inconsistencies with manifests or transit declarations can cause issues).<\/li>\n<li><strong>Timeliness:<\/strong> Submit the ENS within the legal timeframes before arrival (e.g. 2 hours before for short sea, 4 hours for long haul air, etc., as summarized in HMRC guidelines). Late submissions can result in penalties or \u201cDo Not Load\u201d messages.<\/li>\n<li><strong>Amend when necessary:<\/strong> If you realize any detail is incorrect or has changed (and goods haven\u2019t arrived yet), submit an amendment with the corrected data. Use the same LRN (now MRN) when amending, and include all original data plus changes. Note you cannot change certain key identifiers (like Person Lodging) via amendment.<\/li>\n<li><strong>Retention of evidence:<\/strong> Keep copies of the ENS data (or at least the LRN\/MRN and key info) for audit purposes. You may need to provide evidence of ENS filing to carriers or port authorities (e.g., via GVMS you might link ENS MRNs).<\/li>\n<li><strong>Compliance and support:<\/strong> Be aware that failure to submit ENS or providing incorrect data can lead to delays, fines, or goods being refused loading or entry. If you encounter technical issues, HMRC\u2019s ICS helpdesk can assist. Always provide the LRN or MRN when querying a specific declaration.<\/li>\n<\/ul>\n<p>&nbsp;<\/p>\n<p>By following this comprehensive field-by-field guidance, freight forwarders, carriers, and logistics professionals can confidently prepare UK ENS submissions that meet HMRC\u2019s requirements and contribute to a secure and efficient supply chain. Each data element, when optimally provided, helps paint a complete picture of the shipment for customs \u2013 reducing uncertainties and facilitating smooth clearance. Compliance with these guidelines ensures you fulfill the legal obligations while minimizing the risk of customs interventions or penalties.<\/p>\n<p>[\/vc_column_text][vc_text_separator title=&#8221;&#8221;][\/vc_column][\/vc_row][vc_row][vc_column][vc_separator][vc_column_text]<\/p>\n<p><span style=\"color: #999999;\"><em><span style=\"font-weight: 400;\"><b><i>We value your feedback, and if you have any comments, suggestions or anything else that you would like to highlight to us, we will be delighted to hear from you and incorporate your feedback into our content. <\/i><\/b><\/span><\/em><\/span><\/p>\n<p><em>Note: While we have made every attempt to ensure that the information contained in this Site has been obtained from reliable sources, Customs Declarations UK is not responsible for any errors or omissions, or for the results obtained from the use of this information. All information in this Site is provided &#8220;as is&#8221;, with no guarantee of completeness, accuracy, timeliness or of the results obtained from the use of this information, and without warranty of any kind, express or implied, including, but not limited to warranties of performance, merchantability and fitness for a particular purpose. Nothing herein shall to any extent substitute for the independent investigations and the sound technical and business judgment of the reader. In no event will Customs Declarations UK, or its partners, employees or agents, be liable to you or anyone else for any decision made or action taken in reliance on the information in this Site or for any consequential, special or similar damages, even if advised of the possibility of such damages. Certain links in this Site connect to other Web Sites maintained by third parties over whom Customs Declarations UK has no control. Customs Declarations UK makes no representations as to the accuracy or any other aspect of information contained in other Web Sites.<br \/><\/em><\/p>\n<p>[\/vc_column_text][\/vc_column][\/vc_row]<\/p>\n","protected":false},"excerpt":{"rendered":"<p>[vc_row][vc_column][vc_text_separator title=&#8221;&#8221;][vc_column_text] Introduction An Entry Summary Declaration (ENS) is a pre-arrival electronic notification required for most goods entering Great Britain. It provides UK customs authorities with essential information about the goods, allowing them to assess safety and security risks before the goods arrive. The ENS is submitted via HMRC\u2019s Safety &amp; Security GB (S&amp;S GB) [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":2734,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[17,18],"tags":[],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v16.5 - https:\/\/yoast.com\/wordpress\/plugins\/seo\/ -->\n<meta name=\"description\" content=\"At Custom-Declarations.com, we believe that considering the end-to-end workflow is crucial to cross-border trading. We have created a business friendly tool that will consider both your needs and those of your customers when handling customs declarations.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.customs-declarations.uk\/hmrc-safety-security-gb-entry-summary-declaration-ens-data-entry-field-requirement-guidelines\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"HMRC Safety &amp; Security \/ GB Entry Summary Declaration (ENS) Data Entry &amp; Fields Requirement Guidelines | Customs-Declarations.UK\" \/>\n<meta property=\"og:description\" content=\"At Custom-Declarations.com, we believe that considering the end-to-end workflow is crucial to cross-border trading. We have created a business friendly tool that will consider both your needs and those of your customers when handling customs declarations.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.customs-declarations.uk\/hmrc-safety-security-gb-entry-summary-declaration-ens-data-entry-field-requirement-guidelines\/\" \/>\n<meta property=\"og:site_name\" content=\"Customs-Declarations.UK\" \/>\n<meta property=\"article:publisher\" content=\"https:\/\/www.facebook.com\/CustomsDeclarationsUK\" \/>\n<meta property=\"article:published_time\" content=\"2025-08-06T18:25:11+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2026-05-28T09:26:22+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/www.customs-declarations.uk\/wp-content\/uploads\/2025\/07\/CD-Thumbnail-14.jpg\" \/>\n\t<meta property=\"og:image:width\" content=\"1280\" \/>\n\t<meta property=\"og:image:height\" content=\"720\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:creator\" content=\"@DeclarationsUk\" \/>\n<meta name=\"twitter:site\" content=\"@DeclarationsUk\" \/>\n<meta name=\"twitter:label1\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data1\" content=\"72 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"Organization\",\"@id\":\"https:\/\/www.customs-declarations.uk\/#organization\",\"name\":\"Customs-Declarations\",\"url\":\"https:\/\/www.customs-declarations.uk\/\",\"sameAs\":[\"https:\/\/www.facebook.com\/CustomsDeclarationsUK\",\"https:\/\/www.linkedin.com\/company\/customs-declarations-uk\",\"https:\/\/twitter.com\/DeclarationsUk\"],\"logo\":{\"@type\":\"ImageObject\",\"@id\":\"https:\/\/www.customs-declarations.uk\/#logo\",\"inLanguage\":\"en-US\",\"url\":\"https:\/\/www.customs-declarations.uk\/wp-content\/uploads\/2021\/05\/logo.png\",\"contentUrl\":\"https:\/\/www.customs-declarations.uk\/wp-content\/uploads\/2021\/05\/logo.png\",\"width\":468,\"height\":100,\"caption\":\"Customs-Declarations\"},\"image\":{\"@id\":\"https:\/\/www.customs-declarations.uk\/#logo\"}},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/www.customs-declarations.uk\/#website\",\"url\":\"https:\/\/www.customs-declarations.uk\/\",\"name\":\"Customs-Declarations.UK\",\"description\":\"Swift Customs Declarations Service\",\"publisher\":{\"@id\":\"https:\/\/www.customs-declarations.uk\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":\"https:\/\/www.customs-declarations.uk\/?s={search_term_string}\",\"query-input\":\"required name=search_term_string\"}],\"inLanguage\":\"en-US\"},{\"@type\":\"ImageObject\",\"@id\":\"https:\/\/www.customs-declarations.uk\/hmrc-safety-security-gb-entry-summary-declaration-ens-data-entry-field-requirement-guidelines\/#primaryimage\",\"inLanguage\":\"en-US\",\"url\":\"https:\/\/www.customs-declarations.uk\/wp-content\/uploads\/2025\/07\/CD-Thumbnail-14.jpg\",\"contentUrl\":\"https:\/\/www.customs-declarations.uk\/wp-content\/uploads\/2025\/07\/CD-Thumbnail-14.jpg\",\"width\":1280,\"height\":720},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/www.customs-declarations.uk\/hmrc-safety-security-gb-entry-summary-declaration-ens-data-entry-field-requirement-guidelines\/#webpage\",\"url\":\"https:\/\/www.customs-declarations.uk\/hmrc-safety-security-gb-entry-summary-declaration-ens-data-entry-field-requirement-guidelines\/\",\"name\":\"HMRC Safety & Security \/ GB Entry Summary Declaration (ENS) Data Entry & Fields Requirement Guidelines | Customs-Declarations.UK\",\"isPartOf\":{\"@id\":\"https:\/\/www.customs-declarations.uk\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\/\/www.customs-declarations.uk\/hmrc-safety-security-gb-entry-summary-declaration-ens-data-entry-field-requirement-guidelines\/#primaryimage\"},\"datePublished\":\"2025-08-06T18:25:11+00:00\",\"dateModified\":\"2026-05-28T09:26:22+00:00\",\"description\":\"At Custom-Declarations.com, we believe that considering the end-to-end workflow is crucial to cross-border trading. We have created a business friendly tool that will consider both your needs and those of your customers when handling customs declarations.\",\"breadcrumb\":{\"@id\":\"https:\/\/www.customs-declarations.uk\/hmrc-safety-security-gb-entry-summary-declaration-ens-data-entry-field-requirement-guidelines\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/www.customs-declarations.uk\/hmrc-safety-security-gb-entry-summary-declaration-ens-data-entry-field-requirement-guidelines\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/www.customs-declarations.uk\/hmrc-safety-security-gb-entry-summary-declaration-ens-data-entry-field-requirement-guidelines\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/www.customs-declarations.uk\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"HMRC Safety &#038; Security \/ GB Entry Summary Declaration (ENS) Data Entry &#038; Fields Requirement Guidelines\"}]},{\"@type\":\"Article\",\"@id\":\"https:\/\/www.customs-declarations.uk\/hmrc-safety-security-gb-entry-summary-declaration-ens-data-entry-field-requirement-guidelines\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/www.customs-declarations.uk\/hmrc-safety-security-gb-entry-summary-declaration-ens-data-entry-field-requirement-guidelines\/#webpage\"},\"author\":{\"@id\":\"https:\/\/www.customs-declarations.uk\/#\/schema\/person\/636c91b0662504227de082be9e8178fe\"},\"headline\":\"HMRC Safety &#038; Security \/ GB Entry Summary Declaration (ENS) Data Entry &#038; Fields Requirement Guidelines\",\"datePublished\":\"2025-08-06T18:25:11+00:00\",\"dateModified\":\"2026-05-28T09:26:22+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/www.customs-declarations.uk\/hmrc-safety-security-gb-entry-summary-declaration-ens-data-entry-field-requirement-guidelines\/#webpage\"},\"wordCount\":16747,\"commentCount\":0,\"publisher\":{\"@id\":\"https:\/\/www.customs-declarations.uk\/#organization\"},\"image\":{\"@id\":\"https:\/\/www.customs-declarations.uk\/hmrc-safety-security-gb-entry-summary-declaration-ens-data-entry-field-requirement-guidelines\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/www.customs-declarations.uk\/wp-content\/uploads\/2025\/07\/CD-Thumbnail-14.jpg\",\"articleSection\":[\"Article\",\"Guide\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\/\/www.customs-declarations.uk\/hmrc-safety-security-gb-entry-summary-declaration-ens-data-entry-field-requirement-guidelines\/#respond\"]}]},{\"@type\":\"Person\",\"@id\":\"https:\/\/www.customs-declarations.uk\/#\/schema\/person\/636c91b0662504227de082be9e8178fe\",\"name\":\"admin\",\"image\":{\"@type\":\"ImageObject\",\"@id\":\"https:\/\/www.customs-declarations.uk\/#personlogo\",\"inLanguage\":\"en-US\",\"url\":\"https:\/\/secure.gravatar.com\/avatar\/0d0f6c919b646743e92d159adf25ee7b?s=96&d=mm&r=g\",\"contentUrl\":\"https:\/\/secure.gravatar.com\/avatar\/0d0f6c919b646743e92d159adf25ee7b?s=96&d=mm&r=g\",\"caption\":\"admin\"},\"sameAs\":[\"http:\/\/localhost\/customs-declaration\"]}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","_links":{"self":[{"href":"https:\/\/www.customs-declarations.uk\/wp-json\/wp\/v2\/posts\/2715"}],"collection":[{"href":"https:\/\/www.customs-declarations.uk\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.customs-declarations.uk\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.customs-declarations.uk\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.customs-declarations.uk\/wp-json\/wp\/v2\/comments?post=2715"}],"version-history":[{"count":23,"href":"https:\/\/www.customs-declarations.uk\/wp-json\/wp\/v2\/posts\/2715\/revisions"}],"predecessor-version":[{"id":2780,"href":"https:\/\/www.customs-declarations.uk\/wp-json\/wp\/v2\/posts\/2715\/revisions\/2780"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.customs-declarations.uk\/wp-json\/wp\/v2\/media\/2734"}],"wp:attachment":[{"href":"https:\/\/www.customs-declarations.uk\/wp-json\/wp\/v2\/media?parent=2715"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.customs-declarations.uk\/wp-json\/wp\/v2\/categories?post=2715"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.customs-declarations.uk\/wp-json\/wp\/v2\/tags?post=2715"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}