Appendices

Disclaimer: RDSP issuers

The information contained on this page is technical in nature and is intended for Registered Disability Savings Plan (RDSP), Canada Disability Savings Grant (grant) and Canada Disability Savings Bond (bond) issuers. For general information, visit the RDSP section.

Consult this page frequently for newer versions. The following laws and regulations take precedence over information contained in InfoCapsules in the event of discrepancies:

  • Income Tax Act
  • Canada Disability Savings Act
  • Canada Disability Savings Regulations

Appendix A - Understanding Error Codes

Employment and Social Development Canada (ESDC) is responsible for the administration of the Canada Disability Savings Grant (grant) and the Canada Disability Savings Bond (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.

This document 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).

1.0 Background Information

This document provides information to assist in understanding Error Codes. For additional technical information, consult the Interface Transaction Standards (ITS).

1.1. What is an Error Code

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

1.2. 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 801 transactions (Error File) which reference the original transaction identifier along with the name of the field in error.

1.3. How does an Error Code differ from a Refusal Reason

If the CDSP system cannot process an RDSP transaction due to an error(s) in the transaction information, the CDSP system will reject the transaction. In these cases, a corresponding record type 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 record type 901 transaction (the Transaction Processing File).

1.4. Using this document

This document 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 the document are:
    • Issuer Support: 1-888-276-3632
    • Client Services: 1-866-204-0357
    • Canada Revenue Agency (CRA) – Registered Plans Directorate (RPD): 1-800-267-3100 (E) or 1-800-267-5565 (F)

2.0 Error Code

ERROR CODE EXPLANATION

1
Duplicate Issuer Transaction Number

All transactions submitted to the CDSP must contain a unique Issuer Transaction Number for a single issuer. Because identical Issuer Transaction Numbers cannot exist in the CDSP system, such a transaction cannot be processed.

RESOLUTION: Provide a unique Transaction Number that was not previously submitted.

2
Invalid Record Type/Transaction Type

The record type and/or the Transaction Type is invalid.  

RESOLUTION: Review the transaction file and ensure the Record and/or Transaction Type match those defined in the ITS.

3
Issuer Transaction  Number not provided

The Issuer Transaction Number has not been provided.

RESOLUTION: Verify that a unique Issuer Transaction Number is provided in all submitted records.

4
Issuer Business Number (BN) is not 15 characters

The issuer BN included in a transaction record is not 15 characters long.

RESOLUTION: Ensure that all BNs within submitted transaction records contain 15 alpha-numeric characters.

8000
Physical file name does not correspond to file name in header record

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 and/or records.

RESOLUTION:  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.

8001
Incorrect format of physical file name

The submitted physical file name is incorrectly formatted.

RESOLUTION: 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.

8002
Duplicate record with same file name found in the database

A file with the same BN, Transactions Latest Month, Date Sent, and File number already exist in the CDSP system. 

RESOLUTION: Review the file name and ensure the combination of BN, Transactions Latest Month, Date Sent, and File number is unique.

8003
Header Record not the first record in the file

There is another character or transaction found before the Header Record (Record Type (RT) 001).

RESOLUTION: 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.

8004
No Header Record

The file does not contain a Header Record (001). 

RESOLUTION: Ensure that the file begins with a Header Record.

8005
Too many Header Records in the file

Multiple Header Records (RT 001) are present in a transaction file. 

RESOLUTION: 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.

8006
This BN is not authorized to send files or is not associated to a Specimen Plan

The BN included in the Header Record is not authorized to send files to the CDSP and/or is not associated to a Specimen Plan.

RESOLUTION: Ensure that the BN included 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.

8007
The data version in the header does not match the current version of the ITS

The data version information included in the Header Record (RT 001) does not match data versions compatible with the current version of the ITS.

RESOLUTION: Ensure that the Data Version included in the header record matches the current version of the ITS

8008
Record count does not match the number of records in the file

The record count indicated in the Trailer Record (RT 999) does not match the number of records in the transaction file. 

RESOLUTION: 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.

8009
Too many Trailer Records in file

Multiple Trailer Records (RT 999) are present in a transaction file.

RESOLUTION: Ensure that only one record beginning with 999 is present in the file.  

8010
No Trailer Records in file

The issuer submitted a transaction file that does not contain Trailer Record (RT 999).

RESOLUTION: Ensure that a Trailer Record is present within the transaction file and that it is the last record in the file.

8011
Trailer Record not last in file

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.

RESOLUTION: 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.  

8012
Program identifier must be CDSP

The program identifier in the Header Record (RT 001) is not CDSP.

RESOLUTION: Ensure that the program identifier is CDSP in the transaction file’s Header Record.   

8013
The transactions latest month must be on or before the current month

The transaction’s latest month is not on or before the current reporting period set by the CDSP.

RESOLUTION: 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 (i.e. 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.

8100
Invalid date

A date in the transaction file does not conform to the YYYYMMDD format.

RESOLUTION: Review the file and ensure that the format YYYYMMDD is used for all dates.

8101
Invalid value

An invalid value was detected in a record submitted to the CDSP.

Example: The gender value must be ‘1’ or a ‘2’ (as per the ITS) but the record contains the value ‘3’ at the character position assigned to the gender field.

RESOLUTION: Ensure that all data provided conforms to formatting guidelines stated in the ITS.

8102
Is not identified in the CDSP system

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.

The following fields can be affected by this Error Code:

  • the issuer’s BN
  • the Specimen Plan
  • Social Insurance Number (SIN) information for holders and beneficiaries
  • Contract Number

RESOLUTION: 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.

8104
Data is missing from field

Data is missing in a mandatory field.

RESOLUTION: 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.

8105
Invalid SIN

The SIN information submitted did not pass validation requirements.

RESOLUTION: Ensure that the SIN is corrected and matches the SIN provided by the client(s). In addition to the SIN itself, the Given Name, Surname, Date of Birth and Gender associated with the submitted SIN should match information held by the Social Insurance Registry (SIR). Refer to the Error Report record (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.

8106
Amount must be greater than zero

A dollar amount is not greater than zero within the following transaction types:

  • Contribution and/or Grant Request (RT 401-01)
  • Retirement Savings Rollover (RT 401-08)
  • Education Savings Rollover (RT 401-30)

RESOLUTION: Ensure that fields containing dollar amounts are greater than zero.

8108
Amount must be greater than or equal to $0

A dollar amount is negative on the following transaction types:

  • Correction of Contribution and/or Grant Request (RT 401-02)
  • Repayment of Grant and/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

RESOLUTION: Ensure that fields containing dollar amounts are equal to or greater than zero.

8109
Amount must be greater than or equal to $1

The Total LDAP amount on the LDAP transaction type (RT 401-21) is less than one dollar.

RESOLUTION: Ensure that the Total LDAP amount field includes a value that is greater than or equal to one dollar.

8110
Sum of reported amounts must be greater than $0

The sum of all amounts reported on the Repayment of Grant and/or Bond Transaction Type (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

RESOLUTION: Ensure that the sum is greater than zero.

8111
Grant must have been previously paid

No Grant was previously paid to a beneficiary and a repayment of Grant and/or a Grant Termination Adjustment is being reported on the Repayment of Grant and/or Bond transaction type (RT 401-10).

RESOLUTION: Repayment of Grant and Grant Termination Adjustment transactions can only be processed if they correspond to amounts of Grant that were previously paid into a RDSP. Determine if Grant was previously paid to the beneficiary and:

  • 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

8112
Bond must have been previously paid

A repayment of Bond and/or a Bond Termination Adjustment is being reported on a Repayment of Grant and/or Bond transaction (RT 401-10) but no Bond was previously paid to the beneficiary.

RESOLUTION: 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 and,

  • if not, no further action is required as there is no bond to repay or adjust, or
  • if bond does appear to have been previously paid, contact Issuer Support

8113
Date must be on or after July 1, 2011

The LDAP and DAP and/or Retirement Savings Rollover date is before July 1, 2011. This code applies to the following transaction types:

  • Retirement Savings Rollover (RT 401-08)
  • Disability Assistance Payment (RT 401-20)
  • Lifetime Disability Assistance Payment (RT 401-21)

RESOLUTION: For the above transactions, ensure the date reported is on or after July 1, 2011.

8200
Date must be on or after December 1, 2008

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 and/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 and/or Bond as well as Reverse Repayment of Grant and/or Bond (RT 401-10 and 401-11). Applies to the Repayment Date and Reverse Repayment Date fields
  • Disability Assistance Payment (DAP) as well as Lifetime Disability Assistance Payment (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

RESOLUTION:  Ensure that the date(s) are on or after December 1, 2008.

8201
Date is of a future reporting period

The date reported in a transaction is for a future reporting period.

RESOLUTION: Ensure that date provided is on or before the current reporting period end date set by the CDSP.

8203
Date must be on or after Beneficiary’s date of birth

The date information submitted in a transaction is before the beneficiary’s date of birth.

RESOLUTION: Ensure that the dates provided on the applicable transaction are on or after the beneficiary’s date of birth.

8204
Date must be on or before December 31 of the year in which the Beneficiary turns 49

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 (ex: If the beneficiary turns 49 on June 12 2012, the date submitted must be on or prior to December 31, 2012).

RESOLUTION: Ensure that the bond Request Date provided is on or prior to December 31 of the year in which the beneficiary turns 49.

8206
Date must be on or after Contract Signature Date

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.

RESOLUTION: Ensure that the date provided is on or after the Contract Signature Date.

If there is a need to clarify the contract signature date reported to the CDSP or if there is reason to believe that the date submitted does not precede the Contract Signature Date, contact Issuer Support.

8207
Date must be within Issuer approval dates

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.

Transactions dated before the start date of issuer approval cannot be processed by the CDSP as this would mean that the issuer was not authorized to report at this time. In some cases, issuers have also been assigned a cessation date which indicates when they are no longer authorized to submit transactions.

RESOLUTION: 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.

8208
Must be on or after the Bond Request date

The Stop Request Date of a Stop Bond Request (RT 401-06) precedes the original Bond Request date.

RESOLUTION: A request to stop Bond payments must occur after a bond Request is successfully processed by the CDSP. Review prior RDSP bond activity dates and 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.

8220
Specimen Plan must be valid

A Specimen Plan identified in a record is not valid.

RESOLUTION: 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.

8221
Authorized Agent not authorized to send data for the Specimen Plan

The Authorized Agent is not authorized to send data for the indicated Specimen Plan.

RESOLUTION: 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.

8222
Specimen Plan must be associated with the Issuer

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.

RESOLUTION: Ensure that the Specimen Plan and/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.

8230
Contract must not already be a contract that is Registered, Closed, De-registered or Nullified

A Contract Registration transaction package (RT 101-01, 102-02 and 101-03) is submitted for a contract that already exists.

RESOLUTION: 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.

8231
The Beneficiary must not already have a Pending, Registered or De-registered contract

This error applies to:

  • a Contract Registration transaction package (RT 101-01, 102-02 and 101-03) is submitted for a beneficiary that is currently associated to an existing RDSP that has a status of Pending, Registered or De-registered
  • an attempt to initiate a transfer of an existing RDSP but the transfer indicator is not set to Y (Yes) in the Contract registration transaction package

RESOLUTION: 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 was to initiate a transfer, ensure that the transfer indicator is set to Y (Yes). 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 in order to register a new contract.

8233
The Contract Signature Date cannot change once a contract status is pending

A Contract Registration transaction package (RT 101-01, 101-02 and 101-03) has been received for a contract which currently has a status of ‘Pending’ and the Contract Signature Date is different than the one indicated in original Contract Registration transaction package.

RESOLUTION: 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 and submit a new Contract Registration transaction Package with a new Contract Number in the subsequent CDSP processing period.

8234
The other contract must be associated with the beneficiary and other Specimen Plan and must be Pending, Registered, De-registered or Closed

The Transfer Indicator is set to ‘Yes’ 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

RESOLUTION: Ensure the other contract and other Specimen Plan match each other and are associated to the beneficiary of the contract.

8235
Contract is not currently associated to the Specimen Plan

The Contract Number is not associated to 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.

RESOLUTION: Ensure there are no errors in the Specimen Plan submitted to the CDSP, that the contract was not already submitted and/or check 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.

8236
Contract is not currently associated to the Beneficiary

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.

RESOLUTION: Verify the Contract Number and Beneficiary SIN data submitted to the CDSP. If there are no errors, contact Issuer Support.

8237
Contract must be currently associated to the Holder

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.

RESOLUTION: 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).

8238
Contract Registration transaction is missing a component

The Contract Registration transaction package does not include a Contract component (RT 101-01), and/or a beneficiary component (RT 101-02) and/or a holder component (RT 101-03).

RESOLUTION: Ensure that the Contract Registration transaction package contains all three Record Types and resubmit if required.

8239
Duplicate Contract Registration in the same period

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 8240 would be generated. 

RESOLUTION: 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.

8240
Only one Contract Registration request for the Beneficiary in a given period is permitted

Two 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 and only one RDSP can exist for each eligible beneficiary. If duplicate Contract Registration transactions are submitted in the same period, one will receive this error and the other will be processed.

RESOLUTION: 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 a RDSP with another financial organization.

8241
Contract must currently have a status of ‘Registered’

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)

RESOLUTION: If the contract status isPending 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.

8242
The date must be the same as reported on the original contribution

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.

RESOLUTION: Review any Correction of Contribution/Grant Request transactions and make corrections to the correction date field as needed.

8243
Grant requested may only change from ‘No’ to ‘Yes’

The grant requested field in the Correction of Contribution and/or Grant Request transaction (RT 401-02) is set to N when the original contribution had the Grant Requested field set to Y. 

RESOLUTION: 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 was 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.

8244
Must be on or after the Original contribution date

The date indicated in the Correction Date field of the Correction of Contribution and/or Grant Request transaction (RT 401-02) is prior to the date of the original contribution being corrected.

RESOLUTION:  Corrections must be dated after the original contribution. Ensure that the date indicated in the Correction Date field of the Correction of Contribution and/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.

8245
Contract already exists in CDSP system

The Contract Number being submitted via the RT 102-11 already exists for that Specimen Plan.  

RESOLUTION: No two contracts in the CDSP database can be associated to the same Contract Number/Specimen Plan combination. Ensure that a unique Contract Number is chosen when submitting an RT 102-11 transaction.

8246
Contract must already be a contract that is Registered, Deregistered or Pending

The FI submits a Close Contract transaction (RT 102-10) for a contract that is not currently Registered, Deregistered or Pending.

RESOLUTION: Verify if the Close Contract transaction was submitted in error or contact Issuer Support to clarify the status of the contract. 

8247
Contract must already be a contract that is Registered, Closed, or Pending

A Rename Contract transaction (RT 102-11) has been received for a contract that has a status other than Registered, Closed or Pending. 

RESOLUTION: Verify if the Rename Contract transaction was submitted in error or contact Issuer Support to clarify the status of the contract. 

8248
Contract is already associated to the Holder

An Add Holder to Contract transaction (RT 201-13) has been received for a contract to which the holder is already associated.

RESOLUTION: Verify that the SIN and Name fields are for a new holder and are not already associated to the applicable contract.

8249
Cannot remove last Holder on the contract

A transaction includes a request to remove the only holder (RT 201-23) associated to a RDSP

RESOLUTION: A 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 was not previously associated to the RDSP due to error, he/she would need to be added before a request to remove another holder can be processed.  

8250
The SIN or BN is not numerically valid

A SIN reported for either a beneficiary or a holder or the BN reported for an agency is not numerically valid.

RESOLUTION: Check the SIN against the RDSP application or validate the SIN with the applicable individual. Make the correctionand then re-submit the transaction. 

8251
Beneficiary year of birth cannot be modified

The beneficiary component of Contract Registration package (RT 101-02) or an Update Beneficiary transaction (RT 201-02) was received with a year of birth different than the year originally submitted for a beneficiary.

RESOLUTION: 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 Social Insurance Registry. If the birth year already submitted is inaccurate, contact Issuer Support.

8252
Contract already associated to another Beneficiary SIN

The beneficiary component of a Contract Registration transaction package (RT 101-02) has been received for a beneficiary with a SIN that does not match the beneficiary SIN already associated with this contract. 

RESOLUTION: 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.

8253
There must not already be a contract awaiting transfer in the CDSP system for the Beneficiary

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 and a contract already exists with a status of Registered, Pending or De-registered and a transfer indicator of Y for the same beneficiary. 

RESOLUTION: 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 so a Close Contract transaction (RT 102-10) can be submitted in lieu of the original transfer request.  

8254
Conflicting contract transactions pertaining to the same contract received in the same period

Multiple, conflicting contract transactionsare submitted in the same period creating duplicate contract names:

  • two unique Rename Contract transactions (RT 102-11) in the same processing period and for the same contract present in the CDSP database
  • two unique Rename Contract transactions (RT 102-11) requesting to rename two 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

RESOLUTION: 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, re-submitting one will suffice in order 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, re-submit the Close Contract or Rename Contract transactions for the following processing period.

8255
Contract must not be nullified

A transaction cannot be processed because the contract status is nullified.

RESOLUTION: Register a new contract or contact Issuer Support for assistance.

8256
Contract is not associated to the Specimen Plan

Transactions were received for a contract that is not associated to the RDSP’s Specimen Plan.

RESOLUTION: 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.

8258
The original transaction must not have been reversed

The CDSP received a reversal transaction referring to a transaction that has already been reversed in a prior processing period.

RESOLUTION: Once a transaction is reversed, it is not possible to reverse it a second time.

If the intention was to undo a prior reversal, submit a new transaction that matches the original transaction that was reversed.

8259
There must not be more than one reversal for the same transaction within the current processing period

More than one reversal transaction was received in the same processing period for the same transaction.

RESOLUTION: No action is required as one reversal will be processed and the other will receive this error.

8260
Contract must have a status of Closed or Registered

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 (e.g. the financial organization that sends the funds to another organization) so that the CDSP can have 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 or for contracts that are closed as a result of a successfully completed RDSP transfer.

RESOLUTION: 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.

8261
The other contract and Specimen Plan cannot change once a transfer has been successfully resolved

The CDSP received a Contract Registration transaction package (RT 101-01, 101-02 and 101-03) and the following conditions exist:

  • transfer indicator is set to Y
  • a transfer has been resolved (e.g. 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 Specimen Plan information in the contract registration package is different than what was indicated in the previous transfer request that was resolved

RESOLUTION: 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.

8262
Specimen Plan must be designated by CRA to accept rollovers

A rollover transaction has been received that includes a Specimen Plan identifier that has not been designated by CRA as eligible to accept rollovers.

RESOLUTION: The issuer must update the Specimen Plan with the CRA Registered Plans Directorate to accept rollovers. Once this is done, contact CDSP to undergo industry testing to allow submission of this transaction.

8263
Must be within the date range the Specimen Plan is designated by CRA to accept Rollovers

A Rollover transaction has been received witha date that either precedes or exceeds the period for which the designated Specimen Plan is eligible to accept these requests.  

RESOLUTION: Contact Issuer Support to clarify the parameters for this transaction.

8264
Must be greater than the last Consent transaction date submitted

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.

RESOLUTION: Ensure that the Add Consent Date provided is later than the date of latest Add Consent activity for that beneficiary.

8265
Must not exist as a Holder on any contract of the reported beneficiary

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.

RESOLUTION: No further action is necessary.

8266
Must already be recorded as a consent for the Beneficiary

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. 

RESOLUTION: Review the contract to determine who should have Consent status and adjust accordingly.

8267
Must not be an active Holder on the current Beneficiary contract

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.

RESOLUTION: 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 8249). Once the individual or Agency is no longer an active holder, submit a Revoke Consent transaction.

8268
Beneficiary consent cannot be revoked

A Revoke Consent transaction (RT 202-02) has been received with the SIN that matches the contract’s beneficiary.  

RESOLUTION: Consent status cannot be revoked for beneficiaries of RDSPs. No further action is required.

8300
Date is earlier than original Transaction Date

A Reversal Request, Contribution Correction or Stop Bond Request is dated before the date of the original transaction. This applies to the following record types:

  • Stop Bond Payment Request (RT 401-06)
  • LDAP/DAP Reversal (RT 401-22, 401-23)
  • Reverse repayment of Grant and/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)

RESOLUTION: Ensure that the Reversal/Correction/Stop Bond is not dated earlier than the original transaction associated to this transaction.

8301
Error in original transaction, current transaction cannot be processed

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 transaction types:

  • Stop Bond Payment Request (RT 401-06)
  • LDAP/DAP Reversal (RT 401-22, 401-23)
  • Reverse repayment of Grant and/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)
  • Episodic DTC Election Reversal (RT 501-02)
  • SDSP Election Reversal (RT 501-04)

