Browser behaviour differences for Expense type in fluid

The Payroll Department (PrePay Auditors) have been in touch that a number of expenses are being submitted with the incorrect expense type - in this case VISA. Yes whilst the users should select the right one there appears to be browser behaviours at play and was wondering if anyone had a similar experience?

Env: FSCM 9.2.017 PT 8.55.05. This is pre the expenses redesign in PUM 019.

User creates an expense header via fluid interface and clicks to add a line, in some browsers the expense type and associated entry fields are defaulted to a value when user selects expense date.

In Firefox and Chrome the Expense Type is being filled with the last item in the Expense Type drop-down list in our case this is Expense Type: VISA - this then changes the entry field on the expense to support VISA Expense Type requirements and users are completing fields and including say Lunch in description.