Financial & Document Processing Solutions Features

• Complete Scalability

  Infoscore's PayData.NET is ideal for any size processing environment - from 1 item per month to that of organizations which process millions of transactions per month at multiple sites. Because it can be configured to process up to hundreds of thousands of documents per hour, this powerful scalability allows you to expand your system by adding workstations as your lockbox business grows without a costly conversion to a different software platform

• Integration with all other Infoscore Solutions

  All solutions work together as one solution. Integrated solutions include PayData.NET include: Remote Capture Plus, Lockbox & End-User, Merchant Processing, Archive Hosting, Archive Vaulting, Solution Engineering, Ala-Carte Outsourcing and some Specialized Engineering Projects.

• Credit Card & Merchant Processing

  We support VISA, Master Card, AMEX and Discover credit cards using a variety of scanners from simple magnetic strip readers to transports which the images of the front and back of checks, money orders as well as the slot to read credit cards.

  Most merchants have two or three separate deposits taking up to 4-5 days to deposit. We process VISA, Master Card, AMEX and Discover for deposit the next day if settlement takes place before 7pm EST using an all-in-one deposit solution (since August 2009).

  We provide the following equipment and services.
  We can also re-program your existing equipment at no cost in most cases:

  • No Minimums
  • Virtually all credit card terminals
  • ATM terminals including mobile ATMs
  • All-in-one Touch Screens
  • Cash Drawers
  • Printers
  • Portable Wireless Magnetic Reader and Printer
  • Cell Phone POS solutions
  • Scales and Bar Code Scanners
  • Multi-lane bundled discounts
  • Gift and Loyalty Cards
  • Cash Advances based on sales volume
  • Commercial and Residential Loans
  • Provide front page presence of your home page on Google in less than 24 hours

• Multi-Site Operation

  Infoscore's ShareSelect.NET module can be configured to operate these functions in any combination over the WEB, Intranet and/or WAN. In this configuration, the scanner functions are performed remotely while all other functions are performed at the central site. They could also be processed off shore. The all-electronic output of Rwiz.NET allows the distribution through Infoscore's InfoCom.NET

  When using with ShareSelect.NET, functions are grouped into these major functions:

  • Scanner - Mail Opening, Banking and Page Scanners
  • System - CarLar.NET, AFP.NET, Database Operation and Image Storage.
  • Operator - Key.NET, IDE.NET, PDAdmin.NET, Rwiz.NET, AccountSetup.NET and use Capture.NET for Images and Data from 3rd parties.

  The Infoscore PayData.NET systems allows you to scan the payments and associated documents (e.g. invoices with detailed information) at remote location and electronically transmit that information to your central operations location for further processing.

  The all-electronic output allows the distribution to all the specified endpoints regardless of geographic location. In the configuration to the left, the scanner functions are performed remotely while all other functions are performed at the central site.

• Transport Independence

  Infoscore's Capture Station supports captured images and data from a variety of scanners as shown below as well as any Twain-supported Page Scanner, and numerous Shoe Box sized Scanners. If your transport is not supported, Infoscore will work with you to have the transport integrated. In the event data and/or images information is already available, the information can be imported into PayData and processed as if the information were gathered by these Capture stations. Infoscore's solution also captures data for images files as supplied from 3rd party capture software.

  Infoscore's Multi-Transport Driver
  
  (Since 1996)

  • CTS • LS Series
  • FUJITSU • All Scanners • Incl. FI5160c
  • IBML • ImageTrac Series
  • NCR • Itran Series • All others
  • OPEX • DS1224 • AS3690I
  • PANINI • MVX Series
  • UNISYS • Quantum• Teller/Branch Scanners • SmartSource Series
  • OTHERS • Shoe Box /Teller Scanners • Page Scanners

