Remadv

REMADV
Remittance Advice Message

Subject for application in the European Steel Industry
Version December 1999

Corporate FactoryPh. D. Sarraute
EDIFER WORKING GROUP - Message development

UN/EDIFACT D97.A REMADV - Remittance Advice message
REMITTANCE ADVICE MESSAGE (Table of Contents)
0. INTRODUCTION 2
1. BACKGROUND INFORMATION 3
1.1 General information 3
2. DATA MODEL 4
2.1 Data Model Format 4
2.2 Data Model Diagram 5
2.3 Data Model Entities 7
2.4 Data Model Relationships 8
2.5 Data Model Attributes 9
3. SCOPE 12
3.1 Functional Definition 12
3.2 Field of Application 12
3.3 Principles 12
3.4 Message Usage 12
4. MESSAGE DEFINITION 13
4.1 Message Structure 13
4.2 Mapping of the Data Model to the Message 14
4.3 Branching Diagram of the Segments used by Eurofer 19
4.4 General Description of the Message - Subset of Eurofer 23
4.5 Detailed Description of the Message - Subset of Eurofer 27
1
REMITTANCE ADVICE MESSAGE
0. INTRODUCTION
This document provides the definition of the EUROFER subset of the REMITTANCE
ADVICE message based on the UN standard REMADV message of the UN/EDIFACT
directory D97A.
This message has been created by the EDIFER "Message development" working group. The
message is to be used in Electronic Data Interchange (EDI) between partners involved in the
steel industry.
The manual has been structured in the following format:
- A Data Model definition describes the data entities, attributes and their relationships.
- The scope describes the field of application, principles and message usage.
- The message definition covers the structure, the entity/attribute mapping and how the
data described in the data model relates to the message.
- The message definition outlines the general structure of the message and specifies the
use of each segment group and, or segment.
- Based on the branching diagram of the original EDIFACT message REMADV, the
segments used are indicated. This is followed by a detailed description of the segments
used by Eurofer.
2
1. BACKGROUND INFORMATION
1.1 General information

The Remittance advice message is sent by the payer (customer) to the payee (supplier),
providing accounting details relative to a payment for the provision of goods/services as
detailed in the message. This message is based on universal practice and is not dependent
on the type of business or industry.
The following principles are valid for the Remittance advice message;
- A Remittance advice is a notice of a payment to be made.
- A Remittance advice may cover one or more commercial trade transactions, such as
invoices, credit notes, debit notes, etc
- A Remittance advice may include a cross reference to a payment order given to the
bank.
- Each Remittance advice shall be calculated in only one currency, even though the
related transaction is denominated in different currencies.
- Each Remittance advice shall relate to only one settlement date.
The Eurofer subset of the Remittance advice message has been developed under the
following assumptions;
- a payer (customer) informs the payee (supplier) about the payment details
- the payment may cover more than one financial transaction, such as invoices, debit
notes, credit note, etc
A Remittance advice refers to:

- one payer (customer),
- one payee (supplier),
- one payers (customers) financial institution,
- one payees (suppliers) financial institution,
- one payment currency,
- one payment means,
- one payment date,
- several accounting documents,
- one or more adjustment reason.
3
2. DATA MODEL
2.1 Data Model Format

The data model of the Remittance advice message has been created, to make it possible for
potential users to understand the Eurofer subset of the Remittance advice message. This
data model gives the following information :
- contents of the information (data elements) that can occur in the message,
- relationships between the different data elements,
- grouping of the data elements within the data entities,
- and the relationship between data entities.
To simplify the understanding of the data model, the model is defined at a summary level,
specifying when necessary a group of data elements instead of each data element.
The data model consists of data entities, the relationships between those data entities and the
attributes (data elements) in each data entity.
An entity specifies an object against which information is held; it has a name, a description
and attributes.
An attribute describes a unique characteristic (information which can appear on the

remittance advice); it has a name, a description and a value.
The relationships of the data entities within the data model are reflected in the structure of
the diagram in chapter 2.2.
4
2.2 Data Model Diagram
1
Remittance advice
Contains
1
Payment Relates to
1,N
Accounting
document
Has
0,N
Adjustment
Reference to Reference to
Company Message /
Document
5
In this diagram, the rectangles represent data entities and the ovals show us the relationship
between two data entities. How often a relationship can exist between two data entities is
given in both directions and is specified as 0, 1, N.
- 0 means that there is no relationship between the entities.
- 1 means that there is one and only one relationship between the entities.
- N means that there are many relationships between the entities.
- 0,1 means that there can be no or one relationship between the entities.
- 1,N means that there can be one or many relationships between the entities.
- 0,N means that there can be no or many (one or more) relationships between the
entities.
Example relationship between Remittance advice and Accounting document
1. In the direction from Remittance advice to Accounting document.

A Remittance advice can contain one or more Accounting document.
2. In the direction from Accounting document to Remittance advice.

An Accounting document can only be in one Remittance advice.
6
2.3. Data model entities

Because the data entities Company and Message/document are not really basic information
in this message, they have been put outside the data model and they are treated as related
data entities. This has been done to simplify and not to overload the data model, so that the
data model is easier to understand.
The entities are regrouped in two groups. The first group includes all the basic data entities
and the second the related data entities.
The following entities are contained within the data model.
The basic data entities
REMITTANCE ADVICE
PAYMENT
ACCOUNTING DOCUMENT
ADJUSTMENT
The related data entities
COMPANY
MESSAGE/DOCUMENT
REMITTANCE This entity contains the general information about a remittance

