Appendix E. Registered Education Savings Plan provider user guide – Understanding error codes

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.

On this page

Alternate format

A PDF version of the Registered Education Savings Plan provider user guide is available on the index page.

List of acronyms

BCTESG

British Columbia Training and Education Savings Grant

BN

Business number

CESG

Canada Education Savings Grant

CESP

Canada Education Savings Program

CLB

Canada Learning Bond

CRA

Canada Revenue Agency

EAP

Educational assistance payment

ESDC

Employment and Social Development Canada

ITS

Interface Transaction Standards

PCG

Primary caregiver

RESP

Registered Education Savings Plan

RT

Record type

SAGES

Saskatchewan Advantage Grant for Education Savings

SIN

Social Insurance Number

SIR

Social Insurance Registry

Introduction

The Canada Education Savings Program (CESP), within Employment and Social Development Canada (ESDC), is responsible for administering the following education savings incentives:

  • Canada Education Savings Grant (CESG)
  • Canada Learning Bond (CLB)
  • Saskatchewan Advantage Grant for Education Savings (SAGES)
  • British Columbia Training and Education Savings Grant (BCTESG)

Those are available to eligible beneficiaries of Registered Education Savings Plans (RESPs).

This appendix explains the reasons for error codes when the CESP system does not accept transactions submitted by RESP providers. It also provides information for possible means to resolve them

For more information, refer to Appendix C for a list of acronyms and terms used in this guide.

E.1.  Background information

This document provides information to assist RESP providers understand error codes. For additional technical information, consult the Interface Transaction Standards (ITS). The ITS can be downloaded from the Canada.ca/RESPresources website under the Systems Documentation tab.

E.1.1.  What is an error code

An error code is a 4 digit code, which indicates why the CESP system has not accepted a transaction sent by an RESP promoter.

E.1.2.  How are error codes reported to promoters

The CESP system reports transaction errors in monthly error report files (.err) sent to promoters. Each rejected transaction generates a corresponding record type 800 transaction that references the original promoter transaction identifier. It also generates the name of the field in error.

E.1.3.  How does an error code differ from a refusal reason

The CESP system can reject transaction. This will happen if the CESP system cannot process an RESP transaction sent by a promoter, due to an error in the transaction information. In these cases, the promoter will receive a corresponding record type 800 transaction with an error code. This will indicate why the CESP system did not process the transaction. Promoters must investigate error codes and resubmit new transactions with the corrected information.

Transactions successfully processed by the CESP system will not generate error codes. However, a processed transaction will receive a refusal reason if the CESP does not pay the full amount of grant or bond.

E.1.4.  Using this document

This document lists:

  • error codes
  • the corresponding ITS description, and
  • explanations

E.2.  Error codes

E.2.1.  1004 – Transaction is for a future reporting period

Error code 1004: The CESP system generates this error code when the transaction date reported in a record type (RT) is for a future reporting period. This applies to:

  • RT 100
  • RT 200
  • RT 400
  • RT 410
  • RT 411
  • RT 511

The transaction date refers to the date on which the transaction occurred between the subscriber and the promoter.

Resolution: Promoters report all transactions in a reporting period following the end of the period in which the transaction occurred. Reporting periods extend from the first day of the month to the last day of the same month. Promoters have 4 business days after the reporting period ends to finalize their files. Promoters should not submit transactions with a transaction date following the last day of the reporting period.

Should there be system related problems; the promoter is to contact the CESP directly.

E.2.2.  1005 – Specimen plan does not exist

Error code 1005: The CESP system generates this error code when the promoter submits a specimen plan ID that does not exist in the CESP System. This error code applies to:

  • RT 100
  • RT 200
  • RT 400
  • RT 410
  • RT 411
  • RT 511

Resolution: Promoters should first verify the specimen plan ID submitted to the program before the CESP system processes any transactions.

E.2.3.  1007 – Specimen plan is not approved for CESG

Error code 1007: The CESP system generates this error code when the Canada Revenue Agency (CRA) did not approve the specimen plan for the CESG. The CRA must approve the specimen plan for CESG if:

  • transaction type is 11 or 14
  • transaction type is 13 and educational assistance payment (EAP) grant amount is greater than 0
  • transaction type is 19, 21, 22, or 23 and grant amount is greater than 0

Resolution: The CESP system will only accept specimen plans that CRA has approved. When a promoter secures a new specimen plan ID from the CRA, the promoter should contact CESP as soon as possible. This will allow the CESP to update the database accordingly prior to any processing of transactions under the new specimen plan ID.

E.2.4.  1008 – Specimen plan is not approved for CLB

Error code 1008: The CESP system generates this error code when the CRA did not approve the specimen plan for CLB. The CRA must approve the specimen plan for CLB if:

  • transaction type is 13 and EAP CLB amount is greater than 0
  • transaction type is 19, 21, 22, or 23 and CLB amount is greater than 0
  • transaction type is 24

Resolution: The CESP system will only accept in their database specimen plans that CRA has approved. When a promoter secures a new specimen plan ID from the CRA, the promoter should contact CESP as soon as possible. This will allow the CESP to update the database accordingly prior to any processing of transactions under the new specimen plan ID.

E.2.5.  1010 – Contract is not individual/sibling only

Error 1010: The CESP system generates this error code when a contract is not “individual/sibling only”. This only applies to the following record type:

  • RT 400‑24
  • RT 410‑30
  • RT 411‑40
  • RT 511‑12

Resolution: The promoter should submit/resubmit the RT 100 for these contracts with an individual/sibling only flag of “1” to the program. If the promoter never submitted the RT 100 to the CESP system, they can use the contract creation date as the contract transaction date. This can be done as long as, the contract held an individual sibling only status upon account creation. If the promoter already submitted an RT 100, the resubmission of this contract record with the individual/sibling only flag of “1” requires a current version status. The contract date that the promoter will use should be greater or equal to the date previously reported. This will allow the contract record to obtain a current version status. The promoter can then resubmit all financial transactions that previously received error code 1010 along with the RT 100 resubmission(s). Note that financial transactions with a transaction date that precedes its associated contract transaction date will not qualify for payment.

E.2.6.  1011 – Sender is not authorized to submit transactions with CESG content

Error code 1011: The CESP system will generate this error code because senders must be authorized to submit transactions with CESG content if:

  • transaction type is 11 or 14
  • transaction type is 19, 21, 22, or 23 and grant amount is greater than 0
  • transaction type is 13 and EAP grant amount is greater than 0

Resolution: To become authorized, the promoter must meet the requirements of a qualification process. Once complete, the CESP will add them to the CESP system. The promoter must then pass industry testing with an overall success rate of 90% or greater before submitting files for processing. A service provider could send files on behalf of multiple promoters. In that case, each one of those senders must pass industry testing with their own data.

E.2.7.  1012 – Sender is not authorized to submit transactions with CLB content

Error code 1012: The CESP system will generate this error code because sender must be authorized to submit transactions with CLB content if:

  • transaction type is 24
  • transaction type is 19, 21, 22, or 23 and CLB amount is greater than 0
  • transaction type is 13 and CLB EAP amount is greater than 0

Resolution: To become authorized, the promoter must meet the requirements of a qualification process. Once complete, the CESP will add them to the CESP system. The promoter must then pass industry testing. They need an overall success rate of 90% or greater before submitting files for processing. A service provider could send files on behalf of multiple promoters. In that case, each one of those senders must pass industry testing with their own data.

E.2.8.  1013 – Sender is not authorized to submit transactions with Alberta grant content

Error code 1013: The CESP system will generate this error because sender must be authorized to submit transactions with Alberta grant content if transaction type is 25.

Resolution: Alberta grant requests and Alberta grant request reversals are no longer accepted by the CESP system.

E.2.9.  1014 – Sender is not authorized to submit transactions with Additional CESG content

Error code 1014: The CESP system will generate this error because sender must be authorized to submit transactions with Additional CESG content if:

  • transaction type is 11 and primary caregiver (PCG)/spouse is present
  • transaction type is 11 and PCG/spouse given name is present
  • transaction type is 11 and PCG/spouse surname is present
  • transaction type is 11 and PCG/spouse type is present
  • transaction type is 12

Resolution: To become authorized, the promoter must meet the requirements of a qualification process. Once complete, the CESP will add them to the CESP system. The promoter must then pass industry testing. They need an overall success rate of 90% or greater before submitting files for processing. A service provider could send files on behalf of multiple promoters. In that case, each one of those senders must pass industry testing with their own data.

E.2.10.  1015 – Sender is not authorized to submit transactions with SAGES content

Error code 1015: The CESP system will generate this error code because senders must be authorized to submit transactions with SAGES content if:

  • transaction type is 30 or 31
  • transaction type is 19, 21, 22, or 23 and SAGES amount is greater than 0
  • transaction type is 13 and EAP SAGES amount is greater than 0

Resolution: The CESP will only accept approved specimen plans in their database. When a promoter either secures a new specimen plan ID or amends an existing specimen plan with the CRA, the promoter should contact CESP as soon as possible. This will allow the CESP to update the database accordingly prior to any processing of transactions under the new or amended specimen plan ID.

E.2.11.  1016 – Specimen plan is not approved for SAGES

Error code 1016: The CESP system will generate this error code when the CRA has not approved the specimen plan for SAGES. The CRA must approve the specimen plan for SAGES if the following transactions are being submitted for processing:

  • transaction type 30 or 31
  • transaction type 13 and EAP SAGES amount is greater than 0
  • transaction type 19, 21, 22 or 23 and SAGES amount is greater than 0

Resolution: The CESP will only accept approved specimen plans in their database. When a promoter secures a new specimen plan ID from the CRA, the promoter should contact CESP as soon as possible. This will allow the CESP to update the database accordingly prior to any processing of transactions under the new specimen plan ID.

E.2.12.  1017 – Sender is not authorized to submit transactions with BCTESG content

Error code 1017: The CESP system will generate this error code because senders must be authorized to submit transactions with BCTESG content if:

  • transaction type is 40 or 41
  • transaction type is 19, 21, 22, or 23 and BCTESG amount is greater than 0
  • transaction type is 13 and EAP BCTESG amount is greater than 0

