Control Table Setup Sequence

To implement the system, you must set up your organization's business rules in "control tables". Setting up these tables is time-consuming because we allow you to tailor many aspects of the system to meet your organization's requirements. We strongly recommend that you take the time to document how you plan to set up all of these tables before you use the following roadmap to enter the control data. Time spent understanding the interrelationships between this data will reap the rewards of a clean system that meets your current and long term needs.

While we describe the transactions and options in more detail in other sections of this manual, use the following chart (and the remaining sections of this chapter) as your roadmap. Here we list the order in which you perform tasks and the pages you'll use to set up your system. The order is important because some information must exist before other information can be defined (i.e., many dependencies exist).

Note:

Auto setup. The Auto Setup column in the following table contains suggestions to save you time. It also indicates if a control table contains information when the system is installed.

Note:

You don't have to set up every control table. You need only set up those control tables that govern functions that are applicable to your organization.

*Function*	*Menu*	*Auto Setup*
*Global Context*
Algorithm	Admin Menu, Algorithm. You will need to set up an algorithm that populates global context values. The global context is used by various zones in the system to display relevant data. This algorithm is plugged-in on the installation record.	You can run the CI_COPIN DB process to copy many of the algorithms that support basic functionality from the demonstration database. Refer to How To Copy An Algorithm From The Demo Database for more information.
*Accounting Environment*
Country & State	Admin Menu, Country
Currency Codes	Admin Menu, Currency Code	USD is automatically populated
Accounting Calendar	Admin Menu, Accounting Calendar
GL Division	Admin Menu, General Ledger Division
*Security Environment*
Application Service	Admin Menu, Application Service	All base package transactions are automatically populated
Security Type	Admin Menu, Security Type
User Group	Admin Menu, User Group Note, you won't be able to set up users at this point	One user group, ALL-SERVICES, is automatically set up. It references all other application services and a single user called SYSUSER. Note: You may be able to import sample user groups from the demonstration database. Also, you may be able to import user groups if your organization has already defined them using LDAP.
Language	Admin Menu, Language	ENG is automatically populated
Display Profile	Admin Menu, Display Profile	Two display profiles are automatically set up: NORTHAM displays currencies and dates in a classic American format; EURO displays information in a classic European format
Data Access Role	Admin Menu, Data Access Role	CI_DFLT is automatically populated. It references a single user called SYSUSER and a single access group called CI_ACCGRP
Access Group	Admin Menu, Access Group	CI_ACCGRP is automatically populated. It references the data access role CI_DFLT
User	Admin Menu, User	SYSUSER is automatically set up. Note, you may be able to import your users if your organization has already defined them using LDAP.
Return to User Group	You must return to your user groups and define all of their users
*Account Type Environment*
Account Type	Admin Menu, Account Type. At this point, you'll only be able to set up your account type codes. You will return to these account types throughout the setup process to populate additional information.
*Financial Transaction Environment*
Work Calendar	Admin Menu, Work Calendar
Division	Admin Menu, Division
Revenue Class	Admin Menu Revenue Class
Algorithm	Admin Menu, Algorithm. You will need to set up the algorithm that constructs a distribution code's corresponding GL account when it is interfaced to the general ledger
Distribution Code	Admin Menu, Distribution Code
Bank & Bank Accounts	Admin Menu, Bank
Billable Charge Template	Admin Menu, Billable Charge Template. Note, if you want the system to default rate quantities onto billable charges created using this template, you must set up the appropriate unit of measure code, time-of-use code and/or rate quantity identifier.
Billable Charge Upload Line Type	Admin Menu, Billable Charge Line Type
Algorithm	Admin Menu, Algorithm. You will need to set up several algorithms. These algorithms: 1) retrieve a bill segment's consumption, 2) calculate a bill segment's bill lines, 3) construct a bill segment's financial transaction, 4) cancel previously estimated bill segments	Rather than setting these up manually, you can run the CI_COPBI DB process to copy many of these algorithms from the demonstration database. Please review the parameter values on these algorithms after they are copied. Refer to How To Copy An Algorithm From The Demo Database for more information.
Bill Segment Type	Admin Menu, Bill Segment Type
Algorithm	Admin Menu, Algorithm. You will need to set up the algorithm that constructs a payment segment's financial transaction	Rather than setting these up manually, you can run the CI_COPPY DB process to copy many of these algorithms from the demonstration database. Please review the parameter values on these algorithms after they are copied. Refer to How To Copy An Algorithm From The Demo Database for more information.
Payment Segment Type	Admin Menu, Payment Segment Type
Algorithm	Admin Menu, Algorithm. You will need to set up the algorithm that constructs an adjustment's financial transaction	Rather than setting these up manually, you can run the CI_COPAD DB process to copy many of these algorithms from the demonstration database. Please review the parameter values on these algorithms after they are copied. Refer to How To Copy An Algorithm From The Demo Database for more information.
Algorithm	Admin Menu, Algorithm. Several plug-in spots are available to perform additional logic when processing adjustments. For example, if you have the system calculate adjustments, you must set up an adjustment generation algorithm. Refer to Adjustment Type for other available plug-in spots that may be used by your implementation.
Algorithm	Admin Menu, Algorithm. You may want to set up an algorithm that formats the Adjustment information that is displayed throughout the system for a specific Adjustment Type. This algorithm is plugged-in on the Adjustment Type.
Algorithm	Admin Menu, Algorithm. You may want to set up an algorithm that formats the Adjustment information that is displayed throughout the system. This algorithm is plugged-in on the installation record.
Debt Category	Admin Menu, Debt Category
Debt Category Priority	Admin Menu, Debt Category Priority
Adjustment Type	Admin Menu, Adjustment Type
Adjustment Type Profile	Admin Menu, Adjustment Type Profile
Approval Profile	Admin Menu, Approval Profile. Note, an approval profile references a To Do type and one or more To Do Roles; these must be set up before you can set up the approval profile. After the approval profile(s) are set up, they must be referenced on the adjustment types that they govern.
Cancel Reason - Bill	Admin Menu, Bill Cancel Reason
Cancel Reason - Payment	Admin Menu, Payment Cancel Reason
Cancel Reason - Adjustment	Admin Menu, Adjustment Cancel Reason
Tender Type	Admin Menu, Tender Type
Tender Source	Admin Menu, Tender Source
A/P Request Type	Admin Menu, A/P Request Type
Installation	Admin Menu, Installation Options - Framework and Admin Menu, Installation Options. Many fields on the installation record impact the financial transaction environment. Refer to the description of the Billing and Financial Transaction tabs and the Messages tab in the Framework page for more information.
Algorithm	Admin Menu, Algorithm. You will need to set up an algorithm that distributes payments.	If you ran the CI_COPPY DB process described above, this algorithm will have been set up for you.
Algorithm	Admin Menu, Algorithm. You will need to set up an algorithm that handles overpayment situations.
Algorithm	Admin Menu, Algorithm. You may need to set up an algorithm if specific taxpayers can have individual bill due dates.
Algorithm	Admin Menu, Algorithm. You may need to set up an algorithm if you want the system to levy a non-sufficient funds charge if a payment is canceled due to non-sufficient funds.
Algorithm	Admin Menu, Algorithm. You will need to set up an algorithm that formats the bill information that is displayed throughout the system. This algorithm is plugged-in on the installation record.	You can run the CI_COPIN DB process to copy many of the algorithms that format basic information from the demonstration database. Refer to How To Copy An Algorithm From The Demo Database for more information.
Algorithm	Admin Menu, Algorithm. You will need to set up an algorithm that formats the payment information that is displayed throughout the system. This algorithm is plugged-in on the installation record.	If you ran the CI_COPIN DB process described above, this algorithm will have been set up for you
Algorithm	Admin Menu, Algorithm. You will need to set up an algorithm that defaults the amount when a payment is manually added. This algorithm also calculates the amount of an automatic payment for a bill for an account with an active auto pay option. This algorithm is plugged-in on the installation record.	If you ran the CI_COPIN DB process described above, this algorithm will have been set up for you
Algorithm	Admin Menu, Algorithm. Refer to Account Type for other available plug-in spots that may be used by your implementation to perform additional logic when processing payments and bills.
Return to Account Type	Admin Menu, Account Type. You will need to plug-in the algorithms defined above on your account types.
*Customer Environment*
Account Management Group	Admin Menu, Account Management Group. Note: You will probably have to set up To Do Type and To Do Roles before you can set up account management groups. Refer to Assigning A To Do Role for more information on how account management groups may be used to define an entry's role.
Account Relationship	Admin Menu, Account Relationship Type
Alert Type	Admin Menu, Alert Type
Bill Message	Admin Menu, Bill Message
Algorithm	Admin Menu, Algorithm. If you have software capable of reconstructing an image of a bill in a PDF (for the purpose of online display), you will need to create an algorithm that formats the extract records that are sent to your bill image software.	Refer to How To Copy An Algorithm From The Demo Database for more information.
Bill Route Type	Admin Menu, Bill Route Type
Contract Quantity Type	Admin Menu, Contract Quantity Type
Algorithm	Admin Menu, Algorithm. If you have software capable of reconstructing an image of a letter in a PDF (for the purpose of online display), you will need to create an algorithm that formats the extract records that are sent to your letter image software.	If you ran the CI_COPD1 DB process described above, these algorithms will have been set up for you.
Letter Template	Admin Menu, Letter Template
Customer Contact Class	Admin Menu, Customer Contact Class
Customer Contact Type	Admin Menu, Customer Contact Type
Algorithm	Admin Menu, Algorithm. You may need to set up the algorithms that determine if person ID's are in a predefined format.
Identifier Type	Admin Menu, Identifier Type
Industry Codes	Admin Menu, Industry Code
Tax Exempt Type	Admin Menu, Tax Exempt Type
Algorithm	Admin Menu, Algorithm. You may need to set up the algorithms that determine if phone numbers are in a predefined format.
Phone Type	Admin Menu, Phone Type
Person Relationship Type	Admin Menu, Person Relationship Type.
Person Type	Admin Menu, Person Type
Algorithm	Admin Menu, Algorithm. You will need to set up an algorithm that formats the person information that is displayed throughout the system. This algorithm is plugged-in on the installation record.	If you ran the CI_COPIN DB process described above, this algorithm will have been set up for you
Algorithm	Admin Menu, Algorithm. You will need to set up an algorithm to validate a person's name. This algorithm is plugged-in on the installation record.	If you ran the CI_COPIN DB process described above, this algorithm will have been set up for you
Algorithm	Admin Menu, Algorithm. You can override the system's standard account information string by setting up an algorithm that produces this string of information. This algorithm is plugged-in on the installation record.
Algorithm	Admin Menu, Algorithm. If you have software capable of reconstructing an image of a letter in a PDF for the purpose of online display, you will need to create an algorithm that renders this PDF. This algorithm is plugged-in on the installation record.	If you ran the CI_COPD1 DB process described above, this algorithm will have been set up for you
Algorithm	Admin Menu, Algorithm. If you have software capable of reconstructing an image of a bill in a PDF for the purpose of online display, you will need to create an algorithm that renders this PDF. This algorithm is plugged-in on the installation record.	If you ran the CI_COPD1 DB process described above, this algorithm will have been set up for you
Installation	Admin Menu, Installation Options. Many fields on the installation record impact the Customer Environment. Refer to the description of the Main, Person, and Account tabs for more information.
*Automatic Payment (EFT) Environment*
Algorithm	Admin Menu, Algorithm. You will need to set up an algorithm to create automatic payments. This algorithm is plugged-in on the installation record.	You can run the CI_COPAP DB process to copy this algorithm (and other autopay-oriented algorithms) from the demonstration database. Refer to How To Copy An Algorithm From The Demo Database for more information.
Tender Source	Admin Menu, Tender Source Note: Earlier, you created tender sources for the remittance processor and your cash drawers. At this point, you'll need to add at least one tender source for automatic payments. Why? Because automatic payments get linked to a tender control (which, in turn, gets linked to a tender source) when they are interfaced out of the system.
Algorithm	Admin Menu, Algorithm. You will need to set up the appropriate automatic payment date calculation algorithm to populate the extract, GL interface and payment dates on automatic payments.	If you ran the CI_COPAP DB process described above, this algorithm will have been set up for you
Auto Pay Route Type	Admin Menu, Auto Pay Route Type
Tender Type	Admin Menu, Tender Type Note: Earlier, you created tender types for things like cash, checks, etc. At this point, you'll need to add a tender type for each type of automatic payments (e.g., direct debt, credit card, etc.).
Work Calendar	Admin Menu, Work Calendar. You need only set up additional work calendars if the auto pay sources (i.e., the financial institutions) have different working days than does your organization
Algorithm	Admin Menu, Algorithm. If you need to validate the taxpayer's bank account or credit card number, you will need to set up the appropriate validation algorithms.	If you ran the CI_COPAP DB process described above, this algorithm will have been set up for you
Auto Pay Source Type	Admin Menu, Auto Pay Source Type
Algorithm	Admin Menu, Algorithm. You may need to set up an algorithm if your taxpayers can define a maximum withdrawal limit on their autopay options.	If you ran the CI_COPAP DB process described above, this algorithm will have been set up for you
Return to Account Type	Admin Menu, Account Type. You should plug-in the Autopay Over Limit Algorithm in each appropriate Account Type.
*Characteristics*
Algorithm	Admin Menu, Algorithm. If you have ad hoc characteristic types, you may need to set up the algorithms that control how they are validated
Foreign Key Reference	Admin Menu, FK Reference. If you have foreign key characteristic types, you may need to set up foreign key references to control how the user selects the characteristic values (and how the foreign key values are validated).	All base package FK references are automatically populated
Characteristic Type & Values	Admin Menu, Characteristic Type
*Location Environment*
Location Type	Admin Menu, Location Type
Algorithm	Admin Menu, Algorithm. You will need to set up an algorithm to format the standard location info that appears throughout the system. This algorithm is plugged-in on the installation record.	If you ran the CI_COPIN DB process described above, this algorithm will have been set up for you
Algorithm	Admin Menu, Algorithm. You may need to set up the algorithms that determine if geographic ID's are in a predefined format.
Geographic Type	Admin Menu, Geographic Type
*Rate Environment*
Frequency	Admin Menu, Frequency
Rate Quantity Identifier	Admin Menu, Rate Quantity Identifier
Algorithm Type	Admin Menu, Algorithm Type. If you create new Rate Quantity Rules you must set up an algorithm type for each such rule (the algorithm type defines the types of parameters that are passed to the RQ rule).	All base package algorithm types are automatically populated
Rate Quantity Rule	Admin Menu, Rate Quantity Rule
Rate Factor	Main Menu, Rates, Rate Factor
Rate	Main Menu, Rates, Rate Schedule
Rate Version	Main Menu, Rates, Rate Version
Algorithm	Admin Menu, Algorithm. If you use algorithms to dynamically change step boundaries, calculate prices, or implement rate component eligibility rules, you must set up these algorithms.
Rate Component	Main Menu, Rates, Rate Component
Rate Factor Value	Main Menu, Rates, Rate Factor Values
*Obligation Configuration*
Filing Calendar	Admin Menu, Filing Calendar
Tax Type	Admin Menu, Tax Type
Algorithm	Admin Menu, Algorithm. You will need to set up the algorithms that determine: Special criteria to be tested before an obligation is severed. Special processing that should take place prior to the completion of a bill that references obligations of a given type. Special processing that should take place during completion of a bill that references obligations of a given type. Special processing that should take place when obligations of a given type are created. Special processing that should take place when a financial transaction is frozen for obligations of a given type.
Algorithm	Admin Menu, Algorithm. You may want to set up an algorithm that formats the obligation information that is displayed throughout the system. This algorithm is plugged-in on the installation record.
Algorithm	Admin Menu, Algorithm. You may want to set up an algorithm that formats the obligation information that is displayed throughout the system for a specific obligation type. This algorithm is plugged-in on the Obligation Type.
Bill Cycle, Bill Cycle Schedule	Admin Menu, Bill Cycle
Bill Period, Bill Period Schedule	Admin Menu, Bill Period
Obligation Type	Admin Menu, Obligation Type
Obligation Type Start Options	Admin Menu, Obligation Type Start Option
*Wrap Up*
Algorithm	Admin Menu, Algorithm. You will need to set up the algorithms that determine: Special alerts on Control Central (assuming you have special alerts)
Installation Options	Admin Menu, Installation Options - Framework and Admin Menu, Installation Options. At this point, it's a good idea to double-check everything on the installation record.
Postal Default	Admin Menu, Postal Code Default

