Patent Publication Number: US-8527548-B2

Title: Method and apparatus for electronic collection, translation, grouping, and delivery of wage assignment information

Description:
I. RELATED APPLICATIONS 
     This application is a continuation of and claims benefits to application Ser. No. 12/955,705, filed on Nov. 29, 2010, (now U.S. Pat. No. 8,229,978), which is a continuation of and claims benefits to application Ser. No. 12/320,702, filed Feb. 2, 2009, (now U.S. Pat. No. 7,877,423), which is a divisional of and claims benefits to application Ser. No. 11/438,443, filed May 23, 2006, (now U.S. Pat. No. 7,720,797), which is a continuation of and claims benefits to application Ser. No. 10/155,965, filed May 29, 2002, (now U.S. Pat. No. 7,072,909), which is a continuation of and claims benefits to application Ser. No. 09/200,943, filed on Nov. 30, 1998, (now U.S. Pat. No. 6,567,821), which claims the benefit of U.S. Provisional Application No. 60/085,731, filed May 15, 1998, the contents of all of the above applications are incorporated herein by reference in their entirety. 
    
    
     II. BACKGROUND OF THE INVENTION 
     A. Field of the Invention 
     The present invention relates generally to the collection, translation, grouping, and delivery of wage assignment information. More particularly, the invention relates to methods and apparatus for electronic collection of wage assignment information, translation of the information into an electronic wage assignment format, grouping of the formatted information into files by batching for each respective recipient, and electronic delivery of the batched information files to each respective recipient. 
     B. Description of the Related Art 
     If a private or public entity wishes to collect a financial obligation from a particular person, the entity may obtain a judicial order requiring that the person make payments to satisfy the obligation. Frequently, the most common method to satisfy a court-ordered or court-enforced financial obligation is by requiring that the employer withhold a portion of the person&#39;s salary in the form of a wage assignment. A wage assignment may be implemented either by manual or electronic means. Manual implementation is the least efficient manner to process a wage assignment. Furthermore, even electronic implementation includes significant temporal and structural inefficiencies, primarily with regard to the collection, translation, grouping, and delivery of the information. 
     Electronic Implementation of Ware Assignments. Electronic commerce (EC) describes the paperless exchange of business information using electronic data interchange (EDI), electronic funds transfer (EFT), and other means of electronic communication. Of these various types of electronic communication, EDI allows for the accumulation, processing, transmittal, and receipt of business-related information that was once dependent on paper transactions. Generally, EDI describes the computer-to-computer exchange of business information using a public standard. The first such public EDI standard was created by the Transportation Data Coordinating Committee (TDCC), which created the first set of industry EDI standards comprising forty-five transaction sets for the transportation industry. These initial EDI transaction sets provided for the exchange of business information pertaining to ocean, motor, air, and rail carriers and the associated shippers, brokers, customs, freight forwarders, and bankers. Eventually, other business segments soon discovered that EDI was a more cost effective means of communicating business transaction information than paper transactions. 
     For the computer-to-computer exchange of business transaction information through EDI, however, a standard format is required for reasons of compatibility. Initially, the TDCC standards controlled, but these standards were limited to business transactions in the transportation industry. As the use of EDI expanded, there was a need for a new, broader standard. In response, the American National Standards Institute (ANSI) was tasked with the responsibility of creating a new standard, a standard that would include transaction sets for all types of business information. Yet, while ANSI is the coordinator and clearing house for national standards in the United States, ANSI does not write national standards. Instead, ANSI charters organizations, called Accredited Standards Committees (ASCs), to prepare consensus standards. ASCs are composed of voluntary representatives from industry, labor, consumer, and government. Periodically, ANSI charters an ASC to develop a new standard. 
     One such ASC, the ASC X12, was chartered by ANSI to develop standards for the structure, format, and content of electronic business transactions conducted through EDI. The ASC X12 is administered by the Data Interchange Standards Associations, Inc. (DISA), a not-for-profit corporation. Under the management of DISA, the ASC X12 composed and issued the ANSI X12 standard (i.e., the X12 standard). Pursuant to the X12 standard, each EDI transaction involves the electronic transmission of a business document using a particular transaction set. Thus, the transaction sets (or record sets) in the X12 standard define both the file structure and content format for communicating electronic business transactions using EDI. 
     Under the X12 standard, there are a number of particular record sets, each set corresponding to a particular type of business transaction. As of 1994, the X12 standard included 187 record sets. Notably, the various record sets of the X12 standard are delineated by specific numeric codes. For example, record set 135 pertains to student loan applications, and record set 813 pertains to electronic tax filing. For purposes of wage assignments, however, record set 521 is the most common type of transaction set, as record set 521 pertains to income or asset offset. Notably, the record set 521 is still under development. Nonetheless, when finally implemented, the 521 record set will make it possible to electronically communicate wage assignment information. 
     Therefore, under the X12 standard, there is an EDI transaction set for offsets from wages or other income (i.e., the 521 record set) that allows for offsets to wages or other income by means of an electronic implementation of a wage assignment. As described in the Draft Standard for Trial Use, 521 Income or Asset Offset, dated May 15, 1997, hereby incorporated by reference, the record set 521 allows for the input of both the wage transfer instruction as well as other pertinent information related to a wage assignment transaction. The wage transfer instruction and the other information relating to the wage transfer are referred to collectively as wage assignment information. With wage assignment information, an employer may be instructed to withhold automatically a predetermined portion of the wage of a particular employee and to transfer automatically the withheld portion to another person or entity. Thus, for the electronic implementation of a wage assignment, however, the wage assignment information must be collected from an initiating entity; the wage assignment information must then be translated into the proper electronic format; the wage assignment information must then be batched for each recipient; and the wage assignment information must then be delivered to each respective recipient. Furthermore, for this electronic implementation, the initiator of the wage assignment must be capable of sending the wage assignment information in a proper electronic format, and the recipient must be capable of receiving the wage assignment information in an electronic format and then implementing the wage assignment. 
     However, the present systems and methodologies for the electronic processing of wage assignment information are inefficient and undesirable. These shortcomings are demonstrated by the present systems and methodologies. For purposes of considering the present systems and methodologies for electronic implementation of wage assignment information, an illustration of one common type of wage assignment is used herein as an example, namely, a wage assignment based on a child support obligation. With the present systems and methodologies, pursuant to an order by a judicial entity, a state entity generates a wage assignment order for a noncustodial parent to make child support payments to a custodial parent. In almost all cases, the state entity mails the order to the employer of the noncustodial parent. The employer of the noncustodial parent must then process the wage assignment information, so that a withheld wage portion is automatically removed from the wage of the noncustodial parent. Notably, for purposes of the present systems and methodologies, as set forth below, virtually any type of wage assignment would be similarly treated as in the example of a wage assignment based on a child support obligation. 
     Collection of Wage Assignment Information. 
     For a typical wage assignment, such as, for example, a child support obligation, a particular state entity is generally responsible for generating the wage assignment orders for every noncustodial parent subject to a wage assignment. In processing the orders, the state entity generally sends a wage assignment order to the indicated employer of each noncustodial parent. Thus, large employers generally receive multiple wage assignment orders. Moreover, in most cases, employers not only receive multiple wage assignment orders from a state entity, but employers also receive multiple wage assignment orders from multiple state entities. This current system is inefficient and undesirable. According to the present systems and methodologies, there is no means to collect the wage assignment orders and transmit the orders as a single unit to the employers, which would allow for the translation of the orders into an EDI format, batching of the files for each recipient, and delivery as a single EDI transaction. Thus, the present systems and methodologies for collecting wage assignment information are inadequate. 
     Translation of Wage Assignment Information. 
     For a typical wage assignment, such as, for example, a child support obligation, the X12 standard provides a mechanism for automating the allocation of wage assignment orders for child support payments to employers. Because the X12 standard includes a transaction set for wage assignments (i.e., the 521 record set), EDI may be used to process wage assignments electronically. However, in most states, wage assignment orders are still issued on paper. Thus, in these states, wage assignments cannot be implemented electronically. Further, in the remaining states that may use electronic wage assignments, while the wage assignment orders may be electronically generated, the orders are not issued in a format compatible with the X12 standard. Thus, a wage assignment order cannot be processed as an EDI transaction. As such, the present systems and methodologies are inefficient and undesirable. Therefore, according to the present systems and methodologies, there is no means to translate either the paper or the electronic information produced by the state agencies into a format compatible with the X12 standard that may then be batched delivered as an EDI file to employers. Thus, the present systems and methodologies of translating wage assignment information are inadequate. 
     Grouping of Wage Assignment Information. 
     For a typical wage assignment, such as, for example, a child support obligation, separate wage assignment orders are issued for each wage assignment. Thus, as noted above, an employer may not only receive numerous wage assignment orders but may also receive numerous wage assignment orders from numerous state entities. Such inefficiencies strain the resources of employers that must adhere to both judicial and governmental requirements regarding the processing of wage assignments. The X12 standard provides a means to avoid these inefficiencies by the use of EDI. Using the fields of a record set from the X12 standard, such as, for example, the 521 record set, wage assignment orders could be collected, translated and then batched for delivery to employers as a single EDI file. However, the present systems and methodologies do not provide a means of grouping wage assignment orders by recipient, where the orders are also collected, translated, and delivered in a wage assignment collection and delivery system. Thus, the present systems and methodologies of grouping wage assignment information are inadequate. 
     Delivery of Wage Assignment Information. 
     For a typical wage assignment, such as, for example, a child support obligation, an employer implements the wage assignment upon receipt of the wage assignment order. However, if the wage assignment order has been converted into an electronic format, the wage assignment information must be transmitted to the employer in a useable manner. Some employers are capable of receiving files electronically, but most employers are not equipped with this capability. Without these capabilities, an employer cannot receive wage assignment information electronically and automatically implement processing of the wage assignment. As such, the present systems and methodologies are inefficient and undesirable. According to the present systems and methods, there is no means to deliver wage assignment information to employers based on particular delivery requirements, where the information is initially collected from a state entity, translated into an electronic format, and then grouped for each recipient. Thus, the present systems and methodologies of delivering wage assignment information are inadequate. 
     Electronic Implementation of Wage Assignment Information. 
     For the reasons described above, systems and methods would be desirable that could collect wage assignment information, translate the wage assignment information into an EDI file compatible with the X12 standard, group the information by recipient, and then deliver a single EDI file to the each respective recipient. For a typical wage assignment, such as, for example, a child support obligation, such a system and method would allow for the collection of wage assignment orders for child support payments from state entities and, once collected, translate the wage assignment orders into an EDI file compatible with the X12 standard (e.g., the 521 record set), and then group the orders by recipient, and finally deliver a single EDI file to each respective recipient for processing. However, as described above, the current systems and methodologies reflect an unsatisfactory development of systems and methods to collect, translate, group, and deliver wage assignment information from an initiator of a wage assignment to a recipient. Of course, once the recipient obtains the wage assignment, the processing and implementation of the payment and disbursement occur using any known system or method. 
     For information on systems and methods for payment and disbursement processing generally, and for payment processing using debit-based EFT as well as for disbursement processing using addendum-based EDI specifically, see U.S. patent application Ser. No. 08/941,187 of John POLK, entitled “Method and Apparatus for Payment Processing Using Debit-based Electronic Funds Transfer and Disbursement Processing Using Addendum-based Electronic Data Interchange,” filed Sep. 30, 1997, incorporated herein by reference. U.S. patent application Ser. No. 08/941,187 provides efficient apparatus and methods for processing payments and disbursements, including wage assignments. However, U.S. patent application Ser. No. 08/941,187 does not provide a particular apparatus or method, whereby wage assignment information may be collected, translated, grouped, and delivered from an initiator to a recipient. 
     III. SUMMARY OF THE INVENTION 
     It is an object of an invention to provide a system for the collection, translation, grouping, and delivery of wage assignment information from an initiator to a recipient via an accumulator. 
     It is another object of an invention to provide a system for the receipt of wage assignment information at an initiator. 
     It is still another object of an invention to provide a system for the collection of wage assignment information at an accumulator from an initiator. 
     It is yet another object of an invention to provide a system whereby an accumulator may translate wage assignment information into an electronic wage assignment format. 
     It is also an object of an invention to provide a system whereby an accumulator may group electronic wage assignment information by batching the files for each respective recipient. 
     It is furthermore an object of an invention to provide a system whereby an accumulator may deliver the batched wage assignment information files to each respective recipient. 
     It is additionally an object of an invention to provide a system whereby a recipient may process wage assignments based on information received in a batched wage assignment information file. 
     To attain these and other objects, and in accordance with the purposes of the invention, as embodied and broadly described herein, one aspect of the invention includes a method consistent with the present invention that includes the steps, performed by a processor, of receiving a wage assignment at an initiator; dispatching the wage assignment from the initiator to an accumulator; processing the wage assignment at the accumulator; transmitting the wage assignment from the accumulator to a recipient; and implementing the wage assignment at the recipient. 
     In another aspect, the invention includes a method of processing a wage assignment at an initiator, comprising the steps, performed by a processor, of receiving a wage assignment; inputting the wage assignment into a database; and transmitting the wage assignment to an accumulator. 
     In yet another aspect, the invention includes a method of processing wage assignments at an accumulator, comprising the steps, performed by a processor, of collecting a plurality of wage assignments from a plurality of initiators; translating the wage assignments into files with a standard wage assignment format, the format including data in at least one data field; grouping the standard wage assignment format files into batch files based on the data stored in at least one data field of the standard wage assignment format; and delivering a batch file to each of a plurality of recipients. 
     In still another aspect, the invention includes a method of processing a wage assignment at a recipient, comprising the steps, performed by a processor, of receiving a wage assignment from an accumulator; processing the wage assignment; and implementing the wage assignment against a wage of an employee. 
     Additional aspects of the invention are disclosed and defined by the appended claims. It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory and are intended to provide further explanation of the invention as claimed. 
    
    
     
       IV. BRIEF DESCRIPTION OF THE DRAWINGS 
       The accompanying drawings are included to provide a further understanding of the invention, are incorporated in and constitute a part of this specification, illustrate preferred embodiments of the invention, and, together with the description, serve to explain the principles of the invention. 
       In the drawings, 
         FIG. 1  is a block diagram of a wage assignment collection and delivery system; 
         FIG. 2A  is a block diagram of an alternative wage assignment collection and delivery system; 
         FIG. 2B  is a block diagram of another alternative wage assignment collection and delivery system; 
         FIG. 3  is a flow diagram of a method for processing wage assignment information in a wage assignment collection and delivery system, as shown in  FIG. 1 ; 
         FIG. 4  is a block diagram of an initiator, as shown in  FIG. 1 ; 
         FIG. 5  is a block diagram of an accumulator, as shown in  FIG. 1 ; 
         FIG. 6  is a block diagram of the processing performed during collection by an accumulator, as shown in  FIG. 5 ; 
         FIG. 7  is a block diagram of the processing performed during translation by an accumulator, as shown in  FIG. 5 ; 
         FIG. 8  is a block diagram of the processing performed during grouping by an accumulator, as shown in  FIG. 5 ; 
         FIG. 9  is a block diagram of the processing performed during delivery by an accumulator, as shown in  FIG. 5 ; 
         FIG. 10  is a block diagram of a recipient, as shown in  FIG. 1 ; 
         FIG. 11  is a block diagram of a data processor at an initiator, as shown in  FIG. 4 ; 
         FIG. 12  is a block diagram of a data processor at an accumulator, as shown in  FIG. 5 ; 
         FIG. 13  is a block diagram of a data processor at a recipient, as shown in  FIG. 10 ; 
         FIGS. 14A-14B  depict a sample of an order/notice to withhold income for child support, as may be used by a wage assignment collection and delivery system, such as the system shown in  FIG. 1 ; 
         FIGS. 15A-15B  depict a sample of an order/notice to withhold income for child support containing data for purposes of illustration, as may be used by a wage assignment collection and delivery system, such as the system shown in  FIG. 1 ; 
         FIG. 16  is a sample of the contents of the wage assignment information database in the, data processor at the initiator shown in  FIG. 11 , using the illustrative data from  FIGS. 15A-15B ; 
         FIG. 17  is a sample of the contents of the wage assignment information database in the data processor at the accumulator shown in  FIG. 2 , using the illustrative data from  FIGS. 5A-15B ; 
         FIG. 18  is a sample of the contents of the wage assignment information file database in the data processor at the accumulator shown in  FIG. 12 , using the illustrative data from  FIGS. 5A-15B  as well as other illustrative data; 
         FIGS. 19A-19B  depict a sample of an order/notice to withhold income for child support containing field identifiers for purposes of illustrating mapping rules;  FIGS. 19C-19F  are samples of mapping rules corresponding to FIGS.  19 -A 19 B, such as mapping rules that would appear in the mapping rules database in the data processor at the accumulator shown in  FIG. 12 ; 
         FIG. 20  is a sample of the contents of the EDI wage assignment information file database in the data processor at the accumulator shown in  FIG. 12 , using the illustrative data from  FIGS. 15A-15B  as well as other illustrative data; 
         FIG. 21  is a sample of the contents of the EDI batch file database in the data processor at the accumulator shown in  FIG. 12 , using the illustrative data from  FIGS. 15A-15B  as well as other illustrative data; 
         FIG. 22  is a sample of the contents of the recipient delivery database in the data processor at the accumulator shown in  FIG. 12 , containing data corresponding to illustrative parameters for an exemplary recipient delivery database; 
         FIG. 23  is a sample of the contents of a single EDI file from the EDI batch file database corresponding to a single recipient from the recipient delivery database in the data processor at the accumulator shown in  FIG. 12 , containing illustrative data for delivery to an illustrative recipient; 
         FIG. 24  is a sample of the contents of the EDI file database in the data processor at the recipient shown in  FIG. 13 , containing illustrative data for a single illustrative recipient; 
         FIG. 25  is a flow diagram of a method for processing wage assignment information in a wage assignment collection and delivery system, in accordance with one embodiment of the invention, as shown in  FIG. 1 ; 
         FIG. 26  is a flow diagram of a method for processing wage assignment information at an initiator, in accordance with one embodiment of the invention, as shown in  FIG. 25 ; 
         FIG. 27  is a flow diagram of a method for processing wage assignment information at an accumulator, in accordance with one embodiment of the invention, as shown in  FIG. 25 ; 
         FIG. 28  is a flow diagram of a method for processing wage assignment information at a recipient, in accordance with one embodiment of the invention, as shown in  FIG. 25 ; 
         FIG. 29  is a flow diagram of a method for processing wage assignment information in a wage assignment collection and delivery system, in accordance with an alternative embodiment of the invention, as shown in  FIG. 2B ; 
         FIG. 30  is a flow diagram of a method for processing wage assignment information at an initiator, in accordance with an alternative embodiment of the invention, as shown in  FIG. 29 ; 
         FIG. 31  is a flow diagram of a method for processing wage assignment information at an accumulator, in accordance with an alternative embodiment of the invention, as shown in  FIG. 29 ; 
         FIG. 32  is a flow diagram of a method for processing wage assignment information at a recipient, in accordance with an alternative embodiment of the invention, as shown in  FIG. 29 . 
     
    
    
     V. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS 
     A preferred embodiment of this invention, known as NEWWS™ (National Employer Wage Withholding Service), is presently marketed by Lockheed Martin IMS. The scope of the present invention, however, encompasses modifications and variations as described by the methods and apparatus described herein or as contained within the scope of, the listed claims and their equivalents. 
     A. Introduction 
     The system of a preferred embodiment of the invention avoids the inefficiencies and shortcomings of the present wage assignment systems and methodologies by providing for the electronic collection, translation, grouping, and delivery of wage assignment information. Systems consistent with the present invention include receiving wage assignment information at an initiator regarding a wage assignment. The initiator gathers the wage assignment information and transmits the information to an accumulator. The accumulator collects the wage assignment information and then translates the information into an electronic format, such as an electronic file that corresponds to the public EDI standard established by the X12 standard. After translation, the accumulator then batches the electronic files based on a field in the electronic format. The accumulator then delivers a single batch file to each recipient. Upon receipt of a batch file, a recipient then processes the wage assignment and implements a funds or asset transfer in any known manner. 
     A preferred system consistent with the invention comprises several components, including a plurality of initiators, an accumulator, and a plurality of recipients. Each initiator receives and processes wage assignment information for various individuals. The initiators store and maintain the wage assignment information in a database and periodically transmit the database to an accumulator. The accumulator serves as a processing station (also known as a Value Added Network, or VAN) between the plurality of initiators and the plurality of recipients. In particular, the accumulator collects wage assignment information from each of the plurality of initiators and ensures that the information from each initiator is valid. The accumulator then translates the wage assignment information into a standard format, for example, into an EDI file, such as the 521 record set. The accumulator then batches the EDI files according to the recipient indicated in the EDI file and delivers a single EDI file to each of the plurality of recipients. The recipient processes and implements the wage assignment through any of several known methods. For an example of the implementation of a wage assignment, refer to U.S. patent application Ser. No. 08/941,187. 
     B. System 
       FIG. 1  shows a wage assignment collection and delivery system according to one embodiment of the present invention. System  100  includes a plurality of initiators  110   1-n , an accumulator  120 , and a plurality of recipients  130   1-m . Initiators  110   1-n  may represent any entity that initiates a wage assignment. Accumulator  120  is the processing station that receives wage assignments from initiator  110   1-n , processes the wage assignments, and then transmits the wage assignments to recipients  130   1-m . Recipients  130   1-m  entail those entities that receive and implement wage assignments. 
       FIG. 2A  shows a wage assignment collection and delivery system according to an alternative embodiment of the present invention. System  200  includes a plurality of agencies  210   1-n , an accumulator  220 , and a plurality of employers  230   1-m . In this embodiment, the plurality of agencies  110   1-n  are agencies that may initiate a wage assignment, and the plurality of employers  230   1-m  are the employers that may receive and implement wage assignments. Similar to  FIG. 1 , accumulator  120  in  FIG. 2A  is the processing station that receives wage assignments from agencies  210   1-n , processes the wage assignments, and then transmits the wage assignments to employers  230   1-m . 
       FIG. 2B  shows a wage assignment collection and delivery system according to another alternative embodiment of the present invention. System  205  includes a plurality of states  215   1-n , an accumulator  220 , and a plurality of employers  235   1-m . In this embodiment, the plurality of states  215   1-n  are states or state entities that may initiate a wage assignment, and the plurality of employers  235   1-m  are the employers that may receive and implement wage assignments. Similar to  FIG. 1  and  FIG. 2A , accumulator  120  in  FIG. 2B  is the processing station that receives wage assignments from states  215   1-n , processes the wage assignments, and then transmits the wage assignments to employees  235   1-m . In a preferred embodiment of the system shown in  FIG. 2B , the plurality of states  215   1-n  are state agencies that initiate Child Support Orders requiring wage assignments for noncustodial parents, and the plurality of employers  235   1-m  are the employers of the noncustodial parents subject to the wage assignments pursuant to the Child Support Orders. 
     C. Process 
       FIG. 3  is a flow chart  300  illustrating the operation of a system  100  as shown in  FIG. 1 . As shown in  FIG. 3 , each initiator  110  inputs wage assignment information containing a wage assignment into a database that each initiator maintains separately (step  310 ). After the wage assignment information is input into the database, each initiator  110  transmits, such as, in a periodic batch of ASCII files, the wage assignment information stored in the database to accumulator  120  (step  320 ). Accumulator  120  then collects all the wage assignment information from all initiators  110 (step  325 ). Accumulator  120  next translates the wage assignment information into an electronic format, which preferably comprises an EDI file using the 521 record set (step  330 ). After accumulator  120  creates the EDI files, they are initially organized based on the initiator. After the translation, however, accumulator  120  reorganizes the wage assignment files based on one of the data fields, such as, for example, element BPR10 of the 521 record set, which indicates the company initiating the funds transfer (i.e., employer). During this grouping (or batching), a batch of EDI files are created, preferably so that each EDI file is batched based on the employer (step  340 ). Accumulator  120  then delivers the batched EDI files to each of the plurality of recipients  130  (step  350 ). The delivery medium that accumulator  120  uses to deliver the batched EDI files to each of the plurality of recipients  130  depends on the capability of each recipient. For example, accumulator  120  may transmit an EDI file electronically to the most sophisticated recipients  130 , while other recipients  130  may access a web page bulletin board (not shown) that is maintained by accumulator  120 , while still other recipients  130  may receive the files via facsimile, and while still other recipients  130  may receive their files by mail. Whatever the delivery means, once received, each of the plurality of recipients  130  then processes the wage assignment and initiates a funds transfer through any known manner (step  360 ). Notably, a detailed description of the methods of operation of systems consistent with the operation of this system are provided in  FIGS. 25-32 . 
     D. Components 
       FIG. 4  illustrates one representative embodiment of an initiator  110  shown in  FIG. 1 . As shown in  FIG. 4 , initiator  110  includes input station  405 , data processor  410 , and transmission means  420 . Input station  405  provides for the input of wage assignments into a database at initiator  110 . Input station  405  may include either manual or electronic means for inputting wage assignments into a wage assignment information database. Input station  405  may also include an optical character reader (OCR). Data processor  410  contains the database created by input station  405 . Similarly, data processor  410  provides for the periodic transmission of the contents of the wage assignment information database to accumulator  120  via transmission means  420 . Although data processor  410  preferably transmits the contents of the database electronically, initiator  110  may also transmit the database by other means, including by manual means. Thus, transmission means  420  includes both electronic and non-electronic means by transmission. A detailed description of data processor  410  is provided in  FIG. 11 . 
       FIG. 5  illustrates one representative embodiment of accumulator  120  shown in  FIG. 1 . As shown in  FIG. 5 , accumulator  120  includes data processor  505 , collection processing  510 , translation processing  520 , grouping processing  530 , and delivery processing  540 . After initiator  110  transmits a wage assignment to accumulator  120 , data processor  505  at accumulator  120  collects the wage assignment during collection processing  510 . Collection processing  510  includes the collection of a plurality of wage assignment information from a plurality of initiators  110 . Generally, the plurality of initiators  110  transmits a plurality of wage assignment information to accumulator  120  in the form of ASCII format. Thereafter, translation processing  520  converts the wage assignment information into a standardized electronic format such as, for example, an EDI file using the X12 standard. Grouping processing  530  then batches the EDI files based on one data field from the EDI file. Preferably, the data field on which the batching occurs is the data field for the recipient. In this manner, grouping processing  530  batches the EDI files based on the recipient. Delivery processing  540  then delivers a single EDI file to each of a plurality of recipients  130 . Notably, although delivery processing preferably occurs by electronic means, delivery processing  540  may take place by electronic, manual, or other means. Nonetheless, as noted above, in a preferred implementation, the EDI files are batched based on recipient, and therefore, delivery processing  540  dispatches a single EDI file from accumulator  120  to each of a plurality of recipients  130 . A detailed description of data processor  505  is provided in  FIG. 12 . 
       FIG. 6  illustrates one representative embodiment of collection processing  510  shown in  FIG. 5 . As shown in  FIG. 6 , collection processing  510  includes a plurality of wage assignment information  610   1-n  and wage assignment information file  620 . Wage assignment information  610   1-n , which are shown in  FIG. 6  as wage assignment information  610   1 , wage assignment information  610   2 , wage assignment information  610   n , is representative of the plurality of wage assignments received from a plurality of initiators  110 . As shown in  FIG. 6 , the plurality of wage assignment information  610   1-n , are collected by accumulator  120  and placed in wage assignment information file  620 . Generally, the plurality of wage assignment information  610   1-n  are in the ASCII format. Wage assignment information file  620  is simply a database containing the plurality of wage assignment information  610   1-n . 
       FIG. 7  illustrates one representative embodiment of translation processing  520  shown in  FIG. 5 . As shown in  FIG. 7 , translation processing  520  includes wage assignment information file  620 , map processing  710 , mapping rules  715 , and EDI wage assignment information file  720 . In translation processing  520 , as shown in  FIG. 7 , wage assignment information file  620  is subject to map processing  710 . In map processing  710 , mapping rules  715  are applied to the contents of wage assignment information file  620 . In a preferred implementation, mapping rules  715  contain the mapping rules for the 521 record set of the X12 standard. Thus, in this preferred implementation, each wage assignment information in wage assignment information file  620  is translated into an EDI format pursuant to mapping rules  715  by map processing  710 . Following map processing  710 , each wage assignment information contained in wage assignment information file  620  has been translated into an electronic file, preferably an EDI file. These EDI files are then recorded in EDI wage assignment information file  720 . 
       FIG. 8  illustrates one representative embodiment of grouping processing  530  shown in  FIG. 5 . As shown in  FIG. 8 , grouping processing  530  includes a plurality of wage assignment information as EDI files, including wage assignment information as EDI file (for Recipient 1 )  810 , wage assignment information as EDI file (for Recipient 2 )  815 , wage assignment information as EDI file (for Recipient 1 )  820 , and wage assignment information as EDI file (for Recipient n )  825 . Grouping processing  530  also includes batch processing  830 , and a plurality of EDI batch files for recipients, including EDI batch file for Recipient 1    840 , EDI batch file for Recipient 2    850 , and EDI batch file for Recipient n    860 .  FIG. 8  contains examples showing the operation of batch processing  830 , which references both the plurality of wage assignment information as EDI files and the plurality of EDI batch files for recipients. These examples are based on references to Recipient 1  and Recipient 2  as well as Recipient n . 
     As shown in  FIG. 8 , wage assignment information as EDI file (for Recipient 1 )  810  and wage assignment information as EDI file (for Recipient 1 )  820  are two EDI files for Recipient 1 . Wage assignment information as EDI file (for Recipient 2 )  815  is a single EDI file for Recipient 2 . Wage assignment information as EDI file (for Recipient n )  825  shows that an unlimited number of other EDI files may be available for an unlimited number of other recipients. During grouping processing  530 , batch processing  830  batches the EDI files based on one data field from the EDI file. A described above, in a preferred implementation, batch processing  830  utilizes the recipient field from the EDI file (e.g., element BPR10 of the 521 record set) as the field for purposes of batch processing  830 .  FIG. 8  depicts batch processing based upon this preferred implementation. Thus, as shown in  FIG. 8 , EDI batch file for Recipient,  840  shows wage assignment information as EDI file (for Recipient 1 )  810  and wage assignment information as EDI file (for Recipient 1 )  820  as batched in a single EDI batch file for Recipient 1 . Similarly, EDI batch file for Recipient 2    850  contains wage assignment information as EDI file (for Recipient 2 )  815  as a single batch file for Recipient 2 . These examples for Recipient, and Recipient 2  would be implemented similarly for a plurality of other Recipients, such as, for example, Recipient n . Thus, as shown in EDI batch file for Recipient n    860 , wage assignment information as EDI file (for Recipient n )  825  would be contained in a single batch file for Recipient n . 
       FIG. 9  illustrates one representative embodiment of delivery processing  540  shown in  FIG. 5 . As shown in  FIG. 9 , delivery processing  540  includes wage assignment EDI batch file for Recipient x    910 , delivery  920 , FTP  930 , Internet  940 , tape  950 , diskette  960 , and Recipient x    970 . Delivery processing  540  takes an EDI batch file containing wage assignment information for Recipient x    910  and implements delivery  920 . Delivery  920  entails the delivery of the EDI batch file to a recipient  130 , i.e., Recipient,  970 . Delivery  920  may take place by one of several methods, such as, for example, FTP  930 , Internet  940 , a tape  950 , and diskette  960 . Other delivery methods are also available (not shown). Whatever method utilized by delivery  920 , the wage assignment EDI batch file for Recipient x    910  is delivered to Recipient x    970 . In a preferred implementation, delivery processing  540  contains a database indicating the preferred method of delivery for each of a plurality of recipients, such as, Recipient x    970 . A detailed description of the database indicating the preferred method of delivery is provided in  FIG. 22 . 
       FIG. 10  illustrates one representative embodiment of recipient  130  shown in  FIG. 1 . As shown in  FIG. 10 , recipient  130  includes transmission means  1005 , data processor  1010 , payroll department  1020 , and wage assignment  1030 . Recipient  130  receives wage assignment information from accumulator  120  via transmission means  1005 . As described above, in a preferred implementation, transmission means  1005  receives an EDI file containing wage assignment information electronically. However, recipient  130  may also receive wage assignment information via transmission means  1005  in other forms, such as, for example, diskette. Whatever the form, once recipient  130  receives the wage assignment information, the wage assignment information is recorded in data processor  1010 . Recipient  130  then processes the wage assignment in data processor  1010 , which includes informing payroll department  1020  of the wage assignment. Note that payroll department  1020  may include any implementation of the wage assignment, manual or electronic. Payroll department  1020  then implements wage assignment  1030 . In implementing wage assignment  1030 , payroll department offsets or withholds a portion of the salary of the employee subject to the wage assignment. Such payment and disbursement processing may occur by any known system or method. A detailed description of data processor  1010  is provided at  FIG. 13 . 
       FIG. 11  illustrates one representative embodiment of data processor  410  shown in  FIG. 4 , in a wage assignment collection and delivery system as shown in  FIG. 1 . As shown in  FIG. 11 , data processor  410  at initiator  110  preferably includes one or more data processors  1100  equipped with conventional hardware and having operating software to support a central processing unit (“CPU”)  1110 , a random access memory (“RAM”)  1120 , a monitor  1130 , an input/output (I/O) controller  1140 , a data storage device (disk)  1150 , an input device  1160 , and an output device  1170 . Although not depicted, processing station  300  is also capable of supporting peripheral equipment, such as, for example, scanners, printers, modems, etc., in conventional manners. 
     As shown in  FIG. 11 , CPU  1110  is directly coupled to each of RAM  1120 , I/O controller  1140 , and disk  1150 . CPU  1110  operates by accessing RAM  1120  and disk  1150  in any conventional manner to execute program code (not shown) stored in at least one of RAM  1120  and disk  1150  to carry out the functions and acts described in connection with the operation of processing station  1100 . CPU  1110  preferably comprises at least one high-speed digital data processor adequate to execute program modules consistent with the invention, such as the accumulation, processing, storage, and transmission of wage assignment information. 
     In one embodiment, processing station  1100  shown in  FIG. 11  located at an initiator  110 , such as, for example, a state child support department, operates to collect wage assignment information from persons, such as, for example, persons subject to mandatory child support payments. In such an example, a case worker at a state child support department inputs data at input device  1160  regarding a noncustodial parent who is subject to a Child Support Order. Data input at input device  1160  is received at CPU  1110  through I/O controller  1140  and stored in wage assignment information database  1152 , which is stored in disk  1150 . Preferably, processing station  1100  periodically transmits a batch of files through output device  1170  containing the wage assignment information stored in wage assignment information database  1152  to accumulator  120  as shown in  FIG. 1 . Although it is preferable to transmit the database as a batch of files, processing station  1100  could transmit the wage assignment information to accumulator  120  using other equivalent electronic means, such as E-mail, Internet bulletin boards, etc., or non-electronic means, such as Federal Express and the U.S. Postal Service. In the case of non-electronic means, processing station  1100  would either transmit a printout of the database or download the database onto a disk and transmit the disk to accumulator  120 . Once the non-electronic information arrived at accumulator  120 , the wage assignment information would then need to be manually input into the data processor at accumulator  120 . 
     As shown in  FIG. 11 , disc  1150  preferably comprises a large capacity memory capable of maintaining wage assignment information database  1152 . Wage assignment information database  1152  contains data corresponding to a wage assignment, such as, for example, a Child Support Order. Wage assignment information database  1152  can be structured in many forms and typically includes informational fields for the name of the originating state, the name of the originating jurisdiction, the date, and employer identification (which is normally the employer&#39;s Federal Tax Identification Number), the employer name, the employer address, the name of the custodial parent, the social security number of the non-custodial parent, the name of a custodial parent, the ordered termination date (which indicates when the child support is no longer mandatory), the dollar amount, etc. Data contained in wage assignment database  1152  may be periodically obtained and updated from input device  1160 . Samples of the records and the respective fields contained in wage assignment information database  1152  is shown in and described in connection with  FIG. 16 . 
       FIG. 12  illustrates one representative embodiment of data processor  505  shown in  FIG. 5 , in a wage assignment collection and delivery system as shown in  FIG. 1 . As shown in  FIG. 12 , accumulator  120  preferably includes one or more processing stations  1200 , which could be a conventional personal computer, mainframe, or equivalent, each equipped with conventional hardware and having operating software to support a central processing unit (“CPU”)  1210 , a random access memory (“RAM”)  1220 , a monitor  1230 , an input/output (I/O) controller  1240 , a data storage device (disk)  1250 , an input device  1260 , and an output device  1270 . Although not depicted, processing station  1200  is also capable of supporting peripheral equipment such as scanners, printers, modems, etc., in conventional manners. 
     As shown in  FIG. 12 , CPU  1210  is directly coupled to each of RAM  1220 , I/O controller  1240 , and disk  1250 . CPU  1210  operates by accessing RAM  1220  and disk  1250  in any conventional manner to execute program code (not shown) stored in at least one of RAM  1220  and disk  1250  to carry out the functions and acts described in connection with the operation of processing station  1200 . CPU  1210  preferably comprises at least one high-speed digital data processor adequate to execute program modules consistent with the invention, such as the accumulation, transmission, organization, processing, and storage operations as well as the collection, translation, grouping, and delivery of wage assignment information. 
     In one embodiment, processing station  1200  receives wage assignment information at periodic intervals through input device  1260 . In a preferred embodiment, processing station  1200  receives wage assignment information at periodic intervals through input device  1260  in the form of electronic files containing the data relating to Child Support Orders from a plurality of states  215 , as shown in  FIG. 2B . CPU  1210  then temporally stores either the wage assignment information or the wage assignment information file in wage assignment information database  1252  or in wage assignment information file database  1253 , both of which are stored in disk  1250 . If the wage assignment information is not formatted in a file, CPU  1210  initially stores the wage assignment information in wage assignment information database  1252  and then converts the wage assignment information into a wage assignment file and stores the file in wage assignment information file database  1253 . However, if the wage assignment information is initially formatted in a file, then CPU  1210  stores the wage assignment information directly in wage assignment information file database  1253 . Next, preferably, CPU  1210  translates the files in wage assignment information file  1253  into an EDI compatible file according to the ANSI X12 standard, specifically in the 521 record set, and these EDI files are then placed in EDI wage assignment file information file database  1254 , which is stored in disk  1250 . In order to translate the files into an EDI file, CPU  1210  accesses a rules database, such as a mapping rules database  1251 , which is stored in disk  1250 . Mapping rules database  1251  contains the codes needed by CPU  1210  to translate a file received from an initiator into an electronic file, preferably into an EDI file corresponding to the 521 record set. After translation, processing station  1200  then batches the EDI files in a database, such as EDI batch file database  1255 , which is stored in disk  1250 . In a preferred implementation, CPU  1210  batches the EDI files together based on a field containing information about the employer of the noncustodial parent (for example, element BPR10 of the 521 record set). In this implementation, CPU  1210  gathers all EDI files that indicate the same employer, regardless of the state of jurisdiction of origin, and batches those EDI files together in a single batched EDI file. Thereafter, CPU  1210  delivers the batched EDI file through output device  1270  to a recipient  130  on a periodic basis, which corresponds to the indicated recipient among the plurality of recipients  130 . 
     Notably, in the preferred embodiment discussed above, while it is preferable to send a batched EDI file to an indicated employer, the indicated employer may not be capable of electronically receiving EDI files for processing. To account for this possibility, processing station  1200  has a recipient delivery database  1257 , which is stored in disk  1250 . Prior to transmitting a batched EDI file to an indicated employer, CPU  1210  accesses recipient rules database  1257 . If recipient rules database  1257  indicates that the indicated employer can receive EDI file, then the EDI file is transmitted to the indicated employer electronically. Otherwise, CPU  1210  transmits the EDI file (i.e., preferably containing a batch file of one or more EDI files using the 521 record set) to the indicated employer through output device  470  by any transmission medium. In other words, the EDI file may even be sent through E-mail, facsimile transmission, or even the mail. As a further alternative to transmitting the files to the employer, CPU  1210  could transmit the EDI file via output device  1270  to a Web page or bulletin board (not shown). The indicated employer would receive the EDI file by accessing the Web page or bulletin board and then downloading the batched files. These alternative methods would use any conventional Internet server or computer system, access protocols, uploading protocols, downloading protocols, and security protocols. Data contained in one or more of these databases  1251 ,  1252 ,  1253 ,  1254 ,  1255 , and  1257  may be periodically obtained and updated from input device  1260 . Samples of the records and the respective fields contained in databases  1251 ,  1252 ,  1253 ,  1254 ,  1255 , and  1257  are shown in and described in connection with  FIGS. 17-23 . 
       FIG. 13  illustrates one representative embodiment of data processor  1010  shown in  FIG. 10 , in a wage assignment collection and delivery system as shown in  FIG. 1 . As shown in  FIG. 13 , each recipient  130  preferably includes one or more processing stations  1300 , which could be a conventional personal computer, mainframe, or equivalent, each equipped with conventional hardware and having operating software to support a central processing unit (“CPU”)  1310 , a random access memory (“RAM”)  1320 , a monitor  1330 , an input/output (I/O) controller  1340 , a data storage device (disk)  1350 , an input device  1360 , and an output device  1370 . Although not depicted, processing station  1300  is capable of supporting peripheral equipment such as scanners, printers, modems, etc., in conventional manners. 
     As shown in  FIG. 13 , CPU  1310  is directly coupled to each of RAM  1320 , I/O controller  1340 , and disk  1350 . CPU  1310  operates by accessing RAM  1320  and disk  1350  in any conventional manner to execute program code (not shown) stored in at least one of RAM  1320  and disk  1350  to carry out the functions and acts described in connection with the operation of processing station  1300 . CPU  1310  preferably comprises at least one high-speed digital data processor adequate to execute program modules consistent with the invention, such as the accumulation, storage, and processing of wage assignment information and the implementation of wage assignments. 
     In a preferred embodiment, processor station  1300  receives wage assignment information transmitted from accumulator  120  through an electronic medium by inputting an EDI file directly into CPU  1310  through input device  1360 . Data input at input device  1360  is received at CPU  1310  through I/O controller  1340  and stored in EDI file database  1352 , which is stored in disk  1350 . Other embodiments, however, include downloading the wage assignment information from an Internet bulletin board, from E-mail, or inputting the wage assignment information manually. Whatever the means of transmission of wage assignment information, in a preferred implementation, recipient  130  is the employer of the noncustodial parent subject to a wage assignment, and that assignment is then implemented in a manner as described in U.S. patent application Ser. No. 08/941,187. Recipient  130 , however, can process the wage assignment in any manner currently known in the art. Regardless of the manner of implementation, the data contained in database  1352  may be periodically obtained and updated from input device  1360 . Samples of the records and the respective fields contained in database  1352  is shown in and described in connection with  FIG. 24 . 
     E. Database Formats 
     In  FIGS. 11-13 , a number of databases are referenced with respect to the wage assignment collection and delivery systems shown in  FIG. 1  and  FIG. 2B . The following paragraphs describe these databases, but for purposes of illustration, these databases are depicted containing sample data. In fact, the samples of the contents of wage assignment information database  1152 , mapping rules database  1251 , wage assignment information database  1252 , wage assignment information file database  1253 , EDI wage assignment information file database  1254 , EDI batch file database  1255 , recipient delivery database  1257 , and EDI file database  1352  are shown in  FIGS. 16-24 . The specific data and fields illustrated in these figures represent only one possible embodiment of a type of record that can be stored in the databases. For purposes of illustration, the record depicted is that of the preferred embodiment, i.e., the 521 record set of the X12 standard. Therefore, in most cases, the fields shown in  FIGS. 16-24  are relatively straight-forward and self-explanatory. However, note that, in addition to the disclosed databases, the data and fields of these databases, as well as the number of databases, can be readily modified from the described embodiments, for example, to include more or fewer data fields or different or additional records. 
       FIG. 14A-14B  depict a sample of an order/notice to withhold income for child support, i.e., a Child Support Order. As shown in  FIG. 14A-14B , the Child Support Order contains a plethora of information relating to a wage assignment for purposes of a child support obligation. Nonetheless, the form depicted in  FIGS. 14A-14B  is a standard Child Support Order, as used by judicial entities and implemented by state agencies. For that reason, the form depicted in  FIGS. 14A-14B  is hereby incorporated by reference as well as reproduced for purposes of reference in  FIGS. 14A-14B . For the following descriptions,  FIGS. 14A-14B  are used as a reference for purposes of providing a working example of the databases in the wage assignment collection and delivery systems shown in  FIG. 1  and  FIG. 2B . 
       FIGS. 15A-15B  depict a sample of a Child Support Order containing sample data for purposes of illustration. This sample data will be used as the sample content for the databases described in  FIGS. 16-24 . As shown in  FIGS. 15A-15B , the sample Child Support Order has been issued in the State of Virginia by a court in Alexandria, with a order date of Jun. 12, 1998 and a court number of 98-123. The sample order is directed to the employer of John J. Doe which is Y Corp., located at 123 Main Street, Anytown, Va. 12345-00000. As shown in the Child Support Order, the social security number of John Doe is 123-45-6789, the case identifier is 98-123, and the custodial parent is Jane Doe. Furthermore, as also shown in this sample Child Support Order, the child&#39;s name is Susie Doe, who has a date of birth of Jun. 1, 1990. As stated in the sample order, the Child Support Order pertains to an employer in the State of Virginia, and the order requires a wage assignment against the wages of John Doe at Y Corp. until Jun. 1, 2008. Under the terms of the sample Child Support Order, $800.00 a month is required in child support, and $100.00 a month is required in medical support; thus a total of $900.00 a month is required for the wage assignment. The foregoing information from the sample Child Support Order is used for purposes of illustration in  FIGS. 16-24 . 
       FIG. 16  illustrates a sample of the contents of wage assignment information database  1152  in data processor  410  at initiator  110  as shown in  FIG. 11 , using sample information in a preferred implementation of a wage assignment collection and delivery system. Wage assignment information database  1152 , contains a listing of the information relating to a wage assignment, such as the information contained in a Child Support Order, such as, for example, sample order  1500 , as depicted in  FIGS. 15A-15B . As shown in  FIG. 16 , wage assignment information database  1152  contains 8 numbered fields but provides for an unlimited number of additional fields. As also shown in  FIG. 16 , a wage assignment may contain various types of information, which are recorded in wage assignment information database  1152 . The wage assignment information in wage assignment information database  1152  may be recorded in any order. 
       FIG. 17  illustrates a sample of the contents of wage assignment information database  1252  in data processor  505  at accumulator  120  as shown in  FIG. 12 , using sample information in a preferred implementation of a wage assignment collection and delivery system. Wage assignment information database  1252  contains the same information as wage assignment information database  1152 . Essentially, initiator  110  transmits the contents of wage assignment information database  1152  to accumulator  120 . Following such transmission, accumulator  120  initially records the information received from initiator  110  in wage assignment information database  1252 . Wage assignment information database  1252  is thus a temporary database at accumulator  120 . 
       FIG. 18  illustrates a sample of the contents of wage assignment information file database  1253  in data processor  505  at accumulator  120  as shown in  FIG. 12 , using sample information in a preferred implementation of a wage assignment collection and delivery system. As shown in  FIG. 18 , wage assignment information file database  1253  contains nine fields but allows for an unlimited number of additional fields. In one implementation, field  1  identifies initiator  110 . Thus, as shown in  FIG. 18 , field  1  shows two initiators, labeled I 1  and I 2 . For I 1 , there is one file in wage assignment information file database  1253 , and for I 2  there are two files in wage assignment information file database  1253 . Significantly, as shown in  FIG. 18 , the order of the information in each field need not be standardized for purposes of wage assignment information file database  1253 . 
       FIGS. 19A-19F  illustrate a sample of the form and contents of mapping rules database  1251  in data processor  505  at accumulator  120  as shown in  FIG. 12 , using a sample mapping form and sample mapping rules for a preferred implementation of a wage assignment collection and delivery system.  FIGS. 19A-19B  demonstrate how a mapping database may be created for purposes of map processing.  FIGS. 19A-19B  depict the same Child Support Order of  FIGS. 14A-14B , except that each entry possibility has a mapping field.  FIGS. 19A-19B  show these mapping fields as fields  1   a - 36   d . Correspondingly,  FIGS. 19C-19F  depict a table containing the mapping fields of the Child Support Order shown in  FIGS. 19A-19B . In a preferred implementation, as depicted in  FIGS. 19C-19F , the mapping fields correspond to the 521 record set. Thus, in this preferred implementation, the fields of the 521 record set correspond to the fields of mapping rules database  1251 . Thus, when the wage assignment collection and delivery system translates a wage assignment to an EDI file format, as in the above-described preferred embodiment, mapping rules database  1251  contains records having fields corresponding to, for example, the fields identified in  FIGS. 19C-19F . 
       FIG. 20  illustrates a sample of the contents of EDI wage assignment information file database  1254  in data processor  505  at accumulator  120  as shown in  FIG. 12 , using sample information in a wage assignment collection and delivery system. In a preferred implementation, using mapping rules database  1251 , data processor  505  at accumulator  120  maps the information contained in wage assignment information file database  1253  to an EDI format, according to the fields set forth in mapping rules database  1251 . In this manner, the information in wage assignment information file database  1253  is placed in fields corresponding to the mapping rules of mapping rules database  1251 . As noted above, in a preferred implementation, mapping rules database  1251  contains the mapping rules for the 521 record set. Once this mapping occurs, the files are placed in EDI wage assignment information file database  1254 , as shown in  FIG. 20 . Thus, in this preferred implementation, using mapping rules database  1251 , each wage assignment is mapped to the proper field for the 521 record set. As shown in  FIG. 20 , fields  1   a - 36   d  contain these fields of the 521 record set, which correspond to the table shown in  FIGS. 19C-19F . Thus, as shown in  FIGS. 19C-19F  and  FIG. 20 , and using the mapping rules from mapping rules database  1251 , field  1   a  corresponds to the name of the state, field  1   b  corresponds to the name of the jurisdiction, field  2  corresponds to the date of the order, field  3  corresponds to the identifying number of the court, field  6   a  corresponds to the withholder&#39;s name, field  36   d  corresponds to the facsimile number for the person named in field  36   a , etc. In  FIG. 20 , these fields are delineated as rows. In  FIG. 20 , the columns pertain to the plurality of initiators  110 , labeled I 1 , I 2 , I 3 , etc. 
       FIG. 21  illustrates a sample of the contents of EDI batch file database  1255  in data processor  505  at accumulator  120  as shown in  FIG. 12 , using sample information in a wage assignment collection and delivery system. As shown in  FIG. 21 , in a preferred implementation, EDI batch file database  1255  contains records having fields with identifiers corresponding to, for example, fields corresponding to the 521 record set. Thus, EDI batch file database  1255  is similar to EDI wage assignment information file database  1254 . However, EDI batch file database  1255  contains EDI files that are batched by a particular field, such as, for example, one field from the 521 record set. In a preferred implementation, EDI batch file database  1255  contains EDI files that are batched on the recipient field (i.e., field BPR10 of the 521 record set). Thus, in this preferred implementation, as shown in  FIG. 21 , EDI batch file database  1255  contains EDI files, which are batched on the recipient. 
       FIG. 22  illustrates a sample of the contents of recipient delivery database  1257  in data processor  505  at accumulator  120  as shown in  FIG. 12 , containing sample information for a wage assignment collection and delivery system. As shown in  FIG. 22 , a plurality of recipients  130  may accept the transmittal of EDI files by a number of methods, including, but not limited to, FTP, Internet, tape, and diskette. In a preferred implementation, recipient delivery database  1257  contains the methods of delivery for EDI files from an accumulator  120  to a plurality of recipients  130 . As shown in  FIG. 22 , for example, X Corp. accepts the transmittal of EDI files via FTP and diskette but not via Internet or tape. Similarly, Y Corp. accepts the transmittal of EDI files via tape but not via FTP, Internet, or diskette. Once accumulator  120  has determined the proper means of transmittal, the batched EDI file for a particular recipient  130  is removed from EDI batch file database  1255  and transmitted in the manner indicated by recipient delivery database  1257 . Notably, as shown in  FIG. 22 , an unlimited number of delivery methods are possible. 
       FIG. 23  does not depict any database but does illustrate a sample of an EDI file transmittal from data processor  505  at accumulator  120  as shown in  FIG. 12 , using sample information in a preferred implementation of a wage assignment collection and delivery system. As shown in  FIG. 23 , EDI batch file database  1255  contained two EDI files for one particular recipient  130  (i.e., Y Corp.) from a plurality of recipients  130 . As shown in this example, recipient  130  is Y Corp., and EDI batch file database  1255  contained two EDI files for Y Corp. within the EDI batch file. Thus, when accumulator  120  delivers the EDI batch file to this recipient, the transmittal of the EDI batch file will include two EDI files. Notably, because this recipient accepts EDI files via FDP or diskette, as indicated in the recipient delivery database  1257  as shown in  FIG. 22 , the transmittal of the EDI batch file shown in  FIG. 23  may take place by either of these two methods. 
       FIG. 24  illustrates a sample of the contents of EDI file database  1352  from data processor  1010  at recipient  130  as shown in  FIG. 13 , using the sample information for a preferred implementation of a wage assignment collection and delivery system. As shown in  FIG. 24 , the contents of EDI file database  1352  is the same as that transmitted from accumulator  120 , as shown by the EDI batch file described in  FIG. 23 . Notably, however, depending on the method of delivery to recipient  110 , EDI file database  1352  may accept the information from accumulator  120  by any known delivery method, as indicated by recipient delivery database  1257  shown in  FIG. 22 . 
     F. Methods of Operation 
     As shown in  FIG. 3 , in processing a wage assignment from initiator  110  to recipient  130  via accumulator  120 , the system shown and described in connection with  FIG. 1  entails several distinct methods of operation. These methods include the processes that take place at initiator  110 , the processes that take place at accumulator  120 , and the processes that take place at recipient  130 . The steps associated with these processes are described in connection with  FIGS. 25-32  and can be performed in any order, unless otherwise specified or dictated by the steps themselves. 
     In describing the processes consistent with the possible implementations of a system as shown and described in connection with  FIGS. 1 and 2B , alternative implementations of systems consistent with the invention ate described herein. For example,  FIG. 25  illustrates the processes performed by one embodiment of a wage assignment collection and delivery system as shown in  FIG. 1 . In this embodiment, initiator  110  initiates a wage assignment (step  2510 ). Next, accumulator  120  collects, translates, groups, and delivers the wage assignment information (step  2520 ). Finally, recipient  130  receives a wage assignment for processing and implementation ( 2530 ).  FIGS. 26-28  depict flow diagrams illustrating the series of particular steps performed by a wage assignment collection and delivery system as shown in  FIG. 25 . 
       FIG. 26  illustrates the steps performed by initiator  110  in one embodiment of a wage assignment collection and delivery system as shown in  FIG. 1 . As shown in  FIG. 26 , initiator  110  receives a wage assignment order for processing (step  2610 ). Next, initiator  110  inputs the wage assignment information into a database (step  2620 ). At some point in time, and preferably on a periodic basis, initiator  110  then transmits the wage assignment information contained in the wage assignment information database to accumulator  120  (step  2630 ). 
       FIG. 27  illustrates the steps performed by accumulator  120  in one embodiment of a wage assignment collection and delivery system as shown in  FIG. 1 . As shown in  FIG. 27 , accumulator  120  receives wage assignment information from initiator  110  (step  2710 ). As described above, accumulator  120  may receive an unlimited number of wage assignment information transmissions from an unlimited number of initiators  110 . Accordingly, accumulator  120  collects all wage assignment information into a wage assignment information file (step  2720 ). After collection, in a preferred implementation, accumulator  120  then translates each wage assignment in the wage assignment information file into an EDI wage assignment information file (step  2730 ). After translation, accumulator  120  then groups the EDI wage assignment information files by batching the files based on one field from the file. Preferably, the grouping of EDI wage assignment information files during the batching process occurs pursuant to the recipient field, so that the EDI batch files are batched based on the recipient (step  2740 ). After grouping, accumulator  120  then delivers an EDI batch file to each of a plurality of recipients  130 . In a preferred implementation, where the EDI batch files are batched on the recipient, each recipient receives a single batch file containing all wage assignments for that recipient (step  2750 ). 
       FIG. 28  illustrates the steps performed by recipient  130  in one embodiment of a wage assignment collection and delivery system as shown in  FIG. 1 . As shown in  FIG. 28 , recipient  130  receives an EDI batch file from accumulator agency  120  (step  2810 ). Next, recipient  130  processes the wage assignment information from the EDI batch file (step  2820 ). As noted above, an EDI batch file may contain one or more EDI files. Finally, in processing the wage assignment information from the EDI batch file, each wage assignment is implemented at recipient  130  by accounts payable, human resources, or any other payroll system or method (step  2830 ). For example, in a preferred implementation relating to a child support obligation, a child support payment is withheld from the salary of a noncustodial parent, and the payment is then disbursed to the appropriate payee. 
     Similar to  FIG. 25 ,  FIG. 29  illustrates the processes performed by another embodiment of a wage assignment collection and delivery system as shown in  FIG. 2B . In this embodiment, state  215  initiates a wage assignment (step  2910 ). Next, accumulator  120  collects, translates, groups, and delivers the wage assignment information (step  2920 ). Finally, employer  235  receives a wage assignment for processing ( 2930 ).  FIGS. 30-32  depict flow diagrams illustrating the series of particular steps performed by a wage assignment collection and delivery system as shown in  FIG. 29 . 
       FIG. 30  illustrates the steps performed by state  215  in one embodiment of a wage assignment collection and delivery system as shown in  FIG. 2B . As shown in  FIG. 30 , state  215  receives a wage assignment order for processing (step  3010 ). Next, state  215  inputs the wage assignment information into a database (step  3020 ). At some point in time, and preferably on a periodic basis, state  215  then transmits the wage assignment information contained in the wage assignment information database to accumulator  120  (step  3030 ). Notably,  FIG. 30  performs the same steps as described in  FIG. 26 , except that instead of generally referencing an initiator  110  as in  FIG. 26 ,  FIG. 30  references a state  215 , which refers more specifically to a state or a state entity. 
       FIG. 31  illustrates the steps performed by accumulator  120  in one embodiment of a wage assignment collection and delivery system as shown in  FIG. 2B . As shown in  FIG. 31 , accumulator  120  receives wage assignment information from state  215  (step  3110 ). As described above, accumulator  120  may receive an unlimited number of wage assignment information transmissions from an unlimited number of states  215 . Next, accumulator  120  certifies the employer denoted by the wage assignment information (step  3105 ). If the employer participates with the accumulator (e.g., subscribes to the accumulator service), then the wage assignment information is accepted, but if the employer does not participate with the accumulator (e.g., does not subscribe to the accumulator service), then the wage assignment information is rejected (step  3120 ). Accordingly, if the wage assignment information is accepted, accumulator  120  collects all wage assignment information into a wage assignment information file (step  3130 ). After collection, in a preferred implementation, accumulator  120  then translates each wage assignment in the wage assignment information file into an EDI wage assignment information file (step  3140 ). After translation, accumulator  120  then groups the EDI wage assignment information files by batching the files based on one field from the file. Preferably, the grouping of EDI wage assignment information files during the batching process occurs pursuant to the recipient field, so that the EDI batch files are batched based on the recipient (step  3150 ). After grouping, accumulator  120  then delivers an EDI batch file to each of a plurality of employers  235 . In a preferred implementation, where the EDI batch files are batched on the employer, each employer receives a single batch file containing all wage assignments for that employer (step  3160 ). Notably,  FIG. 31  essentially performs the same steps as described in  FIG. 27 , except that  FIG. 31  also contains an employer certification component. 
       FIG. 32  illustrates the steps performed by employer  235  in one embodiment of a wage assignment collection and delivery system as shown in  FIG. 2B . As shown in  FIG. 32 , employer  235  receives an EDI batch file from accumulator agency  120  (step  3210 ). Next, employer  235  processes the wage assignment information from the EDI batch file (step  3220 ). As noted earlier, an EDI batch file may contain one or more EDI files. Finally, in processing the wage assignment information from the EDI batch file, each wage assignment is implemented at employer  235  by accounts payable, human resources, or any other payroll system or method (step  3230 ). Notably,  FIG. 32  performs the same steps as described in  FIG. 28 , except that instead of generally referencing a recipient  130  as in  FIG. 28 ,  FIG. 32  more specifically references an employer  235 . 
     VI. CONCLUSION 
     The systems consistent with the invention provide for more efficient and more economical apparatus and methods for collection, translation, grouping, and delivery of wage assignment information. The systems first collect information relating to wage assignment information, translate the information into an EDI format, which is commonly referred to as a record set. Then, the EDI files are grouped based on the data contained in one or more element fields of the EDI record set and subsequently delivered to recipients who process the wage assignment information in any known method. This improved wage assignment collection and delivery apparatus and methodology provide many advantages over the current wage assignment and collection and delivery technologies. 
     As described above, it will be apparent to those skilled in the art that various modifications and variations can be made in the apparatus and methods of the present invention without departing from the spirit and scope of the invention. Thus, it is intended that the present invention cover the modifications and variations of this invention, provided they come within the scope of the appended claims and their equivalents. In this context, equivalents means each and every implementation for carrying out the functions recited in the claims, even if not explicitly described herein.