ImageMark Transaction Manager 4.2.11 Product Update

Transcription

ImageMark Transaction Manager
4.2.11 Product Update
B004-0000-0680
February 23, 2007
The product described in this book is a licensed product of NCR Corporation. Other brand and product names
appearing in this publication are the trademarks or registered trademarks of their respective holders.
It is the policy of NCR Corporation (NCR) to improve products as new technology, components, software, and
firmware become available. NCR, therefore, reserves the right to change specifications without prior notice.
All features, functions, and operations described herein may not be marketed by NCR in all parts of the world. In
some instances, photographs are of equipment prototypes. Therefore, before using this document, consult with your
NCR representative or NCR office for information that is applicable and current.
To maintain the quality of our publications, we need your comments on the accuracy, clarity, organization, and value
of this book.
Address correspondence to:
NCR Waterloo
Attention: Information Engineering
580 Weber Street North
P.O. Box 1611
Waterloo, Ontario, Canada
N2J 4G5
Copyright © 2007
By NCR Corporation
Dayton, Ohio U.S.A.
All Rights Reserved
Contents
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
About This Book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Who This Book is For . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Related Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5
5
5
6
Revision Record . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Chapter 1: Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Image Quality Review (IQR) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Image Quality Review Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Balancing/Block Balancing (Regular and Expert) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Handling IQ Rejects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Choosing a New Entry (Block Balancing Only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10
10
11
11
13
Chapter 2: System Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Managing Workload . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Managing Workload by Unit-of-Work Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Workflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
16
16
18
23
Chapter 3: Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
IQA Test Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Running the IQA Test Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
List File Keywords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
New Keywords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
TP_GLOBAL_PARMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
TP_PSET_PARMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Changes to Existing Keywords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
BANKSITE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
CA_PSETS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
IDT_ADJUSTMENT_CODES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
IDT_ADJUSTMENT_MACRO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
IQR_GEN_PARMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
26
26
27
28
29
29
30
31
31
32
32
35
39
3
Contents
XREF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Activating Auto Adjustments and IQR Reject Processing on Your System . . . . . . . . . . . . . . . . . .
Part 1: Enable the Send-Image-Suspects-To-IQR Feature . . . . . . . . . . . . . . . . . . . . . . . . . . .
Part 2: Set Up IQA Parameters with Carreker Image Engine . . . . . . . . . . . . . . . . . . . . . . . . .
Part 3: Enable Automatic Non-Proofing of Image Reject Documents . . . . . . . . . . . . . . . . . . .
Part 4: Enable IQR Notification for Codeline Mismatch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Activating Support for Externally-Flagged Exception Items . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
43
44
44
44
45
45
46
Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
4
Preface
About This Book
There are several new features in this release of ImageMark Transaction Manager:
!
Prioritizing units of work that come into TM for processing (retaining priority of work coming in
from a different system)
!
Processing all image suspect items at Image Quality Review (IQR) instead of Balancing. New
parameter settings enable Balancing and Block Balancing to automatically non-proof image
reject items and create offsetting adjustments, thus eliminating the need for operators to perform
this task manually.
!
Support for externally-flagged exception items.
Who This Book is For
This book is for bank personnel (system administrators, programmers, and operators). It is also for
NCR personnel who are supporting a customer installation of this solution.
Conventions
Within the procedures described in this book, conventions help you to identify different types of
information.
Bold
Bold identifies anything you must select, choose, run, press, or type. For example:
Type dbscrpt, then press Enter.
Chevrons
Chevrons (>) indicate a series of menu selections. For example:
Choose File > Import > Formats.
Italics
Italics identify a placeholder that must be replaced with your own specific information. For example:
5
Preface
device=c:\path\7780mint.sys type=H.
Italics are also used for emphasis.
Notes, Tips, Important, Cautions, Warnings
Notes, cautions, and warnings alert you to important or critical information. Each is displayed in a
different way:
Note: Notes contain information that has special importance.
*
Tip: Tips contains useful advice for the user on tasks or procedures.
!
Important: Important text contains information to which the reader should pay close attention.
Caution: Cautions alert you to procedures or conditions that could damage equipment or data.
Warning: Warnings alert you to procedures or conditions that could cause personal injury.
Related Information
For more information on ImageMark Transaction Manager, refer to the following books, available
to NCR customers through the NCR Intranet (contact NCR for download instructions):
ImageMark Transaction Manager 4.2 System Administration (B004-0000-0609)
ImageMark Transaction Manager 4.2 Parameter Generation: ASCII Files (B004-0000-0610)
ImageMark Transaction Manager 4.2 Parameter Generation: Application Generator (B004-00000611)
ImageMark Transaction Manager 4.2 Parameter Generation: Host Emulator (B004-0000-0612)
ImageMark Transaction Manager 4.2 Operations (B004-0000-0613)
6
Revision Record
February 5, 2007
Section
Revision
All
New publication
February 23, 2007
Section
Revision
Parameters
Added a step to Part 3 of “Activating Auto Adjustments and IQR Reject Processing on
Your System”.
7
Revision Record
8
1
Operations
This section tells you what the operational changes are for this release of Transaction Manager.
9
Chapter 1: Operations
Image Quality Review (IQR)
Image Quality Review (IQR)
A document flagged as Image Quality Suspect by IQA is presented at IQR, where the operator can
choose to reject it. An Image Quality reject item will be presented at Balancing for further action.
Items that are flagged as Image Quality Suspect items after IQA are normally presented to Balancing
operators for review. An optional parameter (SendImageSuspectsToIQR) can be configured to have
the system redirect these Image Quality Suspect flagged items to IQR for operator review instead
of Balancing.
Image Quality Review Window
This window can now display codeline fields for mismatched codeline items.
For these items, there is a yellow border around the image display area.
To activate these new display features at your site, see “IQR_GEN_PARMS” on page 39.
Image Quality Review Window
10
Balancing/Block Balancing (Regular and Expert)
Balancing/Block Balancing (Regular and
Expert)
Handling IQ Rejects
The system can optionally be configured to automatically non-proof any IQA reject item, and create
an offsetting adjustment for each non-proofed IQ Reject. If the option is activated through parameters
(see “SendImageSuspectsToIQR” on page 31), the balancing adjustments are automatically created
when the batch is first loaded by the Balancing application.
Auto-Balance Messages (Block Balancing Only)
Successful Message
When you select a batch that is out-of-balance, it may become balanced right away. This happens if:
!
the system creates adjustments automatically when you load the batch
!
the auto-adjustments cause the batch to become balanced
If so, the system displays an informative message:
Click OK to clear the message. No further work on this batch is required.
Configuration Problem Message
If the system is unable to automatically non-proof any of the reject items in the batch, it displays a
message to identify the problem item:
*
Tip: You can use the DRN given in the message to locate the physical item. The system
administrator can use the DRN to locate the item in the SIIPS error log.
11
“Send batch to IQR” Message
When you load a batch containing items that require IQR review, and later when you are working
on the batch, the system may display the following message:
The current batch contains image suspect documents that require processing at IQR.
Send batch to IQR now?
!
If you are still working on the batch, choose No to clear the message.
!
If you are finished balancing the batch, choose Yes.
The system sends the batch to IQR.
You can still see the batch on your screen while it is at IQR, marked by this icon:
!
12
Important: You should periodically refresh the screen by clicking the Refresh
button (on the Block Balancing main window or the Select Entry dialog), until this icon
disappears (when the unit of work is back from IQR).
Choosing a New Entry (Block Balancing Only)
What Has Changed: On the Select Entry screen, “Normal” priority has been replaced with
“Medium-1” through “Medium-8”, priority levels (where 1 is highest). There are 10 priority levels
altogether: High, Medium-1 through Medium-8, and Low.
While Block Balancing is running, you can choose a different entry to work on at any time.
To choose a new entry:
1
Choose Unit of Work > Select Entry.
The system displays the Select Entry dialog, with all entries for the current cycle listed.
Select Entry dialog
2
*
Choose a different cycle and/or parameter set from the drop-down lists at the top of the dialog if:
!
you want to display a specific kind of work (pre-encoded large deposits, un-encoded large
deposits, inclearings, or pre-encoded OTC),
!
the entry you want to work on is not displayed, or
!
there are too many entries displayed and you want to view a subset
Tip: If there are other operators working on the same entry, choose Refresh before you select an
entry, to make sure this screen is up-to-date.
3
Highlight the desired entry, then choose Select.
The system unloads the current entry and loads the newly selected one.
13
14
2
System Administration
This section describes the new and changed system administration procedures for this release of
Transaction Manager.
15
Chapter 2: System Administration
Managing Workload
Managing Workload
Managing Workload by Unit-of-Work Type
Changing Work Priorities
What Has Changed: “Normal” priority has been replaced with “Medium” priority, and includes a
slider with 10 different priority levels to choose from.
Notes: 1 If default priority settings are used, all work flowing through the system is sent from process
to process on a first-in, first out basis. By default, this work would be medium-5 priority.
But sometimes you may wish to change a unit-of-work’s priority, for example, to push it
ahead of the system to meet a deadline.
2
When changing priorities, remember to apply your knowledge of workflow. For example,
raising the priority of a particular DI unit-of-work won’t necessarily get work through the
Entry Item Reports (EIR) auto-activity more quickly, because this auto-activity is triggered
only when the entire entry is processed.
To change the priority of a unit-of-work:
1
Choose View > Work In Progress.
The system displays the Work In Progress dialog.
Work In Progress Dialog
2
16
Select the unit-of-work from the list, then choose Set Priority.
Managing Workload
The system displays the Set Priority dialog.
Set Priority Dialog
3
4
Set the priority for processing this unit of work using the slider:
!
0 (High): high-priority work gets processed first. To push a DI unit-of-work through the
system, move the slider up so that his unit of work has a higher priority than all others.
!
1 through 8 (Medium): medium-priority work gets processed before low priority work, but
after high priority work. All units-of-work are automatically set to medium (5) priority when
they are created in the system. You can specify the processing order of up to 10 units of
work by assigning a different number to each using this dialog.
!
9 (Low): low-priority work will be processed if no other work is in the queue.
Choose OK.
The system changes the selected unit-of-work’s priority.
17
Reports
Reports
One report has changed for this release: the ImageMark Audit report has had values 100 through
111 added. The full description of the report (and a sample) are included here for reference.
ImageMark Audit Report
The ImageMark Audit report (also referred to as the full audit report) lists every item processed in
the system and indicates all changes made to the items and which operator made the changes. The
ImageMark Audit report must be run separately for each application instance.
The item information (the first six report fields) displays on one line, and the change information
related to the item (the remaining fields) displays beneath the item information.
Note: Because this report takes a while to print, you may want to run it using Windows Task
Scheduler. See Chapter 5 of ImageMark Transaction Manager 4.2 Parameter Generation:
ASCII Files (B004-0000-0610).
For each item, the report shows:
!
DRN: the document reference number
!
18
Res. Susp. = resolved suspense item
!
AMOUNT: the item final amount
!
STAT: the way the final amount was entered in the system:
!
M = read by the EPU MICR reader
!
R = read by RSS recognition software
!
C = keyed by Codeline Completion operator
!
K = keyed by Amount Keying operator
!
B = keyed by Balancing operator
!
E = keyed by Expert Balancing operator
!
F = resulted from a field manipulation directive
!
S = assigned by SMM
!
X = assigned or keyed at Reconciliation
!
D = resulted from a Deposit Review
!
I = EPA has imported an auto-select tracer from a 3890-captured entry
!
OPER: the operator’s number, if the final amount was entered through keying
!
1234567890: the first source of each of the 10 item fields (for example, 1=AMOUNT,
2=TRANCODE, 3=ACCOUNT, 4=TRANSIT, 5=SERIAL, and so on):
!
!
!
!
!
F = resulted from a field manipulation directive
Reports
!
!
!
M = read by the EPU MICR reader
!
!
S = assigned by SMM
!
X = assigned or keyed at reconciliation
!
CODELINE: the item codeline read at the EPU
!
! = transport reject character
Note: The codeline may wrap to the next line.
For each item changed, beneath the item information, the report shows:
!
CHG: the number of the field that was changed (1—10) or the reason for the change:
!
11 = free item resolved
!
12 = suspense item added
!
13 = suspense item removed
!
14 = item reclassified as an image reject
!
15 = field marked as non-encode
!
16 = item reclassified
Note: The field reclassified is labelled with a corresponding reclassify code 41—50.
!
17 = adjustment created
!
18 = adjustment confirmed
!
19 = adjusment deleted
!
20 = physical adjustment created
!
21 = item has been reimaged
!
22 = front piggyback item has been reimaged
!
23 = rear piggyback item has been reimaged
!
24 = forced match item
!
25 = forced missing item
!
26 = transport image reject
!
27 = IDT operator reject
!
28 = deposit review required at DRA
!
29 = no deposit review required at host
!
30 = deposit review required at host
!
31 = reclassified to non-negotiable item
!
32 = audit change block split
!
33 = audit change batch split
!
34 = audit change batch moved
19
Reports
!
35 = audit change adjustment moved
!
36 = audit change keying error
!
37 = audit change misread
!
38 = audit change misencode
!
39 = audit change force adjustment deleted
!
40 = codeline replaced
!
41—50 = field 1—10 reclassify
!
51 = IQA image suspect
!
52 = IQA image suspect confirm
!
53 = IQA image suspect cleared
!
54 = IQA image suspect reimaged
!
55 = OSD suspect cleared
!
56 = OSD suspect confirm
!
57 = OSD suspect reimaged
!
58 = OSD suspect
!
59 = physical item moved (this is the old and new logical pocket number)
!
60 = DDRI Unit of Work marked as damaged
!
61 = protected item prompt ignored by autorole
!
62 = amount field change not allowed (protected)
!
63 = field 2 to 10 change not allowed (protected)
!
64 = image change not allowed
!
65 = pocket change not allowed
!
66 = operator changed an item that had a “Protected” warning
!
67 = operator did not change an item that had a “Protected” warning
!
68 = physical item moved (this is the old and new tray number)
!
69 = physical item moved (this is the old tray sequence number)
!
70 = IDT operator reject
!
71—80 = auto-select field change 1—10
!
81—90 = field 1—10 change not allowed
!
91 = supplemental amount changed
!
92 = hold removed
!
97 = block change
!
100 = fields merged
!
101—110 = field 1—10 merged
!
111 = suspect amount validated
Note: If the initial value is not modified, there is no change code.
20
Reports
!
!
!
DATA BEFORE: the field value before the change:
!
? = system reject character
!
If the change is an adjustment, this field displays the adjustment code.
!
If the final amount was initially entered at an operator activity, this field is blank.
DATA AFTER: the field value after the change:
!
? = system reject character
!
If the change is an adjustment, this field displays the adjustment amount.
!
If the final amount was initially entered at an operator activity, this field is blank.
OPER: one of the following codes.
Note: If the code is not an autorole, it is followed by the number of the operator who made the
change.
!
!
!
!
!
F = resulted from a field manipulation directive in CTA auto-activity
!
!
!
S = assigned by SMM
!
X = assigned or keyed at reconciliation
!
21
22
150000
50000
73161221
!!!7!!!7!!
73161222
73161223
!!!b!!!9849
80000
280000
73161220
!!!b!!!!039
0b!!!
280000
38546
73161163
73161220
!!!b!!!!039
----------
AMOUNT
-------------
DRN
ANY BANK
ImageMark Audit Report
K
K
K
K
K
-----
STAT
093
093
093
093
093
----
OPER
(ds01a)
KM C
K CC
K BB
KMCC
KMCC
S CMM
S
----------
1234567890
4
3
3
3
3
2
3
4
3
4
4
3
3
1
3
3
3
3
3
17
1
3
3
2
??9849
???039
50
10000000
100
06414535
06414533
02823847
10000
20964277
20503718
26276364
29603325
84366275
10000
16683
33317310
47544072
000095
061000052
26453288
13912749
09889730
38112441
2166
27103
061000010
39997544
502111002
061000010
CODELINE
CHG
DATA BEFORE
DATA AFTER
--- ----------------- ----------------12
12
12
12
3
06414535
C093
C093
C093
C093
C093
C093
B008
C093
C093
B008
C093
2!!
3!3
OPER
---B074
B074
B022
B022
C093
c42396118c d502201666d
C093
C093
K093
C093
C093
C093
C093
C093
B008
K093
C093
C093
C093
16/Apr/2003
Page 1
Reports
Workflow
Workflow
There is a new parameter for the BANKSITE keyword that can influence workflow. For more
information about the “Image Quality Review (IQR) On Demand” feature, refer to
“SendImageSuspectsToIQR” on page 31.
The revised workflow is included on the following page. Changes are as follows:
!
the IQA autorole has been moved to follow CLC and AK
!
EPA no longer sends work to IQA
!
ACC and RSSR are not used
!
documents from AK that require validation will generate a sort simulator call:
!
for documents that require physical outsorting, the call occurs at IQA
!
otherwise, the call occurs at STG
23
Workflow
24
3
Parameters
This chapter describes the following:
!
changes to the IQA Test Tool
!
changes made to existing keywords and parameters
!
how to enable auto-adjustments on your system
25
Chapter 3: Parameters
IQA Test Tool
IQA Test Tool
The IQA (Image Quality Assessment) test tool is a command line utility that you can use from the
XAP for ad hoc testing of images and parameters.
The IQA Test tool loads the parameters contained in a Parameter List (iqtest.lst) file for the specified
pset number. For each image in the input file, IQATest loads the image and runs the Image Quality
tests contained in the parameter list file.
If any of the IQA tests named in the Parameter List File fail, the final result will be a fail.
IQA Test shall output the results of the tests to stdout as a CSV record containing the following:
!
Image Number
!
Image Filename
!
Expected Result
!
Test Result
!
“ERROR” if the expected Result did not equal the Test Result
Running the IQA Test Tool
To run the utility, enter the following at the command line of the XAP:
IQATestTool -f eipsFile -a appTypeDir [options]
Required Arguments:
-f eipsfile
name of the input eips file containing the images to be assessed
-a appTypeDir the application type directory. It can be defined as:
!
an absolute path,
!
a path relative to the current directory, or
!
a path relative to %IMAGEMARK_ROOT%\opt\siips\classa
Input Options:
-l lstfile
global-level list (.lst) file to search for IQA keywords:
!
IQA_TEST_DEFNS in the global section
!
IQA_PROCESS_TESTS and IQA_PROCESS_RULES in the Pset section
(default iqtest.lst)
26
-p pset
number of the parameter set to use when looking for IQA_PROCESS_TESTS and
IQA_PROCESS_RULES keywords (default: 1)
-t TPDll
name of the third-party assessment DLL to use; if specified, then the system uses
this value instead of the IQADLL environment variable (default: tp_ial)
IQA Test Tool
Output Options:
-o OutDir
directory where output is to be written; all output produced by the following options
is written under this directory (default: current working directory)
-c CSVFile
csv output file to use for IQA test results (default: no csv output)
-e ImageDir
subdirectory where exported images are to be written (default: no images exported)
-i IEDir
subdirectory where flat file for ietest export is to be written (default: no ietest export).
-v
display the command-line arguments and any keywords read from the .lst file to the
screen (default: do not display)
Results are logged into the out.eips file, created in the same directory as the parameter list file (*.lst).
The system displays errors and final results on the screen.
List File Keywords
The IQA test tool reads five different keywords from the list file (.lst) that is specified on the commandline. Three of the keywords are required and define the XML parameter files to use when processing
the EIPS file and two of the parameters are optional and specify third-party config files that can be
passed along to the third-party image assessment library that is used.
The following table describes the keywords:
Keyword
Section
Purpose
IQA_TEST_DEFNS
GLOBAL
Specifies the name of the DIAL test definitions
XML file.
IQA_PROCESS_TESTS
PSet
Specifies the name of the DIAL process tests XML
file.
IQA_PROCESS_RULES
PSet
Specifies the name of the DIAL process rules XML
file.
TP_GLOBAL_PARMS
GLOBAL
Specifies the name of the third-party global config
file that should be loaded after DIAL has been
initialized. This file contains information that is of
specific value to the third-party image assessment
library.
TP_PSET_PARMS
PSet
Specifies the name of the third-party pset config
file that should be loaded after a DIAL session has
been initialized. This file contains information that
is of specific value to the third-party image
assessment library.
27
IQA Test Tool
Examples
These examples all use the same example EIPS file that is in the current working directory:
Example 1:
In this example, we use the IQA test tool to assess the EIPS file using the acc_smcr4 app type
subdirectory found under %IMAGEMARK_ROOT%/opt/siips/classa. The system will use the
defaults iqtest.lst and Pset 1, since the -l and -p options are not specified. The output directory
will be the current working directory and the only output created will be the out.eips file.
IQATestTool -f eips.2.20040402.183700.99999.88.9002.r03.b0001.0043 \\
-a acc_smcr4
Example 2:
In this example, we use the IQA test tool to assess the EIPS file using the acc_smcr4 app type
subdirectory found under %IMAGEMARK_ROOT%/opt/siips/classa. The system will use the
iqa_pod.lst file when processing the EIPS file. The default parameter set (Pset 1) will be used,
since the -p option is not specified. The output directory will be the current working directory and
the only output created will be the out.eips file.
-a acc_smcr4 -l iqa_pod.lst
Example 3:
In this example, we assess the EIPS file using the testParams app type subdirectory found under
the current working directory. The command line specifies the following:
!
the list file will be testCase1.lst (found under the testParams subdirectory);
!
the parameter set is 2 and it must also exist under the testParams subdirectory, and
testParams/2 must contain the XML files referenced by testCase1.lst;
!
the output directory is set to output43 under the current working directory
!
all images will be written to output43/images;
!
a results.csv file that contains all of the test results will be written to output43
!
an ietest compatible import file will be created under output43/ietest
-a testParams -l testCase1.lst -p 2 -o output43 -e images \\
-c results.csv -i ietest -v
28
New Keywords
New Keywords
The following keywords are new:
!
TP_GLOBAL_PARMS
!
TP_PSET_PARMS
TP_GLOBAL_PARMS
Used By: BAL, BBL, EBAL, EBBL, IQA, IQATestTool, STG
Control: bal_pod.lst, bbl_pod.lst ebal_pod.lst, ebbl_pod.lst, iqa_pod.lst, iqtest.lst, stg_pod.lst
Default Source: Not applicable
Default Compiled File: Not applicable
Parameter File Directory: Common
Use TP_GLOBAL_PARMS, together with TP_PSET_PARMS, to enable the Image Inspector
boomerang feature.
!
Important: This keyword will not work by itself. You must also enable the TP_PSET_PARMS
keyword, otherwise IQA will fail on initialization or Pset change.
Values
Default
yes – enabled
tpglobparms.dat
no – disabled
29
New Keywords
TP_PSET_PARMS
Used By: BAL, BBL, EBAL, EBBL, IQA, IQATestTool, STG
Control: bal_pod.lst, bbl_pod.lst ebal_pod.lst, ebbl_pod.lst, iqa_pod.lst, iqtest.lst, stg_pod.lst
Default Source: Not applicable
Default Compiled File: Not applicable
Parameter File Directory: Common
Use TP_PSET_PARMS, together with TP_GLOBAL_PARMS, to enable the Image Inspector
boomerang feature.
!
Important: This keyword will not work by itself. You must also enable the TP_GLOBAL_PARMS
keyword, otherwise IQA will fail on initialization or Pset change.
Values
Default
yes – enabled
tppsetparms.dat
no – disabled
30
Changes to Existing Keywords
The following keywords have been modified:
!
BANKSITE
!
CA_PSETS
!
IDT_ADJUSTMENT_CODES
!
IDT_ADJUSTMENT_MACRO
!
IQR_GEN_PARMS
!
XREF
BANKSITE
Spare1 and Spare2 have been replaced by new parameters.
SendImageSuspectsToIQR
Activate this parameter (which replaces Spare1) when you want IQR to be responsible for all image
review decisions.
When this parameter is active, work that would normally be done at Balancing may be redirected
to Image Quality Review.
Note: This parameter influences workflow decisions. A unit of work can be sent from STG, BAL,
BBL, EBAL, or EBBL to IQR for operator review, then returned to the originating role.
Values
Default
0 – feature disabled
0
1 – send image suspect and high-priority
suspects to IQR
UoWPriority
Use this parameter (which replaces Spare2) to define the unit of work priority to assign to this work
when EPA loads the file.
Values
Default
-1 – use EIPS input filename to determine
priority (does not apply to non-EIPS files)
5
0 – 9, where 0 is highest priority and 9 is lowest
31
CA_PSETS
CASpare2 has been replaced by a new parameter.
UoWPriority
Use this parameter to define the unit of work priority to assign to this work when EPA loads the file.
Note: This parameter overrides the UoWPriority parameter (BANKSITE keyword).
Values
Default
-1 – use EIPS input filename to determine
priority (does not apply to non-EIPS files)
5
0 – 9, where 0 is highest priority and 9 is lowest
IDT_ADJUSTMENT_CODES
For the FieldData parameter:
!
Meta-Characters *1–*10 have a new meaning.
!
A new value [n1,n2] has been added.
FieldData
Use this parameter to set up an array specifying what field data to capture as part of the adjustment.
!
If the adjustment code is credit or debit, then there are 10 fields (for fields 1 to 10).
!
If the code indicates both, then there are 20 fields (for fields 1 to 10 for the debit and fields 11
to 20 for the credit).
!
If no data is defined for the associated field, then the entry will contain a null-string.
Use the following meta-characters to reference data that is not within the item’s field data. All metacharacters start with an asterisk character (*).
32
MetaCharacter
Meaning
#
prompt the operator to enter data for the field
*1–*10
field from current item record
*11–*20
field from credit or deposit slip record
*21–*30
field from batch header
*31–*40
reserved
*41–*55
field from ss_ddr record
MetaCharacter
Meaning
*56
ss_ddr branch_number field
*57
advice reference number
*58
discovered check digit
*59
PCS Bank ID Correction (replacement value from
PCS_BANKID_CORRECTIONS parameter file)
*60
system ID from the BANKSITE parameter file
*61
account name associated with the deposit account
*62
bank ID associated with the deposit account
*63
special processing indicator (code to identify wholesale and commercial
accounts) associated with the deposit account
*64
sub-product code (code to identify wholesale and commercial accounts), from
the Advice table
*65
account type associated with the deposit account
*66
adjustment reason code
*67–*69
reserved
*70–*78
advice reference number (second digit is length of the reference number in the
resulting field)
*79
reserved
*80
Presenting Bank ID value (from block record), left-justified, zero filled to 3 digits
*81
Commingle Bank ID value (from associated credit or deposit slip item), left
justified, zero filled to 3 digits
*82
5-digit branch number (indicating the accounting unit (AU)) extracted from the
batch header account number (digits 3 through 7 of this number). For example,
in the batch header account number 02010400000, the AU would be 01040.
*83
machine number portion of the DRN of the current item
*84
machine number portion of the DRN of the deposit slip
*85
sequence number portion of the DRN from the current item
*86
sequence number portion of the DRN from the deposit slip
*87
machine number portion of the DRN of the adjustment item
*88
sequence number portion of the DRN from the adjustment item
*91–*100
auto-showout adjustment field
*101–*110
field from block header
33
Values
Default
up to 30 alphanumeric characters
“”
“*” – Obtain data from deposit slip record (in the account field only), and
use advice notice special instructions.
“#” – Prompt the operator to enter the data for the field.
“B” – Obtain field data from the matching batch trailer document. If none
available, prompt the operator to enter the data for the field.
“%n” – For data identified by the metacharacter to the immediate left of this
symbol, format the data to be right justified and zero filled to n characters.
(n1,n2) – If this appears immediately after a metacharacter, then only a
substring shall be used where n1 is the position of the first character to
be used and n2 is the position of the last character to be used, relative
to the leftmost end of the string.
[n1,n2] – If this appears immediately after a metacharacter, then only a
substring shall be used where n1 is the position of the first character to
be used and n2 is the position of the last character to be used, relative
to the rightmost end of the string.
Notes: 1 Use “B” when defining a special batch-header adjustment type, in a processing
environment where specialized batch-trailer validation is being used, as specified by the
BATCH_VALIDATION keyword.
2
34
The “%n” is used in conjunction with another meta-character and has no meaning on its
own. It only applies to the metacharacter immediately before it and is not applied against
multiple metacharacters.
IDT_ADJUSTMENT_MACRO
The TransTypeRequired and DocAction parameters each have a new value.
TransTypeRequired
Use this parameter to identify which specific type of transaction in the Document List the MacroName
adjustment should be available for.
Note: You are allowed to configure only one Macro Adjustment structure with
TransTypeRequired=4. DocAction must be set to 5 for this structure.
Values
Default
0 – adjustment is always available
0
1 – adjustment is available only if the highlighted item in the Document
List is part of a deposit transaction
2 – adjustment is available only if the highlighted item in the Document
List is part of a payment transaction
3 – adjustment is automatically applied if the item highlighted in the
Document List has a distribution equal to the set value of the
ItemDist parameter (this process is only run when the unit of work
is first loaded by Balancing). You can also apply this adjustment
manually.
4 – adjustment is automatically applied if the item highlighted in the
Document List is flagged as image suspect or image priority
suspect (this process is only run when the unit of work is first
loaded by BAL). You cannot manually apply this adjustment.
!
Important: If TransTypeRequired is set to 4, the translator will run the XREF cross-reference check
against the BATCH_VALIDATION parameter file, in order to validate the idtmcadj.dat
file. You must set up the cross-reference check by adding the following line to the
bank.trn file in the training parameter set (trn_cpcs or trn_smcr):
XREF
:BATCH_VALIDATION
:batchval.prm
For more information on XREF, see page 43.
35
DocAction
Use this parameter to specify what should happen to the highlighted item in the Document List during
the MacroName adjustment.
Values
Default
0 – force match current item
0
1 – no action
2 – force match first adjustment
4 – force match when field differs
5 – apply field parameters to current item
Note: EXT_SECOND_SOURCE_FIELD_PARMS keyword, FieldUsage parameter, Bit 4 must be
set to 1 (required for force match).
36
Macro Adjustment Parameters for ATM
In this structure, the FieldParms parameter has new values.
FieldParms (Field1 to Field10)
This is an array of merge rules for performing a force match. Defines the merge rule for the associated
field. The format of these strings depends on the setting of the useAdjFielddefns parameter value.
Example:
If the starting field is up to eight characters long and you need to replace the rightmost character
with a 4, use “[8,2]4”. This will result in an existing document field value of “56780” changing to
“56784” after the fieldParms value has been applied.
Values
Default
If UseAdjFieldDefns = 0:
““
“ ” – no merge (default merge from SMM parameters will apply)
Or, a string containing a combination of:
“????” – any 30 alphanumeric characters (except “*”, “[“, “]”, and
“\”) will be copied to this document field
Note: If this string starts with a number and immediately
follows a *<field#>, then start the string with a ‘\” character
so the system can tell the difference between a reference to
field 11 (“*11) and a reference to field 1 followed by the string
“1” (*1\1).
*1 to *15 – copy the content of the matched second source record
to this document field:
*1 = copy from field 1
...
“[end_pos, start_pos]” – a right-aligned substring of the existing
document field value. The substring of the existing
document field goes from position start_pos up to, but not
including, end_pos. Both start_pos and end_pos positions
are from the right-most end of the field. Start_pos has a
range of 1 through 29. end_pos has a range of (start_pos +
1) through 30.
Note: second source field references (*<field#>), substrings
(end_pos, start_pod), and constant strings (????) can be
mixed and matched up to the 30-character limit.
If UseAdjFieldDefns = 1:
FieldParms strings support the same syntax as FieldData values
(IDT_ADJUSTMENT_CODE keyword).
37
UseAdjFieldDefns
Use this parameter (which replaces MacroSpare1) to specify how to assign the FieldParms strings
to the highlighted item.
Values
Default
0 – use the original definition for FieldParms
0
1 – use the same syntax as the FieldData
(IDT_ADJUSTMENT_CODE keyword) values
Reference Adjustment Parameter Structure
Note: The parameters in this structure are repeated for each macro adjustment you set up.
In this structure, AdjReasonCode has new values.
AdjReasonCode
Use this parameter to identify which specific adjustment reason code should be used.
Notes: 1 Values -10 through -8 are to be used for auto adjustments only, not presented to the
Balancing operator for manual selection.
2
You must set TransTypeRequired = 3.
Values
Default
-10 – reason code is in field 10 on the
highlighted item
None (must match an entry in
IDT_ADJUSTMENT_CODES)
highlighted item
highlighted item
1 to 255 – value from the idtfadj.dat file
(IDT_FORCED_ADJUSTMENTS
keyword) that uniquely identifies an
adjustment
38
IQR_GEN_PARMS
Two new parameters have been added, which you can use to set up selective display of image
quality failures (images and codeline information).
SpecialNotificationTest
If there is a specific image quality test that requires operator notification for any item that fails that
test, use this parameter (which replaces Spare5) to specify the test. The values for Vendor, Type,
and Number are defined in the following table. The value is not case-sensitive.
Values
Default
““ – do not notify operator of failures
““
“Vendor,Type,Number” – notify operator if an
item fails this test
DisplayCodelineOnFailure
Use this parameter (which replaces Spare6) to display the codeline of the SpecialNotificationTest
item. The values for Vendor, Type, and Number are defined in the following table. The value is not
case-sensitive.
Values
Default
““ – do not display codelines
““
“any” – display the codeline for all failed items
“Vendor,Type,Number” – display the codeline
for items that fail this test
!
Important: You also need to specify which codeline fields to display using the IDT_COMMON and
FIELD_DEFNS keywords.
Examples:
SpecialNotificationTest = “W,Q,22”
DisplayCodelineOnFailure = “W,Q,22”
This notifies the operator and displays the codeline on the IQR screen whenever the Codeline
Mismatch error occurs.
SpecialNotificationTest = “W,U,4”
DisplayCodelineOnFailure = “W,U,4”
This notifies the operator and displays the codeline on the IQR screen whenever the Date Usability
error occurs.
39
Test Codes
Vendor
Test Type
Test Number
Test Name
W (Wells)
Q (Quality)
0
Global Quality
1
Undersized Compression Image
2
Oversized Compression Image
3
Undersized Image
4
Oversized Image
5
Image too light
6
Image too dark
7
Horizontal Framing Error
8
Vertical Framing Error
9
Horizontal Streaks
10
Vertical Streaks
11
Folded or Torn Corner
12
Folded or Torn Edge
13
Excessive Skew
14
Excessive Spot Noise
15
Out of Focus
16
Piggyback
17
Carbon Strips
18
Carrier
19
Rotated 180
20
Flipped Front to Back
21
Front Rear Mismatch
22
Codeline Mismatch
23
Reserved 1
24
Reserved 2
25
Reserved 3
26
Reserved 4
27
Reserved 5
1
Image Usability
2
Payor Usability
3
Payor Bank Usability
U (Usability)
40
Test Codes
Vendor
N (NCR)
Test Type
Test Number
Test Name
4
Date Usability
5
Payee Usability
6
Courtesy Amount
7
Legal Amount Usability
8
Memo Usability
9
Signature Usability
10
MICR Usability
11
Payee Endorsement Usability
12
BOFD (Bank Of First Deposit)
Endorsement Usability
13
Transit Endorsement Usability
14
Payor Presence
15
Payor Bank Presence
16
Date Presence
17
Payee Presence
18
Courtesy Amount Presence
19
Legal Amount Presence
20
Memo Presence
21
Signature Presence
22
MICR Presence
23
Payee Endorsement Presence
24
BOFD (Bank Of First Deposit)
Endorsement Presence
25
Transit Endorsement Presence
26
Reserved 6
27
Reserved 7
28
Reserved 8
29
Reserved 9
0
Regular Operator Review
1
Expert Operator Review
I (ImageMark)
0
Generic Image Quality Test
A (AppData)
0
Test All Docs
H (Human)
41
Test Codes
Vendor
42
Test Type
Test Number
Test Name
1
Protected
2
Reject
3
Transit
4
On Us
5
Foreign
6
Exchange
7
Review Required
8
High Amount
9
Time Limit
10
Control Document
11
DC Type BBO
12
DC Type Teller
13
DC Type ATM
14
DC Type CC
15
Image Quality Item
16
Ghost
17
NonProof
18
Stored Procedure 1
19
Stored Procedure 2
20
Stored Procedure 3
21
Stored Procedure 4
22
Credit
23
Debit
24
Low Amount
25
Codeline CSV 1
26
Codeline CSV 2
27
Codeline CSV 3
28
Codeline CSV 4
29
IQ Status Good
30
IQ Status Reject
31
IQ Status Physical Clear Reject
Test Codes
Vendor
Test Type
Test Number
Test Name
32
IQ Status Suspect
33
IQ Status High Priority Suspect
34
IQ Status Tests Required
35
IQ Status Protected Reject
36
IQ Status Expert Review Required
XREF
The cross-reference keyword is a special keyword, to be used by the translator when reading a .trn
input file. If a keyword is prefixed by XREF, then the system loads the .prm file for the referenced
keyword and saves it for possible use later when translating a subsequent file listed in the .trn input
file.
XREF now supports the following keywords:
!
BATCH_VALIDATION (used when loading IDT_ADJUSTMENT_MACRO)
!
DOCUMENT_DISTS (used when loading EIE_DISTS)
!
EPU_PARMS (used when loading ARCHIVE_BANK_PARMS)
Examples
These examples show how to set up cross-references in the bank.trn file in the training parameter
set (trn_cpcs and trn_smcr).
Example 1:
#BATCH_VALIDATION
#XREF
#IDT_ADJUSTMENT_MACRO
: batchval.dat
: BATCH_VALIDATION
: idtmcadj.dat
: batchval.prm
: batchval.prm
: idtmcadj.prm
: docdist.dat
: DOCUMENT_DISTS
: eiedist.dat
: docdist.prm
: docdist.prm
: eiedist.prm
: epuparms.dat
: EPU_PARMS
: etibank.dat
: epuparms.prm
: epuparms.prm
: etibank.prm
Example 2:
#DOCUMENT_DISTS
#XREF
#EIE_DISTS
Example 3:
#EPU_PARMS
#XREF
#ARCHIVE_BANK_PARMS
43
Activating Auto Adjustments and IQR Reject Processing on Your System
Activating Auto Adjustments and IQR Reject
Processing on Your System
To activate auto-adjustments and send all IQ Reject items to IQR for processing, make these
changes to your system:
Part 1: Enable the Send-Image-Suspects-To-IQR Feature
1
In the Psets that require image review at IQR, set the SendImageSuspectsToIQR parameter
(BANKSITE keyword) to 1.
2
Run Translat.
3
Add (or uncomment) BANKSITE in the appropriate Pset sections of the STG.lst file.
Part 2: Set Up IQA Parameters with Carreker Image Engine
1
In the global section of IQA_pod.lst and IQATestTool.lst, add (or uncomment) the following line:
TP_GLOBAL_PARMS=tpglobparms.dat
Note: This keyword should reference the Image Inspector global parameter information in the
tpglobparms.dat file.
2
In the bank-specific sections of IQA_pod.lst and IQATestTool.lst, add (or uncomment) the
following line:
TP_PSET_PARMS=tppsetparms.dat
Note: This keyword should reference the Image Inspector Pset-specific parameter information in
the tppsetparms.dat file.
3
On the BAP, configure Carreker Image Assessment.
The system creates the following files:
44
!
TestDefns.xml (to be used by CLC, STG, RSS, BAL, BBL, IQR, IQATestTool, and IQA)
!
SelectRules.xml (to be used by CLC, STG, RSS, BAL, BBL, IQR, IQATestTool, and IQA)
!
SelectTests.xml (to be used by CLC, STG, RSS, BAL, BBL, IQR, IQATestTool, and IQA)
!
ProcessTests.xml (to be used by CLC, STG, RSS, BAL, BBL, and IQR)
!
IQAProcessTests.xml (to be used by IQA only).
4
In the iqa_pod.lst file, rename the file referenced by IQA_PROCESS_TESTS to
IQAProcessTests.xml.
5
On the XAP, make sure that the IQADLL environment variable exists and is pointing to
WFIQA.DLL (the image inspector wrapper).
Activating Auto Adjustments and IQR Reject Processing on Your System
Part 3: Enable Automatic Non-Proofing of Image Reject
Documents
1
Enable the IDT_ADJUSTMENT_MACRO and IDT_FORCED_ADJUSTMENTS keywords for
BAL, EBAL, BBL and EBBL.
2
Enable the IDT_FORCED_ADJUSTMENTS keyword for BCTA and RPT.
3
Configure an “Image Reject” adjustment in the file referenced by the
IDT_FORCED_ADJUSTMENTS keyword. This adjustment is intended to replace the image
reject that was automatically non-proofed.
4
!
If you don’t have the ATM.ext or BTM.ext package, copy and configure the file from
classa\trn_cpcs\1\idtmcadj.dat.
!
If you do have the ATM.ext or BTM.ext package, copy and configure the file from the
appropriate extension.
Configure a macro adjustment that includes the following:
MacroName=’Image REJECT’
TypeRequired = 0
TransTypeRequired = 4
DocAction = 5
QuickDisplay = 0
AdjDisplayType = 0
ExpertBalancer = 1
IsMerge = 0
FieldParms[10][31] = Fields for a non-proof document
ItemDist = 0
refAdjustments = [pointer to Image Reject adjustment from IDT_FORCED_ADJUSTMENT
file]
Note: You can only have one of these macro adjustments. If there are more than one, the system
reads the first one and ignores the rest.
Part 4: Enable IQR Notification for Codeline Mismatch
1
For the IQR_GEN_PARMS keyword, set the SpecialNotificationTest and
DisplayCodelineOnFailure parameters to “W,Q,22”.
The system will notify the operator and display the codeline on the IQR screen whenever the
Codeline Mismatch error occurs.
45
Activating Support for Externally-Flagged Exception Items
Activating Support for Externally-Flagged
Exception Items
To activate this feature:
46
1
Place the required Adjustment Reason Code into field 8, 9, or 10 of the exception item.
2
Set the adjReasonCode parameter (IDT_ADJUSTMENT_MACRO keyword,
REF_ADJUSTMENT structure) for the required automatic adjustment macro to -8, -9, or -10.
Glossary
A
Adjustment
An electronic procedure to correct an error in a customer deposit or teller work. Most adjustments
cause an Advice Notice to be generated.
Advice Notice
A letter that is generated as a result of an adjustment. Includes image(s) of the relevant item(s) and
tapes (if available). Advises the customer or teller of the error and the action taken.
autoadj_mig
A command-line utility that you can run in order to create parameter structures for the
BATCH_VALIDATION and IDT_ADJUSTMENT_MACRO keywords.
B
BBO
Branch Back Office.
BOFD
Bank Of First Deposit: the financial institution at which the check was deposited.
C
CSV
Comma Separated Value: a file type that stores tabular data. Also known as a flat file.
47
Glossary
Cycle
The largest NCR ImageMark Transaction Manager unit of work. Could be used to track the work for
one shift or for one day.
48
Index
Symbols
D
*adjustment meta-characters 32
DisplayCodelineOnFailure 39
DocAction 36
A
activities
remote 16
adjustment meta-characters 32
Advice Notice
meta-characters 32
audit reports
Full Audit report 18
ImageMark Audit report 18
B
BANKSITE 31
SendImageSuspectsToIQR 31
Block Balancing
choosing a new entry 13
E
end-of-cycle reports
audit reports
entry
choosing in Block Balancing 13
F
FieldParms 37
I
C
CA_PSETS 32
UoWPriority 31–32
Choosing a New Entry 13
IDT_ADJUSTMENT_CODES 32
IDT_ADJUSTMENT_MACRO 35
DocAction 36
FieldParms 37
ItemDist 38
TransTypeRequired 35
UseAdjFieldDefns 38
description 18
sample 22
49
Index
images
quality testing 26
IQA Test tool 26
IQR_GEN_PARMS
DisplayCodelineOnFailure 39
SpecialNotificationTest 39
iqtest.lst 26
ItemDist 38
S
SendImageSuspectsToIQR 31
Set Priority dialog 17
setting priority type
high 17
low 17
normal 17
SpecialNotificationTest 39
K
Keywords
BANKSITE 31
CA_PSETS 32
IDT_ADJUSTMENT_CODES 32
IDT_ADJUSTMENT_MACRO 35
T
TransTypeRequired 35
U
M
meta-characters 32
UoWPriority 31–32
UseAdjFieldDefns 38
N
V
New Keywords 31
viewing
remote activities 16
workload
by unit-of-work type
16
P
W
parameters
quality testing 26
priority
changing for work 16
viewing 16
Work In Progress
dialog
changing work priority 16
displaying 16
R
remote activity types 16
reports
ImageMark Audit report
50
18, 22
B004-0000-0680
February 23, 2007

ImageMark Transaction Manager 4.2.11 Product Update

Transcription

Similar documents

ME-709 Magnetic Recumbent Exercise Bike

RE/MAX vs. THE INDUSTRY

OVERCAPPERS

XR650 Brochure

Morgan Stanley Smith Barney Benefit Access Quick

Harborstone Credit Union

instructions for housing deposit ($250.00 usd)

Helsinki | 12 November, 2015

How to Pay My Bill - Students and Authorized Payers

Private Label Card Management Software