Folks HR Review: Canadian HRIS, ATS, Payroll, and AI Terms

Folks HR is a Canadian-focused set of HRIS, applicant tracking, performance, and payroll products for smaller and midsize employers. Its public page uses the dollar sign and lists starting prices of $6 per employee per month for Core HR, $99 per month for ATS, and $3.50 per employee per pay run for Payroll. The accessible page does not label the currency beside those figures, so buyers should confirm it in writing. They are dated vendor starting prices, not a complete quote.

Folks is most relevant when Canadian payroll, bilingual operation, local support, and Canadian hosting are priority requirements. Buyers should examine an important boundary: the vendor markets Canadian data hosting for its core service, while its separate AI terms allow some AI providers to process inputs outside Quebec, including in the United States. That is not necessarily a defect, but it must be reflected in notices, risk assessment, configuration, and contract evidence.

Buying verdict

Shortlist Folks when the proposed modules match a Canadian operating model and the team can validate payroll, privacy, integrations, and export. Its modular offering allows an ATS-only purchase or a wider HRIS and payroll deployment. Do not assume that buying more modules removes every integration or data-transfer boundary.

The best proof uses one province-heavy employee group and one recruiting workflow. Include Quebec if it is material to the organization, because language, payroll, and privacy requirements affect both configuration and governance.

Product boundary

Folks’ plans and features page separates HRIS, ATS, and Payroll plans. The ATS product page explicitly says the ATS can operate as a stand-alone product. It also describes career pages, job distribution, candidate communications, interview scheduling, consent handling, dashboards, contracts, and integrations. These are vendor statements about product scope.

Area	Publicly described scope	Verify in the proposed plan
Core HR	Employee records, time, onboarding, documents, reports, mobile access	Custom fields, history, permissions, exports, and included integration count
ATS	Jobs, applicants, workflow, communications, consent, scheduling, reports	Job boards, parsing limits, source attribution, and hire handoff
Performance	Reviews and development functions	Cycles, calibration, signatures, permissions, and migration
Payroll	Canadian calculations, payslips, direct deposit, reporting	Provinces, tax forms, remittances, corrections, and support responsibility
Agency ATS	ATS plus CRM-oriented functions	Client, contact, job, submission, placement, and billing boundaries

Ask Folks to identify each feature as included, add-on, limited by usage, custom, or roadmap. Retain that schedule with the order form.

Dated pricing snapshot

For this article’s September 2026 revision, the Folks pricing page lists Core HR from $6 per employee per month, ATS from $99 per month, and Payroll from $3.50 per employee per pay run when added to Core HR. It says implementation fees apply to all plans and start at $500. The accessible text uses a dollar symbol without an adjacent currency label, so the quote must confirm whether the amounts are Canadian dollars. Final pricing varies with employee count, modules, and plan.

Normalize the quote for active employees, payroll frequency, recruiters, parsing or messaging allowances, integrations, implementation, sandbox, training, support, tax, and renewal. A biweekly payroll price and a monthly payroll price cannot be compared until converted to the same annual volume.

The feature page also describes different integration allowances across HRIS packages and a resume-parsing allowance in a premium ATS package. Confirm those limits in writing because usage details can materially change price and workflow.

Canadian payroll proof

Folks describes payroll as built for Canadian calculations and reporting. A buyer should validate the legal entities and provinces it will actually run. Use synthetic cases for a regular employee, new hire, termination, bonus, taxable benefit, unpaid leave, retroactive change, off-cycle correction, and employee working across a provincial boundary where relevant.

Compare gross-to-net amounts, employer contributions, year-to-date balances, direct-deposit files, remittance outputs, and year-end forms with an independently calculated expectation. Verify how the system applies statutory updates and how the vendor communicates, tests, and corrects a change.

Payroll acceptance should be signed by the buyer’s payroll owner. A vendor demonstration or a generic Canadian-compliance label is not evidence for a particular pay policy.

ATS and hire handoff

The ATS page names job boards, calendar and email tools, electronic-signature providers, and Canadian payroll systems as integration examples. Treat every connection as product- and plan-specific. Test the exact job board, identity, calendar, signature, background, HRIS, and payroll path required by the buyer.

Run a referral, agency applicant, duplicate candidate, accommodation request, withdrawn applicant, corrected resume, rejection, offer revision, and hire. Confirm that source, consent, communications, feedback, decision, and handoff remain traceable. For a stand-alone ATS deployment, document which system creates the worker identifier and owns post-hire changes.

