Client management - Cronologia

Francesco.bertuletti il 17:12, 23 feb 2016

2016-02-23T17:12:26Z

Francesco.bertuletti: /* Sales Contract */

2016-02-23T17:09:09Z

‎Sales Contract

Francesco.bertuletti il 11:07, 26 gen 2016

2016-01-26T11:07:23Z

Francesco.bertuletti: /* Stand Alone Contract */

2016-01-26T10:27:07Z

‎Stand Alone Contract

Francesco.bertuletti il 09:18, 26 gen 2016

2016-01-26T09:18:24Z

Francesco.bertuletti il 08:57, 26 gen 2016

2016-01-26T08:57:12Z

Francesco.bertuletti: /* Sales Contract */

2016-01-26T08:44:05Z

‎Sales Contract

Francesco.bertuletti: /* Sales Contract */

2016-01-26T08:37:34Z

‎Sales Contract

Francesco.bertuletti: /* Adding, editing and cancelling Client */

2016-01-20T16:02:02Z

‎Adding, editing and cancelling Client

Francesco.bertuletti: /* Adding, editing and cancelling Client */

2016-01-20T15:58:46Z

‎Adding, editing and cancelling Client

@@ Riga 127: / Riga 127: @@
 itmSUITE® contract enable the user to set the maxim expenses for hotel, lunch, dinner and travel and fix the Km travel value. Then is possible to insert the ''[[Glossary|billing schedule]]'' or define a ''[[Glossary|Sale role tariff]]''.
-itmSUITE® manages the states of the ''client'' who may be the following: "Provisory", "Operational","Suspended", "Closed", "Canceled". In the following table are summarized minimum information required for each state and interactions with other itmSUITE® functions. .
+itmSUITE® manages the states of the ''client'' who may be the following: "Provisory", "Operational","Suspended", "Closed", "Canceled". Here below are describe then common step to create a contract then the necessary highlight to manage the contract type mentioned above.
 {| class="wikitable"
 ! Information !! Field !! Note
 |-
-| Common|| <u>Name</u>|| Creation date of the ''[[Glossary|client]]''. Field automatically updated by itmSUITE®
+| General|| <u>Name</u>|| Sales Contract Short Description
 |-
-| Common|| <u>Contract Date</u>|| Date of Contract signature
+| General|| <u>Contract Date</u>|| Date of Contract signature
 |-
-| Common|| <u>Term Start Date</u>|| Starting Contract date
+| General|| <u>Term Start Date</u>|| Starting Contract date
 |-
-| Common|| <u>Term End Date</u>|| End Contract date
+| General|| <u>Term End Date</u>|| End Contract date
 |-
-| Common|| <u>Client</u>|| Contract ''[[Glossary|client]]'' reference
+| General|| <u>Client</u>|| Contract ''[[Glossary|client]]'' reference
 |-
-| Common|| <u>Currency</u>|| Contract ''[[Glossary|currency]]'' reference
+| General|| <u>Currency</u>|| Contract ''[[Glossary|currency]]'' reference
 |-
-| Common|| <u>VAT percent</u>|| Percentage of ''[[Glossary|VAT]]'' will be applied by '[[Glossary|Billing]]'' process
+| General|| <u>VAT percent</u>|| Percentage of ''[[Glossary|VAT]]'' will be applied by '[[Glossary|Billing]]'' process
 |-
-| Common|| <u>Billing Rule</u>|| Rule used  by ''[[Glossary|Billing]]'' process to define the '[[Glossary|Invoice]]'' date
+| General|| <u>Billing Rule</u>|| Rule used  by ''[[Glossary|Billing]]'' process to define the '[[Glossary|Invoice]]'' date
 |}
 == Stand Alone Contract ==

@@ Riga 127: / Riga 127: @@
 itmSUITE® contract enable the user to set the maxim expenses for hotel, lunch, dinner and travel and fix the Km travel value. Then is possible to insert the ''[[Glossary|billing schedule]]'' or define a ''[[Glossary|Sale role tariff]]''.
