Language selection

Government of Canada / Gouvernement du Canada

Search

Appendix A. Understanding RDSP error codes

Disclaimer: RDSP issuers

The information contained on this page is technical in nature. The target audience are issuers of the:

  • Registered Disability Savings Plan (RDSP)
  • Canada Disability Savings Grant (CDSG)
  • Canada Disability Savings Bond (CDSB)

For general information, visit the RDSP page.

On this page

Alternate formats

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

List of acronyms
BN
Business number
CDSB
Canada Disability Savings Bond
CDSG
Canada Disability Savings Grant
CDSP
Canada Disability Savings Program
CRA
Canada Revenue Agency
DAP
Disability assistance payment
DTC
Disability Tax Credit
ESDC
Employment and Social Development Canada
FMV
Fair market value
ITS
Interface transaction standards
LDAP
Lifetime disability assistance payment
ODI
Office for Disability Issues
PA
Privacy Act
RDSP
Registered Disability Savings Plan
RESP
Registered Education Savings Plan
RPD
Registered Plans Directorate
RT
Record type
SDSP
Specified Disability Savings Plan
SIN
Social insurance number
SIR
Social insurance registry
TT
Transaction type

Introduction

Employment and Social Development Canada (ESDC) is responsible for the administration of the:

  • Canada Disability Savings Grant (CDSG) (grant)
  • Canada Disability Savings Bond (CDSB) (bond)

The Canada Disability Savings Program (CDSP) system provides the delivery mechanism and necessary system supports for the effective administration of the grant and bond.

A.1 Error codes

This section explains error codes generated in response to transactions rejected by the CDSP system and provides guidance on how to resolve them.

For additional technical information, consult the Interface Transaction Standards (ITS).

A.1.1 What is an error code

An error code is a 4-digit code indicating why the CDSP system has rejected a transaction.

A.1.1.1 How to report error codes

The CDSP system reports rejected transactions in the monthly error report file (. err).

Each rejected transaction generates one or more corresponding record type (RT) 801 transactions (error file). These transactions reference the original transaction identifier along with the name of the field in error.

A.1.1.2 How does an error code differ from a refusal reason

If the CDSP system cannot process a Registered Disability Savings Plan (RDSP) transaction due to an error(s) in the transaction information, the CDSP system will reject the transaction. In these cases, a corresponding RT 801 transaction with an error code indicating why the CDSP system did not process the transaction is provided. The error(s) must be investigated, and the transaction resubmitted with the corrected information if applicable.

A refusal reason is generated for a processed transaction that is requesting an incentive but has been refused grant or bond for a particular reason. Refusal reasons are reported in the RT 901 transaction (the transaction processing file).

A.1.1.3 Using this section

This section includes the following information:

  • error codes
  • ITS description for each error code
  • detailed explanation for each error code
  • how to resolve or better understand what caused the error
  • a referral to an appropriate point of contact for situations where further investigation may be required to resolve the issue

The points of contact referred to in this section are:

  • Client Services: 1-866-204-0357
  • Canada Revenue Agency (CRA), Registered Plans Directorate (RPD):
    • 1-800-267-3100 English
    • 1-800-267-5565 French

A.1.2 Error code explanation

