KamoCRM + Paylocity

Approved KamoCRM hours into Paylocity with job costing

Paylocity logo
Start freeBook a demoView Pricing

Overview

Paylocity takes approved hours from KamoCRM with labor allocation attached, so time arrives costed rather than as a lump total. The connection is scoped to the company IDs you name — several, if your Paylocity account is structured that way — and the employee directory syncs in on work email so the CRM roster follows payroll. Because Paylocity is particular about how time files are shaped, the setup asks you to confirm the file mapping before the first push, which is a deliberate stop rather than an oversight.

Common use cases

Approved hours pushed to Paylocity

Timecards that clear approval push to the companies you have scoped, without an export step in between.

Costed time, not just totals

Labor allocation travels with the hours so Paylocity reporting can attribute time to the job or cost centre.

Several companies from one CRM

Name more than one Paylocity company ID and the sync covers each, which suits groups running multiple entities on one Paylocity account.

Directory matched on work email

Employees sync from Paylocity and match on work email, so a hire is entered once rather than in both systems.

Setup

  1. 1Open Settings → HR → Payroll Provider Setup in KamoCRM
  2. 2Choose Paylocity and select the environment
  3. 3Enter the credentials issued for your Paylocity account
  4. 4List the company IDs the sync should cover
  5. 5Choose the push target and how employee IDs should be matched
  6. 6Confirm the file mapping — the first push is held until you do
  7. 7Set employee time zones where they differ from the organization default
  8. 8Run the connection test, then push one pay period to confirm

What data syncs

Approved time entries, pushed per pay period
Time entries pulled back from Paylocity for reconciliation
Employee directory with work-email matching
Labor allocation on pushed hours

Questions about Paylocity

Why does setup ask us to confirm a file mapping?
Paylocity is strict about the shape of an incoming time file, and a wrong mapping is discovered at the pay run rather than at push time. The confirmation is a deliberate gate so the first push is checked by a person.
Does it read pay periods and PTO balances?
No. Those two are not part of the Paylocity connection — the pay period calendar and PTO balances are read from the vendors whose APIs expose them. Hours push, time pulls back, and the directory syncs.
Can one connection cover several companies?
Yes. List each company ID during setup and the sync covers all of them.
What about employees in different time zones?
Per-employee time zones can be set where they differ from the organization default, so hours are attributed to the correct day.
What happens to an unmapped earning code?
The sync reports it and names the code rather than dropping the hours. Map it once and re-run the period.

More integrations like Paylocity

ADP Workforce NowPush approved KamoCRM timecards into ADP Workforce NowBambooHRApproved KamoCRM timecards and directory sync with BambooHRDayforceApproved KamoCRM hours into your Dayforce namespaceGustoSend approved KamoCRM timecards straight to Gusto payroll

Connect Paylocity with KamoCRM — free forever. No credit card required.

Start free

Ready to connect Paylocity?

Start your free KamoCRM account and connect in minutes.

Start freeSee all integrations