Support of COD reporting for enrollment status data

This feature introduces support for 2026-27 COD reporting requirements related to Loan Limit Exception processing, including Enrollment Status Effective Date reporting and Enrollment Status updates effective June 28, 2026. Oracle derives the COD Enrollment Status Effective Date from SAFI program start data by default and supports OB3 document overrides and manual updates so schools can manage withdrawals, re-entry scenarios, and other institution-specific reporting needs.

This enhancement adds support for:

Reporting the new COD <EnrollmentStatusEffectiveDate> tag for Direct Loan disbursements which represents the most recent enrollment date for the program
- COD requires this disbursement-level value for Direct Loan disbursements beginning with the 2026-27 award year. It remains optional for maintenance activity.
- The reported Enrollment Status Effective Date should be the most recent enrollment date associated with CIP Code 1.
- Schools are not expected to update all disbursements for loans originated before this release, but this value may still need to be reported if the Loan Limit Exception was not identified correctly under the logic delivered in April.
- COD continues to apply the Loan Limit Exception when the new loan has an EDD, or an EDD and Award Begin Date for Grad PLUS, before July 1, 2026.
- For loans with an EDD, or an EDD and Award Begin Date for Grad PLUS, on or after July 1, 2026, COD evaluates Enrollment Status Effective Date as follows:
  - If the Enrollment Status Effective Date is on or after July 1, 2026, the Loan Limit Exception is not applied.
  - If the Enrollment Status Effective Date is before July 1, 2026, COD reviews the student's prior loans from award years 2017-18 through the current award year.
  - If the student has an applicable undergraduate or graduate loan for the same school, program, and/or credential level in the most recent award year, the Loan Limit Exception is applied.
  - If the student does not have an applicable prior loan, the Loan Limit Exception is not applied.
Maintaining an updated <EnrollmentStatusEffectiveDate> tag when a student withdraws and re-enters their program.
Reporting new COD <EnrollmentStatus> tag values for Direct Loans.
- Report W for withdrawn students.
- Report A for Leave of Absence periods longer than 180 days.
- ED has stated that receipt of either value breaks the Loan Limit Exception for the student and causes the new loan limits to apply.
Deprecating <ProgramAttendanceBeginDate> reporting as this will no longer preserve the loan limit exception for articulation-agreement transfer scenarios.
- If reported, it will not reject, but COD will no longer use it for that purpose.

For Enrollment Status Effective Date reporting, Oracle derives the <EnrollmentStatusEffectiveDate> tag via the following rules:

By default, the <EnrollmentStatusEffectiveDate> is based on the student’s original program start date in the SAFI, unless a user provides an updated value for COD reporting via the OB3 Document (See Delivered Baseline Logic below for baseline rules).

For Enrollment Status reporting, if a disbursement has not yet been disbursed, Oracle now supports:

W values when the student’s SAFI Program Enrollment Status = W
A values when the SAFI Program Enrollment Status = A and the SAFI Enrollment Status Effective Date is at least 180 days in the past
If a disbursement has already been disbursed, Oracle retains the previously accepted COD enrollment status value that was sent for that disbursement at the time it was disbursed.

Updates to Awarding Override Criteria configuration:

You will now be able to set "COD Enrollment Status Effective Date" within the Awarding_Override_Criteria configuration script
- See the attached SFA 26.4.2 Configuration Updates (New Config) and SFA 26.4.2 Configuration Scripting API on Cloud Customer Connect for full details about updated bindings.

Baseline configuration:

Oracle provides baseline configuration to help institutions implement this feature for reporting new enrollment status data to COD.
- OB3 Document: Used to bring in data available within your SIS per program to determine additional loan limit eligibility and will now include COD Enrollment Status Effective Date Override data.
  - COD Enrollment Status Effective Date Override should represent the students' original enrollment date in the reported program, or the student's re-enrollment date after a withdrawal or qualifying break in that same program.
  - This field should be set if the program start date sent in the SAFI is not the correct date to send to COD.
- Awarding Override Criteria:
  - If the OB3InterimException document includes the new metadata "COD Enrollment Status Effective Date Override" field provided with a value, then the "COD Enrollment Status Effective Date" is set equal to that metadata field value
  - Otherwise, the "COD Enrollment Status Effective Date" will be set equal to the Program Start Date received in the student's SAFI.