ADVICE advice such as document type, its reference number and date.
PAYMENT This entity specifies the details of the payment, such as the payment
channel, payment date, payment currency, the bank account numbers
and the payment amounts
ACCOUNTING This entity gives the details of the commercial trade transactions
DOCUMENT covered by the Remittance advice message. This entity specifies the
document number, document date, the amount due, amount remitted,
and payment references.
ADJUSTMENT This entity gives the justification of the difference between the
amount due and the amount remitted of a commercial trade
transaction.
COMPANY An organisation with whom we deal for whatever purpose.

This can be the payer (customer), payee (supplier), buyer, sales
agency, consignor , consignee, etc.
MESSAGE & This entity contains all the references to another message or
DOCUMENT document. For example invoice, credit note, order, despatch advice.
7
2.4. Data model relationships

REMITTANCE ADVICE - PAYMENT
(relation : relates to - 1/1)
- Direction from Remittance advice to Payment.

A Remittance advice contains one Payment information.
- Direction from Payment to Remittance advice.
A Payment information belongs to only one Remittance advice.
REMITTANCE ADVICE - ACCOUNTING DOCUMENT

(relation : relates to - 1/1,N)
- Direction from Remittance advice to Accounting document.

A Remittance advice relates to one or more Accounting document.
- Direction from Accounting document to Remittance advice.
An Accounting document can only be in one Remittance advice.
ACCOUNTING DOCUMENT - ADJUSTMENT

(relation : contains - 1/0,N)
- Direction from Accounting document to Adjustment.

An Accounting document can have no, one or more Adjustments.
- Direction from Adjustment to Accounting document.
An Adjustment belongs to only one Accounting document.
8
2.5. Data model attributes

For each entity specified under point 2.3. Data model entities, a list of attributes and a
description is given.
ENTITY : REMITTANCE ADVICE
remittance advice number

Unique number given to identify a remittance advice.
remittance advice date/time

Date/time of the issue of the remittance advice.
ENTITY : PAYMENT
payment means
Indication of the instrument of payment, which may include a guarantee, e.g. cash,
check, payment to bank account.
payment date
Date on which an amount due is made available to the creditor, in accordance with the
terms of payment.
payment currency
The monetary unit in which payment is made, or is to be made.
payment amount
Actual amount paid, or to be paid.
payment order number

Number given to the payment order sent to the financial institution by the customer.
payers (customers) financial institution

The financial institution used by the payer (customer) for a given financial settlement.
payers (customers) financial institution account number

The payers (customers) account number at the financial institution where this account
is held.
payees (suppliers) financial institution

The financial institution used by the payee (supplier) for a given financial settlement.
payees (suppliers) financial institution account number

The payees (suppliers) account number at the financial institution where this account
is held.
9
ENTITY : ACCOUNTING DOCUMENT
message / document type

Code identifying a referenced message or document, e.g. invoice, credit note, debit note.
message / document number

Identification number of a referenced message or document.
message / document date

The date/time of the referenced message or document.
invoice (credit-, debit note) currency

The monetary unit in which the accounting document is made.
invoice (credit-, debit note) amount (amount due)

Actual amount of the accounting document.
amount remitted
Amount remitted in the accounting document.
payers (customers) payment reference number

Number given by the payer (customer) for the identification of the payment of an
accounting document (invoice).
invoicing party payment reference number

Number given by the invoicing party for the identification of the payment of an
accounting document (invoice).
ENTITY : ADJUSTMENT
adjustment reason
Indication of the reason for adjustment.
adjustment description
Explanation of the motive for the adjustment.
adjustment amount
Amount of the adjustment.
adjustment reference
Indication of the reference justifying the adjustment.
10
THE RELATED DATA ENTITIES
ENTITY : COMPANY
company code, name and address

Code and if necessary the name and address, contact persons and communication
channels of the partners involved by the payee or payer.
Examples are : consignor, consignee, sales office.
ENTITY : MESSAGE / DOCUMENT
message / document type

Code identifying a referenced message or document (e.g. order, delivery schedule
message, delivery just in time message, invoice, credit- and debit note).
message / document number

Identification number of a referenced message or document.
message /document date

The date/time of the referenced message or document.
11
3. SCOPE
3.1. Functional Definition

The Remittance Advice is a communication between trading partners, e.g. payer, payee,
financial institutions, which provides detailed accounting relative to payment, or other form
of financial settlement, for the provision of goods and/or services as detailed in the advice.
3.2. Field of application

This message provides the definition of the Eurofer Remittance advice message to be used
in Electronic Data Interchange between trading partners.
3.3. Principles
This Eurofer Remittance advice message has been created as a subset of the UNSM
REMADV message of EDIFACT. The message is initiated when the payer (customer)
makes a payment to the payee, allowing the payee to reconcile the financial transactions and
to identify the outstanding amounts. A Remittance advice may cover one or more
commercial trade transactions (and related financial transactions), such as invoices, credit
notes, debit notes, etc.
A Remittance advice may include a cross reference to a Payment order.
Each Remittance advice shall be calculated in only one currency, even though the related
transaction is calculated in different currencies.
Each Remittance advice shall relate to only one settlement date.
3.4. Message usage

The message is used to provide accounting details related to payment for the provision of
goods/services.
12
4. MESSAGE DEFINITION
4.1 Message Structure

The REMADV message of UN/EDIFACT is structured in three sections, a Heading section,
Detail section and a Summary section.
4.1.1. Message structure - Heading section
The heading section is used to give the general information relating to the whole message.
Examples of this kind of information are remittance advice number, date of remittance
advice, parties involved, identification of the financial institutions and account numbers, and
when relevant the currencies and the rate of exchange.
The heading section can also be used to give information which has the same content for
each line in the detail section. Examples of this kind of information are references valid for
all detail items specified in the detail section.
4.1.2. Message structure - Detail section
The detail section can be used to identify the reference documents against which payment is
being made, to give the monetary amounts for the amount due and the amount to be
remitted.
This sections allows also to specify the currencies, rate of exchange and related date/period
valid for the referenced document, where different to the remittance, and if necessary to
indicate the adjustment reason(s), amounts(s), the referenced documents and the description
or the adjustment.
4.1.3. Message structure - Summary section
The summary section can be used to give the total amount of payment to be made or other
total amounts.
13
4.2. Mapping of the Data model to the message

