xrorod
Occasional Member - Level 1

Prevent report submission when employee has old unused P-Card transactions

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:

 

  • Employee has an unused P-Card transaction in Available Expenses
  • Transaction is more than 60 days old
  • Employee attempts to submit an expense report
  • Submission is blocked until the old P-Card transaction is submitted/processed

Has anyone implemented something similar? (Please don't say email reminders! haha )

Thanks!

3 REPLIES 3
samasuraj
Occasional Member - Level 3

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:

  1. Reporting: Use an appropriate card transaction or unassigned expense report in Cognos/Intelligence, where available, to identify P-Card transactions older than 60 days.
  2. Automated notifications: Schedule reports or reminders to employees and managers regarding overdue transactions.
  3. Administrative escalation: Establish a policy to escalate outstanding P-Card transactions after 60 days.
  4. Custom integration: Evaluate an external validation process using supported SAP Concur APIs and transaction data. However, this would not automatically create a native submission-blocking rule.

Audit Rules cannot:

  1. Identify unassigned P-Card transactions older than 60 days outside the current report.
  2. Compare those transactions against the employee submitting a new report.
  3. Trigger a hard-stop validation based on those outstanding transactions.
  4. Prevent submission of an otherwise valid expense report until the old transactions are processed.

 

Thanks & Regards

—

Samantha Prathikantam

SF_EC & ECP / SAP Concur Consultant

PoojaKumatkar
Super User
Super User

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:

  • Event: Entry Save
  • Note - Since corporate card data objects are not available for the Report Save event, Entry Save is the earliest available event to trigger the audit rule and restrict report submission.
  • 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.

 

PoojaKumatkar_0-1794402958089.png

 

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

Thanks!
Regards,
Pooja
KevinD
Community Manager
Community Manager

@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. 


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.