RDSP Provider User Guide

A P P E N D I X
Understanding Error
A 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).

I n t h is c hap te r

1. Background Information ............................................... A – 3

2. Error Code ................................................................... A – 4

Table of Contents
1. Background Information ............................................................. - 3 -
1.1. What is an Error Code .......................................................... - 3 -
1.2. How to report Error Codes.................................................... - 3 -
1.3. How does an Error Code differ from a Refusal Reason .......... - 3 -
1.4. Using this Document ............................................................ - 3 -
2. Error Code ................................................................................. - 4 -
 Appendix A: Understanding Error Codes

1. 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

December 18, 2013 Appendix A Page 3 of 28

 Appendix A: Understanding Error Codes

• 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:

o Issuer Support: 1-888-276-3632

o Client Services: 1-866-204-0357
o Canada Revenue Agency (CRA) – Registered Plans Directorate
(RPD): 1-800-267-3100 (E) or 1-800-267-5565 (F)

2. Error Code
ERROR CODE EXPLANATION
1 All transactions submitted to the CDSP must contain
Duplicate Issuer a unique Issuer Transaction Number for a single
Transaction Number 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 The record type and/or the Transaction Type is
Invalid Record Type invalid.
/Transaction Type
RESOLUTION: Review the transaction file and
ensure the Record and/or Transaction Type match
those defined in the ITS.
3 The Issuer Transaction Number has not been
Issuer Transaction provided.
Number not
provided RESOLUTION: Verify that a unique Issuer
Transaction Number is provided in all submitted
records.
4 The issuer BN included in a transaction record is not
Issuer Business 15 characters long.
Number (BN) is not
15 characters RESOLUTION: Ensure that all BNs within submitted
transaction records contain 15 alpha-numeric
characters.

December 18, 2013 Appendix A Page 4 of 28

 Appendix A: Understanding Error Codes

ERROR CODE EXPLANATION

8000 As part of the formatting guidelines provided in the
Physical file name ITS, the combination of Authorized Agent BN, Date
does not correspond Sent and File Number must match in both the
to file name in physical file name and the file’s header record (001).
header record 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 The submitted physical file name is incorrectly
Incorrect format of formatted.
physical file name
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 A file with the same BN, Transactions Latest Month,
Duplicate record Date Sent, and File number already exist in the
with same file name CDSP system.
found in the
database RESOLUTION: Review the file name and ensure the
combination of BN, Transactions Latest Month, Date
Sent, and File number is unique.
8003 There is another character or transaction found
Header Record not before the Header Record (Record Type (RT) 001).
the first record in
the file 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 The file does not contain a Header Record (001).
No Header Record
RESOLUTION: Ensure that the file begins with a
Header Record.
8005 Multiple Header Records (RT 001) are present in a
Too many Header transaction file.
Records in the 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.

December 18, 2013 Appendix A Page 5 of 28

 Appendix A: Understanding Error Codes

ERROR CODE EXPLANATION

8006 The BN included in the Header Record is not
This BN is not authorized to send files to the CDSP and/or is not
authorized to send associated to a Specimen Plan.
files or is not
associated to a RESOLUTION: Ensure that the BN included in the
Specimen Plan 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 information included in the Header
The data version in Record (RT 001) does not match data versions
the header does not compatible with the current version of the ITS.
match 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 The record count indicated in the Trailer Record (RT
Record count does 999) does not match the number of records in the
not match the transaction file.
number of records
in the 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 Multiple Trailer Records (RT 999) are present in a
Too many Trailer transaction file.
Records in file
RESOLUTION: Ensure that only one record
beginning with 999 is present in the file.
8010 The issuer submitted a transaction file that does not
No Trailer Records contain Trailer Record (RT 999).
in file
RESOLUTION: Ensure that a Trailer Record is
present within the transaction file and that it is the
last record in the file.
8011 The issuer submitted a file with a Trailer Record (RT
Trailer Record not 999) that is not the last record within the transaction
last in file 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.

December 18, 2013 Appendix A Page 6 of 28

 Appendix A: Understanding Error Codes

ERROR CODE EXPLANATION

