By Morgan Nimmons on May 9, 2016 2:00:00 PM
In part 1 and part 2 of this blog series, we discussed the process of executing an integration project between an ERP and an eCommerce store and how it differentiated from a CRM and Marketing Automation integration. The point of this series is to emphasize that Integration projects differ by software, company and business processes and specialist integrations such as with Concur, ZenDesk or TrackTraceRx are unique integration projects in and of themselves.
Concur is an expense management solution software that provides better control of travel and expenses within companies. With a business process management solution such as TaskCentre, Concur can be integrated with existing business systems such as accounting, and ERP systems.
Concur’s sequence of actions typically look like this:
When we perform a discovery evaluation of a Concur integration with a new prospect, we usually have a conversation with the company’s accounting team and discuss what their process is for handling an expense after it has been approved in Concur:
• What rules are set in place for how expenses are tracked?
• Will an accounting system or ERP software like SAP manage the expense claim?
So what happens when a prospect wants an integration with a software that we haven’t worked with? We perform a Proof of Concept.
A Proof of Concept usually goes like this:
• The prospect wants to know whether their ERP or CRM solution can connect with another system such as Zendesk API using TaskCentre as the tool to leverage the connection.
• We then set up a simple process to see if we can get data flowing between the two systems, using an evaluation to complete the proof of concept.
Our tool is very flexible and there are many API's that we can work with to perform almost any integration, but when we have not worked with an application before we want to provide enough of a solution so that we can be sure our prospective customer gets the solution that they need.
In this three part series, we explained the various steps that are taken when executing an integration project. The takeaway we wanted readers to get from this was to that no two integrations are the same and we treat every project and customer as a distinctive case.