• Remote Capture

  Any capture station can be installed remotely and connected to a centralized host system. In fact, all modules can be remotely installed (please see the description of Multi-Site Operation - ShareSelect.NET for a full description). Our "Remote Capture Plus" solution automatically installs all the software to operate and capture images. Captured items can be payments only (Check, Cash, and Money Order) or complete Credit Statement Only (e.g. Invoice, Stub, Statement, Envelope, Etc.) and/or Mixed Statements and Payments.

• Flexible batch/item Types

  • Statements Only - Contains statements (no payments) with each statement being a transaction. Each set of items types can be preceded with an optional "Statement Only" Batch Header.
  • Mixed Statements & Payments - In Retail, each transaction in a batch consists of one or more statement (or coupons) followed by one or more payments. In WholeTail, each transaction consists of an optional envelope, form(s) (e.g. invoices), scannable or non-scannable statement, or any other non-payment followed by one or more payments. Each transaction must have at least one non-payment followed by at least one payment. Each set of items types can be preceded with an optional ""Mixed" Batch Header.
  • Payments Only - Contains only payments (no statements) where each payment becomes a transaction. Each set of items types can be preceded with an optional "Payment Only" Batch Header.

  Custom fields can be attached to any statement and/or payment item including "Check-Centric" remote capture. These custom fields can be entered at the remote or centralized location.

• CAR/LAR

  Infoscore's CarLar.NET (Courtesy Amount / Legal Amount Recognition) .NET service gets the best and most reliable results from CAR/LAR utilizing Infoscore's proprietary settings. MITEK and A2iA CAR/LAR recognition engines are supported as well as A2iA's Check Reader.

• Automated Forms Processing

  Infoscore's AFP.NET classification .NET service identifies the current form based on the image characteristics of the incoming image among the database of previously learned "Form" images. The forms types can be intermixed structured (e.g. Tax Form) or non-structured form (e.g. Invoice). The ICR module reads fields from structured forms and columns plus fields (e.g. Customer Number) from unstructured forms. The results from the iAFP.NET are delivered to iIDE.NET for operator correction and business rule processing (e.g. compare the sum of "Invoice Amount" vs. the sum of "Statement Amount").

• Smart Kill Logic - Amount Input

  Infoscore's Key.NET module is used to Enter/Verify Payment Amounts, Enter/Correct MICR code lines, Enter/Correct OCR scan lines, balance multiple transactions and rejects statement or payments. Payments are automatically killed or have to be killed with amounts input by the operator based on comparing CAR/LAR Amounts, OCR document, ICR due amount area, OCR Document due, and any previously keyed amount. Key.NET is also used to verify that the Statement(s) and Payment(s) of each transaction is in-balance.

• IDE image Data Entry (KFI)

  Infoscore's IDE. NET module operates according to account profile settings configured at account setup. During the operation, the system allows the operator to key from Image Non-Repeating Fields and Repeating Fields, Correct Fields read from iAFP. NET, execute business rules like checking field variances in summed fields to the document amount (e.g. Sum of Invoice Amount "Invoice Amount" to that of the Statement Amount), balance document in transactions by changing the statement amount(s) and/or payment amount(s).

• Exception Processing

  Exception items can be handled throughout the workflow:

  • The Hot/Accept/Look-up Items can detect them
  • Modules can automatically detect (e.g. Foreign Items)
  • The operator can identify and categorize them.

  In all cases the identified exception items are available for review by an operator during a subsequent workflow process "DataQaView" and at Output/Report Generation & Delivery -- Rwiz.NET. Once the operator validates the exception as valid and releases the batch. They are available for archive retrieval.

  
  

  Exception items can be viewed and managed at Rwiz.NET. An "Exception Report" containing context information (e.g. Batch, Transaction and Sub-Transaction and DLN, is supplied to pull the item from the batches. This needs to be done since with Check21 a second pass to out-sort the items during power encode, is no longer required.

• Hot/Accept/Look-Up Items

  This Look-Up module test statement and payments for possible stops. A positive stop is based on the existence information from document matching and entry in a file or database. A negative stop is based on the non- existence information from document matching and entry in a file or database. Types of stops include:

  • Account Number from a scan line
  • Matching the system date to an envelope post mark date or a date some location on the document
  • Statement Amount does not equal the Payment Amount
  • Reject any transactions other than transaction with more than one statement and one payment.
  • Check Routing Number.
  • Custom Field (e.g. Invoice Amount) is equal/greater than or less than the expected amount for an Invoice Number).
  • Or any custom stop.

  The system marks them as a exception item along with a reason code and pocket number. Review of these items is the same as Exception Processing immediately above.

• Advanced Business Rules

  There are three main types of business rules; built-in business rules which are built into our system and configurable by the system administrator, those which are User Exits and a User Exit Sub-System. These advanced business rules is one of many reasons our motto is "the processabilities are endless".

  Built-in Business Rules
  The built-in business rules are numerous for example in IDE where a custom definition includes, attached to which document type, sum for balancing, required, type, one or set, etc. can be assigned to a field.

  User Exits
  To increase flexibility of our product we have built in "User Exit" Context Business Rule System. Business rules are applied at the beginning and end of all components (e.g. headers, images, any document type and trailers) of a batch. Business rules can be in any language that supports XML and are definable in any of the following Boolean entry points:

  • During scanning
  • At the beginning and end of a batch document type
  • Captured batch
  • When a batch is received for processing and the batch process is complete
  • Beginning and ending of a transaction
  • At the beginning and ending of a transaction
  • At the beginning and ending of a document
  • At the beginning and ending of all fields
  • During major other context events (e.g. MICR is read)

  This Boolean diagram below was extracted from our UML documentation:

  
  

  For those customers who have the technical staffing, we offer an optional "PayData.NET/ASPX Exploitation Class" to teach our customers programmers' best practices when exploiting our product. This allows you to add to the product while keeping it compatible with future versions as well as build User Exits and User Exit Sub-Systems.

  User Exit Sub-System
  Virtually anything can be done with a user exit sub-system. Some examples include:

  • Infoscore made a PayData.NET module into a .NET "control" for our customer to embed/compile into their system for operation. The embedded control remains as a workflow step in PayData.NET.
  • Inserting information generated by PayData.NET into the screen of a customer software system.
  • Connect to a customer database for specialized balancing decisions.

• Data Quality Assurance Review

  The module is used to Assure and review items that are identified as stops by the operator or Hot/Accept/Look-Up Items as well as any other areas that "stops" are identified. This module can also execute advanced business rules that interact with remote database with or without user interfaces.

• Output/Report Generation & Delivery

  

  Infoscore's Rwiz.NET creates Reports and Transmissions events for a specific period, and delivers them to local equipment (e.g. Printer) or to InfoCom.NET for electronic delivery.
  
  This module provides a work list for each account each with an associated deadline. Reports and Transmission can be created for a given processing date or range of processing dates. Infoscore's InfoCom.NET module takes any Report and Transmission and delivers them via Email, FTP to specified destinations.

• All Electronic Deliverables

  Deliverables are posted to a secure website for customer access and/or download. Deliverables include (but not limited to):

  • Deposit Detail/Summary Reports
  • Custom Detail Reports
  • Image Files for Download
  • Transmission Files, etc.

  Files can be in PDF, XML, HTML, ZIP, text and other electronic formats.

• Secure Web Client Access

  Authorized users can view current intra-day and past date deposits, view/download reports in PDF and other formats, view/print deposit summary and detail information, image information and search any field for specific deposit information by Payment Amount, Deposit Amount, MICR/ICR/OCR information or any other field.

  Deposit Information includes:

  • Viewing current intra-day deposits amount and counts

    
  
  

  • Viewing previous deposits dates (latest date shown)

    

  • Viewing and downloading in PDF and other formats:

  • List of Reports/Files

    

  • Sample Report:

    

• Searching Information in Deposits

  Searching Information in Deposits

  Deposit Information includes:

  
  

  User can search any field within the deposit information by:

  • Payment Amount
  • Deposit Amount
  • MICR/ICR/OCR/Invoice information
  • Any other field

  Example Search of Deposits

  User can search any field within the deposit information:

  
  

  Account, Batch, Transaction and Custom searches are available. The following search shows a transaction level search:

  • Transaction search Fields

    

  • Search Parameters

    

  • Search Results

    

• Electronic Check21 & ACH Deposits

  Infoscore's Check21 module generates X937 electronic image cash letter files compatible with nearly all banks and financial institutions. Any bank not yet supported can be added in a few days.
  Our Check21 module has:

  • Proven MICR parsing extremely limits the number of deposit rejects.
  • All 9.37 Formats are completely configurable via a User Interface
  • Check21 deposits can be by Bank Profile, Selected Account in Bank Profile and well as a specific Account.

• Billing and Work Tracking

  Infoscore's Billing.NET module is used to collect work information to bill 3rd parties and/or to track the services provided for other departments. Billing information can be computed over any processing date range and delivered to an account analysis system. This billing module supports manual and automatically computed fields. Fields are composed of:

  • Conditional or Non-Conditional
  • By Billing Period, by Month, by Week, by Day, by Batch, by Deposit, by Document, by Field Count, by Field Set, by Field, and by Key-Stroke Calculation
  • All information is linked to Host by Bill Code, Billing DDA Number and DDA Number

• Infoscore Engineered Solution

  All Infoscore solutions are to developed according to our "Product Development Life Cycle" insure upgradability and maintainability and safe up to date technology (Please refer to "ENGINEERED SOLUTIONS OF BUSINESS PRODUCTS FOR BUSINESS NEEDS"
  Avoid Costly Software Rot for more details).

• Strict Security

  

  Infoscore's Security.NET utilizes the new ASP.NET 2.0 security library to provide the security layer for the applications. This security layer provides login control, role manager, logging, auditing, PayData function authorization, and encryption services.
  Security related events include log-on failures when using the Microsoft ASP.NET membership system, attempts to tamper with or reuse forms, authentication tickets, and infrastructure events such as disk access failures, etc.
  By default, all Web error and audit failure events are logged to the Windows event log. Health monitoring uses event providers to deliver event notifications.

• Built-in Upgradability

  Infoscore releases major releases as safe technologies are released and as features are added to our solutions. Each time we do a major upgrade we make sure that modules from the previous major release operate on the new release.
  
  In some cases the link from release PayData.NET release 3.0 will be able to operate release PayData.NET 2.0 and PayData.NET 1.0 and pre .NET releases up to 9 years ago. Compatibility of user exits and user exit sub-systems can be compatible across major versions as long as they are implemented in compliance with methods taught in our "PayData.NET Exploitation Class".
  
  We also provide emulators to operate business rules in previous major legacy versions of PayData in order to protect the investments of our customers. In preparation for an upgrade we extract profiles from the customer site, install the profiles on a VMWARE installation that we maintain at our office for each customer; then we test the upgrade to insure a risk free upgrade experience at the customer site.

• Dashboard (PdAdmin)

  Infoscore's PdAdmin. NET module is used to setup, locate, view, monitor, and manage all administrator function of our PayData system as well as to generate reports. Operators can change batch priority, manage Account Setup profile distribution, manage processing dates, view activity logs, manage workstations, edit batches that have been archived, and run productivity and utilization reports. In addition, the dashboard is used to:

  • Configure and monitor system and operator resources
  • Display work-in-process and workload
  • Manage, Search, Change Priority, Invoke Batch Editing, delete and rollback batches in progress
  • Execute reports for work-in-progress and for date ranges in archive

• Infoscore's Development Languages

  Our products are implemented in C#, VB.NET, AJAX, JAVA and SILVERLIGHT. Infoscore provides backward compatibility with previous versions and custom business rules. We also provide emulators to operate business rules and reports in previous major legacy versions of PayData in order to protect the investments of our customers.