Client-server architecture for managing customer vehicle leasing

[0001] The present invention relates to an improved client-server system for managing customer vehicle leases. In particular, the present invention relates to an improved web-enabled client-server system for managing the customer's credit in connection with customer vehicle leases.

[0002] At any given time, a fleet management company may lease numerous vehicles to a plurality of customers for use in the customers' respective vehicle fleets. For example, a given company may lease several vehicles for use by its sales personnel. Another company may lease vehicles not only for use by its sales personnel but also for use by its field service personnel. Yet another company may lease vehicles not only for use by its sales personnel and field service personnel, but also for its executives. A fleet management company may be hired by these companies to manage the companies' leased vehicle fleets. The types of vehicles being leased and the types of leases may vary not only from customer company to customer company, but also within a single customer company. For many customers, both large and small, the needs of their leased vehicle fleets are complex and constantly shifting over time, which inevitably creates complex management issues for fleet managers who are tasked with making management decisions for multiple customers, each of which has its own unique fleet of leased vehicles.

[0003] Among the issues that face fleet managers is the delicate matter of determining appropriate credit limits for a customer in connection with that customer's leased vehicle fleet. By allowing customers to lease too many vehicles, a fleet manager may create a situation where the customer's ability to meet its lease payment obligations is threatened. At the same time, by placing too many limits on a customer's leasing ability, a fleet manager may not only alienate the customer but also negatively impact the fleet management company by not realizing the full business potential of the fleet manager's relationship with that customer. It is often the case that the standard credit reports provided by third vendors are insufficient to meet the needs of fleet managers who are assessing the credit to be extended to lease customers.

[0004] These issues become particularly acute for fleet managers in connection with customers that are small to medium-sized businesses. Unlike large corporations, financial information about small to medium-sized businesses can be harder to obtain. Furthermore, the margin of error for fleet managers when making decisions on how much credit to extend to small businesses or medium-sized businesses is often less comfortable than it is with respect to large companies because the funds available to such businesses to pay leasing costs are typically significantly less than the funds that a large corporation can access. As such, the inventors herein believe that a tool is needed that allows fleet managers to conduct detailed assessments of their customers' credit profiles so that those fleet managers can make more informed decisions when extending credit to their customers.

[0005] In a previous system operated by the assignee of the present invention, fleet managers did not have access to an integrated tool that provided those fleet managers with detailed views of their customers' financial situations and fleet investments and from which those fleet managers could assess a customer's credit situation. For example, no standardized technique was used to determine the risk associated with each customer's fleet. Each fleet manager was essentially free to make independent decisions with respect to his/her customer's credit situation. Moreover, the acquisition and display of customer financial data was not uniform; no standardized technique was available to identify the reliability of the customer financial data. Moreover, this system was limited in the degree to which it could communicate the reliability of the customer's stored financial information in that the system only noted whether financial statements or tax returns were available for the customer (and for how many previous years this data was available). No indicators were systematically provided as to the reliability of that financial data.

[0006] In an effort to meet the delicate credit profile management needs for managers of leased vehicle fleets, disclosed herein is an integrated system that provides fleet managers with efficient access to vast stores of financial information about a customer and further allows fleet managers with multiple levels of approval authority to submit requests for changes to a customer's credit profile, review those requests, and take final actions on such requests (i.e., approve or reject the requests). Credit reviews are performed in the context of projected leased vehicle needs of the customer to enable a determination of whether the customer's credit profile supports those needs. The inventive system preferably also allows fleet managers to perform periodic reviews of a customer's credit profile.

[0007] Through use of the invention which provides the set of graphical user interfaces (GUIs) disclosed herein, users of the present invention can obtain valuable and detailed views of specific aspects of the customer's various credit limits, the customer's current fleet of leased vehicles, the customer's projected fleet needs, the risk associated with both the customer's current fleet and projected fleet, as well as a wide array of financial information about the customer. Through use of the information displayed in these GUIs, fleet managers can make informed decisions when extending credit to customers.

[0008] As such, according to one aspect of the present invention, disclosed herein is a system for managing a credit profile for a customer having a fleet of leased vehicles, the system comprising: (a) a client computer; (b) a server in communication with the client computer; and (c) a database in communication with the server, the database being configured to store a plurality of customer credit profiles; and wherein the server is configured to (1) provide a plurality of GUIs for display on the client computer, wherein at least one of the GUIs is configured to submit a request for a change to a customer's credit profile in response to user input, at least one of the GUIs is configured to display at least a portion of the customer's credit profile in response to user input, and at least one of the GUIs is configured to receive input from the user corresponding to an action to take on the submitted request, and (2) update the customer's credit profile in accordance with the action input. As used herein, the term “credit profile” refers to stored data about a customer company's creditworthiness in connection with vehicle leasing, and includes at least a credit limit corresponding to a maximum amount of monetary credit that has been authorized for extension to the customer and a leased vehicle limit corresponding to a maximum number of leased vehicles that are authorized for the customer's leased vehicle fleet. However, in addition to these fields, the credit profile may also include other limits placed on customers (e.g., a per vehicle credit limit, a per vehicle aftermarket equipment (AME) credit limit, a maximum maintenance management amount, and a maximum risk management amount), as described in greater detail below. The increased number of such limits is believed to be particularly valuable when making decisions in connection with extending credit to small and medium-sized customers.

[0009] According to another aspect of the present invention, disclosed herein is a method for managing a credit profile for a customer having a fleet of leased vehicles, the method comprising: (a) providing at least one GUI through which a user can submit a request to review a proposed change to a customer's stored credit profile; (b) providing at least one GUI through which a user can view data stored in a customer's credit profile in response to a submitted credit review request; (c) providing at least one GUI through which a user can provide input corresponding to an approval or rejection of the credit profile change request; and (d) updating the customer's stored credit profile in accordance with the user's approval or rejection input.

[0010] According to yet another aspect of the present invention, the financial information about the customer that may be stored in each customer's credit profile is preferably accompanied by an identifier that indicates the level of scrutiny that was applied to that financial information, preferably by an external auditor. Preferably a plurality of identifiers exist, each of which corresponds to a different level of scrutiny. These financial information scrutiny indicators are particularly valuable in connection with managing the credit profiles for customers that are smaller in scale than typical large corporations. For many small to medium-sized businesses, fully audited financial statements are not always readily available, but credit decisions will nevertheless have to be made. By providing the scrutiny indicators for customer financial information discussed above, fleet managers are provided with the ability to make better informed decisions when extending credit to their customers.

[0011] The method preferably further comprises providing at least one GUI through which a user can selectively choose to request a change in either or both of the customer's credit limit and the customer's vehicle limit, and optionally other credit profile parameters as disclosed in greater detail below.

[0012] These and other feature of the invention will be in part apparent and in part pointed out to those of ordinary skill in the art upon a review of the teachings herein. The below described preferred embodiment is meant to be illustrative of the invention and not limiting. Instead the invention is intended to be limited only by the claims and their legal equivalents.

[0044] FIG. 1 depicts a suitable hardware architecture for the preferred embodiment of the present invention. The system 100 comprises an application server 102 (preferably clustered servers) in communication with, at the front end, a plurality of client computers 104₁ through 104_n (preferably via a content switch/load balancer 116 that acts as a network traffic cop as is known in the art). The client computers 104 can interconnect with the application server 102 via any known technique for data communication, although a local area network (LAN) connection such as with an intranet is preferred. At the back end, the application server 102 is preferably in communication with one or more databases and other servers via TCP/IP over an Ethernet connection. Once again, any known technique for data communication can be used by the application server 102 to communicate with the one or more databases and backend servers.

[0045] Application server 102 can preferably access database 120, wherein database 120 is preferably configured to store the customer credit profiles and data related thereto, such as data about the customer's current and planned leased vehicle fleets, including but not limited to data such as quote data and order data for each customers fleet. Database 120 may comprise one or more databases. As shown in FIG. 1, database 120 comprises a database 112 in which the majority of the customer data is stored and a database 114 in which vehicle-specific data from a third party provider such as Autodata is stored. Database 112 may be an Informix production database on a Sun E4500 running Solaris 2.6 and database 114 may be an Oracle production database on an IBM RS6000 running AIX 5.2. If desired, the data stored in databases 112 and 114 can be combined into a single Oracle database. However, it should be understood by those of ordinary skill in the art that still other data storage arrangements could be used. For example, the data stored in databases 112 and 114 could be stored in several distributed databases.

[0046] The application server 102 may also be in communication with a plurality of AS/400's 106, which are preferably configured to maintain vehicle information for leased vehicles from activation through lease deletion. Furthermore, the application server may also be in communication with one or more web servers 108. which are preferably configured to access any vehicle image data that may be needed, as well as a security framework system 110. The security framework server 110 preferably is configured to control which users have access to which GUIs as well as what actions each user can take on each GUI. As explained in greater detail below, this security is preferably based on assigned security clearances for various users.

[0047] Preferred hardware for the application server 102 and web servers 108 comprise IBM RS6000 servers running AIX 5.2. Preferred hardware for the client computers 104 are standard desktop PCs. Preferred hardware for the content switch/load balancer 116 is a Cisco 11503 running a 5.0.0 OS. Preferred hardware for the AS/400s 106 are IBM AS/400s. Preferred hardware for the security framework system servers 110 are HP Proliant DL360 G3 servers running Windows 2000. However, it should be understood by those having ordinary skill in the art that any of a number of hardware platforms are also suitable for use in the practice of the present invention depending on the processing needs and resources that are available to a practitioner of the present invention. Moreover, system configurations other than that shown in FIG. 1 may also be used in the practice of the present invention.

[0048] Application servers 102 preferably execute credit management software that allows users of the client computers 104 to interact with the various databases on the backend of system 100 and manage the credit profile of a customer who leases a fleet of vehicles from one or more lessors. Preferably the client computer users are employees of a fleet management company, which is preferably also the lessor of the leased vehicles. However, this need not be the case as the lessor could be one or more outside entities. Through software installed on the client computers 104 (preferably standard browser software), the client computer users can access the credit management software to manage lease customers' credit profiles via a plurality of interactive graphical user interfaces (GUIs) that are displayed on the client computer by the credit management software.

[0049] As explained in greater detail in connection with FIGS. 2-23(d) and the enclosed exhibits, this credit management software allows the client computer users to, among other things, efficiently evaluate the creditworthiness of lease customers, submit requests for changes in a lease customer's credit profile, and approve or reject such submitted requests.

[0050] FIGS. 2-7 depict various preferred GUI pages through which the user can create and revise a customer's credit profile as well as place and release various holds on the customer's credit and ability to order new leased vehicles. These pages can be accessed by the user upon selection of the “credit profile” link 202 displayed on the left hand side of the GUIs. Page 200 of FIG. 2 is displayed after user selection of the credit conditions folder tab 204. For customers that do not already have a credit profile stored in database 120, page 200 allows the user to enter data for the various fields shown to establish the customer's credit profile. These fields include a credit rating 206 for the customer (preferably an integer value between 1 and 3, with “1” representing a best rating for the customer's creditworthiness, with “3” representing a worst rating for the customer's creditworthiness, and with “2” representing a middle rating for the customer's creditworthiness). However, it should be understood that other rating scales could readily be used in the practice of the present invention. The customer's credit rating controls the level of scrutiny that is applied to orders for leased vehicles placed by a customer; preferably, the better the credit rating, the less scrutiny that is applied and the poorer the credit rating, the more scrutiny that is applied. The fields also include a credit limit amount 208 which represents a maximum amount of credit that can be extended to the customer. In the context of vehicle lease management, this credit limit amount effectively translates to the maximum sum of the delivered prices (or capitalized prices) for the customer's leased vehicles based on the customer's needs over a 12 month period. The fields on page 200 also include a vehicle limit 210, which represents the maximum number of leased vehicles that are authorized by the credit profile for the customer's fleet. Additional fields on page 200 include a value 212 that represents that maximum amount of risk allowed by the credit profile for any given vehicle in the customer's fleet and a value 214 that represents a maximum amount of risk allowed by the credit profile for the aftermarket equipment (AME) added to any given vehicle in the customer's fleet. Additional fields on page 200 include a required deposit amount which represents per vehicle security deposit amount, a required deposit percentage which represents a per vehicle percentage of a delivered vehicle's invoice price that is to be used as a security deposit, a required capitalized price reduction amount which represents money paid down, per vehicle, by the customer that reduces the vehicles' delivered prices, a maximum required capitalized price reduction percentage which represents a percentage of money paid down, per vehicle, by the customer that goes toward reducing the vehicles' delivered prices, the number of months of rent required which is essentially an alternate form of sizing the customer's security deposit, whether a letter of credit from a financial institution (bank) is required, the name of the financial institution providing the letter of credit, whether direct debit is to be used, whether license, tax, and title (LT&T) is to be billed, a maximum maintenance management amount which represents a maximum number of customer vehicles for which the fleet management company will cover maintenance costs with unsecured credit (e.g., providing costs to cover maintenance services for vehicles that the customer possesses but are unsecured vis-à-vis the fleet management company, and a maximum risk management amount which represents a maximum number of customer vehicles for which the fleet management company will provide risk management services with unsecured credit, whether an interest rate floor is to be applied, and a percentage for the floor interest rate percentage, and the 12/24/36/48/60 month depreciation percentage values for the lease term. Page 200 may also include a field for indicating whether equity rollover is required. Page 200 also preferably displays, in a display-only format, the overall reduced book value (RBV) for the customer's current fleet of leased vehicles (preferably excluding any account receivable rent that is due) and the number of leased vehicles in the customer's current fleet.

[0051] Once the customer's credit profile has been created, page 200 preferably becomes display-only, with any changes to the customer's credit profile being initiated through the credit review process described below in connection with FIGS. 10-22. However, this need not be the case.

[0052] Page 300 of FIG. 3 is displayed after user selection of the credit hold folder tab 302. Page 300 preferably displays a table 304 that summarizes the credit hold history for the customer. A credit hold represents a decision by the fleet management company to no longer provide new quotes or place orders for a given customer. Credit holds are typically put in place if a fleet manager has significant credit concerns about the customer. Credit holds can be released by fleet managers with appropriate authority based on the fleet manager's assessment of the customer's financial situation. Table 304 preferably displays not only current credit holds (whose status is indicated in table 304 by the “hold” link 306), but also previous credit holds (whose status is indicated in table 304 with the “release” denomination). Table 304 preferably also identifies, for each credit hold, the hold creation date (and release date where applicable), the name of the user who created the credit hold, and the reason that the credit hold was created. Links 306 are preferably provided in table 304 to call up, upon user selection, a page that allows the user to take an action (such as a release action or a maintain hold action) on a given credit hold. Furthermore, create button 308 is preferably provided for user selection to create a new credit hold for the customer.

[0053] Page 400 of FIG. 4 is preferably displayed upon user selection of the create button 308 on page 300. Page 400 is a create credit hold GUI. Page 400 preferably identifies that the user intends to create a credit hold, displays the name of the user creating the credit hold, and displays the current date in a display-only fashion. Another field is preferably provided for user entry of the reason why the credit hold is being created. After the user has entered such a reason on the page, the user can select the save button 402 to save the credit hold in the system. Alternatively, the user can choose to not create the credit hold by selecting the cancel button 404.

[0054] Page 500 of FIG. 5 is preferably displayed upon user selection of a hold link 306 on page 300. Page 500 is a create credit hold update GUI that allows the user take action on the existing credit hold that corresponds to the link 306 selected in table 304. Page 500 preferably identifies that the user intends to release a credit hold, displays the date on which the credit hold was created, displays the name of the user who created the credit hold, displays the reason why the credit hold was created, displays the name of the user releasing the credit hold, and displays the current date in a display-only fashion. Another field is preferably provided for user entry of the reason why the credit hold is being released. After the user has entered a reason for the release on the page, the user can select the save button 502 to save the credit hold release in the system. Alternatively, the user can choose to maintain the credit hold by selecting the cancel button 504 rather than the save button 502.

[0055] Page 600 of FIG. 6 is displayed after user selection of the order hold folder tab 602. Page 600 preferably displays a table 604 that summarizes the order hold history for the customer. An order hold represents a decision by the fleet management company to no longer place new orders for a given customer. Order holds are typically put in place when conditions are less dire than the conditions for a credit hold. Order holds can be released by fleet managers with appropriate authority based on the fleet manager's assessment of the customer's financial situation. Table 604 preferably displays not only current order holds (whose status is indicated in table 604 by the “hold” denomination), but also previous order holds (whose status is indicated in table 604 with the “release” denomination). Table 604 preferably also identifies, for each order hold, the order hold creation date (or release date where applicable), the name of the user who created the order hold, and the reason that the order hold was created. Furthermore, create button 606 is preferably provided for user selection to create a new order hold or an order hold release for the customer.

[0056] Page 700 of FIG. 7 is preferably displayed upon user selection of the create button 606 on page 600. Page 700 is a create/release order hold GUI. Page 700 preferably includes a field in which the user can specify whether a hold or a release is being created, displays the name of the user creating the order hold, and displays the current date in a display-only fashion. Another field is preferably provided for user entry of the reason why the order hold is being created or released. After the user has entered such a reason on the page, the user can select the save button 702 to save the order hold in the system. Alternatively, the user can choose to not create the order hold by selecting the cancel button 704.

[0057] Also, user selection of the comments tab 216 on any of the pages shown in FIGS. 2, 3, and 6 is preferably effective to display a page (not shown) that allows the user to enter and store any comments he/she may have about the customer's credit profile. Additional details about the system in connection with FIGS. 2-7 are described in Exhibit A appended hereto.

[0058] In the event the user selects the “financial summary” link 802 displayed on the left hand side of the GUIs, the GUI page 800 of FIGS. 8(a)-(c) is preferably displayed. As shown in FIGS. 8(a)-(c), table 802 of page 800 preferably provides a detailed summary of the customer's financial information. This information is preferably displayed in a display-only manner. Table 802 preferably provides this financial information for not only the most recent financial statement date, but also for several of the previous months or years.

[0059] Further still, table 802 preferably identifies the level of scrutiny that was applied to the financial information. Financial information that was audited by a third party auditor is preferably designated by an “audited” indicator. Financial information that has been reviewed by a third party auditor, but has not been fully audited, is preferably designated by a “reviewed” indicator. Financial information that has been compiled by a third party accountant or auditor, but not yet reviewed or audited, is preferably designated by a “compiled” indicator. Financial information that has been created internally by the customer and not subject to any third party auditing is preferably designated by an “internal” indicator. Lastly, financial information that is a tax return for the customer is preferably designated by a “tax return” indicator. These indicators for the different levels of scrutiny that have been applied to customer financial information is particularly important in connection with managing the credit profiles for customers that are smaller in scale than typical large corporations. For many small to medium-sized businesses, fully audited financial statements are not always readily available, but credit decisions will nevertheless have to be made. By providing the scrutiny indicators for customer financial information discussed above, fleet managers are provided with the ability to make better informed decisions when extending credit to their customers.

[0060] If the customer does not already have financial information stored in database 120, or if the user wants to add a new financial information to an existing customer, the user can select the create button 804 on page 800. User selection of button 804 is effective to display page 900 of FIGS. 9(a)-(c). Page 900 includes several pre-defined fields in which the user can enter financial data about the customer. Further, the user can identify the date for which the financial data being entered on page 900 is applicable. Further still, within field 904, the user can identify the type of financial statement from which the financial data being entered on page 900 came. Button 906 is effective upon user selection to clear the fields of the user-entered values. Button 910 is effective upon user selection to return the user to page 800 without making any changes to the customer's stored financial information. Button 908 is effective upon user selection to save the financial information entered on page 900 into the system to update the customer's stored financial information.

[0061] In the event the user wishes to update an existing financial statement displayed in table 802 of page 800, the user can select the link 806 applicable to that statement. User selection of a link 806 is preferably effective to display a page like that shown in FIGS. 9(a)-(c) in which the customer can modify one or more of the financial information data values. Additional details about the system in connection with FIGS. 8(a)-9(c) are described in Exhibit B appended hereto.

[0062] User selection of the “credit review” link 1002 displayed in the left hand side of the GUIs is effective to display credit review history page 1000 of FIG. 10. Page 1000 preferably provides users with a window and link into any past credit reviews performed on a customer as well as any credit review that is currently being performed. Display section 1004 preferably identifies information about the credit review history shown in table 1006, particularly the name and customer identifier for which the credit reviews are applicable. The user can reach page 1000 for the customer whose credit will be reviewed via a variety of selection mechanisms, including the “my customers” button 1020 that is effective upon user selection to display a page that lists all of the customers that have been assigned to a particular user (in a preferred embodiment, different fleet managers are assigned different customers, and database 120 preferably stores data that associates each customer with one or more fleet managers). User selection of a customer or customer number that is listed on such a page is preferably effective to display a page in the customer credit review process for that customer, such as page 1000. The GUIs can also include a “find customer” button 1022 that is effective upon user selection to display a search page for finding customers that match a user-specified search query, a customer identifier search field 1026 for finding customers by their identifiers, and a “create customer” button 1024 through which the user can begin the process of adding a new customer to the system.

[0063] Table 1006 lists the credit review history for the customer identified in section 1004. Column 1008 identifies the review status for each credit review. Preferably, the possible review status values are “working” (for pending credit reviews), “approved” (for previous credit review of a type that was approved), and “rejected” (for previous credit reviews relating to a type that was rejected). These values are displayed as links 1010 within column 1008. Upon user selection of a link 1010, the user is preferably routed to page 1100 described below. Additional read-only columns of table 1006 include a “review created date” column 1012 for identifying the date on which the pertinent credit review was created, a “review created by” column 1014 for identifying the user who created the pertinent credit review, a “next review” column 1016 for identifying a date on which a next credit review is to take place, and a “review type” column 1018 for identifying the type for the pertinent credit review (e.g., an annual credit review, an initial credit review, and credit reviews related to requested increases/decreases in credit).

[0064] User selection of the create button 1030 is preferably effective to display a page through which the user can create a new credit review for the customer identified in section 1004. Preferably, button 1030 is disabled if there is already an open credit review for that customer. FIG. 11 depicts a preferred credit review creation page 1100 that is displayed after selection of button 1030. The page 1100 also displays the following folder tabs: review information tab 1102 (for displaying page 1100), limits tab 1202 (discussion to follow in connection with FIGS. 12(a) and (b)), vehicle tab 1302 (discussion to follow in connection with FIGS. 13, 14(a), and 14(b)), risk tab 1502 (discussion to follow in connection with FIG. 15), notes tab 1602 (discussion to follow in connection with FIGS. 16-20), and approvals tab 2102 (discussion to follow in connection with FIG. 21). When page 1100 is first displayed, preferably only tab 1102 is active.

[0065] Section 1104 of page 1100 provides credit review information for the credit review to be created. Section 1104 identifies the creation date, the user who created the credit review, the date on which the next credit review is to occur (which preferably defaults to the one year anniversary of the creation date, but can preferably be modified by user action), the credit review type (which preferably defaults to an “initial credit review”, but can preferably be modified by user action), and a credit review notes text field in which the user can enter any notes about the created credit review. Possible selections for credit review type preferably include initial credit review, annual credit review, credit increase request, and credit decrease request. Once the user has chosen a next credit review date and selected a type for the credit review (and optionally entered notes for the credit review), the user can select the save button 1106 to activate the folder tabs other than the review information tab 1102. User selection of the back button 1110 is effective to return the user to page 1000. User selection of the print button 1108 is effective to display a page from which the user is provided with the ability to selectively print the different sections of the credit profile report shown in FIGS. 23(a)-(d), preferably in any combination of section. The credit report of FIGS. 23(a)-(d) essentially provides, in a single hard copy report, all of the information that is available for display to the user via the pages 800, 1200, 1300, 1400, 1500, 1700, 1800, 1900 and 2100. Additional details about the system in connection with FIGS. 10 and 11 is described in Exhibit C appended hereto.

[0066] FIGS. 12(a) and (b) depict the credit limits page 1200 that is displayed upon user selection of the limits tab 1202. Page 1200 preferably displays the current values stored in the customer's credit profile for the customer's credit limits (section 1204), credit conditions (section 1206), standard lease term depreciation (section 1208), and interest rate options (section 1210). Page 1200 also preferably allows the user to request modifications to the different data fields within these different sections of the customer's credit profile, wherein the request is subject to approval by a user with appropriate security and approval authority. However, the requested vehicle limit value in column 1212 of section 1204 is preferably a calculated value, wherein this value is calculated from data entered on the risk analysis page 1500 shown in FIG. 15. Among the changes that the user can request via page 1200 are changes to the customer's credit limit, amount per vehicle limit, maximum after market equipment (AME) amount per vehicle, maximum maintenance management amount, maximum risk management amount, credit rating, required deposit amount, required deposit percentage, required capitalized price reduction amount, maximum required capitalized price reduction percentage, the number of months of rent required, whether a letter of credit from a financial institution (bank) is required, the name of the financial institution providing the letter of credit, whether direct debit is to be used, whether license, tax, and title (LT&T) is to be billed, whether equity rollover is required, the 12/24/36/48/60 month depreciation percentage values, whether an interest rate floor is to be applied, and a percentage for the floor interest rate percentage.

[0067] User selection of the save button 1214, the credit review data for the requested credit data for the customer is updated in accordance with the data entered by the user in the various fields of page 1200. Additional details about the system in connection with FIG. 12 are described in Exhibit D appended hereto.

[0068] FIG. 13 depicts the vehicles plan page 1300 that is displayed upon user selection of the vehicles tab 1302. Page 1300 preferably includes a table 1304 that displays data corresponding to the customer's planned fleet of leased vehicles. The data in table 1304 is preferably broken down such that each column corresponds to a different vehicle class. From this page, the user can get a sense of the customer's fleet mix and overall fleet investment. The vehicle class identifiers in each column are preferably links 1306 to a vehicle plan details page 1400 for entering vehicle lease plan data, such as that shown in FIGS. 14(a) and (b).

[0069] Through the vehicle plan details page 1400, the user can enter pertinent data for planned vehicle leases, preferably broken down by vehicle class. However, this need not be the case, as page 1400 could also be designed to enter data on a vehicle-by-vehicle basis. Within field 1402, the user can enter a percentage that corresponds to how much of the customer's leased fleet will be made up of leased vehicles of the selected vehicle class. As would be readily understood by those of ordinary skill in the art, this data can also be entered as an integer representing the number of vehicles within the fleet that will be comprised of vehicles matching the selected vehicle class. Within field 1404, the user can specify a maximum risk amount per vehicle for the selected vehicle class which represents the greatest monthly difference between a vehicle's RBV and estimated actual market value. Within field 1406, the user can specify the lease month in which the maximum risk amount per vehicle for the selected vehicle class is to occur. Within field 1408, the user can specify the break/even (B/E) lease month for risk per vehicle for the selected vehicle class, which signifies the lease month where the vehicle's RBV first becomes equal to or lower than the vehicle's estimated actual market value.

[0070] Alongside each field on page 1400 in which the user can enter data, an edited checkbox is preferably provided, wherein user placement of a check within the checkbox is effective to open up the corresponding field for data entry. The remaining data fields of page 1400 are preferably display-only data values that are retrieved from stored information for the customer. Button 1410 is effective upon user selection to save the vehicle class details entered on page 1400. User selection of button 1412 is effective to revert the various data fields of page 1400 that the user may have modified back to their default settings. Button 1414 is effective upon user selection to return the user to page 1300 of FIG. 13. Additional details about the system in connection with FIGS. 13, 14(a) and 14(b) are described in Exhibit E appended hereto.

[0071] FIG. 15 depicts the risk analysis page 1500 that is displayed upon user selection of the risk tab 1502. Page 1500 preferably interacts with the user to set the requested number of leased vehicles for the customer's fleet and identify the total risk/equity amount for the customer (wherein risk is preferably expressed as a negative number and wherein equity is preferably expressed as a positive number) corresponding to the requested number of leased vehicles. Within the fields of column 1504, the user can enter the number of leased vehicles for each of the following three categories—the number of active units in the customer's current fleet of leased vehicles, the number of new units to be added to the customer's fleet of leased vehicles over a rolling 12 month period, and the number of units to be deleted from the customer's fleet of leased vehicles. Initially, these values are pre-set to default values. These default values can be retrieved from data stored in database 120 corresponding to the customer's current fleet size as well as data corresponding to planned deliveries to the customer's fleet and planned deletions from the customer's fleet over a 12 month period. However, via the edited checkbox, the user can enter new values therefor. The requested vehicle limit value in column 1504 is preferably a display only value that is calculated as the current number of units plus the number of new units to be delivered minus the number of units to be deleted. This value represents the number of vehicles that will be present in the customer's fleet of leased vehicles if the credit profile change request is approved.

[0072] Within the fields of column 1506, the user can enter monetary risk/equity amounts for each of the same three categories described in connection with column 1504. Initially, these values are pre-set to default values. Any of a number of techniques can be used to calculate the default risk values, as would be understood by those having ordinary skill in the art, none of which are preferred in the practice of the present invention so long as these default risk values are reasonably based on the factors discussed below. Market values for vehicles are often calculated using past sales experience, either internally or as determined by a third party data source, for that vehicle or previous year make model and series (MMSs) in combination with an expected vehicle utilization, which includes factors such as the cost of the vehicle, the length of the lease term, lease structure, anticipated mileage for the vehicle during the lease term, and any additional equipment that may be present on the vehicle. The risk values in turn can be determined from the market values based on vehicle depreciation tables, as would be understood by those of ordinary skill in the art. It is worth noting that those of ordinary skill in the art may choose to use more or fewer factors when determining risk values. Via the edited checkbox, the user can enter new values for the risk amount. The requested vehicle limit amount in column 1506 is preferably a display-only value that is calculated as the sum of the values in the three categories of column 1506 that are described above.

[0073] The values in column 1508 are per unit risk/equity amounts that are calculated by dividing the values for each category in column 1506 by that category's corresponding unit count in column 1504.

[0074] User selection of the save button 1510 is effective to update the credit review for the customer in accordance with the data entered on page 1500. User selection of button 1512 is effective to return the data on page 1500 to their default values. Additional details about the system in connection with FIG. 15 are described in Exhibit F appended hereto.

[0075] FIG. 16 depicts a notes index page 1600 that is displayed upon user selection of the notes tab 1602. Page 1600 preferably displays a list of pages that are available for display that summarize various notes about the identified customer. For example, link 1604 is user-selectable to call up page 1700 of FIG. 17. Within section 1702, page 1700 displays various biographical data about the identified customer (e.g. year the customer company was founded, the type of business the customer company is engaged in, etc.). Within field 1704, the user can type in any notes that the user wishes to add about the customer company. Button 1706 is effective upon user selection to save any notes that have been added in field 1704 and button 1708 is effective upon user selection to return the user to page 1600.

[0076] Via link 1606 on page 1600, the user can call up page 1800 of FIG. 18. Within section 1802, page 1800 preferably displays various data about the customer's relationship with the fleet management company (e.g., how long the customer has been a customer, the average amount of time that it takes for the customer to pay its bills to the fleet management company, etc.). Within field 1804, the user can type in any notes that the user wishes to add about the customer company. Button 1806 is effective upon user selection to save any notes that have been added in field 1804 and button 1808 is effective upon user selection to return the user to page 1600.

[0077] Via link 1608 on page 1600, the user can call up page 1900 of FIG. 19. Within section 1902, page 1900 preferably displays various financial information about the customer (e.g., the customer's sales revenue for the latest reporting period, net income/losses, the customer's working capital, etc.). Within field 1904, the user can type in any notes that the user wishes to add about the customer company. Button 1906 is effective upon user selection to save any notes that have been added in field 1904 and button 1908 is effective upon user selection to return the user to page 1600. Page 1900 may optionally include a link to view a page that displays greater financial information about the customer.

[0078] Lastly, via link 1610 on page 1600, the user can call up page 2000 of FIG. 20. Within field 2002, the user can type in any notes that the user wishes to add about the customer company, particularly about the customer's fleet of leased vehicles. Button 2004 is effective upon user selection to save any notes that have been added in field 2002 and button 2006 is effective upon user selection to return the user to page 1600.

[0079] Thus, through page 1600, 1700, 1800, 1900, and 2000, the user is provided with easy access to information that can be of value when evaluating a customer's credit and further possesses the ability to add notes that may subsequently aid analysis of the customer's creditworthiness. Additional details about the system in connection with FIGS. 16-20 are described in Exhibit G appended hereto.

[0080] FIG. 21 depicts a credit review approvals page 2100 that is displayed upon user selection of the approvals tab 2102. Page 2100 preferably shows a list of users who have taken an action in the selected credit review and further allows users to update any notes on that user's own actions (as well as view other user's actions). The user preferably identifies the action that he/she is taking on the credit review via field 2104 and its associated drop down menu. User selection of the “update” button on page 2100 is preferably effective to update the credit profile in accordance with the action identified by field 2104. The preferred choices of action include: (1) submitting a credit review for approval, (2) reviewing a credit review, (3) rejecting a credit review, (4) providing final approval for a credit review. FIG. 22 illustrates an exemplary page 2200 that is displayed after a user takes action via field 2104. Within page 2200, the action to be taken by the user is identified and a notes field 2202 is provided in which the user can enter notes regarding his/her action. Button 2204 is provided for finalizing the action to be taken and button 2206 is provided for returning the user to page 2100. Upon selection of the save button 2204, the status of the credit review is updated in accordance with the action taken by the user.

[0081] Table 2108 preferably shows the credit review approval trail for the identified customer. The table columns are preferably (1) the name of the user who took action on the credit review, (2) the date on which each user took action, (3) the action taken by each user, and (4) the notes entered by the user upon taking action. User selection of one of the links in the name column of table 2108 is preferably effective to call up a page that displays the comments in full for that linked name.

[0082] In the event the user either provides final approval or rejects a credit review, a snapshot of the credit review data is preferably saved at that time and subsequent accesses to that credit review are of a display-only variety. Preferably, only users with sufficient authority to approve or reject a credit review are given the ability to take such actions from page 2100.

[0083] If the user provides final approval, it is preferred that the customer's credit profile be updated in accordance with the approved credit review (e.g., updating the customer's credit limit to a new value). Furthermore, upon approval, it is preferred that the system automatically perform a credit check against the updated credit profile for any outstanding quotes or orders for that customer that have a status of “pending approval”, “pending pre-approval” or the like. Additional details about the system in connection with FIGS. 21-22 are described in Exhibit H appended hereto.

[0084] As discussed above, each customer is preferably assigned to one or more users who may be called upon to review the customer's credit profile. Each user who has the ability to take action on a credit review (as opposed to users whose access is limited to a read-only view of the GUIs or limited to credit review initiation) preferably has an associated assigned credit approval level that is stored by the system. This assigned credit approval level preferably identifies either or both of a maximum number of lease vehicles for a customer's fleet that the user can approve and a maximum amount of risk for a given customer that the user can approve. By storing such approval limits for each user, the fleet management company can maintain control over the system users, preferably by assigning greater approval powers to more experienced fleet managers and lesser approval powers to less experienced fleet managers or to sales personnel. In turn, customer credit profile reviews can be assigned to different fleet managers based on the level of approval commensurate with the customer's credit needs. That is, a credit profile review for a customer having a fleet of 25 vehicles and a credit limit of $500,000 would preferably be assigned to a user who has sufficient authority to take action on a fleet or credit limit of that size, rather than being assigned to a user who only has sufficient authority to take approval action for fleets of less than 15 vehicles or $300,000. Software can be readily configured within the system, preferably within either or both the security framework system 110 or application server 102 to automatically assign and route customer credit reviews to users based on the users' assigned approval limits such that the credit profiles assigned to each user for review is of a scope that is commensurate with that user's credit approval limit. In turn, upon logging onto the system, the user can be presented with a page that lists credit reviews that have been assigned to him/her.

[0085] It is also worth noting that in many cases, the customer for whom the credit profile exists is a business entity having many subsidiaries and related companies that also maintain a fleet of leased vehicles. In such cases, that business entity can be referred to as a master customer, and the master customer's credit profile will preferably control credit decisions for all of the master customer's subsidiaries and related companies, each of which can be referred to as a subcustomer. As such, when assembling a credit profile or performing a credit review, this customer hierarchy will be taken into account by treating all of the subcustomer data as if it were master customer data. Thus, the master customer's credit profile preferably includes all of the financial information and vehicle information for the subcustomers within the master customer's hierarchy. Subcustomers preferably will not have an associated credit profile.

[0086] However, this need not be the case. In an alternative embodiment, each subcustomer (including any business unit of the master customer that is classified as a profit center) can have its own associated credit profile. This in turn, would provide users of the inventive system with the ability to make separate credit decisions for each subcustomer.

[0087] While the present invention has been described above in relation to its preferred embodiment, various modifications may be made thereto that fall within the invention's scope, as would be recognized by those of ordinary skill in the art. Such modifications to the invention will be recognizable upon review of the teachings herein by those of ordinary skill in the art. As such, the full scope of the present invention is to be defined solely by the appended claims and their legal equivalents.

Exhibit A

[0088] Customer Module

[0089] Functional Requirements Specification

[0090] Credit Profile

I. Functional Requirements Specification Introduction

II. Screen Print(s)

[0091] A. Credit Conditions

[0092] B. Credit Hold—List

[0093] C. Credit Hold—Create

[0094] D. Credit Hold—Release

[0095] E. Order Hold—List

[0096] F. Order Hold—Create/Release

III. Detail Tables

[0097] A. Field Mapping Tables

• • [0098] 1. Credit Conditions
  • [0099] 2. Credit Hold—List
  • [0100] 3. Credit Hold—Create
  • [0101] 4. Credit Hold—Release
  • [0102] 5. Order Hold—List
  • [0103] 6. Order Hold—Create/Release

[0104] B. Business Validation/System Generated Notes

• • [0105] 1. Credit Conditions
  • [0106] 2. Credit Hold—Create
  • [0107] 3. Credit Hold—Release
  • [0108] 4. Order Hold—Create/Release

[0109] C. Page Actions

• • [0110] 1. Credit Conditions
  • [0111] 2. Credit Hold—List
  • [0112] 3. Credit Hold—Create
  • [0113] 4. Credit Hold—Release
  • [0114] 5. Order Hold—List
  • [0115] 6. Order Hold—Create/Release
    Screen Action Specification
    I. Functional Requirements Specification Introduction

[0116] Credit profile is applicable to Company Customers only and will be comprised of a five-tab screen. The Credit Conditions tab will allow the user to input critical credit parameters. The Credit Review tab will allow the user to input credit review information. The Credit Hold tab will allow the user to put a customer on credit hold and also release the existing credit holds for the customer. The Order Hold tab allows the user to put a customer on order hold or release a customer from order hold. The Comments tab allows the user to enter additional information for the customer. Only the Credit Conditions tab will initially be enabled for new customers. The other tabs will become available once the initial Credit Conditions are saved.

[0117] Comments are also a part of Credit Profile. See the screen action spec Common—Comments.doc for the details regarding comments.

II. Screen Print(s)

[0118] A. Credit Conditions—see FIG. 24

[0119] B. Credit Hold—List—see FIG. 25

[0120] C. Credit Hold—Create—see FIG. 26

[0121] D. Credit Hold—Release—see FIG. 27

[0122] E. Order Hold—List—see FIG. 28

[0123] F. Order Hold—Create/Release—see FIG. 29

III. Detail Tables

[0124] A. Field Mapping Tables

[0125] 1. Credit Conditions

[0126]

		Control
Field Name	Required	Type	Format	Specific Rules	Data Source Details
Ralph current		Read			CustomerEntity.currentFleetRbv
RBV (excludes		Only
AR/Rent Due)
Current Fleet		Read			CustomerEntity.currentFleetSize
Size		Only
Credit Rating	Required	Drop			CustomerEntity.creditProfile.creditRating
		Down
Req. Deposit		Text Entry	Standard		CustomerEntity.creditProfile.required
Amt.			Currency Format		DepositAmount.
Req. Deposit		Text Entry	Standard		CustomerEntity.creditProfile.required
			Percentage		DepositPercentage
			Format
Req. Cap. Cost		Text Entry	Standard		CustomerEntity.creditProfile.required
Red.			Percentage		CapCostReductionPercentage
			Format
Req. Cap. Cost		Text Entry	Standard		CustomerEntity.creditProfile.required
Red. Amt.			Currency Format		CapCostReductionAmount
# Months Rent		Text Entry	Standard		CustomerEntity.creditProfile.months
Required			Numeric Format		RentRequired
Current Month		Read only	Numeric 3,2		CustomerEntity.creditProfile.
Experian Score					currentExperianScore
Highest Experian		Read only	Numeric 3,2		Customer Entity.creditProlile.
Score					highestExperianScore
Lowest Experian		Read only	Numeric 3,2		CustomerEntity.creditProfile.
Score					lowestExperianScore
MTD Average		Read only	Numeric 3,2		CustomerEntity.creditProfile.
Days to Pay					mtdAverageDaysToPay
PTD Average		Read only	Numeric 3,2		CustomerEntity.creditProfile.
Days to Pay					ptdAverageDaystoPay
Letter of Credit		Check			CustomerEntity.creditProfile.letterOf Credit
		Box
Credit Bank		Text Entry	Alpha Numeric	Disabled until	CustomerEntity.creditProfile.letterOf
Name			(50)	Letter of Credit	CreditBankName
				checkbox is
				checked. Does
				not clear if Letter
				of Credit is
				unchecked
Direct Debit		Check			CustomerEntity.creditProfile.directDebit
		Box
LT&T Billed		Check		Defaults to	CustomerEntity.creditProfile.
		Box		‘selected’.	licenseTaxTitleBilled
Credit Limit	Required	Text Entry	Numeric 8,0		CustomerEntity.creditProfile.credit Limit
Vehicle Limit	Required	Text Entry	Standard		CustomerEntity.creditProfile.vehicles Limit
			Numeric Format
Amt. Per Vehicle	Required	Text Entry	Numeric 6,0		CustomerEntity.creditProfile.amount
Limit					PerVehicleLimit
Max AME per	Required	Text Entry	Numeric 5,0		CustomerEntity.creditProfile.maximum
Veh.					AmePerVehicle
Max Maint. Mgmt.		Text Entry	Standard		CustomerEntity.creditProtile.maximum
Amt.			Currency Format		MaintenanceManagementAmount
Max Risk Mgmt.		Text Entry	Standard		CustomerEntity.creditProfile.maximumRisk
Amt.			Currency Format		ManagementAmount
Apply Floor		Check			CustomerEntity.creditProtile.interest
		Box			RateFloor
Floor value		Text Entry	Standard	Enabled only	CustomerEntity.creditProfile.interest
			Percentage	when Apply Floor	RateFloorPercentage
			Format	is checked.
				Defaults to the
				group rate
				default if it exists,
				otherwise
				defaults to the
				corporate rate
				default rate.
12 month (Min		Text Entry	Standard	Defaults to	CustomerEntity.depreciationTermLimits.
Deprec.)			Percentage	2.50%	minimumDepreciationPercentage
			Format
24 month (Min.		Text Entry	Standard	Defaults to	CustomerEntity.depreciationTermLimits.
Deprec.)			Percentage	2.00%	minimumDepreciationPercentage
			Format
36 month (Min.		Text Entry	Standard	Defaults to	CustomerEntity.depreciationTermLimits.
Deprec.)			Percentage	1.75%	minimumDepreciation Percentage
			Format
48 month (Min.		Text Entry	Standard	Defaults to	CustomerEntity.depreciationTermLimits.
Deprec.)			Percentage	1.50%	minimumDepreciationPercentage
			Format
60 month (Min.		Text Entry	Standard	Defaults to	CustomerEntity.depreciationTermLimits.
Deprec.)			Percentage	0.00%	minimumDepreciationPercentage
			Format

[0127] 2. Credit Hold—List

[0128]

Field Name	Required	Control Type	Format	Specific Rules	Data Source Details
Status		Read		Link is available	CustomerCreditHoldEntity.isOnHold
		Only/Link		for items with a
				status of Hold.
Date (Hold)		Read Only		Contains hold	CustomerCreditHoldEntity.holdDate
				date.
Date (Release)		Read Only		Contains release	CustomerCreditHoldEntity.releaseDate
				date.
Entered By (Hold)		Read Only		Contains Entered	CustomerCreditHoldEntity.heldBy
				By for hold.
Entered By		Read Only		Contains Entered	CustomerCreditHoldEntity.releasedBy
(Release)				By for release.
Reason (Hold)		Read Only		Contains Reason	CustomerCreditHoldEntity.holdReason
				for hold.
Reason (Release)		Read Only		Contains Reason	CustomerCreditHoldEntity.releaseReason
				for release.

[0129] 3. Credit Hold—Create

[0130]

Field Name	Required	Control Type	Format	Specific Rules	Data Source Details
Action		Read Only		Defaults to Hold.	CustomerCreditHoldEntity.isOnHold
Date		Read Only		Defaults to the	CustomerCreditHoldEntity.holdDate
				current date
Entered By		Read Only		Defaults to the	CustomerCreditHoldEntity.heldBy
				current user.
Reason	Required	Text Entry	Alpha Numeric (254)		CustomerCreditHoldEntity.holdReason

[0131] 4. Credit Hold—Release

[0132]

Field Name	Required	Control Type	Format	Specific Rules	Data Source Details
Action		Read Only		Defaults to	CustomerCreditHoldEntity.isOnHold
				Release
Hold Date		Read Only			CustomerCreditHoldEntity.holdDate
Held By		Read Only			CustomerCreditHoldEntity.heldBy
Hold Reason		Read Only			CustomerCreditHoldEntity.holdReason
Release Date		Read Only		Defaults to the	CustomerCreditHoldEntity.releaseDate
				current date.
Released By		Read Only		Defaults to the	CustomerCreditHoldEntity.releasedBy
				current user.
Release Reason	Required	Text Entry	Alpha Numeric (254)		CustomerCreditHoldEntity.releaseReason

[0133] 5. Order Hold—List

[0134]

		Control		Specific	Data Source
Field Name	Required	Type	Format	Rules	Details
Action		Read Only		Contains
				Current
				action
Date		Read Only		Contains
				date the
				action was
				completed
Entered By		Read Only		Contains
				user who
				performed
				the action
Reason		Read Only		Contains
				reason the
				action was
				performed

[0135] 6. Order Hold—Create/Release

[0136]

Field Name	Required	Control Type	Format	Specific Rules	Data Source Details
Action		Read Only		If status is hold,	CustomerCreditHoldEntity.isOnHold.
				default to	(if onHold = true, status is
				Release. If	Hold else status is release
				status is
				released,
				default to Hold.
Date		Read Only		Defaults to the	CustomerOrderHoldEntity.holdReleaseDate
				current date.
Entered By		Read Only		Defaults to the	CustomerCreditHoldEntity.enteredBy
				current user.
Reason	Required	Text Entry	Alpha Numeric (254)		CustomerCreditHoldEntity.holdReleaseReason

[0137] B. Business Validation/System Generated Notes

[0138] 1. Credit Conditions

[0139]

Save
Validation	Msg Type	Property Key
Credit Rating is required.	Error
Credit limit is required.	Error
Vehicle Limit is required.	Error
Amt. per Vehicle is required.	Error
Max AME per Veh. is	Error
required.
Unauthorized to save a credit	Error
profile at this Credit Rating.
Unauthorized to save a credit	Error
profile at this Credit Limit
Amount.
Unauthorized to save a credit	Error
profile at this Vehicle Limit.
Unauthorized to save a credit	Error
profile at this Amt. per Vehicle
Limit.
Unauthorized to save a credit	Error
profile at this Max AME per
Veh.
Req. Deposit Amt. must be	Error
greater than or equal to zero.
Req. Deposit Percentage	Error
must be greater than or equal
to zero and less than 100.
Req. Cap Cost Red.	Error
Percentage must be greater
than or equal to zero and
less than 100.
Req. Cap Cost Red. Amt.	Error
must be greater than or
equal to zero.
Months Rent Required must	Error
be greater than or equal
to zero up to the lease
term value.
Lease Term Minimum	Error
Depreciation values
must be greater than
or equal to zero and
less than 100.
EFT/Direct Deposit is required	Warning/Error
for this Customer Warning on
Credit conditions when Direct
Debit is checked and the
EFT/Direct Debit information
is not filled in on the Billing
Options page. Error if
attempting to activate a unit
AND the Direct Debit is
checked AND the Bank name
is not entered on the Billing
Options page.

[0140] 2. Credit Hold—Create

[0141]

Save
Validation	Msg Type	Property Key
Reason is required.	Error

[0142] 3. Credit Hold—Release

[0143]

Save
Validation	Msg Type	Property Key
Reason is required.	Error

[0144] 4. Order Hold—Create/Release

[0145]

Save
Validation	Msg Type	Property Key
Reason is required.	Error

[0146] C. Page Actions

[0147] 1. Credit Conditions

[0148]

			Actions/Data
Description	Action Type	Action-Specific Rules	Source
Save	Button	Refreshes and redisplays
		Credit Conditions page.
Credit Hold	Link	Goes to the Credit Hold page.
Order Hold	Link	Goes to the Order Hold page.
Comments	Link	Goes to the Comments page.

[0149] 2. Credit Hold—List

[0150]

	Action	Action-Specific
Description	Type	Rules	Actions/Data Source
Create	Button	Goes to the Credit Hold -
		Create page.
Hold (list item)	Link	Goes to the Credit Hold -
		Release page for the
		particular item.

[0151] 3. Credit Hold—Create

[0152]

			Actions/Data
Description	Action Type	Action-Specific Rules	Source
Save	Button	Performs Save action, then
		redisplays the Credit Hold
		List.
Cancel	Button	Redisplays the Credit Hold
		List without saving.

[0153] 4. Credit Hold—Release

[0154]

			Actions/Data
Description	Action Type	Action-Specific Rules	Source
Save	Button	Performs Save action, then
		redisplays the Credit Hold
		List.
Cancel	Button	Redisplays the Credit Hold
		List without saving.

[0155] 5. Order Hold—List

[0156]

Description	Action Type	Action-Specific Rules	Actions/Data Source
Create	Button	Goes to the Order
		Hold/ Release page.

[0157] 6. Order Hold—Create/Release

[0158]

			Actions/Data
Description	Action Type	Action-Specific Rules	Source
Save	Button	Performs Save action, then re-
		displays the Order Hold List.
Cancel	Button	Redisplays the Order Hold
		List without saving.

[0159] Customer Module

[0160] Use Case Specification

[0161] Maintain Credit Profile

I. Create/Update a Credit Profile

[0162] A. Brief Description

II. Flow of Events

[0163] A. Basic Flow—Update a Credit Profile

[0164] B. Alternate Flow—Credit Conditions

[0165] C. Alternate Flows—Credit Hold

[0166] D. Alternate Flows—Order Hold

[0167] E. Alternate Flows—Comments

[0168] F. Alternative Flows—Other

III. Special Requirements

[0169] A. Updates to Credit Conditions Tab come from the Credit Review Process

IV. Pre-Conditions

V. Post-Conditions

VI. BR—Credit Profile

[0170] A. General Credit Profile Business Rules

[0171] B. Credit Condition to Tab Business Rules

[0172] C. Credit Hold Tab Business Rules

[0173] D. Order Hold Business Rules

I. Create/Update a Credit Profile

[0174] A. Brief Description

• • [0175] The credit profile identifies information on the customer's credit rating and provides a way to identify critical credit profile parameters. It also the user to hold and release a customer from credit hold, hold and release a customer from order hold, and provides an area for comments. The function of creating and updating the credit profile are very similar with the main difference being that the credit check is performed with the update.
  • [0176] As of the EAM 3.4 release, the Customer Financial Summary has been removed from Credit Profile and exists as its own function.
  • [0177] As of the EAM 3.5 release, the Credit Review process has removed from Credit Profile and exists as its own function.
    II. Flow of Events

[0178] Creating a Credit Profile

• • [0179] When creating a new credit profile (this can only be done once), only the Credit Conditions information will be available; all tabs will be disabled. The user will be required to tab through all of the required fields populating them with the appropriate values. Once the user has populated all required fields, the user can save the record. Once the save is successfully performed, the window will return to an update mode with the newly added record displayed and all previously disabled tabs will be enabled. See the Business Rules section for the details of the default values.

[0180] Updating a Credit Profile

• • [0181] Once a customer credit profile record has been created, the user will be allowed to edit the record. The user will be able to change any of the fields associated with the credit profile, depending on their Credit Approval Level.

[0182] A. Basic Flow—Update a Credit Profile

• • [0183] Beginning with EAM 3.5, the only way to change Credit Profile Values is to generate and gain Final Approval for a Credit Review.
  • [0184] The exception to this is that EDGE Master Role (Security Role only assigned to Group 77 (corporate) users) may still directly update Credit Profile.
  • [0185] 1. The use case begins when the user selects a customer number:
    a) The user may enter a customer number
    b) The user may select a customer from the list of customers assigned to him/her
    c) The user may search for a customer.
  • [0186] 2. The user then selects to work with the Credit Profile
    a) If the customer number is a sub-customer, the system displays a read only version of the Master's credit profile.
    b) The system provides an indicator showing that this is the master's credit profile.
    c) The available tabs are: Credit Conditions, Credit Hold, Order Hold, and Comments.
    d) The system defaults to the Credit Conditions tab.
    e) If the credit profile is being created, the system loads the default values.
    f) If the credit profile already exists, the system loads the saved values.
  • [0187] 3. The user chooses the Credit Profile area to update or review (See the Alternate Flows):
    a) Credit Conditions
    b) Credit Hold Activities
    c) Order Hold Activities
    d) Comments Activities
  • [0188] 4. When the user has completed the desired actions, the use case ends.

[0189] B. Alternate Flow—Credit Conditions:

• • [0190] This tab defines critical credit parameters for the customer.
    1. The “Ralph Current Fleet RBV” and “Current Fleet Size” are shown as read only.
    2. Conditions Information:
  • [0191] a) The user must select a credit rating, 1, 2, or 3, for the customer.
    • [0192] (1) Credit rating 1 is the highest (best) rating and 3 is the lowest (worst) rating.
  • [0193] b) If the customer will be required to post a security deposit based on a dollar amount on each lease, the user may enter that amount for “Required Deposit Amount”.
    • [0194] (1) If the Required Deposit Amount is entered, the Required Deposit % is not allowed.
  • [0195] c) If the customer will be required to post a security deposit based on a percentage of each lease, the user may enter that percentage for “Required Deposit %”.
    • [0196] (1) If the Required Deposit % is entered, the Required Deposit Amount is not allowed.
  • [0197] d) If the customer will be required to meet a minimum capital price reduction amount for each lease, the user may enter that amount for “Required Capital Price Reduction Amount”.
    • [0198] (1) If Required Capital Price Reduction Amount is entered, Required Capital Price Reduction % is not allowed.
  • [0199] e) If the customer will be required to meet a minimum capital Price reduction percentage for each lease, the user may enter that percentage for “Required Capital Price Reduction %”.
    • [0200] (1) If Required Capital Price Reduction % is entered, Required Capital Price Reduction Amount is not allowed.
  • [0201] f) If the customer is required to post a certain number of months rent at lease inception, the user enters the Number of Months Rent Required.
  • [0202] g) The system displays Experian Scores
    • [0203] (indicates relative financial health of a company)
    • [0204] (1) Current Month Experian Score
    • [0205] (2) Highest Experian Score (Best)
    • [0206] (3) Lowest Experian Score (Worst)
  • [0207] h) The system displays the Average Days to Pay for the Customer
    • [0208] (1) Month-to-Date Average Days to Pay
    • [0209] (2) Period-to-Date Average Days to Pay
  • [0210] i) If a letter of credit from a financial institution exists, the user checks the letter of credit checkbox
    • [0211] (1) When the Letter of Credit checkbox is checked, the user may enter the Credit Bank Name.
  • [0212] j) If the customer will be required to provide Electronic Funds Transfer (EFT), the user checks the Direct Debit checkbox
    • [0213] (1) The system displays a message letting the user know that the bank information is required on the Billing Options screen.
      • [0214] (a) See Billing Options and Billing Addresses Use Cases for the detailed Business Rules associated with Autopay.
  • [0215] k) The user selects whether or not the LT&T costs are billed.
    • [0216] (1) This value is defaulted to bill LT&T upon entry.
  • [0217] l) The user selects whether or not Equity Rollover is Required
    3. Credit Limits Information:
  • [0218] a) The user must enter the Credit Limit Amount.
  • [0219] b) The user must enter the maximum allowed number of Vehicles (Vehicle Limit).
  • [0220] c) The user must enter the maximum vehicle cost value (Amount per Vehicle Limit).
  • [0221] d) The user must enter the maximum value allowable for Aftermarket Equipment (AME) (Maximum AME Amount per Vehicle).
  • [0222] e) The user may enter the Maximum Maintenance Management Amount.
  • [0223] f) The user may enter the Maximum Risk Management Amount.
    4. Interest Rate Options:
  • [0224] a) The user selects whether or not an interest rate floor applies for this customer.
    • [0225] (1) If the interest rate floor does apply, the system allows the floor percentage to be updated
    • [0226] (2) If the interest rate floor does NOT apply the user may not modify the floor interest rate percentage.
      5. Lease Term Information:
  • [0227] a) The user may modify the defaulted values for the 12, 24, 36, 48, and 60-month minimum depreciation values.
    6. The user attempts to save the data by selecting the ‘Save’ button.
  • [0228] a) The system validates that the user's credit approval level is greater than zero.
    • [0229] (1) If the user's approval level is set to zero, the system displays a messages telling the user the data could not be saved due to the credit approval level.
  • [0230] b) The system validates that the following values are within the user's credit limit:
    • [0231] (a) Credit Limit Amount
    • [0232] (b) Vehicle Limit
    • [0233] (c) Amount per Vehicle Limit
    • [0234] (d) Maximum AME Amount per Vehicle
  • [0235] c) If the user's credit approval level is less than the customer's limits, the system displays a messages telling the user the data could not be saved due to the credit approval level.
  • [0236] d) If the values are within the user's credit approval levels, the system saves the data.
    • [0237] (1) This is a Phase II customer item. If the save is an update to a previous value for the following items, the system creates a comment that states what was changed, the “from” and “to” values, who changed the value, and the time and date that the value was modified.
      • [0238] (a) Credit Rating
      • [0239] (b) Required deposit amount
      • [0240] (c) Required deposit %
      • [0241] (d) Required cap Price reduction amount
      • [0242] (e) Required cap Price reduction %
      • [0243] (f) # months rent required
      • [0244] (g) Credit limit amount
      • [0245] (h) Vehicle limit
      • [0246] (i) Amount per vehicle limit
      • [0247] (j) Max AME per vehicle
      • [0248] (k) Max maintenance management amount per vehicle
      • [0249] (l) Max risk management amount per vehicle
      • [0250] (m) Apply floor flag
      • [0251] (n) Floor percentage value
      • [0252] (o) Minimum deprecation % and corresponding lease term
        7. The use case ends

[0253] C. Alternate Flows—Credit Hold

• • [0254] This tab allows users to add a customer to Credit Hold and/or release a customer from Credit Hold. Security measures will be implemented to restrict access to the Release function.
    1. Display Credit Holds
  • [0255] a) The system displays all existing Credit Holds for the customer
  • [0256] b) Status—Values
    • [0257] (1) “Hold” indicates that there is an active Credit Hold for this customer
      • [0258] (a) Multiple “Hold” items may be active at any given time
      • [0259] (b) Selecting a “hold” record initiates the release of that Credit Hold
    • [0260] (2) “Release” indicates that a Credit Hold is no longer active for this customer.
      • [0261] (a) Once released, a Credit Hold cannot be reactivated; a new Credit Hold must be created.
  • [0262] c) Date—Values
    • [0263] (1) The Hold Date indicates when the Credit Hold was initiated.
    • [0264] (2) The Release Date indicates when the Credit Hold was cleared.
      • [0265] (a) If the Credit Hold is active, no information is displayed for Release Date
  • [0266] d) Entered By—Values
    • [0267] (1) The Held by indicates the user who initiated the Credit Hold
    • [0268] (2) The Release Entered By indicates the user who cleared the Credit Hold
      • [0269] (a) If the Credit Hold is active, no information is displayed for Release Entered By
  • [0270] e) Reason—Values
    • [0271] (1) The Hold Reason indicates why the Credit Hold was initiated
    • [0272] (2) The Release Reason indicates why the Credit Hold was released
      • [0273] (a) If the Credit Hold is active, no information is displayed for Release Reason
  • [0274] f) The user reviews the information and the use case ends.
    2. Credit Hold—Create
  • [0275] a) The user selects to Create a new credit hold for the current customer
  • [0276] b) The system verifies that the user is allowed to create a Credit Hold
    • [0277] (1) If the user is not authorized to create a Credit Hold, the system displays a message and the use case ends.
  • [0278] c) The system provides some information which can not be changed:
    • [0279] (1) Action=“Hold”
    • [0280] (2) Hold Date=Current System Timestamp
    • [0281] (3) Held By=Current System User
  • [0282] d) The user must enter a reason for the Credit Hold being initiated.
  • [0283] e) The user selects to save the data.
    • [0284] (1) If the user selects to Cancel the Credit Hold Create before selecting Save, the system does not save the data and the Credit Hold list is redisplayed.
  • [0285] f) The system validates that there has been some data added to the Credit Hold Reason
    • [0286] (1) If no data is entered in the Credit Hold Reason, a message is displayed and the data is not saved
  • [0287] g) The system saves the Credit Hold Information and redisplays the list of all Credit Holds for this customer.
  • [0288] h) The use case ends.
    3. Credit Hold Update (Release)
  • [0289] a) The user selects the active Credit Hold that is to be released.
  • [0290] b) The system provides some information which can not be changed:
    • [0291] (1) Action=Release
    • [0292] (2) Hold Date=The date of the original Credit Hold
    • [0293] (3) Held By=The user that entered the original Credit Hold
    • [0294] (4) Hold Reason=The original Hold Reason for this Credit Hold
    • [0295] (5) Release Date=The current System Date
    • [0296] (6) Released By=The current system user.
  • [0297] c) The user must enter a Credit Hold Release Reason
  • [0298] d) The user selects to save the data.
    • [0299] (1) If the reason is not specified, the system will display a message telling the user that the reason is required and the data will not be saved.
    • [0300] (2) If the user does NOT want to release this Credit Hold, they select to Cancel and the system redisplays the Credit Hold List.
  • [0301] e) The system validates that the user's credit approval level is greater than zero.
    • [0302] (1) If the user's approval level is set to zero, the system displays a messages telling the user the data could not be saved due to the credit approval level.
      • [0303] (a) The system validates that the following values are within the user's credit limit:
        • [0304] (i) credit dollar amount
        • [0305] (ii) maximum vehicle count
        • [0306] (iii) vehicle cost
        • [0307] (iv) AME
    • [0308] (2) If the user's credit approval level is less than the customer's limits, the system displays a messages telling the user the data could not be saved due to the credit approval level.
    • [0309] (3) If the values are within the user's credit approval levels, the system saves the data.
  • [0310] f) The system updates the Release information and moves the released Credit Hold to the released holds section.
  • [0311] g) The system saves the data
    • [0312] (1) Clears the released section
    • [0313] (2) Displays the status as Release
    • [0314] (3) Displays the Hold Date & Release Date
    • [0315] (4) Displays the Held by & Hold Release By
    • [0316] (5) Displays the Hold Reason & Release Reason
  • [0317] h) When the final hold record is released, the customer Credit Hold status overlay is removed and the Customer status displays the current customer status (Pending, Active, or Incomplete).
  • [0318] i) The use case ends.