For the understanding of the mapping process, done by the EDIFER working group, it is
necessary to have the knowledge about the structure of the official UNSM REMADV
message and the functionality of the segment groups and segments as defined by the
EDIFACT message development group MD1 - Trade.
To have the complete information about the official version we recommend the usage of the
official document published by UNITED NATIONS - EDIFACT directory D97.A.
In the following table a short overview is given about the meaning and the functionality of
the segment groups and segments in the message. The information given covers :
- the segment group
- the segment
- the description of the meaning and the functionality
- the comments of the EDIFER working group
SEGMENT SEGMENT FUNCTION COMMENTS

GROUP
HEADING SECTION
BGM To identify the Remittance advice message by its Mandatory.

number.
DTM To specify general date/time/period related to the Must be used at least once to identify
whole message. the date of the remittance advice.
RFF To specify the referenced documents valid for
the whole message.
FII To identify the financial institution and account
number and, where relevant , the currency of the
account.
PAI To specify the conditions, guarantee, method
and channel of payment.
FTX Free text information relevant for the whole Not recommended by Eurofer.
message.
GIS To identify various indicators required by the Not used.
processing system.
GROUP 1 To identify the parties (companies) relevant to

the whole message.
NAD Function, name and address of the company.
GROUP 2 To give contact details of the party.

CTA To identify to whom communication should be
directed.
COM To identify communication type and numbers.
GROUP 3 To specify the currencies and related

dates/periods valid for the whole Remittance
advice.
CUX To identify the currencies required in the
Remittance advice. A rate of exchange may be
given to convert a reference currency into the
target currency.
DTM To specify the date/time/period related to the
rate of exchange.
14

GROUP
DETAIL SECTION
GROUP 4 To provide details of all documents to which the

Remittance advice refers. It includes
information on the monetary amounts for each
document and on any adjustments and discounts.
DOC To identify the reference document against
which payment is being made.
MOA To give the monetary amounts for the amount
due and the amount to be remitted.
DTM To specify the date of the referenced document
and to indicate any other relevant date
applicable.
RFF To identify any additional references related to
the referenced document.
NAD To identify a party related to the referenced
document, e.g. issuer of the document.
GROUP 5 To specify the currencies and related

dates/periods valid for the referenced document,
where different from the remittance currency.
CUX To identify the currency and associated rate of
exchange of the referenced document.
DTM To specify the date/time/period related to the
rate of exchange.
GROUP 6 To indicate adjustment amounts and their

referenced documents.
AJT To indicate any adjustments to the amounts
originally specified in the referenced document.
MOA To give the monetary amounts of the
adjustments of each referenced document.
RFF To identify any additional references related to
the adjustment on the referenced document.
FTX Free text information relevant for the
adjustment.
GROUP 7 To indicate instructions to parties. Not used.

INP To indicate instructions to parties. Not used.
FTX To indicate instructions in free text. Not used.
GROUP 8 To provide details of individual line items in the Not used.

referenced document.
DLI To identify a specific line item within the Not used.
MOA To give monetary amounts for the amount due Not used.
and the amount to be remitted of the specific line
item.
PIA To specify item identification codes. Not used.
DTM To specify the date/time/period related to the Not used.
line item.
15

GROUP
GROUP 9 To specify the currencies and related Not used.

dates/periods of the line item where different to
the remittance and document currency.
CUX To identify the currency and associated rate of Not used.
exchange of the line item.
DTM To specify the date/time/period related to the Not used.
rate of exchange.
GROUP 10 To indicate adjustment amounts and their Not used.

referenced documents for the line item.
AJT To indicate any adjustments to the amounts Not used.
originally specified for the line item.
MOA To give the monetary amounts of the Not used.
adjustments of the line item.
RFF To identify any additional references related to Not used.
the adjustment of the line item.
FTX Free text information relevant for the Not used.
adjustment.
SUMMARY SECTION
MOA To give the total amount of the payment to be

made or other amounts.
16
The mapping is done starting from the entities, relationships and attributes of the data model
to the EDIFACT message.
This mapping is presented as a table containing the entities of the following information ;
- the attributes
- the segment group number
- the segment by its tag
- the Edifact data element
- remarks about the usage.
ATTRIBUTE SEGMENT SEGMENT TDID REMARKS

GROUP Data
Element
Entity : REMITTANCE ADVICE

Remittance advice number BGM 1004
Remittance advice date/time DTM 2380 DTM segment in the header,
following BGM.
Entity : PAYMENT
Payment means PAI 4461
Payment date DTM 2380 DTM segment in the header,
following BGM.
Payment currency Group 3 CUX 6345
Payment amount MOA 5025 MOA segment in the summary
section.
Payment order number RFF 1154 Use the code PQ in element
1153.
Payers (customers) financial FII C088 Use code PB in element 3035.
institution
Payers (customers) financial FII 3194
institution account number
Payees (suppliers) financial FII C088 Use code RB in element 3035.
institution
Payees (suppliers) financial FII 3194
institution account number
Entity : ACCOUNTING
DOCUMENT
Message / document type Group 4 DOC 1001
Message / document number Group 4 DOC 1004
Message / document date Group 4 DTM 2380
Invoice (credit- , debit note) currency Group 4 MOA 6345
or
Group 5 CUX 6345
Invoice (credit-, debit note) amount Group 4 MOA 5004 Use the code 77 in element
(amount due) 5025.
Amount remitted Group 4 MOA 5004 Use the code 139 in element
5025.
Payers (customers) payment Group 4 RFF 1154 Use code AHK in element 3035.
reference number
Invoicing party payment reference Group 4 RFF 1154 Use code AHJ in element 3035.
number
17
ATTRIBUTE SEGMENT SEGMENT TDID REMARKS

