26.4 Release Notes

October 2026

Download Document

PRODUCT IMPROVEMENTS

Duplicate Facility Code Validation

The system now prevents duplicate Facility Codes on Ship To addresses.

What’s Improved:

• Added validation to prevent duplicate Facility Codes on Ship To addresses in Contact
• Management and CIW imports
• Clear error messages display when a duplicate Facility Code is detected

Accounts Payable Status Preservation

Paid status on accounts payable entries is now preserved through the document ID capture process.

What’s Improved:

• Accounts payable entries marked as Paid retain their status after running Capture Document ID
• The Payables Export now accurately reflects payment status
• Previously paid entries no longer display as new after document ID capture

Previously, accounts payable entries marked as Paid could revert to New status after running the document ID capture process, causing the Payables Export to show incorrect payment statuses.

Address Import for Shared Locations

Multiple companies can now share the same address without address data being dropped during CIW import.

What’s Improved:

• Multiple companies can now share the same address during Funder import via CIW
• Shared addresses are correctly associated with each company without being dropped

Previously, if a Funder company operated from the same address as another company in the system, that address would be dropped during CIW import, requiring manual re-entry after the import was complete.

Reversal Entry Status After Document ID Capture

Reversal entries now correctly update to Posted status after running document ID capture, even when partial asset returns have occurred.

What’s Improved:

• Reversal entries update to Posted status after Capture Document ID completes
• Posting status updates occur correctly even when assets have been partially returned during a lease
• Reconciliation reporting now reflects the true posting status of reversal entries

Previously, some reversal entries remained in a Transferred status instead of updating to Posted. This fix ensures your reconciliation reports accurately reflect the true posting status of these entries.

Bargain and Likely Purchase Auto-Check Logic

The Bargain and Likely Purchase checkboxes now only auto-check when both conditions are met.

What’s Improved:

• Bargain and Likely Purchase checkboxes only auto-check when both a buyout option exists on the lease and the buyout price meets the configured threshold
• Removes the risk of unintended lease reclassification as Finance/Capital when no buyout option is present

Previously, the Bargain and Likely Purchase checkboxes could auto-check based on the threshold comparison alone, without confirming that a buyout option was actually present on the lease, causing leases to be unintentionally reclassified as Finance/Capital.

Category Lease Rate Factor Handling in Lease Modifications

Category-level lease rate factors now work correctly during lease modifications, and the category LRF carry-forward feature is now available for general use.

What’s Improved:

• The Product Category field now displays correctly when entering LRF by asset type during a modification, and Blended LRF and Periodic Payment values populate as expected
• Category LRFs assigned on the original lease now carry forward correctly to the modified lease through the UI or bulk import (MDIW), for both single and multiple product categories
• Category LRFs can be edited, added, or removed on the modification’s Terms tab, with changes reflected on the new modified deal (M00#)

Known Limitations:

• When a modification adds assets in a new product category, LRFs on original categories may not carry forward. If a category shows no LRF on the modified deal, manually enter it on the Category LRFs tab.
• When a modification removes all assets in a product category, the Schedule tab on the Terms tile may still list the removed category, though the Deal Summary updates correctly.

Previously, category LRFs did not carry forward reliably to modified leases, and the Product Category field displayed blank when entering LRF by asset type during modifications, causing Blended LRF and Periodic Payment values to remain blank.