[0319] D. Alternate Flows—Order Hold

• • [0320] This tab allows users to assign or release a customer from Order Hold.
    1. Order Hold Display
  • [0321] a) The system displays the history of Order Holds for this customer
    • [0322] (1) These values can not be changed on this page.
    • [0323] (2) The list is sorted in descending Hold Date/Release Date.
    • [0324] (3) Action—Hold or Release
    • [0325] (4) Date—Date Order Hold was initiated or Date Order Hold was Released
    • [0326] (5) Entered By—Order Held by or Order Hold Release Entered By
    • [0327] (6) Reason—Reason Held or Reason Released
  • [0328] b) The user reviews the data and the use case ends.
    2. Review Hold—A modified version of Order Hold
• [0329] a) Create Review Hold
  • [0330] (1) Review hold is created when a process, outside of EDGE, runs based on the rules defined below. The process will:
    • [0331] (a) Only update customers who are not already on Order Hold or Review Hold.
    • [0332] (b) Only customers that are active will be considered for Order Hold.
    • [0333] (c) Compare each customer's latest approved credit review date to the current date
      • [0334] (i) If the difference is greater than the number of months defined as the credit review hold limit, the system creates an Order Hold for the customer and all its sub customers.
      • [0335] (ii) For an order hold created by the system, the following information will display for the order hold
        • [0336] (a) Action—Hold
        • [0337] (b) Date—date the system put the customer on order hold
        • [0338] (c) Entered by—System
        • [0339] (d) Reason—Customer's credit has not been reviewed/approved in X months.
        • [0340]  (i) Where X is the number of months since the customer's last approved credit review.
• [0341] b) The system overlays the customer status with Review Hold for the Master and all the sub customers.
  • [0342] (1) A customer can only be removed from Review Hold by the completion and final approval of the Credit Review.
• [0343] c) The use case ends
  3. Order Hold—Create
  • [0344] a) The user selects to create an Order Hold for the customer
    • [0345] (1) If the customer is already on Order Hold the system generates a Release transaction See the Order Hold—Release section below.
  • [0346] b) The system displays the following which can not be changed
    • [0347] (1) Action=Hold
    • [0348] (2) Date=Current system timestamp
    • [0349] (3) Entered By=Current system user
  • [0350] c) The user must enter a Reason explaining why the Order Hold is being initiated
  • [0351] d) The user selects to saves the data.
    • [0352] (1) If the user does not input an Order Hold Reason, the system will display a message stating that the Reason is required and the updates are not saved.
    • [0353] (2) If the user does not want to initiate the Order Hold, they may select to Cancel and the system will NOT save the updates.
  • [0354] e) The system displays the new data in the Order Hold Display
  • [0355] f) The system overlays the customer status with Order Hold
  • [0356] g) The use case ends
    4. Order Hold—Release
  • [0357] a) The user selects to Release the customer from Order Hold
    • [0358] (1) If the customer is not currently on Order Hold, the system generates a Hold transaction. See the Order—Hold section above.
    • [0359] (2) If the customer is on Review Hold (modified version of Order Hold), the user cannot Release the Order Hold.
  • [0360] b) The system displays the following which can not be changed:
    • [0361] (1) Action=Release
    • [0362] (2) Date=Current system timestamp
    • [0363] (3) Entered By=Current system user
  • [0364] c) The user must enter an Order Hold Release Reason
  • [0365] d) The user selects to save the data
    • [0366] (1) If the user does not input an Order Hold Release Reason, the system will display a message stating that the Reason is required and the updates are not saved.
    • [0367] (2) If the user does not want to Release the Order Hold, they may select to Cancel and the system will NOT save the updates.
  • [0368] e) The system validates that the user's credit approval level is greater than zero.
    • [0369] (1) If the user's approval level is set to zero, the system displays a messages telling the user the data could not be saved due to the credit approval level.
  • [0370] f) The system validates that the following values are within the user's credit limit:
    • [0371] (a) credit dollar amount
    • [0372] (b) maximum vehicle count
    • [0373] (c) vehicle cost
    • [0374] (d) AME
    • [0375] (2) If the user's credit approval level is less than the customer's limits, the system displays a messages telling the user the data could not be saved due to the credit approval level.
    • [0376] (3) If the values are within the user's credit approval levels, the system saves the data.
  • [0377] g) The system removes the Order Hold overlay
  • [0378] h) The system displays the Order Hold Display with the Release entry included.
  • [0379] i) The use case ends

[0380] E. Alternate Flows—Comments

• • [0381] Allows users to enter general comments or additional information about the customer.
    1. Comments Display:
  • [0382] a) The system displays the following for all comments previously entered for a customer, which can not be changed.
    • [0383] (1) Comments—Text information logged by the user regarding the customer
    • [0384] (2) Entered By—The person that entered the Comments
    • [0385] (3) Date Entered—The system timestamp from the entry of the comment
    • [0386] (4) Comments are displayed in ascending order by Date Entered
  • [0387] b) The user reviews the comments and the use case ends.
    2. Comments Create
  • [0388] a) The user selects to Create a comment for the customer.
  • [0389] b) See the Common functions for details.
  • [0390] c) The Use Case Ends

[0391] F. Alternative Flows—Other

1. Moving between tabs or leaving the screen for all tabs

• • [0392] a) If the user attempts to change tabs or leave the screen and the data is not saved, the system will display a response message requesting the user to save the data.
    • [0393] (1) A ‘Yes’ reply performs validations and saves the updates if the validations pass
    • [0394] (2) A ‘No’ reply will discard all updates.
  • [0395] b) The Use Case Ends
    2. Perform the credit checks on outstanding quotes with updates on the Credit Conditions tab
  • [0396] a) If the credit dollar amount, vehicle count, vehicle cost, or AME limits on the credit conditions tab are updated, the system will perform the credit check on all Pending Approval or Pending Re-approval quotes for the customer.
    • [0397] (1) If the quote passes the credit check, the system will approve the quote.
    • [0398] (2) If the quote does not pass the credit check, the system will not change the quote status.
  • [0399] b) The Use Case Ends
    III. Special Requirements

[0400] A. Updates to Credit Conditions Tab Come from the Credit Review Process

1. Beginning with EAM 3.5, the only way to change Credit Profile Values is to generate and gain Final Approval for a Credit Review.

• • [0401] a) The exception to this is that Corporate users (Gp 77) can update Credit Profile with proper security clearance via the EDGE Master role.
    IV. Pre-Conditions
    1. The user must be logged on to EDGE and have appropriate security access to create and update a credit profile.
    V. Post-Conditions
    1 The customer credit profile is established/updated with the appropriate information.

VI. BR—Credit Profile

• • [0402] The following business rules apply to creating and updating the customer credit profile.

[0403] A. General Credit Profile Business Rules

• • [0404] Beginning with EAM 3.5, the only way to change Credit Profile Values is to generate and gain Final Approval for a Credit Review.
    1. The credit profile is only applicable for fleet and commercial customers.
    2. The credit profile does not apply to individual or employee customer types.
    3. The system will validate that the credit profile values for credit dollar limit, number of vehicles, vehicle amount limit, and maximum AME limit are within the user's credit approval level established in master data, user security.
    4. The credit profile values are only editable for customers in the user's group.
    5. For customers outside the user's group, the credit profile values will be read only except for corporate users who have full access to customers in all groups pending proper security setup.
    6. The credit profile for fleet customers is only applicable for master customers. Sub-customers do not have their own credit profile.

[0405] B. Credit Condition Tab Business Rules

1. Defaults:

• • [0406] a) All values should default to NULL/Unchecked if no previous value has been entered except:
    • [0407] (a) Minimum Depreciation values which will default as follows:
      • [0408] For NEW customers that have NO Credit Profile established, the Depreciation Rates come from the Default Rates for the Group.
      • [0409] (i) If the Group has no default rates, then use the Corporate (Group 77) Default Rates.
    • [0410] (2) Floor Value %—At create, this will default from the Corporate/Group Rate Default.
      • [0411] (a) Once the user checks “Apply Floor”, the value entered at the time of the save will be saved to the database and redisplayed from there; even if the “Apply Floor” is Unchecked later.
      • [0412] (b) If the user does not check “Apply Floor” during the initial create, the value for Floor Value % will continue to default from the Corporate/Group Rate Default. The value has no meaning unless the “Apply Floor” is also checked.
        2. A note stating, “excludes AR/Rent Due,” must be displayed under the current RALPH fleet RBV.
        3. Credit rating is required. Valid values are 1, 2, and 3.
        4. A user must have a credit approval authority of 35 or more units to assign a credit rating of 1.
        5. The Credit Bank Name is not enabled until the Letter of Credit checkbox is checked.
        6. Required deposit amount is a numeric, currency field containing two decimal places and allowing numbers greater than or equal to zero.
        7. Required deposit percent is a numeric field containing two decimal places and allowing numbers greater than or equal to zero and less than 100.
        8. Required cap Price reduction percent is a numeric field containing two decimal places and allowing numbers greater than or equal to zero and less than 100.
        9. Required cap Price reduction amount is a numeric, currency field containing two decimal places and allowing numbers greater than or equal to zero.
        10. The number of month rent is an integer value allowing numbers greater than or equal to zero up to the lease term value and representing the number of months rent to be collected up-front.
        11. Credit Limit dollar amount is a numeric currency field allowing numbers greater than or equal to zero and representing the total dollar amount of outstanding credit allowed for this customer. Credit Limit dollar amount is required.
        12. The Vehicle Limit is an integer value allowing numbers greater than zero and representing the total number of Enterprise owned leased vehicles allowed for the customer. Vehicle Limit is required.
        13. The Amount per Vehicle limit is a numeric currency value containing two decimal places and allowing numbers greater than or equal to zero and representing the maximum single vehicle value allowed for the customer.
        14. The Maximum AME amount per vehicle is a numeric currency value containing two decimal places and allowing numbers greater than or equal to zero and representing the maximum total capitalized AME allowed on a single vehicle for the customer.
        15. The Maximum maintenance management amount is a numeric currency value containing two decimal places and allowing numbers greater than or equal to zero and representing the total maximum outstanding maintenance management amount allowed for the customer.
        16. The Maximum risk management amount is a numeric currency value containing two decimal places and allowing numbers greater than or equal to zero and representing the total maximum outstanding risk management amount allowed for the customer.
        17. The Bill LT&T indicator defaults to selected.
        18. The floor indicator will allow the user to select Apply Floor
  • [0413] a) The floor indicator will default to selected.
    19. The floor interest rate will only display if the Apply Floor is selected.
  • [0414] a) The floor interest value defaults to the group rate default, if available and to the corporate rate default is no group rate default is defined.
    20. The Minimum depreciation is a numeric value containing two decimal places and allowing numbers greater than or equal to zero but less than 100. This value represents the minimum depreciation by term allowed for any lease for the customer.
    21. Phase II item—A comment will be written to include the name of the value that was changed, the from and to values, the user who made the change, and the date/time of the change when any of the credit condition values, except the letter of credit information

[0415] C. Credit Hold Tab Business Rules

1. Upon entering the tab, the following rules apply:

• • [0416] a) The Credit Hold list is non-editable.
  • [0417] b) The Credit Hold list will contain:
    • [0418] (1) Credit Hold creation timestamp—a value that contains the date and time the customer was placed on Credit Hold status.
    • [0419] (2) Credit Hold Release timestamp—a value that contains the date and time the customer was released from Credit Hold status.
    • [0420] (3) Credit Hold Reason—an alphanumeric value containing the reason the customer was placed on hold with a maximum character length of 255.
    • [0421] (4) Credit Hold Release Reason—an alphanumeric value containing the reason the customer was released from Credit Hold with a maximum character length of 255.
    • [0422] (5) Credit Held by (name of the user who added the Credit Hold record)—an alphanumeric value containing a concatenation of the user's last name, first name, and middle initial
    • [0423] (6) Credit Hold Release Entered By (name of the user who released the Credit Hold record)—an alphanumeric value containing a concatenation of the user's last name, first name, and middle initial
  • [0424] c) The Release information will be blank until a hold record is released.
  • [0425] d) Multiple Credit Holds may be active at any one time.
  • [0426] e) The History list is populated with any prior hold notices that have been released. These items will be listed in descending order by date released.
    2. The user can create a Credit Hold for Fleet Master customers and Commercial customers only.
    3. A Credit Hold can be created regardless of the status of the Out-Of-Sync flag.
    4. Placing the Fleet Master customer on Credit Hold, restricts the entire customer hierarchy from any further sales activity until the Credit Hold has been released.
    5. The system will NOT allow a sub customer (and/or its branches) to be placed on Credit Hold independently.
    6. Credit Hold records can NOT be deleted. They must be released if they are not accurate.

[0427] D. Order Hold Business Rules

1. When a Master customer is put on Order Hold, the entire hierarchy is put on Order Hold.

2. A sub customer cannot be put on Order Hold independently of the master customer.

3. When a customer is on Order Hold, mandatory credit approval is required even if the quote passes the credit checks.

4. With proper management approval on a quote, a customer on order hold can obtain new vehicles. The customer does not need to be released from order hold to have vehicles ordered and delivered.

5. Quote creation is allowed when a customer in on Order Hold.

6. Entered By is a system-filled, read-only text field containing the creating user's last name, first name, and middle initial.

7. The Reason field is a required alphanumeric value. Additions are allowed, but deletes and updates are not allowed.

8. Date is a system-filled read-only date field.

9. Order Hold Display is a system-filled read-only text field listing the Action, Date, the user who put the customer on Order Hold or released the customer from Order Hold, and the Comments associated with the transaction.

10. When a customer is put on Order Hold, the customer status will show Order Hold. Order hold overrides all customer statuses (Pending, Active, or Incomplete).

• • [0428] a) If a customer is also on Credit Hold, the customer status will show Credit Hold because credit hold overrides all statuses.
    11. When a customer is released from Order Hold, the customer status will display the actual customer status (Pending, Active, or Incomplete) unless the customer is on credit hold at which point Credit Hold will overlay the normal status.
    12. If a save is performed and the required fields are not filled in, the system will provide a message requesting the user to fill the required fields.
    Exhibit B

[0429] Customer

[0430] Functional Requirements Specification

[0431] Maintain Financial Summary

I. Functional Requirements Specification Introduction

II. Screen Print(s)

[0432] A. Financial Summary List (top)

[0433] B. Financial Summary List (middle)

[0434] C. Financial Summary List (bottom)

[0435] D. Financial Summary Create (top)

[0436] E. Financial Summary Create (middle)

[0437] F. Financial Summary Create (bottom)

