Hi SkurtzTPI
Please try the below. Hope it helps.
In SAP Concur Expense Pay, a payment demand taking two days to generate when the payment batches are configured to run daily is a payment-processing delay that warrants investigation.
The key distinction is that a daily batch schedule does not necessarily guarantee that a payment demand will be generated every day. Expense reports must first meet the applicable approval, processing, and payment eligibility requirements.
If Concur Support has already escalated the case, I would focus on identifying exactly where the two-day delay occurred.
- Possible causes
Potential cause | What to investigate |
Batch processing delay | Scheduled payment job started late or failed |
Expense reports not eligible | Reports were not fully approved or ready for payment before cutoff |
Payment processing backlog | Eligible reports waited in the processing queue |
Cutoff or timezone mismatch | Reports became eligible after the daily processing cutoff |
Payment batch configuration | Schedule, payment group, or funding-account assignment |
Bank or employee payment validation | Invalid or incomplete payment information |
SAP Concur processing issue | Internal job failure, service degradation, or delayed demand generation |
These are diagnostic possibilities, not confirmed causes of your incident.
- What to check in SAP Concur
For an administrator with the appropriate permissions:
- Open Expense Administration and locate the relevant Payment Manager / Expense Pay functions.
- Identify the payment batch and its configured processing schedule.
- Compare the report's final approval and processing timestamps with the expected batch cutoff.
- Determine when the report became eligible for payment.
- Check when the payment demand was actually created.
- Review whether other payment batches experienced the same delay.
- Examine any payment exceptions or processing failures.
The available menu names and processing reports vary by Concur edition and Expense Pay configuration.
- Important findings from SAP documentation
SAP's documentation identifies two particularly relevant scenarios:
- Daily batches close at the end of the day, but the batch schedule governs closing and processing; it is not necessarily the timestamp at which each individual payment demand is created.
- Missing banking information at report approval is a documented reason a payment demand may not be generated. SAP provides a controlled manual creation function for eligible reports.
Also, changing a batch schedule may not immediately affect an already-open batch; the old schedule can remain in effect until that batch completes.
- Exact investigation path
For SAP Concur Professional Edition, use Payment Manager → Monitor Batches → View Batches → Payment Demands.
Select the relevant batch, open the payment demand, and review its Audit Trail. Compare it with the expense report's approval and payment history.
Ask SAP Support to provide the following timestamps for affected reports:
- Final approval and payment eligibility
- Payment demand creation
- Batch closure
- Submission to the Expense Pay payment engine
If multiple eligible reports were delayed across different employees and batches, that would strengthen the case for a processing-side issue rather than an individual banking-data problem.
Do not manually regenerate demands or reschedule batches while the incident is under investigation without confirming that duplicate payments cannot result.
Thanks & Regards
--
Samantha Prathikantam
SF_EC & ECP / SAP Concur Consultant
