Table of contents: 



Additional Invoice and Material Level Fields in Freight Invoice Payload 


Description:

The Freight Invoice payload has been enhanced to improve auditability, reconciliation, and downstream processing by including additional invoice-level and material-level details.

With this Enhancement:

  • Invoice lifecycle details such as Invoice Status, Action Date, and Action By are included in the payload. 
  • Invoice Raised By, Proforma Invoice Number and Transporter details (Name and PAN) are added. 
  • Legal Entity Code is included for billing reference. 
  • Material-level fields such as Material Invoice Date is included.

Why this Matters:

  • Enables tracking of invoice approval lifecycle in downstream systems.

  • Improves audit visibility of invoice actions.

  • Provides transporter-level statutory details for integrations.

  • Enhances reconciliation with availability of material-level operational dates.



Indent Top-Up Timeline Visibility  


Description:

Timeline has been enhanced to provide better visibility into indent top-up activities by introducing timeline tracking for both Optima Core and Manual Top-Up flows.

With this Enhancement:

  • A new timeline entry is created each time an indent is topped up with additional material. 
  • Applicable for both Optima Core Top-Up and Optima Manual Top-Up. 
  • Multiple top-ups on the same indent are recorded as separate timeline entries. 
  • Each entry captures the event name “Indent TOP UP” along with the corresponding timestamp.

Why this Matters:

  • Provides clear visibility into whether and when an indent was topped up.

  • Enables tracking of multiple top-up events for the same indent.

  • Improves transparency and operational traceability.



LR Number Validation and Trimming Across System Layers   


Description:

The LR number handling has been enhanced to ensure consistent formatting across UI, backend, and integrations by implementing validation and automatic trimming of leading and trailing spaces.

With this Enhancement:

  • UI restricts entry of LR numbers with leading or trailing spaces. 
  • Backend automatically trims LR values before sending them to vendor APIs. 
  • Trimming logic is applied across bulk uploads and ERP/API integrations. 
  • Consistent LR formatting is maintained across all system layers.

Why this Matters:

  • Eliminates mismatch between UI-displayed and backend-sent LR values. 

  • Reduces POD fetch failures caused by incorrect LR formatting. 

  • Ensures seamless integration with vendor systems.


System Timestamp Capture for Back-Dated Actions 


Description:

The system has been enhanced to improve audit traceability by capturing system-generated timestamps for all back-datable operational actions, in addition to user-entered event timestamps.

With this Enhancement:

  • System timestamp is captured whenever a user creates or updates back-datable operational fields. 
  • Both user-entered timestamp and system-generated timestamp are stored separately. 
  • Applicable to operational actions such as Truck In, Truck Out, Material Invoice Date, Reported Date, Unloading Start/End Time, POD Date and more. 
  • System timestamp reflects the actual date and time when the action was recorded in the system

Why this Matters:

  • Eliminates audit gaps between actual action time and user-entered event time.

  • Improves traceability and accountability of operational updates.

  • Enables accurate reporting and audit analysis.

  • Provides clear visibility into when actions were performed in the system.



Configurable Division-Based Material Grouping in Document Section


Description:

The Indent Document section has been enhanced to improve usability by introducing a configurable option to control division-based grouping of materials in the UI.

With this Enhancement:

  • A new toggle “Disable Division Grouping” is added in Admin Settings → Client Settings → Data Manager. 
  • By default, the toggle remains disabled for all clients. 
  • When enabled, materials are displayed in a single consolidated list without division-wise grouping in an indent.
  • Division is shown as a column in the material table when grouping is disabled. 
  • When the toggle is disabled, existing behavior of grouping materials by division continues. 
  • This is a UI-level change with no impact on backend data, bulk uploads, or ERP integrations.

Why this Matters:

  • Improves visibility by allowing users to view all materials in a single list.

  • Enhances ease of verification and usability.

  • Provides flexibility to clients based on their operational preference.



Movement-Level Permissions for LR Number and POD/LR Attachments 


Description:

The system has been enhanced to improve workflow control by introducing movement-level access configuration for LR Number input and POD/LR Attachment uploads.

With this Enhancement:

  • Access to LR Number input and POD/LR Attachment upload is configurable based on movement type (Primary, Secondary, Return, Vendor). 
  • Movement-level control is applied in addition to existing user-role permissions. 
  • System allows enabling or disabling access per movement type. 
  • Final access is determined using a combination of Movement Type and User Role permissions.

Why this Matters:

  • Prevents incorrect users from uploading documents.

  • Strengthens control over document handling based on movement type.

  • Reduces operational confusion and improves process clarity.



GPS to SIM Fallback for Continuous Visibility


Description:

The tracking system has been enhanced to ensure uninterrupted visibility during mid-transit scenarios by extending the fallback mechanism from GPS to SIM tracking when GPS data is unavailable.

With this Enhancement:

  • System automatically detects GPS tracking failure and triggers fallback to SIM tracking (If fallback is enabled). 
  • If no GPS pings are received for 15 minutes, fallback to SIM tracking is initiated (existing behavior retained). 
  • If GPS remains unavailable beyond a configurable duration (e.g., 1 day from last ping), SIM tracking is automatically triggered. 
  • In case of vehicle change mid-transit, system checks GPS availability for the new vehicle and initiates SIM tracking if GPS is not active. 
  • If tracking starts with SIM, any subsequent vehicle change continues with SIM tracking only. 
  • If GPS resumes after SIM fallback, both GPS and SIM tracking continue. 
  • Indent displays a clear indication of fallback from GPS to SIM along with timestamp. 
  • SIM tracking is triggered only when driver mobile number is available and SIM tracking is enabled for the client.

Why this Matters:

  • Ensures continuous tracking visibility without manual intervention.

  • Eliminates tracking gaps during vehicle changes or GPS failures.

  • Improves operational efficiency and real-time monitoring.



Separate Vahan/Sarathi Validation for FTL and PTL Flows 


Description:

The Vahan/Sarathi validation flow has been enhanced to support separate handling for FTL and PTL movements, ensuring compatibility with PTL grouping without impacting existing validation behavior.

With this Enhancement:

  • Separate configurations are introduced for Vahan and Sarathi validations across FTL and PTL flows. 
  • New validation features are supported in addition to the existing configurations. 
  • When both existing and new feature configurations are enabled, the new feature configuration takes priority for validation handling. 
  • If new configurations are disabled, the existing validation behavior continues without impact. 
  • PTL grouping validations are newly handled for both shipper and transporter during vehicle assignment. 
  • Override permissions allow users to bypass validation errors during PTL grouping flows.

Why this Matters:

  • Prevents conflicts between Vahan/Sarathi validation and PTL grouping logic.

  • Eliminates the need to disable validations globally for all movements.

  • Ensures vehicle compliance checks continue for FTL indents.