PRIORITY STATEMENT

This application is a continuation-in-part of U.S. Patent Application Serial No. 13/645,141, filed October 4, 2012, hereby incorporated by reference in its entirety.

FIELD OF THE INVENTION

The present invention relates to a cloud-based skip tracing application. More particularly, but not exclusively, the present invention relates to a cloud-based skip tracing application which allows a user to interact with multiple data vendors in a waterfall process.

BACKGROUND OF THE INVENTION

Skip tracing often involves using numerous different databases or other vendor services to identify accurate and current information for an individual. Because not all information is available from a single source there are numerous complexities introduced into the skip tracing process. This can include determining which vendors to use as some vendors may be more likely to have certain information than other vendors. This can also include determining the order of vendors to use when more than one vendor is used. There may be additional concerns regarding different vendor services including the time it takes with a particular vendor, the cost of using a particular vendor, and other concerns.

Moreover, the more vendors that have to be used in order to identify information, the longer the process takes.

What is needed is an improved method, apparatus, and system for performing skip tracing.

SUMMARY OF THE INVENTION

Therefore, it is a primary object, feature, or advantage of the present invention to improve over the state of the art.

It is a further object, feature, or advantage of the present invention that provides for a cloud-based solution to skip-tracing. Another object, feature, or advantage of the present invention is to provide a platform for skip tracing which allows a user to interface with multiple data vendors.

Yet another object, feature, or advantage of the present invention is to deliver B2B, analytically-driven skip data to the customer in one robust platform.

A further object, feature, or advantage of the present invention is to bring together multiple skip vendors through a unique waterfall process.

A still further object, feature, or advantage of the present invention is to provide optimal waterfall processes designed for various purposes- specific industries, based on account characteristics, and/or skipped product type.

Another object, feature, or advantage of the present invention is to provide users the ability to adjust waterfall settings to suit the purpose of their skip searches.

Yet another object, feature, or advantage of the present invention is to provide a service which can be accessed via an easy-to-use, web-based application and allows the user to control their skip tracing process to meet their company's needs.

A further object, feature, or advantage of the present invention is to allow for clients to send files in various formats and to recognize the format of the files.

A still further object, feature, or advantage of the present invention is to adapt to different file layouts from different vendors and to allow for testing of the vendors.

Another object, feature, or advantage is to allow a user to upload a file to be sent through multiple product packages of their choice.

A still further object, feature, or advantage is to provide a billing process and registration process that will be common to multiple products.

One or more of these and/or other objects, features, or advantages of the present invention will become apparent from the specification and claims that follow. No single embodiment need meet each and every object, feature, or advantage described above and it should be appreciated that different embodiments may have different objects, features, or advantages.

According to one aspect, the present invention provides a cloud-based application that focuses on delivering business-to-business (B2B), analytically-driven skip data to the customer in one robust platform by allowing a user to simply interface with multiple data vendors. The invention brings together multiple skip vendors through a waterfall process. Using analytics, optimal waterfall processes may be designed for various purposes (including to meet different and specific industry needs) based on account characteristics, and/or skipped product type. A user has the option of adjusting the waterfall settings to meet the purpose of their skip searches.

The cloud-based application is preferably an easy-to-use web-based application. Through the application the user is given the ability to control the skip tracing process in a manner that meets their needs. This may include creating different waterfalls by selecting service level and product packages. Thus, a user can access multiple skip tracing sources through a single interface. The waterfall process may include a number of different vendors and a specified sequence of vendors. Thus, a client input file may pass through multiple vendors until a hit is returned. When a record within the client input file receives a hit, it may be returned to the client, while the rest of the records in the client input file are sent onto the next vendor in the waterfall. This process continues until the last vendor in a waterfall has been skipped.

Data may be stored at the record level and be used for any number of purposes including reporting to the client, analytic-based research for optimizing waterfalls, and development of models to use in driving the waterfall process, for example.

According to another aspect of the present invention, a method executed at least in part in a computing device for providing cloud based skip tracing is provided. The method includes providing a cloud based service enabling data interchange with a plurality of vendors providing skip tracing services and receiving at the cloud based service and from a user a file of records for skip tracing. The method further includes applying a waterfall process to the records using the computing device wherein the waterfall process includes at least a subset of the plurality of vendors and returning to the user a results file containing skip tracing results corresponding to the records. The method may further include generating a waterfall score card and sending the waterfall score card to the user, the waterfall score card summarizing performance of the subset of the plurality of vendors.

According to another aspect of the present invention, an apparatus is provided. The apparatus includes a server operatively connected to a network. The server is configured for providing cloud-based skip tracing.

According to another aspect of the present invention, a method executed at least in part in a computing device for providing cloud based skip tracing is provided. The method includes providing a cloud based service enabling data interchange with a plurality of vendors providing skip tracing services and providing a client user interface to clients of the cloud based service wherein the client user interface provides for mapping fields of a client file to a standard input file layout. The method further includes providing an administrator user interface to administrators of the cloud based service wherein the administrator user interface provides for specifying a file layout for files from a vendor though file mapping and establishing a testing status for the vendor. The method further includes receiving at the cloud based service and from a user a file of records for skip tracing, applying a waterfall process to the records using the computing device wherein the waterfall process includes at least a subset of the plurality of vendors, and returning to the user a results file containing skip tracing results corresponding to the records.

According to another aspect a method executed at least in part in a computing device for providing cloud based skip tracing is provided. The method includes providing a cloud based skip tracing service enabling data interchange with a plurality of vendors providing skip tracing services, providing a registration process for the cloud based skip tracing service, the registration process being a common registration process for a plurality of products or services including the cloud based skip tracing service, providing a billing process for the cloud based skip tracing service, the billing process being a common billing process for the plurality of products or services including the cloud based skip tracing service, receiving at the cloud based service and from a user a file of records for skip tracing, applying a waterfall process to the records using the computing device wherein the waterfall process includes at least a subset of the plurality of vendors, and returning to the user a results file containing skip tracing results corresponding to the records.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a diagram illustrating one example of a system of the present invention.

FIG. 2 is a diagram illustrating one example of a method.

FIG. 3 is a flow diagram illustrating a method for processing a client input file.

FIG. 4 is a flow diagram illustrating processing of a record.

FIGS. 5 A and 5B illustrate a method for processing an input file.

FIG. 6 illustrates a method relating to a results file prepared for a client. FIGS. 7 A and 7B illustrate an example of decision tree with four layers of custom criteria.

FIG. 8 illustrates three different examples of waterfall processes in comparison to a conventional process.

FIG. 9 is a screen display of an example of a login screen.

FIG. 10 is a screen display showing a dashboard.

FIG. 11 is a screen display showing selection of an input file.

FIG. 12 is a screen display showing selections of a product package.

FIG. 13 is a block diagram illustrating the analysis of return files to assist in building models or waterfall score cards.

FIG. 14 to FIG. 18 illustrate a file map wizard tool which may be made available to clients to setup and store file layouts specific to clients.

FIG. 19 to FIG. 24 illustrate a vendor test module.

FIG. 25 is a screen display which allows different product packages to be selected for an uploaded file.

FIG. 26 illustrates a system 2600 which allows for a common registration process.

DETAILED DESCRIPTION

FIG. 1 illustrates one example of the present invention. In FIG. 1, a system 10 is shown which includes a host 12. The host 12 may be a web server or other type of server or other computing device which is operatively connected to the "cloud" 14. As used herein, the "cloud" refers to a network such as a wide area network such as the Internet. Various client devices such as computers 16, tablets 18, smart phones 20, or other computing devices may also be in operative communication with the cloud 14. Also shown in FIG. 1 are a number of vendors 22, 24, 26, 28. These vendors may provide various services for skip tracing through online or electronic databases or other means. These vendors may offer their services through the cloud 14 to the host 12, although the services may otherwise be provided. Where computing devices within the system are used, it is to be understood that the computing devices may be programmed with instructions for performing various functions. Such instructions may also be stored on non-transitory computer readable storage media. The host 12 preferably has an associated computer readable storage medium with instructions for performing various functions or methods as described herein. FIG. 2 illustrates an example of a process 100 which the host 12 may be programmed to perform. In step 101 client data is received. The client data may be in the form of a file containing names and/or other information or records. In step 102 waterfall logic is applied. The waterfall logic applied may be based on client preferences, default logic, or other logic regarding the manner in which services and products of vendors should be used in order to provide skip tracing. In step 104 results obtained from various services and products of vendors are analyzed in various ways such as to validate results and remove duplicates or dedup. Various types of validation checks may be applied in order to validate results. For example, a validation check may be performed on any phone number or address received from a vendor before passing onto the client as a result. The skipped result may be crosschecked against tables or information for legitimacy. For example, area code and prefix combinations for phone numbers may be checked to determine validity and state and zip code combinations may be checked to determine validity. Skip results that fail the validation check may be rejected and not returned to the client as a hit.

A dedup process may be used because the vendor skip searches may provide the same information for multiple records. Therefore, dedup processes guard against providing duplicate information to the client. Dedu processes may be run at the vendor and upon receipt of a hit from a vendor. Deduping may be performed on phone numbers, addresses, or email addresses. It is contemplated that for some types of fomiaiion it may be preferable that dedup processes not be performed such as for results associated with products directed towards obtaining bankruptcy, deceased, or incarcerated information where the result can be relevant if the same information is returned multiple times. Irs addition, the dedup process may be performed against information, such as phone numbers, which are provided by the client as a part of the client data in ars input file. Also, the dedup may be configured to skip results that have been previously returned to the client for a particular record.

It is further noted that cost or time constraints may be applied as a part of the waterfall logic applied. One example of a cost constraint may be that a client selects to set a maximum cost per waterfall. Such a setting allows a client to control the cost incurred per record for each waterfall. Once a record reaches the maximum cost, the record is rejected from skip tracing and returned to the client. Thus, the maximum cost per waterfall is one example of a cost constraint that may he set.

One example of a time constraint may be allowing a client to set a time frame for receiving results files. This constraint may be used to return to the client a results file if the time limit has expired before the waterfall finishes processing. The waterfall will continue to process and return any results in a separate file. This feature also provides a failsafe mechanism against potential vendors' processing issues. Due to the waterfall process being dependent on multiple vendors, if one of those vendors is having system issues, processing ma y still continue without delaying the return of results to the client.

Returning to FIG. 2, in step 106, after processing, results may be delivered to the client. The present invention further contemplates any number of different types of reporting. One such example may be a processing report. A processing report may be an automated report sent back to client to show results of files submitted. This report may be by file and may include the file's batch number, hits, and number of phone numbers received. This report may be kept by the client for reconciliation purposes. Another type of report may be an at-a-glance report. An at-a-glance report may be a static report that is viewed through the cloud-based service and may provide an o vervie of the waterfall statistics for a given time period. Preferably an at-a-giance report provides summary information for the most used waterfalls based on number of records submitted. Other reports may include dynamic reports such as those that a user may create. In addition, reports may be generated from result data returned to the client to show waterfall accuracy statistics as will be later explained herein.

Thus, a cloud-based service is provided which manages the data interchange with a plurality of vendors providing skip tracing services according to waterfall logic which identifies and/or sequences different products and services of the different vendors.

FIG. 3 illustrates a process 300 which may be performed when a client provides a data file. In step 302 the incoming file from the client is shown. In step 304, a

determination is made as to what service level is requested. The present invention contemplates that any number of different service levels may be provided and different features may be provided based on the service level. In this example, a basic service level is provided and a conditional service level is provided. Both service levels provide for deduping skip information, validating phone numbers and addresses and dynamic reporting. The basic level of service uses an automatic skip trace waterfall. The conditional service level allows the client to customize the application of the waterfall logic. If the service level is basic, then in step 306 a custom insert field may be read, the customer insert field may be used to specify a particular waterfall to use. The custom insert field may include a waterfall indicator code to indicate a particular waterfall to use. In step 308 a determination is made as to whether the custom insert field is blank. If it is, then in step 312 the record may be sent to be processed using a default waterfall.

Alternatively, if the custom insert is not blank then in step 310 a determination is made as to whether the value in that field is a valid waterfall. If it is then the record may be processed using the specified waterfall. If the value is not a valid waterfall then in step 316 a rejected report may be generated including reporting on the fact that the specified waterfall was not recognized as valid.

Returning to step 304, a determination may be made that the service level is conditional. When the service level is condition, users may customize the application of the waterfalls such as to use more than one waterfall per product package without creating multiple files. If the service level is conditional, then in step 318 the custom insert field may be read. In step 320 a determination is as to whether or not custom insert field is blank. If it is, then in step 322 conditionals may be used to determine the appropriate waterfall. If not then in step 324 a determination is made as to whether the value within the field is associated with a valid waterfall. If it is then in step 326 the record may be sent to the waterfall. If it is not then in step 316 information about the invalid entry may be included in a report.

FIG. 4 illustrates a method 400 for further processing records. In step 402 records from the service level process shown in FIG. 3 may be received. In step 404, client waterfalls may be ordered in descending order to the date created. In step 406 a determination is made as to whether records meet the conditional statements. If not then in step 408 any record which does not meet the conditional statements may be rejected. For records which meet conditional statements, in step 410 a determination is made as to whether records meet more than one conditional statement. If not, then the records may be sent to the waterfall in step 412. If the records do meet more than one conditional statement, then in step 414 the records are sent to the oldest active waterfall in step 414. FIGS. 5A and 5B illustrate a method 500. In step 502, input is received from a client. In step 504 an acknowledgement report may be produced. Such a report may be communicated to the client. In step 506 a product package may be determined by the name of the input file although the present invention contemplates that product packages may otherwise be identified. Product packages may be pre-determined combinations of skip tracing product offerings. The package selected is used to determine the information on which the skip activity will be conducted. It may be used as an indicator of what vendors are available for any particular waterfall. In step 508 a determination may be made as to the service level such as basic or conditional. If the service level is conditional then in step 510 a decision tree may be used to determine a waterfall. Returning to step 508, if the service level is basic then in step 512 a waterfall may be applied as directed.

In step 514 a summary report may be generated which may include totals by waterfall, the records which were rejected, or other information. Then in step 516 a vendor input file may be created from the client input file. In step 518 the input file may be sent to a vendor. In step 520 skip results may be returned from the vendor. Next, as shown in FIG. 5B, in step 522 a determination is made as to whether a record received a hit. If not then in step 524 a determination is made as to whether the cost after obtaining the record meets the maximum allowable cost. If not then in step 528 a determination is made as to whether there is a next vendor in the waterfall. If there is then the process returns to step 516 in FIG. 5 A by creating a vendor input file from the client input file for the next vendor. If there are no more vendors in the waterfall then the process proceeds to step 526 where results from the vendor are temporarily held. Returning to step 522, if the record did receive a hit then the process also continues to step 526. Returning to step 524 if the record does meet the maximum allowable cost the process also continues to step 526.

After the results from the vendor are temporarily held in step 526, in step 530 a results file may be created to send to a client. A separate results file may be provided for each waterfall. In step 532, a results report is produced. In step 534 the results file may be sent to the client. In step 536 a file status check may be performed.

FIG. 6 illustrates a method 600 for managing a result file which is made available to a client such as on a file transfer protocol (ftp) site or a secure file transfer protocol (sftp) site. As shown in FIG. 6, at step 602 a file is waiting to be downloaded. In step 604, a determination is made as to whether or not the file has been downloaded. If it has, then the received information from the client may be input in step 612. If it has not been

downloaded, in step 606 a determination is made as to whether the file has been waiting for a set period of time (such as 10 days in this example). If it has, then in step 614, a notification may be sent to the client warning that the file is waiting to be downloaded. If the file is still waiting to be downloaded after another set period of time (such as 20 days total in this example) in step 608, then in step 616 a notification may be sent to the client warning that the file is waiting to be downloaded and will be deleted after a set period of time (such as in 10 more days). A determination is made in step 610, a determination is made as to whether the file has been waiting for a client for another set time period (such as 30 days total in this example). If it has then in step 618 the file may be deleted from an FTP site where the file has been waiting to be downloaded by the client. In step 620 an email notification may be sent to the client that the file has been deleted.

It is to be understood that making a file available on an FTP web site is merely one way that a file may be delivered to a client. Doing so is convenient in that the client may immediately access the file if desired while at that same time recognizes that files may very large and thus not conducive to being sent via email or similar means. However, it is contemplated that files may be communicated in any number of other ways including alternative electronic means or may be delivered on physical media, or other means as may be appropriate with a particular implementation of the invention.

FIG. 7A and 7B illustrate a decision tree 700 with four levels of custom criteria.

Actual custom criteria used may be selected by a client and may have more or fewer levels. In step 702 an input file is received from a client. In step 704 a first balance range has an associated first age range 706 and a second age range 708. For the first age range 706, there is a first score range 710 and a second score range 712. For the second age range 708 there is a first score range 714 and a second score range 716. For the first score range 710, there is a first phone range 718 and a second phones range 720. Similarly, for the second score range 712, there is a first phones range 722 and a second phones range 724.

Similarly for the first score range 714, there is a first phone ranges 726, and a second phones range 728. For the second score range 716, there is a first phones range 730 and a second phones range 732. For each phones range there is an associated waterfall 734, 736, 738, 740, 742, 744, 746, 748. Fig.7B illustrates a second balance range 750 with a first age range 752 and a second age range 754. For the first age range 752, there is a first score range 756 and a second score range 758. For the second age range 754, there is a first score range 760, and a second score range 762. For the first score range 756 there is a first phones range 764, a second phones range 766. For the second score range 758, there is a first phones range 768 and a second phones range 770. For the first score range 760, there is a first phones range 772 and a second phones range 774. For the second score range 762, there is a first phones range 776 and a second phones range 778. For each phone range there is an associated waterfall 780, 782, 784, 786, 788, 790, 792, 794.

After the waterfalls, in step 796 a determination made as to whether or not the record met the maximum cost per waterfall. If it has, then in step 798 the record may be returned to the client as rejected. If not, then in step 799 the record can be sent to vendors.

FIG. 8 compares a conventional process to different examples for various embodiments of a waterfall 800. A conventional process 802 is shown as well as a first waterfall process 804, and a second waterfall process 806. In the conventional process 802, a record is sent for skip tracing in step 808. In step 810 a decision is made to determine a first vendor 812. Then in step 814 a decision is made regarding additional vendors 816. In step 818, a decision is made regarding another vendor 820. Thus, the process involves a number of discrete steps regarding decisions to make at every step of the process with attendant delays every time a decision is needed.

In the first waterfall 804, in step 822, the record is sent for skip tracing. In step 824 a decision tree is applied and in step 826 a waterfall is provided which defines a sequence of vendors. In the second waterfall 806, in step 828, the record is sent for skip tracing. A first model 830 may be applied as well as a second model 832. The first model may have a probability of a hit 834 and a second model may provide a probability of RPC 836. A formula 838 may be applied to provide a waterfall 840 which includes a sequence of optimal vendors. Thus, the first waterfall 804 and the second waterfall 806 both provide significant advantages over the conventional process 802.

In FIG. 9, a screen display 900 is shown which allows a user to select a registration button 902 if they have not yet registered to use the system. If the user has already registered, then they may enter their username 904 and password 906 and select the login button 908 to login. FIG. 10 illustrates a screen display 1000 which may be presented to a user after they have logged into the system. Menu items 1002 are presented near the top of the screen display. In addition, a user can specify a file to upload 1004. They may also select a product package 1006. In addition, file status information 1008 is provided. FIG. 11 illustrates a screen display 1100 and provides a dialog box or window 1010 where a user may choose a file to upload. The present invention contemplates that files may be uploaded in a standard or pre-defined format. In addition, it is contemplated that file map wizard or other tool may be used to allow the user to send files in any format. With such a tool a user may be taken through a series of steps to map their own file layout.

