screen for a merchant or sub merchant fig9 shows an interface screen for supervisory review of u201c warning u201d transactions flagged by the system which can be approved rejected or removed by the supervisor using this input screen processing rules may be created and selectively implemented at any of the established control levels in the system in a further embodiment the system may include a process for providing a template type user adaptive system that converts data of both known and unknown configurations into payment instructions this processing method provides a u201c wizard u201d interface for receiving data from other systems and converting the data into usable transaction records this facilitates an ability to process payments generated by legacy merchant systems and a variety of other vendor systems the wizard is configurable to identify relevant fields in any order with any delimiter the input file is transformed into a payment instruction by having an operator or an automated process validate a correlation between data in specific fields and the fields needed for a payment instruction for example date fields are validated as having a date format aba number fields are validated as conforming to a known algorithm for such numbers and as representing a valid institution transaction class codes are verified and amount of transaction fields are validated as having an appropriate numeric format a user interface illustrating the implementation of this process is shown in fig1 16 fig1 is an annotated example of a main screen for this process fig1 through.