To successfully get your data to synchronize between your desktop ERP software, and the Beanworks SaaS, we require the installation of a data synchronization tool which we develop in-house at Beanworks. This tool allows us to access the data needed to allow you to accomplish your workflow needs in the SaaS, and needs specific installation requirements to be met in order to enable this functionality seamlessly to the end-user. This document will walk you through the necessary setup required to get the SyncTool up and running.

General Requirements

  • Ensure you have the username and password available for an ERP user with administrator rights.

  • During the Migration meeting, please ensure we have the following access:

**this may require having an IT resource on your side**

  • Access to the server where your ERP/Accounting Solution is located

  • Ability to install the new sync tool through our web application in Chrome on the server

ERP Requirements

The following ERP's and versions are supported by SmartSync. If you currently are not running one of these versions, you will need to upgrade prior to migrating to SmartSync.

ERP

Version

Quickbooks Desktop

2018,2019,2020,2021

Sage 100

2015,2016,2017,2018,2019,2020,2021

Sage 300

2016,2017,2018,2019,2020,2021

Sage 50 US

2021 +

Server Requirements

Typical Environment

Required .NET Version

Minimum Requirements

ERPs Supported

Windows Server 2008 R2

4.5.2

(379893)

300MB HDD

4GB RAM (Sage)

Sage Products:

  • 100 Standard <= 2016

  • 100 Advanced <= 2015

  • 100 Premium <= 2015

  • 50 US 2021

Windows Server 2012 R2

Windows Server 2016

Windows 10

Windows 7

4.7.2 or 4.8 (>=461808)*

500MB HDD

4GB RAM (Sage)

8GB RAM (QBD)

Sage Products:

  • 100 Standard 2016+

  • 100 Advanced 2016+

  • 100 Premium 2018 (please reach out if premium to ensure we are compatible)

  • 300 Premium 2018+

  • 50 US 2021

* If you do NOT have the minimum .NET version installed, your server must be upgraded prior to our Integration meeting. Once updated, you will need to restart the server. Here is the link to upgrade your .NET version

http://go.microsoft.com/fwlink/?linkid=863265

What’s my .NET Version?

To check your .NET version, run Windows Powershell on your server, and then run the following command:

(Get-ItemProperty "HKLM:SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Full").Release

Your .NET version must be above 461808

Firewall Setup

Please ensure that the following traffic is allowed through your firewall to allow our SyncTool to send & receive data to our cloud infrastructure. You can configure your firewall based on domain whitelisting, or application names, depending where your firewall is installed. Domain whitelisting is preferred.

Domain or Service Name

Port or Traffic Type

Notes

sftp.sageapa.com

22000 (SFTP)

Port 22000 is specific to Beanworks

sftp.beanworks.ca

22000 (SFTP)

Port 22000 is specific to Beanworks

beanworks.com

443 (HTTPS Traffic) Outbound

Essentially you need exactly the same rule as you would to allow a web browser to load a website from the server. One of the services that is running has a polling mechanism in it that allows it to read the list of requests that are queued in the web. Without the ability to reach out, the SyncTool will never know when to sync, and in the SaaS, it will look like your requests are never getting acknowledged.

It is not necessary to setup port 80 to be served, we are specifically avoiding anything that allows the outside world to reach into your machine, rather we reach out from your machine.

sageapa.com

443 (HTTPS Traffic) Outbound

Windows Executable - SageSyncTool

443 (HTTPS Traffic) Outbound

Windows Executable - SageAPAutomationsSyncToolServer

443 (HTTPS Traffic) Outbound

Windows Executable - SageAPAutomationsSyncToolClient

443 (HTTPS Traffic) Outbound

Firewall Setup - Auto-Updater

Please ensure that the following IP Addresses are whitelisted in your firewall to allow our AutoUpdater to determine if your SyncTool requires updating. These are the IP addresses for AWS services within Canada (ca-central-1), which is where the servers are that manage version updates. All requests from the Auto-Updater to our servers are port 443 (HTTPS Traffic) Outbound.

"ip_prefix": "52.95.145.0/24"

"ip_prefix": "52.95.146.0/23"

"ip_prefix": "52.92.84.0/22"

Did this answer your question?