GROUP Data
Element
Entity : ADJUSTMENT
Adjustment reason Group 6 AJT 4465
Adjustment description Group 6 FTX C108
Adjustment amount Group 6 MOA 5004 Use the code 109 in element
5025.
Adjustment reference Group 6 RFF 1154 Use the relevant code in element
1153.
Entity : COMPANY
Company code, name and address Group 1 NAD 1154 Use the relevant code for 1153.
Contact information Group 2 CTA C056 Use the relevant code for 3139.
Communication contact Group 2 COM C076
Entity : MESSAGE / DOCUMENT

Message / document type Header RFF 1153 Header section level
or
Group 4 Accounting documents level
or
Group 6 Adjustment level
Message / document number Header RFF 1154 Header section level
or
or
Message /document date Header DTM 2380 Header section level
or
or
18
4.3 Branching Diagram of the Segments used by Eurofer
REMADV Remittance advice message, version D97A

Message to enable the transmission of the information concerning the payments.
The codes used for the usage indicator (USG. IND.) for the segments.
R for REQUIRED - Should always be used in the message
O for OPTIONAL - May be used by trading partners if required.
X for EXCLUDED - Not used in the message.
The codes used for the status of the segments according to EDIFACT:
M for MANDATORY
C for CONDITIONAL
Heading Section
USG.IND. PAGE NUM. TAG NAME STATUS REPEATS GROUP REPEATS
R UNH Message header M 1

R BGM Beginning of message M 1
R DTM Date/time/period M 5
O RFF Reference C 5
O FII Financial institution C 5
O PAI Payment instructions C 1
O FTX Free text C 5
X GIS General indicator C 5
R SEGMENT GROUP 1 C 99
R NAD Name and address M 1
O SEGMENT GROUP 2 C 5
R CTA Contact information M 1
O COM Communication contact C 5
R CUX Currencies M 1
X DTM Date/time/period C 1
19
Detail Section

R DOC Document / message details M 1
R MOA Monetary amount M 5
O DTM Date/time/period C 5
O RFF Reference C 5
X NAD Name and address C 2
R CUX Currency M 1
X DTM Date / time / period C 1
R AJT Adjustment details M 1
O MOA Monetary amount M 1
O RFF Reference M 1
O FTX Free text C 1
X SEGMENT GROUP 7 C 5
X INP Parties to instruction M 1
X FTX Free text C 5
X DLI Document line identification M 1
X MOA Monetary amount C 5
X PIA Additional product id C 5
X DTM Date / time / period C 5
X CUX Physical and logical state M 1
X DTM Parties to instruct C 1
X AJT Adjustment details M 1
X MOA Monetary amount C 1
X RFF Reference C 1
X FTX Free text C 5
Summary Section
R UNS Section control M 1

R MOA Monetary amount M 9
R UNT Message trailer M 1
20
EUROFER REMADV REMITTANCE ADVICE MESSAGE VERSION - DECEMBER 1999 UN/EDIFACT DIRECTORY : D97.A
Level
UN BGM UNS UN
00 H T
M 1 M M M
1 1 1
G01 G03
C 99 C 5
01
DTM RFF FII PAI FTX NA CUX MOA
D See page 2
M 5 C 5 C 5 C 1 C 5 M 1 M 1 M 9
G02
C 5
02
CTA
M 1
03
COM
C 5
Branching Page
Diagram 1
EUROFER REMADV REMITTANCE ADVICE MESSAGE VERSION - DECEMBER 1999 UN/EDIFACT DIRECTORY : D97.A
Leve
l
G04
See page
1 C 9999
01
DOC
M 1
G05 G06
C 5 C 100
02
RFF CUX AJT
MOA DTM
M C C 5 M 1 M 1
5 5
03
MOA
RFF FTX
C C 1 C 5
1
04
Branching Diagram Page 2
21
4.4 General description of the message - subset of Eurofer
4.4.1 Message definition and segment clarification
This section is provided to give clarification and further explanation to the usage of the
segments within the message defined by Eurofer. The message consists of three sections, a
heading section, a detail section and a summary section.
The heading section is representing the payment details, the corresponding references and
the parties involved. Detail information which applies or relates to all line items of the detail
section can also be given in the heading section.
This section should be read in conjunction with the segment usage and the branching
diagram (chapter 3.3.) which indicates the required (R) and optional (O) segments and
segment groups.
The following guidelines and principles apply to the whole message of Eurofer and are
intended to facilitate the understanding and the implementation of the message.
All the specified data/times (segment DTM) should be in the format 'CCYYMMDD'/'hhmm'
unless all parties involved in the transaction agree that there is a functional requirement for
an alternative format.
Periods should be specified as whole numbers representing the required period as indicated
in the format qualifier (weeks, month, etc)
Where a choice of code or text is given, only the code element should be used if possible.
Optional (conditional) data that are not required in the message should not be included.
Care must be taken that the segment qualifier in dependent segments do not conflict with the
segment qualifier of the trigger segment of the group.
22
4.4.2 Message description - Heading section
Information to be or which can be provided in the heading section of the message.
Segment UNH, Message Header

A service segment starting and uniquely identifying a message. The message type code
for the EUROFER remittance advice message is "REMADV".
Note : Remittance advice messages complying with this document must contain the
following data in the segment UNH composite data element S009 with data elements ;
- 0065 REMADV
- 0052 D
- 0054 97A
- 0051 UN
Segment BGM, Beginning of message

A segment for unique identification of the Remittance advice message, the type of
Remittance advice and its function.
Segment DTM, Date/time/period

A segment specifying the dates, and when relevant, the times related to the whole
message. The segment must be specified at least once to specify the message date as
allocated by the sender.
Segment RFF, Reference

A segment for referencing documents which relate to the whole message.
Segment FII, Financial institutions

A segment identifying the financial institution e.g. bank and account number and where
relevant the currency of the account, for each party involved in the transaction. The
Payer institution may indicate the previously agreed choice of financial institution for
payment.
Segment PAI, Payment instructions

A segment specifying the conditions, guarantee, method and channel of payment for the
Remittance advice.
Segment FTX, Free text

A segment with free text information, in coded or clear form, used when additional
information is needed but cannot be accommodated within other segments. In computer
exchanges such text will normally require the receiver to process this segment
manually.
Segment GIS, General indicator

A segment identifying various indicators required by a processing system.
Eurofer has decided not to use this segment.
23
Segment group 1 : NAD-SG2

A group of segments identifying the parties involved in the transaction and, optionally
the contact points and numbers.
Segment NAD, Name and address

A segment to identify a party name and address, either by coded identification or in
clear form.
It is recommended that where possible the coded form of the party ID should be
specified e.g. the payer and payer are known to each other, thus only the coded ID is
required.
Segment group 2 : CTA-COM

A group of segments identifying the contact person or department for a trading party
and specifying the communication channel and number.
Segment CTA, Contact information

A segment to identify a person or department and their function, to whom
communication should be directed.
Segment COM, Communication contact

A segment specifying the communication channel and number for the specified contact.
Segment group 3 : CUX-DTM

A group of segments specifying the currencies and related dates/periods valid for the
whole Remittance advice. Currency data may be omitted in national applications but
will be required for international transactions.
Eurofer has decided to use only the segment CUX of this group.
Segment CUX, Currencies

A segment to identify the currencies required in the Remittance advice. A rate of
exchange may be given to convert a reference currency into a target currency.
24
4.4.3 Message description Detail section
Information to be or which can be provided in the detail section of the message.
Segment group 4 : DOC-MOA-DTM-RFF-NAD-SG5-SG6-SG7-SG8

A group of segments providing details of all documents, e.g. invoices, statements,
despatch advices, etc, to which the Remittance advice refers. It includes information on
the monetary
amounts for each document and on any adjustments (with an indication of the reason for
adjustments) and discounts. For information purposes an indication of the tax element
can be provided.
Eurofer has decided to use only the segments DOC, MOA, DTM, RFF, and the segment
groups SG5 and SG6.
Segment DOC, Document / message details

A segment for identifying the reference document against which payment is being
made.
Segment MOA, Monetary amount

A segment giving the monetary amounts for the amount due and the amount to be
remitted.
Segment DTM, Date/time/period

A segment to specify the date of the referenced document and to indicate any other
relevant dates applicable, e.g. Due date, Tax point date, etc.

A segment for the inclusion of any additional references related to the reference
document.
Segment group 5 : CUX-DTM

A group of segments specifying the currencies and the related dates/periods valid of the
referenced document where different to the remittance currency.
Eurofer has decided to use only the segment CUX of this group.
Segment CUX, Currencies

A segment identifying the currencies and associated exchange rate of the referenced
document where different from the remittance currency.
Segment group 6 : AJT-MOA-RFF-FTX

A group of segments to indicate adjustment amounts and their referenced documents.
Segment AJT, Adjustment details

A segment indicating any adjustments to the amounts originally specified in the
referenced document, and to which items such adjustments apply, with the associated
reason for adjustment.
25

A segment giving the monetary amounts of the adjustments of each reference document
(e.g. original amount, discount amount, etc).
The currency data elements should not be used.

A segment for the inclusion of any additional references related to the reference
document.
Segment FTX, Free text

A segment giving information in clear text when it is necessary.
4.4.4 Message description Summary section
Information to be or which can be provided in the summary section of the message.
Segment UNS, Section control

A service segment placed at the start of the summary section to avoid segment collision.

A segment giving the total amount of the payment to be made or other amounts. It is
taken as given, i.e. is not subject to recalculation. It may be used for checking
operations, such as message validation.
Segment UNT, Message trailer

A service segment ending a message, giving the total number of segments in the
message and the control reference number of the message.
26
4.5 Detailed description of the message - subset of Eurofer

4.5.1 Detailed segment clarification
This section is provided to give detailed clarification and a further explanation to the usage
of the data elements in the segments of the Remittance advice message defined in the subset
of Eurofer. The message consists of three sections, a heading section, a detail section and a
summary section.
The section 4.5.2. describes each segment used in the heading section of the Eurofer
Remittance advice message. The section 4.5.3. describes each segment used in the detail
section of the Eurofer Remittance advice message. The section 4.5.4. describes each
segment used in the summary section of the Eurofer Remittance advice message.
The original EDIFACT segment layout is listed. The appropriate comments relevant to the
Eurofer subset are indicated.
The segments are presented in the sequence in which they appear in the message. The
segment and the segment group tag is followed by Mandatory or Conditional indicator, the
maximum number of occurrences and the segment description.
Reading from left to right, in column one the usage indicator is for the use of the EDIFACT
data elements in the Eurofer subset.
In the other columns the information is given about the data element tag, data element name,
followed by the EDIFACT status and the format.
The codes used for the usage indicator (USG. IND.) for the data elements are,
R for REQUIRED - Should always be used in the message
O for OPTIONAL - May be used by trading partners if required.
X for EXCLUDED - Not used in the message.
27
4.5.2 Detailed segment description - Heading section
GROUP :
SEGMENT :
UNH MESSAGE HEADER
SEGMENT STATUS :
Mandatory 1
FUNCTION :
To head, identify and specify a message
NOTES :
This segment would normally be added as part of the translation process. It has been
included for completeness.
Data Element Summary

