Finance
Sage 100 Contractor
Jobs, cost, employees on the register, and the payroll records the books need. This is where the company already knows who worked, on which job.
uKonnect - Bridge
Sage 100 Contractor and ADP
Finance is in Sage. Payroll is in ADP. Bridge connects them.
The job, the cost code, and the books live in Sage 100 Contractor. The paycheck, the taxes, and the filing live in ADP. uKonnect - Bridge moves employees and payroll between those two systems so the same person and the same pay are entered once.
Two systems, on purpose
Contractors keep both. Sage 100 Contractor prices the work and tracks what a job costs. ADP runs payroll and stays current on tax. The gap is the person who copies one into the other.
Payroll
ADP
ADP Workforce Now, RUN Powered by ADP, or ADP Vantage HCM. This is where pay is calculated, withheld, and filed. The worker record and the pay input have to match Sage.
What gets typed twice
The person
A hire, a rate change, a termination, or a rehire is entered in Sage 100 Contractor and again in ADP. When the two registers drift, the next paycheck or the next job cost is wrong.
The pay
Hours and earnings start in Sage. ADP has to receive them to run the cycle. When ADP finishes, those dollars have to land back in Sage so labor on the job matches what was paid.
This is the same problem ADP’s own Sage 100 Contractor integration was written for: stop maintaining the employee and the payroll result in both systems by hand. Other connectors in this market sell the same promise. One register. Pay sent across. Payroll posted back.
What that copying costs
This is arithmetic for a 25-person crew paid every week. It is an illustration you can redo with your own headcount. It is not a survey.
43 hrs
Copying the hours
25 people × 2 minutes, every week, is 50 minutes a payday. Across a year that is about 43 hours spent retyping time that already exists.
26 hrs
Posting payroll back
Half an hour after each weekly cycle to put the finished payroll into Sage is about 26 hours a year. Until that happens, job cost does not match the paycheck.
8 hrs
The employee changes
Ten hires, rate changes, or terminations a month, typed a second time at 4 minutes each, is about 8 hours a year. A mismatch here is how the two registers drift.
Added together, about 75 hours a year of copying for that crew, before anyone spends time finding the row that does not match. A larger crew or a second company scales the same minutes.
What Bridge moves
The Windows app reads Sage 100 Contractor, maps the fields, and talks to ADP. You can review the mapping before a record is sent. Credentials stored on the PC are encrypted with AES-256-GCM.
- 1
Employees, Sage to ADP
The Sage employee register becomes ADP worker data, so payroll is not rebuilding the roster by hand.
- 2
Employees, ADP to Sage
Changes that happen in ADP write back to the Sage employee register, including the ADP associate id.
- 3
Payroll, Sage to ADP
Sage payroll records for the period go to ADP as pay data, so ADP can calculate the cycle.
- 4
Payroll, ADP to Sage
Processed ADP payroll comes back into Sage payroll records, so the books reflect what was paid.
Built for the ADP products contractors already run
ADP Workforce Now
Current version of ADP Workforce Now. Workers and payroll move through the ADP APIs.
RUN Powered by ADP
The same employee and payroll bridge for companies on RUN Powered by ADP.
ADP Vantage HCM
The same bridge for companies on ADP Vantage HCM.
On your Windows PC
Windows 10 or 11, 64-bit. 4 GB RAM. 500 MB free. A 15-step setup checks the Sage connection, the ADP connection, and the field map.
Ready to connect the two?
Download uKonnect - Bridge for Windows. ADP authentication is required. A free trial is available.