The EPC 2.0 December '26 release is scheduled for December 05, 2026. With this release, we've included the following new features and improvements:

Platform updates

The following EPC platform updates are included in this release:

• Transaction enhancements for accurate billing [EPC-47534]: Prior to this release, billing records were generated based on the original requestType associated with a transaction. In cases such as Credit (hard vs. soft pulls) and Appraisal orders (UAD 3.6 GSE-determined appraisal types), fulfillment partners often performed a different service than what was originally requested. Since there was no mechanism for partners to report these changes, billing discrepancies could occur, potentially resulting in revenue leakage.
  To address this gap, the Transaction Service now supports transaction amendments through the following new endpoints:
  • POST /v2/transactions/{transactionId}/amendments
  • GET /v2/transactions/{transactionId}/amendments
    These enhancements enable partners to report the actual service performed on a transaction, such as upgrading a BASIC_APPRAISAL to a FULL_APPRAISAL. The Transaction Service can now accept, validate, persist, and emit amendment events, ensuring billing is aligned with the services actually delivered.
• Duplicate PATCH Response detection and validation [EPC-31520]: Prior to this release, consecutive duplicate PATCH responses from partners could be processed multiple times, potentially resulting in redundant updates and unnecessary system activity. With this enhancement, duplicate responses are automatically detected, rejected with an appropriate HTTP error response, and excluded from further processing.
• ITP updates now supported for PDD partners [EPC-47865]: Ability to update ITP in UPDATE_DISCLOSURE_RECIPIENTS action to support PDD partners. Impacted field IDs: 3164 and 3197
• Opt-out for ICE-managed UAD 3.6 processing [EPC-46905]: Partners can now opt out of ICE-managed UAD 3.6 XML parsing and valuation collection processing while remaining eligible as pricing providers in lender scenarios. This enhancement helps provide flexibility for partners managing their own UAD 3.6 workflow and valuation data integration by introducing the following:
  • A new optional feature flag that enables partners to use their own UAD 3.6 processing implementation
  • Synchronization of the feature flag with SCM

JavaScript guest library updates

The following JavaScript guest library updates are included in this release:

• Document Uploader:
  • borrowerPairID filtering support [EPC-43211]: New optional borrowerPairID GUID parameter for partners to filter eFolder attachments by borrower pair:
    • When borrowerPairID is provided, the Document Uploader displays only eFolder attachments associated with the specified borrower pair
    • When borrowerPairID is not provided, all eFolder attachments are displayed
    • borrowerPairID must be the new GUID-based identifier, not the legacy format (for example, _borrowerPair1)
  • Support for large attachments [EPC-48153]: Document Uploader no longer enforces a 200 MB attachment size limit and now attempts to upload all files available in Encompass eFolder or from local sources. Any file size restrictions or processing failures are handled by downstream services, with errors returned to users as applicable:
    • Applies consistently to both local files and eFolder documents, providing a more uniform lender experience
    • The maxAttachmentSize setting no longer has a maximum allowed value
• Current Version selected by default in File Picker [EPC-47468]: To help ensure only active document versions are sent to partners, File Picker now defaults the Version filter to Current Version instead of All, helping users avoid selecting outdated document versions.
  Exceptions:
  • File sources that do not support version filtering continue to display all files
  • Version filtering is not applied to Partner Files, Local Drive, eSign, or Unassigned eFolder files