If you have cash drawers you will also need to set up the following information:

Create a person / account to which you will link your over / under obligation. Refer How To Get An Unbalanced Tender Control In Balance (Fixing Over/Under) for more information.
Create an obligation to which your over/under payments will be linked. This obligation will reference your over / under obligation type. Refer to Over / Under Cash Drawer Obligations for more information.

If you upload payments from an external source (e.g., a remittance processor or lock box), you must set up the following information:

Create a person and account to which the system will link payments with invalid account. Refer to Phase 3 - Create Payment Events, Tenders, Payments and Payment Segments for information about the process that books invalid payments to this account. Refer to How To Transfer A Payment From One Account To Another for how a user transfers the payment from the invalid account to the correct account (once known).
Create an obligation for this account. This obligation will reference your payment suspense obligation type. The system needs this obligation so that it can distribute the invalid account's payment (and this is necessary so that cash will reflect the payment). Refer to Payment Upload Error Obligations for more information.
Update the tender source associated with the respective source of payments to indicate the obligation created in the previous step should be used for payments with invalid accounts. Refer to Setting Up Tender Sources for more information.
Because the payment upload process simply books payments that reference invalid accounts to the account associated with the suspense obligation on the payment's tender source, this account should belong to an account type with the appropriate payment distribution algorithms. This may entail creating a new account type that will only be used on suspense accounts.

The remaining sections describe additional control tables that must be set up for specific functional areas.