ANSI X9.129-2016 pdf download.Legal Orders Exchange
1 Scope
This standard establishes the file sequences, record types, and field formats to be used for the electronic bilateral exchange of legal orders, specific to levies and asset based orders. The standard file format will enable an automated transport of standard formats for legal order presentment request types. This will include electronic legal services, presentment, ingestion of the document into a Financial Institution and its outbound response. The file transmission specifications will contain data fields only. Future versions of this Standard may include transmission of supporting documentation. The Financial Institution will follow the mandated state/federal regulations in the processing of legal orders. The standard does not address any changes to Regulations. The Financial Institutions and Requesters will abide by independent service level agreements established between the two parties to detail the specific expectations of service (included, but not limited to scope, quality, turnaround time and responsibilities).
2 Purpose and Application
The purpose of this standard is to provide a structure to facilitate the electronic bi-lateral exchange of legal order information including legal service of levies, or other asset based orders, Financial Institution response notifications, and payout/release requests. Although this standard is formatted for levies, it will serve as the foundation for future legal order types. This standard does not include or cover remittance of monetary transactions and or levies/garnishments that by statute or jurisdiction cannot be fulfilled by this standard. The standard specifies a file transmission environment with legal order related records providing the necessary information for processing them in other environments.
4 File Structure
The formats contained in this standard are designed to provide the data required by a Financial Institution to process a Legal Order notice or request, while minimizing the number of records and the amount of data that must be sent. The standard recognizes levels of Legal Order Processing, e.g., levy/garnishment name or type, hold, release pay instructions, etc. The standard minimizes the number of records required to create the adjustment message based on the adjustment level, as well as the action taken indicator and the investigation type. This clause describes: a) the different types of records which are mandatory and conditional within a file; and b) the organization of a file.
4.2.2 Requester
Supplemental Information Record (Type 10) The Requester Supplemental Information Record (Type 1 0) shall be present and always follow the File Header Record (Type 01 ). It is a mandatory record with one record per file.
4.2.3 Request Content Record (Type 20)
The Request Content Record (Type 20) shall be present and always follow the Request Supplemental Information Record (Type 1 0). There shall be one content record for each case in the file. 4.2.2 Request Debtor Record (Type 25) The Request Debtor Record (Type 25) is a mandatory record to identify each customer in a legal order case and will always follow the Request Content Record (Type 20). There shall be one debtor record per customer. 4.2.3 Request Account Record (Type 26) The Request Account Record (Type 26) is a conditional record available to provide an order to a specific account only and will always follow a Request Debtor Record (Type 25). There shall be one account record per account.
4.2.4 Maintenance Request Record (Type 40)
The Maintenance Request Record (Type 40) shall follow the Request Debtor Record (Type 25) or the conditional Request Account Record (Type 26). This record type is conditional and used by the Requester to provide the action for the Financial Institution to take on an existing case.
4.2.5 Response Supplemental
Information Record (Type 11) The Response Supplemental Information Record (Type 1 1 ) shall be present and always follow the File Header Record (Type 01 ). It is a mandatory record with one record per file. 4.2.6 Response Content Record (Type 30) The Response Content Record (Type 30) shall be present and always follow the Response Supplemental Information Record (Type 1 1 ). There shall be one content record for each case in the file. All records within the Response Content Record (Type 30) must have a match to and be in the same order as in the Request Content Record (Type 20).ANSI X9.129-2016 pdf download
