Key Enhancements:

• Dealer ID Added to Variable Loan Endpoint

  • Variable loans now include both Client and Dealer information.
  • Dealers also have their own associated clients.

• New Versioned Endpoints (v7):

  1. Get Accounts Endpoint
     • Retrieves all accounts.
     • Expanded from the existing v1 endpoint to include DealerId for the variable loan system.
  2. Get Variable Loan by ID
     • Retrieves variable loan details filtered by ID.
     • Expanded from the existing v1 endpoint to include DealerId.
       

We’ve expanded auditing capabilities to provide greater transparency and control over Curtailment-related activities on Bailment Accounts.

Key Updates:

• Curtailments & Curtailment Direct Debits:

  • Auditing has been implemented for Curtailments and Curtailment Direct Debits on Bailment Accounts.
  • Audit records can be accessed directly from the Bailment Account screen by selecting the Audit button.

• Curtailment Schedules:

  • Auditing has also been added to Curtailment Schedules.
  • These records are viewable from the Edit Curtailment Schedule dialog via the Audit button.

These enhancements support improved oversight and historical tracking of Curtailment actions, helping users maintain compliance and data integrity.

1. Red: Critical errors that must be resolved before proceeding.
   
2. Yellow: Important issues that need correction to continue.
   
3. Blue: Warnings only; informational and do not block processing.
   

When performing a dealer transfer on an asset with a curtailment arrangement in place, if the curtailment schedule has not yet started, the system allows the account to be transferred. However, the curtailment-related direct debits (DDs) on the originating account are not being removed as expected.

This results in residual DDs remaining on the original account post-transfer, which can lead to incorrect billing or confusion in account management.

Issue Resolved:
The system logic has been updated to ensure that when a dealer transfer is executed under these conditions, any curtailment DDs associated with the originating account are correctly removed. This aligns with expected behavior and prevents unintended DD activity on inactive accounts.

A bug was identified in the Security Register (Sec Reg) dialog where certain date fields are unintentionally cleared when the dialog is closed using the X button.

Steps to Reproduce:

• Highlight and copy the Date of Birth field.
• Close the dialog using the X button (without pressing Save).
• Reopen the dialog: the Date of Birth field is now blank.
• An audit record is created showing the removal of this data.

This issue causes the Date of Birth, Driver Licence Expiry Date, and Date of Death fields to be cleared from both the UI and the database when the dialog is closed via the X button. This leads to unintended data loss and audit entries that incorrectly suggest intentional removal.

Resolution:
The dialog behavior has been corrected to ensure that closing via the X button does not clear any data from the UI or database. All date fields now persist regardless of whether the user saves or closes the dialog.

A bug was identified in the MotorWeb API related to the handling of the VehicleType field. The issue was triggered by changes in the values provided by NZTA, which were not reflected in the API’s XSD specification. This caused errors when unexpected VehicleType codes were received.

• ✅ Updated Codebase:
  New VehicleType codes from NZTA (as per the provided XML file) have been added to the system to prevent validation errors.

• ✅ Error Handling Improvements:
  Enhanced error handling now displays a customised error message when unexpected values are encountered, improving transparency and debugging.

• ✅ Additional Fixes:
  Resolved a secondary issue related to missing vehicleRucRuctypeCode values, which previously caused the MotorWeb search to fail.

These updates ensure smoother integration with NZTA data, reduce API failures, and improve the robustness of MotorWeb search functionality.

A new field has been introduced to support Variable Loan account types within Quote Profiles, providing greater flexibility in quoting scenarios.

Key Changes:

• ✅ New Field Added:

  • Label: Variable Loan Quote
  • Visibility: Only exposed when the account type associated with the quote profile is based on the Variable Loan system.

• ✅ Dropdown Options Available:

  • Daily Interest – Repayable
  • Daily Interest – Reinvest
  • Annualised Interest – Repayable
  • Principal & Interest (default)

• ✅ Default Behavior on Upgrade:
  Existing quote profiles will default to Principal & Interest during the database upgrade to ensure consistent system calculations.