- Review the related information within SFA 26.4.2 Configuration Updates (Updates to Baseline Config) attached to the release notes post on Cloud Customer Connect to understand the delivered configuration changes and determine whether refinements are needed for your implementation.

UI Improvements:

All places where Program Attendance Begin Date is displayed, the field has been renamed to COD Enrollment Status Effective Date
Add/Edit Functionality (Editable Fields)
- Navigation: Packaging > Add/Edit > Direct Loan
- Within the Add/Edit popup, users with "Package Fund Edit" can make manual adjustments to key data for Direct Loans:
  - New editable field for COD Enrollment Status Effective Date available for all Direct Loan types: Users can adjust the COD Enrollment Status Effective Date for each Academic Year.
  - Value Range: Accepts a date, and can be left blank.
  - Defaulting: If not specifically edited and saved, the system will automatically default to the value set in configuration if available.
  - Scope: Editing is available for both term-based and non-term programs.
  - Validation: Invalid entries will trigger clear validation errors to prompt user correction before submission.
  - Editing the Enrollment Status Effective Date value does not automatically adjust the Loan Limit Exception or calculated award amount; instead, it updates the value submitted to COD.

Reporting Improvements:

The existing Program Attendance Begin Date fund output field is replaced by the COD Enrollment Status Effective date field in the reporting and extract views.

Business benefit: This enhancement helps schools remain compliant with COD reporting requirements for Direct Loans beginning with the COD June 28, 2026 update. It supports accurate Loan Limit Exception processing, reduces the risk of sending incorrect enrollment status data to COD, and provides a controlled correction path for customer edge cases without disrupting existing integration behavior.

Steps to enable and configure

Use the Opt In UI to enable this feature. For instructions, refer to the Optional Uptake of New Features section of this document.

Offering: Student Financial Aid

Update Configuration Scripts:

Review baseline configuration for setting the COD Enrollment Status Effective Date posted on Cloud Customer Connect, and update your configuration if needed.
- To get started, ensure that "Configuration Administration" Permission is enabled and download your existing configuration from Oracle Student Financial Aid within Administration > Configuration Administration > Download.
- This configuration will include the pre-populated system data, which you can then update as needed.
  - DOCUMENTS.csv
    - Add a row for the new OB3InterimException document for the 2026-27 Award Year (if you have not already added this document with the Loan Limit Exception Management feature delivered in 26B)
  - DOCMETDATA.csv
    - Add metadata fields for COD Enrollment Status Effective Date Override if needed to provide a corrected COD <EnrollmentStatusEffectiveDate> value.
  - FAS_FUND_CONFIG.csv
    - Edit the Awarding_Override_Criteria Groovy configuration script for the 2026-27 Award Year referencing baseline logic and adjusting based on your institutional policy.
- Once your configuration is set, navigate to Administration > Configuration Administration, and upload your zipped configuration.

Review Downstream Reporting and Integrations:

Validate any downstream reporting, integrations, or customer documentation that reference the old Program Attendance Begin Date naming.

Repackage Students:

After successful testing in non-production, load your updated configuration to production, then repackage impacted students to adjust funding as needed.
- Divide your bulk repackaging operation into manageable groups, taking into consideration processing windows, communication needs, and the availability of supporting resources. This approach will help ensure you are prepared to support students whose awards may change as a result of the repackaging process.

Tips and considerations

Logic Customization Needed: Review your configuration after export and determine whether updates are needed for the OB3 document and for how the new COD Enrollment Status Effective Date document metadata is used in Award Overriding Criteria.
Repurposed Reporting Field: The existing fund output and reporting field Program Attendance Begin Date is repurposed and renamed to CODEnrollmentStatusEffectiveDate.
Configuration Scripting API: The existing binding name for Program Attendance Begin Date is renamed to CodEnrollmentStatusEffectiveDate.
Leave of Absence Data Matters: Maintain Leave of Absence data accurately including what the Enrollment Status Effective Date is set to in the SAFI so Oracle can determine when the COD Enrollment Status of A should be reported.
Manual Updates Are Available: Users with Package Fund Edit permission can manually update COD Enrollment Status Effective Date values in Packaging > Add/Edit > Direct Loan.

Key resources

Refer to the following Department of Education documentation:
Review related posts on Cloud Customer Connect:
- Discussion on OBBB May 13th Office Hours

Access requirements

No new access requirements.