As a mandatary, you can correct information in accepted transactions and rejected transactions. Only you can send transactions for these contracts. We cannot send transactions for a contract that you hold. 

Correcting data in a rejected transaction

After a production cycle, an error report (RT12) (.err) may be sent to you. It specifies the rejected transactions and their error codes.

To correct the incorrect data, you simply need to return an original transaction in a new file with the corrected information.

Correcting data in an accepted but incorrect transaction

If you find that a transaction is incorrect after we've accepted it, even though it complies with the standards, you must cancel the original transaction and send us a transaction with the correct information. The new transaction will form the amended transaction.

Rules for amending a transaction

The following criteria must be met for amended transactions:

• Cancelled and amended transactions must be sent in one file. They can be part of a file containing original transactions.
• A cancelled transaction must contain the same information as the transaction to be cancelled, except for the transaction identifier (ID) and the version code, which will be 1.
• All the accepted transactions with the same date as the transaction to be corrected or a future date, for all the contract's beneficiairies, must be cancelled (version code 1) and amended (version code 2) and contain the same data, except for the identifier (ID).
• Type 03, 04, 05 or 06 transactions that are accepted but incorrect can be cancelled (version code 1) without being amended (version code 2).  
• An accepted type 02 transaction sent by mistake must be cancelled (version code 1) and followed by an amended transaction (version code 2) in which the total amount of annual contributions is 0.

Correcting beneficiary information

If you need to change certain beneficiary information (SIN, last name, first name, gender, address, month or day of birth), you do not have to send an amended transaction. Since this information has no effect on the QESI amount granted, you must only include the new information in the next transaction you send us.

However, to modify the beneficiary's year of birth, you must send an amended transaction. This information could have an effect on the QESI amount granted.

Correcting information when a beneficiary or subscriber dies

The death of a beneficiary or subscriber can have financial consequences on the QESI paid into the contract.

Beneficiary's death

A beneficiary's death has no impact on the QESI amount paid into the contract, so you don't have to send us a transaction.

However, a special tax could apply if one of these events occurs:

• The beneficiary is replaced by someone who is not a recognized beneficiary.
• Property is transferred from one RESP to another in an authorized transfer.
• A person who is not a sibling of the plan's other beneficiaries becomes a beneficiary when the plan has already received a QESI increase amount.
• An accumulated income payment (AIP) is made.
• The plan is closed by the subscriber.

For a family contract, the QESI amounts accumulated after the annual claims on behalf of the deceased beneficiary may remain in the contract and be used by the other beneficiaries. The $3,600 cumulative limit is also applied when the educational assistance payment is claimed.

Subscriber's death

A person who is not a blood relative of each beneficiary of a family RESP may, upon the death of an original subscriber to that RESP, acquire their rights as a subscriber to the same plan, provided that each beneficiary was related by blood to the plan's original subscriber.

In November 2021, an addition was made to relationship types. Relationship type “8” (succession) was added so we'd be informed that the original subscriber died and responsibility for the RESP was transferred to another subscriber, even if that subscriber is not a blood relative of each plan beneficiary.

The “Subscriber's relationship type” attribute name was modified in the Annual application for the QESI (type 02), Replacement of a beneficiary (type 03) and Inter-plan transfer (type 04) transactions, in order to add the new relationship type 8 (succession).

The “Primary caregiver's relationship type” attribute name was enhanced in type 02 transactions to add the new relationship type 8 (succession).