ICE Data & Document Automation Critical Patches

An issue occurred where the page number data field was not generated, causing Tax Returns and Investment Statement documents to show missing page-level data fields during validation. The issue has been fixed in this critical patch release. After sorting, the page number field is now correctly generated and displayed on each page of the document, enabling complete and accurate validation.

ADE-23792

When an EVOE document's income table was split across two pages, income data for years 2024/2025 was not being extracted correctly. As a result, some data point values were not found in data validation work items in the ICE Data & Document Automation desktop application. This also resulted in incomplete or incorrect data displayed in Income Analyzer.

The issue has been resolved. The extraction engine has been updated to correctly handle EVOE income tables that span multiple pages. The income data is extracted accurately, each description properly associated with its corresponding amount, and no placeholder values are added. Data validation work items show required values in the data extraction panel. Income Analyzer displays complete income history and accurate income calculations for all applicable years.

AIQD-8675

When an EVOE document's income table was split across two pages, ADE could not associate income descriptions with their corresponding amounts for 2024/2025 and was populating placeholder values for EVOE. This resulted in incomplete or incorrect data extraction for prior years.

The issue has been resolved. The extraction engine has been updated to correctly handle EVOE income tables that span multiple pages. The income data is extracted accurately, each description properly associated with its corresponding amount, and no placeholder values are added.

ADE-23544

There was an issue with Electronic Verification of Employment (EVOE) address extraction where ZIP codes followed by a country code (e.g. "94588, US") were being incorrectly captured. With this fix, the formatting logic has been updated to strip the country code suffix, ensuring only the ZIP code is retained.

ADE-23647

Resolved an issue where the Applicant field was missing from the Borrower Credit Score Detail data point in the credit report. The field now displays correctly as expected.

ADE-23553

Users encountered a "Cannot complete operation" error when attempting to submit documents for data validation. The ADE submission failures occurred due to new data attributes not being included in the ADE XML file.

The issue is resolved ensuring successful submission processing.

ADE-23620

There was an issue in the Data Mapper where mapping exceptions were incorrectly calculated. When unvalidated data was ingested for a military paystub, unmapped data points from that document were not being included in the exception count.

With this fix, the mapping exception count now includes unmapped data points from unvalidated military paystubs, giving a complete and accurate count.

AIQP-69683

Resolved an issue preventing lenders from delivering loans via SFTP. The issue was caused by a compatibility gap between the delivery system and the security requirements of the SFTP destination server.

The delivery system has been updated to support the latest security standards required by modern file delivery servers. Affected lenders can now successfully deliver loans through their automated workflows as expected.

AIQP-69555, DDASRE-16709

When selective document propagation was enabled, original attachments were incorrectly moved to the zArchive folder for suppressed document types instead of remaining in their original container.

The issue has been resolved. The Post Filing Indexing Validation workflow has been updated to correctly apply selective propagation settings. Original attachments will remain in their original container when their document type is suppressed from propagation.

AIQP-69494

For correspondent customers, the Audit Analyzer's Golden Data Set field mappings were writing back audit data to standard Encompass fields instead of the designated auxiliary fields.

With this fix, the Encompass field IDs for Audit Analyzer-related mappings have been corrected. Writeback data will now be accurately directed to the appropriate auxiliary fields provisioned for the correspondent flow.

AIQP-69767

There was an issue that prevented users from manually associating a borrower to an Occupancy Agreement document in the Business Association Application (BAA).

A borrower whose name included a suffix of "II" experienced a data extraction issue: the two lowercase L's in the borrower's last name were incorrectly extracted as the letter "i". This mismatch prevented the borrower from being automatically assigned as the applicant on the Occupancy Agreement. When users attempted to complete application association manually through BAA, they received an error. The error occurred due to a null collaborator created when applicant data was cleared via the Data Correction Panel.

The issue is resolved. Null collaborator creation is blocked, and users can successfully complete application association in BAA.

AIQP-69434

There was an issue with duplicate loan data points created upon waive, reset, and save operations. As a result, documents present in the loan folder and correctly associated to borrowers were not getting to the Employer Merge. The Income Analyzer displayed no data despite documents being accepted and valid.

The issue is resolved. Auto-mapping was disabled to prevent duplicates, and existing duplicates were removed from affected loan folders. Documents flow correctly to Employer Merge and appear in Income Analyzer as expected.

AIQP-69463

An issue was identified where SFTP address books were not being automatically updated to the Approved status upon completion of an approval request. Affected books remained in the Under Review status indefinitely.

The issue has been resolved. Address books will now correctly transition to the Approved status once the associated approval request is completed.

AIQP-69728, DDASRE-17066

Outbound SFTP deliveries to destination servers using advanced cipher algorithms such as ChaCha20‑Poly1305 now complete successfully. The underlying file transfer utility has been upgraded to support modern encryption standards, restoring reliable delivery to recipients that have enabled this server-side requirement. Before this fix, deliveries failed due to SFTP cipher mismatches.

AIQP-70273

SFTP deliveries to destination servers that require the rsa-sha2-256 or rsa-sha2-512 host key algorithms now complete successfully. The file transfer utility has been upgraded to support these algorithms, resolving the connection negotiation behavior that previously blocked deliveries to affected recipients.

AIQP-70970

When a destination SFTP server has not whitelisted the sending IP address, the outbound delivery now fails after standard retry attempts instead of remaining in a pending state. This change frees FTP adaptors for other deliveries and surfaces a clear delivery failure so that the sender can take corrective action with the receiver. Before this fix, shared FTP adaptors were blocked when destinations were not whitelisted.

AIQP-70398