Resolution: The CESP will only accept approved specimen plans in their database. When a promoter either secures a new specimen plan ID or amends an existing specimen plan with the CRA, the promoter should contact CESP as soon as possible. This will allow the CESP to update the database accordingly prior to any processing of transactions under the new or amended specimen plan ID.

E.2.13.  1018 – Specimen plan is not approved for BCTESG

Error code 1018: The CESP system will generate this error code when the specimen plan has not been approved for BCTESG. The CRA must approve the specimen plan for BCTESG if the following transactions are being submitted for processing:

  • transaction type 40 or 41
  • transaction type 13 and EAP BCTESG amount is greater than 0
  • transaction type 19, 21, 22 or 23 and BCTESG amount is greater than 0

Resolution: The CESP will only accept approved specimen plans in their database. When a promoter secures a new specimen plan ID from the CRA, the promoter should contact CESP as soon as possible. This will allow the CESP to update their database accordingly prior to any processing of transactions under the new specimen plan ID.

E.2.14.  2027 – Transaction date precedes beneficiary birth date

Error code 2027: The CESP system will generate this error code on:

  • RT 200‑03
  • RT 400
  • RT 410
  • RT 411
  • RT 511

For RT 400, this will apply specifically to transaction types 11, 13, 14, 24 and 21 if the CLB amount is greater than 0. The transaction date represents the date the activity (financial or other) occurred between the promoter and the subscriber of the RESP.

Resolution: The transaction date must be on or subsequent to the beneficiary’s date of birth. The promoter should correct the transaction date and resubmit the transaction.

E.2.15.  2033 – Transaction date must be before beneficiary’s 21st birthday

Error code 2033: The CESP system will generate this error code because the transaction date must be before beneficiary’s 21st birthday. This applies if the transaction type is 24.

Resolution: When transaction type is 24, the transaction date must be before the beneficiary’s 21st birthday. The promoter should correct the transaction date and resubmit the transaction.

E.2.16.  3006 – Amount must be greater than 0

Error code 3006: The CESP system will generate this error code on RT 400. In transaction types 11‑Contribution, 13‑EAP and 14‑Post‑secondary education (PSE) Contribution Withdrawal. The contribution amount, EAP amount, and PSE amount must be a numeric value from 0.01 to 9,999,999.99.

Resolution: The amount indicated in the contribution, the EAP or the PSE contribution withdrawal fields must be a number between 0.01 and 9,999,999.99. The promoter should correct the amount and resubmit the transaction.

E.2.17.  3099– Amount is out of range

Error code 3099: The CESP system will generate this error code on RT 400. Specifically on the grant amount, EAP grant amount, CLB amount and CLB EAP amount fields.

CLB amount – If the promoter enters an amount, dollar value must be 0.00 to 20,000 if transaction type = 19, 23 or 22.

CLB amount – If the promoter enters amount, dollar value must be 0.00 to 5,000.00 if transaction type = 21.

CLB EAP amount – If the promoter enters an amount, dollar value must be 0.00 to 5000.00 if transaction type = 13.

When the following fields are mandatory, they must be populated with a numerical value from 0.00 to 9,999,999.99:

  • grant amount
  • EAP grant amount
  • SAGES amount
  • SAGES EAP amount fields
  • BCTESG amount, and
  • BCTESG EAP amount

Resolution: For transaction types 19, 22 or 23, the CLB amount must be between 0.00 and 20,000.00. For transaction type 21, the CLB amount must be between 0.00 and 5,000.00. For transaction type 13, the CLB EAP amount must be between 0.00 and 5,000.00. Grant amounts, EAP grant amounts, SAGES amounts, SAGES EAP amounts, BCTESG amounts and BCTESG EAP amounts must be between 0.00 and 9,999,999.99 when mandatory. The promoter should correct the amount in error and resubmit the transaction.

E.2.18.  5025 – Contribution transaction has been reversed – invalid status

Error code 5025: The CESP system will generate this error code because the contribution the promoter is referring to has been reversed.

Resolution: The CESP system cannot process this transaction.

E.2.19.  5026 – Error in contribution transaction, current transaction cannot be processed

Error code 5026: The CESP system will generate this error code because of an error in the contribution transaction. This means that the CESP system cannot process the transaction referring to the contribution.

Resolution: The promoter must correct the error in the contribution transaction before they submit an updated transaction.

E.2.20.  5027 – Unable to locate the contribution transaction

Error code 5027: The CESP system will generate this error code when a transaction refers to a contribution that is not found in the CESP system.

Resolution: If the contribution transaction does not exist in the system, it is not possible to process a transaction that refers to the contribution.

E.2.21.  5028 – Date of contribution transaction must be later than December 31, 2004

Error code 5028: Date of contribution transaction must be later than December 31, 2004.

Resolution: The contribution transaction date must be later than December 31, 2004. The promoter must correct the date and resubmit.

E.2.22.  5029 – PCG/spouse information is same as in contribution transaction received in the same period – No processing performed

Error code 5029: PCG/spouse information is same as in contribution transaction received in the same period – No processing performed.

