TRADACOMS ›
Exception Condition › EXCHDR
EXCHDR: Exception Condition File Header
The EXCHDR message is part of the TRADACOMS Exception Condition file: exception condition reports.
The Exception Condition file contains: EXCHDR → EXCINF → EXCTLR.
Message structure
| Segment | Name | Usage |
|---|---|---|
MHD | Message Header | One message only, at the start of the file |
TYP | Transaction Type Details | |
CDT | Customer Details | |
BDT | Bank Details | |
FIL | File Details | |
MTR | Message Trailer |
Segments and data elements
| Element | Name | M/C | F/V | Format | Notes |
|---|---|---|---|---|---|
MSRF | Message Reference | M | V | 9(12) | Consecutive count of messages within the transmission |
TYPE | Type of Message composite | M | 'EXCHDR' '3' for this version | ||
| Type | M | F | X(6) | ||
| Version Number | M | F | 9(1) |
| Element | Name | M/C | F/V | Format | Notes |
|---|---|---|---|---|---|
TCDE | Transaction Code | M | F | 9(4) | Code Values List 2; '0850' · code list 2 |
TTYP | Transaction Type | C | V | X(12) | Code Values List 3 · code list 3 |
| Element | Name | M/C | F/V | Format | Notes |
|---|---|---|---|---|---|
CIDN | Customer's Identity composite | M | EAN location number identifying customer Customer code as allocated/used by the supplier | ||
| Customer's EAN Location Number | C | F | 9(13) | ||
| Customer's Identity Allocated by Supplier | C | V | X(17) | ||
CNAM | Customer's Name | C | V | X(40) | Customer's Legal Name |
CADD | Customer's Address composite | C | A maximum of five lines to give the customer's address | ||
| Customer's Address Line 1 | C | V | X(35) | ||
| Customer's Address Line 2 | C | V | X(35) | ||
| Customer's Address Line 3 | C | V | X(35) | ||
| Customer's Address Line 4 | C | V | X(35) | ||
| Customer's Post Code | C | V | X(8) | ||
VATR | Customer's VAT Registration Number composite | C | Trader's VAT number allocated by HM Customs & Excise Government department or non-UK VAT number | ||
| Numeric VAT Registration Number | C | F | 9(9) | ||
| Alphanumeric VAT Registration Number | C | V | X(17) |
| Element | Name | M/C | F/V | Format | Notes |
|---|---|---|---|---|---|
BKIC | Bank Identity Code | M | F | X(2) | Service Bank's own identity code |
BNAM | Bank Name | C | V | X(35) | Service Bank/3rd Party Bank Name |
SVID | Service Identity composite | M | Name of service as allocated by Service Bank Customer's user number as allocated by Bank | ||
| Service Code | M | V | X(6) | ||
| User Code | M | V | X(8) | ||
BKIN | Bank Information | C | V | X(17) | Customer to Bank information, eg F/X Deal Number |
CUIN | Currency Indicator | C | V | X(3) | Currency Code (List 31) |
| Element | Name | M/C | F/V | Format | Notes |
|---|---|---|---|---|---|
FLGN | File Generation Number | M | V | 9(4) | This number is sequential per file type, per trading partner |
FLVN | File Version Number | M | V | 9(4) | Original (which is always 1) is incremented by 1 for each additional copy created |
FLDT | File Creation Date | M | F | 9(6) | Date the file is created. Format: YYMMDD |
FLID | File (Reel) Identification | C | V | X(6) | Reference on the outside of reel containing the file |
| Element | Name | M/C | F/V | Format | Notes |
|---|---|---|---|---|---|
NOSG | Number of Segments in Message | M | V | 9(10) | Control count of segments including MHD and MTR |
Need to exchange TRADACOMS messages with a UK retailer?
SupplyLens connects your ERP, e-commerce or accounting system to any TRADACOMS or EDIFACT trading partner: orders in, invoices out, fully managed.
Book a demo Learn about retail EDI →