CommonRecord:CommonLine

1
CommonRecordCommonLine

• Setting the Standard

Presented by Michelle Jarzyniecki
2
Response Agenda

• Underlying Business Requirements
• Key Differences Between CommonLine and Common
  Record CommonLine
• Response Overview
• Response Formats
• Response Codes
• Response Type Codes
• Error Processing (Error Codes)
• Loan Status Process
• Response Examples
• Questions

3
Underlying BusinessRequirements

• Maintain current CommonLine functionality
• Maintain flexibility for our School customers
• Follow the Common Record direction - if possible
  - based on feedback from FAMS providers
• Collaborative Standards

4
Key Differences

• The Response business process remains the same
  however, there is a difference in the way data is
  communicated.
• The basic difference is that the information is
  contained in a new structure with new formats.

5
Key Differences
6
Key Differences
7
Introduction

• The response process provides information needed
  to verify that requests submitted were
  successfully received and/or processed.
• A Response must be sent to the entity that sent
  the original Request and it may also be sent to
  interested 3rd parties.

8
Document ID

• DocumentID does not mirror the value that was
  sent in the request document
• DocumentID for FFELP does not follow the COD
  process
• FFELP service providers can not maintain batch
  integrity on files
• There are multiple players involved in the loan
  process
• There may be multiple responses for one request

9
Response Formats

• There are 3 Response Formats now available
  Snapshot, Full, and Standard
• The ltFullResponseCodegt element may be used to
  select the format of the Response to be returned.
• Service Providers are required to support the
  Snapshot format. Other formats are optional.
• Software providers must support all 3 formats.

10
Response Formats

• Snapshot Format
• An image of the student and loan data on the
  service providers system at the time the
  response is created.
• The data in this format coincides with the
  current CommonLine response.
• Basic Response Elements
• See Response Layout for detailed requirements

11
Response Formats

• Full Format
• Data tags and values sent in the original change
  request.
• Minimal data requirements as defined in the
  response record layout
• Basic Response Elements
• Response may need to be built from the request
  file and not from the service providers system
• See Response Layout for detailed requirements

12
Response Formats

• Standard Format
• Only minimal data requirements as defined in the
  response layout.
• Basic Response Elements
• Recommended for Real-time Processing where
  request integrity can be maintained
• See Response Layout for detailed requirements

13
Response Formats

• All of the response formats contain the same
  Basic Response Elements
• ltResponsegt complex element for each major block
  included in the document
• ltResponseCodegt simple element within each
  ltResponsegt complex element
• ltEditProcessResultgt complex element within the
  ltResponsegt complex element.
• The difference among the 3 formats lies in the
  amount of data required for each.

14
Response Formats

• Response Complex Element Example
• ltResponsegt
• ltResponseCodegtRejectedlt/ResponseCodegt
• ltEditProcessResultgt
• ltResponseErrorCodegt2515lt/ResponseErrorCodegt
• ltResponseMessagegtInvalid Valuelt/ResponseMessagegt
• ltResponseErrorFieldgtSSNlt/ResponseErrorFieldgt
• ltReportedValuegt000121222lt/ReportedValuegt
• lt/EditProcessResultgt
• lt/Responsegt

15
Response Formats

• Some Response Blocks Contain Additional Response
  Elements
• Financial Data
• PLUSDebtAmount
• TotalOustandingStaffordSLSDebt
• Award
• GuaranteeDate
• Status code info (Lender, Guarantor, Prom Note
  and Credit)
• ServiceTypeCode
• CurrentGuaranteeAmount
• GuaranteeAdjustmentIndicator
• GuaranteeAmountReductionCode
• ReinstatementAvailableAmount
• ActualInterestRate
• RevisedNoticeOfGuaranteeCode
• ResponseTypeCode
• CustomExtension

16
Response Formats

• Some Response Blocks Contain Additional Response
  Elements
• FFELPLoanInformation
• ResponseToOriginator
• LenderOfLastResortIndicator
• FinancialAwardConfirmationCode
• SerialLoanActualIndicator
• Disbursement
• DisbursementNetAmount
• DisbursmentStatusCode
• DisbursmentFeeAmount
• DisbursmentFeePaid
• GuaranteeFeeAmount
• GuaranteeFeePaid

