DHL (formerly Exel) (US and CAN) EDI 990 Load Tender Response

Schema Reference

6 segments · X12 990 Response to a Load Tender

ISA01 Authorization Information Qualifier

M ID 2-2

ISA02 Authorization Information

M AN 10-10

ISA03 Security Information Qualifier

M ID 2-2

ISA04 Security Information

M AN 10-10

ISA05 Interchange ID Qualifier

M ID 2-2

ISA06 Interchange Sender ID

M AN 15-15

ISA07 Interchange ID Qualifier

M ID 2-2

ISA08 Interchange Receiver ID

M AN 15-15

ISA09 Interchange Date

M DT 6-6

ISA10 Interchange Time

M TM 4-4

ISA11 Interchange Control Standards Identifier

M ID 1-1

ISA12 Interchange Control Version Number

M ID 5-5

ISA13 Interchange Control Number

M N0 9-9

ISA14 Acknowledgment Requested

M ID 1-1

ISA15 Usage Indicator

M ID 1-1

GS01 Functional Identifier Code

M ID 2-2

GS02 Application Sender's Code

M AN 2-15

GS03 Application Receiver's Code

M AN 2-15

GS04 Date

M DT 8-8

GS05 Time

M TM 4-8

GS06 Group Control Number

M N0 1-9

GS07 Responsible Agency Code

M ID 1-2

GS08 Version / Release / Industry Identifier Code

M AN 1-12

ST01 Transaction Set Identifier Code

M ID 3-3

ST02 Transaction Set Control Number

M AN 4-9

B101 Standard Carrier Alpha Code

O ID 2-4

B102 Shipment Identification Number

M AN 1-30

B103 Date

O DT 8-8

B104 Reservation Action Code

O ID 1-1

N901 Reference Identification Qualifier

M ID 2-3

N902 Reference Identification

C AN 1-30

SE01 Number of Included Segments

M N0 1-10

SE02 Transaction Set Control Number

M AN 4-9

Automating DHL (formerly Exel) (US and CAN) EDI 990

Stacksync validates, transforms, and delivers your 990 transactions automatically — so your team can focus on operations, not EDI compliance.

Validate

Transform

Route

Monitor

Stacksync sends 990 Load Tender Responses from your TMS automatically when your dispatch team accepts or rejects a DHL (formerly Exel) (US and CAN) load — ensuring fast response times and carrier compliance.

DHL (formerly Exel) (US and CAN) EDI 990 FAQ

Common questions about 990 Response to a Load Tender transactions with DHL (formerly Exel) (US and CAN).

How long does it take to set up DHL (formerly Exel) (US and CAN) EDI with Stacksync?

Most suppliers are fully connected and processing live DHL (formerly Exel) (US and CAN) EDI transactions within 3–5 business days. Stacksync's no-code setup means you don't need developers or EDI consultants — configure your field mappings through our visual interface, run a test cycle, and go live.

Do I need an existing VAN or AS2 connection to trade with DHL (formerly Exel) (US and CAN)?

No. Stacksync handles the entire EDI transport layer. We connect directly to DHL (formerly Exel) (US and CAN)'s trading partner network through our certified connections. You don't need to manage a separate VAN subscription, AS2 certificates, or SFTP configurations.

How does Stacksync help with DHL (formerly Exel) (US and CAN) compliance?

Stacksync improves compliance scores by eliminating manual processing delays. Purchase Orders sync to your system in real time, ASNs are generated automatically when you ship, and invoices are validated with three-way matching before submission. Real-time monitoring alerts you to issues before they become chargebacks.

What EDI document types does Stacksync support for DHL (formerly Exel) (US and CAN)?

Stacksync supports all EDI document types required by DHL (formerly Exel) (US and CAN) — including Purchase Orders (850), Invoices (810), ASNs (856), PO Acknowledgments (855), and more. Our platform handles the full lifecycle from order to payment automatically.

Can I connect DHL (formerly Exel) (US and CAN) EDI to my existing ERP or WMS?

Yes. Stacksync integrates with any system that has a database or API — including SAP, Oracle, NetSuite, Microsoft Dynamics, and custom-built ERPs. Data flows bidirectionally between DHL (formerly Exel) (US and CAN)'s EDI network and your system in real time.

What happens when DHL (formerly Exel) (US and CAN) updates their EDI specifications?

Stacksync monitors DHL (formerly Exel) (US and CAN)'s EDI spec changes and updates our mappings proactively. When a change affects your integration, we notify you and apply updates — so you stay compliant without scrambling to decode new implementation guides.