e-OSCAR 4.0 Planned Releases
Check out features and enhancements that we're planning on releasing in upcoming e-OSCAR System Releases.
NOTE: Delivery dates for these features are subject to change due to unforseen circumstances including development delays, feature priority modifications, quality assurance testing, or direction & guidance from regulators &/or Consumer Reporting Agencies. RELEASE CONTENTS ARE NOT FINALIZED UNTIL JUST PRIOR TO SCHEDULED RELEASES. FINAL INFORMATION ABOUT RELEASE CONTENT IS INCLUDED IN RELEASE NOTES.
e-OSCAR's General Release Timeline
Planned release contents updated as of: August 5, 2025
Sept 25, 2025
eo2025.12
-
Modification to Get Next Notification process to present the next oldest Notification of the same type instead of the next oldest Notification regardless of type. For instance, when working Block Notifications, clicking Get Next will return the next oldest Block Notification (ASL-79373)
-
Update to AUD Archive Report to correctly include Data Furnisher Authorized Name data in field versus currently populated Operator ID code (ASL-81951)
-
​Activation of new e-OSCAR Terms of Use​
Oct 9, 2025
eo2025.13
-
Release details pending
Nov 6, 2025
eo2025.14
-
Creation of optional daily email to all ACDV Responders within an organization indicating that new ACDVs have been received. This general guidance email will direct operators to log into e-OSCAR to access and respond to disputes and does not relieve Data Furnishers from their responsibility to proactively log into e-OSCAR to review ACDVs (ASL-1007)
-
Creation of optional email sent to all ACDV Responders within an organization indicating that one or more pending ACDVs will reach their Response Due Date within 5 days. This general guidance email will direct operators to regularly log into e-OSCAR to access and respond to disputes in a timely fashion, and does not relieve Data Furnishers from their responsibility to proactively log into e-OSCAR to review ACDVs (ASL-163)
-
(Services by e-OSCAR Schema Change) Addition of Notification ID field after "recordidentifier" and before "notificationType" to Block/DR Notification Services. Details to be published in SwaggerHub. We will provide backwards compatibility until May 6, 2026 (ASL-75567)​
-
(Services by e-OSCAR Schema Chage) Update to Payload Encryption schema to remove "pwObjClass" in the payload response for all API endpoints with JSON. Details to be published in SwaggerHub. We woll provide backwards compatibility until May 6, 2026 (ASL-75250)
-
Addition of ITIN as a SSN equivalent in ACDV, Reinsertion, and Dispute Response Notification transactions. ITIN will be allowed to be entered into the current SSN field in these transactions as well as within Case Search. ITIN will be captured within the SSN field in the corresponding Archives. Tool tips and error logic within the application will be updated to reflect this change. NOTE: ITIN will continue to not be allowed in AUD, AUD Notifications, Block Notifications, and Block Rescission Requests. (ASL-81010)
Dec 4, 2025
eo2025.15
-
Addition of capability to export CSV for the Operator Activity Report (ASL-69571)
-
Addition of Case ID as the last column on the ACDV, Block Notification, DR Notification, AUD Notification, and Reinsertion Activity Reports (ASL-81302)
-
Include company Registration ID on the Extract Archive Page in a similar fashion as to how it is displayed on the Schedule Archive Page (ASL-84195)