17
Response Formats

• Response Complex Element Example
• ltResponsegt
• ltResponseCodegtRejectedlt/ResponseCodegt
• ltEditProcessResultgt
• ltResponseErrorCodegt2515lt/ResponseErrorCodegt
• ltResponseMessagegtInvalid Valuelt/ResponseMessagegt
• ltResponseErrorFieldgtCreditAuthorizationIndicatorlt/
  ResponseErrorFieldgt
• ltReportedValuegtyeslt/ReportedValuegt
• lt/EditProcessResultgt
• ltPLUSDebtAmountgt5000lt/PLUSDebtAmountgt
• ltTotalOustandingStaffordSLSDebtgt5000lt/TotalOustand
  ingStaffordSLSDebtgt
• lt/Responsegt

18
Response Formats
19
Blocks
Blocks Requiring a Response Complex Element

• Attended School
• Student
• Address
• Phone
• Employment
• Financial Data

• Loan Information
• Award
• Person (Reference, Borrower, Cosigner)
• Disbursement

20
Response Codes
21
Response Codes

• Determination of the ltResponseCodegt within a block

Note Except when combined with Change Request
See Response Type Code for additional detail on
this exception.
22
Response Codes

• Examples
• 1.) Only use Accepted in the Attended School
  block.
• 2.) If all elements in the block contain good
  data except one element is invalid, use
  Rejected.
• 3.) If one element is causing the record to be
  Pending and another has invalid data, use
  Rejected.
• 4.) If all data is good, use Accepted.
• Use ltEditProcessResultgt to describe any errors.

23
Response Type Code

• ltResponseTypeCodegt is returned within the
  Response for the Award block to specify the type
  of request to which the response relates.
• Valid Values
• ResponseToLoanRequest
• ResponseToCreditRequest
• ResponseToChangeRequest
• ModificationAfterGuarantee

24
Response Type Code
25
Response Type Code

• ltResponseTypeCodegt is required regardless of the
  Response Format used
• Responses will not be sent for Demographic
  changes (address, phone or email)
• If a Change Request is received and an update
  occurred outside of the change request process
  (Modification), only one ResponseToChangeRequest
  should be sent.
• If the ltFullResponseCodegt for a Change Request is
  Standard, a Modification can not be combined
  with the response.

26
Response Type Code

• Use ModificationAfterGuarantee once a
  ltGuarantorStatusCodegt of 40 has been received
  for all subsequent unsolicited status or data
  updates
• Disbursement data or amount changes
• Loan status updates
• Hold and release instructions
• Refer to the Response Trigger Conditions table in
  the Implementation Guide for additional
  information.
• Only a single entity should transmit
  Modifications
• Lender for lender flow process
• Guarantor for guarantor flow process

27
Error Processing

• For each rejected request, the response can be
  utilized to describe all processing errors.
• ltResponseCodegt will contain a value of Rejected
• ltEditProcessResultgt complex element will be
  repeated for each error described
• In order to process a rejected Change Request,
  all detected errors must be corrected and the
  request must be submitted as a new Change
  Request.
• Error Codes for duplicate simple element
• Error Code 2366 Service Provider does not
  support the processing of this type of request.

28
Error Processing

• Simple Elements within ltEditProcessResultgt
• ltResponseErrorCodegt required element
• ltResponseMessagegt optional element
• ltResponseErrorFieldgt required element
• ltReportedValuegt conditionally required element
• Each complex element that contains its own
  response block should be processed independently.
• Errors that prevents processing can be repeated
  for the remaining response blocks.

29
Error Processing

• For a Loan Request, only the fields in error have
  to be corrected.
• For Post-guarantee Change Requests
• An attempt will be made to process all data in
  the Person and Loan Information blocks regardless
  of errors in the Award or Disbursement blocks.
• If the business function can not be determined
  based on data provided in the Award and
  Disbursement blocks, use Error Code 2513 Change
  Request does not contain minimal data elements.

30
Rejected Responses
31
Rejected Responses
32
Default Values

• Default values are used when data is required by
  the response schema, but it was not supplied in
  the request or was invalid.
