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’m trying to find a way to monitor old/unsubmitted P-Card transactions and potentially prevent employees from submitting a new expense report when they still have P-Card transactions older than 60 days sitting in Available Expenses.
Concur Support mentioned that audit rules cannot look at transactions in the Available Expenses section.
Has anyone found another way to achieve something similar?
Ideally, the validation would work like this:
Has anyone implemented something similar? (Please don't say email reminders! haha )
Thanks!
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 @xrorod
Topic: Prevent report submission when employee has old unused P-Card transactions
Please see the below. Hope this helps.
——-
SAP Concur – Preventing Report Submission Due to Old P-Card Transactions
SAP Concur's standard Audit Rules cannot access unassigned P-Card transactions in Available Expenses when
validating a new expense report.
Therefore, they cannot block report submission based on outstanding P-Card transactions older than 60 days.
For a mandatory Submission Block, a custom solution would need to be evaluated with SAP Concur, as this functionality
is not available through Standard Audit Rules.
Actions:
Audit Rules cannot:
Thanks & Regards
—
Samantha Prathikantam
SF_EC & ECP / SAP Concur Consultant
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 @xrorod ,
I haven't worked on P-Card previously; however, I tried creating the below sample audit rule using the available data objects in our test instance.
Could you please configure this rule and test whether it works as expected?
Audit Rule:
Note - Since there is no available data object to identify when a transaction was assigned to an employee, I have used the Transaction Date field as an alternative to determine whether the transaction is older than 60 days. However, this approach may or may not work as expected.
If it doesn't work as intended, you can remove the 60-day condition and retain only the first two conditions, irrespective of the transaction age. This way, the audit rule should trigger whenever there is an unutilized P-Card transaction in the employee's profile.
Exception - Trigger hard stop msg.
If this answers your query, then please mark solution as accepted!
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
@xrorod one thing of note in @PoojaKumatkar example is she used a Corporate Card Payment type. Just be sure you select the P-Card Payment type.
This is actually a pretty common audit rule usually set up for T&E Cards, but it also can be set up for any card payment type you have set up.