CESP Interface Transaction Standards, Version 5.0

Disclaimer: RESP promoters

The information contained on this page is technical in nature and is intended for Registered Education Savings Plan (RESP) and Canada Education Savings Program promoters. For general information, visit the RESP section.

Official title: CESP Interface Transaction Standards, Version 5.0

Information Bulletin

Number:
CESP/PCEE-2013/14-001-527
Date:
April 15, 2013
Subject:
CESP Interface Transaction Standards, Version 5.0

Purpose

This Information Bulletin details the changes to the CESP Interface Transaction Standards (ITS) version 5.0 dated January 15, 2013 released due to the new Saskatchewan Advantage Grant for Education Savings (SAGES).

CESP ITS Version 5.0 Changes

  • Section: Background to ITS version 5.0
    • Add:
      Effective January 1, 2013, the Government of Saskatchewan will help Saskatchewan families save for their children's post-secondary education by providing a grant to a Registered Education Savings Plan (RESP) at a rate of 10% of the subscriber's annual contributions up to a maximum of $250 per child per year ($500 if carry forward room is available) and to a lifetime limit of $4,500.

      The ITS version 5.0 adds the required logic to the previous ITS to implement and administer the new Saskatchewan Advantage Grant for Education Savings (SAGES). There are two new record types: 410 (Provincial Request) and 910 (SAGES transaction processing report record), as well as additional fields added to the 400 record type layout. Refer to the appropriate sections of this document for details. All other record types remain constant.

  • Section: Transaction Type 21 CES Grant, CLB, SAGES and Alberta Grant Repayments
    • Add:
      Non-Resident to Repayment Type Field
  • Section: Record Type"410" – Provincial Request
    • Add:
      Transaction Type 30 – SAGES Request TransactionProvide the RESP details of a contribution on a Transaction Type 410-30 SAGES Request Transaction for each contribution for which SAGES is being requested. SAGES is paid on a "first come, first served" basis within a reporting period. This means that if two or more SAGES requests for the same Beneficiary are received in the same period, the first request successfully processed will be paid.

      SAGES requests do not receive payment if they have a transaction date earlier than three years when compared to the date sent in the Header Record (001) of the file or if the transaction date is more than three years from the contribution transaction date.

      Transaction Type 31 – Cancel SAGES Request TransactionUse Transaction Type 410-31 to cancel a previously paid transaction requesting SAGES. Refer to the contribution that had a successfully processed SAGES Request.

  • Section: Record Types "900" and "910" - Transaction Processing Report
    • Add:
      At the end of each processing period, the Program sends a Transaction Processing Report to the Sender with a record for every successfully processed transaction. This report contains two record types: a record type 900, and for SAGES related information, a record type 910. Each record provides detailed results of the processing of financial transactions submitted (e.g. how much grant was attracted by each contribution, Alberta Grant, CLB or SAGES request, or how much grant, bond or SAGES was repaid). The report is the Program's confirmation to the Sender that the submitted transactions were correctly formatted, contained all the mandatory information and passed all the necessary business rules. The Transaction Processing Report also lists all contract, beneficiary, and subscriber information that was successfully processed.

      The processing of a Sender's file(s) results in a series of grant/bond payments and repayments. Repayments are netted out from the payments, generally resulting in a payment to the Sender. The payment will be automatically deposited into the Sender's account according to the banking information supplied to the Program. Senders are to use the transaction processing report to update their own contract notional accounts.

      The record type 900 indicates the effect the transaction had on the payment received by the Sender. The payment requisitioned flag tells the sender if the 900 record is a payment or repayment of grant, Alberta Grant, or CLB to or from the Program. In this case the payment requisitioned flag would be set to "Yes", signifying that this transaction affects the amount paid to the Sender. In the case of an EAP, PSE contribution withdrawal, transfer or termination adjustment, there is no money moving between the promoter and the Program so the payment requisitioned flag would be set to "No" signifying that this transaction does not affect the amount paid to the Sender.

      In the case of the record type 910, the payment requisition flag is set to "Yes" if the 910 record is for a payment or repayment of SAGES or a cancellation of SAGES. When the 910 record is for the SAGES portion of an EAP, transfer or termination adjustment, there is no money moving between the promoter and the Program so the payment requisitioned flag would be set to "No". The promoter can then reconcile all transactions with the flag set against the payment received from the Program.

      Financial Transactions confirmed by record type 900

      • Contributions
      • Educational Assistance Payments
      • Post-Secondary Education (PSE) withdrawals
      • Grant Repayments
      • Transfers
      • Termination Adjustments
      • Canada Learning Bond Requests
      • Alberta Grant Requests
      • Reversals of the above financial transactions

      Financial Transactions confirmed by record type 910

      • SAGES Requests
      • Cancel SAGES Requests
      • SAGES portion of Contribution reversals
      • SAGES portion of Educational Assistance Payments
      • SAGES portion of Grant Repayments
      • SAGES portion of Transfers
      • SAGES portion of Termination Adjustments
  • Note: A single record type 910 is used to confirm a SAGES Request or Cancel SAGES Request. One record type 900 and one record type 910 are reported together for the same financial transaction for cases where the SAGESEAP Amount or SAGES Amount is greater than zero or a contribution is being reversed that was previously paid SAGES.

  • Section: 7.1 Record Type "001" – Header Record
    • Add:
      '050' to Data Version
  • Section: 7.6 Record Type "400" – Financial Transaction
    • Add:
      Added a new repayment type to the Record Type 400: 12 – Non-resident
    • New:
      Added two new fields to the Record Type 400:
      • SAGES Amount
      • SAGESEAP Amount
  • Section: 7.6.1 Type "400" Validation Rules
    • New:
      Added SAGES Amount and SAGESEAP Amount error codes:
      • 7040 - Transaction date must be on or after January 1, 2013
      • 1016 - Specimen Plan is not approved for SAGES
      • 7001 - Invalid date
      • 3099 - Amount is out of range
      • 1015 - Sender is not authorized to submit transactions with SAGES content

      Refer to Appendix E (Understanding Error Codes) of the RESP Provider User Guide for a full description of each error code.

  • Section: 7.7 Record Type "410" – Provincial Request
    • New:
      Provincial Request, Record Type 410, is used to report provincial request activity on a RESP contract. Currently, there are two transaction types of provincial request transactions reported: '30' – SAGES Request and '31' - Cancel SAGES Request.
  • Section: 7.7.1 Record Type '410-30' - SAGES Request
    • New:
      Added Record Type "410-30" – SAGES Request
  • Section: 7.7.1.1 Type "410-30" Validation Rules
    • Add:
      Added SAGES Request Transaction error codes:
      • 7005 - Data is missing from field
      • 7000 - Invalid date
      • 1004 - Transaction is for a future reporting period
      • 7040 - Transaction date must be on or after January 1, 2013
      • 2027 - Transaction date precedes beneficiary birth date
      • 7001 - Invalid value
      • 7002 - Invalid transaction type
      • 1015 - Sender is not authorized to submit transactions with SAGES content
      • 1005 - Specimen Plan does not exist
      • 7008 - Promoter is not associated with the Specimen Plan
      • 7030 - Sender not authorized to send data for the Specimen Plan
      • 7031 - Beneficiary is not associated with the Specimen Plan
      • 1016 - Specimen Plan is not approved for SAGES
      • 5031 - Contribution transaction date is later than Specimen Plan eligibility end date
      • 1010 - Contract is not Individual / Sibling only
      • 5025 - Contribution transaction has been reversed – invalid status
      • 5026 - Error in contribution transaction, current transaction cannot be processed
      • 5027 - Unable to locate the contribution transaction
      • 5034 - Date of contribution transaction must be on or after January 1, 2013
      • 7006 - Beneficiary on Contribution Transaction is invalid

      Refer to Appendix E (Understanding Error Codes) of the RESP Provider User Guide for a full description of each error code.

  • Section: 7.7.2 Record Type '410-31' – Cancel SAGES request
    • Add:

      Added Record Type '410-31' – Cancel SAGES Request

  • Section: 7.7.2.1 Type "410-31" Validation Rules
    • Add to table:
      Added Cancel SAGES Request Transaction error codes:
      • 7005 - Data is missing from field
      • 7000 - Invalid date
      • 1004 - Transaction is for a future reporting period
      • 7040 - Transaction date must be on or after January 1, 2013
      • 2027 - Transaction date precedes beneficiary birth date
      • 7001 - Invalid value
      • 7002 - Invalid transaction type
      • 1015 - Sender is not authorized to submit transactions with SAGES content.
      • 1005 - Specimen Plan does not exist
      • 7008 - Promoter is not associated with the Specimen Plan
      • 7030 - Sender not authorized to send data for the Specimen Plan
      • 7031 - Beneficiary is not associated with the Specimen Plan
      • 1016 - Specimen Plan is not approved for SAGES
      • 5031 - Contribution transaction date is later than Specimen Plan eligibility end date
      • 5025 - Contribution transaction has been reversed – invalid status
      • 5026 - Error in contribution transaction, current transaction cannot be processed
      • 5027 - Unable to locate the contribution transaction
      • 5035 - No valid SAGES request received on the contribution
      • 5036 - Valid cancel request already processed for the contribution

      Refer to Appendix E (Understanding Error Codes) of the RESP Provider User Guide for a full description of each error code.

  • Section: 7.12 Record Types "900" and "910" – Transaction Processing Report
    • New:
      Added description along with a new record type. Each transaction processed by the CES Program system is acknowledged by a Type "900" transaction processing report or in the case of SAGES, a Type "910" SAGES transaction processing report.
  • Section: Appendix A – Transaction Error Codes
    • Add to table:
      Added new SAGES error codes as previously listed in this document.
  • Section: Appendix A – Refusal Reasons
    • Add to table:
      Added new SAGES error codes as previously listed in this document.
      • O - Late SAGES request

      Refer to Appendix F (Understanding Refusal Reasons) of the RESP Provider User Guide for a full description of this refusal reason.

  • Section: Appendix D – RT400 Data Elements
    • Add to table:
      Added new SAGES error codes as previously listed in this document.
      • SAGES Amount
      • SAGESEAP Amount

Contact Us

Questions on this Information Bulletin should be directed to the Canada Education Savings Program by e-mail at cesp-pcee@hrsdc-rhdcc.gc.ca or by calling 1-888-276-3624.

Report a problem or mistake on this page
Please select all that apply:

Thank you for your help!

You will not receive a reply. For enquiries, contact us.

Date modified: