Financial Advisory Blog

Armanino’s Financial Advisory blog is your source for thought leadership around cloud ERP and accounting solutions and integrations. Supported by the Cloud Accounting Institute and numerous experts in cloud, finance, reporting, integration, compliance, and technology, Armanino’s Financial Advisory blog features must-read content on what’s happening in the finance industry, case studies, white papers, and much more.

August 9, 2017

The Process of Configuring an Integration Pack from Armanino

Posted by Niromal Perera

You’ve just purchased an Armanino integration pack to sync your key applications. So what happens next, after the statement of work (SOW) is signed?The Process of Configuring an Integration Pack from Armanino (Image of street signs in many directions)

At this point, it is up to the delivery team to execute the project. Usually, integration packs are bundled together with a software implementation project, which means there are two teams working with you in a joint project engagement. The implementation team would get in first and work closely with you to configure your ERP or procure-to-pay solution, for example, and bring on the integration team shortly after that.

The real trigger for the integration team to begin work is when you and the implementation project manager have a detailed understanding of the data you are working with and how the business processes function. Being able to understand the data and the business processes are what drive the requirements phase of the project, and the requirements are what drive the build-out of the integration solution.

Once you have signed off on the requirements, the integration team begins the design and configure stage of the project. Typically, this stage lasts anywhere from 4-6 weeks, with weekly calls to provide you with updates and discuss any issues that have come up. The more standard the requirement set is, the more the design and configure stage runs like a well-oiled machine. (This is the benefit of pre-built integration packs.) After the configuration is built out and tested internally, the team sets up a meeting with you to work on a walk-through of the product, as well as training, so that you can test the integration pack on your own.

Typically, there are holdups during the testing phase because of “dirty” data, meaning data that does not match up between systems. For example, employee IDs in Concur are not the same as they are in Sage Intacct, so it takes extra time to go in and clean up the data for a smooth integration.

The user acceptance testing (UAT) phase is the final hurdle before we can deploy to production and go live with the integration. During this phase, you complete end-to-end testing of the solution. With most of the issues buttoned up during the internal testing phase, UAT phases usually go quickly. Once you have signed off, we run one final test to make sure everything looks good. After that, we celebrate, and transition you to Armanino’s support team.

Your integration pack includes year-round support as part of the subscription fee. You are set up with a JIRA account, to log and track issues, and assigned a client manager to help with anything you need post go-live. This level of support helps you continue to maximize the ROI on your solutions.

Learn more about Armanino’spre-built and custom integration pack capabilities in the Armanino Marketplace.

« | »