ProDon:Commitment Management (Objective vs Automatic)

From Logilys
Revision as of 15:23, 23 February 2017 by Jguillemette (talk | contribs)
Jump to: navigation, search
Commitment Management (Objective vs Automatic)


Introduction

A commitment is an agreement taken between a client and the organization. In ProDon, the commitment refers to this agreement. The commitment notion generally implies several instalments on long term. The commitment will allow several notions to be followed and viewed, such as the commitment total objective, the sum of money given by the client up to this day as well as the projections to come. The commitment itself does not contain money, but it will be used to create the planned transactions according to the agreement.

Commitment Creation

All commitments are created from a client file. Most of the time, a commitment will have to be created from the one with whom an agreement was taken or from the one that will pay for the commitment.

The commitments are divided in 2 types: objective and automatic. For more details, please refer to the sections about the particularities of each type.

ProDon5 Commitment Management (Objective vs Automatic) 001.png
To create a commitment, select the "Commitment" tab of the client file (A) then click on the add button Bouton Ajouter.png (B).


Presentation of common elements between the 2 commitment types (Main information and "Progression" tab)

ProDon5 Commitment Management (Objective vs Automatic) 002.png
A: Allows to select the commitment's client.
B: Allows to select the third party client if the option has been activated (See K)
C: Allows to choose the commitment type that the user will create.
D: Allows to choose the beginning date and the ending date of the commitment.
E : Allows to add internal notes about the commitment. F: Allows to document the origins that will be assigned to the generated transactions by the commitment.
G: Allows to document the canvasser of the generated transactions by the commitment. H: It shows the commitment advancement/progression, including the next instalment date, the targeted objective and the details of the created transaction by the commitment. This is also where the user will be able to end the current commitment.
I: Folder where all the documents linked to this transaction can be put. J : Allows to tie up an already done transaction to the current commitment.
K: Allows to activate/deactivate the add a third party client option to the transaction. L: Allows to do a Mass Mailing of commitment type.
M: Allows to access to the client or to the canvasser file tied to the commitment.


Frequency/Instalment Tab

It is here that the frequency and the instalment amount of the commitment can be set.

ProDon5 Commitment Management (Objective vs Automatic) 003.png
A: Allows to set the frequency and the instalment amount of the commitment. B: Allows to choose the payment method used to pay the generated transaction by the commitment.

Characteristics tab

Allows the addition, deletion and edition of the characteristics that need to be assigned to the commitment.

ProDon5 Commitment Management (Objective vs Automatic) 006.png
A: Buttons allowing to add, edit or delete commitment characteristics assign to the commitment. B: Here is the assigned commitment characteristics as well as their details.

Transaction Characteristics tab

Allows to add, delete and edit the transaction characteristics that you want to assign to the commitment.

ProDon5 Commitment Management (Objective vs Automatic) 004.png
A: Buttons allowing to add, edit or delete the commitment transaction characteristics assign to it. B: Here is the assigned commitment transaction characteristics as well as their details.

Tasks tab

ProDon5 Commitment Management (Objective vs Automatic) 005.png
A: Button to add/edit/delete the tasks linked to the commitment as well as changing their processing status. B: Details of the tasks assigned to the commitment

Difference between commitment by objective vs automatic

Commitment by objective

The transactions linked to commitments by objective are created when receiving a payment. This notion applies to commitments needing an action like a cheque process.

Automatic commitment

The transactions linked to automatic commitments will be massively created to a frequency that you can choose. This notion will apply to commitments which does not need any action to trigger the instalment, for example the instalments on the client's payroll or pre-authorized bank transfer.


Document name: ProDon:Commitment Management (Objective vs Automatic)
Version : 5