Canada Disability Savings Program System - Industry testing guide

1.1 Purpose

The goal of industry testing is to ensure that issuers can provide quality data in the files they are submitting to the CESP for processing by minimizing the number of errored and rejected transactions. In addition, the industry testing process helps financial institutions ensure that their system is ready to report transactions to, and receive transactions from, the CDSP system.

1.2 Scope

This document is limited to the industry testing process and includes criteria for satisfying the related requirements.

1.3 Schedule

Authorized agents can schedule a testing timeframe with the E-Services team at any time. Once a test file has been transferred to the CESP, an email should be sent to the industry testing mailbox at EDSC.CN.PCEE.TESTDEINDUSTRIE-INDUSTRYTESTING.CESP.NC.ESDC@esdc-edsc.gc.ca as outlined in the file submission section of the industry testing process.

1.4 Confidentiality

Test files provided by authorized agents may contain live data such as SIN information and/or financial information and is considered "protected". The data volume information and client specific information is considered competitive information and is treated with confidentiality, as are the test results. Specific information about an issuer, agent or service provider will not be disclosed to any other issuer, agent, or service provider.

All test files must be transferred to the CESP using the secure method specified in the file submission section of the industry testing process. Test files submitted in violation of this security requirement will not be tested under any circumstances.

2.1 File creation

The authorized agent is responsible for creating and sending a file or set of files to the CESP for testing. Service providers must submit separate files for each agent they represent. Filenames should be prefixed with "CDSPT".

Refer to the appendices section for information pertaining to the types and volumes of transactions required for each test.

Note: The method used for creating transactions in industry testing must be the same method used in production.

2.2 File submission

MSFT is the ESDC approved internet connectivity solution software for transmitting files electronically. Files can be sent for industry testing upon successful completion of connectivity testing.

Test files sent through MSFT are not automatically queued up for testing. An email must be sent to the industry testing mailbox at EDSC.CN.PCEE.TESTDEINDUSTRIE-INDUSTRYTESTING.CESP.NC.ESDC@esdc-edsc.gc.ca once the test files have successfully been transferred to the CESP. The email should contain the following information:

• name of issuer, agent, and service provider if applicable
• filename(s) submitted for testing
• name and contact information of individual(s) responsible for submitting data and retrieving results
• specify if live data is included in test files (specimen plan and business numbers provided by CRA must be used for industry testing)
• CDSP release number or ITS version used for testing
• special processing instructions (for example, special test cases such as a simulation of multiple production runs)

2.3 File processing

Each industry test is processed against a non-populated database. The reason for this is to give the agent complete control over the data environment used for testing and to facilitate the interpretation of the results. The agent is responsible for preparing the test environment by submitting a file containing baseline data such as contracts, beneficiaries, and holders to the CDSP system. Subsequent files should be submitted, and will be processed, in the order specified in the appendices section.

The SIR and CRA validation processes are simulated in the test environment and all validation rules are automatically passed.

2.4 Transaction processing results

Transaction volumes and success rates are reported back to the agent in the Production processing results report upon completion of processing the test file(s). Cumulative volumes and success rates will be provided in situations where multiple files were sent and processed in the same cycle.

2.5 CDSP system output files

At the completion of each simulated production run, the following output files will be generated (if applicable) and reported back to the agent:

• an error file (.err)
• a transaction processing file (.pro)
• a contract status file (.reg) (if applicable)
• a transfer information extract file (.xfr) (if applicable)
• a beneficiary DTC eligibility file (.dtc) (if applicable)

Note: Refer to the current version of the CDSP system ITS for a description of the format of the output files.

Once received, the CDSP system output files should be loaded into the authorized agent's system to update the processed transactions and record the CDSG and CDSB amounts in their system.

3.1 Circumstances requiring industry testing

Industry testing is required under the following business and system related circumstances:

• a new RDSP issuer
• the implementation of the education savings rollover functionality
• the implementation of the retirement savings rollover functionality
• the addition of an authorized agent
• a change of service provider
• a specimen plan transfer
• a system update or conversion

Industry testing may also be required for certain business or system related circumstances other than those listed above. The issuer is responsible for contacting the CESP Enrolment team at NC-INSCRIPTION_ENROLMENT-GD@esdc-edsc.gc.ca who in turn will coordinate with the CESP E-Services team. Once informed of the circumstances, the CESP E-Services team will inform issuers of which tests must be conducted.

A repeat of industry testing will be required when submitted transactions are repeatedly generating unacceptable error rates in the production environment. In situations where unacceptable error rates are on-going, the issuer and/or agent may be suspended from sending production files to the CDSP system until such a time as lower error rates are established in industry testing.

3.2 Volume criteria

Transaction volume requirements for the various industry tests are detailed in the appendices section.

3.3 Success rates

Minimum success rate requirements for the various types of industry tests are defined in the appendices section. Success rates are calculated based on the ratio of the number of successfully processed transactions (error is not generated) to the number of processed transactions by transaction type.

4.1 Appendix A: Full test

Appendix A outlines the details of the CDSP transactions required for a full industry testing cycle.

Note: Each file must be successfully tested before proceeding to the next file until all requirements in each file are met.

4.2 Appendix B: Transfer and correction test

Transfer and correction testing may be required under the following circumstances:

• a transfer by plan amendment
• a merger or amalgamation

4.3 Appendix C: Retirement savings rollover test

Appendix C outlines the requirements for the Retirement savings rollover transaction industry testing cycle. The test is broken up into 3 separate files and detailed in the following sections.

Note: Each file must be successfully tested before proceeding to the next until all the requirements in each file are met.

4.4 Appendix D: Education savings rollover test

Appendix D outlines the requirements for the Education savings rollover transaction industry testing cycle. The test is broken up into 3 separate files and detailed in the following sections.

Note: Each file must be successfully tested before proceeding to the next until all the requirements in each file are met.