TABLE OF CONTENTS

• How Paycom integration works in Fieldclix
• What syncs and in which direction
• How records are matched between systems
• The capture folder
• Sync details by object
  • Employees (Paycom file → FCX)
  • Payroll Items (Paycom file → FCX)
  • Payroll Costs (Paycom file → FCX)
  • PTO balances (Paycom file → FCX)
  • Export Build Plans (FCX → file)
  • Export Hours (FCX → file)
• Configuration and support
• Questions & Answers

What this article covers: how Fieldclix connects to Paycom through file-based integration — which Excel or CSV files are used, which FCX records they update, and how records are matched. Delivery is typically through a configured folder (often populated by scheduled reports or SFTP drop); Fieldclix scans that folder on a schedule.

Direction key: ⇨ into FCX | ⇦ out of FCX (file export)

How Paycom integration works in Fieldclix

Unlike API-based payroll systems, Paycom integration is file-driven:

1. Paycom (or your payroll team) places Excel reports in a capture folder Fieldclix can read.

2. Scheduled sync jobs parse those files and update FCX.

3. For payroll closure, FCX may export CSV or Excel files out to the same or another folder for Paycom to import.

There is no live Paycom API in the standard integration service. Correct file names, column headers, and delivery timing are essential.

Typical lifecycle:

1. Reference data into FCX — employees and payroll items from Excel

2. PTO balances into FCX — from a PTO balance report

3. Jobs and hours out of FCX — optional file exports at payroll closure

4. Cost actuals into FCX — cost rate Excel matched to payroll checks after Paycom processes payroll

What syncs and in which direction

Automated scheduled flows cover Employees, Payroll Items, Payroll Costs, and PTO Balance. Export Build Plans and Export Hours are separate export actions (manual or scheduled) that write files for Paycom.

How records are matched between systems

After the first successful import, FCX stores a link in the External Links table.

First-time matching (before a link exists):

Once linked, later imports use the stored link. Terminated employees who were never synced are skipped on first import.

The capture folder

Fieldclix integration reads from a capture folder path configured for your tenant.

• Employees and PTO: the integration picks the most recently modified file whose name contains the configured keyword (for example Employees.xlsx, PTOBalance.xlsx).

• Payroll items: expects an exact file name (default PayrollItems.xlsx) in the folder root.

• Payroll costs: searches for files matching the payroll check pay date and a configurable keyword (default Cost_Rates), for example 20250615*Cost_Rates*.xlsx.

Files are read from the folder root only (not subfolders). Your implementation team configures the folder path and file naming conventions. Reports are often delivered by scheduled export from Paycom or SFTP/file drop into that folder.

Sync details by object

Employees (Paycom file → FCX)

Direction: Paycom file → FCX only.

Source file: Excel employee report (default keyword Employees.xlsx).

Key columns and mapping:

Important behavior

• Pay frequency and payroll profile must match a configured payroll period mapping or the row fails.

• If supervisor is not linked yet, the employee may be processed again on a later run after the supervisor syncs.

• Paycom is the HR source of truth; FCX changes do not write back to Paycom.

Payroll Items (Paycom file → FCX)

Direction: Paycom file → FCX only.

Source file: PayrollItems.xlsx with two sheets:

• Deductions → FCX payroll items with item type Deductions

• Earnings → FCX payroll items with item type Earnings

FCX matches by existing link, then by abbreviation, before creating a new payroll item.

Payroll Costs (Paycom file → FCX)

Direction: Paycom file → FCX only.

When it runs: For payroll checks waiting to sync from payroll, when a matching cost file is present in the capture folder.

File naming: {YYYYMMDD}*{FileNameKeyword}*.xlsx where the date is the check pay date (default keyword Cost_Rates).

Row mapping:

Prerequisites: Employee and payroll item links must exist. Employees on the check without rows in the file are logged as missing.

Result: Cost data imports into the payroll check as Cost Rates (same outcome as other payroll systems’ cost import).

PTO balances (Paycom file → FCX)

Direction: Paycom file → FCX only.

Source file: Latest *PTOBalance.xlsx* in the capture folder.

Employee must already be linked. Unlinked employee codes are skipped with an error.

Export Build Plans (FCX → file)

Direction: FCX → file for Paycom setup.

Purpose: Export active build plans so job/detail codes can be loaded into Paycom before hours export.

Output: Jobs.xlsx with columns such as:

This is a one-time or periodic export script, not part of the automated import schedule. Output path may be the capture folder or a path chosen at run time.

Export Hours (FCX → file)

Direction: FCX → file at payroll closure.

When it runs: For payroll checks marked ready for sync to payroll.

Output: CSV file per check, named {PeriodTypeCode}-{PayDate}.csv, written to a configured folder.

Typical content (layout can be client-specific):

• Employee number

• Payroll item abbreviation

• Hours or quantity (wage and non-wage allocations)

• Tax code (when applicable)

• Company code and build plan reference (combined job key)

After a successful export, the payroll check is marked synced to payroll. Company code and period-type mapping are configured per client in the export script.

Configuration and support

Paycom integration — capture folder path, file names, payroll period mappings, employee category, location type, cost file keyword, and export scripts — is set by the Fieldclix Implementation team. End users do not configure file integration in the FCX UI.

Coordinate with your payroll team on:

• Which Paycom reports to schedule

• How files are delivered to the capture folder (manual copy, network share, SFTP, etc.)

• Timing: employee and item files before payroll; cost files after Paycom processes the check

Questions & Answers

Q: Does Fieldclix connect to Paycom through an API?

A: No for the standard integration. Data moves through files in a configured folder. Export at closure also produces files for Paycom to consume.

Q: What is the main employee match key?

A: Paycom Employee Code is stored in the external link. Before a link exists, FCX may match by Clock Seq # = FCX Employee Number.

Q: Why was my employee file ignored?

A: Check that a file matching *Employees.xlsx* exists in the capture folder and is the newest matching file. Verify required columns and payroll period mapping.

Q: Why were payroll costs not imported?

A: Common causes: no file matching the check pay date and keyword, missing employee or payroll item links, pay date not set on the check, or check not in the queue for cost import.

Q: Are Export Build Plans and Export Hours automatic?

A: They are export scripts run on demand or on a schedule set by Implementation — separate from the four automated import flows (Employees, Payroll Items, Payroll Costs, PTO Balance).

Q: Can I change Paycom codes after employees are linked?

A: After linking, FCX follows the external link, not the display ID alone. Changing codes without a coordinated relink can cause duplicates or missed rows. Contact FCX Support.

Q: How does Paycom compare to Paylocity in Fieldclix?

A: Paylocity uses live API sync for most steps. Paycom uses file import and export. Both use external links for matching.