SAP Concur S/4HANA integration is often the most technically demanding workstream in an SAP Concur deployment – and one of the most underestimated.
When implemented properly, it creates seamless data flow between SAP Concur and your ERP landscape. When designed poorly, it introduces manual reconciliation effort, fragmented processes, and operational complexity that undermines the value of T&E automation.
This guide explores how SAP Concur integrates with SAP S/4HANA, where challenges commonly emerge, and how organisations can plan effectively from the outset.
Why Native Integration Matters
Historically, SAP Concur integrations often relied on middleware platforms such as MuleSoft, Dell Boomi, or SAP PI/PO to transfer and transform data between systems.
These approaches work, but maintaining an additional middleware layer introduces cost, monitoring overhead, and architectural complexity.
To simplify this, SAP provides the Integration Connector for SAP (ICS), which enables prebuilt integration capabilities between SAP Concur and SAP ERP landscapes, including S/4HANA.
For many standard scenarios, ICS significantly reduces the need for custom middleware.
However, “native” does not mean “plug-and-play”.
Your:
- Chart of accounts
- Cost centre structures
- Organisational hierarchies
- Approval workflows
- Tax mappings
- GL structures
still require careful design (data mapping) and alignment. This is where implementation experience becomes critical.
The Four Core Integration Interfaces
Employee Import
Employee and organisational data must flow into SAP Concur to determine:
- User creation and maintenance
- Approval structures
- Cost allocations, etc.
Data may originate from systems such as SAP Success Factors, Workday, HCM or alternative HR platforms and can be transferred using APIs or SFTP integration + flat files interfaces depending on the landscape design.
Failures within employee imports often create approval bottlenecks, inactive users, or incorrect organisational assignments.
List Import
Reference data from S/4HANA is imported into Concur, including:
- Organisational hierarchies
- Cost centres
- Project codes
- Work or Internal orders
Within ICS-enabled landscapes, these imports can leverage SAP-delivered integration content and ERP-side enhancements.
Import frequency should align with organisational change rates. Dynamic structures may require daily updates, whereas more stable environments may support weekly schedules.
Financial Posting
Approved expense reports ultimately need to post back into S/4HANA with:
- Correct GL mappings
- Expense Header level information
- Expense Entry level information
- Expense Allocation related information
- Tax treatment
- Currency handling and many more fields
This is where integration complexity increases significantly.
Expense types, tax logic, currencies, and country-specific accounting requirements all require alignment between SAP Concur and S/4HANA.
Multi-country deployments introduce further complexity due to local accounting structures and differing regulatory requirements.
Payment Confirmation
Once reimbursements or cash advances are processed in S/4HANA, payment status can be returned to SAP Concur to complete the end-to-end audit trail.
This ensures employees and finance teams have visibility from expense creation through to payment completion.
SAP ICS vs Middleware vs SFTP: When to Use What
For S/4HANA environments, SAP ICS is typically the preferred approach for standard interfaces such as:
- List imports
- Financial postings
- Payment confirmations
The framework is SAP-delivered, designed specifically for ERP integration scenarios, and helps reduce implementation effort.
File-based approaches, including SFTP, continue to play an important role for batch integrations and data exchange scenarios.
Middleware platforms such as MuleSoft, Dell Boomi, and SAP PI/PO remain valuable where:
- Non-SAP applications are involved
- Complex transformation logic is required
- Multiple systems need orchestration
- Broader enterprise integration architecture exists
For S/4HANA customers, however, minimising unnecessary integration layers generally reduces long-term complexity.
In one large-scale 18-country Concur deployment delivered by FinTrans Solutions, SAP ICS supported the majority of core Concur integration points, significantly reducing middleware dependency.
Planning Integration for RISE with SAP
RISE with SAP shifts S/4HANA into a cloud operating model, but integration planning remains equally important.
While core integration principles remain unchanged, organisations should also consider:
- Network architecture
- Authentication methods
- Security design
- Data residency requirements
- Cloud connectivity considerations
The key principle is simple:
Plan SAP Concur integration and RISE migration together.
Designing against the future-state landscape avoids unnecessary redesign work later and creates a more scalable architecture.
Common Integration Mistakes
Treating Integration as a Phase Two Activity
Integration architecture should be designed after fill Concur functional design sign-off and developed alongside functional configuration in an overlapping/ agile approach.
Leaving integration until late stages compresses testing cycles and frequently delays go-live.
No Monitoring or Error Management
Monitoring, alerts, and exception handling should be incorporated early.
Without them, failed transactions can remain unnoticed and create downstream reconciliation issues.
Skipping End-to-End Testing
Testing individual interfaces is not enough.
Complete scenarios should be validated end-to-end:
Employee creation → expense creation & submission → approval → posting → reimbursement → payment confirmation.
This provides confidence that the process functions correctly under real operating conditions.
Getting It Right
When SAP Concur and S/4HANA integration is implemented effectively, employee structures remain aligned, expense data flows automatically into finance systems, and reporting becomes more accurate and timelier.
FinTrans Solutions has designed and delivered SAP Concur integrations across complex, multi-country and multi-entity landscapes using SAP-native integration approaches and tailored architectures.
If you are planning a new implementation or redesigning an existing integration landscape, it is worth evaluating the architecture early rather than solving issues after go-live.
Frequently Asked Questions
Does SAP Concur connect to S/4HANA without middleware?
Yes. SAP Concur integrates natively with S/4HANA through SAP ICS for financial posting, list import, and payment confirmation. Employee import from SuccessFactors uses SFTP, also direct with no middleware required.
What is SAP ICS and how does it work with Concur?
SAP Integration Content Suite (ICS) is SAP’s native integration framework. Its preconfigured BAdI connectors enable automated data exchange between Concur and S/4HANA for list imports, financial postings, and payment confirmations without third-party middleware.
How often should employee data sync between SuccessFactors and Concur?
Daily for high-growth organisations or those with frequent restructures. Weekly is sufficient for more stable workforce structures.
What is SAP ICS in SAP Concur integration?
SAP Integration Connector for SAP, or ICS, provides prebuilt integration capabilities between SAP Concur and SAP ERP landscapes, including SAP S/4HANA.
Is SAP Concur-S/4HANA integration plug-and-play?
No. Even with native integration tools, organisations must carefully align chart of accounts, cost centres, approval workflows, tax logic, GL structures, and organisational hierarchies.
When should middleware be used for SAP Concur integration?
Middleware is useful when non-SAP applications are involved, complex transformation logic is required, multiple systems need orchestration, or enterprise architecture already depends on middleware platforms.
Why is end-to-end testing important in SAP Concur integration?
End-to-end testing validates the full process from employee creation and expense submission through approval, posting, reimbursement, and payment confirmation.