Compliance Records vs LMS Certificates

Smooth HR and Smooth LMS both track "training," but they serve different audit purposes. Employee Compliance in HR is the regulatory ledger—status, renewal dates, I-9/EEO fields, scheduled expiry alerts. LMS Certificate in Smooth LMS is proof of course completion—quiz scores, progress, printable PDF. They are not synchronized automatically today; HR must deliberately attach LMS outputs to HR records when a training obligation must appear on the employee file.

This guide defines the boundary, recommended handoff workflows, and how to avoid duplicate or conflicting records. Read alongside Employee Compliance, Employee Documents, and HRMS + LMS Integration Overview.

Help URL: Compliance Vs Lms Certificates

HR compliance home: Documents & Compliance Overview

Table of Contents

1. Two systems of record
2. Comparison table
3. When to use which
4. Recommended handoff workflow
5. Quiz printouts vs certificates
6. Renewals and recurring training
7. Onboarding vs compliance timing
8. Optional automation (future)
9. Audit scenarios
10. Troubleshooting
11. Related guides

Two systems of record

Smooth HR — Employee Compliance

Managed in Employee Compliance with master Compliance Type definitions:

• Tracks Pending → Complete → Expired lifecycle.
• Supports I-9 list fields, EEO voluntary data, verification attachments.
• Scheduled jobs email HR Managers before expiry.
• Naming: COMP-{employee}-{type}-{####}.

Ideal for: "Demonstrate this employee completed annual harassment training and is due again in 12 months."

Smooth LMS — LMS Certificate

Issued when learner completes a course with Enable Certification:

• Tied to LMS Enrollment progress ≥ 100%.
• Printable via LMS Certificate print format (certification template in LMS Settings).
• Does not auto-update Employee Compliance.

Ideal for: "Prove the learner passed the module content and assessment."

Comparison table

Use both for high-risk training: LMS for delivery + assessment; HR compliance for status and renewal.

When to use which

When in doubt, ask auditors: "Do you need renewal tracking?" If yes → Employee Compliance. If only completion proof → LMS may suffice, but many employers still copy PDF to Employee Document for single-file retrieval.

Recommended handoff workflow

After learner completes mandatory LMS course:

1. Learner downloads LMS Certificate from /lms or desk print.
2. HR (or automated notification to HR) receives completion alert from LMS notifications (Lms Settings General).
3. HR uploads PDF to Employee Document with type "Training Certificate" OR attaches to existing Employee Compliance Verification Document field.
4. HR sets Employee Compliance Status = Complete, Completion Date = today.
5. If Compliance Type has Requires Renewal, confirm Next Renewal Date calculated.
6. For quiz-heavy courses, also store LMS Quiz Submission PDF (Overview capability map).

Do not mark compliance Complete solely because enrollment exists—wait for LMS completion or verified external certificate.

Quiz printouts vs certificates

Smooth LMS supports two PDF artifacts:

HR compliance officers may require quiz printouts for safety modules while executives only need certificate summary. Store both in Employee Documents linked to the same compliance row.

Print steps:

1. Open LMS Quiz Submission from course reports.
2. Print or Download PDF (your site's PDF export).

Renewals and recurring training

Annual cycle example:

1. HR compliance shows Expired or upcoming renewal.
2. L&D re-assigns course (or learner self-enrolls if allowed).
3. New LMS Certificate issued.
4. HR updates compliance record with new PDF and dates.

LMS LMS Training Assignment overdue status does not replace HR expiry—use both dashboards in Overview.

Onboarding vs compliance timing

Employee Onboarding may create compliance rows from template Required Documents while LMS hook enrolls mandatory courses simultaneously.

Typical split:

• Day -7 to Day 1: Portal signatures (Onboarding Portal), LMS mandatory modules.
• Day 1: HR verifies I-9 Employee Compliance sections.
• Day 30: LMS assignment due date default from hook.

Align template task descriptions with LMS course titles so new hires understand parallel workstreams.

Optional automation (future)

Documented optional enhancement: custom hook to auto-create Employee Compliance when LMS Certificate is issued—matching Compliance Type by course name or mapping table.

Until implemented:

• Maintain SOP for manual handoff.
• Weekly report: LMS completions without matching HR compliance Complete.
• Consider scheduled report for high-volume sites.

Audit scenarios

Scenario A — OSHA inspection

Auditor requests proof of safety orientation. Provide Employee Compliance row (Complete) + attached LMS Certificate + quiz PDF from Employee Document.

Scenario B — Internal HR audit

Compare counts: LMS Training Assignment Completed vs Employee Compliance Complete for type "Harassment Training 2026." Investigate gaps.

Scenario C — Terminated employee

HR offboarding (Tenure) retains documents; LMS access disabled via User; historical certificates remain.

Troubleshooting

Related guides

• Integration Overview
• Onboarding Mandatory Training
• Assign Training from HR
• Documents & Compliance Overview
• Employee Compliance
• Employee Documents
• Signature Templates
• Onboarding Templates
• Employee Onboarding
• LMS Settings

Last updated: May 2026

Mapping table: Compliance Type ↔ LMS Course

Maintain a living spreadsheet or internal wiki mapping until automated:

Review mapping quarterly with Documents & Compliance owners and L&D moderators.

Data retention and legal holds

When litigation hold applies, preserve:

• Employee Compliance rows (HR)
• Employee Document attachments (Employee Documents)
• LMS Quiz Submission and LMS Certificate (LMS)

Disabling User login does not delete LMS history—consistent with Tenure separation policies.

International and state variants

Compliance Type supports Applicable Countries / States notes. LMS may require separate courses per locale. Auto onboarding enrolls global mandatory set—use regional assignments for jurisdiction-specific modules after HR sets Employee branch/state on People record.

Quality assurance before audits

Run dual-list reconciliation:

1. Export LMS enrollments progress ≥ 100 for mandatory courses.
2. Export Employee Compliance Complete for matching types.
3. Join on Employee.user_id = LMS member email.
4. Investigate HR-only or LMS-only rows.

Attach reconciliation memo to audit binder alongside integration overview SOP.

FAQ

Can one LMS certificate satisfy two compliance types? Only if policy allows—usually one-to-one mapping.

Does LMS validity days update HR Next Renewal Date? Not automatically—HR enters or verifies dates on Complete.

Are external vendor certs supported? Upload to Employee Document; mark compliance Complete without LMS enrollment.

Working with e-signatures and LMS together

Policy acknowledgment frequently uses Signature Envelopes or Signature Requests while skills validation uses LMS quizzes. An employee may show Fully Executed handbook signature in HR and 80% progress on LMS—both must reach complete states before HR sets unified "orientation complete" checklist on Employee Onboarding.

Train coordinators to check Verification Document on Employee Compliance for LMS PDFs, not just signature PDFs from Signing Portal.

Sample compliance record lifecycle (harassment training)

1. Pre-hire: Compliance Type "Harassment 2026" exists with 12-month renewal.
2. Day 0: Onboarding hook enrolls LMS course; HR creates Employee Compliance row Pending.
3. Day 5: Learner completes course; LMS Certificate issued.
4. Day 6: HR attaches certificate; sets Complete; Next Renewal Date auto-calculates.
5. Month 11: HR scheduler alert; L&D re-assigns via Assign Training From Hr.
6. Month 12: New certificate; HR updates same compliance row or creates new year type per policy.

Document variant in your internal playbook linked from Documents & Compliance Overview.

Smooth HR (HRMS)