Connecting SAP Concur to your ERP and HRIS

    An SAP Concur project often succeeds or fails on its integrations: employee data, master data, accounting exports, payments and card feeds. Bratsi masters SAP Concur data models and APIs, and has delivered integrations with the leading ERPs and HRIS on the market.

    An integration project? Let's talk for 30 minutes

    The integrations we deliver

    ERP: SAP S/4HANA, SAP ECC, SAP Business ByDesign, Oracle (including JD Edwards), Microsoft Dynamics

    HRIS: SAP SuccessFactors, Workday and other HRIS, to create and update employee records

    Corporate cards: Amex, Visa, Mastercard transaction feeds

    Master data: cost centers, analytical dimensions, suppliers, purchase orders

    Methods: standard connectors, Concur APIs (Web Services) or flat files, depending on your architecture

    ERP migration

    Changing ERP requires reworking the entire integration with SAP Concur: export formats, master data and accounting rules. For example, we migrated SAP Concur ERP integration configurations from Oracle JD Edwards to SAP S/4HANA for an international wine and spirits group.

    Project examples

    International wine and spirits group

    migration of ERP integrations from Oracle JD Edwards to SAP S/4HANA

    International hotel group (more than 8,000 employees)

    integration architecture via Concur Web Services

    Frequently asked questions

    API or flat file: which should you choose?

    APIs allow real-time exchanges and greater control. Flat files remain simple and robust for scheduled flows. The right choice depends on your ERP, HRIS and teams. We help you make it from the scoping phase.

    Can you integrate SAP Concur with a non-SAP ERP?

    Yes. We have delivered integrations with Oracle, Oracle JD Edwards and Microsoft Dynamics.