• Default values should not be stored as the
  intended value for that element.
• See the table in the Response Layout section of
  the Implementation Guide under Format and Valid
  Values.

33
Default Values
34
Default Values
35
Loan Status Process Agenda

• Loan Status Rules
• Loan Status Codes
• Guarantor Status
• Lender Status
• Promissory Note Status
• Credit Status
• Examples

36
Loan Status Rules

• Status reporting is required up to and including
  first disbursement.
• Before a ltGuarantorStatusCodegt of 40, make
  pre-guarantee changes.
• After a ltGuarantorStatusCodegt of 40, make
  post-guarantee changes.
• A ltResponseTypeCodegt of ResponseToLoanRequest
  should be used to report any changes of status or
  data up to and including the initial reporting of
  ltGuarantorStatusCodegt of 40.

37
Loan Status Rules

• A ltResponseTypeCodegt of ModificationAfterGuarante
  e should be used to report any changes of status
  or data after the initial reporting of
  ltGuarantorStatusCodegt of 40 that are not in
  response to a Post-Guarantee Change Request.
• A ltResponseTypeCodegt of ResponseToChangeRequest
  should be used to report a response to
  Post-Guarantee Request.
• If both solicited and unsolicited post-guarantee
  changes occur, all of the changes should be
  rolled up and reported in a single
  ResponseToChangeRequest.

38
Guarantor Codes

• Guarantor Status Codes
• ltGuarantorStatusDateTimegt is linked with this
  element.
• Date-time stamps must be reported in Greenwich
  mean time (GMT).
• The most recent dated code should always overlay
  an older dated code. Except
• Codes 01 and 05 may be overwritten by any other
  code, regardless of the ltGuarantorStatusDateTimegt.
  
• Codes 01 may not overwrite any other code,
  regardless of the ltGuarantorStatusDateTimegt.
• Code 05 may not override any other code except
  01, 15, 25, and 30 regardless of the
  ltGuarantorStatusDateTimegt.
• Code 40 may not be overwritten by any other code,
  except 35 regardless of the ltGuarantorStatusDateTi
  megt.

39
Guarantor Codes
40
Lender Codes

• Lender Status Codes
• ltLenderStatusDateTimegt is linked with this
  element.
• Date-time stamps must be reported in Greenwich
  mean time (GMT).
• The most recent dated code should always overlay
  an older dated code. Except
• Codes 01 and 05 may be overwritten by any other
  code, regardless of the ltLenderStatusDateTimegt.
• Code 01 may be overwritten by code 05, regardless
  of the ltLenderStatusDateTimegt.
• Codes 01 and 05 may not overwrite any other code,
  regardless of the ltLenderStatusDateTimegt.
• Code 45 may not be overwritten by any other code,
  except code 30 and 3, regardless of the
  ltLenderStatusDateTimegt.

41
Lender Codes
42
Prom Note Codes

• Promissory Note Status Codes
• ltPromissoryNoteStatusDateTimegt is linked with
  this element.
• Date-time stamps must be reported in Greenwich
  mean time (GMT).
• The most recent dated code should always overlay
  an older dated code. Except
• A code may not be overwritten with a lower value
  code, regardless of the ltPromissoryNoteStatusDate
  Timegt (e.g., a value of 25 should not overlay a
  value of 40).
• Code 60 may not be overwritten by any code,
  except 50 and 55 regardless of the
  ltPromissoryNoteStatusDateTimegt.

43
Prom Note Codes
44
Prom Note Codes
45
Credit Codes

• Credit Status Codes
• ltCreditStatusDateTimegt is linked with this
  element.
• Date-time stamps must be reported in Greenwich
  mean time (GMT).
• The most recent dated code should always overlay
  an older dated code. Except
• Code 01 may not overwrite any other code,
  regardless of the ltCreditStatusDateTimegt.

46
Credit Codes
47
Loan Status Examples

• Same process used currently for CL5
• Please see Appendix G in the Implementation guide
  for detailed examples.
• Submit any questions or issues to the ESC
  committee for review.

48
Response Examples

• Switch to Word Documents
• Use Handouts

49
CRC - Response Processing
Questions?