[0438] G. Financial Summary Update (top)

[0439] H. Financial Summary Update (middle)

[0440] I. Financial Summary Update (bottom)

III. Detail Tables

[0441] A. Field Mapping Tables

• • [0442] 1. Financial Summary List
  • [0443] 2. Financial Summary Create
  • [0444] 3. Financial Summary Update

[0445] B. Business Validation/System Generated Notes

• • [0446] 1. Financial Summary Create
  • [0447] 2. Financial Summary Update

[0448] C. Page Actions

• • [0449] 1. Financial Summary List
  • [0450] 2. Financial Summary Create
  • [0451] 3. Financial Summary Update
    IV. Exceptions from Standards
    Screen Action Specification

[0452] I. Functional Requirements Specification Introduction

• • [0453] The user may Create/Update/Delete Financial Summary records for a customer. The 5 most recent financial summary records will be displayed on the list screen. The user may create new financial summary records, update or delete any of the 5 most recent records that are shown on the screen. All values are entered and displayed in thousands (i.e. If 10,000 is the actual number, 10 is entered and displayed).

[0454] II. Screen Print(s)

• • [0455] A. Financial Summary List (top)—see FIG. 30
  • [0456] B. Financial Summary List (middle)—see FIG. 31
  • [0457] C. Financial Summary List (bottom)—See FIG. 32
  • [0458] D. Financial Summary Create (top)—see FIG. 33
  • [0459] E. Financial Summary Create (middle)—see FIG. 34
  • [0460] F. Financial Summary Create (bottom)—see FIG. 35
  • [0461] G. Financial Summary Update (top)—see FIG. 36
  • [0462] H. Financial Summary Update (middle)—see FIG. 37
  • [0463] I. Financial Summary Update (bottom)—see FIG. 38

[0464] III. Detail Tables

[0465] A. Field Mapping Tables

• • [0466] 1. Financial Summary List

[0467]

Field Name	Required	Control Type	Format	Specific Rules	Data Source Details
Currency Type		Read Only	Text
AE		Read Only	Text		Customer.salespeople.ae.fullname
AM		Read Only	Text		Customer.salespeople.am.fullname
Financial		Read Only	Text		financialSummary.type.description
Statement Type
Period		Link	Standard Date		financialSummary.period
Balance Sheet - Assets
Cash & ST		Read Only	Numeric (11, 0)	Displays	financialSummary.cash.AndStInvestments
Investments				parenthesis for
(amt)				negative amounts.
				Displays - (dash) if
				empty.
Cash & ST		Read Only	Percentage (3, 0)		financialSummary.cashAndStInvestmentsPercent
Investments (%)
Accounts		Read Only	Numeric (11, 0)	Displays	financialSummary.accountsReceivable
Receivable -				parenthesis for	LessTrade
Trade (amt)				negative amounts.
				Displays - (dash) if
				empty.
Accounts		Read Only	Percentage (3, 0)		financialSummary.accountsReceivable
Receivable -				LeseTradePercent
Trade (%)
Inventory (amt)		Read Only	Numeric (11, 0)	Displays	financialSummary.inventory
			parenthesis for
				negative amounts.
				Displays - (dash) if
				empty.
Inventory (%)		Read Only	Percentage (3, 0)		financialSummary.InventoryPercent
Total Current		Read Only	Numeric (11, 0)	Displays	financialSummary.totalCurrentAssets
Assets (amt)				parenthesis for
				negative amounts.
				Displays - (dash) if
				empty.
Total Current		Read Only	Percentage (3, 0)		financialSummary.totalCurrentAssetsPercent
Assets (%)
Net Fixed Assets		Read Only	Numeric (11, 0)	Displays	financialSummary.netFixedAssets
(amt)				parenthesis for
				negative amounts.
				Displays - (dash) if
				empty.
Net Fixed Assets		Read Only	Percentage (3, 0)		financialSummary.netFixedAssetsPercent
(%)
Intangibles (amt)		Read Only	Numeric (11, 0)	Displays	financialSummary.Intangibles
				parenthesis for
				negative amounts.
				Displays - (dash) if
				empty.
Intangibles (%)		Read Only	Percentage (3, 0)		financialSummary.IntangiblesPercent
Total Assets		Read Only	Numeric (11, 0)	Displays	financialSummary.totalAssets
(amt)				parenthesis for
				negative amounts.
				Displays - (dash) if
				empty.
Total Assets (%)		Read Only	Percentage (3, 0)		Constant = 100%
Balance Sheet - Liabilities & Equity
Accounts Payable -		Read Only	Numeric (11, 0)	Displays	financialSummary.accountsPayableLessTrade
Trade (amt)				parenthesis for
				negative amounts.
				Displays - (dash) if
				empty.
Accounts Payable -		Read Only	Percentage (3, 0)		financialSummary.accountsPayableLessTradePercent
Trade (%)
Current Maturities		Read Only	Numeric (11, 0)	Displays	financialSummary.currentMaturities
(amt)				parenthesis for
				negative amounts.
				Displays - (dash) if
				empty.
Current Maturities		Read Only	Percentage (3, 0)		financialSummary.currentMaturitiesPercent
(%)
Total Current		Read Only	Numeric (11, 0)	Displays	financialSummary.totalCurrentLiabilities
Liabilities (amt)				parenthesis for
				negative amounts.
				Displays - (dash) if
				empty.
Total Current		Read Only	Percentage (3, 0)		financialSummary.totalCurrentLiabilities
Liabilities (%)				Percent
Long-term Debt		Read Only	Numeric (11, 0)	Displays	financialSummary.longTermDebt
(amt)				parenthesis for
				negative amounts.
				Displays - (dash) if
				empty.
Long-term Debt		Read Only	Percentage (3, 0)		financialSummary.longTermDebtPercent
(%)
Total Liabilities		Read Only	Numeric (11, 0)	Displays	financtalSummary.totalLiabilities
(amt)				parenthesis for
				negative amounts.
				Displays - (dash) if
				empty.
Total Liabilities		Read Only	Percentage (3, 0)		financialSummary.totalLiabilitiesPercent
(%)
Preferred Stock		Read Only	Numeric (11, 0)	Displays	financialSummary.preferredStock
(amt)				parenthesis for
				negative amounts.
				Displays - (dash) if
				empty.
Preferred Stock		Read Only	Percentage (3, 0)		financialSummary.preferredStockPercent
(%)
Retained Earnings		Read Only	Numeric (11, 0)	Displays	financialSummary.retainedEarnings
Earnings (amt)				parenthesis for
				negative amounts.
				Displays - (dash) if
				empty.
Retained		Read Only	Percentage (3, 0)		financialSummary.retainedEarningsPercent
Earnings (%)
Total Equity		Read Only	Numeric (11, 0)	Displays	financialSummary.totalEquity
(amt)				parenthesis for
				negative amounts.
				Displays - (dash) if
				empty.
Total Equity (%)		Read Only	Percentage (3, 0)		financialSummary.totalEquityPercent
Total Liabilities &		Read Only	Numeric (11, 0)	Displays	financialSummary.totalLiabilitiesAndEquity
Equity (amt)				parenthesis for
				negative amounts.
				Displays - (dash) if
				empty.
Total Liabilities &		Read Only	Percentage (3, 0)		Constant = 100%
Equity (%)
Net Equity (amt)		Read Only	Numeric (11, 0)	Displays	financialSummary.netEquity
				parenthesis for
				negative amounts.
				Displays (dash) if
				empty.
Operations
Net Sales (amt)		Read Only	Numeric (11, 0)	Displays	financialSummary.netSales
				parenthesis for
				negative amounts.
				Displays - (dash) if
				empty.
Net Sales (%)		Read Only	Percentage (3, 0)		Constant = 100%
Gross Margin		Read Only	Numeric (11, 0)	Displays	financialSummary.grossMargin
(amt)				parenthesis for
				negative amounts.
				Displays - (dash) if
				empty.
Gross Margin		Read Only	Percentage (3, 0)		financialSummary.grossMarginPercent
(%)
Interest Expense		Read Only	Numeric (11, 0)	Displays	financialSummary.InterestExpense
(amt)				parenthesis for
				negative amounts.
				Displays - (dash) if
				empty.
Interest Expense		Read Only	Percentage (3, 0)		financialSummary.interestExpensePercent
(%)
Income Before	*p1034X	Read Only	Numeric (11, 0)	Displays	financialSummary.IncomeBeforeTaxes
Taxes (amt)				parenthesis for
				negative amounts.
				Displays - (dash) if
				empty.
(%)		Read Only	Percentage (3, 0)		financialSummary.incomeBeforeTaxes
					Percent
Net Income (amt)		Read Only	Numeric (11, 0)	Displays	financialSummary.netincome
				parenthesis for
				negative amounts.
				Displays - (dash) if
				empty.
Net Income (%)		Read Only	Percentage (3, 0)		financialSummary.netincomePercent
Cash Flow/Burn
Depreciation &		Read Only	Numeric (11, 0)	Displays	financialSummary.depreciationAndAmortization
Amortization				parenthesis for
				negative amounts.
				Displays - (dash) if
				empty.
Cash Flow		Read Only	Numeric (11, 0)	Displays	financialSummary.cashFlow
				parenthesis for
				negative amounts.
				Displays - (dash) if
				empty.
Capital		Read Only	Numeric (11, 0)	Displays	financialSummary.capitalExpenditures
Expenditures				parenthesis for
				negative amounts.
				Displays - (dash) if
				empty.
Proceeds From		Read Only	Numeric (11, 0)	Displays	financialSummary.proceedsFromSaleOfCapitalEquipment
Sale of Captl				parenthesis for
Equip				negative amounts.
				Displays - (dash) if
				empty.
Cash Burn		Read Only	Numeric (11, 0)	Displays	financialSummary.cashBurn
				parenthesis for
				negative amounts.
				Displays - (dash) if
				empty.
Ratio Analysis
Working Capital		Read Only	Numeric (11, 0)	Displays	financialSummary.workingCaptal
(amt)				parenthesis for
				negative amounts.
				Displays - (dash) if
				empty.
Working Capital		Image		Displays green up	financialSummary.workingCapitalTrend
(ind)				arrow if current >
				previous.
				displays red down
				arrow if current <
				previous.
Current Ratio		Read Only	Numeric (11, 0)	Displays	financialSummary.currentRatio
(amt)				parenthesis for
				negative amounts.
				Displays - (dash) if
				empty.
Current Ratio		Image		Displays green up	financialSummary.currentRatioTrend
(ind)				arrow if current >
				previous.
				displays red down
				arrow if current <
				previous.
Quick Ratio		Read Only	Numeric (11, 0)	Displays	financialSummary.quickRatio
(amt)				parenthesis tor
				negative amounts.
				Displays - (dash) if
				empty.
Quick Ratio (ind)		Image		Displays green up	financialSummary.quickRatioTrend
				arrow if current >
				previous.
				displays red down
				arrow if current <
				previous.
AR Turnover		Read Only	Numeric (11, 0)	Displays	financialSummary.arTurnover
(Days) (amt)				parenthesis for
				negative amounts.
				Displays - (dash) if
				empty.
AR Turnover		Image		Displays green up	financialSummary.arTurnoverTrend
(Days) (ind)				arrow if current <
				previous.
				Displays red down
				arrow if current >
				previous.
Inventory Turnover		Read Only	Numeric (11, 0)	Displays	financialSummary.inventoryTurnover
(Days) (amt)				parenthesis for
				negative amounts.
				Displays - (dash) if
				empty.
Inventory Turnover		Image		Displays green up	financialSummary.inventoryTurnoverTrend
(Days) (ind)				arrow if current <
				previous.
				Displays red down
				arrow if current >
				previous.
Total Debt/Equity		Read Only	Numeric (11, 0)	Displays	financialSummary.totalDebtEquity
(amt)				parenthesis for
				negative amounts.
				Displays - (dash) if
				empty.
Total Debt/Equity		Image		Displays green up	financialSummary.totalDebtEquityTrend
(ind)				arrow if current <
				previous.
				Displays red down
				arrow if current >
				previous.
Long-term		Read Only	Numeric (11, 0)	Displays	financialSummary.longTermDebtEquity
Debt/Equity				parenthesis for
(amt)				negative amounts.
				Displays - (dash) if
				empty.
Long-term		Image		Displays green up	financialSummary.longTermDebtEquity
Debt/Equity (ind)				arrow if current <	Trend
				previous.
				Displays red down
				arrow if current >
				previous.
EBIT/Interest			Numeric (11, 0)	Displays	financialSummary.ebitInterestExpense
Expense (amt)				parenthesis for
				negative amounts.
				Displays - (dash) if
				empty.
EBIT/Interest				Displays green up	financialSummary.ebitInterestExpense
Expense (ind)				arrow if current >	Trend
				previous.
				displays red down
				arrow if current <
				previous.

• • [0468] 2. Financial Summary Create

[0469]

		Control
Field Name	Required	Type	Format	Specific Rules	Data Source Details
Currency Type		Read
		Only
Financial	Yes	Drop		Defaults to blank	financialSummary.type.description
Statement Type		Down
Period	Yes	Text Entry/	Standard Date		financialSummary.period
		Calendar
		Selector
Balance Sheet -
Assets
Cash & ST		Text Entry	Numeric (11,0)		financialSummary.cashAndStInvestments
Investments
(amt)
Accounts		Text Entry	Numeric (11,0)		financialSummary.accountsReceivable
Receivable -					LessTrade
Trade (amt)
Inventory (amt)		Text Entry	Numeric (11,0)		financialSummary.inventory
Total Current		Text Entry	Numeric (11,0)		financialSummary.totalCurrent Assets
Assets (amt)
Net Fixed Assets		Text Entry	Numeric (11,0)		financialSummary.netFixedAssets
(amt)
Intangibles (amt)		Text Entry	Numeric (11,0)		financialSummary.intangibles
Total Assets		Text Entry	Numeric (11,0)		financialSummary.totalAssets
(amt)
Balance Sheet -
Liabilities &
Equity
Accounts		Text Entry	Numeric (11.0)		financialSummary.accountsPayableLessTrade
Payable - Trade
(amt)
Current		Text Entry	Numeric (11,0)		financialSummary.currentMaturities
Maturities (amt)
Total Current		Text Entry	Numeric (11,0)		financialSummary.totalCurrentLiabilities
Liabilities (amt)
Long-term Debt		Text Entry	Numeric (11,0)		financialSummary.longTermDebt
(amt)
Total Liabilities		Text Entry	Numeric (11,0)		financialSummary.totalLiabilities
(amt)
Preferred Stock		Text Entry	Numeric (11,0)		financialSummary.preferredStock
(amt)
Retained		Text Entry	Numeric (11,0)		financialSummary.retainedEarnings
Earnings (amt)
Total Equity		Text Entry	Numeric (11,0)		financialSummary.totalEquity
(amt)
Total Liabilities &		Read	Numeric (11,0)		financialSummary.totalLiabilitiesAndEquity
Equity (amt)		Only
Net Equity (amt)		Read	Numeric (11,0)		financialSummary.netEquity
		Only
Operations
Net Sales (amt)		Text Entry	Numeric (11,0)		financialSummary.netSales
Gross Margin		Text Entry	Numeric (11,0)		financialSummary.grossMargin
(amt)
Interest Expense		Text Entry	Numeric (11,0)		financialSummary.interest Expense
(amt)
Income Before		Text Entry	Numeric (11,0)		financialSummary.incomeBeforeTaxes
Taxes (amt)
Net Income (amt)		Text Entry	Numeric (11,0)		financialSummary.netIncome
Cash Flow/
Burn
Depreciation &		Text Entry	Numeric (11,0)		financialSummary.depreciationAndAmortization
Amortization
Cash Flow		Read	Numeric (11,0)		financialSummary.cashFlow
		Only
Capital		Text Entry	Numeric (11,0)		financialSummary.capitalExpenditures
Expenditures
Proceeds From		Text Entry	Numeric (11,0)		financialSummary.proceedsFromSaleOf
Sale of Captl					CapitalEquipment
Equip
Cash Burn		Read	Numeric (11,0)		financialSummary.cashBurn
		Only

• • [0470] 3. Financial Summary Update

[0471]

		Control
Field Name	Required	Type	Format	Specific Rules	Data Source Details
Currency Type		Read
		Only
Financial		Drop			financialSummary.type.description
Statement Type		Down
Period		Read			financialSummary.period
		Only
Balance Sheet -
Assets
Cash & ST		Text Entry	Numeric (11,0)		financialSummary.cashAndStInvestments
Investments
(amt)
Accounts		Text Entry	Numeric (11,0)		financialSummary.accountsReceivable
Receivable -					LessTrade
Trade (amt)
Inventory (amt)		Text Entry	Numeric (11,0)		financialSummary.inventory
Total Current		Text Entry	Numeric (11,0)		financialSummary.totalCurrent Assets
Assets (amt)
Net Fixed Assets		Text Entry	Numeric (11,0)		financialSummary.netFixed Assets
(amt)
Intangibles (amt)		Text Entry	Numeric (11,0)		financialSummary.intangibles
Total Assets		Text Entry	Numeric (11,0)		financialSummary.totalAssets
(amt)
Balance Sheet -
Liabilities &
Equity
Accounts		Text Entry	Numeric (11,0)		financiatSummary.accountsPayableLessTrade
Payable - Trade
(amt)
Current		Text Entry	Numeric (11,0)		financialSummary.currentMaturities
Maturities (amt)
Total Current		Text Entry	Numeric (11,0)		financialSummary.totatCurrentLiabilities
Liabilities (amt)
Long-term Debt		Text Entry	Numeric (11,0)		financialSummary.longTermDebt
(amt)
Total Liabilities		Text Entry	Numeric (11,0)		financialSummary.totalLiabilities
(amt)
Preferred Stock		Text Entry	Numeric (11,0)		financialSummary.preferredStock
(amt)
Retained		Text Entry	Numeric (11,0)		financialSummary.retainedEarnings
Earnings (amt)
Total Equity		Text Entry	Numeric (11,0)		financialSummary.totalEquity
(amt)
Total Liabilities &		Read	Numeric (11,0)		financialSummary.totalLiabilitiesAndEquity
Equity (amt)		Only
Net Equity (amt)		Read	Numeric (11,0)		financialSummary.netEquity
		Only
Operations
Net Sales (amt)		Text Entry	Numeric (11,0)		financialSummary.netSales
Gross Margin		Text Entry	Numeric (11,0)		financialSummary.grossMargin
(amt)
Interest Expense		Text Entry	Numeric (11,0)		financialSummary.interestExpense
(amt)
Income Before		Text Entry	Numeric (11,0)		financialSummary.incomeBeforeTaxes
Taxes (amt)
Net Income (amt)		Text Entry	Numeric (11,0)		financialSummary.netIncome
Cash Flow/
Burn
Depreciation &		Text Entry	Numeric (11,0)		financialSummary.depreciationAndAmortization
Amortization
Cash Flow		Read	Numeric (11,0)		financialSummary.cashFlow
		Only
Capital		Text Entry	Numeric (11,0)		financialSummary.capitalExpenditures
Expenditures
Proceeds From		Text Entry	Numeric (11,0)		financialSummary.proceedsFromSaleOf
Sale of Captl					Capital Equipment
Equip
Cash Burn		Read	Numeric (11,0)		financialSummary.cashBurn
		Only

[0472] B. Business Validation/System Generated Notes

• • [0473] 1. Financial Summary Create

[0474]

Save
Validation	Msg Type	Property Key
Duplicate Record Exists for this period.	Error
Date should be current system date or	Error
earlier
Financial Summary Period is required.	Error
Financial Statement Type is required.	Error
Invalid Amount.	Error
Invalid Date.	Error

• • [0475] 2. Financial Summary Update

[0476]

Save
Validation	Msg Type	Property Key
Financial Statement Type is required.	Error
Invalid Amount.	Error

[0477] C. Page Actions

[0478] 1. Financial Summary List

[0479]

		Action-
Des-	Action	Specific
cription	Type	Rules	Actions/Data Source
Create	Button		System displays Financial Summary Create
			page and a popup to remind the user to enter
			the amounts in thousands, not whole dollars.

[0480] 2. Financial Summary Create

[0481]

	Action
Description	Type	Action-Specific Rules	Actions/Data Source
Clear	Button		Confirmation message is displayed. If response
			is ok, entries are cleared. If response is cancel,
			entries are not cleared. Screen remains on the
			create page.
Save	Button	Validations are done.	Displays confirmation popup asking if the user
			entered the amounts in thousands, not whole dollars.
			If yes, performs validation, saves the Financial
			Summary Entry, computes calculated fields and
			redisplays the Financial Summary Update Page
			with the updated calculations.
			If no, remains on the Financial Summary
			Create Page.
Cancel	Button		System displays Financial Summary List page.

[0482] 3. Financial Summary Update

[0483]

	Action
Description	Type	Action-Specific Rules	Actions/Data Source
Clear	Button		Confirmation message is displayed. If response
			is ok, entries are cleared. If response is cancel,
			entries are not cleared. Screen remains on the update page.
Save	Button	Validations are done.	Displays confirmation pop up asking if the user
			entered the amounts in thousands, not whole dollars.
			If yes, performs validation, saves the Financial
			Summary, computes calculated fields and
			redisplays the Financial Summary Update Page
			with the updated calculations.
			If no, remains on the Financial Summary Update Page.
Delete	Button		System displays a delete confirmation message
			“Are you sure you want to delete this Financial
			Summary Record?”
			If Yes, the Financial Summary will be deleted
			and the system displays the Financial Summary
			List page.
			If No, the system will stay on the Financial
			Summary Update page.
Back	Button		System displays a warning if there is unsaved
			data. If clicks ok, then the system displays the
			Financial Summary List page.

[0484] IV. Exceptions from Standards

1. Numeric values are in thousands instead of whole dollars (i.e. 10,000 is displayed and entered as 10).

2. Percentages are shown as whole percentage with no decimal places (i.e. 100%).

3. Negative amounts are entered with ‘−’ symbol (i.e. “−1234”), but displayed on the list page with parenthesis (i.e. “(1234)”).

[0485] 4. Trend indicators are not generically “up” or “down” which would be the same direction for all indicators. Instead the trend indicators are “good” or “bad”, therefore the direction of the arrow is dependent on which item you are looking at as well as the direction of the trend. (i.e. A number that has increased from the last period may be represented by an “up” arrow for working capital, however an increase in debt equity would be represented by a “down” arrow).

[0486] Customer Module

[0487] Use Case Specification

[0488] Maintain Financial Summary Information

I. Customer—Maintain Financial Summary Information

[0489] A. Brief Description

II. Flow of Events—Maintain Financial Summary

[0490] B. Basic Flow—Create A New Period of Financial Information

III. Alternate Flows

[0491] A. Alternate Flow—Review/Update Financial Information For Selected Period

[0492] B. Alternate flow—Delete A Single Financial Summary Period

[0493] C. Alternate flow—Clear A Financial Summary Period

[0494] D. Alternate Flow—View Customer's Financial Summary Comparison

IV. Special Requirements

V. Pre-Conditions

VI. Post-Conditions

VII. Business Rules Definitions

[0495] A. Financial Summary Information

[0496] B. Access Authority

[0497] C. Customer Financial Summary Comparison

[0498] D. Negative Values

[0499] E. Financial Summary Reference Information

[0500] F. Calculations

[0501] I. Customer—Maintain Financial Summary Information

[0502] A. Brief Description

• • [0503] The Financial Information is entered for each Master Customer (Fleet and Commercial) to provide insight into the financial condition and credit decisions that are being made for both new customers and extensions to credit for existing customers.
  • [0504] This information will provide the business (over time) the ability to make better, more informed decisions, as well as provide a common interface to financial information and reporting to management. All dollar amounts are entered in thousands.

[0505] II. Flow of Events—Maintain Financial Summary

[0506] A. Basic Flow—Create A New Period of Financial Information

1. The user selects to view the Customer's Financial Summary Comparison.

• • [0507] a) The user must have proper authority to view or update this information.
  • [0508] b) For Fleet or Commercial customers, the user may view or modify the Master customer Financial information. For Sub-customers, the information will be read-only and not available for update.
    2. The system displays the following customer information for reference (as the header);
  • [0509] a) Customer ID
  • [0510] b) Customer Name
  • [0511] c) Group/Br (Peoplesoft Dept ID)
  • [0512] d) Customer Status
  • [0513] e) Customer Type
    3. The system displays the existing Customer's Financial Summary Comparison. (Refer to Alternate Flow—Display Customer Financial Summary Comparison).
  • [0514] a) See Business rules section for calculated values.
    Create Financial Period.
    4. The user selects to create a new period of financial information.
  • [0515] (1) The system provides a reminder to the user to ensure that all values are entered in thousands, not in whole dollars.
  • [0516] (2) The user selects to continue.
    5. The system displays the following information for reference:
  • [0517] a) A message stating, “Please ensure that all values are entered in thousands, NOT IN WHOLE DOLLARS.”
  • [0518] b) Currency Code: (USD or CAN) based on customer's address country code.
    6. The user must select the Financial Period ending date (month, day, year).
    7. The user must select the Financial Statement type. Valid values are:
  • [0519] a) Audited
  • [0520] b) Reviewed
  • [0521] c) Compiled
  • [0522] d) Internal
  • [0523] e) Tax Returns
    8. The user enters the Balance Sheet—Assets values:
  • [0524] a) The system provides a way to indicate to the user that Debits are entered as positive values and Credits as negative values DR/(CR).
    • [0525] (1) Cash & ST Investments
    • [0526] (2) Accounts Receivable—Trade
    • [0527] (3) Inventory
    • [0528] (4) Total Current Assets
    • [0529] (5) Net Fixed Assets
    • [0530] (6) Intangibles
    • [0531] (7) Total Assets
      9. The user enters the Balance Sheet—Liabilities & Equity values:
  • [0532] a) The system provides a way to indicate to the user that Debits are entered as negative values and Credits as positive values (DR)/CR.
    • [0533] (1) Accounts Payable—Trade
    • [0534] (2) Current Maturities
    • [0535] (3) Total Current Liabilities
    • [0536] (4) Long-term Debt
    • [0537] (5) Total Liabilities
    • [0538] (6) Preferred Stock
    • [0539] (7) Retained Earnings
    • [0540] (8) Total Equity
      10. The user enters the Operations values:
  • [0541] a) The system provides a way to indicate to the user that Debits are entered as negative values and Credits as positive values (DR)/CR.
    • [0542] (1) Net Sales
    • [0543] (2) Gross Margin
    • [0544] (3) Interest Expense
    • [0545] (4) Income Before Taxes
    • [0546] (5) Net Income
      11. The user enters the following Cash Flow/Burn values:
  • [0547] a) The user can only enter positive values for the Cash Flow/Burn section.
    • [0548] (1) Depreciation and Amortization
    • [0549] (2) Capital Expenditures
    • [0550] (3) Proceeds from Sale of Captl. Equip.
      12. The user selects to save the data, return to the customer financial summary, or clear values.
  • [0551] a) If the user selects to save:
    • [0552] (1) The system provides a reminder to the user to verify that all values are entered in thousands, not in whole dollars.
      • [0553] (a) The user selects to continue.
        • [0554] (i) The system performs the following data validations:
        • [0555]  (a) If the user has not filled all required fields, the system provides a message and the user must enter the appropriate data.
        • [0556]  (b) If the selected Financial Period ending date already exists in the system, the system provides a message and the user must modify the Financial Period ending date before successfully saving.
        • [0557]  (c) If the Total Assets is not equal to the sum of Total Liabilities and Total Equity, the system provides a message and the data must be corrected before saving successfully.
        • [0558] (ii) The system saves the data.
        • [0559] (iii) The system calculates and redisplays the updated customer's single financial period information.
      • [0560] (b) The user selects to cancel.
        • [0561] (i) The system does not save the data and redisplays the customer's single financial period information as previously modified.
  • [0562] b) If the user selects to return to the customer financial summary, the system returns to the Customer's Financial Summary Comparison and the information is not saved.
  • [0563] c) If the user selects to Clear Values, refer to Alternate Flow—Clear A Financial Summary Period.
    13. After a successful save and redisplay of data, the user can create another period of financial data:
  • [0564] a) The user selects a new Financial Period ending date
  • [0565] b) The user enters new values and successfully saves.
  • [0566] c) Another financial period record is created.
    14. When the user selects to return to the Customer's Financial Summary Comparison, the use case ends.

[0567] III. Alternate Flows

[0568] A. Alternate Flow—Review/Update Financial Information For Selected Period

1. From the Customer's Financial Summary Comparison, the user may select a Financial Period to review or update.

2. The system displays the following information for reference:

• • [0569] a) A message stating, “Please ensure that all values are entered in thousands, NOT IN WHOLE DOLLARS.”
  • [0570] b) Financial Period ending date
  • [0571] c) Currency Code: (USD or CAN) based on customer's address country code.
    3. The system displays the selected Financial Period.
    4. The system displays the selected Financial Summary information.
  • [0572] a) If no changes are required, the user views the data, chooses to return to the customer financial summary and the use case ends
  • [0573] 5. The user may modify any of the values displayed (refer to Create Financial Summary Information for the list of values and rules that apply).
    6. The user cannot modify the Financial Period ending date.
    7. The user may modify any or all Balance Sheet—Assets values:
  • [0574] a) The system provides a way to indicate to the user that Debits are entered as positive values and Credits as negative values DR/(CR).
    8. The user may modify any or all Balance Sheet—Liabilities & Equity values:
  • [0575] a) The system provides a way to indicate to the user that Debits are entered as negative values and Credits as positive values (DR)/CR.
    9. The user may modify any or all Operations values:
  • [0576] a) The system provides a way to indicate to the user that Debits are entered as negative values and Credits as positive values (DR)/CR.
    10. The user may modify any or all Cash Flow/Burn values:
  • [0577] a) The system provides a way to indicate to the user that Debits are entered as negative values and Credits as positive values (DR)/CR.
    11. The user may select to clear all values for the selected period.
  • [0578] a) Refer to Alternate Flow—Clear A Financial Summary Period.
    12. The user may select to delete the selected financial period information.
  • [0579] a) Refer to Alternate Flow—Delete A Single Financial Summary Period.
    13. The user may select to return to the Customer's Financial Summary Comparison.
    14. The user selects to save the modifications.
  • [0580] a) The system provides a reminder to the user to verify that all values are entered in thousands, not in whole dollars.
  • [0581] b) The user selects to continue.
    • [0582] (1) The same validations that apply for creating a financial period of information apply when updating a selected financial period.
    • [0583] (2) The system calculates the Total Liabilities and Equity amount.
    • [0584] (3) The system calculates the Net Equity amount.
    • [0585] (4) The system calculates the Cash Burn amount.
    • [0586] (5) The system calculates and redisplays the updated customer's single financial period information.
  • [0587] c) The user selects to cancel.
    • [0588] (1) The system does not save the data and redisplays the customer's single financial period information as previously modified.
      15. The use case ends.

[0589] B. Alternate Flow—Delete a Single Financial Summary Period

1. When viewing a customer's single financial period information, the user may select delete the period.

2. The system displays a message confirming that the user wants to delete the entire period.

• • [0590] a) If the user chooses to not delete, the system does not delete the information and redisplays the financial period details. The user may then select to go back to the Customer's Financial Summary Comparison.
  • [0591] b) If the user confirms the period deletion, the period is removed from the system and the user is returned to the Customer's Financial Summary Comparison.
    3. The flow ends.

[0592] C. Alternate Flow—Clear a Financial Summary Period

1. When the system displays the customer's single financial period information, the user may select to clear the selected period information.

2. The system displays a message confirming that the user wants to clear the information.

• • [0593] a) If the user chooses to not clear, the system does not clear the information and redisplays the single financial period information. The user may then select to go back to the Customer's Financial Summary Comparison.
  • [0594] b) If the user confirms the to clear the data, all entered and calculated data is cleared and the user is returned to the customer's single financial period for further entry.
    3. The flow ends.

[0595] D. Alternate Flow—View Customer's Financial Summary Comparison

1. The user selects to view the Customer's Financial Summary Comparison Information.

2. The system displays a summary of the five (5) most recent available financial periods for the customer in descending order (most recent to least recent).

3. The system displays the following information for reference:

• • [0596] a) Account Executive Name
  • [0597] b) Account Manager Name
  • [0598] c) Currency Code: (USD or CAN) based on customer's address country code.
  • [0599] d) Financial Statement Type
  • [0600] e) Period (MM-DD-YYYY)
    4. The system displays the Balance Sheet Amount and calculated percentages for each period:
  • [0601] a) The system indicates that amount values are displayed in thousands (000's).
  • [0602] b) For the following items, Credit values that were entered as negatives will be displayed in parenthesis.
    • [0603] (1) Cash & ST Investments
    • [0604] (2) Accounts Receivable—Trade
    • [0605] (3) Inventory
    • [0606] (4) Total Current Assets
    • [0607] (5) Net Fixed Assets
    • [0608] (6) Intangibles
    • [0609] (7) Total Assets
  • [0610] c) For the following items, Debit values that were entered as negatives will be displayed in parenthesis.
    • [0611] (1) Accounts Payable—Trade
    • [0612] (2) Current Maturities
    • [0613] (3) Total Current Liabilities
    • [0614] (4) Long-term Debt
    • [0615] (5) Total Liabilities
    • [0616] (6) Preferred Stock
    • [0617] (7) Retained Earnings
    • [0618] (8) Total Equity
    • [0619] (9) The system calculates the Total Liabilities & Equity amount (Refer to business rules)
    • [0620] (10) The system calculates the Net Equity amount (Refer to Business Rules)
      5. The system displays the Operations amounts and calculated percentages for each period:
  • [0621] a) The system indicates that amount values are displayed in thousands (000's).
  • [0622] b) Debits that were entered as negative values will be displayed in parenthesis. The following values are displayed:
    • [0623] (1) Net Sales amount and percentage
    • [0624] (2) Gross Margin amount and percentage
    • [0625] (3) Interest Expense amount and percentage
    • [0626] (4) Income Before Taxes amount and percentage
    • [0627] (5) Net Income amount and percentage
      6. The system displays the Cash Flow/Burn values:
  • [0628] a) The system indicates that amount values are displayed in thousands (000's).
  • [0629] b) For the following items, Debit values that were entered as negatives will be displayed in parenthesis.
    • [0630] (1) Depreciation and Amortization
    • [0631] (2) The system calculates the Cash Flow amount (Refer to Business Rules)
    • [0632] (3) Capital Expenditures
    • [0633] (4) Proceeds from Sale of Captl. Equip.
    • [0634] (5) The system calculates the Cash Burn amount (Refer to Business Rules)
      7. The system calculates and displays the following Ratio Analysis values for each period (Refer to business rules for calculations).
  • [0635] a) The system indicates if the trend is positive or negative when compared to the previous period's value.
    • [0636] (1) Working capital
    • [0637] (2) Current Ratio
    • [0638] (3) Quick Ratio
    • [0639] (4) AR Turnover (Days)
    • [0640] (5) Inventory Turnover (Days)
    • [0641] (6) Total Debt/Equity
    • [0642] (7) Long Term Debt/Equity
    • [0643] (8) EBIT/Interest Expense

[0644] IV. Special Requirements

• • [0645] N/A

[0646] V. Pre-Conditions

1. The user must be logged on the EDGE and have object security access to maintain Financial Summary Information.

2. With Update access, the user can create, update, delete, and view address information.

• • [0647] a) Corporate users have access to update all group/branches.
  • [0648] b) Group/branch users have access to update all customers within their group, but only view access to other group's customers.
  • [0649] c) With View access, the user can view the existing Customer's Financial Summary Information for any group/branch.
    3. With no access defined, the Financial Summary information tab will not be available within the Customer Credit Profile.

[0650] VI. Post-Conditions

1. The Customer's Financial Summary Information are created, updated, or deleted in EDGE.

[0651] VII. Business Rules Definitions

[0652] A. Financial Summary Information

1. The Financial Summary information is applicable to Master Customers (Fleet and Commercial types).

2. Sub-customers will display the master's information for viewing only.

3. Financial Summary information is not applicable to Individual or Employee type customers.

[0653] B. Access Authority

1. Users will need proper authority to view or update the Customer's Financial Summary Comparison.

[0654] C. Customer Financial Summary Comparison

1. The Customer's Financial Summary Comparison consists of the five (5) most recent periods of financial summary information.

2. The financial periods are displayed from most recent to least recent.

3. If a sixth (6th) financial period is added, the oldest period drops off and is no longer available for viewing. If an intermediate period is deleted, the (previously) 6th period will be redisplayed as the 5th period in the summary.

[0655] D. Negative Values

1. When entering negative values in the individual period creation/editing, the negative sign will be entered.

2. When displaying negative values in the summary, the values are displayed in parenthesis.

[0656] E. Financial Summary Reference Information

1. The Currency Code should default based on the customer's address country code. (i.e. USD or CAN).

2. The Financial Period ending date must be entered on the period details (i.e. Oct. 24, 2004) and must be today's date or earlier.

3. The Financial Statement Type must be entered on the period details. Valid values are:

• • [0657] a) Audited
  • [0658] b) Reviewed
  • [0659] c) Compiled
  • [0660] d) Internal
  • [0661] e) Tax Returns

[0662] F. Calculations

1. The following total amount calculations are applicable to each period:

[0663]

Calculated
values	Amounts	Formula
Balance	Total Liabilities &	Total Liabilities +
Sheet	Equity	Total Equity
	Net Equity	Total Equity −
		Preferred Stock −
		Intangibles
Cash Flow/	Cash Flow	Net Income +
Burn		Depreciation and Amortization
	Cash Burn	Cash Flow −
		Capital Expenditures +
		Proceeds from Sale of Captl. Equip.

2. The following Percentage calculations are applicable to each period:

[0664]

Calculated
Values	Percentages	Formula
Operations	Net Sales %	100%
	Gross Margin %	If Net Sales Amount = 0
		Default to zero
		Otherwise
		Gross Margin Amount/Net Sales
		Amount
	Interest Expense %	If Net Sales Amount = 0
		Default to zero
		Otherwise
		Interest Expense/Net Sales Amount
	Income before	If Net Sales Amount = 0
	Taxes %	Default to zero
		Otherwise
		Income before Taxes/Net Sales
		Amount
	Net Income %	If Net Sales Amount = 0
		Default to zero
		Otherwise
		Net Income/Net Sales Amount
Balance	Cash and ST	If Total Assets = 0
Sheet	Investments %	Default to zero
		Otherwise
		Cash and ST Investments/Total
		Assets
	Accounts Receivable -	If Total Assets = 0
	Trade %	Default to zero
		Otherwise
		Accounts Receivable-Trade/
		Total Assets
	Inventory %	If Total Assets = 0
		Default to zero
		Otherwise
		Inventory/Total Assets
	Total Current	If Total Assets = 0
	Assets %	Default to zero
		Otherwise
		Total Current Assets/Total Assets
	Net Fixed Assets %	If Total Assets = 0
		Default to zero
		Otherwise
		Net Fixed Assets/Total Assets
	Intangibles %	If Total Assets = 0
		Default to zero
		Otherwise
		Intangibles/Total Assets
	Total Assets %	100%
	Accounts Payable -	If Total Liabilities & Equity = 0
	Trade %	Default to zero
		Otherwise
		Accounts Payable-Trade/Total
		Liabilities & Equity
	Current Maturities %	If Total Liabilities & Equity = 0
		Default to zero
		Otherwise
		Current Maturities/Total Liabilities &
		Equity
	Total Current	If Total Liabilities & Equity = 0
	Liabilities %	Default to zero
		Otherwise
		Total Current Liabilities/Total
		Liabilities & Equity
	Long-term Debt %	If Total Liabilities & Equity = 0
		Default to zero
		Otherwise
		Long-Term Debt/Total Liabilities &
		Equity
	Total Liabilities %	If Total Liabilities & Equity = 0
		Default to zero
		Otherwise
		Total Liabilities/Total Liabilities &
		Equity
	Preferred Stock %	If Total Liabilities & Equity = 0
		Default to zero
		Otherwise
		Preferred Stock/Total Liabilities &
		Equity
	Retained Earnings %	If Total Liabilities & Equity = 0
		Default to zero
		Otherwise
		Retained Earnings/Total Liabilities &
		Equity
	Total Equity %	If Total Liabilities & Equity = 0
		Default to zero
		Otherwise
		Total Equity/Total Liabilities &
		Equity
	Total Liabilities &	100%
	Equity

3. The following Ratio Analysis Calculated values are applicable to each period:

[0665]

Amounts	Formula	Indicators
Working Capital	Total Current Assets - Total Current	A positive trend is indicated if the
	Liabilities	Current Period is greater than the
		Previous Period.
		A negative trend is indicated if the
		Current Period is less than the
		Previous Period.
		No trend is indicated if the Current
		Period is equal to the Previous
		Period.
Current Ratio	If Total Current Liabilities = 0	A positive trend is indicated if the
	Default to zero	Current Period is greater than the
	Otherwise	Previous Period.
	Total Current Assets/Total	A negative trend is indicated if the
	Current Liabilities	Current Period is less than the
		Previous Period.
		No trend is indicated if the Current
		Period is equal to the Previous
		Period.
Quick Ratio	If Total Current Liabilities = 0	A positive trend is indicated if the
	Default to zero	Current Period is greater than the
	Otherwise	Previous Period.
	(Total Current Assets −	A negative trend is indicated if the
	Inventory)/Total Current Liabilities	Current Period is less than the
		Previous Period.
		No trend is indicated if the Current
		Period is equal to the Previous
		Period.
AR Turnover	If the Net Sales of Accounts	A positive trend is indicated if the
(Days)	Receivable-Trade Amount = 0	Current Period is less than the
	Default to zero	Previous Period.
	Otherwise	A negative trend is indicated if the
	360/(Net Sales/Accounts	Current Period is greater than the
	Receivable-Trade)	Previous Period.
		No trend is indicated if the Current
		Period is equal to the Previous
		Period.
Inventory	If Net Sales or Inventory Amount =	A positive trend is indicated if the
Turnover (Days)	0	Current Period is less than the
	Default to zero	Previous Period.
	Otherwise	A negative trend is indicated if the
	360/(Net Sales/Inventory)	Current Period is greater than the
		Previous Period.
		No trend is indicated if the Current
		Period is equal to the Previous
		Period.
Total Debt/	If Total Equity = 0	A positive trend is indicated if the
Equity	Default to zero	Current Period is less than the
	Otherwise	Previous Period.
	Total Liabilities/Total Equity	A negative trend is indicated if the
		Current Period is greater than the
		Previous Period.
		No trend is indicated if the Current
		Period is equal to the Previous
		Period.
Long Term Debt/	If Total Equity = 0	A positive trend is indicated if the
Equity	Default to zero	Current Period is less than the
	Otherwise	Previous Period.
	Long Term Debt/Total Equity	A negative trend is indicated if the
		Current Period is greater than the
		Previous Period.
		No trend is indicated if the Current
		Period is equal to the Previous
		Period.
EBIT/Interest	If Interest Expense = 0	A positive trend is indicated if the
Expense	Default to zero	Current Period is greater than the
	Otherwise	Previous Period.
	(Income Before Taxes − Interest	A negative trend is indicated if the
	Expense)/((−1) * Interest Expense)	Current Period is less than the
		Previous Period.
		No trend is indicated if the Current
		Period is equal to the Previous
		Period.

Exhibit C

[0666] Lease Management

[0667] Functional Requirements Specification

[0668] Credit Review and History

I. Functional Requirements Specification Introduction

II. Screen Print(s)

[0669] A. Credit Review History

[0670] B. Create Credit Review History

[0671] C. Update Credit Review History

III. Detail Tables

[0672] A. Field Mapping Tables

• • [0673] 1. Credit Review History List
  • [0674] 2. Create Credit Review History
  • [0675] 3. Update Credit Review History

[0676] B. Business Validation/System Generated Notes

• • [0677] 1. Credit Review History List
  • [0678] 2. Create/Update Credit Review History

[0679] C. Page Actions

• • [0680] 1. Credit Review History List
  • [0681] 2. Create Credit Review History
  • [0682] 3. Update Credit Review History
    Screen Action Specification

[0683] I. Functional Requirements Specification Introduction

• • [0684] This Credit Review History will provide a window into any past Credit Reviews performed on a Customer as well as the Credit Review currently being performed. Since only one Credit Review may be active at once, most of the information will be historical. Upon Final Approval, a snapshot is taken of all data relevant to the Credit Review. This snapshot of the data is what the user will see when they view Historical Credit Review Information.

[0685] II. Screen Print(s)

• • [0686] A. Credit Review History—see FIG. 39
  • [0687] B. Create Credit Review History—see FIG. 40
  • [0688] C. Update Credit Review History—see FIG. 41

[0689] III. Detail Tables

[0690] A. Field Mapping Tables

1. Credit Review History List

[0691]

		Control
Field Name	Required	Type	Format	Specific Rules	Data Source Details
Review Status	Link	Hyperlink	creditReview.reviewStatus.description
Review Created	Read	Standard Date	creditReview.createTimestamp
Date	Only
Review created by	Read	Standard Name	creditReview.createdBy
	Only	Format
Next Review	Read	Standard Date	creditReview.nextReviewDate
	Only
Review Type	Read	Alpha	creditReview.reviewType.description
	Only

2. Create Credit Review History

[0692]

		Control
Field Name	Required	Type	Format	Specific Rules	Data Source Details
Review Created		Read	Standard Date	DateUtil.currentDate
Date		Only
Review created		Read	Standard Name	EmployeeEntity.currentUser
by		Only	Format
Next Credit	Required	Pop up	Standard Date	DateUtils.addYears(DateUtil.currentDate( ),
Review Date		calendar		1)
Credit Review	Required	Drop	Alpha	creditReviewType.findAll
Type		down
Credit Review		Text Area	Alphanumeric	creditReview.reviewNotes
Notes

3. Update Credit Review History

[0693]

		Control
Field Name	Required	Type	Format	Specific Rules	Data Source Details
Review Created		Read	Standard Date	creditReview.reviewCreatedDate
Date		Only
Review created By		Read	Standard Name	creditReview.createdByName
		Only	Format
Next Credit	Required	Pop up	Standard Date	creditReview.nextReviewDate
Review Date		calendar
Credit Review	Required	Drop	Alpha	creditReview.reviewType
Type		down
Credit Review		Text Area	Alphanumeric	creditReview.reviewNotes
Notes

[0694] B. Business Validation/System Generated Notes

[0695] 1. Credit Review History List

[0696]

Create
Validation	Msg Type	Property Key
Only one active Credit Review is allowed for	Error
a customer

[0697] 2. Create/Update Credit Review History

[0698]

Save
Validation	Msg Type	Property Key
Next Credit Review Date can not be a past	Error
date.
Next Credit Review Date is required.	Error
Credit Review Type is required.	Error