Return to Stylus Studio EDIFACT home page. Return to Stylus Studio EDIFACT D94B Messages page. Statement of account message
0. INTRODUCTIONThis specification provides the definition of the Statement of account message (STATAC) to be used in Electronic Data Interchange (EDI) between trading partners involved in administration, commerce and transport. 1. SCOPE1.1. Functional DefinitionA Statement of Account is a communication from a Seller or his agent to a Buyer or his agent, providing information about the status of an account at a specific point in time. It is used as an aid to reconciliation. At the same time it may be a reminder of payment due. 1.2. Field of ApplicationThe UN Standard Statement of Account Message may be used for both national and international business. It is based on universal commercial practice and is not dependent on the type of business or industry. 1.3. Principles
2. REFERENCESSee UNTDID, Part 4, Chapter 2.6 UN/ECE UNSM - General Introduction, Section 1. 3. TERMS AND DEFINITIONSSee UNTDID, Part 4, Chapter 2.6 UN/ECE UNSM - General Introduction, Section 2. 4. MESSAGE DEFINITION4.1. Data Segment ClarificationThis section should be read in conjunction with the Branching Diagram and the Segment Table which indicate mandatory, conditional and repeating requirements. The following guidelines and principles apply to the whole message and are intended to facilitate the understanding and implementation of the message: All specified dates/times should be in the format 'yymmdd'/'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, months, etc.) Where a choice of code or text is given only the code element should be used wherever possible. Conditional data that is 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 a group. Free text information within the message should be avoided as this inhibits automatic processing. It is only used when additional information that cannot be accommodated within the other segments is required. 4.1.1. Header sectionInformation to be provided in the Header section: 0010 UNH, Message headerA service segment starting and uniquely identifying a message. The message type code for the Statement of account message is STATAC. Note: Statement of account messages conforming to this document must contain the following data in segment UNH, composite S009:
0020 BGM, Beginning of messageA segment by which the sender must uniquely identify the Statement of Account. 0030 DTM, Date/time/periodA 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. 0040 RFF, ReferenceA segment for referencing documents which relate to the whole message. 0050 CUX, CurrenciesA segment identifying the currency of the Statement of Account. The payment currency is the default currency for all amounts, it must be specified in international transactions. 0060 Segment Group 1: NAD-SG2A group of segments identifying the parties involved in the transaction and, optionally the contact points and numbers. 0070 NAD, Name and addressA segment to identify a party name and address, either by coded identification or in clear form. 0080 Segment Group 2: CTA-COMA group of segments identifying the contact person or department for a trading party and specifying the communication channel and number. 0090 CTA, Contact informationA segment to identify a person or department and their function, to whom communications should be directed. 0100 COM, Communication contactA segment specifying the communications channel and number for the specified contact. 4.1.2. Detail sectionInformation to be provided in the Detail section: 0110 Segment group 3: DOC-MOA-DTM-RFF A group of segments providing details of all documents, e.g. invoices, credit notes, etc, to which the Statement of Account refers. It contains details of the monetary values associated with the documents and of relevant dates. There must be at least one occurrence of this group within the Statement of Account Message. 0120 DOC, Document/message detailsA segment identifying the reference document against which payment is to be made. 0130 MOA, Monetary amountA segment to specify the required amounts for the referenced document e.g. amount due, discount amount, payment amount. 0140 DTM, Date/time/periodA 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. 0150 RFF, ReferenceA segment for the inclusion of any additional references related to the reference document. 4.1.3. Summary sectionInformation to be provided in the Summary section: 0160 UNS, Section controlA service segment placed at the start of the summary section to avoid segment collision. 0170 MOA, Monetary amountA segment specifying the total amount pertaining to the message. The outstanding balance amount is mandatory and is taken as given, i.e. it is not subject to recalculation. 0180 FTX, Free textA segment for free text information, in coded or clear form. 0190 UNT, Message trailerA service segment ending a message, giving the total number of segments in the message and the control reference number of the message. 4.2. Data segment index (Alphabetical sequence by tag)
4.3. Message structure4.3.1. Segment table
Return to Stylus Studio EDIFACT D94B Messages page. |
Site Map | Privacy Policy | Terms of Use | Trademarks |