Installment and Pre-Collect Payment Plans Services

The Vendor is required to provide installment and pre-collect payment plans services for include:
1. Customized student account installment payment plan
• Allow fees to be paid by the student and authorized user to the contractor.
• Provide flexible number of payments per semester to be determined by university.
• Require regularly scheduled payments to be processed as auto-pay transactions.
• More than one authorized user to set up a separate plan for a student.
• Change the number of payments, budget amount, remaining budget amount, payment method, cancel or change the deadline and designated payment date.
• Create “hidden” payment plans that may be activated on-demand for individual students.
• Payment plan balances to be controlled manually by the plan owner or by university.
• Payment plan balances to be controlled automatically by integration with PeopleSoft student administration and oracle student management cloud.
• Create batch outstanding balance and payment files that university can manually upload to university student information system.
• Post payments automatically into university student information system.
• Generate reports on a daily, weekly, monthly, semester, or yearly basis.
• Change the text of all email notifications to students and authorized users.
• Send email notifications for upcoming plans, future plans, upcoming payment, missed payment, and plan termination.
• Seamlessly integrate with contractor’s electronic billing and payment processing system.
2. Customized pre-collect payment plan
• Provide a customized pre-collection payment plan for students who are currently enrolled, have a delinquent balance, and are on a registration hold.
• Transmit and process a daily file containing student name, id #, email address, and balance due.
• Determine the number of payments allowed and minimum payment amount.
• Change the date of the payment and payment amount.
• Send email notifications encouraging students to enroll in the pre-collect option.
• Staff to make notes on accounts.
• Allow payers to create a standalone account to access their payment plans without using single sign-on, supporting users who no longer have access to the student portal.
- Customer service: (note: all potential costs should be restated in section x pricing schedule).
• Customer service support to the university business office.
• User groups and how they function. State how input from user groups is incorporated into the roadmap of product development.
• Long-term goals and objectives with regard to higher education.
- Application technology:
• Modules function as an integrated whole and detail any limitations in their ability to function independently from other modules.
• The application security features for data, for each module, and for the system.
• All row-level security options as well as any field-level encryption available.
• Transactions or functions that are not done on a real time basis and list batch jobs required for this function.
• Tools and expertise which university technical staff would use to support, troubleshoot, configure, or customize the application.
• Customizations available and associated cost (i.e., hourly and fixed fee).
• Configuration and customization will affect future releases of software.
• Workflow functionality included with the application and provide a list of any function for which workflow is already built and delivered.