USG. IND. TAG NAME STATUS FORMAT
R 0062 MESSAGE REFERENCE NUMBER M an..14

Unique message number assigned by the sender
R S009 MESSAGE IDENTIFIER M

R 0065 Message type identifier M an..6
REMADV Remittance advice message
R 0052 Message type version number M an..3
D
R 0054 Message type release number M an..3
97A
R 0051 Controlling agency M an..2
UN United nations
X 0057 Association assigned code C an..6
X 0068 COMMON ACCESS REFERENCE C an..35
X S010 STATUS OF THE TRANSFER C

X 0070 Sequence message transfer number M n..2
X 0073 First/last sequence message transfer C a1
28
GROUP :
SEGMENT :
BGM BEGINNING OF MESSAGE
SEGMENT STATUS :
Mandatory segment repeat : 1
FUNCTION :
To indicate the type and function of a message and to transmit the identifying number.
NOTES :

R C002 DOCUMENT/MESSAGE NAME C

R 1001 Document/message name, coded C an..3
481 Remittance advice
X 1131 Code list qualifier C an..3
X 3055 Code list responsible agency, coded C an..3
X 1000 Document/message name C an..35
R 1004 DOCUMENT/MESSAGE NUMBER C an..35

Contains the Remittance advice number
R 1225 MESSAGE FUNCTION, CODED C an..3

5 Replace
7 Duplicate (re-transmission)
9 Original
O 4343 RESPONSE TYPE, CODED C an..3

AB Message acknowledgement
NA No acknowledgement needed
29
GROUP :
SEGMENT :
DTM DATE / TIME / PERIOD
SEGMENT STATUS :
FUNCTION :
To specify date, and/or time, period.
NOTES :
All specified dates/times should be in the format 'CCYYMMDD'/'hhmm' unless all
parties involved in the transaction agree that there is a functional requirement for an
alternative format.

R C507 DATE/TIME/PERIOD M
R 2005 Date/time/period qualifier M an..3
137 Document/message date/time
138 Payment date
See code list EDIFACT for other values
R 2380 Date/time/period C an..35
R 2379 Date/time/period format qualifier C an..3
102 CCYYMMDD
203 CCYYMMDDhhmm
30
GROUP :
SEGMENT :
RFF REFERENCE
SEGMENT STATUS :
Conditional segment repeat : 5
FUNCTION :
To specify a reference.
NOTES :
This segment is used for referencing documents, relating to the whole message or to
all the received items specified in the detail section.
The documents paying for must be given in the segment group 4, triggered by the
segment DOC.

R C506 REFERENCE M
R 1153 Reference qualifier M an..3
AEK Payment order number
PQ Payment reference
See code list EDIFACT for other codes
R 1154 Reference number C an..35
X 1156 Line number C an..6
X 4000 Reference version number C an..35
31
GROUP :
SEGMENT :
FII FINANCIAL INSTITUTION INFORMATION
SEGMENT STATUS :
FUNCTION :
To identify an account and a related financial institution.
NOTES :

R 3035 PARTY QUALIFIER M an..3

PB Paying financial institution
RB Receiving financial institution
R C078 ACCOUNT IDENTIFICATION C

R 3194 Account holder number C an..35
X 3192 Account holder name C an..35
X 3192 Account holder name C an..35
O 6345 Currency, coded C an..3
O C088 INSTITUTION IDENTIFICATION C

O 3433 Institution name identification C an..11
O 1131 Code list qualifier C an..3
O 3055 Code list responsible agency, coded C an..3
O 3434 Institution branch number C an..17
O 3432 Institution name C an..70
O 3436 Institution branch place C an..70
X 3207 COUNTRY, CODED C an..3
32
GROUP :
SEGMENT :
PAI PAYMENT INSTRUCTIONS
SEGMENT STATUS :
FUNCTION :
To specify the instructions for payment.
NOTES :

R C534 PAYMENT INSTRUCTION DETAILS M

O 4439 Payment conditions, coded C an..3
O 4431 Payment guarantee, coded C an..3
1 Direct payment
33 Open account for payment
O 4461 Payment means, coded C an..3
20 Cheque
42 Payment to bank account
50 Payment by postgiro
X 1131 Code list qualifier C an..3
X 3055 Code list responsible agency, coded C an..3
X 4435 Payment channel, coded C an..3
33
GROUP :
SEGMENT :
FTX FREE TEXT
SEGMENT STATUS :
FUNCTION :
To provide free from or coded text information.
NOTES :

R 4451 TEXT SUBJECT QUALIFIER M an..3

AAI General information
X 4453 TEXT FUNCTION, CODED C an..3
O C107 TEXT REFERENCE C

O 4441 Free text identification M an..17
O C108 TEXT LITERAL C

R 4440 Free text C an..70
O 4440 Free text C an..70
O 3453 LANGUAGE, CODED C an..3
34
GROUP :
Group 01 : NAD SG2 SG3
Conditional group repeat : 99
SEGMENT :
NAD NAME AND ADDRESS
SEGMENT STATUS :
To specify the name/address and their related function, either by C082 only and/or
unstructured by C058 or structured by C080 thru 3207.
NOTES :
This segment is used for identifying the parties relevant for the whole message.
Party details can be given in coded form or clear text. We recommend the use of
coded form, using C082. The basis of this codification could be one of the national or
international code lists. Examples of such code lists are VAT-registration number,
Chamber of commerce, Wirtschaftsvereinigung, Odette, EAN, etc.

R 3035 PARTY QUALIFIER M an..3

