Skip to content

Settings and activity

1 result found

  1. 26 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Thanks for confirming, Andy - Really appreciate the screenshot. 🙂

    I've checked in with our Payroll team where this detail is saved.
    We appreciate wanting more options for gender when entering personal details, and in some regions such as AU & NZ this is optional.
    Currently, in order to ensure successful payroll filings with HMRC in the UK, we need to match the schema they provide. That said, our team are reassessing how this fits in Xero so I'll shift this Idea to 'under review' and can share any updates that come.

    An error occurred while saving the comment
    Kanika Selvan 2 commented  · 

    Hi,
    So just reading this thread that looks to rooted in 2022 😳 and still isnt sorted. Wooooow. A complete lack of action... interesting. Often it is said that in-action... we should also note and believe about an organisation. So this isnt a priority for Xero then... when doing payroll.. for human, living people?? Sounds like this is just a choice we should all be believing when making a decision about if Xero is the accounting tool for our organisations.

    I say this because as a person who works in tech, i am horrified by the various different technically inaccurate excuses below, for what can only be a harmful and probelmatic stance and a business choice. Your tech isnt stopping you from fixing it, you are choosing not to prioritise it on your backlog. Our team dont get payslips from Xero, so I can only say im sorry to those that do.

    We will probably leave now, after this. But if it helps... lets dispell some tech myths here shall we, because we wouldnt want technology to been a screen for discriminatory and harmful practice would we????

    1. 'HMRC say we have to' What HMRC requires in their submission, is not ther same as what Xero need to submit and show to people. So the field you have to map to HMRC in the filing.. it doesnt have to be on the employee facing profile. It doesnt constrain the My Details view for employees and you could do what most orgaisations do and choose who sees what and select when they are utilised... if its a bit complicated to do that... then I would say that its worth the time and effort. But it isnt a technical constraint that cannot be fixed.
    2. 'It has to be on the payslip' A payslip display is an employee facing document, its built by Xero and the format is generated by Xero and whilst the submission to HMRC may need to be binary... there is no rule about the payslip. The idea that you present the same data on the UX on the payslip and that it has to align with the HMRC data scheme.... the math aint mathin and someone needs to go and check that again with the people in the back who actually do that data submission.
    3. 'We are forced to align' Hmmm, no. What this means is that even if it is aligned with HMRC and Global, it means that you BUILT your data model to align with it and you dont want to go to do the work to re-design it, when you build it to HMRC and now you would have to change it to do both HMRC submission and align with people and their actual human needs. So you dont want to make other options happen... when in fact this is now international scale impacts. Wowza. It takes work, but lets not pretend on this screen and chat that this is a 'HMRC says no=Xero tech says no'. In reality... this is 'HMRC Says no= Xero decided not to take ownerships of their tech stack and fix it because they didnt prioritise that ticket over in product'. This isnt a full re-write of the data model... unless you have a VERY brittle data model...
    4. 'Add a second field' Even if you couldnt put a third gender on, which to be honest feels like asking for the minimum. If the Xero, UK HMRC and compliance team have really got you on this. Maybe you should take the idea of two fields....one for HMRC and one for everyone else to see. In part you should be backing this final ideas as a compromise, because Im sure, sure ,sure, that someone already suggested that internally and someone who didnt really think that this was worthwhile decided not to bother making it happen. .(not that this would be sufficient for our organisation, i would have expected that you would put the effort across the last 4 years to just deal with this properly instead of thinking that this thread and re-direct was sufficient) i would say that you could hide it from the payslip... so... why hasnt that been done at the minumum.... hmmmmm... is it because your product strategy doesnt care about it??
    5. Lets be real here, inclusion takes effort, it is with care and an honest understanding of disliking this kind of tech smoothing being a way to bat off good people returning and returning and returning to this chat for 4 years in asking for Xero to decide to be on the right side of history. The UX is lazy and you shouldnt have put this down the list because the below escalations are really shameful.

    Lets say it together, shall we... 'We at Xero have not yet prioritised decoupling the employee-facing gender identity field from the payroll filing field.'