Paycom

Bring your people data from Paycom into MuchSkills. Your Paycom administrator gives MuchSkills read-only access, and we map the fields and run the sync. The set-up is part of your MuchSkills implementation.

Updated

Custom integrationAdmins and HRIT

Who
Your Paycom administrator, with our CTO
How it connects
Custom set-up, part of your implementation
Sync
Every 5 hours, or on demand with Sync Now
Access
Read-only

How it works

PaycomRead-only access to the people in scope
Read-only, HTTPS, every 5 hours
MuchSkills readsMaps your field names, blocks sensitive data, applies your scope
Each sync
Your workspacePeople, managers, departments and tags, kept current

MuchSkills reads from Paycom on a schedule. New starters, leavers, manager changes and department changes arrive at the next sync, with no manual work on either side. Nothing is written back to Paycom.

Before you start

  • A Paycom administrator on your side, or your Paycom implementation partner.
  • A list of who should be in MuchSkills: everyone, or a selection by country, company, department or worker type.
  • Your field names. Paycom installations name custom fields differently, so have your field list to hand for the technical session.

Steps

In Paycom

Paycom does not publish its API or a developer portal, so access is arranged through your Paycom representative. The details below can vary with your agreement, and your representative can confirm them.

  1. Ask Paycom for API access. Contact your Paycom representative and ask for read-only API access to employee data for an integration with MuchSkills. Paycom may ask for a short call or a non-disclosure agreement first.
  2. Limit it to the employee data in scope. Ask for the employee endpoints only: names, work email, position, manager, department, status and location. Keep sensitive data such as social security numbers, bank details and pay switched off.
  3. Allow the connecting IP addresses. Paycom accepts API calls only from approved IP addresses, so the addresses MuchSkills connects from must be added to your allow list before Paycom issues the credentials.
  4. Note your connection details. The API SID and token that Paycom issues, the list of endpoints that are switched on, and the companies or locations the access covers.

With MuchSkills

  1. Send us the connection details. The credentials and connection details from the steps above, your field list and your scope, through a secure channel we agree.
  2. Join the technical session. Your Paycom administrator and our CTO map the fields and test the connection together.
  3. Check a first sync. We sync a handful of people or one department. You check their names, managers, departments and any tags in MuchSkills.
  4. Widen the scope. We switch the sync on for everyone in scope. From then on it runs every 5 hours.

Check it worked

  • Team/Org › Members lists the people in scope.
  • The people in scope have an invitation to create their MuchSkills profile.
  • Managers see their direct reports in My Circle.

What you get

  • Paycom stays the source of truth. People data is entered once, in Paycom, and MuchSkills follows.
  • A skills layer on your HR system. Skills, certifications and project history sit next to the people records you already trust.
  • Clean data for planning. Reporting lines, departments and tags arrive ready for filtering, gap analysis and Team Builder.

Important to know

What syncs. Only name and email are required. Sync as many of the other fields as you can, because each one makes MuchSkills more useful.

FieldNeededUsed for
First and last nameRequiredProfiles, search, every view
EmailRequiredMatching and sign-in. Must be the address people sign in with
Job titleRecommendedProfiles, roles, Discover
ManagerRecommendedReporting lines, My Circle, reports. MuchSkills maps it from Paycom automatically
DepartmentRecommendedDepartments and filters
Employee statusRecommendedDeactivating leavers
Location or countryRecommendedFilters and scoping
Profile photoRecommendedProfiles and the org chart
Worker typeRecommendedFiltering, for example employee or contractor
AbsenceRecommendedAvailability in Team Builder and My Circle. Dates and percentages only
Other fieldsOptionalAny field can become a filterable tag, for example legal entity, team or cost centre. Agree them with us first

Data MuchSkills does not accept. These are blocked when data arrives and never stored, even if the source includes them: age or date of birth, salary or other compensation data, performance ratings, and political, religious or health data.

Who is included. Limiting what the integration user can see in Paycom is the preferred way, so nothing outside your scope leaves your system. The fallback is a country filter in MuchSkills; records outside it are ignored and not stored. Your security or compliance team decides which fits your rules.

Leavers are deactivated, not deleted. Project history and certificates stay on record.

Our IP addresses. MuchSkills always connects from the same two addresses: 13.51.77.53 and 16.170.107.61. If Paycom or your network limits access by IP address, add both to the allow list.

Troubleshooting

What you seeWhyWhat to do
Some people are missingThey are outside what the integration user can see in Paycom, or outside the scope filterCheck the integration user's permissions and the scope
Managers are missing or wrongThe manager is outside the scope, or has no manager set in PaycomCheck that every manager is in scope and that reporting lines are filled in in Paycom
A person appears twiceTheir Paycom email differs from the address they signed up withAlign the email in Paycom, then contact support
Paycom refuses the connectionPaycom accepts API calls only from approved IP addressesAdd 13.51.77.53 and 16.170.107.61 to your Paycom allow list
The sync stoppedThe credentials expired, or the integration user was disabled or lost permissionsRenew the access in Paycom and send us the new details securely
Paycom is not listed in MuchSkills, or shows as Contact us. Can we still connect it?

Yes. Paycom is connected as a custom set-up rather than from a form, because every installation is configured differently. Email support@muchskills.com or use the chat, and we book the technical session.

Do we need middleware or an integration platform?

No. MuchSkills reads directly from Paycom over HTTPS. Your team only creates the read-only access described on this page.

Can we leave out some countries, companies or groups?

Yes. The preferred way is to limit what the integration user can see in Paycom, so only people in scope ever leave your system. If that is not possible, MuchSkills can filter by country as records arrive and ignore the rest without storing them.

Can we test with a few people first?

Yes. The first sync can be limited to a handful of people or one department. You check the result, then we widen the scope. There are no separate test tenants.

How often does it sync?

Every 5 hours. An Owner or Admin can also run a sync at any time with Sync Now.

What happens to people who leave?

They are deactivated at the next sync, never deleted. Their project history and certificates stay on record, which matters for compliance.

Do you import absence reasons?

No. If you sync absence, MuchSkills takes only the dates and the percentage of time away. Reasons such as sick leave are never imported.

How do we send the credentials safely?

Through a secure channel we agree with you in advance, such as a password manager share. Never by plain email.

Checking Daniel’s calendar...

Ask us anything

A real person replies, usually the same working day.

Live webinar · 13 Oct, 17:00 CEST

How to analyse the Skill Gaps in your organisation

MuchSkills allows organisations to conduct an in-depth skills gap analysis in a matter of minutes and uncover the skill gaps that hurt organisational performance In this webinar, you will learn how t…