T4 & T4A XML CRA Error Troubleshooting
GOAL: To provide a documented list of T4 and T4A XML errors that occur either from submitting to CRA, or upon running validation of the XML – and the associated steps to reconcile the data.
ISSUE: <cppe_cntrb_amt> or <cpp_cntrb_amt> is negative.
FIX: <cppe> correlates to CPP2, so this implies that the CPP or CPP2 deductions are negative which is impossible and should be reconciled for the impacted Employee.
ISSUE: Province Code has a value of ‘00’ for out of country record.
XML:580570,22: value '00' does not match any member types of the union
FIX: Province code for out of the country can be changed to ‘ZZ’ or noted back to the local province in certain cases.
ISSUE: City Name has a value that has a length which exceeds 28 characters.
XML:304325,48: value 'Mount Albert, East Gwillimbury' has length '30' which exceeds maxLength facet value '28'XML:304325,48: value 'Mount Albert, East Gwillimbury' has length '30' which exceeds maxLength facet value '28'
FIX: Shorten the city name code for all instances where this is happening.
ISSUE: Address has a length that exceeds the maximum of 30 characters.
XML:309936,63: value '4_ _________ ____. West, Mississauga' has length '35' which exceeds maxLength facet value '30'
FIX: Shorten the address in all instances where it is applicable to be below the maximum character value of 30.
ISSUE: The Initial value is NULL, when this must be populated.
XML:233060,14: value '' does not match regular expression facet '\p{L}{1}'
FIX: Populate the Initial value in all instances where it is NULL.
NOTE: The<init> line is not required, if the line is removed the .XML file should not error - however, if it is present then the Initial value must be populated.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article