Table 1: Error codes
Error codes Record type Explanation Resolution
Duplicate issuer transaction number 1 All transactions submitted to the CDSP must contain a unique issuer transaction number for a single issuer. This is because identical issuer transaction numbers cannot exist in the CDSP system, such transactions cannot be processed. Provide a unique transaction number that was not previously submitted.
Invalid RT/transaction type (TT) 2 The RT or the TT is invalid. Review the transaction file and ensure the RT or TT match those defined in the ITS.
Issuer transaction number not provided 3 The issuer transaction number has not been provided. Verify that a unique issuer transaction number is provided in all submitted records.
Issuer business number (BN) is not 15 characters 4 The issuer BN included in a transaction record is not 15 characters long. Ensure that all BNs within submitted transaction records contain 15 alpha-numeric characters.
Physical file name does not correspond to file name in header record 8000 As part of the formatting guidelines provided in the ITS, the combination of authorized agent BN, date sent, and file number must match in both the: physical file name and the file's header record (001). Contact the CDSP for any system problem relating to the structure of files or records. Ensure that both the physical file name and the file name found in the file's header are identical. Refer to section 6.8 of the ITS for information on file naming standards.
Incorrect format of physical file name 8001 The submitted physical file name is incorrectly formatted. Ensure that the physical file name is correctly formatted and contains 36 characters. Refer to section 6.8 of the ITS for information on file naming standards.
Duplicate record with same file name found in the CDSP system 8002 A file with the same BN, transactions latest month, date sent, and file number already exists in the CDSP system. Review the file name and ensure the combination of BN, transactions latest month, date sent, and file number is unique.
Header record not the first record in the file 8003 There is another character or transaction found before the header record (RT 001). The header record must be the first record in each file. Delete all additional spaces or characters that may appear before the header record and resubmit.
No header record 8004 The file does not contain a header record (RT 001). Ensure that the file begins with a header record.
Too many header records in the file 8005 Multiple header records (RT 001) are present in a transaction file. All files processed by the CDSP must contain a single header record. Ensure that only one header record beginning with 001 exists in the transaction file.
This BN is not authorized to send files or is not associated to a specimen plan 8006 The BN included in the header record is not authorized to send files to the CDSP or is not associated to a specimen plan. Ensure that the BN in the header record is the correct BN for the financial organization authorized to send files to the CDSP. If the BN that was originally submitted was correct, contact Issuer Support for further assistance.
The data version in the header does not match the current version of the ITS 8007 The data version information included in the header record (RT 001) does not match data versions compatible with the current version of the ITS. Ensure that the data version included in the header record matches the current version of the ITS.
Record count does not match the number of records in the file 8008 The record count indicated in the trailer record (RT 999) does not match the number of records in the transaction file. Ensure that the record count indicated in the trailer record matches the actual record count. Refer to section 12 of the ITS for information about trailer record formatting standards.
Too many trailer records in file 8009 Multiple trailer records (RT 999) are present in a transaction file. Ensure that only one record beginning with 999 is present in the file.
No trailer records in file 8010 The issuer submitted a transaction file that does not contain trailer record (RT 999). Ensure that a trailer record is present within the transaction file and that it is the last record in the file.
Trailer record not last in file 8011 The issuer submitted a file with a trailer record (RT 999) that is not the last record within the transaction file. The trailer record must make up the last line within the transaction file. Ensure that the trailer record is the last in the record sequence of the transaction file and that there are no other records beginning with 999 in the file.
Program identifier must be CDSP 8012 The program identifier in the header record (RT 001) is not CDSP. Ensure that the program identifier is CDSP in the transaction file's header record.
The transactions latest month must be on or before the current month 8013 The transaction's latest month is not on or before the current reporting period set by the CDSP. Ensure that the transaction's latest month component of the physical file name is on or before the month following the current reporting period set by the CDSP. For example, the transaction's latest month cannot be in a future reporting period. Refer to section 6.8 of the ITS for more information about physical file name formatting standards.
Invalid date 8100 A date in the transaction file does not conform to the YYYYMMDD format. Review the file and ensure that the format YYYYMMDD is used for all dates.
Invalid value 8101 An invalid value was detected in a record submitted to the CDSP. Example, the gender value must be ‘1', ‘2', ‘3' or ‘4' (as per the ITS) but the record contains the value ‘5' at the character position assigned to the gender field. Ensure that all data provided conforms to formatting guidelines stated in the ITS.
Is not identified in the CDSP system 8102 A field in a record cannot be matched with existing data in the CDSP system. This error code applies to most transaction records that require matching with data associated to an existing RDSP contract. This error code may affect the following fields:
  • issuer's BN
  • specimen plan
  • social insurance number (SIN) information for holders and beneficiaries
  • contract number
 Review the transaction and ensure that the data corresponds to data previously validated by the CDSP for the concerned RDSP. If unsure about the data registered in the system, contact Issuer Support.
Data is missing from field 8104 Data is missing in a mandatory field. Ensure that the mandatory fields were completed for each transaction and that the data complies with the formatting guidelines provided in the ITS for the transaction.
Invalid SIN 8105 The SIN information submitted did not pass validation requirements. Ensure that the SIN is corrected and matches the SIN provided by the client(s). In addition to the SIN itself, the following information associated with the submitted SIN must match the records held by the social insurance registry (SIR):
  • given name
  • surname
  • date of birth
  • gender
