I am needing to enter a missing receipt affidavit in the Sap Concur App. The instructions I have found say the following:
To create a declaration for your missing receipt within the SAP Concur mobile app follow these instructions:
The problem is that I do not have an option which says "Missing Receipt Declaration".
Can anyone offer the correct procedure?
@Rich_Hinkle Those are the correct steps, so I'm not sure why you don't see that option. Here are a few suggestions:
1. Make sure you have the latest version of the app.
2. Do a hard reboot of your mobile phone.
3. If options 1 and 2 don't work, use the desktop version to see if the option is there.
I looked at your company's site and the set up does have the MRD turned on for both policies that you are assigned. I'm a little befuddled here.
If a receipt of any kind is already attached to an eligible expense, the Missing Receipt Affidavit option will not show as it is not finding an eligible expense. We also have audit rules to prevent certain expense types from allowing the affidavit and a separate audit rule for a $ limit. Audit Rules can make the expense ineligible so the option to select the affidavit does not appear. Maybe there are some audit rules preventing the expense from using the affidavit.
Also, for the expense you are having trouble with, does the same thing happen when you try from the desktop site, or does it work there? Maybe a phone compatibility issue...?
I am having this issue as well. I'm our Concur admin, and I just had to send a report back to an employee so that they could replace their handwritten "missing receipt" images for Missing Receipt Affidavits. They asked me how to do it, and they were using the app. I went into my own app and created a test expense item so I could send them a screenshot, and found that I do not have the option to add a Missing Receipt Affidavit, when trying to follow the instructions the OP was also trying to follow. The employee also sent me a screenshot, and they don't have the option either. They are using iOS, I am using Android. My app is up-to-date, I am not sure about theirs. We are able to add the MRAs using the website. Any ideas why this is working for us on the website but not the app? Thank you!
@mwatford Hard for me to give a concrete answer, but it could be that the expense entry doesn't require a receipt. I looked at your receipt limits and see they are set to $25. So, do you know if the user was trying to attach an MRA to an entry that was less than $25? If so, that is likely the issue. If the entry doesn't require a receipt, I believe the MRA option will not be available.
I cannot test it out myself in your site because the MRA is not available when acting as a Proxy or Delegate.
So, if you can ask the user what the amount of the entry is they are trying to attach the MRA to, we can go from there.
Each of the employee's expenses needing an MRA are over the $25 threshold. Additionally, when I did my own test, I made sure to make my test expense over $25 as well. Also, I detached the images she had originally attached to her transactions, so I know that isn't the issue either. Thank you!
@mwatford Hmmm...I was hoping the amount was the issue. Can you take screenshots of your mobile phone showing that the MRA isn't available, please? If you could show the entry on the expense report with the receipt image required icon, then a screenshot of you drilled into the entry, then a screenshot of the options you have when you press Attach Receipt, that would be great. You should be able to paste the images right here on the Community in your reply. If you don't want to post them publicly, you can send them to me in a private message. Just click on my username (KevinD). You'll see a Message button.
I went in to my app to get the screenshots and found that the MRA is now appearing for me. Since I wasn't seeing it previously and now could, I asked the employee to try again and hers was now available as well. I do have a screenshot she sent me initially showing that the MRA was not listed as an option, but since it all seems to be working now, I think we're good to go. Thank you, I appreciate the help!
@mwatford Great to hear. I guess the app was just having a "moment". 🙂