XML FILE CREATION FOR CUSTOMS FILE (SOC) – USER MANUAL
Version: V1.0.38.2
Prepared by: Arul Jothi. M
Date: 22/12/2025
Table of Contents
Introduction
System
Requirements
Logging
In
SOC
Manifest XML Creation
4.1 Introduction
4.2 Message Type
4.3 BL Number Entry
4.4 Generating a New SOC XML File
4.5 Values Fetching Criteria – Shipment, Vessel & Container
4.6 Trader Information Capturing
4.7 EDI Mapping Requirements
4.8 Data Required for Package, Weights & Volumes
4.9 Shipping Marks & Cargo Description
Troubleshooting
Common Issues
Frequently
Asked Questions (FAQs)
Support
1. Introduction
The SOC (Shipper-Owned Container) Customs File Creation
module is used to generate the SOC Manifest XML in the ASYCUDA-compliant
format required by Sri Lanka Customs. This file includes essential shipment
elements such as:
The system auto-extracts all required fields and converts
them into the ASYCUDA XML structure. This automation ensures:
Zero
manual XML typing
Reduced
data-entry errors
Faster
submission to Customs
Full
compliance with regulatory norms for NVOCC operators
2. System Requirements
Supported Browsers:
Google
Chrome 90+
Mozilla
Firefox 85+
3. Logging In
Open
ZEALIT 2.0 in your browser.
Log
in using your assigned credentials.
Navigate
to Customs File Creation → SOC Manifest via Dashboard or Search.
4. SOC Manifest XML Creation
4.1 Introduction
The SOC Manifest module prepares the export/import manifest
in ASYCUDA XML for NVOCC operations.
This module captures all BL, container, cargo & voyage data from the SOC
booking workflow.
4.2 Message Type
To generate the SOC XML, enter:
Message Type:
CMB-SOC-Manifest
This identifies the file as a SOC-based manifest for Sri
Lanka Customs.
4.3 BL Number Entry
Enter the correct BL Number in the BL Number input
field.
4.4 Generating a New SOC XML File
Click
Create New in the Customs File Creation screen.
The
system generates an XML record for the selected BL.
Errors
will highlight missing mandatory fields (fix & regenerate).
4.5 Values Fetching Criteria – Shipment, Vessel &
Container
Below is how the XML tags get populated:
A. Total Packages & Gross Mass
Captured from the Container Details screen:
Total_number_of_packages
Total_gross_mass
👉 Both are mandatory
to generate SOC XML.
B. Vessel Master Information
Fetched from Vessel Master → Nationality Column:
Fetched from Voyage Master → Notes Column:
Make sure voyage notes are updated — otherwise XML will show
missing fields.
4.6 Trader Information Capturing
Captured directly from SI Instruction Page → Booking
Screen:
Exporter
name & address
Consignee
name & address
Notify
party details
You do not need to modify master data — SI page edits
are enough.
4.7 EDI Mapping Requirements
A. Container Type Mapping
Use EDI Mapping → CMB_IGM → CON_ISO
Example:
|
System Type
|
XML ISO Code
|
|
45GP
|
45G1
|
B. Package Type Mapping
Package codes come from Container Details → Package Code.
Map them here:
EDI Mapping → CMB_IGM → CARGO_PACKAGE
Example:
|
Package Code
|
Description
|
|
CT
|
CARTONS
|
4.8 Package, Gross Mass & Volume
Captured from Container Details:
Number
of packages
Gross
mass
Volume
in CBM
Ensure mandatory fields are filled to avoid XML failures.
4.9 Shipping Marks & Cargo Description
Fetched from Booking Screen:
Whatever text is entered there directly appears in the XML
file.
5. Troubleshooting Common Issues
|
Issue
|
Suggested Fix
|
|
Create New button not showing
|
Check user permissions
|
|
BL details not loading
|
Verify BL is created & mandatory fields filled
|
|
XML not generating
|
Check SI, container details, and vessel data
|
|
Missing voyage-related XML tags
|
Ensure Voyage Notes are entered
|
|
Package or ISO mismatch
|
Update EDI Mapping table
|
6. Frequently Asked Questions (FAQs)
Q1: Can I edit SI details after generating XML?
Yes — but regenerate the XML after updating details.
Q2: Are House B/Ls compulsory for SOC?
No — only required if shipment structure includes HBLs.
Q3: Why is my SLPA Ref not appearing?
Because Voyage Notes are empty — update them.
Q4: Can I generate multiple XML files for the same BL?
Yes — if the booking remains in editable stage.
7. Support
For help, contact: