WO2007149665A2 - System and method for document interaction and processing claims - Google Patents
System and method for document interaction and processing claims Download PDFInfo
- Publication number
- WO2007149665A2 WO2007149665A2 PCT/US2007/069278 US2007069278W WO2007149665A2 WO 2007149665 A2 WO2007149665 A2 WO 2007149665A2 US 2007069278 W US2007069278 W US 2007069278W WO 2007149665 A2 WO2007149665 A2 WO 2007149665A2
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- bankruptcy
- code
- document
- filing
- different
- Prior art date
Links
- 238000000034 method Methods 0.000 title claims abstract description 63
- 238000012545 processing Methods 0.000 title claims description 43
- 230000003993 interaction Effects 0.000 title description 10
- 230000032683 aging Effects 0.000 claims description 4
- 238000012546 transfer Methods 0.000 claims description 4
- 230000004931 aggregating effect Effects 0.000 claims 1
- 230000006870 function Effects 0.000 description 60
- 230000008520 organization Effects 0.000 description 23
- 230000008569 process Effects 0.000 description 21
- 238000004891 communication Methods 0.000 description 11
- 230000000694 effects Effects 0.000 description 6
- 238000010200 validation analysis Methods 0.000 description 6
- 230000009471 action Effects 0.000 description 5
- 230000008901 benefit Effects 0.000 description 5
- 230000008859 change Effects 0.000 description 5
- 238000004590 computer program Methods 0.000 description 5
- 238000013479 data entry Methods 0.000 description 5
- 238000007726 management method Methods 0.000 description 5
- 238000010586 diagram Methods 0.000 description 4
- 238000010923 batch production Methods 0.000 description 2
- 238000011156 evaluation Methods 0.000 description 2
- 230000014509 gene expression Effects 0.000 description 2
- 238000012790 confirmation Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000006855 networking Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000002093 peripheral effect Effects 0.000 description 1
- 230000004044 response Effects 0.000 description 1
- 238000012552 review Methods 0.000 description 1
- 238000012795 verification Methods 0.000 description 1
- 230000000007 visual effect Effects 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
- G06Q40/02—Banking, e.g. interest calculation or account maintenance
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q50/00—Information and communication technology [ICT] specially adapted for implementation of business processes of specific business sectors, e.g. utilities or tourism
- G06Q50/10—Services
- G06Q50/18—Legal services
Definitions
- the proof of claim filing process is not that simple for a creditor with many proofs of claims to file.
- a large creditor such as a bank may be associated with a number of debtors.
- an issuer bank may have a number of different debtors who have defaulted on loans made by the bank. These debtors may have filed for bankruptcy in the various bankruptcy courts around the country.
- the bank may have to file proofs of claims in almost 100 different, separate court systems. This is a particularly burdensome and time consuming task.
- any information resulting from the filing of a proof of claim may not be systematically tracked for the bank, since it is likely that the filing systems for one or more court systems may not interface with the bank's computer system.
- Embodiments of the invention address the above problems, as well as other problems.
- Embodiments of the invention are directed to bankruptcy claim processing systems and methods.
- One embodiment of the invention is directed to a method comprising receiving requests and data records from a plurality of creditors to file bankruptcy documents with a plurality of different bankruptcy organizations, and automatically generating the bankruptcy documents with the received data records.
- the bankruptcy documents are suitable for filing with different bankruptcy organizations.
- the bankruptcy documents are batch filed with the different bankruptcy organizations.
- the different bankruptcy organizations may be bankruptcy courts.
- a server computer at a data processing organization may receive requests from a plurality of creditors to file proofs of claims for debts owed by debtors to the creditors with a plurality of different bankruptcy organizations.
- Each request can include data records for generating a proof of claim.
- proofs of claims are automatically generated and formatted for filing with different bankruptcy organizations.
- the proofs of claims are then batch filed with different bankruptcy organizations along with any backup documentation that would support the proofs of claims.
- Another embodiment of the invention is directed to a method comprising: creating a document object model, wherein the document object model models document objects on a document; reviewing the document object model; and after reviewing the document object model, selecting a code version from a library of code versions, wherein the selected code version is specifically associated with at least one document object on the document.
- Another embodiment of the invention is directed to a computer readable medium comprising: code for creating a document object model, wherein the document object model models document objects on a document; code for reviewing the document object model; and code for selecting a code version from a library of code versions, wherein the selected code version is specifically associated with at least one document object on the document.
- FIG. 1 is a block diagram showing components of a data processing system.
- FIG. 2 is a block diagram showing components of a computer apparatus.
- FIG. 3 is a block diagram showing processing modules that can be used in embodiments of the invention.
- FIG. 4 is a flowchart illustrating how the processing modules in FIG. 3 can process bankruptcy claim information.
- FIG. 5 is a POC input record text file.
- FIG. 6 is a daily summary report of POC filings.
- FIG. 7 is a POC validation report.
- FIG. 8 is a backup documentation validation report.
- FIG. 9 is a POC filing activity summary report.
- FIG. 10 shows data fields for a return file, after a proof of claim has been filed.
- FIG. 11 is a POC aging report.
- FIG. 12 is a POC batch tracking report.
- FIG. 13 is a POC search Web page.
- FIG. 14 is a POC search result display.
- FIG. 15A-15C are parts of a screenshot of a Web page, which allows a user to add a POC.
- FIG. 16 is a backup documentation management web interface.
- FIG. 17 is a batch file management web interface.
- FIG. 18 is a report generation web interface.
- FIG. 19 is a flowchart which illustrates steps that can be used in a document interaction process.
- FIG. 20 shows two document objects associated with a search creditor function.
- Some embodiments of the invention are directed to systems, methods, and computer readable media associated with proof of claim filings. Other embodiments of the invention are directed to systems, methods, and computer readable media for interacting with electronic documents such as Web pages. Yet other embodiments are directed to combinations thereof.
- the specific embodiments of the invention that are described below are described in the context of bankruptcy proceedings, it is understood that embodiments of the invention are not limited to the specific embodiments described.
- the document interaction embodiments can be used with other types of courts, including other types of civil courts or even criminal courts, as well as administrative agencies (e.g., government agencies).
- Embodiments of the invention provide a single system and interface for a creditor (such as a financial institution) or other entity to interact with different courts having differently configured computer systems.
- Embodiments of the invention can accept proof of claim data and documentation from a creditor via a Web-based front end and/or through batch file transfers via an SFTP (secure file transfer protocol) connection or the like.
- SFTP secure file transfer protocol
- Embodiments of the invention can also interface with other systems such as bankruptcy information systems and bankruptcy evaluation systems (described in the above noted U.S. provisional patent applications) to collect bankruptcy data related to a pending bankruptcy proceeding (e.g., a Chapter 13 proceeding).
- case data from a bankruptcy information system can be pre-loaded to initiate a proof of claim generation and filing process.
- unfiled proofs of claims can be identified using the bankruptcy evaluation system and case data can be pre-loaded to initiate the proof of claim filing process.
- Embodiments of the invention also allow creditors to create or edit proofs of claims using a Web interface. They may also query a database for the status of previously created proofs of claims. Embodiments of the invention can track all activity relating to the filing of a proof of claim, including any information generated by a court's computer system as resulting from the filing. Embodiments of the invention may also provide a database for the activity and information from which the creditor can use for ongoing tracking purposes. Reports can be provided to help creditors manage and administer proofs of claims.
- embodiments of the invention also allow creditors to: (1 ) generate and file a new proof of claim with back-up documentation (including generated and populating a B10 form in PDF for court filing), (2) receive court receipts for proofs of claims, which are successfully filed, (3) amend or withdraw previously filed proofs of claims, (4) upload proofs of claims and back-up documentation for future release, and (5) produce activity and summary reports for administration and tracking purposes.
- a server computer at a data processing organization may receive requests from a plurality of creditors to file proofs of claims for debts owed by debtors to the creditors with a plurality of different bankruptcy organizations. Each request can include data records for generating a proof of claim. Then, proofs of claims are automatically generated and formatted for filing with different bankruptcy organizations. The proofs of claims are then batch filed with different bankruptcy organizations along with any backup documentation that would support the proofs of claims.
- FIG. 1 shows a member 12, a bankruptcy notification service 40, a data processing organization 20, and a court 30 in communication with each other via a communication medium 22.
- FIG. 1 shows a member 12, a bankruptcy notification service 40, a data processing organization 20, and a court 30 in communication with each other via a communication medium 22.
- bankruptcy notification service 40, data processing organization 20, and court 30 are shown for simplicity of illustration, it is understand that there may be additional members, bankruptcy notification services, data processing organizations, and courts in other embodiments within the scope of the invention.
- Each of these components is described in further detail below.
- a data processing system according to an embodiment of the invention may include fewer components than those shown in FIG. 1.
- Member 12 may be a member bank in a banking association. In other embodiments, however, the member 12 need not be a bank that is part of a predefined banking association. In addition, the member 12 could alternatively be any suitable creditor and need not be a bank. For example, instead of a member, the member could be a creditor such as a retail store, sole proprietorship, government entity, etc. The member 12, or other creditor, may utilize at least one client computer 12(a) to send and receive information.
- the bankruptcy notification service 40 may comprise any suitable organization that can notify creditors of bankruptcies that have been filed. Suitable bankruptcy notification services are provided by Visa ® . Such bankruptcy notification services monitor bankruptcy courts for bankruptcy filings by debtors. Those debtors are then identified and creditors are notified of the bankruptcy filings so that the creditors may thereafter file proofs of claims.
- the data processing organization 20 may have at least one server computer 20(a), which may have a corresponding computer readable medium (CRM) 20(b) to store information or store code for performing the functions of the data processing organization 20.
- the data processing organization 20 may also have a database 20(c) that is operatively coupled to the server computer 20(a) for temporarily or permanently storing bankruptcy information.
- the data processing organization 20 and/or its server computer 20(a) may perform various functions. Such functions include: a search function (where users may search, view, edit delete, amend, and withdraw individual proofs of claims, and add or delete backup documentation relating to such proofs); an add function (where users may add new proofs of claims and may add back documentation); a legacy proof of claim function (where users can amend, replace, or withdraw proofs of claims that they filed through other channels); a manage files function (which allows users to submit proofs of claims and backup documentation to batch files, and download batch related documentation based on date ranges); and a reports function (which allows users to download and view batch process and proof of claim filing reports).
- a search function where users may search, view, edit delete, amend, and withdraw individual proofs of claims, and add or delete backup documentation relating to such proofs
- an add function where users may add new proofs of claims and may add back documentation
- a legacy proof of claim function where users can amend, replace, or withdraw proofs of claims that they filed through other channels
- the search function can provide a number of data fields for a user via a graphical user interface.
- the data fields may include case number, date of POC generated or date of POC filed, account number, debtor name, debtor social security number (SSN), POC identifier, filing action, secured claim amount, unsecured claim amount, priority claim amount, record status, collateral type, batch number, court number, and court state.
- the results of the search may include information such as: POC ID, case number, account number (last four digits), court, record status, debtor 1 and debtor 1's SSN, debtor 2 and debtor 2's SSN, and any claim amount(s).
- the add function can allow a user to add a new POC record.
- the user may fill out appropriate data fields and may send this information to the host site.
- the manage files function allows a user to upload new backup documentation or delete existing documentation for a non-filed POC or a new POC. The user sees the individual court's requirements on the graphical user interface.
- a "manage batch files" function users can download return files from batch processes and upload POCs and supporting documentation in a batch format.
- the reporting function allows a user to download various reports including the following: daily status report, proof of claim validation report, documentation validation report, filing activity report, batch track report, aging report, and account tracking report.
- Other data fields that can be provided to a user via a graphical user interface when filing a POC may include the following: unique identifier, chapter (e.g., 7, 11 , etc.), hold expire date, release filing without backup documents, court number-city, case number, claim number, debtor account number, debtor name, debtor social security number, creditor, creditor address and phone number, notices, previously filed date, basis for claim (e.g., goods sold, services performed), date debt incurred, date court judgment obtained, includes interest charges, secured claim amount, collateral type, arrearages, unsecured non-priority claim amount, unsecured priority, signature, and installment loan.
- a "server computer” or “host computer” may be embodied by one or more computational apparatuses, which can service the requests of one or more client computers.
- a server computer or host computer is a powerful computer or cluster of computers that behave as a single computer.
- the server computer 20(a) can be a mainframe computer, a minicomputer, or a minicomputer cluster.
- the server computer 20(a) may include one or more database servers and one or more Web servers.
- the server computer 20(a) may service the requests of one or more client computers.
- the court 30 may be a bankruptcy court. Preferred embodiments of the invention can be used to file proofs of claims in any suitable type of bankruptcy proceeding. Such proceedings may include Chapter 7, Chapter 13, Chapter 11 , etc. bankruptcy proceedings.
- the court 30 may have at least one host computer 30(a), which may operate a Web site (or host site) 30(b) to allow the public to file documents or access records.
- FIG. 1 to communicate electronically may including any suitable combination of communication lines, channels, and radio interfaces.
- the communication medium 22 may include, for example, the Internet, an intranet, the public switched telephone network (PSTN), or a wireless telephone or radio network.
- the server computer 20(a) and various client computers e.g., client computer 12(a)
- the communication medium 22 could comprise a payment processing network such as a VisaNetTM.
- Any of the computations apparatuses may utilize any suitable number of subsystems. Examples of such subsystems or components are shown in FIG. 2.
- the subsystems shown in FIG. 2 are interconnected via a system bus 475. Additional subsystems such as a printer 474, keyboard 478, fixed disk 479, monitor 476, which is coupled to display adapter 482, and others are shown.
- Peripherals and input/output (I/O) devices which couple to I/O controller 471 , can be connected to the computer system by any number of means known in the art, such as serial port 477.
- serial port 477 or external interface 481 can be used to connect the computer apparatus to a wide area network such as the Internet, a mouse input device, or a scanner.
- the interconnection via system bus allows the central processor 473 to communicate with each subsystem and to control the execution of instructions from system memory 472 or the fixed disk 479, as well as the exchange of information between subsystems.
- the system memory 472 and/or the fixed disk 479 may embody a computer readable medium.
- a debtor (not shown) may file for bankruptcy with the court 30.
- the bankruptcy notification service 40 After the debtor files for bankruptcy, the bankruptcy notification service 40 electronically or manually contacts the bankruptcy court 30 to determine if the debtor has filed for bankruptcy (step 18(a)-1). For example, the bankruptcy notification service 40 may contact the court's client computer 30(a) via the communication medium 22, or may have an employee contact the court 30 by phone or in person. After contacting the bankruptcy court 30, the bankruptcy notification service 40 receives information verifying the debtor has filed for bankruptcy (i.e., a bankruptcy notice) (step 18(a)-2). The information may be sent to the bankruptcy notification service 40 electronically or through a paper delivery service (e.g., the U.S. mail).
- a paper delivery service e.g., the U.S. mail
- the bankruptcy notification service 40 sends the bankruptcy notice to the member 12. This can be done using a paper delivery service (e.g., the U.S. mail service) (step 18(b)-1 ) or electronically through the communication medium 22 (step 18(b)-2).
- a paper delivery service e.g., the U.S. mail service
- the communication medium 22 step 18(b)-2
- the member 12 After the member 12 receives a bankruptcy notice from the bankruptcy notification service 40, the member 12 processes the bankruptcy notice. The member 12 determines whether or not it wants to file a proof of claim against the debtor in the court 30. In some cases, the member 12 may decide that the value of any potential claim that is filed in the bankruptcy proceeding would not exceed the fees for processing the claim, so the member 12 may decide that filing a proof of claim would not be cost effective. On the other hand, the member may decide that it is cost effective to file the proof of claim.
- the member 12 can send POC (proof of claim) input records and supporting documentation to the data processing organization 20.
- POC proof of claim
- the POC input records and the documentation files may be sent to the data processing organization 20 electronically via the communication medium 22 using the member's client computer 12(a) (steps 18(c) and 18(d)), and this information may be received by the server computer 20(a).
- the server computer 20(a) After the server computer 20(a) receives the POC input records and supporting documentation, the server computer 20(a) processes the information and generates appropriate proofs of claims for the court 30.
- the server computer 20(a) also formats other proofs of claims for other courts. These other proofs of claims may have originated from a request by the member 12, or other creditor. Supporting documentation is also associated with (e.g., attached to) the various proofs of claims that are generated. The proofs of claims are then "batched" together for filing at period time intervals.
- a batch mode filing process may include the simultaneous or near simultaneous filing of proofs of claims with the same or different courts, wherein the courts have the same or different filing procedures and/or filing formats.
- proof of claim filing requests may be received from various creditors and the POC filings may be generated by the server computer 20(a). Once generated, the POC filings may be batched together so that they are submitted to various courts in batches at predetermined times. The predetermined times may include once a day, twice a day, every hour, every half hour, etc.
- the server computer 20(a) can determine which proofs of claims are ready and complete with backup information, valid data, etc., and they are filed with the various courts according to their specific requirements.
- the batches of proofs of claims may be batched according to time of filing, as described above. They may alternatively or additionally be batched by court.
- the court 30 may send a filing receipt back to the data processing organization 20 (steps 18(g) and 18(h)). If the proof of claim filing and other filings in the batch were not successful, the data processing organization 20 can follow up to track any problems that may have occurred in the POC filings.
- the server computer 20(a) operated by the data processing organization 20 may generate filing reports and other documents (e.g., PDF reports or POC transaction return files which may be .txt files).
- the server computer 20(a) can then send any filing reports back to the client computer 12(a) operated by member 12 (steps 18(i), 18G)).
- FIG. 3 shows block diagram of various software modules and components that can be used in the systems and methods according to embodiments of the invention.
- the components include proof of claim input records 224 (for generating proofs of claims), an optional customized interface 222, and supporting documentation files 232. Reports 274 and POC Transaction Return Files 272 are also shown.
- the software modules that are shown include a validate and post POC records module 220, a validate and post back-up documents module 230, a generate B-10 forms and docs module 240, a POC status updates modules 250, a file claims module 260, and a generate reports module 270.
- Each of these modules interacts with a database 210 including a POC table, rejects (information about rejected filings), and a file directory.
- the various modules may be embodied by computer code stored on a computer readable medium.
- the POC processing module 220 validates the received information and loads information into one or more POC Tables (steps 310, 312).
- the document file processing module 230 validates and loads supporting documentation, and updates and logs control tables (step 314). Then, one or more documentation tables are loaded (step 316).
- a Website may accept user entry and they may pass the request onto a Web interface (step 304).
- the Web interface accepts the message from the member 12, and then validates and loads received information to a POC table (step 306). Logs and control tables are also updated.
- One or more POC tables are loaded (step 312) using the POC processing module 220, and the documentation file processing module 230 validates and loads supporting documentation (steps 314, 316). Documentation is converted, if needed, and logs and control tables are updated.
- the B10 generation module 240 generates B10 forms for various different courts with different filing requirements and updates logs and control tables (step 318). After the B10 forms are generated and after any supporting documentation is ready to be sent to the bankruptcy courts, the POC status updates module 250 determines which are proofs of claims are ready to file (step 320). Logs and control tables are also updated.
- the batch filing module 260 connects with the court and attempts to file the POCs with backup documentation in a batch mode (step 322).
- the court 30 then either accepts or rejects the filed POCs, and then provides receipts for successful filings (step 326).
- the batch filing module 250 then receives the court's responses and then updates logs and control tables (step 324).
- the generate reports modules 270 then generates reports, and also updates logs and control tables (step 328).
- the member 12, can thereafter download files and reports through the Web interface or through an SFTP or other type of connection (step 330). Alternatively, reports can be sent to the member 12 via e-mail.
- a number of different filing reports may be provided to the users (e.g., creditors such as members, etc.) of embodiments of the invention.
- embodiments of the invention can provide users with at least seven types of reports to assist in the management of their filed proofs of claims. These reports are useful and may be output in a tangible format such as via a display or on a piece of paper by a printer or the like.
- FIGS. 5-18 screenshots, reports, and data fields are shown in FIGS. 5-18.
- embodiments of the invention allow a member or other creditor to easily monitor the status of any proof of claim filings that it has requested. This is particularly useful when a creditor needs to file many proofs of claims and monitor their status.
- FIG. 5 shows a proof of claim input record (.txt file), which has information that a member or other creditor may provide to the data processing organization so that the data processing organization can generate and file proofs of claims.
- the input record may include a number of data fields.
- the "unique identifier" field contains an identifier which keeps the particular record unique. It allows the server computer to match the POC record with its corresponding back-up documentation. It identifies the system user, member, claim status, and sequence number. As shown, there are indicia to represent the user, the member, the status of the claim (e.g., filed, amended, or withdrawn), and the sequence.
- the sequence may be the number of times that the proof of claim has been submitted. For example, if it has been rejected by a bankruptcy court once, then the sequence number may be "1".
- the "transaction type” field indicates what the member wants to do with the record. For example, a member may want to add a file, delete a file, hold a file, but not release it, and release a previously held file.
- "Filing action” indicates what was done with the court. For example, a record may be filed, amended, or withdrawn.
- "Court number” indicates the court where the claim will be filed.
- "B-10 Fields” includes the case number, the claim amount, etc. This includes data needed to generate a B-10 form.
- "Automatically generate B-10” form indicates whether the server computer or the member will generate the B-10 form.
- "Automatically Generate Back-up Document” indicates whether the system or member will generate unsecured back-up documentation.
- FIG. 6 shows a Daily Summary Report. It shows the number of proof of claim records and documentation files received from the user, and the number of records accepted and rejected. It also shows the status of the proofs of claims filed at the bankruptcy courts.
- FIG. 7 shows a proof of claim validation report.
- FIG. 7 shows that one record was rejected and the reject detail for that rejected POC filing is provided.
- the rejected claim had an invalid court number and $0 for a claim amount.
- FIG. 8 shows a documentation validation report. This provides a report on the status of the filing of the documentation supporting the proof of claim filings. As in FIG. 7, the reasons for the rejections are provided.
- FIG. 9 shows a filing activity report. As shown therein, the proofs of claims that are ready to file are listed. It shows the unique IDs of the claims, the district court, the case number, the number of claims, and amounts, the filing dates and times, the case stamp, the document submitted, the document stamp, and the batch number.
- FIG. 10 shows data fields for return files, after proofs of claims have been filed.
- the data fields include a unique identifier, a filing status, a date and time that the claim was filed, a court ID stamp, the name of the district court in which the claim was filed, the case number, the claim number, the debt type, the claim amount, and the account number on the claim.
- FIG. 11 shows a screenshot of an aging report. As shown, the statuses of the POCs to be filed are shown. One POC has a status of "waiting" as the server computer is waiting for back-up documentation to submit with the POC. Another POC has a status of "hold” whereby a member may have requested that the filing be held upon further notice. The last POC has a status of "ready” to file.
- FIG. 12 is a batch track report. As shown in FIG. 12, one batch of POCs per day was filed, and the status of each of those batch filings is shown.
- FIG. 13 is a search POC form. As shown, a user can enter specific information into the various data entry boxes in the form and can search for POCs.
- FIG. 14 shows the results of the search using the search form shown in FIG. 13. As shown, a number of POCs and their statuses are shown.
- FIGS. 15A-15C show a form that can be on a Web site that can be run by the data processing organization.
- the form can be used for filling in an individual POC. This form might be used if a single POC is to be submitted through the Web site operated by a data processing organization.
- FIGS. 15A-15C show that the server computer operated by the data processing organization may create and file an individual proof of claim using the form shown in FIGS. 15A-15C, or it may create and file a batch of proofs of claims as described above.
- FIG. 16 is a screen that will allow one to upload backup documentation to the server computer operated by the data processing organization to attach to POCs. As shown, documentation such as promissory notes and contracts may be attached to the POCs.
- FIG. 17 shows a file management screenshot. The screen shown in
- FIG. 17 may be used to upload batches of POC files and batches of documentation files associated with the POC files to the server computer operated by the data processing organization.
- FIG. 18 shows a screen that will allow one to download reports. As shown, various reports that gather filing information from various date ranges may be downloaded.
- embodiments of the invention have a number of advantages.
- a creditor such as a bank may interact with a single entity (e.g., a data processing organization) to file all of its proofs of claims (or other bankruptcy documents) with various bankruptcy courts around the country.
- the bank need not take the time and effort to figure out the filing requirements of each and every bankruptcy court.
- embodiments of the invention allow creditors to easily track the status of many proof of claim filings. This helps creditors with large numbers of claims keep track of their claims.
- CM/ECF bankruptcy court Case Management/Electronic Case Filing
- Each bankruptcy court's filing system is based on the same CM/ECF system, but each court may choose to configure its own system to its own requirements and needs.
- different courts may be on different versions of the system.
- the courts may also choose to update their systems at different times, with or without notification of its users.
- the data processing system that is described above preferably operates continuously and would preferably not have to stop or become interrupted, because one or more courts decide to change the configurations of their filing systems.
- code version A may automate the "search creditor” function for a bankruptcy court in California
- code version B may automate the "search creditor” function for a bankruptcy court in Florida.
- embodiments of the invention can log into any court's computer filing system and determine the system's document (e.g., Web page) layout, components, and properties. Once it determines the court system's layout, components, and properties, it then selects which code version to use for each function it needs to perform and executes the code in the grouping of code versions that is selected.
- system's document e.g., Web page
- Embodiments of the invention have a number of advantages. First, if the court makes changes to its system, the system will most likely still be able to perform the necessary functions since the changes will most likely already be in the code version library from other courts. Second, programming time is minimized since code is reused. Embodiments of the invention can use pre-existing code versions in libraries in order to reuse existing code. Third, embodiments of the invention eliminate the need to manually track each court's filing configurations, since embodiments of the invention will be able to react accordingly to different configurations created over time by the various courts.
- a document object model is created.
- the document object model models document objects on a document.
- "document objects” include any elements on an electronic document such as a Web page that may correspond to a particular function. For example, a fill in box for a creditor and a corresponding "submit” button may form a document object associated with the function "search creditor.”
- the document object model basically "models" the document objects on the document by determining characteristics such as any text, input elements, and data entry fields that may be associated with the document objects, and their locations on the document.
- a digital computer such as the server computer 20(a) in FlG. 1 , may select a code version from a library of code versions, wherein the selected code version is specifically associated with at least one document object on the document. For example, there may be a first code version in a first library of code versions. The first code version may be specifically associated with a first document object on the document. There may be a second code version from a second library of code versions. The second code version may be specifically associated with a second document object on the document. The first code version and the second code version are included in a customized group of code versions, wherein the customized group of code versions is used to cause a digital computer to automatically interact with the document. For example, the code in the customized group of code versions may cause a microprocessor in the digital computer to cause populate the document with the correct bankruptcy data, and then submit the populated document to the appropriate bankruptcy court.
- FIG. 19 shows a flowchart illustrating how a document interaction embodiment of the invention can be performed.
- the server computer 20(a) shown in FIG. 1 may open a Web browser, and navigate to the court's Web site 30(b) (step 2410) (as if a human was performing this function).
- the server computer 20(a) then logs into the court's Web site 30(b) (step 2420).
- a Web page i.e., an electronic "document
- a single Web page is discussed. It is understood the described process can be repeated for any number of Web pages.
- the server computer 20(a) then creates a document object model (step
- the server computer 20(a) by identifying the functions on the Web page and selecting code versions from libraries of code versions that correspond to those functions. This process is described in further detail below. Based on the information collected on the document object model, the correct code versions are selected by the server computer 20(a), and the selected code versions are used by the server computer 20(a) to interact with the Web page. A customized grouping of code versions is created for the Web page and/or the Web site 30(a), and the code in this customized group of code versions can be used to automatically fill in the Web page and then activate it (e.g., automatically selecting a submit button), thereby automating the proof of claim filing process. The next document is then filed or the user logs off (step 2440).
- FIG. 19 The exemplary creation of the document object model and the selection of code versions is shown in box 2000 in FIG. 19.
- box 2000 in the creation of the document object model, document objects on a court's Web page are collected and a document object model is created (step 2432).
- blocks 2434 illustrate exemplary document objects associated with the following functions that are associated with filing a proof of claim: "start”, “search creditor”, “enter claim”, “add creditor” and "finish”.
- the server computer 20(a) may identify particular properties associated with each of the document objects. For example, it may identify the document object associated with the function "search creditor.” This particular document object may have a number of data entry boxes whereby a user may enter the name or other information that would identify a creditor, and may have a "search” button which the user may select after the user enters information into the data entry boxes. The location of the search button on the court's Web page, and the format and locations of the data entry boxes associated with the "search creditor" function may be determined by the server computer 20(a). This process may be repeated for all or less than all of the document objects on the Web page, or on the Web site 30(b).
- the server computer 20(a) reviews the document object model and then selects the appropriate code versions to use with each document object (step 2436).
- Each function and/or document object may have a library of code versions associated with it, and one code version from each library is selected to form a customized grouping of code versions for that Web page (or Web site 30(a)). For example, as shown by reference number 2438 in FIG.
- the document object associated with the "start” function may use code version A from a first library of code versions
- the document object associated with the "search creditor” function may use code version B from a second library of code versions
- the "enter claim” function may use code version C from a third library of code versions
- the "enter claim” function may use code version X from a fourth library of code versions
- the "finish” function may use code version A from a fifth library of code versions.
- the selected code versions A, B, C, X, and A may form a customized grouping of code versions that can automate the filing process for the particular bankruptcy court 30.
- selected code versions may be characterized as a customized code grouping that is suitable for interacting with that Web page.
- This customized code grouping may be formed automatically by a digital computer such as the server computer 20(a).
- embodiments of the invention can create a new iexplore.exe process and open a connection using shdocvw.dll (shdocvw.dll is a library used by Windows applications to add basic file and networking operations, and is encapsulated in .NET I ntemetExplorer object). Then, embodiments of invention interact with the IE object by issuing commands (e.g., navigate to URL, quit browser window, etc.), receiving events (e.g., browser window ready - new page loaded), and getting properties (document object model document).
- commands e.g., navigate to URL, quit browser window, etc.
- receiving events e.g., browser window ready - new page loaded
- properties document model document
- a new document object model is created using mshtml.dll (a module containing HTML-related utility functions and which is encapsulated in a .NET HTMLDocument object).
- Embodiments of the invention then assign an I ntemetExplorer. Document property to the HTMLDocument object, and then interact with the HTMLDocument object.
- Embodiments of the invention then receive data (e.g., rendered HTML, rendered text), get properties (individual document object model elements), and issue commands (e.g., fill in text box, click button, click anchor, select option element, etc.).
- the court Web page navigation process can be broken down into discrete steps or core functions. They include a) Login, b) Logout, c) Upload documents, d) File proof of claim (F:Start; F:Search Creditor; F:Add Creditor; F:Enter Claim; and F:Finish), and e) File withdrawal (W) (W:Start; W:Search Case; W:Select Party; W:Add Party; W:Claim Action; W:Attorney; W:Claim Amount / Number; W:Claim Party; W:Claim Status; W:Confirm; and W:Finish).
- Each core function contains of a grouping of verifications, commands, and results. For example, “Login” will do the following: verify that the current page contains required keywords; locate and fill the "Usemame” text box; locate and fill the "Password” text box; locate and click the "Login” button; wait for new page to load; and verify current page contains required keywords to validate login success. Checks are also made for alternate keywords (i.e. "invalid username", "user already logged in”, etc).
- each core function may be associated with or contain multiple code versions, so that compatibility is maintained as changes to court websites are made. As explained above, document objects on Web pages can differ from court to court. For example, as shown in FIG. 20, the function "F:Add Creditor” can work differently for two different courts. As shown in FIG. 20, in
- Version A Address 1 , Address 2, City, State, Zip are discrete text boxes and may be associated with a bankruptcy court in California.
- Version B may be associated with a bankruptcy court in Maryland.
- the address is one multi-line text box, and the entire address is entered at once.
- the "F:Add Creditor” function is run, the first thing that the digital computer does is locate the address text boxes on the Web page. If it finds discrete address fields, it uses “Version A” logic; if it finds one multi-line field, it uses “Version B” logic. When courts upgrade their sites and change from “Version A” to “Version B", the change will be detected and compensated for automatically.
- Page elements that are the same in appearance may have different properties from court to court. Buttons, text boxes, lists, etc that serve the same purpose from court to court can have different names or captions. Code versions are created for the core functions to account for these differences. For example, "FiSearch Creditor” needs to identify an existing select list on the page. This select list will contain the names of all the existing creditors on a case. The select list is present on each court's "Search Creditor” page, but the actual element name will differ. Some courts call it [I st_search Creditor], others [lst_Creditor]. There are two possible versions of this list.
- [lst_searchCreditor] is found, it is utilized and the function continues. If it is not found, [lst_Creditor] is searched for; if found, it is utilized and the function continues. If neither is found, an error is shown. Possible error outcomes are: 1) that the page didn't load successfully, 2) it is the wrong page, or 3) a new list name variation has occurred, and a new version needs to be added to the function.
- the sequence of core functions and/or the sequence of Web pages may be predetermined by the data processing organization, so that the server computer 20(a) knows what Web order pages to expect when filing POCs.
- the above-described process is used to automatically interact with each of the Web pages, even through they are configured differently or recently reconfigured.
- new court functionality is added to each Web page, new core functions are created, and called from the court subclasses. If existing court functionality is modified, a new version of instructions may be added to the corresponding core function.
- First embodiments of the invention can be used to automatically file proofs of claims or other documents with bankruptcy courts or the like.
- any of the software components or functions described in this application may be implemented as software code to be executed by a processor using any suitable computer language such as, for example, Java, C++ or Perl using, for example, conventional or object-oriented techniques.
- the software code may be stored as a series of instructions, or commands on a computer readable medium, such as a random access memory (RAM), a read only memory (ROM), a magnetic medium such as a hard-drive or a floppy disk, or an optical medium such as a CD-ROM. Any such computer readable medium may reside on or within a single computational apparatus, and may be present on or within different computational apparatuses within a system or network.
Landscapes
- Business, Economics & Management (AREA)
- Engineering & Computer Science (AREA)
- Strategic Management (AREA)
- Accounting & Taxation (AREA)
- Finance (AREA)
- Economics (AREA)
- Tourism & Hospitality (AREA)
- Theoretical Computer Science (AREA)
- Marketing (AREA)
- General Physics & Mathematics (AREA)
- Technology Law (AREA)
- Physics & Mathematics (AREA)
- General Business, Economics & Management (AREA)
- Primary Health Care (AREA)
- Human Resources & Organizations (AREA)
- General Health & Medical Sciences (AREA)
- Health & Medical Sciences (AREA)
- Development Economics (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
- Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
Description
Claims
Priority Applications (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
BRPI0713324-3A BRPI0713324A2 (en) | 2006-06-22 | 2007-05-18 | METHOD AND SYSTEM FOR DOCUMENT INTERACTION AND CREDIT PROCESSING, LEGIBLE MEDIA BY COMPUTER, COMPUTER SERVER, SERVER, AND, DATA PROCESSING SYSTEM |
CA002656052A CA2656052A1 (en) | 2006-06-22 | 2007-05-18 | System and method for document interaction and processing claims |
AU2007261236A AU2007261236B2 (en) | 2006-06-22 | 2007-05-18 | System and method for document interaction and processing claims |
EP07783944A EP2038834A4 (en) | 2006-06-22 | 2007-05-18 | System and method for document interaction and processing claims |
Applications Claiming Priority (10)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US81612906P | 2006-06-22 | 2006-06-22 | |
US60/816,129 | 2006-06-22 | ||
US81826106P | 2006-06-29 | 2006-06-29 | |
US60/818,261 | 2006-06-29 | ||
US81955306P | 2006-07-07 | 2006-07-07 | |
US60/819,553 | 2006-07-07 | ||
US11/613,889 | 2006-12-20 | ||
US11/613,859 | 2006-12-20 | ||
US11/613,889 US20070300141A1 (en) | 2006-06-22 | 2006-12-20 | Method and system for document interaction |
US11/613,859 US8538866B2 (en) | 2006-06-22 | 2006-12-20 | System and method for processing bankruptcy claims |
Publications (2)
Publication Number | Publication Date |
---|---|
WO2007149665A2 true WO2007149665A2 (en) | 2007-12-27 |
WO2007149665A3 WO2007149665A3 (en) | 2008-06-19 |
Family
ID=38834204
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/US2007/069278 WO2007149665A2 (en) | 2006-06-22 | 2007-05-18 | System and method for document interaction and processing claims |
Country Status (5)
Country | Link |
---|---|
EP (1) | EP2038834A4 (en) |
AU (1) | AU2007261236B2 (en) |
BR (1) | BRPI0713324A2 (en) |
CA (1) | CA2656052A1 (en) |
WO (1) | WO2007149665A2 (en) |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2012001229A1 (en) * | 2010-06-28 | 2012-01-05 | Nokia Corporation | Method and apparatus for a paged update protocol |
Family Cites Families (8)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5956737A (en) * | 1996-09-09 | 1999-09-21 | Design Intelligence, Inc. | Design engine for fitting content to a medium |
US20040019560A1 (en) * | 1999-03-12 | 2004-01-29 | Evans Scott L. | System and method for debt presentment and resolution |
US6981212B1 (en) * | 1999-09-30 | 2005-12-27 | International Business Machines Corporation | Extensible markup language (XML) server pages having custom document object model (DOM) tags |
WO2001067362A2 (en) * | 2000-03-07 | 2001-09-13 | Broadcom Corporation | An interactive system for and method of automating the generation of legal documents |
US7055165B2 (en) * | 2001-06-15 | 2006-05-30 | Intel Corporation | Method and apparatus for periodically delivering an optimal batch broadcast schedule based on distributed client feedback |
US20030028477A1 (en) * | 2001-07-31 | 2003-02-06 | Accredited Bankruptcy Services, Inc. | Automated method and system for consumer financial counseling |
US7624067B2 (en) * | 2001-12-21 | 2009-11-24 | Glynntech, Inc. | Bankruptcy creditor manager internet system |
US20040064404A1 (en) * | 2002-10-01 | 2004-04-01 | Menachem Cohen | Computer-based method for automatic remote coding of debtor credit databases with bankruptcy filing information |
-
2007
- 2007-05-18 WO PCT/US2007/069278 patent/WO2007149665A2/en active Application Filing
- 2007-05-18 EP EP07783944A patent/EP2038834A4/en not_active Withdrawn
- 2007-05-18 AU AU2007261236A patent/AU2007261236B2/en active Active
- 2007-05-18 BR BRPI0713324-3A patent/BRPI0713324A2/en not_active IP Right Cessation
- 2007-05-18 CA CA002656052A patent/CA2656052A1/en not_active Abandoned
Non-Patent Citations (1)
Title |
---|
See references of EP2038834A4 * |
Cited By (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2012001229A1 (en) * | 2010-06-28 | 2012-01-05 | Nokia Corporation | Method and apparatus for a paged update protocol |
US9792381B2 (en) | 2010-06-28 | 2017-10-17 | Here Global B.V. | Method and apparatus for a paged update protocol |
Also Published As
Publication number | Publication date |
---|---|
AU2007261236B2 (en) | 2013-05-02 |
BRPI0713324A2 (en) | 2012-03-13 |
EP2038834A4 (en) | 2011-03-16 |
CA2656052A1 (en) | 2007-12-27 |
WO2007149665A3 (en) | 2008-06-19 |
EP2038834A2 (en) | 2009-03-25 |
AU2007261236A1 (en) | 2007-12-27 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US7669116B2 (en) | Single access point for filing of converted electronic forms to multiple processing entities | |
US7234103B1 (en) | Network-based tax framework database | |
US7181420B2 (en) | Methods and systems for online self-service receivables management and automated online receivables dispute resolution | |
US7603301B1 (en) | Verification and printing of a tax return in a network-based tax architecture | |
US20090182717A1 (en) | Interactive forms processing system and method | |
US7340421B1 (en) | Account reconciliation methods and systems | |
US20140180883A1 (en) | System, method and article of manufacture for providing tax services in a network-based tax architecture | |
US20070300141A1 (en) | Method and system for document interaction | |
US20070174191A1 (en) | Factoring system and method | |
US20050209955A1 (en) | Apparatus and method for document processing | |
CA2452852A1 (en) | Financial funding system and methods | |
US20090059909A1 (en) | Method and system for loan application non-acceptance follow-up | |
US8538866B2 (en) | System and method for processing bankruptcy claims | |
CA2407667C (en) | Method for a network-based tax model framework | |
US8874476B1 (en) | Automated federal court filing system | |
US20060031125A1 (en) | Interactive forms processing system and method | |
WO2001075598A1 (en) | Module for the interconnectivity of independent software applications | |
JP2002259896A (en) | Electronic document processing device and method | |
AU2007261236B2 (en) | System and method for document interaction and processing claims | |
CN111080459A (en) | Configuration method and device of configuration file and readable storage medium | |
US20090313158A1 (en) | Online closing system and method | |
KR101869653B1 (en) | Administrative task computerized publishing system connected with on-nara system, and administrative task computerized publishing method based on the same | |
JP7526595B2 (en) | Transportation expense payment system and transportation expense payment method. | |
JP7511670B2 (en) | Credit operation support method and credit operation support system | |
Ptiček et al. | The potential of SEPA Credit Transfer implementation in Croatia |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 07783944 Country of ref document: EP Kind code of ref document: A2 |
|
ENP | Entry into the national phase in: |
Ref document number: 2656052 Country of ref document: CA |
|
NENP | Non-entry into the national phase in: |
Ref country code: DE |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2007261236 Country of ref document: AU |
|
NENP | Non-entry into the national phase in: |
Ref country code: RU |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2007783944 Country of ref document: EP |
|
ENP | Entry into the national phase in: |
Ref document number: 2007261236 Country of ref document: AU Date of ref document: 20070518 Kind code of ref document: A |
|
ENP | Entry into the national phase in: |
Ref document number: PI0713324 Country of ref document: BR Kind code of ref document: A2 Effective date: 20081219 |