COD Export

Use the COD Export page to create files for submission to the Common Origination and Disbursement (COD) system through EDconnect. These files contain origination and disbursement records for fund source processing.

Resolve export-related exceptions during the COD Export process. Resolve import-related exceptions through the COD Exceptions process.

The export process consists of three steps:

  1. Define the selection criteria for records to export.

  2. Select and export the records to the COD system.

  3. Review the history of exported COD batches.

Financial Aid Processes File Management

Use Processes > System Administration > Financial Aid Processes File Management to upload and download files in Azure File Storage. This functionality allows you to place files where financial aid processes, such as Application Data Import/Export, Clearinghouse, and NSLDS Reports, expect them. Refer to Financial Aid Processes File Management.

Prerequisites

Authorization:

  • Common - Processes - View

  • Financial Aid - Processes - COD Export - Export COD File

Configure campus-level security for COD Export so users see only records for their assigned campus on the History tab:

  1. In Settings > System > Campuses > Campus Groups, create or select a Campus Group containing only the campus that the user can access.

  2. In Settings > System > Staff, select the staff member and assign that Campus Group on the General tile.

You should be familiar with:

Access

Processes > Financial Aid > COD Export

Export COD Files

Process Tab

Use the Selection Criteria section on the Process tab to define the records for the COD Export file.

To prevent duplicate processing, the export process checks whether selected records are already included in a Student Review Batch.

  • You cannot queue a new batch with the same selection criteria while an existing batch is still processing.

  • If a matching batch has been gathered but not yet exported, records already in that batch are not gathered again.

Student Review Batches Tab

The Student Review Batches tab enables you to review the student records included in a temporary batch. Before creating the final batch, you can remove student records that do not need to be exported to COD.

History Tab

The History tab contains detailed information about the records included in a batch. You can review the details and decide whether to regenerate or cancel a batch.

When Enable Campus Level Security On BatchesClosed Select "Yes" if you want Anthology Student to enable campus-level security for batches based on the logged-in user’s permissions for the session default campus. The user will only be able to access batches created for campuses that they can access. If a batch has been created for multiple campuses and the user cannot access at least one of the campuses, the batch will NOT be visible to the user. If you select "No," the logged-in user can view batches from multiple campuses, even if they do not have permission to access the batch details for some students. This setting is enabled by default. A script ensures that batches on the History tab that were created before the implementation of the campus-level security are also filtered based on the new campus-level security. is turned on in Settings > System > General, the records on the History tab will be filtered based on the logged-in user and the campus groups associated with the user. Record filtering is based on the SyCampusId. Records with a NULL value in the CampusID field will be visible to all users. CampusID = NULL is assigned to records that are not in Succeeded status (e.g., Completed, Enqueued).

A clean-up script ensures that batches are also filtered if they were created before the implementation of the campus-level security feature. The script runs at the batch level per process and assigns SyCampusId values to the records in the batch.

If the feature is turned off, the History tab will load the records based on the default campus setting (Session Defaults).

 

This feature applies to U.S. compliance only.