The Status Transfer option changes the application status and/or transfers application ownership and responsibility to another user. Since every application has one owner responsible for it, transfer of responsibility and ownership may be appropriate when the application changes statuses, such as when it goes from credit approval to documentation tracking. Applications may be tracked and processed by non-owners as well, as when a credit approval officer or investigator records a follow-up note for their manager to review. Refer to the Notebook for more information on notes.
As with other Application menu options, the user must first select an application using either the Single Application Selection or the Application Work Schedule. If running data entry requirements via status transfer, LeasePak will be able to detect that it has been called by U0801 Status Transfer and not by U0801 Data Entry Requirement. It will pass all fields on from U0801 Status Transfer to the stored procedure, including: application number, current status, new status, current owner, new owner, effective date, effective time, approval expiration date, credit line expiration date, credit approved officer, preliminary credit score, final credit score, transfer unprocessed notes, reasons/conditions.
Application status represents its current stage of processing. For example, applications that have just been entered through the New Application module may have the status ENTR (Entry), while applications that are undergoing credit investigation may have the status INVS (Investigation).
The first character of the application status code defines its major category:
The actual values of these status codes are defined and customized with the Application Status update [U0811].
It is important to note that application statuses do not, by themselves, define who may access the application at a given time. For example, the fact that an application is in the Investigation (Ixxx) phase does not prevent a salesperson from entering additional information, or a documentation clerk from starting work on it. Field level security, previously defined for each user through the Application User Profile update [U0831], restricts the fields a user may modify. Refer to the Application Field Security update [U0814] and the Application User Profile update [U0831] for more information on defining field security for each status.
In addition, data entry requirements are used to define those fields which must be entered before an application's status may be transferred to that level. The purpose is to allow the contents of the application to be "built- up" as the application evolves from the "Entry" status to the "Booked" status. Thus, a status change is only allowed if all minimum entry requirements have been met for the selected status. For more information on entry requirements, refer to Data Entry Requirements.
The owner of the application is the person primarily responsible for the next step in its processing. To transfer ownership, the initial username of the new owner is entered in the NEW OWNER field. An application may be owned by only one user at a time. The ownership of an application can be transferred at any time, not just when the application status is changed. The significance of ownership is:
If a follow-up
date is specified when selecting a work schedule, only those applications
with unprocessed notes on or before the date entered will appear on the work
schedule.
Thus, ownership insures that every application will appear on at least the owner's work schedule, providing tracking of all applications regardless of whether unprocessed notes exist.
Rather than transferring ownership to another user, it may be more appropriate to simply record a follow-up note for another user using the Notebook update (accessed by pressing <F7> or <GOLD-N> F3 or selecting Notebook from the Options menu). Ownership of the application would then remain with the original user, but there would be at least two follow-up notes for the application on the other user's work schedule: one for the original owner and one for the other user. This may be more efficient if the other user is simply to check on something for the application. Upon completing the task indicated, the user would then mark the follow- up note as processed, causing it to no longer appear on the work schedule.
This screen is used to change the status of an application and/or transfer the ownership of an application to another user.
These checks do not apply if the user has the privilege to bypass the rate plan edit checks. Refer to the OVERRIDE RATE PLAN field of the Application User Profile update [U0831] for more information on this bypass privilege. Refer to the Rate Plan update [U0816] for more information on rate plans and the specific fields which must agree.
To transfer an application to booked status, use the Book Lease option of the New Lease update [U0101]. If a user selects "Booked" as NEW STATUS on the Application Status Transfer update, a message appears to this effect.
The following conditions must be met before an application may be booked:
ACQUISITION COST
OTHER CHARGES
RESIDUAL AMOUNT
UPFRONT SALES TAX
All booked assets associated with the application must be off-lease and in the same Portfolio/Company/Region/Office as the application.
For Master Applications, LeasePak will require that any increase in the Master Application credit limit beyond the original credit limit stay within the tolerance and approval credit limit in the user's Application User Profile [U0831].
Note that once an application status is changed to "Booked," it cannot be changed to any other status. To remove a lease that has been booked, use the Remove Lease option [RM] of the New Lease update [U0101].
NEW OWNER may be defaulted with a user previously identified on the Application User Profile update [U0831] when a status is changed or when the current user's credit limit is insufficient. Refer to the Application User Profile update [U0831] for more information on these defaults.
EFFECTIVE DATE and EFFECTIVE TIME are reported in the application history section of the Application Inquiry [R0502]. They may only be changed by users with the privilege to modify the date and time, as established with the Application User Profile update [U0831].
When the status is first changed to "Approved," a default expiration date is calculated by adding the APPROVAL EXPIRATION DAYS from the Application Portfolio update [U0822] to the effective date of the application. Note that calendar days, not business days, are used in this calculation.
Users with proper security may modify this date. Refer to the CHANGE APPROVAL EXPIRATION DATE field of the Application User Profile update [U0831] for information on the security needed to change this date.
If the batch application status has not been defined for the portfolio that the application being booked into, the following message “The batch application status has not been defined for portfolio