BY Buyer
PE Payee
PR Payer
SE Seller
SU Supplier
O C082 PARTY IDENTIFICATION DETAILS C

R 3039 Party id identification M an..35
R 3055 Code list responsible agency, coded C an..3
58 EUROFER
91 Assigned by seller or seller's agent
92 Assigned by buyer or buyer's agent
O C058 NAME AND ADDRESS C

R 3124 Name and address line M an..35
O 3124 Name and address line C an..35
O C080 PARTY NAME C

R 3036 Party name M an..35
O 3036 Party name C an..35
O 3045 Party name format, coded C an..3
35

O C059 STREET C
R 3042 Street and number/P.O. Box M an..35
O 3042 Street and number/P.O. Box C an..35
O 3164 CITY NAME C an..35
O 3229 COUNTRY SUB-ENTITY IDENTIFICATION C an..9
O 3251 POSTCODE IDENTIFICATION C an..9
O 3207 COUNTRY, CODED C an..3

Use ISO 3166 two alpha country code.
36
GROUP :
Group 02: CTA - COM
SEGMENT :
CTA CONTACT INFORMATION
SEGMENT STATUS :
FUNCTION :
To identify a person or a department to whom communication should be directed..
NOTES :

O 3139 CONTACT FUNCTION, CODED C an..3

AD Accounting contact
IC Information contact
See code list EDIFACT for other codes.
R C056 DEPARTMENT OR EMPLOYEE DETAILS C

O 3413 Department or employee identification C an..17
O 3412 Department or employee C an..35
37
GROUP :
Group 02: CTA - COM
SEGMENT :
COM COMMUNICATION CONTACT
SEGMENT STATUS :
FUNCTION :
To identify a communication number of a department or a person to whom
communication should be directed.
NOTES :

R C076 COMMUNICATION CONTACT M

R 3148 Communication number M an..512
R 3155 Communication channel qualifier M an..3
EM Electronic mail
FX Telefax
TE Telephone
TL Telex
38
GROUP :
Group 03: CUX- DTM
SEGMENT :
CUX CURRENCIES
SEGMENT STATUS :
FUNCTION :
To specify currencies used in the transaction and relevant details for the
rate of exchange.
NOTES :
If the payment currency is different from the invoicing currency the segment CUX is
used to give the rate of exchange. This can be done by giving in the first occurrence
of the composite C504 the reference currency (invoicing currency), the second
occurrence of the composite C504 is used as target currency (payment currency) and
the rate of exchange can be specified in the data element 5402.

O C504 CURRENCIES DETAILS C

R 6347 Currency details qualifier M an..3
2 Reference currency
R 6345 Currency, coded C an..3
O 6343 Currency qualifier C an..3
4 Invoicing currency
O 6348 Currency rate base C n..4

3 Target currency
11 Payment currency
See code list for other codes
O 5402 RATE OF EXCHANGE C n..12
X 6341 CURRENCY MARKET EXCHANGE, CODED C an..3
39
4.5.3 Detailed segment description - Detail section

GROUP :
Group 04: DOC- MOA DTM RFF NAD SG5 SG6 SG7 SG8
SEGMENT :
DOC DOCUMENT/MESSAGE DETAILS
SEGMENT STATUS :
FUNCTION :
To identify documents, either printed, electronically transferred, or referenced.
NOTES :

R C002 DOCUMENT/MESSAGE NAME M

R 1001 Document/message name, coded C an..3
380 Commercial invoice
381 Credit note
382 Commission note
383 Debit note
389 Self-billed invoice
O 1000 Document/message name C an..35
R C503 DOCUMENT/MESSAGE DETAILS C

R 1004 Document/message number C an..35
X 1373 Document/message status, coded C an..3
X 1366 Document/message source C an..35
X 3453 Language, coded C an..3
X 3153 COMMUNICATION CHANNEL IDENTIFIER, CODED C an..3
X 1220 NUMBER OF COPIES OF DOCUMENT REQUIRED C n..2
X 1218 NUMBER OF ORIGINALS OF DOCUMENT REQUIRED C n..2
40
GROUP :
SEGMENT :
MOA MONETARY AMOUNT
SEGMENT STATUS :
FUNCTION :
To specify a monetary amount.
NOTES :

R C516 MONETARY AMOUNT M

R 5025 Monetary amount type qualifier M an..3
9 Amount due / amount payable
12 Amount remitted
77 Invoice amount
R 5004 Monetary amount C n..18
O 4405 Status, coded C an..3
41
GROUP :
SEGMENT :
DTM DATE / TIME / PERIOD
SEGMENT STATUS :
FUNCTION :
To specify date, and/or time, period.
NOTES :
All specified dates/times should be in the format 'CCYYMMDD'/'hhmm' unless all
parties involved in the transaction agree that there is a functional requirement for an
alternative format.

R C507 DATE/TIME/PERIOD M
R 2005 Date/time/period qualifier M an..3
137 Document/message date/time
R 2380 Date/time/period C an..35
R 2379 Date/time/period format qualifier C an..3
102 CCYYMMDD
203 CCYYMMDDhhmm
42
GROUP :
SEGMENT :
RFF REFERENCE
SEGMENT STATUS :
FUNCTION :
NOTES :
This segment is used for referencing documents, relating to the referenced document
in the segment DOC.

R C506 REFERENCE M
AHJ Payees reference number
AHK Payers reference number
CT Contract number
CO Buyers order number
43
GROUP :
Group 05: CUX- DTM
SEGMENT :
CUX CURRENCIES
SEGMENT STATUS :
FUNCTION :
To specify currencies used in the transaction and relevant details for the
rate of exchange.
NOTES :
If the payment currency is different from the invoicing currency the segment CUX is
used to give the rate of exchange. This can be done by giving in the first occurrence
of the composite C504 the reference currency (invoicing currency), the second
occurrence of the composite C504 is used as target currency (payment currency) and
the rate of exchange can be specified in the data element 5402.


