hmrc / design-patterns

Documenting HMRC design patterns

http://hmrc.github.io/assets-frontend/

MIT License

32 stars 4 forks source link

Match an organisation to HMRC records #28

Open rpowis opened 7 years ago

rpowis commented 7 years ago

Screenshot

rpowis commented 7 years ago

Do we need a pattern for this? And is it an HMRC or a government-wide pattern?

stevenaproctor commented 7 years ago

@gavinwye Unsure this is a pattern, especially when you consider different company types with different details. This is more like an arrangement of components.

adamliptrot-oc commented 7 years ago

Looks to be handled by https://github.com/hmrc/business-customer-frontend

gavinwye commented 7 years ago

Assessed as being Useful and Unique but more work is needed and a lot of work may have been done in this business matching service so we should progress this at some point.

thanksparc commented 6 years ago

Research update. This very pattern is actually used by at least 5 services in the business area. I got in touch with all the user researchers, and they are gathering information for us. What I got from them so far is that the pattern is working well for users.

Some important points that you need to know:

the full pattern includes a page that is shown when the company can't be matched. I'll upload a screenshot.
the pattern can change slightly depending on the type of company: limited company, sole trader, or overseas company.
the make this pattern usable, it's paramount to tweak the form validation with fuzzy matching. This makes easier to match what users type with the information that HMRC hold.

vickytnz commented 6 years ago

back in the day, Genine (the UR at the time on AWRS and ATED) wrote up notes about the work we'd done with the UTR https://paper.dropbox.com/doc/UTR-Unique-Taxpayer-Reference-number-guidance-ffwJmBDiiOwNjAPI0dLyW

stevenaproctor commented 6 years ago

This issue has been closed because it is part of a business-matching microservice that other services can use. This can be documented later when needed. It may also be documented by different components, like company name, unique taxpayer reference number and others.

jennifer-hodgson commented 6 years ago

@stevenaproctor - do you have an update on why this one is re-opened, w/ regard to the business-matching microservice mentioned above?

jennifer-hodgson commented 6 years ago

On the GOV.UK Design System backlog.

stevenaproctor commented 6 years ago

@jennifer-hodgson It was reopened because there are multiple versions of this floating around. It is a service pattern and different from the GOV.UK Design System backlog.

jennifer-hodgson commented 6 years ago

OK. Is it so different it doesn't count as a variant?

stevenaproctor commented 6 years ago

Company details gets someone to confirm business details so they can register for a service. A bit like ID verification. I think it is a different thing based on similar ideas.

torydunn-hmrc commented 5 years ago

Good to see it is in progress, as services need a consistent pattern to ask for these details.

Liam-Macarthur commented 1 month ago

The design pattern for Asking for company registration number I believe is currently introducing an A11Y issue where all input fields should have a label. As of now this design has a input field with a hint above it but these should then link to a label similar to the screenshot above from Jan 31 2017. There you can see that both input fields have a corresponding label with a hint linked to this.