8012 The program identifier in the Header Record (RT
Program identifier 001) is not CDSP.
must be CDSP
RESOLUTION: Ensure that the program identifier is
CDSP in the transaction file’s Header Record.
8013 The transaction’s latest month is not on or before
The transactions the current reporting period set by the CDSP.
latest month must
be on or before the RESOLUTION: Ensure that the Transaction’s Latest
current month 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 A date in the transaction file does not conform to the
Invalid date YYYYMMDD format.

RESOLUTION: Review the file and ensure that the

format YYYYMMDD is used for all dates.
8101 An invalid value was detected in a record submitted
Invalid value 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.

December 18, 2013 Appendix A Page 7 of 28

 Appendix A: Understanding Error Codes

ERROR CODE EXPLANATION

8102 A field in a record cannot be matched with existing
Is not identified in data in the CDSP system. This error code applies to
the CDSP system 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 in a mandatory field.
Data is missing from
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 The SIN information submitted did not pass
Invalid SIN 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.

December 18, 2013 Appendix A Page 8 of 28

 Appendix A: Understanding Error Codes

ERROR CODE EXPLANATION

8106 A dollar amount is not greater than zero within the
Amount must be following transaction types:
greater than zero
• 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 A dollar amount is negative on the following
Amount must be transaction types:
greater than or
equal to $0 • 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 The Total LDAP amount on the LDAP transaction
Amount must be type (RT 401-21) is less than one dollar.
greater than or
equal to $1 RESOLUTION: Ensure that the Total LDAP amount
field includes a value that is greater than or equal to
one dollar.
8110 The sum of all amounts reported on the Repayment
Sum of reported of Grant and/or Bond Transaction Type (RT 401-10)
amounts must be is not greater than zero. This sum may include:
greater than $0
• Grant Repayment Amount
• Bond Repayment Amount
• Grant Termination Adjustment Amount
• Bond Termination Adjustment Amount

RESOLUTION: Ensure that the sum is greater than

zero.

December 18, 2013 Appendix A Page 9 of 28

 Appendix A: Understanding Error Codes

ERROR CODE EXPLANATION

8111 No Grant was previously paid to a beneficiary and a
Grant must have repayment of Grant and/or a Grant Termination
been previously paid 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 A repayment of Bond and/or a Bond Termination
Bond must have Adjustment is being reported on a Repayment of
been previously paid 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 The LDAP and DAP and/or Retirement Savings
Date must be on or Rollover date is before July 1, 2011. This code
after July 1, 2011 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.

December 18, 2013 Appendix A Page 10 of 28

 Appendix A: Understanding Error Codes

ERROR CODE EXPLANATION

8200 The date on the following transactions must be on or
Date must be on or after December 1, 2008:
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 The date reported in a transaction is for a future
Date is of a future reporting period.
reporting period
RESOLUTION: Ensure that date provided is on or
before the current reporting period end date set by
the CDSP.
8203 The date information submitted in a transaction is
Date must be on or before the beneficiary’s date of birth.
after 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.

December 18, 2013 Appendix A Page 11 of 28

 Appendix A: Understanding Error Codes

ERROR CODE EXPLANATION

