Interface Transaction Standards: Files
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
At the completion of a processing period, the CDSP system will report back to each authorized agent the following file types:
- An error file (.err)
- A transaction processing file (.pro)
- A contract status file (.reg)
- A Social Insurance Number (SIN) Usability file (.sur)
- A transfer information extract file (.xfr)
- A Beneficiary DTC eligibility file (.dtc)
4.1 Error File
This ITS details the format that is required for each transaction type, and provides the authorized agent with the validation rules for those transaction types. If transactions are not submitted in compliance with these formats and validation requirements, the transactions are subject to rejection. Each transaction error, whether due to problems in format or invalid data, is reported back to the issuer or authorized agent for correction and resubmission. This is done electronically via the Transaction Error File.
These transaction errors include:
- Failure to correctly format the file
- Failure to correctly format a transaction
- Failure to supply the necessary information for a mandatory field
- Failure to comply with CDSP system business rules
The Error File contains two different record types, RT “801” - Errors and RT “851” – Severe Errors. A list of error codes can be found appended to this document (Appendix A).
4.2 Transaction Processing File
At the end of each processing period, the CDSP system returns a Transaction Processing File to the authorized agent. The Processing File provides the details of results for all successfully processed transactions submitted (e.g. how much grant and/or bond money was paid in respect of each contribution or bond request, or how much grant and/or bond money was repaid). Every transaction submitted to the CDSP system and successfully processed will appear in this file including those financial transactions which have been processed without grant or bond being paid. A refusal reason will accompany each of the aforementioned transactions which have not received grant or bond. A list of refusal reasons can be found appended to this document (Appendix ‘A’).
The file is the CDSP system’s confirmation to the authorized agent that the submitted transactions were correctly formatted, contained all the mandatory information and passed all the necessary validation rules. The Processing File will also list all contract, beneficiary and holder information transactions that were successfully processed.
Grant and/or bond transactions which have been re-adjudicated (either positively or negatively) are also reported to the authorized agent in the Transaction Processing File. The CDSP system performs re-adjudication on financial transactions under the following situations:
- Contract Registration - Authorized agent resubmission of contract information after the processing of unpaid grant and/or bond requests.
- Contribution Correction - Authorized agent submitted financial transaction releasing grant for previously submitted contributions.
- Retirement Savings Rollover Reversal - Authorized agent submitted financial transaction releasing grant for previously submitted contributions.
- Education Savings Rollover Reversal – Authorized agent submitted financial transaction releasing grant for the previously submitted contributions;
- Contract Closure (Transfer Completed) – Authorized agent transferring out closes contract allowing for the re-adjudication of pending grant/bond for authorized agent transferring in.
- CRA – Reassessment or Update of DTC, Residency, Income and/or Contract Status.
- Episodic DTC Election – Re-adjudication occurs in the event an Episodic DTC Election period is processed and results in an election period which starts prior to grant and bond requests already processed.
The Transaction Origin field (transaction position 68-69 in the 901.pro file) documents the above circumstances allowing for the differentiation of CDSP system-generated transaction records and authorized agent transaction results records.
The processing of an authorized agent’s file(s) results in a series of grant and/or bond payments and repayments. Repayments are netted out from the payments. This generally results in a payment to the authorized agent. The payment will be automatically deposited into the authorized agent’s account according to the banking information supplied to the CDSP system.
The record type 901 – “Transaction Processing File” carries with it an indication of the effect the transaction has on the payment received by the authorized agent. The Payment Requisitioned flag tells the authorized agent if the 901 record is a payment or repayment of grant or bond, to or from the CDSP system. For example, the processing of a contribution transaction would result in the payment of grant to the authorized agent (assuming it passed all the rules and no refusal reason was present). The Payment Requisitioned flag would be set in this case. In the case of a DAP or LDAP there is no money moving between the authorized agent and the CDSP system. The Payment Requisitioned flag would not be set for those transactions. The authorized agent can reconcile all flagged transactions with the payment received from the CDSP system.
4.3 Contract Status File
Each month the CDSP system will process all contract registration information transactions and report back the current status of the contract transaction to the financial institution. In certain circumstances the CDSP system will receive information from CRA that affects the contract registration status of a particular contract. Any change in the contract status (current and/or at contract signature date) will be reported back to the authorized agent with the record type 951 – contained in the “Contract Status File”. If there is more than one change, only the most up to date status will be indicated. The “Reason for Change of Contract Status” field was added to this report in Version 2.0 of the ITS in order to clarify why a contract status has been changed. The “Transfer Status” field was added to this record type in Version 2.1 of the ITS in order to convey the current status of a contract being transferred. Beginning with Version 3.1 of the ITS, the purpose of the Contract Status File is expanded to inform the financial institution of the successful processing of new or updated Episodic DTC elections as well as new or updated SDSP elections.
4.4 SIN Usability File
Each month the CDSP system will verify the integrity of all beneficiary and holder SINs through the Social Insurance Registry (SIR). As a result of this monthly verification, any particular SIN may either be identified (flagged) by SIR as “not usable” or identified (un-flagged) by SIR as “usable”. The CDSP system will report the information regarding the usability status of SINs back to issuers/authorized agents via the record type 921 - SIN Usability File (.sur).
4.5 Transfer Information Extract File
Beginning in January 2013, ESDC will provide to the receiving issuer, all historical transactional information in ESDC’s possession from all previous contracts for a particular beneficiary for all RDSP transfer transactions when following criteria is met:
- a valid close contract transaction must be received from the originating/relinquishing issuer;
- the contract transfer from the relinquishing to the receiving issuer must be resolved; and
- the new contract under the receiving issuer must be registered.
The record type 971 - Transfer Information Extract File(.xfr) will include all information from all prior issuers that can be used by the receiving issuer for the ongoing administration of a particular beneficiary’s RDSP.
The transaction types of the .xfr file are as follows:
- “971-01” - Contribution/Contribution Correction Information.
- “971-02” - Bond Request Information.
- “971-03” - Retirement Savings Rollover/Retirement Savings Rollover Reversal Information.
- “971-04” - Grant/Bond Repayment - Grant/Bond Repayment Reversal Information.
- “971-05” - DAP/DAP Reversal Information.
- “971-06” - LDAP/LDAP Reversal Information.
- “971-07” - Education Savings Rollover/Education Savings Rollover Reversal Information.
The details of each individual transaction type for the RT-971 - Transfer Information Extract File(.xfr) are outlined in Section 11 of this document.
4.6 Beneficiary DTC Eligibility File
Beginning in , the CDSP system will extract and send authorized agents all updated Beneficiary DTC eligibility information via a transaction Record Type “981” – Beneficiary DTC Eligibility file (.dtc). This monthly generated file will report all updates which have been made by CRA to the yearly DTC eligibility status of Beneficiaries who have a pending (having passed Social Insurance Registry (SIR) validation) or registered contract. In transfer situations, this information will be sent to the latest relinquishing issuer if the transfer is unresolved or to the receiving issuer upon resolution of the transfer and registration of the contract.
The Record Type “981” – Beneficiary DTC Eligibility file will also include an annual DTC eligibility status update produced in February of every calendar year providing an update of all Beneficiary DTC eligibility profiles for that calendar year.
The initial file scheduled to be sent during the processing period will report the DTC eligibility profiles of all beneficiaries by year, beginning from the year of the contract signature date to the year the file is produced. It will not provide information for carry forward years or for contracts that have a status other than pending (passed SIR validation) or registered.
Note: The authorized agent will receive a blank file when no DTC eligibility update has been made in that period for any Beneficiaries.
Report a problem or mistake on this page
- Date modified: