Exception Reports

OnBase Exception Reports recognizes relationships between a base document type and one or more secondary document types and generates reports on missing, matching, or aged items. The OnBase Exception Reporting module allows users to create reports based on a keyword relationship between document types. The reporting capability queries the OnBase database for indices found on one document type to validate the presence of complementary document types with the same indexing information. Any absent documents or index discrepancies are reported to the user. This allows the user to be alerted to documents that are expected, but have not yet been brought into the OnBase system.

Application

There are two types of Exception Reports available within the OnBase system: Basic Exception Reports and Advanced Exception Reports.

Basic Exception Reports can indicate a missing secondary document relating to a primary document, or vice versa (a one-to-one relationship). For example, a shipping company decides to track shipping labels to determine the receipt of packages. There are two document types: shipping labels (primary) and receipts (secondary). The unique matching keyword found on both documents is the shipment number. If 100 packages were shipped with their respective shipping labels, and only 99 receipts were returned, the Basic Exception Report would indicate the missing receipt, as well as the shipment number for the missing receipt. Now, the shipping company can effectively follow-up with the driver or the customer to determine what happened to the missing receipt or whether the delivery actually occurred.

In addition, amount keywords on secondary documents can be totaled against the amount keyword on the primary document. If the sum of the amounts on the secondary documents does not match the amount on the primary document, the report will reflect such discrepancies.

Advanced Exception Reports compare more than two document types. Advanced reports can report on documents from both a primary document type and multiple secondary document types (a one-to-many relationship). Advanced Exception Reports will find any missing documents.

For example, a bank has several loan applications on file that have related documents such as titles, credit reports, and surveys. All of these items can be retrieved via matching keyword types such as loan application number, which exists on all document types. Code keywords can be used to distinguish between different types of loan applications, such as a house, education, or car loan application. The bank decided that the number 20 will equal an education loan and 30 will equal a car loan. The code keyword values assigned tell the system which documents to expect for each type of loan. An education loan has four corresponding documents, but a car loan only has three corresponding documents. Any missing documents for each loan type are reported. Advanced Exception Reports also allow users to place ticklers on documents to bring attention to such tasks as renewals, re-certifications, etc.

Core Features

• Identify missing and matching documents within the system (one-to-one relationships and one-to many relationships)

• Unlimited document Exception Reporting

• Maintain system integrity between documents in the OnBase system

• Place ticklers on documents to bring attention to renewals and re-certifications