RESOLUTION: 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.

8303
Unable to locate the original transaction

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, 401-23)
  • Reverse repayment of Grant and/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)
  • Episodic DTC Election Reversal (RT 501-02)
  • SDSP Election Reversal (RT 501-04)

RESOLUTION: Verify the Original Issuer Transaction Number and ensure the original transaction was submitted and processed successfully. 

8305
Original transaction must have been designated as the active request

The Original Transaction Number on the Stop Bond Payment Request transaction (RT 401-06) refers to an inactive Bond Payment Request.

RESOLUTION: 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 bond was paid.

8306
Another Stop Bond Payment has already been requested for the original transaction

A Stop Bond Payment Request transaction (RT 401-06) has already been successfully processed by the CDSP for the original bond request indicated.

RESOLUTION: 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 re-activate a Bond Payment Request (e.g. by stopping the previous Stop Bond Payment request), submit a new Bond Payment Request (401-05).

8307
A more recent Correction transaction is already associated to the contribution

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.

RESOLUTION: Corrections to RDSP contributions must be applied in chronological order. Ensure the correction date provided reflects the date that the correction was requested and re-submit the transaction if required.

8308
Original transaction and its reversal were found in the same processing period

An original transaction and its corresponding reversal transaction have been received in the same processing period.

RESOLUTION: Verify the intent of the submission and resubmit if required.

8309
Date must be on or after Certification Date

The Episodic DTC Election (501-01) transaction date precedes the Medical Doctor certification date.

RESOLUTION: Ensure that the transaction date provided on the Episodic DTC Election is on or after the date the Medical Doctor signs the form concerning future DTC eligibility.

8310
Beneficiary must not be DTC ineligible for 5 consecutive years on or after the contract signature year and before the year of election request processing

An Episodic DTC Election (501-01) has been received for a beneficiary who has either been ineligible for DTC or for whom eligibility is undetermined for 5 consecutive years on or after the year of the contract signature date and before the year of the processing of the request.

RESOLUTION: Verify the DTC Election date and determine if action is required or contact Issuer Support to clarify the DTC eligibility of the beneficiary.

8311
Episodic DTC election period must not overlap with an existing Episodic DTC election period for the same contract

An Episodic DTC Election (501-01) has been received for a beneficiary with an existing processed Episodic DTC election with one or more years in common.

RESOLUTION: Verify the DTC Election date and determine if action is required.

8312
Must be on or after January 1, 2014

An Education Savings Rollover (401-30) has been received with a date prior to January 1, 2014.

RESOLUTION: Ensure the date reported in the Education Savings Rollover is on or after January 1, 2014.

Appendix B - Understanding Refusal Reasons

Employment and Social Development Canada (ESDC) is responsible for the administration of the Canada Disability Savings Grant (grant) and the Canada Disability Savings Bond (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.

This document explains the Refusal Reasons received in response to financial requests for grant and/or bond when the CDSP system processes a financial transaction but does not award full benefits. The document also describes means to resolve/re-process transactions that have been allocated a refusal reason by the CDSP system.

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

1. Background Information

This document provides information to assist in understanding Refusal Reasons. For additional technical information, consult the Interface Transaction Standards (ITS).

1.1 What is a Refusal Reason?

Refusal Reasons indicate why transactions requesting grant or bond, which met all formatting rules and were processed by the system, did not receive a full grant or bond payment.

1.2. How Are Refusal Reasons Reported to Financial Institutions?

The CDSP system reports Refusal Reasons in the 66-67 position of the 901 record type provided at the end of each reporting period. This is applicable to the:

  • grant request submitted through a RT 401-01
  • bond request submitted through a RT 401-05

1.3. Refusal Reasons Differ from Error Codes

If the CDSP system cannot process an RDSP transaction sent by a financial institution (FI), due to an error in the transaction information, the transaction is rejected. In these cases, a record type 801 transaction with an Error Code indicating why the transaction was not processed is provided in the Error File report that references the original transaction identifier along with the name of the field in error. These Error Codes should be investigated and new transactions with the corrected information resubmitted.

Transactions successfully processed by the CDSP system will not generate Error Codes. If a transaction is processed but the full amount of grant or bond is not paid, a refusal reason will be generated and reflected in the record type 901.

1.4 Using this Document

This document lists the following information for each incentive:

  • Refusal Reason Codes and a detailed explanation for each code
  • how to resolve or better understand what caused the refusal
  • 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 the document are:
    • Issuer Support: 1-888-276-3632
    • Client Services: 1-866-204-0357
    • Canada Revenue Agency (CRA): 1-800-959-8281 (E) or 1-800-959-7383 (F)

2. Refusal Reasons

REFUSAL REASON EXPLANATION
01
Maximum Current Entitlement of Grant/Bond Paid

All of the beneficiary’s grant/bond entitlement, including any carry forward entitlement, has been paid out for the calendar year in which the contribution or bond request was made. This refusal reason is also generated when a bond request is processed with zero bond payment because the income level of the beneficiary/primary caregiver (PCG) exceeds the maximum.  

RESOLUTION: Generally no action is required. If the grant or bond paid does not match the expected amount, investigate and contact issuer support for more information if required.
02
Lifetime Contribution Limit Exceeded

The total amount of contributions (including rollovers) for a beneficiary has exceeded the $200,000 contribution limit. Any subsequent contributions made after this limit is reached are refused grant.

RESOLUTION: Investigate what caused the total contribution amount to exceed $200,000 and determine if any contributions were reported incorrectly. If there is a discrepancy in the contribution amount(s), submit a contribution correction with the correct amount. If a discrepancy exists in the beneficiary’s lifetime contribution amount, contact issuer support for more information.
03
Lifetime Limit Exceeded

The beneficiary has received the maximum lifetime grant payable of $70,000 or for bond, $20,000.

RESOLUTION: No action is required. This refusal reason on a contribution or bond request means that no further grant or bond will be paid to the beneficiary.
04
Age of Beneficiary

The transaction date of the contribution is later than December 31st of the year in which the beneficiary turned 49.

RESOLUTION: No further action is required as grant will not be paid after the end of the year in which the beneficiary turned 49.
05
Specimen Plan not Valid

The specimen plan reported on the bond request no longer has a valid status in the CDSP system. To be valid, a specimen plan must have a status of “registered”, “under review”, “ceased” or “revoked”. This refusal reason only occurs during the annual resubmission of an active bond request.

RESOLUTION:  Contact issuer support to verify the status of the specimen plan reported on the bond request.
06
No Grant requested

Grant was not requested on a contribution as the grant requested flag was set to “No”.

RESOLUTION: Confirm that grant was to be requested for the contribution and if yes, submit a contribution correction transaction for the same amount as the original contribution, and ensure the flag is set to “Yes”.
08
SIN Not Usable

The Social Insurance Number (SIN) reported on the contribution requesting grant or bond has been flagged as “not usable” by the Social Insurance Registry (SIR).

RESOLUTION: A SIN can be flagged for a number of reasons, and if the contract holder has questions about the reason they should contact SIR. If the beneficiary’s SIN is unusable because they have a new SIN, resubmit the bond request or submit a contribution correction using the new SIN.
10
Invalid Beneficiary SIN

The SIN used on the annual resubmission of a bond request is no longer valid as it has been linked to a new SIN.

RESOLUTION: Contact the contract holder to validate the SIN and if required obtain the beneficiary’s new SIN and resubmit a bond request using the updated SIN if applicable.
19
Contract Not Registered

A grant or bond request has been submitted for a contract that does not have a status of registered.

RESOLUTION: Use the Contract Status Report to determine why the contract is not registered and re-submit the contract registration package if applicable. If it is not clear why the contract was not registered, contact issuer support.
21
Last Bond payment under this application – new 18+ Bond request required

This is a warning message to submit a new bond application request because the beneficiary is in his or her 18th year. If no 18+ application is submitted bond will no longer be paid.

RESOLUTION: Request that the holder complete a new 18+ bond application and resubmit the request.
22
Bond request is not/no longer designated to attract Bond for the Beneficiary

The original bond request submitted is no longer active.

RESOLUTION: Notify the holder and ask if they would like to continue receiving bond. If yes, submit a new bond request to reactivate the bond.
24
Contract status conditions for adjustment of payment not met

A correction has been submitted on a contract that has a status of closed or de-registered.

RESOLUTION: Determine if contract has correct status and take corrective action. Contact issuer support if required.
26
Bond resubmission date is not within issuer approval dates

The annual resubmission of an active bond request occurred after the cessation date of the Specimen Plan.

RESOLUTION: Verify the Specimen Plan eligibility with CDSP issuer support and then resubmit the bond request with a date which is within the specimen plans approved period. Generally no action is required as the contract is closed or transferred when the specimen plan is no longer approved.
29
Beneficiary is a non-resident

The beneficiary is not a Canadian resident as of the day the transaction occurred.

RESOLUTION: Refer the holder to CRA to confirm the beneficiary’s residency status as of the transaction date.
30
Beneficiary DTC eligibility not confirmed

DTC eligibility has not been confirmed by CRA for the beneficiary in the year which the transaction occurred.

RESOLUTION: Refer the holder to CRA to confirm DTC.
32
Beneficiary DTC eligibility not confirmed for 2 or more consecutive non-election years

DTC eligibility has not been confirmed by CRA for the beneficiary for two or more consecutive years where an election has not been submitted.

RESOLUTION: Refer the holder to CRA to confirm DTC.

33
Beneficiary DTC eligibility not confirmed for 5 or more consecutive years

DTC eligibility has not been confirmed by CRA for the beneficiary for five or more consecutive years regardless of a DTC election.

RESOLUTION: Refer the holder to CRA to confirm DTC.
99
Other

Used onlyin special cases.

RESOLUTION: Information provided as these cases occur.

Appendix C - Transaction types

This document lists the transaction types that can be sent to the Canada Disability Savings Program (CDSP) system as well as the files that are sent to financial institutions in response to the transaction types.

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

1. Objective

To help financial institutions determine which transaction files are sent to the CDSP system and which files are produced by the CDSP system in response to the received transaction files.

A quick reference table is provided.

2. Using this document

This document includes the following information:

  • a list of the transactions types sent by the financial institution to the CDSP system;
  • a list of processing activities that may result from the transaction types sent by the financial institution; and
  • a list of files processed by the CDSP system.

3. Column descriptions

1st Column: Record Type (RT) and Transaction type (TT) sent by the financial institution to the CDSP system

  • A list of the possible transaction types sent by the financial institution to the CDSP system.

2nd Column: Processing that may result from the transaction types sent by the financial institution

  • Depending on the nature of the transaction type submitted by the financial institution, the following processing activities may occur (such as contract registration, Canada Disability Savings Grant (grant) and Canada Disability Savings Bond (bond) payments, grand and bond re-adjudication).

3rd Column: Files sent by the CDSP system to financial institutions

  • A list of potential files (Error File, Transaction Processing File, SIN Usability File, Contract Status File and Transfer Extract File) sent by the CDSP system in response to specific transaction types sent by the financial institution.
  • RT 981 – Beneficiary DTC Eligibility File: on a monthly basis, if the Canada Revenue Agency (CRA) has updated the Disability Tax Credit (DTC) status of a beneficiary, they forward this information to the CDSP system which in turn sends this data to the impacted financial institution. It is not sent in response to a specific transaction type sent by the financial institution.

4. Finding more information

For more information on transactions listed in the following table, see the reference sources below.

4.1. RT 101 – Contract Registration

  • RDSP Provider User Guide, Chapter 4-2: Setting Up an RDSP, Sections 1 (Information Exchange) and 2 (Opening a New Plan)
  • ITS, Sections 3.1 (Contract Registration Transaction) and 6.4 (Contract Registration Information)

4.2. RT 102 – Contract Update

  • RDSP Provider User Guide, Chapter 4-2: Setting Up an RDSP, Section 3.1 (Contract Update Information)
  • ITS, Sections 3.2 (Contract Update Transactions) and 6.5 (Contract Update Information)

4.3. RT 201 – Beneficiary and Holder Update

  • RDSP Provider User Guide, Chapter 4-2: Setting Up an RDSP, Section 3.2 (Beneficiary and Holder Update Information)
  • ITS, Sections 3.3 (Beneficiary and Holder Update Transactions) and 6.6 (Beneficiary and Holder Update Information)

4.4. RT 202 – Consent

  • RDSP Provider User Guide, Chapter 4-3: Request for Grant and Bond, Section 4 (Add/Revoke Consent)
  • ITS, Sections 3.4 (Consent Transactions) and 6.7 (Consent Information for Beneficiary)

4.5. RT 401 – Financials

  • RDSP Provider User Guide, Chapter 4-3: Request for Grant and Bond
  • RDSP Provider User Guide, Chapter 4-4: DAP and LDAP
  • RDSP Provider User Guide, Chapter 4-5: Rollover Transactions
  • RDSP Provider User Guide, Chapter 4-6: Transfers
  • ITS, Sections 3.5 (Financial Transactions) and 6.8 (Financial Transactions)

4.6. RT 501 – Election

  • RDSP Provider User Guide, Chapter 2-3: Specified Disability Savings Plan
  • RDSP Provider User Guide, Chapter 3-6: Repaying the Grant and Bond, Section 3 (Loss of DTC and Elections)
  • ITS, Sections 3.6 (Election Transactions) and 6.9 (Elections)

4.7. RT 701 – Reporting

  • ITS, Sections 3.7 (Reporting Transactions) and 6.10 (Reporting Transactions)
RT and TT sent by the financial institution to the CDSP system
(the 3 digit number is the RT, the 2 digit is the TT)
Processing that may result from the TT sent by the financial institution Files sent by the CDSP system to financial institutions
Contract Registration Grant and Bond Payments Grant and Bond Re-adjudication Transaction Processing
901
(.pro)
Error File
801 851
(.err)
Contract Status
951
952
953
(.reg)
SIN Usability
921
(.sur)
Transfer
971
(.xfr)
Beneficiary DTC Eligibility
981
(.dtc)
101 Footnote 1 Contract Information 01 yes yes P Footnote 2 yes yes yes 951 no If the transfer is resolved and the old contract is closed Is sent if CRA has reported a change in the beneficiary's DTC status to the CDSP system. It is not sent in response to a transaction type sent by the financial institution
Beneficiary Information 02 yes yes P Footnote 2 yes yes yes no yes
Holder Information 03 yes yes P Footnote 2 yes yes yes no yes
102 Close Contract (may be relinquishing contract in a transfer) 10 yes (Received in Transaction Processing File 901) no yes (Received in Transaction Processing File 901) yes no 951 no If the transfer is resolved and the new contract is registered
Rename Contract 11 no no no yes yes no no no
201 Update Beneficiary Information 02 no no no yes yes no yes no
Update Holder Information 03 no no yes yes yes no yes no
Add Holder to Contract 13 no no yes yes yes no yes no
Remove Holder from Contract 23 no no no yes yes no no no
202 Add or Update Consent for Beneficiary 01 yes yes yes yes yes 951 P Footnote 2
952 P Footnote 2
no If the transfer is resolved, the old contract is closed and the new contract is registered Is sent if CRA has reported a change in the beneficiary's DTC status to the CDSP system. It is not sent in response to a transaction type sent by the financial institution
Revoke Consent for Beneficiary 02 no no no yes yes no no no
401 Contribution and Grant Request 01 yes grant yes yes yes 951 P Footnote 2
952 P Footnote 2
no If the transfer is resolved, the old contract is closed and the new contract is registered
Correction of Contribution and Grant Request 02 yes grant yes yes yes 951 P Footnote 2
952 P Footnote 2
no
Bond Payment Request 05 yes bond yes yes yes 951 P Footnote 2
952 P Footnote 2
no
Stop Bond Payment Request 06 no no no yes yes no no no
Retirement Savings Rollover 08 yes no yes yes yes 951 P Footnote 2
952 P Footnote 2
no If the transfer is resolved, the old contract is closed and the new contract is registered Is sent if CRA has reported a change in the beneficiary's DTC status to the CDSP system. It is not sent in response to a transaction type sent by the financial institution.
Retirement Savings Rollover Reversal 09 no no no yes yes no no no
Repayment of Grant and/or Bond 10 no no no yes yes no no no
Reverse Repayment of Grant and/or Bond 11 no no no yes yes no no no
Disability Assistance Payment (DAP) 20 no no no yes yes no no no
Lifetime Disability Assistance Payment (LDAP) 21 no no no yes yes no no no
DAP Reversal 22 no no no yes yes no no no Is sent if CRA has reported a change in the beneficiary's DTC status to the CDSP system. It is not sent in response to a transaction type sent by the financial institution
LDAP Reversal 23 no no no yes yes no no no
Education Savings Rollover 30 yes no yes yes yes 951 P Footnote 2
952 P Footnote 2
no If the transfer is resolved, the old contract is closed and the new contract is registered
Education Savings Rollover Reversal 31 no no no yes yes no no no
501 Episodic Disability Tax Credit (DTC) Election 01 no no no yes yes 952 A no no
Episodic DTC Election Reversal 02 no no no yes yes 952 A no no
Specified Disability Savings Plan (SDSP) Election 03 no no no yes yes 953 A no no
SDSP Election Reversal 04 no no no X X 953 A no no
701 Monthly Reporting of Fair Market Value (FMV) 01 no no no X X no no no Is sent if CRA has reported a change in the beneficiary's DTC status to the CDSP system. It is not sent in response to a transaction type sent by the financial institution
Transfer Reporting of FMV and Earnings Amounts 02 no no no X X no no no
Report a problem or mistake on this page
Please select all that apply:

Thank you for your help!

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

Date modified: