In this guide we will be taking a generalised look at our distributed connectors. These are pieces of software designed to communicate between our iCompleat solution and your ERP/Accounting Software.
What is a Distributed Connector?
A distributed connector refers to a software component or middle-ware that enables communication and data exchange between different systems or applications in a distributed computing environment. It acts as an interface or bridge that facilitates the seamless flow of data and interactions across multiple nodes or endpoints within a network.
In this instance, the connector is bridging the gap between iCompleat and your ERP/Accounting Software, sending relevant data to, and retrieving data from each to optimise your purchasing requests and account payable process.
Which ERP/Accounting Software can I connect to?
We currently support connections to the following ERP/Accounting Software:
Click on the accounting software name to see the guide to each connector.
How does it work?
For the connector to work, it needs to communicate with both iCompleat and your ERP/accounting software with a “2-way” connection. This ensures it can read and write data to and from each application. This communication will always be initiated from the connector installed on your systems.
If your ERP/accounting software is hosted on a system that cannot access the internet, the connector will need to be installed to your DMZ for it to communicate with our web service.
The connector must be able to communicate with the following in our Azure Relay.
- Destination address:
If your firewall supports DNS approval listing, please add an entry for:
If you are unable to use a wildcard in your firewall rule, please add:
In this case you will also need to allow the gateway addresses for our namespace, which can be found by using this PowerShell script.
It is important to note that although the IP address of the Relay is fixed, the additional addresses found with the above script can be changed from time to time without warning by Microsoft. For this reason, we recommend using the wildcard rule option if your infrastructure allows.
If you need to explicitly define IP addresses, we recommend you routinely check these with the script linked above.
Here’s a diagram of an example of our connector being used to connect iCompleat to a local Sage 50 deployment.
What if my ERP/Accounting Software version is no longer supported?
Unfortunately, if your ERP/accounting software provider has ceased supporting your version of their software, then we cannot offer support for the connection. You can tell if your connection is no longer supported in your iCompleat settings, each connection is split into supported and unsupported. In the case that you need support for an unsupported accounting software version we recommend that you upgrade your ERP/accounting software so we can best solve your issues.