Refer to the error report RT 801 for information on which SIN field has caused the error. If necessary, contact the client(s) to validate the information that they provided. If the data originally submitted appears to be correct, refer the client(s) to the SIR so they can verify what information they hold.
Amount must be greater than $0 8106 A dollar amount is not greater than zero within the following TT:
  • contribution or grant request (RT 401-01)
  • retirement savings rollover (RT 401-08)
  • education savings rollover (RT 401-30)
 Ensure that fields containing dollar amounts are greater than zero.
Amount must be greater than or equal to $0 8108 A dollar amount is negative on the following TT:
  • correction of contribution or grant request (RT 401-02)
  • repayment of grant or bond (RT 401-10)
  • Disability Assistance Payment (DAP) (RT 401-20)
  • Lifetime Disability Assistance Payment (LDAP) (RT 401-21)
  • monthly reporting (RT 701-01), applies to fair market value (FMV) amount field only
  • transfer reporting (RT 701-02), applies to FMV Amount field only
 Ensure that fields containing dollar amounts are equal to or greater than zero.
Amount must be greater than or equal to $1 8109 The total LDAP amount on the LDAP TT (RT 401-21) is less than one dollar. Ensure that the total LDAP amount field includes a value that is greater than or equal to one dollar.
Sum of reported amounts must be greater than $0 8110 The sum of all amounts reported on the repayment of grant or bond TT (RT 401-10) is not greater than zero. This sum may include:
  • grant repayment amount
  • bond repayment amount
  • grant termination adjustment amount
  • bond termination adjustment amount
 Ensure that the sum is greater than zero.
Grant must have been previously paid 8111 No grant was previously paid to a beneficiary. Also, a repayment of grant or a grant termination adjustment is being reported on the repayment of grant or bond TT (RT 401-10). Repayment of grant and grant termination adjustment transactions can only be processed if they correspond to amounts of grant that were previously paid into an RDSP. Determine if grant was previously paid to the beneficiary. If not, no further action is required as there is no grant to repay or adjust. If grant does appear to have been previously paid, contact Issuer Support
Bond must have been previously paid 8112 A repayment of bond or a bond termination adjustment is being reported on a repayment of grant or bond transaction (RT 401-10). However, no bond was previously paid to the beneficiary. Repayment of bond and bond termination adjustment transactions can only be processed if they correspond to amounts of bond that was previously paid into an RDSP. Determine if bond was previously paid for the concerned RDSP. If not, no further action is required as there is no bond to repay or adjust. If bond does appear to have been previously paid, contact Issuer Support.
Date must be on or after July 1, 2011 8113 The LDAP and DAP or retirement savings rollover date is before July 1, 2011. This code applies to the following TT:
  • retirement savings rollover (RT 401-08)
  • DAP (RT 401-20)
  • LDAP (RT 401-21)
 For the above transactions ensure the date reported is on or after July 1, 2011.
Date must be on or after December 1, 2008 8200 The date on the following transactions must be on or after December 1, 2008:
  • RDSP contract registration (RT 101-01), applies to the contract signature date field only
  • contribution or grant request as well as bond payment request (RT 401-01 and 401-05), applies to the contribution date and bond request date fields
  • repayment of grant or bond as well as reverse repayment of grant or bond (RT 401-10 and RT 401-11), applies to the repayment date and reverse repayment date fields
  • DAP as well as LDAP (RT 401-20 and 401-21), applies to the DAP date and LDAP date fields
  • DAP reversal as well as LDAP reversal (RT 401-22 and 401-23), applies to the DAP reversal date and LDAP reversal date fields
  • monthly reporting and transfer reporting (RT 701-01 and 701-02), applies to the reporting date field
 Ensure that the date(s) are on or after December 1, 2008.