FIG. 12 illustrates a screen display 1200 which allows a user to select the type of product package. The present invention contemplates that various types of product packages may be used. For example, different types of product package may include the type of skip trace information to be determined. This may include address only, address and phone, phone only, email address, or other information. The type of product package may also be associated with the purpose of the search. For example the search may relate to bankruptcy, incarceration, litigation, or other purposes. The below table illustrates example of product packages and the type of skip data which may be returned. Of course, the present invention contemplates that any type of skip data may be used as may be appropriate for a particular industry or for particular circumstances. It is to be further understood that a particular file may be sent through multiple product packages of a user's choice.

Product Package Skip Data Returned

Phones Search Phone Numbers

Contact Information Phone Numbers

Address

Email Address

Place of Employment Employer Name

Employer Address

Employer Phone Number

Employee Position

Employee Verified Flag

Deceased Scrub Deceased Flag

Deceased Date

Incarcerated Scrub Incarcerated Flag

Date of Incarceration

Incarcerated Location

Cell Phone Search Phone Numbers

Cell Phone Indicator

Litigious Persons Search (Basic) Litigious Person Indicator

Litigious Persons Search Litigious Person Indicator

(Premium) Attorney Information

FIG. 13 illustrates a diagram illustrating a waterfall scorecard. In system 1300 an analysis component 1304 is provided to produce a waterfall scorecard 1306. The waterfall scorecard 1306 provides for advanced level reporting on the accuracy of the skip vendors. It may use an additional return file 1302 from the client with validation information per skip result to match with the source vendor. The return file 1302 from the client may provide unique phone/account level information that identifies which phone number received which result. This data may come in transactional style. In one embodiment, the data may include: a unique identifier, a responsible party code (RPC) phone number and date, a work number phone number and date, attempt and date, any other action taken on a phone and its date. The matched data may be summarized and returned to the client. The client can use the scorecard 1306 to determine how well each of their vendors are performing, and make adjustments to their waterfall (s) as necessary. As the source information is not generally returned to the client, generic names (e.g. "generic vendor Y "vendor 2," etc.) may be used to identify vendors in the scorecard.

Analytics may be also be used to create models based on information using the analysis component 1304. It is contemplated that data returned by a client may be either part of the collective or logically removed from all other data and not used in the collective analysis. Clients may be given a choice of being part of the collective and receiving the benefit of a large data set or not to be. The collective data will be used to create models 1308 that will predict the probability to contact the consumer. It is contemplated that models 1308 may be industry specific models, or based on other information.

A record sent for skip tracing may then use an existing model to determine the probability of a hit per vendor and the expected probability of contact per vendor. The combination of the two probabilities may be used to determine the best vendor for that record. This vendor determination process may be used for phone number skip tracing or skip tracing for other types of contact information.

FIG. 14 to FIG. 18 illustrate another aspect which provides for a file map wizard tool which may be made available to clients to setup and store file layouts specific to clients. Thus, instead of using only files in a specific file layout, such as a tab delimited text file, other file layouts may be used. The file map wizard may import a sample file and map the client's fields to the a standard layout. This information may be stored and then when other files are received from the client such a format will be expected. At any time, a client may edit their file format settings should they have need to change their file formatting.

FIG. 14 illustrates a File Map Wizard window 1400. A first step is shown which allows a user to select a sample file by entering the file location within the text box 1402 directly or using the browse button 1404 to find the file. A preview of the file is shown in text box 1406. A next button 1408 and cancel button 1410 are also shown.

FIG. 15 illustrates a second step in which data within the file is defined including the text format, the presence or absence of a header record and a preview of the file selected. As shown in FIG. 15, text format 1412 is selected such as a fixed columns format or a delimited field format. Where a delimited field format is selected the type of character or symbol used to delimit fields may be selected such as a tab, comma, space, semicolon, or other character or symbol. Information regarding the header record 1414 may be selected including whether the file contains field names on a particular record number and if so the record number as well as where the data records begin. The preview 1416 is also shown.

FIG. 16 illustrates a fixed column text format being selected and a different preview

1418 which shows column numbers.

FIG. 17 illustrates a third step which includes defining individual data field formats. A shown in FIG. 17, a grid 1420 provides a fields column 1422, a field type column 1424, and a field format column 1426. Examples of field types may include date, dollar, number, text. The field format depends upon the field type. Thus, for example where the field type is date, the field format may include different data formats.

FIG. 18 illustrates a fourth step of mapping file fields to corresponding location in a file layout. Fields may be dragged from a your file column 1428 to the ClientIN File column 1432, or selected and moved using arrow 1430. Some fields may not be mapped and thus may remain in the Your File column 1428. A finish button 1434 is also shown to complete the file mapping process by closing out the file mapping wizard and creating the records necessary to apply this file format for future files received from the client.

Although various details regarding one embodiment of the file map wizard are shown in FIGS. 14-18, it is to be understood that different options, variations, and alternatives are contemplated. For example, instead of a single default file mapping which may be defined for a package of a client, the system may allow for choosing between different file mappings specified by the client. In addition, although various field formats and file layouts are described, other types of field formats and file layouts may be used as may be appropriate in particular situations.

Another aspect relates to a vendor test module which is shown in FIG. 19 to FIG.

24. As previously explained, numerous different vendors may be accommodated.

However, when considering a new vendor or an existing vendor's new product offering, the new vendor should be tested. However, in order to test, a certain amount of effort would be needed to generate and process test files, then create the necessary SQL Server Integration Services (SSIS) packages to include the vendor in production, along with the other vendors. This aspect provides a module that makes on-boarding vendors simple and streamlined. The module allows for entering in file information (format, mapping, name, SSIS creation, etc.) and promoting a vendor into production.

In one embodiment, to set up a vendor in the test module, an Admin enters the vendor's business information on the setup page and a testing status of "Evaluation" may be specified. Testing status allows files with the vendor to be processed but without including the vendor in any active waterfalls as only "Active" vendors can be included in waterfalls.

Next, the Admin may provide the system with the file details using a File Mapping Wizard. FIG. 19 illustrates a first step using the File Mapping Wizard. A window 1900 is shown which allows a file direction 1902 to be specified. The file direction may be ingoing (e.g. "To LocateSmarter") or outgoing (e.g. "From LocateSmarter"). The file direction indicates whether a file is to be accepted or created. If the file direction is ingoing, the vendor is returning a results file and the system needs to be able to read the file. If the file direction is outgoing, the system is creating the file to send to the vendor. A sample file may be selected 1904 and specified in text box 1906. File name elements 1908 may be specified. This involves selecting element types such as from dropdown list boxes 1910, 1914, 1918. Examples of element types include hardcoded text, date (generated), underscore, extensions, sequence number or other type. Depending upon the element type selected a text box 1912, 1920 may be displayed. For example, where hardcoded text is selected from the dropdown list box 1910, the hardcoded text may be specified in the text box 1912. Once this step is completed, a user may select the next button 1922 to proceed to the next step or the cancel button 1924 to cancel.

FIG. 20 illustrates a next step in which the data within the file including a declaration of the text format 1926, the header record 1928, and a preview of file 1930. The text format 1926 can be fixed columns or delimited fields. The header record can indicate if one is present that field names are present and at which record. The header record can also indicate at which record the data records starts. Once this step is completed, a user may select the next button 1922 to proceed to the next step or the cancel button 1924 to cancel.

FIG. 21 illustrates the same step as shown in FIG. 20, except that the text format

1932 specifies a delimited field format, allowing the manner in which fields are delimited to be specified as well and a different preview 1934 is shown. Once this step is completed, a user may select the next button 1922 to proceed to the next step or the cancel button 1924 to cancel.

FIG. 22 illustrates the screen shown in FIG. 20 except showing the 1936 with fixed columns after the preview is generated. Once this step is completed, a user may select the next button 1922 to proceed to the next step or the cancel button 1924 to cancel.

FIG. 23 illustrates a next step in which individual data field formats may be defined. This screen 1940 includes a grid 1942 with a field name column 1944, a field type column 1946, and a field format column 1948. The field name column 1944 includes field names from the sample file. If the file contains a header record then the values in this column should be the corresponding text from the sample file. If the file does not contain a header record then the values in this column may be generic such as Field 1, Field 2, Field 3, ..., Field n. The Field Type column may contain values from drop down lists.

Examples of field types could include Date, Dollar, Number, Text, etc. The Field

Formation may contain drop down lists for selecting the specific data format. The contents of these dropdown lists are dependent upon the field type. For example, if Date is selected as a Field Type, the Field Format drop down may include options such as MMDDYYYY, YYYYMMDD, MM/DD/YYYY, MM/DD/YY, etc. Once this step is completed, a user may select the next button 1922 to proceed to the next step or the cancel button 1924 to cancel.

FIG. 24 illustrates a next step in mapping the file fields to its place in the database.

The database fields need not be actual table and field names but may be a description of what the field is. As shown in FIG. 24, a column for file fields 1950 is shown and a column for database fields 1952 is also shown. The mapping may also indicate that a particular file field is not mapped to a database field. Once mapping is complete, a user can select a finish button 1954 or may select a cancel button 1924 at any time. Once the mapping is complete the file mapping wizard closes and a SSIS package is created for this vendor with the specified file direction.

Once the files are mapped and the SSIS packages are created, the vendor testing can begin. Testing can occur with actual name, SSN, and date of birth combinations. The test module may be able to generate a test file on command. An Admin may have a form on the user interface in which they specify what to include in a test file. The specification may include the number of records to include in the test file, a checkbox to mark fields other than Name, SSN, Date of Birth and Address as blank, a drop down list box to select from which client to use for a test account population, and a text box for inputting the comment that should be stored for the transactions. The Admin may then select a Create Test File button to generate a test file. Thus, in this manner vendor services may be tested. When the vendor is ready to be moved into production, the Admin may simply change the status from Evaluation to Active. This enables the vendor to be included in production waterfalls.

Once a vendor is approved, it may be added to waterfalls in the normal manner such as that shown in FIG. 25. FIG. 25 illustrates a screen display 2500 which allows a file to be selected in the input box 2502. The file may be located using a browse button 2504. One or more product packages may be selected such as by selecting checkbox such as the phones number search box 2506, the place of employment search 2508, the bankruptcy scrub 2510, the deceased scrub 2512, and the incarcerated scrub 2514. For each of the selected product packages either the system default waterfalls checkbox 2516 may be selected or a corresponding drop down lists 2518, 2520, 2522, 2524, 2526. The file may then be uploaded by selecting the upload button 2528.

According to another aspect of the invention, the skip tracing service may use billing and registration processes which are common to other products. One of the advantages of sharing billing and registration processes across multiple product lines is to permit easy integration when cross-selling products.

FIG. 26 illustrates a system 2600. The system 2600 includes a common database 2602. The common database stores information obtained from the registration process and for cross-selling product notifications. Examples of different products are shown including Locate Smarter 2608, a second product 2610, a third product 2612, a fourth product 2614, a next product line 2616. In addition, a common database 2604 is shown for storing information related to billings. The Locate Smarter 2608 product shown here may be the cloud-based skip tracing application previously described herein.

Thus, a cloud-based service has been described which manages the data interchange with a plurality of vendors providing skip tracing services according to waterfall logic which identifies and/or sequences different products and services of the different vendors. The present invention contemplates numerous variations, options, and alternatives as may be appropriate in different circumstances. The present invention is not to be limited to the specific embodiments described herein.