Temenos Lifecycle Management Suite - Account Origination Product Guide
Disburse
| End-User Guide > Application Processing > Post-Decision > Approval > Disburse |
The disbursement function allows users to disburse an approved loan application to core and/or third party integration. The disbursement process may be a live process or a nightly batch disbursement process.
This topic includes the following information:
 |
While an application's disbursement is processing, an application is locked and users are prevented from making changes until the disbursement completes.
Refresh or re-open the workspace after the application has been disbursed to enable editing of the application. |
Applications may be disbursed manually by Account Origination module end users or automatically by administrative configurations made with Event Processing.
Account Origination module users with the appropriate permissions are able to able to disburse an application, once an application is approved. Users are able to manually disburse an application from the:
Once an application is in a disbursable state, users may select the Disburse button within the application toolbar.
When the Disburse button is clicked, the Disbursement process initiates.
When a user navigates to the final screen assigned to a Workflow’s Approval category, the Disburse button appears in the screen’s toolbar.
When the Disburse button is clicked, the Disbursement process initiates.
Applications may also be automatically disbursed by Event Processing, based on the following application conditions:
 |
The IsAccountReadyForDisbursement flag is automatically set to true by the system when the following conditions are met in the application:
|
Application Type IsAccountReadyForDisbursement Disburse? Account True Account Account False None
|
If the application is locked by a system user:
|
 |
In the event of validation errors, To-dos or other system errors, the automated disbursement does not complete. The application remains in an Auto Approved or Loan Officer Approved status. Additionally if a user bypasses warnings on the approval, the warnings are also bypassed during the automatic disbursement. |
During the disbursement process, a notification stating "application is being automatically disbursed by the module" is added to the application. Once the application disburses, this notification is removed and queuing rules execute.
Once an application is ready to be disbursed, click 
. The Disbursement Summary pop-up window appears, indicating the disbursement actions that are to occur.
|
Account applications must include at least one account product for disbursement; therefore, if an account application does not include any account products, a Validation error is received upon clicking to inform that at least one account product must be added to disburse the application. |
Click Continue to proceed with the disbursement. Click Cancel to return to the application without disbursing.
After clicking Continue, the Disburse Application pop-up window appears. Select the Accept Terms check box and click Disburse. To return to the application without disbursing, click Cancel.
Upon clicking Disburse, the disbursement process begins. During the disbursement process, the following occurs:
|
If the application does not pass the account Validations or Validation Rules, the disbursement process stops and errors generate. Once the validations are cleared, click . |
After the disbursement process completes, a Success message appears:
|
The success message may indicate the application has been partially disbursed if an account product's funding is not successful.
|
Once an application has been disbursed, the system processes the account product funding records.
|
If multiple account products are being processed, the system disburses and funds the Base Share Account first. Once the base share is processed, the system disburses and funds any remaining account products.
|
Funding records are sent to the core in the order that they appear in the Event/Action pair(s) configured to execute by the system administrator in System Management > Origination > Event Processing. When an account product is disbursed, the configured action executes to create the funding record in the core and/or transmit the funding information to the applicable third party connector.
|
If all funding actions are configured in one Event/Action pair, the funding records are processed in the order that they appear in the configured action. If more than one Event/Action pair is configured, the funding records are processed in the order that the Event/Action pairs were created. Cash and Check funding records are not disbursed to the core since they are processed immediately once the cash and/or check is received at the institution. |
|
If account disbursement or funding is not successful, clicking again initiates the disbursement process for the unsuccessful records. All successful records are skipped and the disbursement process picks up with the first record that is not successful. |
Upon successful account disbursement and funding, the following fields are set in the screen for each account product:
Once all account products on the application have been successfully disbursed and funded, Is Account Disbursed is set to true for the application. When this field is set to true, the overall application is able to disburse and the following fields are set for the application:
When configured to appear in an application, the Disbursement Summary panel provides a table that lists each account product as well as their corresponding funding record(s).
The grid within this panel indicates the following information for both account products and funding records:
| Column | Description | ||
| Status |
|
||
| Date |
|
For an application to be disbursed, it must be in a disbursable state. The following system-defined validations may prevent an application from being disbursed:
|
Validations do not make the Disburse button unavailable in the toolbar. |
| Validations | ||
| If an account number for a account product is required and not present, disbursement cannot continue. | ||
| If the Eligibility Required field is set to "Yes" within the Origination page in System Management, and the Primary applicant value for IsEligible is false, then disbursement cannot continue and an error message stating the following is received: "The primary applicant is not eligible." | ||
| Stipulations required for disbursement must be met or waived. | ||
| DisbursementDate is required. | ||
| If AutoTransfer/ACH, FIAccountNumber is required. | ||
| If ACH, ACHRoutingNumber is required. | ||
| If ACH, ACHAccountNumber is required. | ||
| If ACH, ACHPrimaryOwnerName is required. | ||
| If ACH, ACHAccountTypeId is required. | ||
| If disbursement provider is batch, must pass its validation. | ||
| Ensures funding is within limits. | ||
| OFAC is active and has not been run on a primary applicant. | ||
| Precise ID is active and applicants have not passed the Precise ID check. | ||
| The application cannot have already been disbursed. | ||
| The application must be approved. | ||
| The application cannot be withdrawn. | ||
| The application cannot have a disbursement pending. | ||
|
If the Minimum and/or Maximum Term set for an Open End loan is exceeded.
|
In addition to the system-defined validations, institutions are able to create their own validations and To Dos that have the ability to prevent an application from disbursing.
