diff --git a/modules/purchase_trade/process_documentation/ITSA/Interacid_Tradon_Practice_Book.html b/modules/purchase_trade/process_documentation/ITSA/Interacid_Tradon_Practice_Book.html
index cdda475..d464586 100644
--- a/modules/purchase_trade/process_documentation/ITSA/Interacid_Tradon_Practice_Book.html
+++ b/modules/purchase_trade/process_documentation/ITSA/Interacid_Tradon_Practice_Book.html
@@ -415,10 +415,11 @@
         <tbody>
           <tr><td>Purchase contract</td><td><a class="model-link" href="#purchase.purchase" data-tryton-model="purchase.purchase">purchase.purchase</a></td><td>Supplier-side commercial contract.</td></tr>
           <tr><td>Sale contract</td><td><a class="model-link" href="#sale.sale" data-tryton-model="sale.sale">sale.sale</a></td><td>Customer-side commercial contract.</td></tr>
+          <tr><td>Open lot</td><td><a class="model-link" href="#lot.lot" data-tryton-model="lot.lot">lot.lot</a></td><td>Planned quantity used for matching.</td></tr>
           <tr><td>Physical lot</td><td><a class="model-link" href="#lot.lot" data-tryton-model="lot.lot">lot.lot</a></td><td>Executed quantity used for matching, costing and invoicing.</td></tr>
           <tr><td>Lot quantity state</td><td><a class="model-link" href="#lot.qt" data-tryton-model="lot.qt">lot.qt</a></td><td>Open, physical, matched or shipped quantity status used by matching screens.</td></tr>
           <tr><td>Shipment</td><td><a class="model-link" href="#stock.shipment.in" data-tryton-model="stock.shipment.in">stock.shipment.in</a></td><td>Operational record for shipment milestones, BL data, costs and lots.</td></tr>
-          <tr><td>Budgeted/ordered/actual cost</td><td><a class="model-link" href="#fee.fee" data-tryton-model="fee.fee">fee.fee</a></td><td>Cost entered first at contract level, then ordered at shipment level, then allocated to physical lots.</td></tr>
+          <tr><td>Budgeted/ordered/actual cost</td><td><a class="model-link" href="#fee.fee" data-tryton-model="fee.fee">fee.fee</a></td><td>Cost entered first as budgeted at contract level, then ordered at shipment level and inherited on all linked physical lots. Specific costs can be directly assigned to physical lots.</td></tr>
           <tr><td>Price curve</td><td><a class="model-link" href="#price.price" data-tryton-model="price.price">price.price</a></td><td>Argus index or other market reference used by Basis/formula pricing.</td></tr>
         </tbody>
       </table>
@@ -432,7 +433,34 @@
     <h2>Party defaults and price curves</h2>
     <p>Before entering the trade, Back-office will make sure the supplier, customer, service providers and Argus curves exist. Party defaults reduce repeated entry on contracts and enforce Interacid's default tolerance discipline.</p>
 
-    <h3>Party screen - Contract and Execution tabs</h3>
+    <h3>Party screen - General tab</h3>
+    <p>In Tradon, any company, contact, entity or person  is a Party. This screen allows you to manage default values for various attributes. These defaults are used when creating contracts and other documents.</p>
+    <div class="table-wrap">
+      <table>
+        <thead>
+          <tr><th>#</th><th>Attribute</th><th>Required</th><th>Operational description</th></tr>
+        </thead>
+        <tbody>
+          <tr><td><span class="num">1</span></td><td><strong>Name</strong></td><td><span class="req req-yes">Yes</span></td><td>Name of the party.</td></tr>
+          <tr><td><span class="num">2</span></td><td><strong>Code</strong></td><td><span class="req req-yes">Yes</span></td><td>Unique code for the party (By default, it is auto-generated).</td></tr>
+          <tr><td><span class="num">3</span></td><td><strong>Party Name</strong></td><td><span class="req req-no">No</span></td><td>Long name for the party.</td></tr>
+          <tr><td><span class="num">4</span></td><td><strong>Building Name</strong></td><td><span class="req req-no">No</span></td><td>Self-explanatory.</td></tr>
+          <tr><td><span class="num">5</span></td><td><strong>Street</strong></td><td><span class="req req-no">No</span></td><td>Self-explanatory.</td></tr>
+          <tr><td><span class="num">6</span></td><td><strong>Postal Code</strong></td><td><span class="req req-no">No</span></td><td>Self-explanatory.</td></tr>
+          <tr><td><span class="num">7</span></td><td><strong>City</strong></td><td><span class="req req-no">No</span></td><td>Self-explanatory.</td></tr>
+          <tr><td><span class="num">8</span></td><td><strong>Country</strong></td><td><span class="req req-yes">Yes</span></td><td>Self-explanatory.</td></tr>
+          <tr><td><span class="num">9</span></td><td><strong>Subdivision</strong></td><td><span class="req req-no">No</span></td><td>Self-explanatory.</td></tr>
+          <tr><td><span class="num">10</span></td><td><strong>Categories</strong></td><td><span class="req req-yes">Yes</span></td><td>A party can belong to one or more categories. A supplier should be assigned to the appropriate supplier category (same principle applies to customers, brokers...).</td></tr>
+        </tbody>
+      </table>
+    </div>
+    <div class="screenshot-placeholder">
+      <div class="shot-title">Party General tab</div>
+      <img src="assets/party_general.png" alt="Party General tab">
+
+    </div>
+
+    <h3>Party screen - Contract tab</h3>
     <div class="table-wrap">
       <table>
         <thead>
@@ -444,7 +472,7 @@
           <tr><td><span class="num">3</span></td><td><strong>Weight basis</strong></td><td><span class="req req-no">No</span></td><td>Default commercial weight basis for the party, used when creating purchase or sale contracts.</td></tr>
           <tr><td><span class="num">4</span></td><td><strong>Association</strong></td><td><span class="req req-no">No</span></td><td>Default trade rule or association reference. Use only when the commercial terms require it.</td></tr>
           <tr><td><span class="num">5</span></td><td><strong>Origin</strong></td><td><span class="req req-no">No</span></td><td>Default product/geographic origin for documentation. For sulfuric acid, this should reflect the supplier or plant origin where relevant.</td></tr>
-          <tr><td><span class="num">6</span></td><td><strong>SLA places</strong></td><td><span class="req req-no">No</span></td><td>Optional execution service cost matrix by location. Use for service providers where standard control, terminal or logistics costs are known by place.</td></tr>
+          
         </tbody>
       </table>
     </div>
diff --git a/modules/purchase_trade/process_documentation/ITSA/assets/party_general.png b/modules/purchase_trade/process_documentation/ITSA/assets/party_general.png
new file mode 100644
index 0000000..4f69095
Binary files /dev/null and b/modules/purchase_trade/process_documentation/ITSA/assets/party_general.png differ

#	Attribute	Required	Operational description
1	Name	Yes	Name of the party.
2	Code	Yes	Unique code for the party (By default, it is auto-generated).
3	Party Name	No	Long name for the party.
4	Building Name	No	Self-explanatory.
5	Street	No	Self-explanatory.
6	Postal Code	No	Self-explanatory.
7	City	No	Self-explanatory.
8	Country	Yes	Self-explanatory.
9	Subdivision	No	Self-explanatory.
10	Categories	Yes	A party can belong to one or more categories. A supplier should be assigned to the appropriate supplier category (same principle applies to customers, brokers...).
3	Weight basis	No	Default commercial weight basis for the party, used when creating purchase or sale contracts.
4	Association	No	Default trade rule or association reference. Use only when the commercial terms require it.
5	Origin	No	Default product/geographic origin for documentation. For sulfuric acid, this should reflect the supplier or plant origin where relevant.
6	SLA places	No	Optional execution service cost matrix by location. Use for service providers where standard control, terminal or logistics costs are known by place.