8204 The Bond Request Date field of a bond Payment
Date must be on or Request (RT 401-05) includes a date that is after
before December 31 December 31 of the year in which the beneficiary
of the year in which turns 49 years of age (ex: If the beneficiary turns 49
the Beneficiary on June 12 2012, the date submitted must be on or
turns 49 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 The transaction contains a date that is before the
Date must be on or RDSP’s Contract Signature Date. Refer to the ITS for
after Contract a complete list of applicable fields.
Signature Date
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 The date information submitted to the CDSP does
Date must be within not occur within the Issuer Agreement and Issuer
Issuer approval Cessation dates. Refer to the ITS for a complete list
dates 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.

December 18, 2013 Appendix A Page 12 of 28

 Appendix A: Understanding Error Codes

ERROR CODE EXPLANATION

8208 The Stop Request Date of a Stop Bond Request (RT
Must be on or after 401-06) precedes the original Bond Request date.
the 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 A Specimen Plan identified in a record is not valid.
Specimen Plan must
be 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 The Authorized Agent is not authorized to send data
Authorized Agent for the indicated Specimen Plan.
not authorized to
send data for the RESOLUTION: Examine the Header Record for the
Specimen Plan 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 The Specimen Plan identifiers submitted to the CDSP
Specimen Plan must are not associated with the issuer BN indicated in
be associated with the transaction. Consult the ITS for the applicable
the Issuer 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.

December 18, 2013 Appendix A Page 13 of 28

 Appendix A: Understanding Error Codes

ERROR CODE EXPLANATION

8230 A Contract Registration transaction package (RT
Contract must not 101-01, 102-02 and 101-03) is submitted for a
already be a contract that already exists.
contract that is
Registered, Closed, RESOLUTION: Ensure that the Contract
De-registered or Registration records refer to the correct Contract
Nullified 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 This error applies to:
The Beneficiary
must not already • a Contract Registration transaction package (RT
have a Pending, 101-01, 102-02 and 101-03) is submitted for a
Registered or De- beneficiary that is currently associated to an
registered contract 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.

December 18, 2013 Appendix A Page 14 of 28

 Appendix A: Understanding Error Codes

ERROR CODE EXPLANATION

8233 A Contract Registration transaction package (RT
The Contract 101-01, 101-02 and 101-03) has been received for a
Signature Date contract which currently has a status of ‘Pending’
cannot change once and the Contract Signature Date is different than the
a contract status is one indicated in original Contract Registration
pending 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 Transfer Indicator is set to ‘Yes’ on a Contract
The other contract information component of a Contract Registration
must be associated transaction (RT 101-01) and one of the following is
with the beneficiary true:
and other Specimen
Plan and must be • the other contract is not associated with the
Pending, Registered, beneficiary reported in this Contract Registration
De-registered or transaction package
Closed • 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 The Contract Number is not associated to the
Contract is not Specimen plan identified within that record and is
currently associated applicable to the following:
to the Specimen
Plan • 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

December 18, 2013 Appendix A Page 15 of 28

 Appendix A: Understanding Error Codes

ERROR CODE EXPLANATION

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 The RDSP contract on a transaction is not associated
Contract is not to the beneficiary SIN reported on the same
currently associated transaction. Refer to the ITS for applicable
to the Beneficiary transactions.

RESOLUTION: Verify the Contract Number and

Beneficiary SIN data submitted to the CDSP. If there
are no errors, contact Issuer Support.
8237 The holder information in the transaction does not
Contract must be match the holder information for that Contract.
currently associated
to the Holder 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 The Contract Registration transaction package does
Contract not include a Contract component (RT 101-01),
Registration and/or a beneficiary component (RT 101-02) and/or
transaction is a holder component (RT 101-03).
missing a
component RESOLUTION: Ensure that the Contract
Registration transaction package contains all three
Record Types and resubmit if required.

December 18, 2013 Appendix A Page 16 of 28

 Appendix A: Understanding Error Codes

ERROR CODE EXPLANATION

8239 Multiple Contract information transactions (RT 101-
Duplicate Contract 01) indicating duplicate Specimen Plan and Contract
Registration in the Number data are received in the same processing
same period 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 Two Contract Registration transaction packages (RT
Only one Contract 101-01, RT 101-02 and RT 101-03) that contain the
Registration request same beneficiary SIN data are received during the
for the Beneficiary same processing period and only one RDSP can exist
in a given period is for each eligible beneficiary. If duplicate Contract
permitted 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 One of the following transactions has been received
Contract must for a contract that is not registered:
currently have a
status of • Update Beneficiary (RT 201-02)
‘Registered’ • 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 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

December 18, 2013 Appendix A Page 17 of 28

 Appendix A: Understanding Error Codes

ERROR CODE EXPLANATION

status of the contract, contact Issuer Support.
8242 The contribution date in the Correction of
The date must be Contribution/Grant Request transaction (RT 401-02)
the same as does not match the original contribution date
reported on the previously submitted.
original contribution
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 The grant requested field in the Correction of
Grant requested Contribution and/or Grant Request transaction (RT
may only change 401-02) is set to N when the original contribution
from ‘No’ to ‘Yes’ 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 The date indicated in the Correction Date field of the
Must be on or after Correction of Contribution and/or Grant Request
the Original transaction (RT 401-02) is prior to the date of the
contribution date 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.

December 18, 2013 Appendix A Page 18 of 28

 Appendix A: Understanding Error Codes

ERROR CODE EXPLANATION

8245 The Contract Number being submitted via the RT
Contract already 102-11 already exists for that Specimen Plan.
exists in CDSP
system 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 The FI submits a Close Contract transaction (RT
Contract must 102-10) for a contract that is not currently
already be a Registered, Deregistered or Pending.
contract that is
Registered, RESOLUTION: Verify if the Close Contract
Deregistered or transaction was submitted in error or contact Issuer
Pending Support to clarify the status of the contract.
8247 A Rename Contract transaction (RT 102-11) has
Contract must been received for a contract that has a status other
already be a than Registered, Closed or Pending.
contract that is
Registered, Closed, RESOLUTION: Verify if the Rename Contract
or Pending transaction was submitted in error or contact Issuer
Support to clarify the status of the contract.
8248 An Add Holder to Contract transaction (RT 201-13)
Contract is already has been received for a contract to which the holder
associated to the is already associated.
Holder
RESOLUTION: Verify that the SIN and Name fields
are for a new holder and are not already associated
to the applicable contract.
8249 A transaction includes a request to remove the only
Cannot remove last holder (RT 201-23) associated to a RDSP.
Holder on the
contract 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.

December 18, 2013 Appendix A Page 19 of 28

 Appendix A: Understanding Error Codes

ERROR CODE EXPLANATION

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

RESOLUTION: Check the SIN against the RDSP

application or validate the SIN with the applicable
individual as well as the BN if required. Make the
correction and then re-submit the transaction.
8251 The beneficiary component of Contract Registration
Beneficiary year of package (RT 101-02) or an Update Beneficiary
birth cannot be transaction (RT 201-02) was received with a year of
modified 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 The beneficiary component of a Contract
Contract already Registration transaction package (RT 101-02) has
associated to been received for a beneficiary with a SIN that does
another Beneficiary not match the beneficiary SIN already associated
SIN 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 A Contract Registration transaction package (RT
There must not 101-01, 101-02 and 101-03) has been received with
already be a a Y in the transfer indicator field of the RT 101-01
contract awaiting and a contract already exists with a status of
transfer in the CDSP Registered, Pending or De-registered and a transfer
system for the indicator of Y for the same beneficiary.
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.

December 18, 2013 Appendix A Page 20 of 28

 Appendix A: Understanding Error Codes

ERROR CODE EXPLANATION

8254 Multiple, conflicting contract transactions are
Conflicting contract submitted in the same period creating duplicate
transactions contract names:
pertaining to the
same contract • two unique Rename Contract transactions (RT
received in the 102-11) in the same processing period and for
same period 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 A transaction cannot be processed because the
Contract must not contract status is nullified.
be nullified
RESOLUTION: Register a new contract or contact
Issuer Support for assistance.

December 18, 2013 Appendix A Page 21 of 28

 Appendix A: Understanding Error Codes

ERROR CODE EXPLANATION

8256 Transactions were received for a contract that is not
Contract is not associated to the RDSP’s Specimen Plan.
associated to the
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 CDSP received a reversal transaction referring
The original to a transaction that has already been reversed in a
transaction must not prior processing period.
have been reversed
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 More than one reversal transaction was received in
There must not be the same processing period for the same
more than one transaction.
reversal for the
same transaction RESOLUTION: No action is required as one reversal
within the current will be processed and the other will receive this
processing period error.
8260 A Transfer Reporting transaction (RT 701-02) has
Contract must have been received for a contract that does not currently
a status of Closed or have the status of either Closed or Registered.
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.

December 18, 2013 Appendix A Page 22 of 28

 Appendix A: Understanding Error Codes

ERROR CODE EXPLANATION

8261 The CDSP received a Contract Registration
The other contract transaction package (RT 101-01, 101-02 and 101-
and Specimen Plan 03) and the following conditions exist:
cannot change once
a transfer has been • transfer indicator is set to Y
successfully • a transfer has been resolved (e.g. the
resolved 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 A rollover transaction has been received that
Specimen Plan must includes a Specimen Plan identifier that has not been
be designated by designated by CRA as eligible to accept rollovers.
CRA 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 A Rollover transaction has been received with a date
Must be within the that either precedes or exceeds the period for which
date range the the designated Specimen Plan is eligible to accept
Specimen Plan is these requests.
designated by CRA
to accept Rollovers RESOLUTION: Contact Issuer Support to clarify the
parameters for this transaction.
8264 An Add Consent transaction (RT 202-01) has been
Must be greater received with a Consent Date that is earlier than the
than the last date provided for a previous Add Consent
Consent transaction transaction.
date submitted
RESOLUTION: Ensure that the Add Consent Date
provided is later than the date of latest Add Consent
activity for that beneficiary.

December 18, 2013 Appendix A Page 23 of 28

 Appendix A: Understanding Error Codes

ERROR CODE EXPLANATION

8265 An Add Consent transaction (RT 202-01) has been
Must not exist as a received for a holder or BN that is already associated
Holder on any to an open or closed contract.
contract of the
reported beneficiary RESOLUTION: No further action is necessary.
8266 A Revoke Consent transaction (RT 202-02) has been
Must already be received that refers to a SIN or BN that does not
recorded as a match an existing consent for the beneficiary. In
consent for the addition, this code can be generated if both a
Beneficiary 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 A Revoke Consent transaction (RT 202-02) has been
Must not be an received with a SIN or BN for an active holder for
active Holder on the which an Add Consent transaction (RT 202-01) has
current Beneficiary been previously submitted.
contract
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 A Revoke Consent transaction (RT 202-02) has been
Beneficiary consent received with the SIN that matches the contract’s
cannot be revoked beneficiary.

RESOLUTION: Consent status cannot be revoked

for beneficiaries of RDSPs. No further action is
required.

December 18, 2013 Appendix A Page 24 of 28

 Appendix A: Understanding Error Codes

ERROR CODE EXPLANATION

8300 A Reversal Request, Contribution Correction or Stop
Date is earlier than Bond Request is dated before the date of the original
original Transaction transaction. This applies to the following record
Date 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 A reversal request, contribution correction or Stop
Error in original Bond request has been received for a transaction
transaction, current that was rejected in error. This applies to the
transaction cannot following transaction types:
be processed
• 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.

December 18, 2013 Appendix A Page 25 of 28

 Appendix A: Understanding Error Codes

ERROR CODE EXPLANATION

8303 The Original Transaction Number contained in one of
Unable to locate the the following refers to a transaction not previously
original transaction 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 The Original Transaction Number on the Stop Bond
Original transaction Payment Request transaction (RT 401-06) refers to
must have been an inactive Bond Payment Request.
designated as the
active 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 A Stop Bond Payment Request transaction (RT 401-
Another Stop Bond 06) has already been successfully processed by the
Payment has CDSP for the original bond request indicated.
already been
requested for the RESOLUTION: If the intention is to stop the original
original transaction 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).

December 18, 2013 Appendix A Page 26 of 28

 Appendix A: Understanding Error Codes

ERROR CODE EXPLANATION

8307 A Correction of contribution/Grant request
A more recent transaction (RT 401-02) has been received with a
Correction correction date that is before the correction date of
transaction is another Contribution Correction transaction already
already associated processed for that transaction.
to the contribution
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 An original transaction and its corresponding
Original transaction reversal transaction have been received in the same
and its reversal processing period.
were found in the
same processing RESOLUTION: Verify the intent of the submission
period and resubmit if required.
8309 The Episodic DTC Election (501-01) transaction date
Date must be on or precedes the Medical Doctor certification date.
after 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 An Episodic DTC Election (501-01) has been received
Beneficiary must not for a beneficiary who has either been ineligible for
be DTC ineligible for DTC or for whom eligibility is undetermined for 5
5 consecutive years consecutive years on or after the year of the
on or after the contract signature date and before the year of the
contract signature processing of the request.
year and before the
year of election RESOLUTION: Verify the DTC Election date and
request processing determine if action is required or contact Issuer
Support to clarify the DTC eligibility of the
beneficiary.
8311 An Episodic DTC Election (501-01) has been received
Episodic DTC for a beneficiary with an existing processed Episodic
election period must DTC election with one or more years in common.
not overlap with an
existing Episodic RESOLUTION: Verify the DTC Election date and
DTC election period determine if action is required.
for the same
contract

December 18, 2013 Appendix A Page 27 of 28

 Appendix A: Understanding Error Codes

ERROR CODE EXPLANATION

8312 An Education Savings Rollover (401-30) has been
Must be on or after received with a date prior to January 1, 2014.
January 1, 2014
RESOLUTION: Ensure the date reported in the
Education Savings Rollover is on or after January 1,
2014.

December 18, 2013 Appendix A Page 28 of 28

RDSP Provider User Guide

A P P E N D I X
Understanding Refusal
B 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).

I n t h is c hap te r

1. Background Information ............................................... B – 3

2. Refusal Reasons .......................................................... B – 4

Table of Contents
1. Background Information .............................................................................. 3
1.1. What is a Refusal Reason? ..................................................................... 3
1.2. How Are Refusal Reasons Reported to Financial Institutions? ..................... 3
1.3. Refusal Reasons Differ from Error Codes ................................................. 3
1.4. Using this Document ............................................................................. 3
2. Refusal Reasons ......................................................................................... 4
 Appendix B: Understanding Refusal Reasons

1. Background Information
This document provides information to assist in understanding Refusal
Reasons. For additional technical information, consult the 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:

December 18, 2013 Appendix B Page 3 of 7

 o Issuer Support: 1-888-276-3632
o Client Services: 1-866-204-0357
o Canada Revenue Agency (CRA): 1-800-959-8281 (E) or 1-800-
959-7383 (F)

2. Refusal Reasons

REFUSAL REASON EXPLANATION

01 All of the beneficiary’s grant/bond entitlement,
Maximum Current including any carry forward entitlement, has been
Entitlement of Grant paid out for the calendar year in which the
/Bond Paid 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 The total amount of contributions (including rollovers)
Lifetime Contribution for a beneficiary has exceeded the $200,000
Limit Exceeded 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 The beneficiary has received the maximum lifetime
Lifetime Limit grant payable of $70,000 or for bond, $20,000.
Exceeded
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.