Date is of a future reporting period 8201 The date reported in a transaction is for a future reporting period. Ensure that date provided is on or before the current reporting period end date set by the CDSP.
Date must be on or after beneficiary's date of birth 8203 The date information submitted in a transaction is before the beneficiary's date of birth. Ensure that the dates provided on the applicable transaction are on or after the beneficiary's date of birth.
Date must be on or before December 31 of the year in which the beneficiary turns 49 8204 The bond request date field of a bond payment request (RT 401-05) includes a date that is after December 31 of the year in which the beneficiary turns 49 years of age. For example, if the beneficiary turns 49 on June 12, 2012, the date submitted must be on or prior to December 31, 2012. Ensure that the bond request date provided is on or prior to December 31 of the year in which the beneficiary turns 49.
Date must be on or after contract signature date 8206 The transaction contains a date that is before the RDSP's contract signature date. Refer to the ITS for a complete list of applicable fields. Ensure that the date provided is on or after the contract signature date. If clarification is needed regarding the contract signature date reported to the CDSP, contact Issuer Support. If there is reason to believe, the submitted date does not precede the contract signature date, contact Issuer Support for assistance.
Date must be within issuer approval dates 8207 The date information submitted to the CDSP does not occur within the Issuer Agreement and Issuer Cessation dates. Refer to the ITS for a complete list of applicable fields. The CDSP cannot process transactions dated before the issuer's approval start date. This ensures the issuer was authorized to report at that time. In some cases, issuers have also been assigned a cessation date which indicates when they are no longer authorized to submit transactions. Ensure that transaction dates occur within the issuer agreement and cessation dates. Contact Issuer Support for further clarification on an issuer's authorized date range.
Must be on or after the bond request date 8208 The stop request date of a stop bond request (RT 401-06) precedes the original bond request date. A request to stop bond payments must occur after a bond request is successfully processed by the CDSP. Review prior RDSP bond activity dates. Ensure that the date included in stop request date field for the stop bond request transaction(s) (RT 401-06) is on or after the original bond request date.
Specimen plan must be valid 8220 A specimen plan identified in a record is not valid. Ensure that the specimen plan data submitted matches the specimen plan identifier for that RDSP. If there are no errors in the specimen plan identifier, contact Issuer Support.
Authorized agent not authorized to send data for the specimen plan 8221 The authorized agent is not authorized to send data for the indicated Specimen Plan. Examine the header record for the transaction and ensure that the authorized agent number indicated is without errors and matches the relevant authorized agent. If the authorized agent number appears to be correct, contact Issuer Support to clarify the authorized agent's status.
Specimen plan must be associated with the issuer 8222 The specimen plan identifiers submitted to the CDSP are not associated with the issuer BN indicated in the transaction. Consult the ITS for the applicable transactions and fields. Ensure that the specimen plan or BN submitted match the specimen plan identifier for that applicable RDSP. If both specimen plan and issuer BN data appear to be correct, contact Issuer Support.
Contracts must not already be a contract that is registered, closed, de-registered or nullified 8230 A contract registration transaction package (RT 101-01, RT 102-02 and RT 101-03) is submitted for a contract that already exists. Ensure that the contract registration records refer to the correct contract number for the concerned RDSP. If the contract number/specimen plan combination appears to be correct and there is no knowledge of prior activity for the affected contract, contact Issuer Support.
The beneficiary must not already have a pending, registered or de-registered contract 8231 This error applies when a contract registration transaction package (RT 101-01, RT 102-02, and RT 101-03) is submitted for a beneficiary. The beneficiary must already be associated with an existing RDSP that has a status of pending, registered, or de-registered. It also applies to an attempt to initiate a transfer of an existing RDSP. However, the transfer indicator is not set to "Y" (Yes) in the contract registration transaction package. Only one RDSP contract can exist for each eligible beneficiary. Review the transaction and ensure that the contract registration transactions refer to the correct contract number for the concerned RDSP. If the intent were to initiate a transfer, ensure that the transfer indicator is set to "Y". If the contract-related data is correct, contact the holder to find out whether RDSP activity has occurred for the affected beneficiary with another financial organization. Any other existing contract must be closed to register a new contract.
The contract signature date cannot change once a contract status is pending 8233 A contract registration transaction package (RT 101-01, RT 101-02 and RT 101-03) has been received for a contract which currently has a status of "pending". Also, the contract signature date is different than the one indicated in the original contract registration transaction package. Ensure that the "contract signature date" field is correct. If the contract signature date has been changed intentionally due to a new contract being signed by the holder(s), close the existing pending contract. Submit a new contract registration transaction package with a new contract number in the subsequent CDSP processing period.
The other contract must be associated with the beneficiary and other specimen plan and must be pending, registered, de-registered or closed 8234 The transfer indicator is set to "Y" on a contract information component of a contract registration transaction (RT 101-01) and one of the following is true:
  • the other contract is not associated with the beneficiary reported in this contract registration transaction package
  • the other contract is not associated with the other specimen plan
  • the other contract has a status other than pending, registered, de-registered or closed
 Ensure the other contract and other specimen plan match each other and are associated to the beneficiary of the contract.
Contract is not currently associated with the specimen plan 8235 The contract number is not associated with the specimen plan identified within that record and is applicable to the following:
  • another transaction was submitted before a contract registration package for a beneficiary
  • the contract registration transaction was rejected due to errors
  • the contract and specimen plan reported on a transaction do not match
Refer to the ITS for applicable transactions.		 Ensure there are no errors in the specimen plan submitted to the CDSP. Check that the contract was not already submitted and the error report (RT 801) to determine whether it was rejected in error. If the specimen plan appears to be correct for that contract, contact Issuer Support.
Contract is not currently associated to the beneficiary 8236 The RDSP contract on a transaction is not associated to the beneficiary SIN reported on the same transaction. Refer to the ITS for applicable transactions. Verify the contract number and beneficiary SIN data submitted to the CDSP. If there are no errors, contact Issuer Support.
Contract must be currently associated to the holder 8237 The holder information in the transaction does not match the holder information for that contract. This error applies to the update holder information (RT 201-03) and remove holder from contract (RT 201-23) transactions. Correct any mismatches for the contract number and holder SIN data and ensure that the contract number field was not blank in the original transaction record(s).
Contract registration transaction is missing a component 8238 The contract registration transaction package does not include a contract component (RT 101-01), or a beneficiary component (RT 101-02) or a holder component (RT 101-03). Ensure that the contract registration transaction package contains all 3 RTs and resubmit if required.
Duplicate contract registration in the same period 8239 Multiple contract information transactions (RT 101-01) indicating duplicate specimen plan and contract number data are received in the same processing period. Only one contract registration transaction for a contract and specimen plan can be submitted in a single processing period. If duplicate contract registration transactions are submitted in the same period, one will receive this error and the other will be processed. Note, if both contract registration transaction packages indicated identical beneficiary SIN data, error code 8240 would be generated. Check the error report (RT 801) or the contract status report (RT 951) to determine the status of the processed transaction. Contact Issuer Support to investigate further or for assistance.
Only one contract registration request for the beneficiary in a given period is permitted 8240 2 contract registration transaction packages (RT 101-01, RT 101-02, and RT 101-03) that contain the same beneficiary SIN data are received during the same processing period. Since only one RDSP can exist for each eligible beneficiary, this creates a conflict. If duplicate contract registration transactions are submitted in the same period, one will receive this error and the other will be processed. Check the error report (RT 801) or the contract status report (RT 951) to determine the status of the processed transaction. Ensure that the beneficiary does not have an RDSP with another financial organization.
Contract must currently have a status of registered 8241 One of the following transactions has been received for a contract that is not registered:
  • update beneficiary (RT 201-02)
  • update holder (RT 201-03)
  • add holder (RT 201-13)
  • remove holder (RT 201-23)
  • monthly reporting (RT 701-01)
 If the contract status is pending submit a new contract registration transaction package (RT 101-01, RT 101-02, and RT 101-03) with updated information. To clarify the current status of the contract, contact Issuer Support.
