This invention relates to interfaces in a check testing environment. More specifically the invention relates to simplifying the interfaces in a check testing environment.
Conventional interfaces in a check testing environment may be complex and cumbersome. The task configuring data required for creating check records in a check testing environment allows mistakes and inaccuracy.
In addition, the required data creation may be time-consuming and therefore costly, which may make the current system a sub-optimal system.
Therefore, it would be desirable to simplify the data entry interface in a check testing environment. The simplification may reduce the number of fields required in creating check records.
Furthermore, it would be desirable for the system to set the various fields that do not require user data entry, to a default value, thereby simplifying and shortening the process for creating check records for use in a check testing environment.
Interfaces, according to some embodiments, may be configured to accept user input relating to a first subset of user configurable entry fields. Such entry fields may be selected from a larger plurality of entry fields.
The first subset of user configurable entry fields may include a check image date text entry field. The check image date text entry field may accept user input relating to a date of a check.
The first subset of user configurable entry fields may also include a check image DPI (dots per inch) text entry field. The check image DPI text entry field may accept user input relating to a DPI of the image of the check.
The first subset of user configurable entry fields may also include an encode magnetic ink character recognition (“MICR”) line on generated check checkbox. The MICR line on generated check checkbox may be configured, when selected, to transmit an electronic instruction to encode MICR line information on the check.
The first subset of user configurable entry fields may also include a draw courtesy amounts on generated check checkbox. The draw courtesy amounts on generated check checkbox may be configured, when selected, to transmit a second electronic instruction to draw courtesy amount information on the check. Courtesy amount information is information that reflects the value of the check and is written in numeric form on the face of the check.
The first subset of user configurable entry fields may also include an encode MICR line amounts on generated check checkbox. The encode MICR line amounts on generated check checkbox may be configured, when selected, to transmit a third electronic instruction to encode MICR line amounts information on the check.
The first subset of user configurable entry fields may also include a draw legal amounts on generated check checkbox. The draw legal amounts on generated check checkbox may be configured, when selected, to transmit a fourth electronic instruction to draw legal amounts information on the check.
The method may further include defining a second subset of entry fields. The second subset may include the plurality of entry fields excluding the first subset of entry fields. The second subset may include numerous entry fields.
The method may further include setting each entry field from the second subset of numerous entry fields to a non-user-configurable default value and a concealment attribute.
Furthermore, the method may include tagging each of the entry fields set to the non-user configurable default value, with a concealment tag such that a user can not view those fields. This setting enables the user to experience a more simplified method for creating check records to be used in the check testing environment.
The method may further include enabling the second subset of entry fields to be user configurable upon entry of a password.
The objects and advantages of the invention will be apparent upon consideration of the following detailed description, taken in conjunction with the accompanying drawings, in which like reference characters refer to like parts throughout, and in which:
Some embodiments involve a method for providing a graphical user interface in a check testing environment. Certain embodiments may simplify such an interface over conventional interfaces.
Interfaces according to certain embodiments may provide a text entry field table. The text entry field table may be configured to accept user input relating to a plurality of check records. The check records may be suitable for use in the check testing environment.
The text entry field table may include a record type column. The record type column may accept user input relating to the plurality of check records. The record type column may define each check record to be either a debit or a credit.
The text entry field table may also include an auxiliary serial number column. The auxiliary serial number column may accept user input relating to the plurality of check records. The auxiliary serial number column may define each check record's auxiliary serial number.
The text entry field table may also include an account number column. The account number column may accept user input relating to the plurality of check records. The account number column may define each check record's account number.
The text entry field table may also include an amount column. The amount column may accept user input relating to the plurality of check records. The amount column may define each check record's total amount.
The text entry field table may also include a return reason code column. The return reason code column may accept user input relating to the plurality of check records. The return reason code column may describe, when applicable, the reason for the rejection of the check.
The text entry field table may also include a routing transit number column. The routing transit number column may accept user input relating to the plurality of check records. The routing transit number column may define each check record's routing transit number.
The method may further include inputting data into a check record from the plurality of check records. Upon receipt of the data, the method may search using a check testing system. The searching may identify duplicates of received data. Upon determining that no duplicates exist in the database for the inputted data, the check testing system may be configured to save the data as a check record in the database.
According to some embodiments, the method may provide, on a first graphical user interface, a text entry field table which accepts user input relating to a plurality of check records to be used in the check testing environment.
According to some embodiments, the method may provide, on a second graphical user interface, a text entry field table which accepts user input relating to a plurality of check records to be used in the check testing environment.
Some embodiments involve a four-quadrant graphical user interface.
The apparatus may present an upper left quadrant displaying either a check date text entry field configured to receive data related to the date of the check or an image DPI text entry field configured to receive data related to the DPI of the image of the check.
The apparatus may also present an upper right quadrant displaying either a check date text entry field configured to receive data related to the date of the check or an image DPI text entry field configured to receive data related to the DPI of the image of the check.
The apparatus may further present a lower left quadrant displaying the check-image related options and a lower right quadrant displaying the actual check image.
Step 210 shows loading preferably, previously-used, pre-conditioned test data. The pre-conditioned data is data that has already proven the desired outcome. The previously-used, pre-conditioned test data together with the data repository, shown at 212, may be transmitted to test data store interface 214. Test data store interface 214 may return sanitized data from the received data. The sanitized data may be data with specified fields omitted, enabling the data to be agnostic—i.e., non-traceable to an actual transaction. Test data store interface 214 may add name and/or address information to the data. Test data store interface 214 may also provide test region information for the data. The returned data may be loaded into a database, as shown at 216. The data may require additional pre-conditioned steps, as shown at 218. A user may reserve and/or condition the data when necessary, making it suitable for a specific test scenario, as shown at 220. In one example, conditioning the data 220, may allow the user to change a character thereby enabling the test data to return the data as “invalid.”
The user may select a region and/or cycle as shown at 222. The user may also select a channel for testing as shown at 222. The user may view and select test data as shown at 224. The user may condition the data and save the data into a database as shown at 226. “File saved” with standard naming convention 228 stores the conditioned data 226.
Print resource 230 locates all files saved at 228 for a “print for” cycle. A print file may be created as shown at 232. A “print for” capture may also be created as shown at 232.
File ingestion resource as shown at 234, locates all files for a pre-determined cycle. An x9 file and print for ingestion is now created as shown at 236.
The check record data table 315 may include record type column 318 which may enable the user to characterize the data as either a debit type of data or a credit type of data.
Another column may include a transaction set number for a single transaction shown at column 320. A single transaction 320 may include a transaction comprising a single credit and multiple debits. A single transaction 320 may also include multiple credits and a single debit. A single transaction may also include multiple credits and multiple debits.
Another column may include an auxiliary serial column 320 displaying the check number. Another column may include a field six column 324 which may identify a unique application such as a return item, a forward or return substitute check or a remotely printed check. Another column may include a routing column 326 which may display the routing number. Another column may include a field four column 328 which when necessary may be used for specific testing for legacy checks such as a military bank check. Another column may include an account type column 330 which may define the user or test account number. Another column may include a transaction code type column 332 which may define the processing to be either debit type processing or credit type processing. Another column may include an amount type column 334 which may define the dollar amount of the credit or debit. Another column may include an item description type column 336 which may describe the scenario of the test. Another column may include a return reason code type column 338 which may define a return reason for a check.
Another column may include the test environment and/or cycle type column 340 which may define a test region from the three standard test regions where the data may be executed. Furthermore, each test region may be used repeatedly. Test environment and/or cycle may also define the iteration of testing where test data will be executed.
Origination routing number 342 may be another column type which may indicate, the drawing bank, for x937 files. X937 files are files that are processed electronically and may need no printing or capturing of items. The destination routing number 344 may be another column type which may indicate, for x937 files, the drawee bank.
Upon selection of a single checkbox from checkboxes 354-380, or upon selection of a plurality of checkboxes from checkboxes 354-380, the system may enable the user to either edit or save the selection of check records. Upon selection of checkbox 352 and option button 382, the system may be configured to save all the data from the check record data table 315 to a new file. Upon selection of checkbox 352 and option button 384, the system may be configured to enable the user to edit all the previously recorded test data.
Thus, systems and methods for simplifying a check testing data interface is provided. Persons skilled in the art will appreciate that the present invention can be practiced by other than the described embodiments, which are presented for purposes of illustration rather than of limitation, and that the present invention is limited only by the claims that follow.