Objective Our client is a leader in Hospitality Services and part of an international Group. The Asia Pacific marketing department team selected a CRM package to be used by Sales staff across the business. This CRM package was not affiliated with their ERP software and there was no OOTB integration. It was quickly identified that creating and maintaining two separate …
Solving Out Of The Box API limitations
Objective Our client had an existing, simple integration in place between their ERP and a Field Service software package. They wanted to expand on this integration, but the integration methods provided by the Field Service software had changed. Instead of “pushing” data changes to the ERP, they now only provided Webhook subscriptions. The client’s ERP software was unable to manage …
Rectify and Expand simPRO to ERP Integration
Objective Our Construction-industry client had a pre-existing integration built between simPRO and their ERP system. This integration had been built by their ERP vendor for them and was reliant on having IBM middleware in place, hosted by their ERP vendor. We had been involved in the original work to develop process and data translation for the integration and at the …
Construction AP Automation
Objective Our Construction-based client chose to to implement the SAP Concur Invoice system and integrate it to their Enterprise Management software. The integration required a two-way feed, sending Supplier Account details and Purchase Orders from their ERP to Concur Invoice, and approved invoice data from Concur Invoice back into their ERP. They were aware that most AP Automation software is …
Facilitation of ERP Software Selection in a Multi-System Environment
Objective Our client, a market leading provider of critical maintenance services to the oil and gas sector in Australia, New Zealand and the Middle East, recognised the business risk their internally developed operational and financial systems posed. After a Big Four consultancy market review was delivered, we were engaged to present options for implementing a yet to be selected, market …
Concur Expense Management Integration
Objective Our client had decided to implement the Concur Expense Management system and wanted to integrate the software to their Enterprise Management software. Integration for them meant the ability to automate the dynamic selection lists in Concur, as well as send the approved expense claims and corporate credit card reconciliations for payment into the ERP. We were engaged to build …
Supply Chain / Logistics Systems Review
Objective A fashion brand was stuck on a very old version of their legacy ERP, waiting several years for Global Head Office to fit them into an ERP upgrade project. In order to fill process gaps, they had previously added several peripheral systems to their main ERP. All the systems were connected through manual integration, with minimal automated integration. They …
Development of ERP to Field Service Software Integration
Objective A national service business decided to implement an industry-specific service software solution, as a complement to their current company-wide ERP system. In particular, the service system would provide the capability for field service mobility. The new system would provide the service front end, while the ERP would provide the financial and reporting back end. Management realised that in order …
You must be logged in to post a comment.