From Paper to XML: Transitioning Your SAD to the New EU H1 Standard

The Single Administrative Document (SAD) is the customs declaration form used for international trade; the EU H1 standard replaces paper SADs with a structured XML format to streamline declarations, improve data accuracy, and meet EU customs requirements.

The Single Administrative Document (SAD) is the standard customs declaration used across the EU for imports, exports and transit movements. Historically a paper form filled out by traders or brokers, the SAD records key data such as consignor/consignee details, commodity codes, values, origin, transport mode, and movement references. The new EU H1 standard modernizes the SAD by defining a structured XML message format that electronic systems use to transmit the same information to customs authorities.

Transitioning from paper to the H1 XML format is more than a format change; it is an opportunity to streamline processes, reduce errors, and integrate customs data with your warehouse and transport systems. Below is a practical, beginner-friendly guide to understanding the H1 standard and planning a smooth conversion from paper SADs to compliant XML declarations.

Why the EU H1 XML standard?

Moving to XML supports automation, validation, and faster processing. Customs authorities can automatically verify fields, check tariff classifications, and trigger risk assessments before goods arrive. For traders and logistics providers, H1 enables electronic submission through national customs IT systems or via a customs broker, reduces transcription errors, and shortens release times.

Key elements carried in the H1 SAD XML

Although implementations vary by member state, the H1 XML carries the same essential SAD data:

• Trader identifiers (EORI numbers), names and addresses
• Consignment details: transport mode, container identifiers, and shipment references
• Commodity information: tariff (CN) codes, descriptions, quantities, units and origin
• Commercial values, currency and incoterms
• Customs procedure codes, movement types, and supervisory measures
• Supporting references: invoices, licences, certificates and permits

Preparing to transition: a practical checklist

1. Inventory your current paper SADs and data sources. Identify where every field is captured today (ERP, WMS, spreadsheets, broker forms).

2. Map existing fields to the H1 XML schema. For each paper field, find the corresponding XML element and required format (dates, numeric formats, code lists).

3. Clean and standardize your data. Ensure you have valid EORI numbers, correct CN codes, standardized address formats, and consistent units of measure.

4. Choose how you will generate XML. Options include in-house development, your ERP/WMS/TMS vendor, a customs broker’s submission service, or a middleware provider that transforms your data to H1 XML.

5. Confirm communications and security requirements. Most customs systems require secure connections and authentication, often certificate-based. Plan for user permissions and audit trails.

6. Test with customs. Use test environments (sandbox) offered by national customs authorities to validate message structure, mandatory fields and business rules.

7. Train staff and update procedures. Ensure your supply chain partners, brokers and carriers understand the new electronic workflow.

Data mapping and validation tips

One of the most common challenges is data format mismatch. XML schemas enforce strict formats for dates, decimals and codes. Create validation rules early in the process so you catch issues before submission. Consider these practical tips:

• Use code lists where possible (e.g., country codes, units, customs procedure codes) rather than free text.
• Standardize commodity descriptions and always store the corresponding CN code.
• Format numeric values with the required decimal separator and number of decimals.
• Verify currency codes (ISO 4217) and unit codes (UN/CEFACT or local standards).
• Automate validation with schema checks and business-rule checks (e.g., verifies that the declared origin is allowed for the tariff).

Integration with business systems

To get the full benefit of H1 XML, integrate customs messaging into your ERP, WMS and order management systems. This reduces duplicate data entry and accelerates release times. Typical integrations include:

• ERP → XML generator: use order and invoice data to populate the SAD XML automatically.
• WMS → shipment data: capture weights, package counts and container IDs from the warehouse system.
• TMS → transport references: bring carriage and route information into the declaration.

Testing and go-live strategy

Adopt a phased approach to reduce risk:

1. Develop and validate a sample XML file with your provider or IT team.
2. Run technical tests in customs’ sandbox environment to confirm schema conformity and connectivity.
3. Perform end-to-end tests: simulate a real shipment, including generation, submission, customs response and downstream actions (release orders, movement references).
4. Start live operations with low-risk shipments (e.g., known commodity codes, trusted partners), then scale up as confidence grows.

Common mistakes to avoid

1. Assuming all paper fields map one-for-one — some paper data must be split or combined to meet XML requirements.

2. Ignoring validation rules — failing schema or business-rule validation causes rejections and delays.

3. Neglecting identifiers — missing or invalid EORI numbers and licence references are frequent rejection causes.

4. Poor data governance — inconsistent commodity codes, addresses or unit measures create errors and audits.

5. Ramping up too fast — not testing thoroughly before full live operation can disrupt inbound supply chains.

Benefits you can expect

By moving to H1 XML you should see:

• Faster customs processing and fewer manual corrections
• Improved data accuracy and auditability
• Better supply chain visibility thanks to electronic references like MRNs
• Lower administrative costs and fewer delays at borders
• Improved compliance via automated rule checks

Who needs to be involved

Successful transition requires coordination across several stakeholders:

• Internal: customs/compliance teams, IT, warehouse and transport operations, sales and procurement.
• External: customs brokers, customs authorities, software vendors, carriers and trade partners.

Example: a small importer’s transition in brief

Step 1: Gather sample paper SADs and identify recurring fields.

Step 2: Work with your ERP vendor or broker to map fields to H1 XML elements and create transformation scripts.

Step 3: Clean your master data (EORI, CN codes, units) and run sample XML files through the customs sandbox.

Step 4: Fix validation errors, document new processes, train staff and start live submissions for a few shipments.

Step 5: Review performance, refine mappings and expand to all inbound shipments.

Final advice



Treat the transition to H1 XML as a business process improvement, not just a technical project. Invest time in data quality, testing and stakeholder training. Use the move to eliminate duplicated manual steps, integrate customs with warehouse and transport systems, and build repeatable, auditable procedures. That approach will reduce risk, shorten clearance times, and make customs declarations a seamless part of your supply chain operations.