This lets you establish rules for configuring selected fields on the Add/Edit Customer form. Depending on the field, rules can specify whether the field is required or restricted, and establish defaults. Rules can be based on Account Type, Status or User Group as applicable.You can:
Configure Customer fields as being required when creating or editing an account.
Require for specific Account Type(s)
Require for all Account Types
Configure default values for Customer fields when creating an account. This supports:
Default by specific Account Type(s)
Default for all Account Types
Defaults using a combination of both
Configure what fields cannot be edited when creating or editing an account. This can be configured using a combination of Account Type, Account Status and IDI platform User Group.
Some fields will only have a subset of these options available. The following considerations determine the options for each field:
Fields that are required by the IDI platform will not have an option to set a required rule.
Check box fields are already considered Required because they must have a Yes or No value. The IDI platform does not support Unspecified for these fields.
Fields that are used for account-specific information such as Name, Email, or SSN do not allow default values.
Individual fields that are part of a logical grouping of fields are grouped together for ease of administration.
See to see what options are available for each configurable field.
Configuration Options
Group
Field Name
Require
Default
Restrict
Notes
Basic Info
Account Type
Account Status
Account Number
Account Manager
Customer Name
Disallow Checks/ACH
This lets you flag accounts with a history of bad check writing. Flagged customer accounts will not be allowed to make ACH payments through Desktop Client, Customer Care, and OnlineBill. For these customers, only guaranteed funds will be allowed for payments (i.e. cash or approved credit card transactions). This can help reduce returned check fees.
Note
Identifying bad check writers is a manual process and establishing criteria is up to individual carriers.
This setting is also available in Desktop Client You only need to flag the account in one application or the other (i.e. flagging the account In Customer Care also flags the account in Desktop Client and vice versa). You can restrict which users can toggle this setting in both applications. In Desktop Client the setting is restricted by permission profiles. In Customer Care the setting is restricted by Groups in Customer Field Settings.
Disable E-Pay Notifications
This lets you disable E-Pay notifications for the account. When the property is set, the account will be omitted from IDI platform notifications that use the E-Pay Account Notifications or E-Pay Transaction Notifications data sources. The E-Pay Account Notifications and E-Pay Transaction Notifications data sources will omit accounts where the EPayNotificationOptOut property is set to true.
When creating a new customer, the new Disable E-Pay Notifications property defaults to unchecked. Note: This property is not available for Prospect accounts.
Market
Sales Associate
State
Region
Zone
Currency
Language
Establish Date
CPNI Opt In
Tax Information
All Tax Information fields considered as a single group.
Credit Information
DOB
SSN
FEIN
DL #
DL State
Duns #
Accessibility
All Accessibility fields considered as a single group.
*Contact configurations apply to both the primary customer contact and the billing contact. They do not apply to other contact types.
Out-of-the-box configuration rules are added when this functionality is deployed on an existing system. This is to maintain consistency for fields that had pre-existing rules governing their behavior. These are described in .
Out-of-the-Box Rules
Out-of-the-Box configuration rules are provided when Field Configuration functionality is deployed on an existing system. This is to maintain consistency for items that had pre-existing rules governing their behavior. These rules will ensure system behavior is not altered upon upgrade; however, you may modify or remove these rules as needed.
Default Country
The Detault Country setting (Manage > Settings > Customer > Default Country) is no longer available as of version 18.7. Instead, this can be set up using Field Configuration. To account for the current Default Country on existing systems, an out-of-the-box rule is added to set the default value for all account types based on what was previously set via Manage > Settings.
Contact Fields
Customer Care previously required several fields on Primary and Billing contacts. Going forward, you have control over these fields. To maintain consistency on deployment, rules to require the following fields are provided out-of-the-box:
Address 1 – all account types
City – all account types
State – all account types
Zip – all account types
First Name / Last Name – account types where tax class = residential
Company Name – account types where tax class = business or industrial
Sales Channel
If the SaaS Config setting Require sales associate when creating new Customer is true, a configuration rule will be created to require the Sales Channel field. Note: As of version 18.7, the SaaS Config setting is no longer used. It was only accessible by IDI.
Customer Field Configuration Page
Selecting MANAGE > Customer Field Configuration displays the page where you add and manage configuration rules. This page lets you select individual fields to configure rules (+ Add Field). Existing rules are listed in alphabetical order. An option to filter/search by specific text is available to quickly find a field. For listed fields, you can show/hide the rules for an individual field (>), all fields (far right expand all/collapse all). And you can edit or delete the rule configuration for a listed field as needed via the associated edit (blue pencil) and delete (red trash can) buttons at the right.
(Show Picture)
For details on adding and managing rules, see: