Unable to enter the number 6!

[MistJJ]

Hi,

In the series of bugs and headaches with Concur, I am unable to correct the incorrect amount proposed after taking a photo of an invoice. The number 6 entered on my phone systematically displays a - sign instead of the 6, which is therefore impossible to enter! I've turned off my phone, turned it back on, and restarted the app without success. I've cleared the cache, cleared my phone's cache, uninstalled the app, reinstalled it, turned my mobile data off and on again, but the problem persists!

All other numbers work fine except for 6! (I have no problem entering it, for example, on my phone's calculator!).

So what can I do to resolve this problem that's preventing me from completing my expense report?

Thank you for your help.

[PoojaKumatkar]

Hi @MistJJ ,

This must be some mobile app bug. Time being you can use below workaround to complete your expense report.

• Log in to Concur via the web from a desktop or mobile browser.
• Upload and edit your expense from there.

Note: Changes made on the web will sync with your mobile app.

Regarding issue, can you please try below:

Check whether the issue with "6" happens:

• Only in the amount field after OCR (invoice photo),
• Or also when entering manual amounts or text fields elsewhere in Concur.

With this we will get to know whether this is OCR issue or some mobile keyboard issue or any other issue.

if issue still persists, then you can reach out to your company Concur Administrator and ask them to raise a support ticket with Concur and provide below details:

Mention:

• Your phone model and OS version
• App version
• The issue (number 6 converts to "-" only in amount fields)

If this answers your query, then please mark solution as accepted.

[KevinD]

@MistJJ well, you get the prize for most interesting issue of the month. 🙂

I couldn't recreate the issue, so I'm not sure if it is an app issue or something else. I've posted internally to our mobile team to see if anyone has come across this issue. It's the first time I've had someone report it, so I am not sure it is an issue we have ever come across before. 

If I hear back from the mobile team, I'll let you know.