-itmSUITE® manages the states of the ''client'' who may be the following: "Provisory", "Billable", "Inactive", "Canceled". In the following table are summarized minimum information required for each state and interactions with other itmSUITE® functions.
+itmSUITE® manages the states of the ''client'' who may be the following: "Provisory", "Operational","Suspended", "Closed", "Canceled". In the following table are summarized minimum information required for each state and interactions with other itmSUITE® functions. .
 {| class="wikitable"

@@ Riga 161: / Riga 161: @@
 The aim of Fixed price contract is providing a simple way to manage Project / service Revenue inserting an agreement billing schedule and subordinate billing to delivery.
-To activate a Stand Alone contract is necessary to:
+To activate a Fixed Price contract is necessary to:
 * Select the Fixed Price for Services flag
 * Valorise the Total Service Fixed Amount
@@ Riga 167: / Riga 167: @@
 * Add one or more Billing schedule
 * Associate a delivery to a Billing schedule if we subordinate billing to the delivery met.

@@ Riga 154: / Riga 154: @@
 The aim of Stand Alone contract is providing a simple way to define a client due and inserting an agreement billing schedule.
 To activate a Stand Alone contract is necessary to:
-Select the Stand Alone contract flag
+* Select the Stand Alone contract flag
-Valorise the Total Service Fixed Amount
+* Valorise the Total Service Fixed Amount
-Add one or more Billing schedule
+* Add one or more Billing schedule

@@ Riga 125: / Riga 125: @@
 * Fixed price / T&M
-itmSUITE® contract enable the user to set the maxim expenses for hotel, lunch, dinner and travel and fix the Km travel value. Then is possible to insert the remittance schedule or define a Sale Role tariff
+itmSUITE® contract enable the user to set the maxim expenses for hotel, lunch, dinner and travel and fix the Km travel value. Then is possible to insert the ''[[Glossary|billing schedule]]'' or define a ''[[Glossary|Sale role tariff]]''.
 Here below are  describe then common step to create a contract then the highlight to
 necessary to manage the contract type mentioned above.
@@ Riga 134: / Riga 135: @@
 |-
 | Common|| <u>Name</u>|| Creation date of the ''[[Glossary|client]]''. Field automatically updated by itmSUITE®
 |-
 | Common|| <u>Client</u>|| Contract ''[[Glossary|client]]'' reference
 |-
-| Common|| <u>Currency</u>|| Contract '[[Glossary|currency]]'' reference
+| Common|| <u>Currency</u>|| Contract ''[[Glossary|currency]]'' reference
 |-
-| Common|| <u>VAT percent</u>|| Percentage of '[[Glossary|VAT]]'' will be applied by '[[Glossary|Billing]]'' process
+| Common|| <u>Billing Rule</u>|| Rule used  by ''[[Glossary|Billing]]'' process to define the '[[Glossary|Invoice]]'' date
-| Common|| <u>Billing Rule</u>|| Rule used  by '[[Glossary|Billing]]'' process to define the '[[Glossary|Invoice]]''date
+|}
-|}
+== Stand Alone Contract ==

@@ Riga 122: / Riga 122: @@
 * Controlling profitability of a project
 The main type of contract managed into the system:
-* Stand-alone contract / Linked to Project /
+* Stand-alone contract / Linked to Project / Service
 * Fixed price / T&M
 Here below
 are describe then common step to create a contract then the highlight to
 necessary to manage the contract type mentioned above.

← Versione meno recente		Versione delle 08:37, 26 gen 2016
Riga 117:		Riga 117:

	=== Sales Contract ===		=== Sales Contract ===
		+	Creating
		+	a Sales contract is the first step for:
		+	* Billing a client
		+	* Controlling profitability of a project
		+	The main type of contract managed into the system:
		+	* Stand-alone contract / Linked to Project /
		+	Service
		+	* Fixed price / T&M
		+	Here below
		+	are describe then common step to create a contract then the highlight to
		+	necessary to manage the contract type mentioned above.

@@ Riga 112: / Riga 112: @@
 <u>Organization Units</u>, enable the ''[[Glossary|user]]'' to define a complete Tree Level Hierachy of a Client. For each level (division,department,office) in general we can define a ''[[Glossary|resource ]]'' that belongs to it and definire is role as Member or Manager.
+* Manager belongs to more <u>Organization Units</u>
-Manager can belongs to more <u>Organization Units</u>
+* Member belongs to only one <u>Organization Unit</u>
-Member can belongs to only one <u>Organization Unit</u>
+For each Organization Unit the [[Glossary|user]] can provide <u>address</u> informations and can enable the <u>Use for Ticket Info</u> flag.
 === Sales Contract ===

@@ Riga 105: / Riga 105: @@
 |Bank Accounts|| <u>Bank Name</u> ,<u>Account Number</u>,<u>ABI</u>,<u>CAB</u> || Alphanumeric fields. Mandatory fields to set define a Bank relationship.
 |-
-|Bank Accounts|| <u>CIN</u> ,<u>Notes</u>,<u>Address</u></u> || Alphanumeric fields.Fields that enable the user to define the bank account' informations
+|Bank Accounts|| <u>CIN</u> ,<u>Notes</u>,<u>Address</u></u> || Alphanumeric fields.Fields that enable the ''[[Glossary|user]]'' to define the bank account' informations
 |-
 |Bank Accounts || <u>Defaults</u>  || Flag that determines the use of the bank account specified as default bank account.
 |}
 === Sales Contract ===