Resolution: The following fields must be different for the system accepts the transaction:

  • promoter business number (BN)
  • specimen plan ID
  • contract ID
  • PCG/spouse
  • PCG/spouse given name
  • PCG/spouse surname
  • PCG/spouse type

E.2.23.  5030 – Contribution transaction did not request grant

Error code 5030: In order to request Additional CESG, the original contribution transaction (RT 400‑11) must request grant.

Resolution: The original contribution transaction must request CESG. The promoter must correct and resubmit.

E.2.24.  5031 – Contribution transaction date is later than specimen plan eligibility end date

Error code 5031: The contribution transaction date must be earlier than the specimen plan eligibility end date.

Resolution: The promoter must correct the contribution transaction date and resubmit.

E.2.25.  5032 – A more recent PCG/spouse information transaction is already associated to the contribution

Error code 5032: A more recent PCG/spouse information transaction is already associated to the contribution.

Resolution: Additional CESG transactions could receive a refusal reason of I, L or M. If that is the case, the PCG/spouse information should be updated (through another RT 511) by using a later date than the previously submitted RT 511. If Additional CESG refusal reason is 4, the PCG should correct the beneficiary information at the CRA. You can refer to the “beneficiary matching report for refusal reason 4” for unmatched fields. Once that is done, you can submit the RT 511 (with same PCG/spouse information) with a later date than the previously submitted RT 511.

E.2.26.  5033 – Late contribution transaction

Error code 5033: The promoter is submitting a RT for a RT 400‑11 transaction that is no longer eligible for additional grant due to 3‑year rule. The transaction date of the RT 400‑11 and file sent date of the RT 511 exceed 36 months.

Resolution: There can be no more than 36 months between the RT 400‑11 transaction date and the RT 511 sent date. The promoter must correct and resubmit.

E.2.27.  5034 – Date of contribution transaction must be later than December 31, 2012

Error code 5034: Date of contribution transaction must be later than December 31, 2012 to receive SAGES.

Resolution: The contribution transaction date must be on or after January 1, 2013.

E.2.28.  5035 – No valid SAGES request received on the contribution

Error code 5035: The CESP system received a transaction to cancel a SAGES request. However, the original SAGES request transaction (RT 410‑30) did not request SAGES.

Resolution: If the intent was to request SAGES, resubmit the contribution with this request.

E.2.29.  5036 – Valid cancel request already processed for the contribution

Error code 5036: The CESP system received a cancel SAGES request transaction (RT 410‑31) for a transaction that is already cancelled.

Resolution: Confirm the status of the original SAGES transaction prior to submitting a RT 410‑31.

E.2.30. 6000 – Physical file name does not correspond to file name in header record

Error code 6000: The CESP system will generate this error code when a discrepancy occurs. The discrepancy is between the file name sent by the promoter and the header record within the file. As outlined in the ITS, the physical naming of a file must follow the proceeding format:

Header to CESP: 001 + sender business number (BN) + date sent + sender file number

For further information on file naming conventions, we recommend that you refer to the File naming standards section of the ITS

The combination of sender BN, date sent and file number must match in both the file name and the header record.

Please contact the CESP directly for any systems problems relating to the structure of files and records.

Resolution: The physical file name and the header record (the first record in the file) must be the same. This is excluding the file type in the header record. The promoter must correct and resubmit.

E.2.31.  6001 – Incorrect format of physical file name

Error code 6001: The CESP system will generate this error code for an incorrect file name. This will occur when the physical file name does not adhere to the file naming standard outlined in the File naming standards section of the ITS. The physical file name must be displayed to CESP in the format as follows:

File type + sender BN + date sent + sender file number

The file type is a single uppercase character that indicates the type of file the promoter is submitting:

  • P = Production data file
  • S = Summary reporting file
  • T = Test data file
  • Z = Test summary reporting file

The promoter BN must be a 15 character alphanumeric field.

The date sent format is: YYYYMMDD.

The file number is a 2 digit number assigned by the sender to distinguish between multiple files sent to CESP on the same day. If the sender sends 1 file in a day, he must still use a file number. The file number does not need to follow a strict sequence.

Resolution: The physical file name must adhere to the file naming standard. The promoter must rename the file and resubmit.

E.2.32.  6002 – Duplicate record with same file name found in database

Error code 6002: The combination of sender BN, date sent and sender file number submitted by the sender must be unique. The CESP system will reject a file when it has already received and processed the same combination. A promoter can repeat a file number, providing the date sent is different. Additionally, the sender can submit 2 or more files on the same day and with the same date sent. However, each file needs to have its own unique file number.

Resolution: File names must be unique. The promoter must rename the file per the file naming standard while making sure that it has its own unique number and resubmit.

E.2.33.  6003 – No header record

Error code 6003: The CESP system will generate this error code when it receives a file without a header record (RT 001). The header record is mandatory to identify the source of a transaction file. Should there be any system related problems in regards to generating a proper header record the sender/promoter is to contact CESP immediately.

Resolution: The promoter must include a header record in the file. The promoter must add a header record and resubmit.

E.2.34.  6005 – Too many header records in 1 file

Error code 6005: The CESP system will generate this error code when the promoter submits more than one RT 001 in 1 file. Each file must have 1 and only 1 RT 001.

Resolution: The promoter must eliminate the surplus header record and resubmit the file.

E.2.35.  6006 – This BN is not authorized to send files

Error code 6006: The CESP system will generate this error code when there is an issue with the sender BN. This occurs when the CESP system does not recognize the sender BN referenced in the record system as being authorized to send files. The sender BN is a 15 character alphanumeric identifier unique to each promoter conducting business with CESP.

To become authorized, the promoter must meet the requirements of a qualification process and the CESP must add them to the CESP system. The promoter must then pass industry testing with an overall success rate of 90% or greater before submitting files for processing. A service provider could send files on behalf of multiple promoters. In that case, each one of those senders must pass industry testing with their own data.

Resolution: Verify that the promoter uses the appropriate BN. If it is indeed a new BN that and the CESP system did not test it, the promoter must contact the CESP to begin industry testing.

E.2.36.  6010 – Record count does not match the number of records in file

Error code 6010: The CESP system will generate this error code when there is an issue with the record count. This happens when the number of records in a file does not match the record count as submitted in the RT 999‑Trailer record. The trailer record is also referred to as the transaction control count. It must include in its record count the total number of transactions (RT 100, RT 200, RT 400, RT 410, RT 411 etc.), including the header, sub‑header and trailer record.

Resolution: The number of records in the file must be the same as the record count in the trailer record. The promoter must correct and resubmit.

E.2.37.  6011 – Too many trailer records in file

Error code 6011: The CESP system will generate this error code when the promoter submits more than one RT 999 in a file. Each file must have one, and only one, RT 999.

Resolution: The promoter must eliminate the surplus trailer record and resubmit the file.

E.2.38.  6012 – No trailer records in file

Error code 6012: The CESP system will generate this error code when a promoter submits a file without a trailer record (RT 999). The trailer record is mandatory in each file submitted by the sender. We use it to provide CESP and the promoter’s system with a control count of the number of records in each file.

Resolution: The promoter must include a trailer record in the file. The promoter must add a trailer record and resubmit.

E.2.39.  6014 – The data version in header does not match the current version

Error code 6014: The CESP system will generate this error code when the data version in the file is not the current version. The data version is a mandatory field of the header record (RT 001). It must be populated with the current version number of the ITS in order for the CESP system to process it successfully.

Resolution: The data version indicated in the file must be the most current version of the ITS. The promoter must correct and resubmit.

E.2.40.  6015 – Trailer record not last in file

Error code 6015: The CESP system will generate this error code when there is another character or transaction found after the trailer record (RT 999). The RT 999 must be the last record in each file. It must also contain an accurate control count or the CESP system will reject the file.

Resolution: The trailer record must be the last record in the file. The promoter must delete all additional spaces or characters that may be after the trailer record and resubmit.

E.2.41.  6016 – Header record not the first record in the file

Error code 6016: The CESP system will generate this error code when there is another character or transaction found before the header record (RT 001). The RT 001 must be the first record in each file or the CESP system will reject the file.

Resolution: The header record must be the first record in the file. The promoter must delete all additional spaces or characters that may be before the header record and resubmit.

E.2.42.  7000 – Invalid date

Error code 7000: Error code 7000 is most commonly generated for one of the following reasons:

  1. the date field in error is not submitted in a valid date format. This applies to:
    • RT 100
    • RT 200
    • RT 400
    • RT 410
    • RT 411
    • RT 511
  2. the year of birth submitted does not match the year of birth already established for the beneficiary in the CESP system for the beneficiary

If the CESP system generates this error, it will not send the beneficiary information to the Social Insurance Registry (SIR) for validation.

Please note that for an error code 7000, the CESP system will not populate the 5 SIR fields in the record type 900‑Transaction error report. This is because the CESP system rejects the transaction before it is sent to SIR for validation.

Resolution:

  1. the CESP system requires that all dates be formatted YYYYMMDD, numerals only without delimiters such as spaces or punctuations. The promoter needs to ensure the date they submit is formatted as outlined in the File naming standards section of the ITS
  2. if the birth date format is correct, the promoter should verify the birth date on their records. They should contact the custodial parent and/or subscriber of the RESP. Should the custodial parent and/or subscriber confirm the date of birth is accurate, the promoter should direct him/her to contact the SIR

An error code 7000received on an RT 200‑03 beneficiary information transaction should be perceived as similar to an error code 7006‑Invalid SIN. The year of birth that the promoter is submitting does not correspond with the year of birth already validated by SIR.

The CESP system will not send the remaining 4 fields (given name, surname, sex, and SIN) to SIR for validation. Therefore, the CESP recommend advising the subscriber/custodial parent that they should verify all 5 fields.

There are a very small number of 7000 errors received on the RT 200‑03 that require manual intervention on the part of the program. Your promoter support officer is responsible to review monthly any “potential” manual fixes for your company. However, should you have concern that a 7000 error received requires manual intervention, please contact your promoter support officer.

E.2.43.  7001 – Invalid value

