Yes, DSV handles electronic invoices through EDIFACT, XML and other formats as well. Our standard message types are: D10B, Inbound and Outbound. DSV Standard XML Outbound

Yes, DSV uses an EDIFACT standard for most EDI setups. Additionally, we use XML, flat file and CSV formats.

The DSV EDI messaging capability is covers receipt, processing, and transmission of EDI messages related to arrival, routing, dispatch, delivery and invoicing for transport and stock keeping units, bill of material, pre-advice, outbound order, receipt confirmation, order confirmation, order status, inventory movement, inventory report, inventory confirmation for warehouse operations.

Electronic communication with customs is possible, but dependent on local law and solutions available in the different markets.

Yes, DSV have two sets of standard messages. For transport modes (both Road and Air & Sea) we have 5 EDI standard message types based on EDIFACT standard. For logistics and supply chain operations we have 22 documented and tested DSV XML messages. The standard communication type is SFTP (FTP is available but not recommended for security reasons).

DSV works according to ITIL (Information Technology Infrastructure Library) structured working and planning procedures. Customer involvement in the process of scoping, testing, and sign off is necessary to ensure the requested functionality, quality output, and delivery timelines.

FTP (File Transfer Protocol) is a standard method for transferring files over the Internet. A password protected FTP site is provided for each trading partner to pickup and drop-off files using an automated process or by manually copying to and from the FTP site. SFTP (Secure File Transfer Protocol) is a protocol which creates an encrypted ‘tunnel’ between a client and host, across which data can be securely exchanged. To protect the integrity of data, DSV strongly recommends using SFTP over FTP. Requesting FTP integration will be more cumbersome, as a risk-assessment process will be mandatory prior to the integration.

HTTP (Hyper Text Transfer Protocol) is the protocol that web browsers and web servers use to communicate with each other over the Internet. HTTPS (Hyper Text Transfer Protocol Secure) is a combination of the Hypertext Transfer Protocol with the SSL/TLS protocol to provide encryption and secure identification of the server. To protect the integrity of data, DSV strongly recommends using HTTPS over HTTP.

AS2 (Applicability Statement 2) is an extremely well-defined standard data transport protocol. AS2 is a specification about how to transport data securely and reliably using HTTP over the Internet. If you need to carry out EDI transactions, AS2 is an excellent choice.

DSV strongly recommends using secure protocols like AS2, SFTP, HTTPS. AS2 is becoming more prevalent due to high level of security.

Some connection types work in host/client architecture, which means that host manages access (authorizes access, manage rights), shares files and the client use services offered by host. An example of this is SFTP where the company that hosts the SFTP service can: Manage users, set access, manage disk space/folders structure, generate and manage authorized keys. The client role is simpler as it only utilizes available services managed by the host. DSV can act as host or client, both options are supported.

Yes, DSV can build EDI integrations to all DSV applications able to receive and handle EDI information, when needed.

No, currently DSV only have EDI standard messages to: Our largest consignment handling systems, CargoLink and CargoWise, as well as our largest warehouse management system RedPrairie. We are in the process of extending the portfolio of standard messages.

When sending a tracking request shortly after the booking the SSCC numbers are not showing. While timing will depend on the specific booking, shortly after being created the SSCC numbers should become visible in the API Tracking response. If the number isn’t visible after 30 minutes, please reach out to support.

The packages / references / SHIPPER_REFERENCE and CONSIGNEE_REFERENCE types are visible on the label.



Please note that the value inserted to this field will be truncated if too long for the label. You can also add your own SSCC in packages / trackingNumbers. The number of SSCCs must match the quantity provided for the package.
If trackingNumbers are not sent in the booking DSV will create an SSCC for the package instead.
Value in packages / shippingMarks will show up in 'Marks'. (Package level Marks and Numbers)

The EDI support team is the part of Global IT team and provides 24/7/365 EDI support services.

The DSV EDI team ensures detailed planning of all integration tasks to secure on time delivery. Resources and competences are utilized to support all business requests according to well documented procedures and monitored Quality Gates.

We provide 24/7/365 support to monitor processing data and troubleshoot any issues that might occur.

Our EDI platform is a business-critical tool, and we ensure that all data is processed in a secure and reliable way. There are secure proxy gateways placed in the EDI platform to provide multiple layers security to maximize protection of the enterprise data assets and meet audit requirements. Our applications run on clustered servers to prevent them from single point of failure.

We follow a standardized EDI development process where we analyze requirements, build the integrations, carry out tests and deploy solutions to a live system. We ensure that all development is done in line with the development process, which guarantees that the change is done in a controlled, well documented way with minimal risk. We also complete unit tests, component tests, UAT tests, and quality assurance to ensure high quality integrations.

Good communication and availability are crucial for effective EDI implementation.

Yes, we have a test environment. All changes are required to be validated and approved in the test environment prior to deployment to a live system.

If your system is compatible with DSV EDI standard messages and communication setup, the expected delivery time is 20 working days per standard message.