This content from the SAP Concur Community was machine translated for your convenience. SAP does not provide any guarantee regarding the correctness or completeness of this machine translated text. View original text custom.banner_survey_translated_text
I assume the system will flag claims that are a perfect match but what happens if someone manually enters a different date or claims a different amount?
For example submits the credit card receipt and also claims the detailed restaurant receipt on another claim.
Can anybody provide some insight into what it would catch and what it won't?
Thanks
Solved! Go to Solution.
This content from the SAP Concur Community was machine translated for your convenience. SAP does not provide any guarantee regarding the correctness or completeness of this machine translated text. View original text custom.banner_survey_translated_text
@DonMichon Hello! Here is the criteria that SAP Concur looks at for Duplicate Transactions:
This content from the SAP Concur Community was machine translated for your convenience. SAP does not provide any guarantee regarding the correctness or completeness of this machine translated text. View original text custom.banner_survey_translated_text
@DonMichon Hello! Here is the criteria that SAP Concur looks at for Duplicate Transactions:
This content from the SAP Concur Community was machine translated for your convenience. SAP does not provide any guarantee regarding the correctness or completeness of this machine translated text. View original text custom.banner_survey_translated_text
Hi Melanie
Is there a way to prevent same receipt being claimed by several employees?
In other words, does the Duplicate Transaction Check audit rule only run on the claimant?
Thanks
Geoff
This content from the SAP Concur Community was machine translated for your convenience. SAP does not provide any guarantee regarding the correctness or completeness of this machine translated text. View original text custom.banner_survey_translated_text
This content from the SAP Concur Community was machine translated for your convenience. SAP does not provide any guarantee regarding the correctness or completeness of this machine translated text. View original text custom.banner_survey_translated_text
I would like to know solution for this
This content from the SAP Concur Community was machine translated for your convenience. SAP does not provide any guarantee regarding the correctness or completeness of this machine translated text. View original text custom.banner_survey_translated_text
@shreekarra this rule looks at the individual's expense reports and looks at the details entered, not the receipt attached.
This content from the SAP Concur Community was machine translated for your convenience. SAP does not provide any guarantee regarding the correctness or completeness of this machine translated text. View original text custom.banner_survey_translated_text
@Geoff1 yes, the rule only evaluates the claimant. It does not look across a number of employees' claims.
This content from the SAP Concur Community was machine translated for your convenience. SAP does not provide any guarantee regarding the correctness or completeness of this machine translated text. View original text custom.banner_survey_translated_text
@Geoff1 I replied to your private message! Let me know if we can help further 😁
Melanie
This content from the SAP Concur Community was machine translated for your convenience. SAP does not provide any guarantee regarding the correctness or completeness of this machine translated text. View original text custom.banner_survey_translated_text
In our case, the issue arises from different reimbursement amounts. When a user purchases items in a foreign currency using a corporate credit card, the bank converts the amount using their exchange rate. However, when the user submits a cash claim, Concur converts the amount using a different exchange rate. Consequently, even though the transaction currency and amount remain the same, the reimbursement amount differs due to the varying exchange rates used. This discrepancy makes it difficult for Concur's audit rule to detect and for Concur auditors to identify duplicate (auditors only have visibility on approved/reimbursement amount), even if both transactions are submitted in the same report.
This situation can be frustrating as it is a common issue, and we end up having to recover the duplicate amounts from the user. Fortunately, our in-house post-payment analytic tools have flagged these duplicate claims by cross-checking both the transaction and reimbursement amounts.
We have raised this issue multiple times with Concur regarding the lack of duplicate checks, but no action has been taken thus far. I have submitted an improvement request for this case and would greatly appreciate your support and votes to help enhance our processes to prevent duplicates at pre-payment stage. You can vote for the improvement request at the following link: https://influence.sap.com/sap/ino/#/idea/320669
Thank you for your support!
This content from the SAP Concur Community was machine translated for your convenience. SAP does not provide any guarantee regarding the correctness or completeness of this machine translated text. View original text custom.banner_survey_translated_text
Hi all,
I need your input on an issue I've encountered. I came across duplicate expenses that were not flagged as duplicates because the amounts differed due to variations in the distances calculated by the mileage calculator. In such cases, is there an option to check the destination along with the same date?