Integrations · Accounting
ControlBoard and Sage 100 Contractor
ControlBoard® reads clients, jobs and employees from Sage 100 Contractor, so the schedule runs on the jobs and
people your accounting team already keeps. Sage 100 Contractor runs on your own server, so a small Windows
service, the ControlBoard agent, reads it there with a read-only login and sends the records in. It only
calls out: no port is opened on your network. Sage 100 Contractor stays the system of record, and approved
hours leave ControlBoard as a payroll file.
What flows where
Your system keeps the money. ControlBoard runs the work.
The agent reads whole tables in an update window you choose, every night by default, and whenever an administrator asks.
Sage 100 Contractor
Clients, jobs, employees, payroll, job cost and the ledger. The agent reads only the tables it is allowed to.
Into ControlBoard
- Clients as customers
- Jobs
- Employees as people
ControlBoard®
Schedules the labor and equipment, tells the field, collects the hours and keeps job cost and the forecast live.
Getting connected
Your administrator installs the agent on the Sage server with a one-time code.
Give the agent a read-only Sage 100 Contractor login limited to the tables it reads.
Allow the server to call out on port 443; nothing calls in.
Review the first match, then let the agent keep the lists in step.
Common questions
Do we have to open our firewall?
No. The agent only calls out, on port 443, to ControlBoard. No port is opened on your network, and the agent reads Sage 100 Contractor with a read-only login.
Who controls the agent's updates?
Your server’s administrator. Updates run in a window you set, or by hand, and ControlBoard never forces one. The card in ControlBoard shows the agent’s version and when it last checked in.
What happens if the server is off?
Nothing is lost. The agent catches up at its next check-in, and whoever set it up gets one email per outage.