To enable modules:
Select Administration > Hierarchy > Settings > Modules.
Enter the hierarchy ID in the Hierarchy ID field, or click the link and select a node from the hierarchy tree.
Select Override inheritance.
Note:The Override inheritance check box overrides the settings from the parent hierarchy ID, which is listed in the Inherited from field. This allows you to configure the module settings differently for the selected hierarchy ID. If this check box is not selected, you will not be able to make any changes on this screen, and the selected hierarchy ID will retain the settings of the parent node.
In the Enabled Modules list, select the modules you want to enable. For a complete list of modules, see the table below.
Note:Only those modules that have been purchased by your company or organization can be selected.
Click Save.
Module |
Description |
---|---|
Use the Account Management module to configure and edit account settings. This includes updating the account holder’s contact information, verifying the current balance, changing account limits, changing Merchant Category Code Groups, requesting new or replacement cards, and closing or suspending accounts. For more information, see Card Accounts. |
|
Use the Chart of Accounts module to manage accounting codes. For more information, see Chart of Accounts and Accounting Codes. |
|
If Convenience Checks are enabled for your organization, use the Convenience Checks module to manage your convenience check program. This module is available only for Purchasing Card programs and can be enabled only if the Account Management module is also enabled. For more information, see Managing Convenience Checks. |
|
Use the Custom Fields module to create and edit custom fields for the following modules: Transaction, Payables, Merchant, Employee, Account, and Merchant Category Codes. For transaction custom fields, you can also set role restrictions to control which user roles have edit access to the custom fields. For more information, see Custom Fields. |
|
Use the Custom Mappers module if after running a flex mapper you still require data beyond the scope of a flex mapper. Contact your J.P. Morgan program coordinator or relationship manager for more information about custom mappers. |
|
Use the Cycles module to create and modify cycles based on the accounting needs of your company or organization. You can configure PaymentNet to automatically generate the periods within a cycle, or you can manually create the periods. For more information, see Cycles. |
|
Use the Electronic Payment module to enable users to make card account payments online and to review completed and recurring payments. For more information about setting up banking details and viewing payment information, see Managing Bank Account Information and Viewing Payment Information. |
|
Use the Electronic Statement module to define which accounts can access their statements online through PaymentNet. If this module is enabled, cardholders can choose to receive electronic reminders when their statements are ready for viewing. For more information, Setting Up Statement Reminders. |
|
Use the Flex Mappers module if your organization needs to move data between PaymentNet and your organization’s accounting system, such as a general ledger (GL) or enterprise resource planning (ERP) system. Flex mappers are data export files in a specific layout and format, usually a limited or fixed-length text file. For more information, see Flex Mappers. |
|
Use the Imports module to transfer data to PaymentNet from an external file. Import files are useful for importing large amounts of data to PaymentNet, such as when setting up a new organization or making a large number of changes to existing data. For more information, see Imports. |
|
Use the Merchant Category Code (MCC) module to assign default accounting codes to an MCC. An MCC is a four-digit number assigned to a business by Visa or MasterCard. It is used to classify businesses by the type of goods or services they provide and allows enhanced merchant data to be passed to PaymentNet. Each merchant is responsible for selecting their own MCC when they enroll to accept Visa or MasterCard. For more information, see Merchant Category Codes. |
|
Use the Merchant Category Code Group (MCCG) module to submit a request to create custom groups of related MCCs. MCCGs must be created at the processor, and many are predefined. You can use this module to request new MCCGs so that you can easily apply spending restrictions and control cardholders' ability to make purchases from all the merchants in a group. For example, you could request a new MCCG called Prohibited Airlines to which individual airline carriers would be assigned by their MCCs, and then exclude this MCCG from your cardholders' accounts to prevent them from using these airlines. For more information, see Merchant Category Code Groups. |
|
Use the Merchants module to view details about all the merchants in the system. A merchant is any business or organization from which goods and services are purchased. The merchant information in PaymentNet is supplied by the card associations and is updated automatically. You can manually configure merchant information for your organization as necessary. For more information, see Merchant Settings. |
|
If Single-Use Accounts are enabled for your organization, use the Payables module to create new payables, view and modify existing payables, resolve exceptions, and manage vendors. For more information, see SUA Payables. |
|
Use the Query module to search for information and filter the data you want to view. You can save a custom query and use it as often as you need it. For more information, see Queries. |
|
Use the Transaction Defaulting module to automatically apply default accounting codes to each transaction based on the employee, hierarchy, merchant, MCC, account, or customer code. For more information, see Configuring Transaction Hierarchy Settings. |
|
Use the Transactions module to manage transaction details like adding transaction notes, reviewing and approving transactions, and applying accounting codes. For more information, see Transactions. |
|
Login Credentials - Auto E-mail |
Use this option to have PaymentNet automatically send an email message to new system users with their organization ID, user ID, and password information. For new users, these login credentials are sent in separate emails. In addition, PaymentNet sends an existing user their new password when it is changed by anyone other than the user. For example, if a program administrator performs a password reset for a cardholder, the cardholder will receive an email with their new password. PaymentNet sends these messages to the email address listed in the employee record. You can track when PaymentNet sends credentials by adding the Credentials Sent column to the Employee List screen view. For more information, see Customizing Your Screen View. |
Sync Employee E-mail with Account E-mail Addresses |
Use this option to keep account email addresses in sync with employee email addresses. If this option is enabled, then any time an employee’s email address is changed in PaymentNet, the email address for all the accounts assigned to that employee’s user ID will also be updated. This change will occur if the employee updates the email address saved in their profile or if a program administrator changes it on the Employee Detail screen. In addition, if a program administrator assigns a new account to an employee or updates the assigned user ID for an account, the email address for the account will be updated to match the employee’s email address. Once the address change is saved in PaymentNet, the new email address will take effect within the hour. The cardholder’s email address cannot be changed on the Account Detail screen when this option is in effect. Note: The first time the hierarchy settings are saved with this option selected, all card accounts will be updated overnight with the email address currently specified for the cardholder. If the employee’s email address and the account email address are not the same, the email address for the account will be overwritten. This action cannot be reversed. Users will receive an email notification when the email address for their account has been changed. Selecting this option also changes the effect of updating email addresses via import files. If you use an Account Import file to update the email address on an account, the email address will also be updated in the cardholder’s user profile and in all of the accounts assigned to the same user ID. If you use an Employee Import file to update the email address for an employee, the email address will be updated in the cardholder’s profile and also in all of the accounts assigned to that employee’s user ID. For more information about import files, see Imports. This option has no effect on single-use accounts. |