TRADACOMS ›
Statement / Remittance › SRMINF
SRMINF: Statement/Remittance Line Details
The SRMINF message is part of the TRADACOMS Statement / Remittance file: statements of account and remittance advice.
The Statement / Remittance file contains: SRMHDR → SRMINF → SRMTLR.
Message structure
| Segment | Name | Usage |
|---|---|---|
MHD | Message Header | |
SRD | Statement/Remittance Line Details | Repeat for each line in the message |
DNB | Data Narrative | Repeat if necessary at line level |
SRT | Statement/Remittance Message Totals PYC = Payment Details MTR = Message Trailer | One message for each separate statement (if used in a statements file) or remittance (if used in a remittance file) |
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 | 'SRMINF' '9' for this version | ||
| Type | M | F | X(6) | ||
| Version Number | M | F | 9(1) |
| Element | Name | M/C | F/V | Format | Notes |
|---|---|---|---|---|---|
SEQA | First Level Sequence Number | M | V | 9(10) | Starts at 1 and is incremented by 1 for each segment of this type in the message |
CLOC | Customer's Location composite | M | One of the following 3 customer's references must be present. If the line detail is not location-specific, use the first sub-element, zero-filled EAN location number identifying the customer's location Customer's own identity for the location to which the goods ordered are to be/have been delivered Supplier's reference for the customer's location | ||
| Customer's EAN Location Number | C | F | 9(13) | ||
| Customer's Own Location Code | C | V | X(17) | ||
| Supplier's identification of Customer's Location | C | V | X(17) | ||
LINE | Statement/Remittance Line Code | C | F | X(2) | Identifies nature of the entry for the line of the statement/remittance advice Code Values List 15 · code list 15 |
LIDR | Line Document Reference composite | M | If the line details are not document specific, one of the sub-elements should be used and zero-filled The number of the original document to which the line relates, else a number allocated by the message sender Format: YYMMDD | ||
| Line Document Number | C | V | X(17) | ||
| Line Document Date | C | F | 9(6) | ||
LIDA | Line Document Amount Payable | M | V | 9(10)V9(2) | In Pounds. LIDA = LIDT - LIDD + LIDV |
LIDT | Line Document Total (excluding VAT and Discount) | C | V | 9(10)V9(2) | In Pounds. Before settlement discount + VAT have been applied |
LIDV | Line Document VAT | C | V | 9(10)V9(2) | In Pounds |
LIDD | Line Document Discount Taken | C | V | 9(10)V9(2) | In Pounds |
| Element | Name | M/C | F/V | Format | Notes |
|---|---|---|---|---|---|
SEQA | First Level Sequence Number | M | V | 9(10) | Takes the value of SEQA in the preceding SRD segment with which this segment is nested |
SEQB | Second Level Sequence Number | M | V | 9(10) | Starts at 1 and is incremented by 1 for each 2nd level repeat |
DNAC | Data Narrative Code Code Table Number Code Value | C | V | 9(4) | Standard data narrative previously defined and agreed by sender and receiver Number of relevant code list Code Value from code list · code list 22 |
RTEX | Registered Text composite | C | Essential text, where not provided for by specific fields may be communicated using this element. Application codes to define function of the text must be registered with the ANA prior to use. The same application code may be repeated up to four times, or up to four different codes may be used · code list 24 | ||
| First Registered Application Code | C | V | X(3) | ||
| Application Text | C | V | X(40) | ||
| Second Registered Application Code | C | V | X(3) | ||
| Application Text | C | V | X(40) | ||
| Third Registered Application Code | C | V | X(3) | ||
| Application Text | C | V | X(40) | ||
| Fourth Registered Application Code | C | V | X(3) | ||
| Application Text | C | V | X(40) | ||
GNAR | General Narrative composite | C | Narrative covering information which cannot be sent in a coded form ie RTEX/DNAC. This is likely to preclude automatic processing | ||
| General Narrative Line 1 | C | V | X(40) | ||
| General Narrative Line 2 | C | V | X(40) | ||
| General Narrative Line 3 | C | V | X(40) | ||
| General Narrative Line 4 | C | V | X(40) |
| Element | Name | M/C | F/V | Format | Notes |
|---|---|---|---|---|---|
SRLC | Statement/Remittance Line Count | M | V | 9(10) | Number of SRD segments in this message |
SRAP | Statement/Remittance Amount Payable | M | V | 9(10)V9(2) | Net sum of LIDA elements in this message |
SRDT | Statement/Remittance Document Totals | C | V | 9(10)V9(2) | Net sum of LIDT elements in this message. The result can be negative |
SRVT | Statement/Remittance VAT Totals | C | V | 9(10)V9(2) | Net sum of LIDV elements in this message. The result can be negative |
SDCD | Statement/Remittance Discount Totals | C | V | 9(10)V9(2) | Net sum of LIDD elements in this message. The result can be negative |
SETC | Settlement Discount Totals | C | V | 9(10)V9(2) | For settlement discounts calculated on totals from the line documents in this message, rather than on the line documents individually. In Pounds |
| Element | Name | M/C | F/V | Format | Notes |
|---|---|---|---|---|---|
PRRF | Primary Reference composite | M | A = Accompanying Remittance Advice; I = Invoice; R = Remittance Advice; S = Statement To flag if related message involved Unique message reference linking related messages | ||
| Related message indicator | M | F | X(1) | ||
| Primary Reference | M | V | X(17) | ||
DATE | Date relating to message | M | F | 9(6) | Service Processing Date as agreed with Service Bank |
SNIC | Supplier's Network I/d code | M | V | X(14) | Used by Bank to send message to supplier eg EAN location number |
PAYM | Payment Method | C | V | X(6) | Express (or override) preference as defined by Bank |
| Element | Name | M/C | F/V | Format | Notes |
|---|---|---|---|---|---|
NOSG | Number of Segments in Message | M | V | 9(10) | Control count of the number of segments comprising message. The count includes the MHD and MTR segments surrounding the message |
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 →