This subsystem captures all necessary information to enroll a customer. The information can be manually entered through an administrative interface, manual entered through a guided wizard interface or entered directly by the customer through a web interface.
Special features include
This subsystem interfaces directly with Equifax for both residential and commercial credit analysis. This interface is used during the enrollment process to determine if a deposit will be required. The web interface returns a credit score and calculates a required deposit amount based upon that score.
Special features include
This subsystem interfaces directly with Energy Service Group (ESG) for both residential and commercial customers. ESG was chosen as the default EDI provider as they offered a common transaction format for all states. The interface is written in such a fashion as to make switching EDI providers relatively easy.
Special features include
This subsystem provides an enrollment interface that is designed to walk a support representative through the process of enrolling a customer. The subsystem uses a step by step approach complete with prompts to ask for customer information and/or responses to authorize their enrollment.
Special features include
This subsystem allows sales staff to capture a variety of information about potential customers. This information can be used to track the progress of sales attempts as well as ultimately creating new enrollments without having to duplicate enrollment information.
Special features include
This subsystem stores plan rates which are then used by all enrollment and invoicing processes. These rates are date/time stamped to insure that enrolling customers get the most current pricing. The rates may be entered into the system manually or uploaded by external systems. Uploaded rates are deemed to be effective until a new rate is uploaded or until the plan is deactivated. These rates are used to define plan pricing during enrollment/re-enrollment and for MTM pricing during invoice creation.
Special features include
This subsystem automatically classifies any past due account or write-off account as delinquent. Alternate collection methods can then be used for these accounts. In severe cases, the accounts can be marked for disconnection and turned over to a collection agency. If payment is made, the system will automatically remove the customer from the delinquent subsystem. Tracking items and notices can be generated from within the subsystem to aid in the collection process.
Special features include
This subsystem is used for cross departmental communication as well as a method for the subsystem to communicate required actions. This subsystem allows for manual as well as automated action item generation. These actions can be assigned to individuals or groups based upon conditions within the system. They aid in the work process associated with REP functions.
Special features include
This subsystem is used to estimate energy demands in the near future. The difference between this daily demand and the physical wholesale power purchased is used to either buy or sell block power to match a client’s estimated power needs.
Special features include
This subsystem automatically generates invoices based upon receiving EDI transactions. Every EDI transaction will automatically be assigned to a pending invoice or create a new invoice should one not exist. The system will analyze all transactions associated with an invoice and mark the invoice as complete once all required transactions have been received.
Special features include
This subsystem generates a list of payments due over the next few weeks and allows support staff to request payment either individually or in bulk. Payment requests that fail are placed in a denied status where notices can be sent via an automated process to the customer indicating that the payment failed and tracking items are generated to support staff indicating that the customer should be contacted to fix the problem. Payment requests that succeed are automatically placed in a received status and then used to generate cash entries that are itemized against invoices. This automatic itemization process allows support staff to easily determine if money is due as well as increasing the accuracy of the aging reports. If payments are reversed, these automatic entries can be corrected manually during the process of balancing bank statements. Any past due account is automatically placed in the delinquent subsystem where alternate collection methods can be used. Credit card and ACH processing is currently handled thru an API interface with CyberSource. The interface is written in such a fashion as to make switching Institutions relatively easy.
Special features include
This subsystem allows manual and automated entry of payable and receivable transactions which can then be itemized against invoices to quickly determine under or over payments. The interface is simple and easy to use. Cash entries can be easily extracted for external system interfaces.
Special features include
This subsystem provides a wide variety of reports and messaging used in conjunction with the retail subsystem. Examples include basic audit reports, pre and post close accounting reports, invoice generation and meter read cycle reports.
Special features include
Reporting examples include but are not limited to
Meter read cycle Ability to automatically generate and distribute system messages thru email. Messaging examples include
This subsystem provides a method of reviewing all changes made to master transactions. The system is designed to retain a history of each modification made. The retention of the change history is dynamic and can be controlled on an individual table by table basis.
Special features include
The subsystem extracts all relevant retail transactions and summarizes them into ledger entries during an accounting close process. Once closed, a period can be locked thus preventing accidental alterations to transactions associated with that period. The summarized ledger entries can then be extracted and entered into alternate accounting systems such as Quick Books if desired. The accounting subsystem is also designed to accept manual entries and can therefore be used as a replacement for external accounting subsystems.
Special features include
This subsystem provides multiple levels of security within the entire application. The first level of security is by table. The security subsystem can restrict access by table or groups of tables. The second level of security is controlled at a company level. Each user defined to the system can be associated with multiple companies. The system can be used to allow anything from full access to no access for a company within authorized tables. The third level of access is by application screen. Users can be allowed or prevented from viewing content on a screen by screen basis.
Special features include
This subsystem is used to automate daily processing. Nearly all functions within the application can be entered into the task scheduler and run on an automated timer throughout the day.
Special features include
This subsystem allows potential customers to perform all common tasks associated with the act of changing energy providers and managing “payment for services” accounts. The guided navigation allows customers to easily review plans and rates currently available, specify payment information, change energy providers and specify a date the change is to take effect. Existing customers can alter payment dates within predefined system limits, view historical invoices and alter personal information associated with the account.
Special features include
Copyright © 2019 Ingbretson Software LLC - All Rights Reserved.