CRC Compliance Processing

1
CRC Compliance Processing
Presented by Kim Shiflette
2
Overview

• General Compliance
• Loan Request and Response
• Change Request and Response
• Disbursement Roster, Forecast, and Acknowledgement

3
General Compliance

• Organizations must support all required elements
  and processes for those documents it is
  implementing,
• Including request types which are not yet able to
  be processed by the entity.
• Compliance criteria for service providers and
  software providers differ and are explained in
  the documentation.
• Service providers must format the CRC document in
  the same format and version in which it was
  received.

4
General Compliance, cont.

• Organizations exchanging data with a fully CRC
  compliant organization can be assured that the
  data will be processed according to the standards
• Participants are required to use a NCHELP
  compliant transport protocol.
• Refer to the NCHELP Technical Manual for
  CommonLine and Common Account Maintenance
  processes for approved transport protocols.

5
General Compliance, cont.

• The current version must be supported as well as
  Commonline Release 4.
• This applies only to participants who previously
  adopted Release 4 and are now implementing CRC.
• For organizations that previously implemented
  Release 4 and Releases 5, continued support of
  both is recommended.
• If an organization receives Custom Extension
  data, that it does not support, the organization
  should ignore the data elements

6
General Compliance, cont.

• Software providers must support all basic,
  optional and additional services.
• Software providers must support all loan types
  (FFELP and alternative) in the Loan Request
  document.
• Service providers must support all FFELP loan
  types that they offer
• a reject response in the Response document for
  any loan type they do not support.
• Service providers are not required to support
  more than 4 disbursements.
• Software providers are required to support 20
  disbursements.

7
General Compliance, cont.

• Services providers must support all basic
  services. Additional Serives are optional.
• Hold/Release (error)
• Credit Processing (error)
• DisbursementDayOverride (error)
• Custom Extension (ignore)
• Netting (error)
• Response Format (ignore)

8
Loan Request and Response

• Service providers must support either guarantee
  and print and print and guarantee
• Software providers must support receiving
  responses to a Reprint request.
• Service Providers - it is optional for service
  providers to create a response to a Reprint
  request.

9
Loan Request and Response, cont.

• Service providers who process alternative loans
  must support the required data elements for their
  alternative loan programs.
• Software providers must support the all
  alternative loan data elements
• School Certification Requests are optional for
  Services Providers and Required for Software
  providers.

10
Loan Request and Response, cont.

• Reference information is optional for service
  providers and software providers to support.
• Borrower reference information can be submitted
  in the Loan Request Document.
• Reference information may be passed back in the
  Response Document.
• The receipt and delivery of email information is
  optional for service providers
• The ability to collect and distribution of email
  information is required for software providers
• E-mail information can be submitted in the Loan
  Request document and passed back in the Response
  document.

11
Change Request and Response

• Software providers are required to support the
  CRC change request routing rules to determine the
  recipient of the Change Request.
• If multiple lender guarantor combos for same
  student, and multiple loans send to most recent
  loan
• Organizations that receive post-guarantee Change
  Requests document must support the Response
  document.
• If the receiving organization cannot process the
  Change Request due to lack of authorization, the
  receiving organization should
• either forward the Change Request to the
  appropriate service provider for processing via
  the Change Request document
• or return an error message indicating they do not
  support the request.

12
Change Request and Response, cont.

• Service providers do not respond to person level
  Change Requests (address, phone and email).
• CDA may act as an intermediary between the school
  and the appropriate guarantor, lender, or service
  provider when processing change requests.

13
Response

• Service Providers must support the Snapshot
  response format
• Service Providers may optionally support the Full
  and Standard Response formats.
• Software provides must support all Response type
  formats - Snapshot, Standard and Full to be
  consider compliant.

14
Disbursement Roster, Forecast,and
Acknowledgement

• Software providers must support the Disbursement
  Roster and the Disbursement Forecast.
• Service providers must support the Disbursement
  Roster only
• support of the Disbursement Forecast is optional
  for service providers.
• CDAs must support the Disbursement Roster and the
  Disbursement Roster Acknowledgment documents.

15
Disbursement Roster, Forecast,and
Acknowledgement, cont.

• To be CRC compliant for disbursement processing,
  disbursing agents must support the following
  funds disbursement methods
• Electronic Funds Transfer (EFT)
• Individual borrower check
• Master check

16
CRC Compliance Processing
Questions?