UI: SIN/ITN and Tax Residency (Add a beneficial owner)

[Apt766525]

Design Ticket
UI Design - SIN/ITN and Tax Residency (Add a beneficial owner) #17965

Two separate, unrelated groups (see details in wireframes):

• CRA Tax Number as one input (SIN, ITN, or TTN)
• Tax Residency

Instructions

• Data source:
  SIN Validation : Refer document for rules.
  https://docs.google.com/document/d/11IxIqIIBg2bmSESIe2-RSHRZj4zmF1Sx/edit?usp=drive_link&ouid=100179527247507750986&rtpof=true&sd=true

SIN Validation: https://en.wikipedia.org/wiki/Social_insurance_number

Question for Policy: if we use SIN as unique, do we want to know it even if you pay tax in another country?
Answer = YES

General SIN info
https://www.tbs-sct.canada.ca/pol/doc-eng.aspx?id=13342

[steveburtch]

Hey team! Please add your planning poker estimate with Zenhub @hfekete @kialj876 @patrickpeinanw

[Apt766525]

@steveburtch @forgeuxGH5 Updated ticket with SIN / ITN Validation document

[gunanagar]

This is fixed now. Thanks
@patrickpeinanw - Can you check this difference in text between design and actual UI.

[gunanagar]

@patrickpeinanw SIN # shall be separated by a hyphen (-), but allowed here. Pls refer below

• Created a separate ticket SIN # - Additional Validations (Add a beneficial owner) #18554

[gunanagar]

Should not accept 000 000 000 , Please check

[gunanagar]

This is will be fixed in later stories.

Highlighted mismatches between Figma wireframe and the application

1. Display message is incorrect when CRA text field is not selected . Pls refer Figma design -
   https://www.figma.com/file/C2ThYIhZSO44dYBVGp8xAj/Register-Beneficial-Owners?type=design&node-id=1470-22&mode=design

2.Place holder text is not highlighted when CRA text field is selected

[patrickpeinanw]

Should not accept 000 000 000 , Please check

000 000 000 is supposed to pass the validation check. At the component level, we are only checking if the user input is a 9-digit string with acceptable combination.

Maybe this can be handled in the future when users submit the form and we can call some API to verify if the input is an actual tax number.

[forgeuxGH5]

@patrickpeinanw @gunanagar based on the SIN validation doc linked in the description a SIN can't start with 0 - is that not true?

[patrickpeinanw]

@patrickpeinanw @gunanagar based on the SIN validation doc linked in the description a SIN can't start with 0 - is that not true?

I need access to that google doc. A request has been sent.

For now, the only validation check is based on the Luhn Algorithm described in that wikipedia link. According to that link, tax numbers starting with 0 are CRA-assigned individual tax numbers, temporary tax numbers or adoption tax numbers.

[Apt766525]

@patrickpeinanw Shared access.

[patrickpeinanw]

@forgeuxGH5 @gunanagar Based on the google doc, I will:

1. fail the validation if the first digit is 8
2. fail the validation if "000 000 000" is entered, even if it can pass the checksum check.

Question: do we need to allow 0 to be the first digit? It might be a valid TTN?

[Apt766525]

@patrickpeinanw The rules are valid for TTN too. 0 cant be the first digit.