This enhancement improves quoting accuracy and supports a broader range of loan structures within the quoting process.

1. Reducing Principal

• Total Principal Due over the life of the loan excluding the interest amounts.

We’ve implemented auditing capabilities for Security Makes to enhance traceability and accountability.

• Audit Tracking: All changes made to Security Makes are now recorded.
• Audit Access: Users can view audit records directly within the Edit Security Make dialog by selecting the new Audit button.

This feature provides greater visibility into modifications and supports compliance and review processes.

• Temporary IO Instalment Period:
  The system now treats the IO amount as a temporary instalment for a defined period (e.g., 6 months). During this time, the IO value is reflected as the current instalment on the account.

• Automatic Transition to P&I Instalment:
  After the IO period concludes and the final IO instalment has been posted, the system will automatically update the account to reflect the Principal & Interest (P&I) instalment amount.

• Instalment Lifecycle:

  • Instalment One: Temporary IO instalment runs for the defined IO period.
  • Instalment Two: P&I instalment takes effect for the remainder of the account term unless another Interest Rate Change Notification is processed.
    

• Direct Debit Schedule:
  No changes have been made to the Direct Debit Schedule functionality. It continues to operate using the IO DD amount.

• Projection Report Accuracy:
  These changes ensure that both instalment values are correctly displayed for their respective dates, resolving prior issues with the Projection Report and enabling accurate client communication.

Enhancement Summary:
To support more detailed communication templates, a new Communication replacement field has been added to capture the Interest Rate Change Percentage from the Main dialog of the Interest Rate Change Notification process.

Details:

• ✅ New Field Added:

  • Field Name: [OCR_Actual]
  • Source: Interest Rate Change Percentage from the Main dialog

• ✅ Existing Field Reminder:

  • [OCR_Change] continues to bring through the Interest Rate Change value from the Edit Rate Change Notification Details dialog.

This enhancement allows for more precise and dynamic communication generation, especially in scenarios where both the change value and percentage are relevant.

Enhancement Summary:
Users now have the ability to select and delete multiple Direct Debit lines from the Direct Debit Schedule in a single action, improving efficiency and usability.

Key Features:

• ✅ Multi-select support: Select multiple Direct Debit entries at once.
• ✅ Bulk deletion: Delete selected lines simultaneously, reducing manual effort.
• ✅ Validation: Ensures only eligible lines are removed, maintaining data integrity.

This update streamlines Direct Debit management and supports faster adjustments to scheduled payments.

Issue Resolved:
When the Post Interest Rate Process was run, communications were being created with a Completed Date already populated. This was incorrect behavior, as these communications should remain incomplete until manually actioned or processed further.

Fix Implemented:

• Communications generated during the Post Interest Rate Process will now have a blank Completed Date by default.
• This ensures proper tracking of communication status and prevents premature closure of records.

This update improves workflow accuracy and ensures communications reflect their true processing state.

When running the Variable Loan Account Status report across two companies, the Future Balance Total displayed at the bottom of the report was showing the combined ledger total for both companies, regardless of the company selected in the report dialog. This caused confusion, as the other summary lines were correctly scoped to the selected company.

Resolution:
The report has been updated to improve clarity and consistency:

• The Future Balance Total line now reflects the balance for the selected company only, aligning with the other summary lines.
• A new line has been added to the report to display the Total Future Balance for both companies. This line represents the full ledger total and is clearly labeled to distinguish it from the company-specific total. This line will not display if a company has been selected as a report parameter
  

Issue Resolved:
Previously, when entering dates beyond the year 2049 in Vault or Bailment forms (e.g., entering 010155 for 1 Jan 2055), the system incorrectly interpreted the year as 1955 due to the default behavior of Microsoft’s TwoDigitYearMax, which is limited to 2049.

Enhancement Implemented:
We have overridden the default behavior and extended the TwoDigitYearMax to 2069, allowing correct interpretation of two-digit years up to 2069.

Impact:

• Dates entered with two-digit years (e.g., 55) will now correctly resolve to 2055 instead of 1955.
• This change ensures accurate date handling for long-term contracts and future-dated entries.