Table of contents: 


UI Labels Updated to Clearly Show Payment Posted and Paid Dates 

Description:
The UI has been enhanced to clearly reflect distinct payment milestones by updating date labels related to payment posting and payment completion. This ensures better clarity and alignment with the underlying payment information captured by the system. 
With this enhancement: 
  • The generic Invoice Date label has been updated in relevant sections of the UI. 
  • Payment Posted Date is now displayed next to Payment Posted Ref No 
  • Payment Paid Date is now displayed next to Payment Paid Ref No 
  • In bulk upload and export files, where a single date field was previously labelled as “Invoice Date”, it is now labelled as Date. 
  • The existing Invoice Date field continues to be fetched and displayed correctly at the indent level, with no change to its logic or behaviour. 
  • The change is UI-only, with no impact on backend data, mappings, or workflows. 
Why This Matters: 
  • Improves clarity by clearly distinguishing between payment posting and payment completion dates. 
  • Enhances user understanding of payment timelines.
  • Maintains existing system behaviour while improving UI accuracy and readability.


Enhancement to Support Optima Variance & Variance Summary Reports in Reports V2 with Multi-Date and Depot Filter  

Description:
Optima Variance and Optima Variance Summary reports have been enhanced and made available in Reports V2, using the existing optima_entries data source. These reports now support improved filtering and align with current permission and access controls.

With this enhancement: 

  • Optima Variance and Optima Variance Summary reports are available in Reports V2. 
  • Reports continue to use the existing optima_entries collection when the Optima feature is enabled. 
  • Report access and visibility follow the existing permission and access control logic. 
  • Depot Selection:
    • Report generation supports single depot selection. 
    • Multiple depot selection is restricted to maintain data accuracy, consistency and load.
  • Date Selection: 
    • Users can select a date range while generating the reports. 
    • Report data is fetched strictly based on the selected date range. 
    • If the selected range exceeds the configured limit, a validation message is displayed as “Please select a date range within <configured limit> day(s)”.

Why This Matters: 

  • Enables access to Optima Variance insights directly from Reports V2. 
  • Provides flexible date-range analysis with controlled system performance. 
  • Ensures consistent data accuracy using existing Optima data sources. 
  • Maintains secure and role-based access to reports.
 


Enhancement for PTL Grouping – Validation & Ungrouping Functionality 

Description:
PTL dispatch workflows have been enhanced to provide clear indent-level visibility for mandatory Material Invoice (MI) and LR validations, along with the ability to selectively ungroup non-compliant indents. This ensures smoother dispatch while maintaining all required validations. 

With this enhancement: 

  • During PTL dispatch, the validation popup displays the specific indent IDs missing MI and/or LR. 
  • If more than 10 indents are impacted, the indent numbers are shown in a tooltip. 
  • Users can ungroup indents that are missing MI or LR before dispatch. 
  • Ungrouped indents are treated as separate shipments. 
  • PTL groups with compliant indents can proceed with dispatch without interruption. 
  • Existing PTL grouping logic remains unchanged. 
Why This Matters: 
  • Improves dispatch efficiency for PTL shipments. 
  • Provides clear visibility into validation requirements at the indent level. 
  • Allows uninterrupted dispatch of compliant indents. 
  • Enhances operational control while maintaining mandatory MI/LR compliance.  
 


ERP Reference ID to support Dual Transporter Reference ID

Description: 

The Procure module has been enhanced to support reference IDs from ERP. 

With this enhancement:

  • Vendor Master now maintains a single reference_id field.
  • ERP sends both existing and new ERP reference IDs in the payload.
  • The existing reference ID is used to identify and update the new ERP reference ID in Procure.
  • The new Reference ID must be valid and unique with respect to each client.  
  • Rejection reasons are captured and mapped against reference IDs.
  • Rejected transporter records can be downloaded as ERP Transporter Rejections from the Transporter Master export section in Procure. 
Why This Matters: 
  • Ensures correct reference ID usage across the system.



Freight Invoice API Enhancements for Posting and Custom Field Updates 

Description:
Freight Invoice processing has been enhanced to support API-driven posting and improved flexibility in managing custom fields, ensuring smoother financial provisioning and richer data synchronisation with ERP systems. 

With this enhancement: 

  • Freight invoice posting is triggered when invoices are created or updated via API.
  • Custom fields at the freight invoice level can be updated even after the invoice reaches Approved status.
  • Custom field updates are accepted via API even when there is no change in invoice status (e.g., Approved → Approved).
  • All relevant freight invoice custom fields are included in the Freight Invoice Posting API payload sent to the ERP. 

Why This Matters: 

  • Ensures timely and complete freight provisioning through API-based workflows. 
  • Enables post-approval data enrichment for business-critical custom fields. 
  • Improves data accuracy and completeness in ERP integrations. 
  • Enhances flexibility while preserving existing approval workflows.