Error code 7001: Informs promoters that a transaction used an invalid value. This is a common error when promoters submit a financial transaction (RT 400). This happens when they use a beneficiary SIN that is not currently established in the CESP system. A beneficiary SIN would not be established in the CESP system for the following reasons:

  1. the promoter never submitted the RT 200‑03 beneficiary information transaction
  2. the promoter did submit the RT 200‑03 beneficiary information transaction but the CESP system rejected it with an error code
  3. the beneficiary SIN is no longer valid in the CESP system

Resolution:

  1. if you have not submitted a RT 200‑03 Beneficiary information transaction:
    • please submit a RT 200‑03 in the following production run. The promoter can submit the financials in the same month for processing
  2. if you have submitted a RT 200‑03 beneficiary information transaction and received an error code:
    • check the error reports returned by the CESP to verify why the RT 200‑03 did not process successfully. The error report will provide the error that the CESP system generated on the RT 200‑03, as well as the field that was in error. The promoter should correct this error and resubmit the RT 200‑03. The promoter can then resubmit the financial transactions (RT 400) for processing in the same file as the correct RT 200‑03
  3. if you have already successfully submitted a RT 200‑03 beneficiary information transaction:
    • the CESP validates, on a monthly basis, the usability of the SIN for all beneficiaries already established in the system. The SIN validation report (RT 920) notifies promoters when beneficiaries have SIN issues. There could be instances in which a permanent SIN replaces an expired 900 series SIN. Since there was a change to the beneficiary SIN information, the beneficiary SIN in the CESP system will become a linked SIN. This will show as a SIN Issue 3 in RT 920 and the CESP system will reject financial transactions (RT 400) that the promoter submits using the original SIN. The promoter will receive an error code 7001 on the report. The promoter must submit a new RT 200‑03 beneficiary information transaction to the CESP with the updated beneficiary SIN. He must then resubmit all financial transactions (RT 400) rejected with an error code 7001

Note: The CESP system could also send this error code when it receives a new SAGES request during the SAGES suspension period. This would occur for a contribution that previously had a successfully processed SAGES request.

  • Resolution: The CESP wants to make sure that eligible SAGES amount already received in an RESP remain in that RESP. To do so, effective as of the February 2018 processing period, the CESP system will reject all SAGES requests submitted for contributions that previously had a successfully processed SAGES request. This will apply during the SAGES suspension period.

E.2.44.  7002 – Invalid transaction type

Error code 7002: The CESP system will generate this error code on:

  • RT 100
  • RT 200
  • RT 400
  • RT 410
  • RT 411
  • RT 511

It will occur when the transaction type referenced in the record is not supported by the CESP system or is not valid for the given record type.

Resolution: Only use valid transaction types as per ITS. The promoter must correct and resubmit.

E.2.45.  7005 – Data is missing from field

Error code 7005: The CESP system will generate this error code when data is missing from a mandatory field. When submitting a record to CESP, all mandatory fields, as per the ITS, must be filled. This applies to the following:

  • RT 001
  • RT 100
  • RT 200
  • RT 400
  • RT 410
  • RT 411
  • RT 511
  • RT 999

Please refer to the Interface Transaction Standards document to identify mandatory fields for each RT. Should the promoter leave any mandatory fields empty, the transaction will reject.

Resolution: Ensure that you populate all mandatory fields before submitting transactions to the CESP system.

E.2.46.  7006 – Invalid SIN

  1. Error code 7006: the CESP system commonly generate this error code on RT 200‑03 “Beneficiary Information”. This occurs when the information in one or more of the 5 fields that the promoter submits does not match what SIR has on file. The 5 fields verified with SIR are: SIN, given name, surname, sex, and date of birth. The CESP system will note any and all fields that the SIR rejects in the error report returned to the promoter by the CESP
  2. The CESP system will also return an “invalid SIN” error if the beneficiary’s SIN is not numerically valid. ESDC uses a mathematical formula to determine the validity of the composition of a SIN. This occurs before the CESP system sends the beneficiary’s information to SIR. Therefore, if the “invalid SIN” error is due to the SIN not being numerically valid, no information will appear in the 5 fields returned in the error report
  3. A promoter may receive an error code 7006 – invalid SIN even though all 5 fields are designated with a “1” – passed SIR validation. This situation may occur where there was a change to a SIN or the SIN was linked to another SIN at SIR

Resolution: 1 and 2. Determine which field is in error and verify the information with the subscriber of the RESP. The promoter would know which fields are in error by looking in the error report. Should the subscriber confirm that the information is correct; the promoter should refer the subscriber to SIR.

Please note that SIR will only discuss information held in their database with the beneficiary’s custodial parent. Once the custodial parent corrects the information, the promoter should resubmit the transaction.

  1. Where the promoter receives an error code 7006 – invalid SIN, but all 5 fields are designated with a “1” – passed SIR validation, the promoter should contact the subscriber and/or custodial parent. He would need to verify if the beneficiary’s SIN has changed for any reason since initially provided. Should the subscriber/custodial parent confirm that they have changed the beneficiary’s SIN, the promoter must submit a new RT 200‑03 – beneficiary information. He must submit the information with the new SIN for each contract and specimen plan held for that beneficiary

The promoter should also contact the CESP to advise that a new SIN is being submitted for the beneficiary. They could then discuss any further transactions that they may need to submit to update the beneficiary’s accounts.

E.2.47.  7008 – Promoter is not associated with the specimen plan

Error code 7008: The CESP system will generate this error code on:

  • RT 100
  • RT 200
  • RT 400
  • RT 410
  • RT 411
  • RT 511

It will happen in situation where the CESP system does not recognize the specimen plan ID referenced as belonging to the promoter.

The specimen plan ID is a numeric identifier assigned to the promoter by the CRA.
To become authorized, the promoter must meet the requirements of a qualification process and the CESP must add them to the CESP system database.

The promoter must then pass industry testing with an overall success rate of 90% or greater before submitting files for processing. A service provider could send files on behalf of multiple promoters. In that case, each one of those promoters must pass industry testing with their own data.

Resolution: If the promoter indicated the specimen plan in error, the promoter must correct and resubmit. If the specimen plan is new to the promoter, the promoter must contact CESP to initiate industry testing.

E.2.48.  7017 – Date of financial transaction must be later than December 31, 1997

Error code 7017: The CESP system will generate this error code on RT 400 with a transaction date that is prior to 1998. The CESP was announced in the February 1998 Budget and only maintains records of RESP activity that occurred on or after January 1, 1998.

Resolution: The transaction date must be after December 31, 1997. The promoter must correct and resubmit.

E.2.49.  7018 – Date is earlier than original transaction date

Error code 7018: The CESP system will generate this error code on an RT 400. This will happen when the transaction date of the RT 400 reversal is prior to the date of the original transaction. The transaction date must be on or after the original transaction date if the reversal flag = 2.

Resolution: Ensure that the date of the transaction you intend to reverse is on or after the transaction date of the original transaction.

E.2.50.  7020 – Error in original transaction, current transaction cannot be processed

Error code 7020: The CESP system will generate this error code on financial transaction. This situation will happen when the promoter attempts to submit reversals for financial transactions that the CESP system did not process successfully. The CESP system did not process successfully the RT 400 “Original promoter transaction ID” field that the promoter is referencing to in the RT 400 reversal.

Resolution: Verify that the CESP system did process the original promoter transaction ID you wish to reverse.

E.2.51.  7021 – Original transaction and its reversal were found in the same processing period – No processing performed

Error code 7021: The CESP system will generate this error code when the promoter submits a reversal and its’ original transaction in the same processing period. The CESP supports corrections to financial transactions (RT 400) by submitting a transaction to reverse the original transaction. The promoter then needs to resubmit another transaction with the corrected information. The reversal transaction indicates that the transaction and amounts reported did not actually occur as reported. A reversal transaction must always include the promoter BN and transaction ID from the original RT 400 transaction that they want to reverse. If the promoter submits the original transaction and the reversal in the same processing period, the system will reject both and no processing will occur.

Resolution: No processing occurs when the system generates this error. In that case, promoters need only to submit a transaction with the correct information in the following production run.

E.2.52.  7022 – Unable to locate the original transaction

Error code 7022: The CESP system will generate this error code on transaction ID. This will happen when the CESP system cannot match or find the original promoter transaction ID that the promoter refers to in a reversal. This occurrence is commonly due to the promoter never submitting an original transaction or the CESP system rejecting it.

The CESP system supports corrections to RT 400‑Financial transactions by submitting a transaction to reverse the original transaction. The promoter must then resubmit another transaction with the corrected information. A reversal indicates that the transaction and amounts reported did not actually occur as reported. A reversal transaction must always include the promoter BN and transaction ID from the original RT 400 transaction the promoter wants to reverse.

Resolution: Verify the original promoter transaction ID and original promoter BN that the promoter referred to in the reversal. Ensure that the CESP system has received and successfully processed the original transaction.

E.2.53.  7023 – The status of the original transaction is invalid

Error code 7023: The CESP system will generated this error code when the original promoter transaction ID is not in “processed” status. To process a reversal, the original transaction must have a “processed” status in the CESP system. If the original transaction has already been reversed, the subsequent reversal will raise error code 7023. The CESP system supports corrections to RT 400‑Financial transactions by submitting a transaction to reverse the original transaction. The promoter must then resubmit the corrected information. A reversal indicates that the transaction and amounts reported did not actually occur as reported. A reversal transaction must always reference the original RT 400 transaction that the promoter wishes to reverse. The promoter will do so by referencing the promoter BN and transaction ID that appears on the original transaction.

Resolution: The promoter will confirm the status of the original transaction that they intend to reverse before submitting a transaction reversal.

E.2.54.  7030 – Sender not authorized to send data for the specimen plan

Error code 7030: The CESP system will generate this error code in relation to a sender’s BN. This happens when a sender BN specified in the header record is not authorized to send data pertaining to that specimen plan ID. The specimen plan ID is a numeric identifier assigned to the promoter by the CRA.

Resolution: To become authorized, the sender/promoter must meet the requirements of a qualification process and the CESP must add them to the CESP system. The sender must then pass industry testing with an overall success rate of 90% or greater before submitting files for processing. A service provider could send files on behalf of multiple promoters In that case, each one of those promoters must pass industry testing with their own data.

E.2.55.  7031 – Beneficiary is not associated with the specimen plan

Error code 7031: The CESP system will generate this error code on:

  • RT 400
  • RT 410
  • RT 411
  • RT 511

This will happen when the CESP system is unable to process one of those records because the beneficiary his not associated with the specimen plan identified in the specimen plan ID field of the transaction. The beneficiary would not be associated with the specimen for any of the following reasons:

  1. the promoter did not submit the RT 200‑03 Beneficiary information transaction
  2. the promoter did submit the RT 200‑03 Beneficiary information transaction but it was rejected for an error
  3. the promoter did submit the RT 200‑03 Beneficiary information. The CESP system did process the transaction. However, the specimen plan ID given in the RT 400 did not correspond with the specimen plan ID in the RT 200‑03

Resolution: If you have not submitted an RT 200‑Beneficiary information:

  1. please submit an RT 200‑03 in the following production run. You can submit the financials in the same month for processing

If you have submitted an RT 200‑03 Beneficiary information transaction:

  1. check the error reports returned by the CESP system to verify why the RT 200‑03 did not process successfully. The error report will provide the error on the RT 200‑03, as well as the field that was in error. The promoter should correct this error and resubmit the RT 200‑03. The promoter can then submit the financials for processing
  2. check the processing reports returned by the CESP system to verify the specimen plan ID given in the RT 200‑03 beneficiary information transaction. Ensure that this specimen plan ID corresponds with the specimen plan ID submitted in the RT 400

E.2.56.  7032 – Beneficiary is not associated to a CLB account

Error code 7032: The CESP system will generate this error code on RT 400. This error is in relation to transaction type 13, 19, 21, 22, and 23. A request for CLB amount or CLB EAP amount is made and the beneficiary does not have a CLB account.

Resolution: The beneficiary must have a CLB account. The promoter must correct and resubmit.

E.2.57.  7033 – The SIN or BN is not numerically valid

Error code 7033: Occurs when the SIN or BN is not numerically valid. ESDC uses a mathematical formula to determine the validity of the composition of a SIN. This occurs before the CESP system sends the beneficiary’s information to SIR.

Resolution: Resubmit transaction with an accurate SIN or BN.

E.2.58.  7034 – Transaction date must be on or after January 1, 2004

Error code 7034: The CESP system will generate this error code if:

  • the transaction date is before January 1, 2004 if the transaction type is 24
  • the transaction date is before January 1, 2004 if transaction type is 19, 21, 22 or 23 and CLB amount is greater than 0
  • the transaction date is before January 1, 2004 if transaction type is 13 and CLB EAP amount is greater than 0

Resolution: The transaction date must be on or after January 1, 2004. The promoter must correct and resubmit.

E.2.59.  7035 – Transaction date must be on or after January 1, 2005

Error code 7035: The CESP system will generate this error code on a record type and transaction type 511‑12. This will happen when the transaction date is before January 1, 2005.

Resolution: The transaction date must be on or after January 1, 2005. The promoter must correct and resubmit.

E.2.60.  7036 – Must be 0 or blank if transaction type 21 and repayment reason is 1

Error code 7036: The CESP system will generate this error code for a transaction type 21. This will occur when the repayment reason = 1 and a non‑zero amount is provided for any of the following fields:

  • CLB amount
  • BCTESG amount

Resolution: The CLB amount and BCTESG amount must be 0 or blank when transaction type is 21 and repayment reason is 1. The promoter must correct and resubmit.

E.2.61.  7037 – Date of birth is prior to January 1, 2004

Error code 7037: The CESP starting offering the CLB incentives only in January 2004. Beneficiary date of birth must be on or after January 1, 2004 in order to be eligible for CLB.

Resolution: The transaction date must be on or after January 1, 2004. The promoter must correct and resubmit.

E.2.62.  7039 – Transaction date is earlier than contribution transaction date

Error code 7039: The CESP system will generate this error code on an RT 511‑12. This occurs when the transaction date in the RT 511‑12 is not equal to or greater than the transaction date in the original RT 400‑11 transaction.

Note: If the RT 511‑12 is an update, the transaction date should be later than the transaction date used in the previously submitted 511‑12.

Resolution: The RT 511‑12 transaction date must be equal or later than the original RT 400‑11 transaction date. The promoter must correct and resubmit.

E.2.63.  7040 – Transaction date must be on or after January 1, 2013

Error code 7040: The CESP system will generate this error code on SAGES request transactions. This occurs when the date of the SAGES request transaction is before January 1, 2013.

Resolution: The transaction date must be on or after January 1, 2013. Correct and resubmit the transaction if required.

E.2.64.  7041 – Transaction date must be on or after August 15, 2015

Error code 7041: The CESP system will generate this error code on BCTESG request transactions. This occurs when the date of the BCTESG request transaction is before August 15, 2015.

Resolution: The transaction date must be on or after August 15, 2015. Correct and resubmit the transaction if required.

E.2.65.  7042 – Beneficiary date of birth must be on or after January 1, 2006.

Error code 7042: The CESP system will generate this error code if the beneficiary date of birth is before January 1, 2006.

Resolution: The promoter must confirm the date of birth of the beneficiary requesting BCTESG.

Page details

Date modified: