Interface Transaction Standards: File Submission

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

2.0 File Submission

When submitting electronic files, each authorized agent is required to use a unique identifier that will identify their files to the CDSP system. The CDSP system uses the "Business Number" (BN) as assigned by CRA as the unique identifier. The authorized agent BN will appear in the transaction file name and in the header and trailer records of the file. The issuer BN will appear in each individual transaction within the transaction file. It is essential that each individual issuer transaction number is unique to the issuer BN. If two or more authorized agents are submitting transactions for an issuer, the issuer is responsible for ensuring that the authorized agents do not use the same issuer transaction number.

Before submitting any file for processing, the authorized agent must pass "industry testing". This is a process to verify that the authorized agent can provide the proper information in the correct format to the CDSP system. If a "service provider" is submitting files on behalf of two or more authorized agents, each one of those authorized agents must pass "industry testing" using their own data.

2.1 File Format Overview

Authorized agents can submit one or more files for processing in any reporting period. The file name is structured to allow several files to be reported on a given day or for a given period. In addition to the authorized agent BN and the file date, a file number is added for further distinction. The file number need not be in any specific order. It exists solely to make multiple file names unique for files sent on the same day.

The file itself must conform to a specific structure. A file must consist of a header record (record type 001) followed by the transaction(s) formatted as specified below in this document, with a trailer record (record type 999) at the end. Failure to follow this structure will result in rejection of the file.

Any files the CDSP system receives from an authorized agent after the data delivery cut-off date will be held and processed in the next reporting period, unless otherwise notified. The authorized agent is responsible for ensuring that files arrive in a timely manner to be processed within a particular processing period.

2.2 Record Format Overview

Once all certification requirements are met, it is necessary for the authorized agent to inform the CDSP of all relevant activity concerning the RDSP. All activity must be reported to the CDSP system electronically as follows:

  • Contract registration information, which is used to establish the contract, beneficiary and holder information for purposes of registration.
  • Information updates and changes relating to the non-financial aspects of the RDSP, such as beneficiary and holder information (personal), contract information and consent information.
  • Financial transactions such as Contributions, Requests for Grant or Bond, Retirement Savings Rollover and Reversal, Education Savings Rollover and Reversal, Grant/Bond Repayment and Reversal, Disability Assistance Payment (DAP), Lifetime Disability Assistance Payment (LDAP) and their Reversals and Contribution Corrections.
  • Election transactions, which report occurrences of Episodic DTC and Specified Disability Savings Plan (SDSP) elections.
  • Reporting transactions, which are utilized to report Fair Market Value (FMV), and Contract Transfer Information.

Transactions submitted to the CDSP system are categorised by record type and transaction type. Contract registration information is reported using a record type 101, while changed or updated information to previously registered contracts is reported using a record type 102 (contract) or 201 (beneficiary and holder). Information adding or revoking consent for residency, DTC eligibility and income validations at CRA is reported utilizing record type 202. All financial transactions fall into record type 401. Record type 501 is utilized for SDSP elections and Episodic DTC elections. A record type 701 includes all reporting transactions. Within each record type there are one or more transaction types.

When the CDSP system receives a file for processing, the format and content of each transaction is validated (see each record type as described in this documentfor layout format and validation rules). If transactions are not submitted within the guidelines outlined, the transactions may be rejected and the authorized agent will be responsible for performing the necessary corrections and resubmitting the data. The authorized agent will receive confirmation of acceptance in the processing files that the CDSP system sends back to the authorized agent. If any transaction is rejected, it will appear in the error file identifying the nature of the error.

2.3 Transaction Reporting Sequence

Transactions must be submitted in a logical sequence. A contract must achieve a status of "registered" via the submission of contract registration information before any update or change transactions (RT "201" – beneficiary and holder update information) can be processed. As well, the CDSP system must have received contract registration information before any financial transactions (RT "401" – Financial Transactions) can be processed. While transactions may be in any order in the submission file, the CDSP system will process all transactions in the following order; Contract Registration Information (RT101-102), Update/Change Information (RT-201), Consent Information (RT-202), Elections (RT 501), Financial (RT 401) and Reporting Information (RT 701).

2.4 Timeliness of Transaction Processing

In Budget 2012, the requirements that new contracts are reported within 60 days, that contributions and bond requests are reported within 180 days and that transfers be completed within 120 days, were removed. These were replaced with a requirement that the issuer act without delay in reporting these transactions.

2.5 Reporting Period Cut-off Date

The CDSP system will process files and pay grant and/or bond on a monthly basis. Schedules with processing dates (transaction periods, file submission cut-off and grant and/or bond payment dates) will be sent out to the authorized agent via ListServ (an electronic notice) on a periodic basis. Reporting periods extend from the first day of the month to the last day of the same month. Authorized agents are given four business days after the reporting period ends to finalize their file(s) to be sent for processing. Authorized agents are not to include any transactions that occurred after the last day of the reporting period.

2.6 Transaction Formats

There are several transaction formats that will be used to report information to the CDSP system. These formats are outlined in detail in the Transactions Format section of this document. The CDSP system implementation date for each defined transaction is listed in the Transactions Format section as well.

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: