Below
is a suggested order to configure your iNovah system. This may not be typical in all
environments. Business Rules may dictate
the exact order item should be configured.
If there are any questions or concerns, please contact your Project
Manager.
1. User (p 7-3)
a. All users who need access to
iNovah need to be configured as a User in iNovah. Once setup as a User, assign that user to a Group.
2. Group (p 7-7)
a. A Group is a compilation of
Users. An example of suggested Group
permissions and settings are illustrated in Appendix B.
3. Tenders (p 7-50)
a. Examples of Tenders are
Cash, Check, and Credit Cards. Configure
each Tender Type that is to be used for payment collection.
4. Allocations (p 7-45)
a. An Allocation is the
breakdown of a Payment. There could be a
few allocations, or a few hundred.
Configure each Allocation that is to be collected.
5. Payment Types (p 7-41)
a. A Payment Type represents
the fee or bill that is being collected.
There could be many Payment Types or just a few. Don’t forget to associate any and all
Allocations and Tenders that could be collected for the Payment Type.
6. Business Unit (p 7-76)
a. A Business Unit is a
collection of Payment Types. A Payment
Type cannot be collected unless it is associated to a Business Units. One or many Business Units can be configured.
7.
Multi-Groups (p 7-82) if needed
a. If there are Payment Types
that cannot be taken with other Payment Types, Multi-groups may be needed. If all Payment Types can be taken together in
a Multi-Payment then Multi-Groups are not needed.
8. Banks (p 7-58)
a. Banks need to be created to
show where the Tender is to be deposited.
Each Bank Account will be a Bank in iNovah. One or more Banks can be
created
9.
Funds (p 7-61) if needed
a. Funds are used if multiple
Allocations are utilized for a Payment Type, yet not the entire Tender
collected is going to the same Bank Account.
Each Allocation can be configured to a Fund and then when a Tender is
collected the Funds will populate in order of priority. At the end of the day each Fund will have an
amount that it owes or is short from another fund.
10.
Credit Cards (p 7-26) if needed
a. If using a integrated Credit
Card solution with iNovah, a Credit Card Merchant needs to be configured. Each Credit Card Merchant will need to be
configured to the corresponding Credit Card.
11.
ACH (p 7-28) if needed
a. If using an ACH merchant
though iNovah, an ACH Merchant needs to be configured. Each ACH Merchant will need to be configured
to the corresponding Tender.
12.
Offices (p 7-72)
a. An Office is the physical
location where the collection of the Payment Takes place (Downtown, Southside
Office, etc.) One or more Offices can be
configured. Remember to associate the
Tenders that the Office can collect as well as Bank, Credit Card, and ACH
information.
13.
Collection Points (p 7-55)
a. A Collection Point is how
the Payment is collected (Over the Counter, Mail, Drive-Thru.) One or more Collection Points can be
configured. Limits can be placed on
Validations, Endorsements, and Receipts can be configured here as well.
14.
Images (p 7-38)
a. The central location of all
Images in iNovah. If wanting a Payment
or Tender icon, it must first be configured here. The Image will then be available in the
corresponding image dropdown box.
15.
Actions Reasons (p 7-85)
a. Many events in iNovah
require an Action Reason (Void, Adjustment, Reopen a Batch) for auditing
purposes. Action Reasons can be added,
edited or deleted from here.
16.
Forms in Form Editor (Form Editor Guide)
a. All Forms can be customized
in iNovah. Utilize any default forms
first and modify as needed due to Business Rules.
Related Topics