Hi - we have the duplicate transaction rule turned on and I submitted a case for a duplicate airfare between 2 reports. It should have flagged on the same date, expense type, and dollar amount. (airfare on Feb. report that was not being flagged but same airfare on paid Jan. report) Part of the case 27282911 suggestion was to turn on the audit rule for duplicate ticket #. We have since deactivated that audit rule as it was flagging unexpected non duplicates. The original case was submitted and not resolved for a true airfare duplicate.
Has anyone else had an issue with a true duplicate on 2 reports? 
Thanks
Hi @eileenkline ,
It is possible that the duplicate transaction check rule was not triggered because the February report was not submitted.
Please refer to the duplicate transaction check conditions below. It is possible that one of the conditions may not have been met.
- The expenses are on the same report or separate reports that have been submitted and not returned to the user
- The reimbursement amounts of the transactions match the variance condition defined in the audit rule
If required, you can create a dummy report in your admin profile and try to satisfy all of the conditions to check whether the rule is triggered. If it works, it will confirm that one of the conditions was not met in the February report.
If this answers your query, then please mark solution as accepted.
@eileenkline question for you...I was looking at one of the reports in question. I noticed in the Audit Trail that you had made a change to the city field for the airfare on 01/15/2026. Is that correct?
Was this change done by you acting as a Processor?
Also, I looked at the February expense report as well, but I didn't see an airfare with the same amount or date. Were there changes made to the airfare expense on the February report?
Thank you,
Kevin
SAP Concur Community Manager
Did this response answer your question? Be sure to select “Accept as Solution” so your fellow community members can be helped by it as well.
Hi @eileenkline ,
It is possible that the duplicate transaction check rule was not triggered because the February report was not submitted.
Please refer to the duplicate transaction check conditions below. It is possible that one of the conditions may not have been met.
- The expenses are on the same report or separate reports that have been submitted and not returned to the user
- The reimbursement amounts of the transactions match the variance condition defined in the audit rule
If required, you can create a dummy report in your admin profile and try to satisfy all of the conditions to check whether the rule is triggered. If it works, it will confirm that one of the conditions was not met in the February report.
If this answers your query, then please mark solution as accepted.
@eileenkline also, it might not have been triggered if the report was submitted then returned and then changes were made.
The rule is likely working correctly, it might be that for this one employee the circumstances of report changes and submission was what the rule not trigger.
Thank you,
Kevin
SAP Concur Community Manager
Did this response answer your question? Be sure to select “Accept as Solution” so your fellow community members can be helped by it as well.
