OVERALL CONTROL / 0.6-customer-control
Grades and scoring
Data access
25% of the overall score before applicability adjustment.
Scored answers and evidence
Read interface 2.5/10
Report outputs only
Paycom / customer-generated Report Center outputs and GL Concierge payroll-ledger export files; the Data Services agreement separately describes API/SFTP access, whose technical object, mutation and synchronization contracts remain unverified.
Report Center generates selected HR/payroll report outputs. The legal agreement confirms API/SFTP services exist but does not supply their technical record schema.
Paycom Report Center and recurring outputs ↗
Generate reports across HR/payroll; filters and saved format; Push Reporting to authorized users · Checked 2026-10-16
Paycom General Terms and Conditions ↗
Sections 8 and 19; ordinary-course client data use; third-party obligations; commercial reuse and documentation restrictions · Checked 2026-10-16
Bulk delivery 2.5/10
Manual report download
Paycom / customer-generated Report Center outputs and GL Concierge payroll-ledger export files; the Data Services agreement separately describes API/SFTP access, whose technical object, mutation and synchronization contracts remain unverified.
Customers can generate and export selected mapped GL reports in a chosen file layout for import into their accounting software. API/SFTP bulk completeness is unverified.
Paycom GL Concierge export files ↗
Mapped GL reports for import; payroll data; on-demand exports in chosen file layout · Checked 2026-10-16
Query expressiveness -
-
Paycom / customer-generated Report Center outputs and GL Concierge payroll-ledger export files; the Data Services agreement separately describes API/SFTP access, whose technical object, mutation and synchronization contracts remain unverified.
Report Center filters operate inside the provider UI; an external API query/filter contract is unverified.
Paycom Report Center and recurring outputs ↗
Generate reports across HR/payroll; filters and saved format; Push Reporting to authorized users · Checked 2026-10-16
Access cost barrier -
-
Paycom / customer-generated Report Center outputs and GL Concierge payroll-ledger export files; the Data Services agreement separately describes API/SFTP access, whose technical object, mutation and synchronization contracts remain unverified.
Lowest-paid-plan entitlement and complete fixed API or partner access fees are unresolved.
Paycom Data Services terms and access keys ↗
Section 19 Data Services: API/SFTP, access keys, third-party facilitators and restrictions; section 8 post-termination access · Checked 2026-10-16
Third-party accessibility
20% of the overall score before applicability adjustment.
Scored answers and evidence
Third-party eligibility -
-
Paycom / customer-generated Report Center outputs and GL Concierge payroll-ledger export files; the Data Services agreement separately describes API/SFTP access, whose technical object, mutation and synchronization contracts remain unverified.
Terms allow third parties only as necessary to facilitate the client’s API usage and bind them to client obligations; key issuance and chosen-provider production eligibility remain unverified.
Paycom General Terms and Conditions ↗
Sections 8 and 19; ordinary-course client data use; third-party obligations; commercial reuse and documentation restrictions · Checked 2026-10-16
Downstream permission 7.5/10
Published purpose and confidentiality boundaries
Paycom / customer-generated Report Center outputs and GL Concierge payroll-ledger export files; the Data Services agreement separately describes API/SFTP access, whose technical object, mutation and synchronization contracts remain unverified.
Section 19 permits ordinary-course use of client data and necessary third-party API facilitators under client obligations; resale, commercialization and publication of API/SFTP documentation are restricted.
Paycom General Terms and Conditions ↗
Sections 8 and 19; ordinary-course client data use; third-party obligations; commercial reuse and documentation restrictions · Checked 2026-10-16
External action
15% of the overall score before applicability adjustment.
Scored answers and evidence
Write interface -
-
Paycom / customer-generated Report Center outputs and GL Concierge payroll-ledger export files; the Data Services agreement separately describes API/SFTP access, whose technical object, mutation and synchronization contracts remain unverified.
The Data Services terms describe interfaces, imports and transmissions but do not prove named external mutation endpoints or permissions.
Paycom General Terms and Conditions ↗
Sections 8 and 19; ordinary-course client data use; third-party obligations; commercial reuse and documentation restrictions · Checked 2026-10-16
Custom application path -
-
Paycom / customer-generated Report Center outputs and GL Concierge payroll-ledger export files; the Data Services agreement separately describes API/SFTP access, whose technical object, mutation and synchronization contracts remain unverified.
Customer credential setup alone does not establish chosen third-party production eligibility.
Paycom General Terms and Conditions ↗
Sections 8 and 19; ordinary-course client data use; third-party obligations; commercial reuse and documentation restrictions · Checked 2026-10-16
Continuity
15% of the overall score before applicability adjustment.
Scored answers and evidence
Refresh mechanism 5.0/10
Scheduled feeds or recurring extracts
Paycom / customer-generated Report Center outputs and GL Concierge payroll-ledger export files; the Data Services agreement separately describes API/SFTP access, whose technical object, mutation and synchronization contracts remain unverified.
Push Reporting delivers recurring selected reports to authorized users; this establishes scheduled output, not record-level change events.
Paycom Report Center and recurring outputs ↗
Generate reports across HR/payroll; filters and saved format; Push Reporting to authorized users · Checked 2026-10-16
Limit visibility 2.5/10
Governors or limits stated without quantities
Paycom / customer-generated Report Center outputs and GL Concierge payroll-ledger export files; the Data Services agreement separately describes API/SFTP access, whose technical object, mutation and synchronization contracts remain unverified.
Data Services terms permit API-call and SFTP-request limits without publishing quantities or a recovery protocol.
Paycom General Terms and Conditions ↗
Sections 8 and 19; ordinary-course client data use; third-party obligations; commercial reuse and documentation restrictions · Checked 2026-10-16
CDC and deletion capture -
-
Paycom / customer-generated Report Center outputs and GL Concierge payroll-ledger export files; the Data Services agreement separately describes API/SFTP access, whose technical object, mutation and synchronization contracts remain unverified.
Reports can expose selected current fields, but stable record identities, exhaustive population coverage and hard-deletion semantics are unverified.
Paycom Report Center and recurring outputs ↗
Generate reports across HR/payroll; filters and saved format; Push Reporting to authorized users · Checked 2026-10-16
Replay and gap recovery 2.5/10
Rebuild from a fresh snapshot; no historical replay established
Paycom / customer-generated Report Center outputs and GL Concierge payroll-ledger export files; the Data Services agreement separately describes API/SFTP access, whose technical object, mutation and synchronization contracts remain unverified.
Regenerate the supported GL report/export selection to rebuild that selected current output. Raw HR records, historical deletions and a retained event log are not established.
Paycom GL Concierge export files ↗
Mapped to perfection; on-demand data and GL exports · Checked 2026-10-16
Data exit
20% of the overall score before applicability adjustment.
Scored answers and evidence
Export custody 7.5/10
Customer-held structured files or API records
Paycom / customer-generated Report Center outputs and GL Concierge payroll-ledger export files; the Data Services agreement separately describes API/SFTP access, whose technical object, mutation and synchronization contracts remain unverified.
GL Concierge exports customer-held payroll-ledger files for import into the chosen accounting program.
Paycom GL Concierge export files ↗
Mapped GL reports for import; payroll data; on-demand exports in chosen file layout · Checked 2026-10-16
Post-cancellation access Disclosure
-
Disclosure only; does not reduce planned-exit credit.
Paycom / customer-generated Report Center outputs and GL Concierge payroll-ledger export files; the Data Services agreement separately describes API/SFTP access, whose technical object, mutation and synchronization contracts remain unverified.
Section 8 permits extra charges for post-termination access; it does not establish a defined retrieval window or an exit extract entitlement.
Paycom General Terms and Conditions ↗
Sections 8 and 19; ordinary-course client data use; third-party obligations; commercial reuse and documentation restrictions · Checked 2026-10-16
Planned migration fidelity 5.0/10
Selected report fields in structured files; broader scope unverified
Paycom / customer-generated Report Center outputs and GL Concierge payroll-ledger export files; the Data Services agreement separately describes API/SFTP access, whose technical object, mutation and synchronization contracts remain unverified.
Portable mapped GL fields and selected report outputs are established. Raw HR records, files, native definitions and whole-product reconstruction remain unverified.
Paycom Report Center and recurring outputs ↗
Generate reports across HR/payroll; filters and saved format; Push Reporting to authorized users · Checked 2026-10-16
Paycom GL Concierge export files ↗
Mapped GL reports for import; payroll data; on-demand exports in chosen file layout · Checked 2026-10-16
Business logic and customization
5% of the overall score before applicability adjustment.
Scored answers and evidence
Logic authoring 2.5/10
External integration code; native business logic portability not established
Paycom / customer-generated Report Center outputs and GL Concierge payroll-ledger export files; the Data Services agreement separately describes API/SFTP access, whose technical object, mutation and synchronization contracts remain unverified.
Data Services permit external interfaces within the client’s business purpose. Ownership and portability of native workflow artifacts are not established.
Paycom General Terms and Conditions ↗
Sections 8 and 19; ordinary-course client data use; third-party obligations; commercial reuse and documentation restrictions · Checked 2026-10-16
Rights to custom logic -
-
Paycom / customer-generated Report Center outputs and GL Concierge payroll-ledger export files; the Data Services agreement separately describes API/SFTP access, whose technical object, mutation and synchronization contracts remain unverified.
Rights to reusable native workflow definitions and independent execution are unresolved.
Paycom Data Services terms and access keys ↗
Section 19 Data Services: API/SFTP, access keys, third-party facilitators and restrictions; section 8 post-termination access · Checked 2026-10-16
Scores are out of 10. * Incomplete evidence discounts verified capabilities (unknown answers stay unknown). Planned migration drives data exit. Scoring method ↗
CUSTOMER CHOICE
Third-party accessibility
Terms allow third parties only as necessary to facilitate the client’s API usage and bind them to client obligations; key issuance and chosen-provider production eligibility remain unverified.
Confirm who can connect, who owns the credentials and which uses are permitted. Customer consent and provider approval can be separate requirements; the selected plan and contract still matter.
READ / INTEGRATE
API and export routes
Report Center generates selected HR/payroll report outputs. The legal agreement confirms API/SFTP services exist but does not supply their technical record schema. Customers can generate and export selected mapped GL reports in a chosen file layout for import into their accounting software. API/SFTP bulk completeness is unverified. Report Center filters operate inside the provider UI; an external API query/filter contract is unverified.
| Access route | Authentication | Credential owner | Provider approval | Access requirement | Last checked |
|---|---|---|---|---|---|
| Customer Report Center and GL file export | session | Customer | No | customer authorization | 2026-10-16 |
| Paycom Data Services API/SFTP route | Not confirmed | Customer | Not confirmed | Not confirmed | 2026-10-16 |
Availability depends on your product, plan and agreement. See the documentation below for the requirements of each route.
ECONOMIC ACCESS
Cost, authentication and limits
Lowest-paid-plan entitlement and complete fixed API or partner access fees are unresolved.
Check API entitlement, credential ownership and rate limits for the route you intend to use. Include review fees, customer-plan upgrades and ongoing access charges in the total.
ACT FROM OUTSIDE
External action
The Data Services terms describe interfaces, imports and transmissions but do not prove named external mutation endpoints or permissions.
Validate the supported operation, acting identity and permission scope (read access does not imply write permission). Ambiguous retries and revoked credentials also affect whether an external workflow can run safely.
KEEP ACCESS USEFUL
Continuity
Push Reporting delivers recurring selected reports to authorized users; this establishes scheduled output, not record-level change events. Reports can expose selected current fields, but stable record identities, exhaustive population coverage and hard-deletion semantics are unverified. Regenerate the supported GL report/export selection to rebuild that selected current output. Raw HR records, historical deletions and a retained event log are not established. Data Services terms permit API-call and SFTP-request limits without publishing quantities or a recovery protocol.
CDC, deletions and recovery
| Question | Answer / applicable route | Evidence |
|---|---|---|
| Can ongoing extraction identify updates and deleted records on the declared route? | -Paycom / customer-generated Report Center outputs and GL Concierge payroll-ledger export files; the Data Services agreement separately describes API/SFTP access, whose technical object, mutation and synchronization contracts remain unverified. Reports can expose selected current fields, but stable record identities, exhaustive population coverage and hard-deletion semantics are unverified. | Paycom Report Center and recurring outputs ↗Generate reports across HR/payroll; filters and saved format; Push Reporting to authorized usersChecked 2026-10-16 |
| How can extraction recover after missed events or an interrupted consumer? | Rebuild from a fresh snapshot; no historical replay establishedPaycom / customer-generated Report Center outputs and GL Concierge payroll-ledger export files; the Data Services agreement separately describes API/SFTP access, whose technical object, mutation and synchronization contracts remain unverified. Regenerate the supported GL report/export selection to rebuild that selected current output. Raw HR records, historical deletions and a retained event log are not established. | Paycom GL Concierge export files ↗Mapped to perfection; on-demand data and GL exportsChecked 2026-10-16 |
Useful ongoing access includes corrections and deletions, not only the first export. A failed request, changed filter or lost resource permission should not be interpreted as a deleted record.
LEAVE WITH YOUR DATA
Data exit and portability
Portable mapped GL fields and selected report outputs are established. Raw HR records, files, native definitions and whole-product reconstruction remain unverified. Section 8 permits extra charges for post-termination access; it does not establish a defined retrieval window or an exit extract entitlement.
Test the output against the destination’s required fields and history. Check stable identifiers, relationships, attachments and extraction time; a sample file proves only the coverage of that sample.
BUILD / INSPECT / REUSE
Business logic and customization
Data Services permit external interfaces within the client’s business purpose. Ownership and portability of native workflow artifacts are not established. Rights to reusable native workflow definitions and independent execution are unresolved.
Custom API access, ownership of workflows and the right to export their definitions are separate questions. A custom-app capability alone does not establish that business rules can move to another system.
AGREEMENTS / API DOCS / PROGRAM REQUIREMENTS
Documented conditions
Answers below come from public provider materials. Every answer retains its source check date, scope (a partner agreement does not describe every customer route). Customer contracts and live behavior still need verification.
| Question | Answer / applicable route | Evidence |
|---|---|---|
| What structured read interface is documented? | Report outputs onlyPaycom / customer-generated Report Center outputs and GL Concierge payroll-ledger export files; the Data Services agreement separately describes API/SFTP access, whose technical object, mutation and synchronization contracts remain unverified. Report Center generates selected HR/payroll report outputs. The legal agreement confirms API/SFTP services exist but does not supply their technical record schema. | Paycom Report Center and recurring outputs ↗Generate reports across HR/payroll; filters and saved format; Push Reporting to authorized usersChecked 2026-10-16 Paycom General Terms and Conditions ↗Sections 8 and 19; ordinary-course client data use; third-party obligations; commercial reuse and documentation restrictionsChecked 2026-10-16 |
| How can customers retrieve data in bulk? | Manual report downloadPaycom / customer-generated Report Center outputs and GL Concierge payroll-ledger export files; the Data Services agreement separately describes API/SFTP access, whose technical object, mutation and synchronization contracts remain unverified. Customers can generate and export selected mapped GL reports in a chosen file layout for import into their accounting software. API/SFTP bulk completeness is unverified. | Paycom GL Concierge export files ↗Mapped GL reports for import; payroll data; on-demand exports in chosen file layoutChecked 2026-10-16 |
| What queries can a customer issue outside the provider UI? | -Paycom / customer-generated Report Center outputs and GL Concierge payroll-ledger export files; the Data Services agreement separately describes API/SFTP access, whose technical object, mutation and synchronization contracts remain unverified. Report Center filters operate inside the provider UI; an external API query/filter contract is unverified. | Paycom Report Center and recurring outputs ↗Generate reports across HR/payroll; filters and saved format; Push Reporting to authorized usersChecked 2026-10-16 |
| Who decides whether a chosen third party may connect? | -Paycom / customer-generated Report Center outputs and GL Concierge payroll-ledger export files; the Data Services agreement separately describes API/SFTP access, whose technical object, mutation and synchronization contracts remain unverified. Terms allow third parties only as necessary to facilitate the client’s API usage and bind them to client obligations; key issuance and chosen-provider production eligibility remain unverified. | Paycom General Terms and Conditions ↗Sections 8 and 19; ordinary-course client data use; third-party obligations; commercial reuse and documentation restrictionsChecked 2026-10-16 |
| What extra commercial condition applies to the routes supplying the assessed read capability, relative to the lowest paid plan? | -Paycom / customer-generated Report Center outputs and GL Concierge payroll-ledger export files; the Data Services agreement separately describes API/SFTP access, whose technical object, mutation and synchronization contracts remain unverified. Lowest-paid-plan entitlement and complete fixed API or partner access fees are unresolved. | Paycom Data Services terms and access keys ↗Section 19 Data Services: API/SFTP, access keys, third-party facilitators and restrictions; section 8 post-termination accessChecked 2026-10-16 |
| What permission is needed for the documented downstream use? | Published purpose and confidentiality boundariesPaycom / customer-generated Report Center outputs and GL Concierge payroll-ledger export files; the Data Services agreement separately describes API/SFTP access, whose technical object, mutation and synchronization contracts remain unverified. Section 19 permits ordinary-course use of client data and necessary third-party API facilitators under client obligations; resale, commercialization and publication of API/SFTP documentation are restricted. | Paycom General Terms and Conditions ↗Sections 8 and 19; ordinary-course client data use; third-party obligations; commercial reuse and documentation restrictionsChecked 2026-10-16 |
| Which external write operations are documented? | -Paycom / customer-generated Report Center outputs and GL Concierge payroll-ledger export files; the Data Services agreement separately describes API/SFTP access, whose technical object, mutation and synchronization contracts remain unverified. The Data Services terms describe interfaces, imports and transmissions but do not prove named external mutation endpoints or permissions. | Paycom General Terms and Conditions ↗Sections 8 and 19; ordinary-course client data use; third-party obligations; commercial reuse and documentation restrictionsChecked 2026-10-16 |
| How can customers connect an application they build or choose? | -Paycom / customer-generated Report Center outputs and GL Concierge payroll-ledger export files; the Data Services agreement separately describes API/SFTP access, whose technical object, mutation and synchronization contracts remain unverified. Customer credential setup alone does not establish chosen third-party production eligibility. | Paycom General Terms and Conditions ↗Sections 8 and 19; ordinary-course client data use; third-party obligations; commercial reuse and documentation restrictionsChecked 2026-10-16 |
| What mechanism supports repeatable extraction of changes? | Scheduled feeds or recurring extractsPaycom / customer-generated Report Center outputs and GL Concierge payroll-ledger export files; the Data Services agreement separately describes API/SFTP access, whose technical object, mutation and synchronization contracts remain unverified. Push Reporting delivers recurring selected reports to authorized users; this establishes scheduled output, not record-level change events. | Paycom Report Center and recurring outputs ↗Generate reports across HR/payroll; filters and saved format; Push Reporting to authorized usersChecked 2026-10-16 |
| How are integration limits disclosed? | Governors or limits stated without quantitiesPaycom / customer-generated Report Center outputs and GL Concierge payroll-ledger export files; the Data Services agreement separately describes API/SFTP access, whose technical object, mutation and synchronization contracts remain unverified. Data Services terms permit API-call and SFTP-request limits without publishing quantities or a recovery protocol. | Paycom General Terms and Conditions ↗Sections 8 and 19; ordinary-course client data use; third-party obligations; commercial reuse and documentation restrictionsChecked 2026-10-16 |
| Where can a usable data copy be delivered? | Customer-held structured files or API recordsPaycom / customer-generated Report Center outputs and GL Concierge payroll-ledger export files; the Data Services agreement separately describes API/SFTP access, whose technical object, mutation and synchronization contracts remain unverified. GL Concierge exports customer-held payroll-ledger files for import into the chosen accounting program. | Paycom GL Concierge export files ↗Mapped GL reports for import; payroll data; on-demand exports in chosen file layoutChecked 2026-10-16 |
| What retrieval rights are documented at cancellation? | -Paycom / customer-generated Report Center outputs and GL Concierge payroll-ledger export files; the Data Services agreement separately describes API/SFTP access, whose technical object, mutation and synchronization contracts remain unverified. Section 8 permits extra charges for post-termination access; it does not establish a defined retrieval window or an exit extract entitlement. | Paycom General Terms and Conditions ↗Sections 8 and 19; ordinary-course client data use; third-party obligations; commercial reuse and documentation restrictionsChecked 2026-10-16 |
| How can customers define their own business logic? | External integration code; native business logic portability not establishedPaycom / customer-generated Report Center outputs and GL Concierge payroll-ledger export files; the Data Services agreement separately describes API/SFTP access, whose technical object, mutation and synchronization contracts remain unverified. Data Services permit external interfaces within the client’s business purpose. Ownership and portability of native workflow artifacts are not established. | Paycom General Terms and Conditions ↗Sections 8 and 19; ordinary-course client data use; third-party obligations; commercial reuse and documentation restrictionsChecked 2026-10-16 |
| What rights or portability are documented for custom workflow artifacts? | -Paycom / customer-generated Report Center outputs and GL Concierge payroll-ledger export files; the Data Services agreement separately describes API/SFTP access, whose technical object, mutation and synchronization contracts remain unverified. Rights to reusable native workflow definitions and independent execution are unresolved. | Paycom Data Services terms and access keys ↗Section 19 Data Services: API/SFTP, access keys, third-party facilitators and restrictions; section 8 post-termination accessChecked 2026-10-16 |
| What usable data or native definitions can leave before cancellation? | Selected report fields in structured files; broader scope unverifiedPaycom / customer-generated Report Center outputs and GL Concierge payroll-ledger export files; the Data Services agreement separately describes API/SFTP access, whose technical object, mutation and synchronization contracts remain unverified. Portable mapped GL fields and selected report outputs are established. Raw HR records, files, native definitions and whole-product reconstruction remain unverified. | Paycom Report Center and recurring outputs ↗Generate reports across HR/payroll; filters and saved format; Push Reporting to authorized usersChecked 2026-10-16 Paycom GL Concierge export files ↗Mapped GL reports for import; payroll data; on-demand exports in chosen file layoutChecked 2026-10-16 |
SOURCES / SCOPE / HISTORY
Sources and open questions
This review is based on the documentation below. Live account behavior and customer-specific agreements haven’t been tested.
Still to confirm
- Technical structured query/filter contract
- Chosen third-party eligibility and provider selection requirements
- Complete lowest-plan entitlement and fixed API fees
- Named external mutation operations and permissions
- Eligibility for a chosen custom application
- Contractual post-cancellation retrieval terms
- Native workflow artifact ownership, reusable export and independent execution
- Deletion identities for the scoped collection
- Retained replay and complete scoped recovery contract
Documentation
Assessment checked 2026-10-16. Each answer retains its source and applicable route; the check date does not establish live account behavior.