AI terms reveal the processing boundary

Folks’ AI terms of use identify CV analysis and summary, candidate-to-job matching, and writing assistance. The terms say these functions are optional, require administrative activation, and are assistance rather than exclusive decision tools. They also state that outputs may contain inaccuracies, bias, omissions, or hallucinations and assign human-supervision duties to the customer.

The same terms say an AI provider may process input outside Quebec, including elsewhere in Canada or the United States. They say provider retention information is available by written request. A buyer should obtain the provider list, locations, retention periods, training restrictions, security terms, deletion mechanism, and change-notice process before activation.

Test each AI feature independently. Use a job-related rubric, equivalent resumes with formatting differences, and cases that should not be ranked from sensitive or proxy attributes. Record the input, output, reviewer action, override, and candidate-notice path. Keep the function off if the organization cannot explain and govern its use.

Data residency needs precise language

Folks’ Core HR page says the company is Canadian-owned, holds SOC 2 Type 2 assurance, and hosts data in Canada. Its privacy policy describes service providers and asks customers to contact its privacy officer for more information about transfers outside Quebec or Canada. The AI terms disclose a more specific exception for certain AI processing.

These pages can be reconciled only by defining which data, feature, provider, backup, telemetry, support access, and region each statement covers. Ask for a data-flow diagram and subprocessor register. Contract language should distinguish primary application storage from transient processing, logs, support, backups, and optional AI services.

Do not repeat all data stays in Canada without the qualification shown in the vendor’s own AI terms.

Privacy and access controls

The Office of the Privacy Commissioner of Canada explains the PIPEDA fair information principles, including accountability, identified purposes, limited collection, limited use and retention, accuracy, safeguards, openness, access, and challenge. Provincial and employment rules may also apply. This regulator guidance does not certify Folks.

Turn those principles into product tests. Provide notice to a test applicant, collect only required fields, correct an inaccurate record, export the person’s data, apply a retention rule, and verify deletion across integrations and AI-derived fields. Use roles for HR, payroll, manager, recruiter, employee, and auditor. Confirm that payroll and sensitive employee documents do not inherit broad recruiter or manager access.

Security evidence

SOC 2 Type 2 is a vendor-stated assurance claim on Folks’ site. Request the current report, covered entity and services, period, exceptions, complementary customer controls, and bridge letter. Ask for penetration-test summary, vulnerability process, incident notice, recovery objectives, backup restoration test, subprocessor list, and support-access controls.

Validate the tenant separately: administrator recovery, multi-factor authentication, single sign-on if licensed, role changes, export permissions, API credentials, audit events, terminated users, and mobile-device access. Evidence about the vendor environment does not prove that a customer’s configuration follows least privilege.

Implementation plan

Phase	Required result
Scope	Each HRIS, ATS, payroll, performance, AI, and integration requirement maps to a licensed function
Data	Workers, managers, jobs, candidates, documents, balances, and identifiers are cleaned and owned
Configure	Roles, policies, bilingual content, notices, retention, and approvals match written policy
Test	Payroll, recruiting, integrations, privacy, permissions, and failure recovery pass scenario tests
Parallel run	Payroll and required reports reconcile for agreed cycles
Launch	Support, rollback, monitoring, access review, and issue ownership are active

Avoid enabling AI functions during initial migration unless their data flow and controls have already passed review. That keeps core record reconciliation separate from optional processing.

Unknowns to close

Public material does not establish the final customer price, implementation duration, service levels, full API object coverage, support performance, complete subprocessor list, or AI-provider retention. Vendor pages also contain changing package and product statements that require a dated order schedule.

Request the quote, feature schedule, implementation statement, security report, privacy and data-processing terms, AI provider register, integration specification, service levels, sample export, retention schedule, and deletion confirmation. Verify payroll coverage for each province and legal entity rather than extrapolating from general Canada positioning.

Decision rule

Choose Folks when the contracted modules pass Canadian payroll, bilingual workflow, ATS, access, privacy, integration, and exit tests at a normalized three-year cost. Keep AI disabled until its cross-border processing, provider retention, candidate notice, human review, and output validation are accepted. Pause if Canadian hosting is presented without the vendor’s own AI-processing qualification or if statutory payroll results cannot be independently reconciled.