ANSI X9 TR 51:2020 pdf download.Levies Companion Document-Uniform Adoption of X9.129 for Levies Version 3.0.
The purpose of this document is to formalize an industry standard for exchange of legal orders using the ANSI X9.129 standard format and a compilation of industry norms. This document is not intended to replace the ANSI X9.129 standard, but rather to clarify how financial institutions and agencies should use the standard to ensure all necessary and appropnate levies and asset based orders are exchanged between financial institutions and/or agencies. The use of this document requires that all legal orders exchange paicipants obtain, use and adhere to the record and field usage definitions detailed In the ANSI X9. 129 standard, Users of this document are required to review and be knowledgeable of the full standard to ensure file structure and data and field specifications are understood and used correctty. This document fuher defines the specific usage of the ANSI X9.129 standard and describes all of the records and fields which contain critical data. Based on this usage, it is reasonable to expect that exchange paicipants will implement file validation practices to ensure that all critical data is contained in legal order exchange files. If a file contains records or fields of cntical data that do not conform to the usage practices detailed in the standard is reasonable to expect the receiving Institution or agency will reject the em or file back to the sending institution or agency as the order(s) contained in the file may be unusable/unprocessable. Conversely, if a record or field which does not contain crical data is populated with incomplete, erroneous, or invalid data is reasonable to expect these files or items would be accepted and processed.
2 General Conventions of the Document
The document contains details for each record that is deemed to have cntical data and lists all associated fields contained in ANSI X9,129.
The first piece of information is the validation criteria column, This column defines whether or not the field will be validated for legal orders exchange. The validation criteria column has three seings, ‘required’, ‘required if present’ or blank.
• ‘Required’ is defined as: must be present and in compliance with the ANSI X9.129 standard’s usage deflnion unless this Companion Document modifies that usage. If modified by this document, the LCD takes precedence, Erroneous or invalid data may result in an item level or file level reject.
• ‘Required if present’ is defined as: if the field is populated it must be in compliance wh the ANSI X9.129 standard’s usage definition unless this Companion Document modifies that usage. If modified by this document, the LCD takes precedence. Erroneous or invalid data may result in an item level or file level reject.
• When “Validation Criteria” is blank means no special validation is required.
• Mandatory fields which are A (Aipha), AN (Alphanumeric) and ANS (Alphanumeric/special) Types cannot be all blanks.
The second piece of information is a comments column. This column provides additional information regarding each field augmenting the ANSI X9.129 standard to facilitate legal orders exchange.
Records within this document are either Mandatory or Conditionally Required. Mandatory records must atways appear within a file. Conditionally Required records will appear when the condion as stated in the introduction to that record is fulfilled.ANSI X9 TR 51 pdf download.