2 Reference currency
4 Invoicing currency

3 Target currency
11 Payment currency
See code list for other codes
O 5402 RATE OF EXCHANGE C n..12
X 6341 CURRENCY MARKET EXCHANGE, CODED C an..3
44
GROUP :
Group 06: AJT- MOA RFF FTX
SEGMENT :
AJT ADJUSTMENT DETAILS
SEGMENT STATUS :
FUNCTION :
To identify the reason for an adjustment.
NOTES :

R 4465 ADJUSTMENT REASON, CODED M an..3

1 Agreed settlement
3 Damaged goods
4 Short delivery
5 Price query
9 Invoice error
X 1082 LINE ITEM NUMBER C an..6
45
GROUP :
SEGMENT :
MOA MONETARY AMOUNT
SEGMENT STATUS :
FUNCTION :
NOTES :


5 Adjustment amount
46
GROUP :
SEGMENT :
RFF REFERENCE
SEGMENT STATUS :
FUNCTION :
NOTES :
This segment is used for a referencing document, relating to the adjustment of the

R C506 REFERENCE M
CT Contract number
DQ Delivery note number
PL Price list number
47
GROUP :
SEGMENT :
FTX FREE TEXT
SEGMENT STATUS :
FUNCTION :
To provide free from or coded text information.
NOTES :

R 4451 TEXT SUBJECT QUALIFIER M an..3

CHG Change information
X 4453 TEXT FUNCTION, CODED C an..3
O C107 TEXT REFERENCE C

O 4441 Free text identification M an..17
O C108 TEXT LITERAL C

R 4440 Free text C an..70
O 3453 LANGUAGE, CODED C an..3
48
4.5.4 Detailed segment description - Summary section
GROUP :
SEGMENT :
UNS SECTION CONTROL
SEGMENT STATUS :
FUNCTION :
Service segment to separate Header, Detail and Summary sections of a message.
NOTES :

R 0081 SECTION IDENTIFICATION M an1

S Separates the detail from the summary section.
49
GROUP :
SEGMENT :
MOA MONETARY AMOUNT
SEGMENT STATUS :
FUNCTION :
NOTES :


129 Total amount subject to payment discount
138 Total monetary discount amount
139 Total payment amount
50
GROUP :
SEGMENT :
UNT MESSAGE TRAILER
SEGMENT STATUS :
Mandatory 1
FUNCTION :
Service segment ending a message, giving the totals number of segments.
NOTES :

R 0074 NUMBER OF SEGMENTS IN A MESSAGE M n..6
R 0062 MESSAGE REFERENCE NUMBER M an..14

Unique message number assigned by the sender
51
All information provided in this documentation is provided as is without any warranties of any
kind including warranties of accuracy, fitness for a particular purpose, or non-infringement or
intellectual property.
EUROFER shall not be held responsible for any errors or any loss resulting from any use of this
document or the specification herein.
The materials contained in this document may be copied provided that ALL copies retain the
copyright and any other proprietary notices contained on the materials. No material may be
modified, edited or taken out of context such as its use creates a false or misleading statement or
impression as to the positions, statements or actions of the publisher.
2001 EUROFER. All rights reserved. All countries.
52

Remadv

Încărcat de

Informații document

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

Remadv

Încărcat de

Drepturi de autor:

Formate disponibile

REMADV

Remittance Advice Message

Version December 1999

EDIFER WORKING GROUP - Message development

REMITTANCE ADVICE MESSAGE (Table of Contents)

REMITTANCE ADVICE MESSAGE

The manual has been structured in the following format:

1.1 General information

- A Remittance advice is a notice of a payment to be made.

- Each Remittance advice shall relate to only one settlement date.

A Remittance advice refers to:

2.1 Data Model Format

An attribute describes a unique characteristic (information which can appear on the

2.2 Data Model Diagram

Example relationship between Remittance advice and Accounting document

1. In the direction from Remittance advice to Accounting document.

2. In the direction from Accounting document to Remittance advice.

2.3. Data model entities

The basic data entities

The related data entities

REMITTANCE This entity contains the general information about a remittance

COMPANY An organisation with whom we deal for whatever purpose.

2.4. Data model relationships

- Direction from Remittance advice to Payment.

REMITTANCE ADVICE - ACCOUNTING DOCUMENT

- Direction from Remittance advice to Accounting document.

ACCOUNTING DOCUMENT - ADJUSTMENT

- Direction from Accounting document to Adjustment.

2.5. Data model attributes

ENTITY : REMITTANCE ADVICE

remittance advice number

remittance advice date/time

payment order number

payers (customers) financial institution

payers (customers) financial institution account number

payees (suppliers) financial institution

payees (suppliers) financial institution account number

ENTITY : ACCOUNTING DOCUMENT

message / document type

message / document number

message / document date

invoice (credit-, debit note) currency

invoice (credit-, debit note) amount (amount due)

payers (customers) payment reference number

invoicing party payment reference number

THE RELATED DATA ENTITIES

company code, name and address

ENTITY : MESSAGE / DOCUMENT

message / document type

message / document number

message /document date

3.1. Functional Definition

3.2. Field of application

A Remittance advice may include a cross reference to a Payment order.

Each Remittance advice shall relate to only one settlement date.

3.4. Message usage

4.1 Message Structure

4.1.1. Message structure - Heading section

4.1.2. Message structure - Detail section

4.1.3. Message structure - Summary section

4.2. Mapping of the Data model to the message

SEGMENT SEGMENT FUNCTION COMMENTS

BGM To identify the Remittance advice message by its Mandatory.

GROUP 1 To identify the parties (companies) relevant to