To assist businesses with the creation of their XML file formatted returns, we show the top problems that cause returns to be rejected. Please review your XML files to ensure they meet all these requirements.
1. Your file name must end with the extension ".xml"
2. The first line of your XML file must appear as:
<?xml version="1.0" encoding=" "?>
Where " " is the encoding used in your XML file. The three allowable character encoding options are Windows-1252, ISO-8859-1, and UTF-8.
Example:
If you used ISO-8859-1, then the first line must be:
<?xml version="1.0" encoding="ISO-8859-1"?>
3. The last line of your XML file formatted return must be </Submission>
Please ensure no characters remain after this tag. Otherwise, the system will reject the submission automatically.
4. All required tags as outlined in the specifications documentation are mandatory and must contain valid data. Do not submit returns with empty required fields.
Example:
Last name Smith:
Format is <snm>Smith</snm>
Required
- maximum of 20 alphanumeric characters
- omit titles such as Mr., Mrs.
- do not include first name or initials
5. We do not accept returns which use XML shortcut tags, for example, <pstl_cd/>
Your validating parser may not detect this tag as an error.
6. When using any of the special characters below in the content area of your XML file, each must be coded exactly as indicated:
If " < " is used in the content area of the tag, enter as <
If " > " is used in the content area of the tag, enter as >
If " " " is used in the content area of the tag, enter as "
If " ' " is used in the content area of the tag, enter as '
If " & " is used in the content area of the tag, enter as &
Example:
Last name Smith & Smith:
Format is <snm>Smith & Smith</snm>
Note
Although the above special characters are entered as four or more characters, they are considered to be only one character when input in the content area of an XML tag.
7. When filing multiple returns within a single XML file, ensure that each return is separated by the <Return> </Return> tags.
Example:
<Return>
<T4>
<T4Slip></T4Slip>
<T4Summary></T4Summary>
</T4>
</Return>
<Return>
<T5>
<T5Slip></T5Slip>
<T5Summary></T5Summary>
</T5>
</Return>
8. Each tag in your XML file formatted return must be coded exactly as indicated in the specification documentation for each return type. An incorrectly spelled tag will result in the rejection of your submission.
9. Before saving your return on DVD, CD, or diskette, use a validating parser in combination with the CRA schema files to ensure your submission is valid and can be processed by the CRA. See magmedia filers validating.
10. Before sending your return to us, confirm the XML file is saved and accessible on the DVD, CD, or diskette. We receive many blank or unreadable DVDs, CDs, or diskettes.
11. For financial tags, enter the applicable tags by entering dollars and cents.
Example:
<empt_incamt>10.00</empt_incamt>
12. Please ensure the report type code on the T619, the summary, and the slips is coded correctly.
Example:
If you are sending original slips, the report type code will
be coded as follows:
- T619 <rpt_tcd>O</rpt_tcd>
- Slips <rpt_tcd>O</rpt_tcd>
- Summary <rpt_tcd>O</rpt_tcd>
If you are sending amended slips, then the report type code will be coded as follows:
- T619 <rpt_tcd>A</rpt_tcd>
- Slips <rpt_tcd>A</rpt_tcd>
- Summary <rpt_tcd>A</rpt_tcd>
If you are sending cancelled slips, then the report type code will be coded as follows:
- T619 <rpt_tcd>A</rpt_tcd>
- Slips <rpt_tcd>C</rpt_tcd>
- Summary <rpt_tcd>A</rpt_tcd>
13. Please ensure to transmit the appropriate file with the appropriate tax year.