Must be the same as reported on the original contribution 8242 The contribution date in the correction of contribution/grant request transaction (RT 401-02) does not match the original contribution date previously submitted. For example, a July 10, 2010, contribution date is indicated in the RT 401-02 transaction and the original contribution date reported on the contribution is July 1, 2010. Review any correction of contribution/grant request transactions and make corrections to the correction date field as needed.
Grant requested may only change from "No" to "Yes" 8243 The grant requested field in the correction of contribution or grant request transaction (RT 401-02) is set to "N". This occurs when the original contribution had the grant requested field set to "Y". Review the current RT 401-02 record and correct the grant requested field (transaction position 88) to "Y" so that it is consistent with the original contribution data. If the intention were to reverse (wholly or partially) a prior contribution and grant payment by changing the grant requested field to "N" in the correction transaction. Submit a RT 401-02 record with the new contribution information along with a repayment transaction (RT 401-10) indicating the amount of grant to repay to the CDSP.
Must be on or after the original contribution date 8244 The date indicated in the correction date field of the correction of contribution or grant request transaction (RT 401-02) is prior to the date of the original contribution being corrected. Corrections must be dated after the original contribution. Ensure that the date indicated in the correction date field of the correction of contribution or grant request transaction (RT 401-02) is on or after that of the original transaction. Contact Issuer Support for clarification of original transaction dates.
Contract already exists in CDSP system 8245 The contract number being submitted via the RT 102-11 already exists for that specimen plan. Can't have 2 contracts in the CDSP database associated to the same contract number/specimen plan combination. Ensure that a unique contract number is chosen when submitting an RT 102-11 transaction.
Contract must already be a contract that is registered, de-registered or pending 8246 The FI submits a close contract transaction (RT 102-10) for a contract that is not currently “registered”, “de-registered” or “pending”. Verify if the close contract transaction was submitted in error or contact Issuer Support to clarify the status of the contract.
Contract must already be a contract that is “registered”, “closed”, or “pending”. 8247 A rename contract transaction (RT 102-11) has been received for a contract that has a status other than registered, closed or pending. Verify if the rename contract transaction was submitted in error or contact Issuer Support to clarify the status of the contract.
Contract is already associated to the holder 8248 An add holder to contract transaction (RT 201-13) has been received for a contract to which the holder is already associated. Verify that the SIN and name fields are for a new holder and are not already associated to the applicable contract.
Cannot remove the last holder on the contract 8249 A transaction includes a request to remove the only holder (RT 201-23) associated to an RDSP. An RDSP must have at least one active holder. Verify that all holders that have requested to be associated to the RDSP have been reported to the CDSP. If a holder were not previously associated to the RDSP due to an error, they would need to be added before a request to remove another holder can be processed.
The SIN or BN is not numerically valid 8250 A SIN reported for either a beneficiary, a holder, or the BN reported for an agency is not numerically valid. Check the SIN against the RDSP application or validate the SIN with the applicable individual. Make the correction and then re-submit the transaction.
Beneficiary year of birth cannot be modified 8251 The beneficiary component of contract registration package (RT 101-02) or an update beneficiary transaction (RT 201-02) was received. The year of birth provided is different from the year originally submitted for the beneficiary. Confirm the year of birth and correct the transaction if required. Note, that the original year of birth submitted would have been validated by the SIR. If the birth year already submitted is inaccurate, contact Issuer Support.
Contract already associated to another beneficiary SIN 8252 The beneficiary component of a contract registration transaction package (RT 101-02) has been received. The SIN provided does not match the beneficiary SIN already associated with this contract. Only one contract can exist per beneficiary. Verify the beneficiary SIN and correct the error(s) if needed. If there has been a change to the beneficiary's SIN, ensure that the new SIN is being reported.
There must not already be a contract awaiting transfer in the CDSP system for the beneficiary 8253 A contract registration transaction package (RT 101-01, 101-02 and 101-03) has been received with a "Y" in the transfer indicator field of the RT 101-01. A contract already exists with a status of registered, pending or de-registered and a transfer indicator of "Y" for the same beneficiary. Only one transfer request can be processed at a time for a beneficiary. Enquire about other potential RDSP transfers with the applicable holder(s) or beneficiary. If a transfer is no longer required, advise the holder(s) to communicate with the other financial organization. This will allow a close contract transaction (RT 102-10) to be submitted in lieu of the original transfer request.
Conflicting contract transactions pertaining to the same contract received in the period 8254 Multiple, conflicting contract transactions are submitted in the same period creating duplicate contract names:
  • 2 unique rename contract transactions (RT 102-11) in the same processing period and for the same contract present in the CDSP database
  • 2 unique rename contract transactions (RT 102-11) requesting to rename 2 separate contracts to the same new contract name
  • a contract registration transaction package (RT 101-01, 101-02 and101-03) and a close contract transaction (RT 102-10) for the same contract in the same period
  • a contract registration transaction package (RT 101-01, 101-02 and 101-03) and a rename contract transaction (102-11) for the same contract in the same period
 For the two scenarios involving conflicting rename contract transactions, ensure that the contract name being used in the transaction is accurate and make corrections if needed. If two rename contract transactions were submitted, resubmitting one will suffice to successfully complete the renaming. For the scenarios involving a close contract or rename contract transaction received during the same period as a contract registration transaction, verify whether the close contract or rename contract transactions were submitted in error. If so, no further action is needed. If the intent was to close or rename the contract, resubmit the close contract or rename contract transactions for the following processing period.
Contract must not be nullified 8255 A transaction cannot be processed because the contract status is nullified. Register a new contract or contact Issuer Support for assistance.
Contract is not associated to the specimen plan 8256 Transactions were received for a contract that is not associated to the RDSP's specimen plan. Verify and confirm whether the specimen plan provided in the original transaction was accurate and make corrections if needed. If there is reason to think that the specimen plan reported in the original transaction(s) was incorrect, contact Issuer Support.
The original transaction must not have been reversed 8258 The CDSP received a reversal transaction referring to a transaction that has already been reversed in a prior processing period. Once a transaction is reversed, it is not possible to reverse it a second time. If the intention were to undo a prior reversal, submit a new transaction that matches the original transaction that was reversed.
There must not be more than one reversal for the same transaction within the current processing period 8259 More than one reversal transaction was received in the same processing period for the same transaction. No action is required as one reversal will be processed and the other will receive this error.
Contract must have a status of “closed” or “registered” 8260 A transfer reporting transaction (RT 701-02) has been received for a contract that does not currently have the status of either closed or registered. Transfer reporting transactions are sent by the relinquishing issuer involved in a transfer. For example, the financial organization that sends the funds to another organization so that the CDSP can have a record of assets being moved to another issuer. This type of transaction can only be processed for contracts that are registered but are awaiting closure pending on the new issuer completing a transfer request. It can also be for contracts that are closed as a result of a successfully completed RDSP transfer. The transfer reporting transaction is only applicable to plans that are either currently registered or are now closed but were at one point registered. Contact Issuer Support to clarify the current status of a contract.
The other contract and specimen plan cannot change once a transfer has been successfully resolved 8261 The CDSP received a contract registration transaction package (RT 101-01, 101-02 and 101-03) and the following conditions exist:
  • the transfer indicator is set to "Y"
  • a transfer has been resolved (for example, the relinquishing contract has been closed after a transfer request was received and processed) for the same contract indicated in the contact registration package
  • other contract and other specimens plan information in the contract registration package is different than what was indicated in the previous transfer request that was resolved
 It is not possible for relinquishing contract information to change once a transfer has been resolved. Determine whether the new contract registration transaction with a transfer indicator set to "Y" is needed or was sent in error. As the transfer has already been resolved, it is likely that no further action is necessary.
Specimen plan must be designated by the CRA to accept rollovers 8262 A rollover transaction has been received that includes a specimen plan identifier that has not been designated by the CRA as eligible to accept rollovers. The issuer must update the specimen plan with the CRA RPD to accept rollovers. Once this is done, contact CDSP to undergo industry testing to allow submission of this transaction.
Must be within the date range the specimen plan is designated by the CRA to accept rollovers 8263 A rollover transaction has been received with a date that either precedes or exceeds the period for which the designated specimen plan is eligible to accept these requests. Contact Issuer Support to clarify the parameters for this transaction.
Must be greater than the last consent transaction date submitted 8264 An add consent transaction (RT 202-01) has been received with a consent date that is earlier than the date provided for a previous add consent transaction. Ensure that add consent date provided is later than the date of the latest add consent activity for that beneficiary.
Must not exist as a holder on any contract of the reported beneficiary 8265 An add consent transaction (RT 202-01) has been received for a holder or BN that is already associated to an open or closed contract. No further action is necessary.
Must already be recorded as a consent for the beneficiary 8266 A revoke consent transaction (RT 202-02) has been received that refers to a SIN or BN that does not match an existing consent for the beneficiary. In addition, this code can be generated if both a revoke consent and add consent transaction are submitted for the same period and for the same beneficiary. Review the contract to determine who should have consent status and adjust accordingly.
Must not be an active holder on the current beneficiary contract 8267 A revoke consent transaction (RT 202-02) has been received with a SIN or BN for an active holder for which an add consent transaction (RT 202-01) has been previously submitted. An active holder of a contract cannot have his previously submitted consent transaction revoked. To revoke consent status in such a scenario, submit a remove holder transaction (RT 201-23) for the current RDSP contract. This would only be possible for RDSPs with multiple holders, refer to error code 8249). Once the individual or Agency is no longer an active holder, submit a revoke consent transaction.
Beneficiary consent cannot be revoked 8268 A revoke consent transaction (RT 202-02) has been received with the SIN that matches the contract's beneficiary. Consent status cannot be revoked for beneficiaries of RDSPs. No further action is required.
Date is earlier than the original transaction date 8300 A reversal request, contribution correction or stop bond request is dated before the date of the original transaction. This applies to the following RT:
  • stop bond payment request (RT 401-06)
  • LDAP/DAP reversal (RT 401-22, 401-23)
  • reverse repayment of grant or bond (RT 401-11)
  • retirement savings rollover reversal (RT 401-09)
  • education savings rollover reversal (RT 401-31)
  • correction of contribution/grant request (RT 401-02)
 Ensure that the reversal/correction/stop bond is not dated earlier than the original transaction associated to this transaction.
Error in original transaction, current transaction cannot be processed 8301 A reversal request, contribution correction or stop bond request has been received for a transaction that was rejected in error. This applies to the following TT:
  • stop bond payment request (RT 401-06)
  • LDAP/DAP reversal (RT 401-22, 401-23)
  • reverse repayment of grant or bond (RT 401-11)
  • retirement savings rollover reversal (RT 401-09)
  • education savings rollover reversal (RT 401-31)
  • correction of contribution/grant request (RT 401-02)
  • Specified Disability Savings Plan (SDSP) election reversal (RT 501-04)
 The original transaction would not have generated financial activity; therefore, reversals or corrections of these transactions cannot be processed. Verify the original transaction number and determine if action is required or contact Issuer Support to clarify.
Unable to locate the original transaction 8303 The original transaction number contained in one of the following refers to a transaction not previously reported:
  • stop bond payment request (RT 401-06)
  • LDAP/DAP reversal (RT 401-22, RT 401-23)
  • reverse repayment of grant or bond (RT 401-11)
  • retirement savings rollover reversal (RT 401-09)
  • education savings rollover reversal (RT 401-31)
  • correction of contribution/grant request (RT 401-02)
  • SDSP election reversal (RT 501-04)
 Verify the original issuer transaction number and ensure the original transaction was submitted and processed successfully.
Original transaction must have been designated as the active request 8305 The original transaction number on the stop bond payment request transaction (RT 401-06) refers to an inactive bond payment request. Replace the information provided in the original transaction number field with the transaction number of the current active bond payment request. The active bond payment request will be the latest request for which the bond was paid.
Another stop bond payment has already been requested for the original transaction 8306 A stop bond payment request transaction (RT 401-06) has already been successfully processed by the CDSP for the original bond request indicated. If the intention is to stop the original bond payment request, no further action is needed as the original request was processed. If the intention is to reactivate a bond payment request. For example, by stopping the previous stop bond payment request), submit a new bond payment request (RT 401-05).
A more recent correction transaction is already associated to the contribution 8307 A correction of contribution/grant request transaction (RT 401-02) has been received with a correction date that is before the correction date of another contribution correction transaction already processed for that transaction. Corrections to RDSP contributions must be applied in chronological order. Ensure the correction date provided reflects the date that the correction was requested and resubmit the transaction if required.
Original transaction and its reversal were found in the same processing period 8308 An original transaction and its corresponding reversal transaction have been received in the same processing period. Verify the intent of the submission and resubmit if required.
Must be on or after January 1, 2014 8312 An education savings rollover (RT 401-30) has been received with a date prior to January 1, 2014. Ensure the date reported in the education savings rollover is on or after January 1, 2014.

Page details

2025-09-18