December 9, 2013 Annex B Page 4 of 7

REFUSAL REASON EXPLANATION
04 The transaction date of the contribution is later than
Age of Beneficiary 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 The specimen plan reported on the bond request no
Specimen Plan not longer has a valid status in the CDSP system. To be
Valid 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 Grant was not requested on a contribution as the
No Grant requested 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 The Social Insurance Number (SIN) reported on the
SIN Not Usable 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 The SIN used on the annual resubmission of a bond
Invalid Beneficiary request is no longer valid as it has been linked to a
SIN 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.

December 9, 2013 Annex B Page 5 of 7

REFUSAL REASON EXPLANATION
19 A grant or bond request has been submitted for a
Contract Not contract that does not have a status of registered.
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 This is a warning message to submit a new bond
Last Bond payment application request because the beneficiary is in his
under this application or her 18th year. If no 18+ application is submitted
– new 18+ Bond bond will no longer be paid.
request required
RESOLUTION: Request that the holder complete a
new 18+ bond application and resubmit the request.
22 The original bond request submitted is no longer
Bond request is active.
not/no longer
designated to attract RESOLUTION: Notify the holder and ask if they
Bond for the would like to continue receiving bond. If yes, submit
Beneficiary a new bond request to reactivate the bond.
24 A correction has been submitted on a contract that
Contract status has a status of closed or de-registered.
conditions for
adjustment of RESOLUTION: Determine if contract has correct
payment not met status and take corrective action. Contact issuer
support if required.
26 The annual resubmission of an active bond request
Bond resubmission occurred after the cessation date of the Specimen
date is not within Plan.
issuer approval dates
RESOLUTION: Verify the Specimen Plan eligibility
with 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 The beneficiary is not a Canadian resident as of the
Beneficiary is a non- day the transaction occurred.
resident
RESOLUTION: Refer the holder to CRA to confirm
the beneficiary’s residency status as of the
transaction date.

December 9, 2013 Annex B Page 6 of 7

REFUSAL REASON EXPLANATION
30 DTC eligibility has not been confirmed by CRA for the
Beneficiary DTC beneficiary in the year which the transaction
eligibility not occurred.
confirmed
RESOLUTION: Refer the holder to CRA to confirm
DTC.
32 DTC eligibility has not been confirmed by CRA for the
Beneficiary DTC beneficiary for two or more consecutive years where
eligibility not an election has not been submitted.
confirmed for 2 or
more consecutive RESOLUTION: Refer the holder to CRA to confirm
non-election years DTC.
33 DTC eligibility has not been confirmed by CRA for the
Beneficiary DTC beneficiary for five or more consecutive years
eligibility not regardless of a DTC election.
confirmed for 5 or
more consecutive RESOLUTION: Refer the holder to CRA to confirm
years DTC.
99 Used only in special cases.
Other
RESOLUTION: Information provided as these cases
occur.

December 9, 2013 Annex B Page 7 of 7

RDSP Provider User Guide

A P P E N D I X

Transaction Types
C
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).

I n t h is c hap te r

1. Objective .................................................................... C – 3

2. Using this Document ..................................................... C – 3

3. Column Descriptions ..................................................... C – 3

4. Finding More Information ............................................... C – 4

Table of Contents
1. Objective ................................................................................................................ - 3 -
2. Using this Document ......................................................................................... - 3 -
3. Column Descriptions .......................................................................................... - 3 -
4. Finding More Information ................................................................................ - 4 -
4.1. RT 101 – Contract Registration ............................................................. - 4 -
4.2. RT 102 – Contract Update ....................................................................... - 4 -
4.3. RT 201 – Beneficiary and Holder Update .......................................... - 4 -
4.4. RT 202 – Consent ....................................................................................... - 4 -
4.5. RT 401 – Financials .................................................................................... - 4 -
4.6. RT 501 – Election ........................................................................................ - 5 -
4.7. RT 701 – Reporting .................................................................................... - 5 -
 Appendix C: Transaction Types

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.

February 5, 2016 Appendix C Page 3 of 10

 Appendix C: Transaction Types

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)

February 5, 2016 Appendix C Page 4 of 10

 Appendix C: Transaction Types

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)

February 5, 2016 Appendix C Page 5 of 10

 Processing that may result from the TT
Files sent by the CDSP system to financial institutions
sent by the financial institution
RT and TT sent by the
Contract
financial institution to the Error
Transaction Status SIN Beneficiary
CDSP system Grant and Grant and File Transfer
Contract Processing 951 Usability DTC
(the 3 digit number is the Bond Bond Re- 801 971
Registration 901 952 921 Eligibility
RT, the 2 digit is the TT) Payments adjudication 851 (.xfr)
(.pro) 953 (.sur) 981
(.err)
(.reg) (.dtc)
Contract If the
01 X X P2 X X X 951
Information transfer is
Beneficiary resolved
101 1 02 X XP X X X X and the
Information
old
Holder contract
03 X XP X X X X
Information is closed
If the Is sent if CRA
X X transfer is has reported a
Close Contract change in the
resolved
(may be beneficiary’s
(Received in (Received in and the
relinquishing 10 X X 951 DTC status to
Transaction Transaction new
102 contract in a the CDSP
Processing File Processing File contract
transfer) system. It is
901) 901) is
registered not sent in
response to a
Rename
11 X X transaction
Contract
type sent by
Update the financial
Beneficiary 02 X X X
institution
Information
Update Holder
03 X X X X
201 Information
Add Holder to
13 X X X X
Contract
Remove Holder
23 X X
from Contract

1
101-01, 101-02 and 101-03 must always be sent as a package
2
“P” Means “potential”
 Appendix C: Transaction Types

Processing that may result from the TT

Files sent by the CDSP system to financial institutions
sent by the financial institution
RT and TT sent by the
Contract
financial institution to the Error
Transaction Status SIN Beneficiary
CDSP system Grant and Grant and File Transfer
Contract Processing 951 Usability DTC
(the 3 digit number is the Bond Bond Re- 801 971
Registration 901 952 921 Eligibility
RT, the 2 digit is the TT) Payments adjudication 851 (.xfr)
(.pro) 953 (.sur) 981
(.err)
(.reg) (.dtc)
If the
transfer is
resolved,
the old
Add or Update contract
951 P
Consent for 01 X X X X X is closed
952 P
202 Beneficiary and the
new Is sent if CRA
contract has reported a
is change in the
registered beneficiary’s
Revoke Consent DTC status to
02 X X
for Beneficiary the CDSP
Contribution If the system. It is
951 P
and Grant 01 X grant X X X transfer is not sent in
952 P
Request resolved, response to a
Correction of the old transaction
Contribution 951 P contract type sent by
02 X grant X X X the financial
and Grant 952 P is closed
Request and the institution
401
new
Bond Payment 951 P contract
05 X bond X X X
Request 952 P is
registered
Stop Bond
Payment 06 X X
Request

February 5, 2016 Appendix C Page 7 of 10

 Appendix C: Transaction Types

Processing that may result from the TT

Files sent by the CDSP system to financial institutions
sent by the financial institution
RT and TT sent by the
Contract
financial institution to the Error
Transaction Status SIN Beneficiary
CDSP system Grant and Grant and File Transfer
Contract Processing 951 Usability DTC
(the 3 digit number is the Bond Bond Re- 801 971
Registration 901 952 921 Eligibility
RT, the 2 digit is the TT) Payments adjudication 851 (.xfr)
(.pro) 953 (.sur) 981
(.err)
(.reg) (.dtc)
If the
transfer is
resolved,
the old
Retirement contract
951 P
Savings 08 X X X X is closed
952 P
Rollover and the
new
contract
is Is sent if CRA
registered has reported a
change in the
Retirement
beneficiary’s
Savings
09 X X DTC status to
Rollover
the CDSP
Reversal
system. It is
Repayment of
not sent in
Grant and/or 10 X X
response to a
Bond
transaction
Reverse
type sent by
Repayment of
11 X X the financial
Grant and/or
institution.
Bond
Disability
Assistance 20 X X
Payment (DAP)
Lifetime
Disability
Assistance 21 X X
Payment
(LDAP)

February 5, 2016 Appendix C Page 8 of 10

 Appendix C: Transaction Types

Processing that may result from the TT

Files sent by the CDSP system to financial institutions
sent by the financial institution
RT and TT sent by the
Contract
financial institution to the Error
Transaction Status SIN Beneficiary
CDSP system Grant and Grant and File Transfer
Contract Processing 951 Usability DTC
(the 3 digit number is the Bond Bond Re- 801 971
Registration 901 952 921 Eligibility
RT, the 2 digit is the TT) Payments adjudication 851 (.xfr)
(.pro) 953 (.sur) 981
(.err)
(.reg) (.dtc)
DAP Reversal 22 X X
LDAP Reversal 23 X X
If the
transfer is
resolved,
the old
Education contract
951 P
Savings 30 X X X X is closed
952 P
Rollover and the
new Is sent if CRA
contract has reported a
is change in the
registered beneficiary’s
DTC status to
Education
the CDSP
Savings
31 X X system. It is
Rollover
not sent in
Reversal
response to a
Episodic
transaction
Disability Tax
01 X X 952 A type sent by
Credit (DTC)
the financial
Election
institution
Episodic DTC
Election 02 X X 952 A
501 Reversal
Specified
Disability
03 X X 953 A
Savings Plan
(SDSP) Election
SDSP Election
04 X X 953 A
Reversal

February 5, 2016 Appendix C Page 9 of 10

 Appendix C: Transaction Types

Processing that may result from the TT

Files sent by the CDSP system to financial institutions
sent by the financial institution
RT and TT sent by the
Contract
financial institution to the Error
Transaction Status SIN Beneficiary
CDSP system Grant and Grant and File Transfer
Contract Processing 951 Usability DTC
(the 3 digit number is the Bond Bond Re- 801 971
Registration 901 952 921 Eligibility
RT, the 2 digit is the TT) Payments adjudication 851 (.xfr)
(.pro) 953 (.sur) 981
(.err)
(.reg) (.dtc)
Monthly Is sent if CRA
Reporting of has reported a
01 X X
Fair Market change in the
Value (FMV) beneficiary’s
DTC status to
the CDSP
701 Transfer system. It is
Reporting of not sent in
FMV and 02 X X response to a
Earnings transaction
Amounts type sent by
the financial
institution

February 5, 2016 Appendix C Page 10 of 10