Check Processing with Laserfiche and Checkmation IS120 presented by Brett Voeller Senior Systems Architect

Checkmation’s origins Checkmation SOAR with Remittance Processing was developed for the City of Gilroy to reduce their costs, and streamline their utility bill payment processing workflow. Goals: Reduce in-house labor dedication. Reduce item processing costs from Wells Fargo Bank. Reduce float. Expedite and improve records keeping procedures.

What is Checkmation SOAR’s core process? ScannerVerifierExport

Metadata extraction - Checks Aux OnUs Routing number OnUs Signature Check image (front and back) Payor Payee Check number Legal amount Courtesy amount

Metadata extraction - Remittance stubs Barcode values Key values Stub image (front and back) Name and address

Checkmation can handle payments that contain: One remittance stub and one payment instrument Multiple remittance stubs and one payment instrument One remittance stub and multiple payment instruments Multiple item processing

Payment instruments & remittance stubs are fed through a check scanner. The check scanner derives the MICR data and images the items. 1. Scanner

The batch populates, image by image, into the scanning station program. Partner items are associated in real time. The batch is checked by the operator, then sent on.

2. Server Image quality assurance functions are performed on the payment instrument images. The server performs metadata extraction on payment instruments and remittance stubs. A database table lookup function can be performed to import metadata unavailable on, or difficult to derive from the remittance stubs.

3. Verifier The operator executes his or her verification duties. –Judges images against programmatically extracted data. –Has opportunity to amend incorrectly extracted data or escalate the item to another operator.

4. Admin/Export Batches are automatically checked for duplicate items. Batches are grouped (can be scheduled or manual). Image cash letters are sent to a financial institution (can be scheduled or manual). The document image repository is updated (can be scheduled or manual). Accounting programs is updated with CSV or TXT file exports (can be scheduled or manual).

Remittance payment processing with Remote Deposit Capture, Laserfiche and accounting integration

Laserfiche integration The Checkmation server creates Laserfiche documents based on either the check or the remittance stub. The documents are based on checks only for check batches and on remittance stubs for remittance batches. The Laserfiche properties that are affected by Checkmation are: –Document Volume –Document Name –Document Template –Document Location

Laserfiche integration Document Volume –Checkmation can specify in which volume the document resides. Checkmation obtains the current volumes available in the Laserfiche repository and allows the admin utility to specify a volume for each archive profile. Document Name –A document can have both Literal and Variable names. The Variable names are derived from the Checkmation Batch, Document, Page, and Image Cash Letter properties. Also available are multiple dates that are related to either the batch or the current date of process.

Laserfiche integration Document Template –Checkmation can specify a template and template fields for each archive profile. The template is obtained from a list of templates available in Laserfiche. The template fields can be populated with values from Checkmation Batch, Document, Page, and ICL properties, along with multiple date formats. The template fields can also be populated with Literal values. Document Location –In the same lines as the document name, the folder structure can be a specific path (Literal) or a variable path (depending on a token). The Variable path uses token values from Batch, Document, Page and ICL properties, along with multiple date formats. The document folder path does not have to exist during time of document creation. Checkmation will create it before placing the document in Laserfiche.

Laserfiche integration How Checkmation documents go into Laserfiche –The documents from Checkmation are imported into Laserfiche via LST files. Checkmation uses the Laserfiche Toolkit (API). –LST files are import agent documents that Laserfiche interprets and uses to specify the volume, name, template, template field values, and document location of each document. –Along with those properties, the LST files also contain the image reference where Laserfiche can pick up the image to include in the document.