This option allows users with the proper permissions to enter configuration details for any installed modules. ADMIN access as well as any role with the permission 'MODULE_CONFIGURATIONSTORE' granted to it will be able to access the "Configuration' option under System.
Users with USAS_MANAGER access will have access to a subset of these options.
View Configuration
- From the System menu select 'Configuration'
- Click on Description of the one you would like to view. It will highlight in Blue
- A description box will open up to the right and an Edit box below that.
Edit Configuration
- From the System menu select 'Configuration'
- Click on beside desired module
- Make any necessary changes
- Click on
Payable Module Configuration
Is the Payable's module initialized? Indicates whether Payable Journals have been initialized.
The Payables module is initialized by default after data has been imported.
Accounts Receivable Billing Email Setup
Allows user to enter a From Email and CC Email to be used when emailing AR Billings. In order for this configuration option to be available, the district must have the Accounts Receivable and Email Notification Services modules installed first.
Activity Ledger Configuration
If initialized, indicates Activity Ledgers should be cleared and reposted at startup.
Application Configuration
This configuration option will default to Production with Notifications and Jobs enabled unless the APPLICATION_INSTANCE_TYPE is updated in the Docker Configuration. When configuring Non-Production instances (training/test) this can be used to prevent scheduled jobs or notifications from sending from both the live database and test database. Uncheck the corresponding check box to disable External Notifications or User Job Execution.
For additional information see the Redesign Technical Documentation page for How to Configure Non-Production Instances.
Instance Type | |
---|---|
Production | Default production mode |
Support | Typically a temporary copy of a given districts production data for resolving support issues |
Training | A training instance typically contains anonymized data |
Demo | A Demo instance typically contains anonymized data |
Development | Reserved for use by the SSDT |
Authentication and Password Requirement Configuration
Allows user to make changes the user password configuration. NOTE: this will affect all users on the system.
- alter the minimum length of a password and optionally require mixed case and/or numeric values as part of the password
- alter password expiration. Sets the number of days between required password changes. Default value is 90 days. If set to zero, passwords will not automatically expire.
- Pre-Expired Password: If a user's password is changed by an administrator, should the password be immediately expired? This will require the user to change the password on the next login. Does not affect users who hold the 'ADMINISTRATORS' role.
Classic Migration Configuration
Contains the date and time Classic's ADJUST program was run when closing the last fiscal year prior to export.
The date and time will be filled in automatically after the data has been imported. The ADJUST date and time are pulled from the 'Fiscal Year Closed' field in Classic's USACON.
Database Administration Configuration
Disbursement Configuration
These options apply to the creation of Disbursements.
Collapse Items for Same Account: If this is checked and there are multiple invoice items posted to the same account, the accounts will be collapsed on the Disbursement.
Max Items Per Disbursement: The maximum number of items per disbursement. The value in this field is calculated using the values entered in the following fields and cannot be manually modified (Stub Lines divided by Max Items per Disbursement). If the 'Use Overflow Stubs' option is selected this limit will be ignored.
Num Lines Per Item: The number of lines to be used per line item.Used to calculate 'Max Items Per Disbursement.'
Stub Lines: Determines the total number of lines that can be used on the disbursement. Used to calculate 'Max Items Per Disbursement.'
Use Overflow Stubs: If this option is checked, the Max Items Per Disbursement limit will be ignored.
EIS Classic Integration Configuration
Before setting up the EIS configuration, you must first install the 'EIS Classic Integration' module from the Modules option under System.
Allows user to
- enter a pending threshold amount.
- By checkmarking 'AUTOMATIC', it will automatically flag a 6xx level object code item as an 'inventory item' when invoicing a PO item. If left unchecked, user will be prompted in AP invoice to flag 5xx and 6xx level object code items as an 'inventory item'.
The SSDT Inventory Pending Extract report will pull the flagged items based on the spreadsheet.
EMIS SOAP Service Configuration
Before extracting your fiscal year data for financial reporting, you must enter the fiscal year in which you are reporting for. For example, if you are reporting data for FY21, enter 2021 as the fiscal year. This will need to be reset for successive years.
Email Configuration
Available when the Email Notification Services module is enabled. The Default Administrator Address is not being used at this time so this can be left as "root." The Default From Address will be used when sending emails from the application (Report Bundle Immediate option or via the Job Scheduler). The Port and SMTP Host information must also be entered for emails to be sent. Generally, the Port and SMTP Host information would be known by the ITC.
Encumbrance Module Configuration
Is the Encumbrance module initialized? Indicates whether Encumbrance ledgers have been initialized.
Encumbrances are initialized by default after data has been imported.
Expenditure Module Configuration
Is the Expenditure module initialized? Indicates whether Expenditure ledgers have been initialized.
Expenditure are initialized by default after data has been imported.
Import Utility Configuration
GL Journal Entry Module Configuration
Indicates whether the general ledger journal entries have been initialized.
GL Ledger journal entries are initialized by default after data has been imported.
IRS Form 1099 Submission Configuration
The box should be check if the district is submitting their 1099 File electronically to the IRS themselves. When checked, it populates required submitter fields in the 1099 Extract program for the entity. A 5-digit Transmitter Control Code (TCC) must be received from IRS and entered here in order to file electronically using the IRS FIRE system. If you don't have a TCC, you can click here for more information on how to apply for one. An application for a TCC code should be done well in advance of 1099 processing. Users with USAS_Manager and Administrator access can update this configuration option.
PreEncumbrance Module Configuration
Am I tracking requisitioned amounts? Indicates whether the Preencumbrance module has been initialized.
Revenue Module Configuration
Is the Revenue module initialized? Indicates whether Revenue ledgers have been initialized.
Revenues are initialized by default after data has been imported.
Transaction Configuration
This option will allow the district to track the highest transaction number used instead of the system using the highest number retrieved from the database. This will be helpful in eliminating gaps in transaction numbers.
Check Number
Separate bank accounts created under CORE/BANK accounts may contain the same check number. The highest number in the configuration would be for all Bank Accounts.
Example:
When vendors are imported over, if the district highest number was 900100 in classic, when creating a new vendor in redesign, it's going to default to the highest number so it would auto assign 900101. With the Transaction Configuration option, you have the option to control the 'highest' transaction number by entering a number of your choice. NOTE: It does work a bit differently than Classic. To auto assign, the system will base it off of the 'highest vendor number' entered in the Transaction Configuration screen. For example, if I want to start incrementing from 9428, and the next number vendor on file is 13413, that is a huge gap between the two numbers. I would enter '13413' as my highest vendor in Transaction Configuration and when I create a new vendor, it will think 13413 is my highest and then it will look at the last one used (9428) and increment from there and assign 9429.
USPS Configuration
When the 'USPS Integration Module' is installed (under SYSTEM/Modules), the USPS Configure information will be automatically filled in.
Vendor Tax ID Number Configuration
Allows validation when entering a new vendor or using an existing vendor on a Purchase Order or Invoice transaction, based on district configuration flag.
No Warning: The configuration will default to show no error or warning related to Vendor Tax ID numbers.
Require for All Vendors: An error will show for any vendor without a Vendor Tax ID number entered. On the Vendor record, a Vendor Tax ID number must be entered for the vendor before the user is able to save the current transaction.
Require for 1099 Vendors: An error will show for any vendor with a 1099 Type different than 'Non 1099' without a Vendor Tax ID number entered. On the Vendor record, a Vendor Tax ID number must be entered for the vendor before the user is able to save the current transaction.
Warn for All Vendors: A warning will show for any vendor without a Vendor Tax ID number entered.
Warn for 1099 Vendors: A warning will show for any vendor with a 1099 Type different than 'Non 1099' without a Vendor Tax ID number entered.