How to Configure Factorial for a 100 Person Company

How to configure Factorial for a 100 person company is straightforward with the right plan: define goals, map your organisation and data, set up core modules (absence, time tracking, onboarding, documents), test workflows and train users — then iterate after go‑live. With careful preparation and a partner like Faqtic, a certified Factorial partner staffed by former Factorial employees, a 100‑person implementation can be efficient, compliant and highly adopted.

What initial planning steps are needed before configuring Factorial?

Start by setting clear objectives, identifying stakeholders and auditing existing HR processes and data. This planning phase reduces rework, clarifies scope and creates the roadmap for a smooth implementation.

Key planning activities include:

• Defining success criteria (e.g., reduce leave admin time by X%, centralise employee records, automate onboarding).
• Appointing an implementation team: project owner, HR lead, IT lead, payroll contact and 2–3 managers as pilot users.
• Mapping current processes (leave, onboarding, expense approvals, time tracking) and pain points.
• Auditing employee data: which fields exist, which are missing and what needs migration.
• Setting a timeline, milestones and budget for licences, integrations and support.

Who should be on the implementation team?

Include one project lead (COO/Head of People), the HR operations lead, an IT contact for permissions and integrations, a payroll/accounting rep and 2–3 managers to pilot features. The project lead owns decisions and scheduling; the HR lead manages configuration details.

What is a realistic timeline and budget for a 100‑person implementation?

Typical timelines range from 4–8 weeks for standard setups and 8–12+ weeks for complex payroll integrations or custom workflows. Budget should cover Factorial licences, partner implementation fees (if using Faqtic), minor integration work and change management resources.

What data should be audited before migration?

Audit core employee data (names, IDs, contracts, emails), job details (roles, departments, managers), compensation fields, leave balances, historical absence records, payroll identifiers and authorised signatories. Mark fields that require cleanup or standardisation (e.g., job titles).

How should the organisation structure be set up in Factorial for 100 employees?

Set up departments, teams, locations and reporting lines to reflect how people actually work and how managers should receive notifications; this ensures accurate reporting and approvals.

Best practices:

• Create departments for major functions (Sales, Engineering, People, Finance) and teams for smaller units or product squads.
• Use locations for different offices or countries to manage local public holidays and compliance.
• Assign managers in each employee record so approvals route correctly.
• Use custom fields for cost centres, employment type (full‑time/part‑time/contractor) or employee IDs for payroll mapping.

How should multi‑location or hybrid teams be modelled?

Use the location field to set office or country; combine with team or department to reflect cross‑functional squads. Locations drive holiday calendars and local compliance, while teams and departments drive reporting and approvals.

Should job levels and grades be modelled in Factorial?

Yes. Adding job levels as custom fields or using a standardised job title taxonomy makes compensation reporting and career planning simpler. Factorial’s custom fields let HR tag seniority, band and job family for analytics.

How to import employee data and migrate from spreadsheets or legacy systems?

Export and clean source data, map it to Factorial’s CSV template, run a small test import, then import the full dataset. Always back up originals and validate after import.

Practical steps:

1. Export data from spreadsheets or the old HRIS.
2. Standardise formats (dates, phone numbers, job titles), remove duplicates and normalise role names.
3. Use Factorial’s import templates and map fields carefully. If in doubt, consult Faqtic for mapping support.
4. Run a pilot with 5–10 employees to confirm mapping and permissions.
5. Import full data and validate with spot checks across departments.

What employee fields are essential to import?

At minimum: legal name, personal email, company email, start date, contract type, department, manager, location, national ID (where applicable), bank details (if required for payroll) and emergency contact. Add custom fields for cost centre or employee number if needed.

How should historical leave and balances be handled?

Decide whether to migrate historical leave for reporting or to start fresh from go‑live. If migrating, convert balances to the Factorial format and note accrual start dates. For simplicity, many companies opt to migrate the current balances and keep historical records in a separate archive.

How to configure roles, permissions and approval workflows in Factorial?

Define a small set of roles (Super Admin, HR Admin, Manager, Employee) and customise permissions to limit access to sensitive data; set approval chains for leave, expenses and overtime aligned with reporting lines.

Recommended configuration for a 100‑person company:

• Super Admin: One or two trusted people (CEO or Head of People) with full control.
• HR Admin: HR Ops executes configuration, approves exceptions and manages reports.
• Manager: Can approve leave/time and view team dashboards; no access to salary unless necessary.
• Employee: Access to self‑service features — request leave, view payslips and update personal info.

How to set multi‑level approval chains?

Use Factorial’s approval workflow settings to require manager approval, then HR approval for certain requests (e.g., unpaid leave). For larger changes (sabbaticals, contract amendments), include a custom approval step routed to the HR Admin or finance.

How to handle restricted access to sensitive HR data?

Use role restrictions and hide salary fields from managers by default. Create a policy for ad‑hoc data access requests and log any manual exports. Factorial’s audit trail will help trace changes.

How to set up absence, leave policies and working hours?

Configure leave types, accrual rules, public holiday calendars and working patterns so leave balances and approvals reflect company policy and local legislation.

Key configuration tasks:

• Create standard leave types: annual leave, sick leave, parental leave, unpaid leave and special leave.
• Set accrual rules (monthly, yearly pro rata) and carryover policies.
• Configure public holidays per location and company‑wide policies (e.g., company closure days).
• Define working hours and part‑time patterns to ensure accurate balance calculations.

How to handle part‑time, shift work and flexible schedules?

Set custom working patterns for part‑time employees and shifts. Factorial allows different schedules per employee so accrual and absence calculations remain accurate. For shift work, enable specific shift templates and overtime rules.

How to manage statutory sick pay, parental leave and other legal entitlements?

Configure special leave types with local rules for accrual and pay. Keep statutory calculations documented outside Factorial if payroll provider needs specific fields, but record the absence type in Factorial for compliance and reporting.

How to configure onboarding, offboarding and document management?

Create onboarding checklists, document templates and automated task assignments so new hires are productive from day one and offboarding is compliant and auditable.

Essential elements to configure:

• Onboarding templates by role (IT account, workspace access, first‑week goals).
• Contract templates with placeholders for variables (start date, salary, role) and e‑signature workflows.
• Document repository for policies, NDAs and handbooks with access control.
• Offboarding workflows to collect devices, revoke access and schedule exit interviews.

Which documents should be uploaded to Factorial?

Employment contracts, offer letters, company policies, tax forms and identity documents where legally permissible. Store payslips only if Factorial is used for payslip distribution; otherwise, keep payslips within payroll software but link records.

How to automate onboarding tasks?

Use Factorial’s templates to assign tasks to HR, IT and hiring managers automatically on the employee’s start date. Include reminders and deadlines to ensure completion before the first day.

How to enable time tracking, shifts and attendance for diverse roles?

Enable the time tracking module and create appropriate clock‑in methods (mobile app, web clock) and timesheet rules to reflect office, remote and field roles.

Steps to configure:

• Choose the tracking method: clock‑in/clock‑out or manual timesheets.
• Set rules for overtime calculation, rounding and grace periods.
• Create shift templates for rotating or fixed shifts and assign employees accordingly.
• Provide mobile access for field staff and enable geofencing if required (check local law).

How to manage field staff and remote workers differently?

For field staff, use mobile clock‑in with GPS or approved devices and stricter audit rules. For remote workers, permit manual timesheets with manager approval and focus on output‑based metrics where possible.

How to handle overtime and payroll handover?

Define overtime categories and approval requirements. Configure exports so that payroll receives approved hours in the required format (CSV, API). If Factorial doesn’t process payroll directly, standardise an export template for your payroll provider.

How to connect Factorial with payroll, accounting and other tools?

Integrate Factorial with payroll providers or export standardised data; connect to common workplace tools (Google Workspace, Microsoft 365, Slack) and use API/Webhooks or Zapier for other apps.

Integration options and advice:

• Check native integrations: certain European payroll providers have direct integrations with Factorial.
• Use Factorial’s export templates for payroll reports (employee lists, salary fields, worked hours).
• Integrate with Google Workspace or Azure AD for single sign‑on and automated user provisioning.
• Connect Slack or MS Teams for notifications to managers or onboarding channels.
• Use Zapier or the Factorial API for bespoke integrations (recruitment systems, accounting software).

Which payroll integrations are common for European SMEs?

Common integrations include ADP, localised payroll software used in Spain, Portugal, France and other markets. If no direct integration exists, a reliable CSV export/import or API workflow will suffice.

How to ensure data consistency between Factorial and payroll?

Use unique employee identifiers and synchronise a canonical source of truth (usually Factorial for HR data and the payroll system for payments). Establish a monthly reconciliation process and automate exports to reduce manual errors.

How to customise reports, dashboards and KPIs for a 100‑person company?

Create dashboards for headcount, turnover, absence rate and time‑to‑hire; schedule regular reports for management and use custom fields to slice data by cost centre or project.

KPIs to configure and monitor:

• Headcount and growth by department
• Turnover rate (voluntary vs involuntary)
• Absence rate and top reasons for absence
• Time‑to‑hire and open positions
• Overtime hours and distribution by team

How to build useful HR dashboards?

Start with 3–5 executive metrics and build manager dashboards for team health. Use automated exports and scheduled emails so leadership gets monthly snapshots without manual work.

How to create ad‑hoc reports for audits or finance?

Use Factorial’s reporting tools to filter by custom fields (cost centre, project) and export CSVs for finance. Keep report templates for recurring audits to save time.

How to train users and manage change for smooth adoption?

Deploy a pilot phase, run role‑based training sessions and maintain ongoing support channels; adoption depends as much on communication and training as system configuration.

A practical rollout approach:

1. Run a pilot with one department (10–20 users) to validate workflows.
2. Conduct role‑based training: HR admins, managers and employees have different needs.
3. Create quick reference guides and short video tutorials for common tasks (request leave, approve timesheets).
4. Use internal champions in each team to answer questions and promote usage.
5. Set measurable adoption goals (e.g., 90% of leave requests via Factorial in the first 30 days).

What training formats work best?

Mix live workshops for admins and managers with on‑demand short videos and an FAQ hub. Short, task‑focused sessions (20–30 minutes) are more effective than long seminars.

How to measure and sustain adoption?

Track system logins, percentage of leave/expense requests processed through Factorial and completion rates of onboarding tasks. Act on low usage by running refresher sessions and addressing blockers quickly.

How to ensure security, compliance and GDPR when using Factorial?

Factorial provides platform security, but the company must configure user permissions, data retention policies and DPA agreements to meet GDPR and industry compliance.

Security and compliance checklist:

• Sign a Data Processing Agreement (DPA) with Factorial and ensure subprocessors are documented.
• Limit access via role‑based permissions and enforce strong password/SSO policies.
• Define data retention and deletion policies for leavers and archival records.
• Enable audit logs and regular reviews of admin accounts.
• Train staff on data privacy and avoid storing unnecessary sensitive personal data in Factorial.

What GDPR actions should HR complete before go‑live?

Update privacy notices, ensure lawful bases for processing employee data, document retention policies and implement processes for data subject access requests. Coordinate with legal/compliance if the company operates across multiple EU countries.

How to manage access for former employees?

Automate offboarding to revoke access immediately on termination and decide whether to anonymise or delete personal data according to retention policy. Keep a minimal audit trail for legal requirements.

How long does it take to implement Factorial for a 100 person company?

Implementation typically takes 4–8 weeks for standard setups and 8–12+ weeks for complex payroll, multi‑country rules or heavy integrations; using a specialised partner can shorten the timeline.

Factors affecting timeline:

• Complexity of payroll and integrations
• Data quality and migration scope
• Number of custom workflows and approvals
• Availability of internal stakeholders for testing and training

What is a practical go‑live checklist?

Verify employee records, confirm manager assignments, test leave accruals, validate payroll exports, complete admin training, run a pilot and communicate the launch plan with clear support routes.

How to phase a rollout to reduce risk?

Consider a two‑phase approach: (1) core HR + absence + documents for all employees, (2) time tracking and advanced integrations for nominated teams. This lowers risk and allows HR to build confidence.

How can Faqtic support and accelerate a Factorial implementation?

Faqtic, a certified Factorial partner with former Factorial staff, provides end‑to‑end services: reselling licences, implementation, data migration, custom integrations, training and ongoing support — reducing risk and accelerating adoption.

How Faqtic helps in practice:

• Hands‑on configuration by people who know Factorial inside out.
• Data migration and template mapping to avoid common pitfalls.
• Custom integrations using the Factorial API and experience connecting local payroll systems across European markets.
• Role‑based training and change management plans tailored to SME realities.
• Post‑go‑live support and SLA options so HR teams aren’t left alone after launch.

What services does Faqtic typically deliver for a 100‑person company?

Faqtic commonly provides a discovery workshop, data migration, full configuration of absence/time/onboarding modules, payroll integration, manager training, a pilot launch and three months of hypercare support to ensure stable adoption.

Can Faqtic help with custom reports or GDPR processes?

Yes. Faqtic builds custom reports, automates exports for finance and helps define GDPR procedures (retention schedules, DPA reviews, data subject request processes) to fit local regulations.

What are common pitfalls and how can they be avoided?

Pitfalls include poor data quality, unclear approval chains, insufficient training and trying to configure everything at once. Avoid these by prioritising critical features, running a pilot and engaging a partner for expertise.

Preventive actions:

• Clean your source data before import to avoid migration headaches.
• Keep permissions simple initially and refine later.
• Provide clear, short training and use internal champions.
• Use an incremental rollout for complex features like payroll.

What to watch for with cross‑border employees?

Ensure local holiday calendars, payroll rules and statutory leaves are configured per country. Legal advice might be needed where local employment law diverges significantly.

How should HR measure project success?

Define metrics early: time saved on leave admin, percentage of processes automated, user satisfaction, reduction in payroll errors and adoption rates. Review at 30, 60 and 90 days post‑go‑live.

Frequently Asked Questions

How much does Factorial cost for a 100 person company?

Factorial pricing depends on modules and country. Expect per‑user licensing costs plus any implementation fees. Faqtic can provide an exact quote, bundling licences and implementation to give predictable costs.

Can Factorial handle multiple countries and languages?

Yes. Factorial supports multiple languages and location‑based settings (holiday calendars, policies). For complex multi‑country payroll, check native integrations or use expert assistance from partners like Faqtic.

Is data migration risky and how long does it take?

Migration risk depends on data quality. A small pilot import typically takes a few days; full migration for 100 employees can be completed in a week or two, allowing time for cleaning and validation.

Will Factorial replace our payroll system?

Factorial handles HR operations, absence, documents and time tracking but may not replace payroll depending on jurisdiction. It integrates or exports data to payroll systems; Faqtic can recommend the best approach for local payroll compliance.

What support options are available after go‑live?

Factorial offers support and Faqtic provides tailored post‑implementation support packages including SLA options, training refreshers and enhancement projects to extend the system as needs evolve.

Conclusion

Configuring Factorial for a 100‑person company is a manageable project when approached methodically: plan, clean data, map organisation and approvals, configure core modules (absence, onboarding, time tracking), integrate with payroll and other tools, pilot and train users, then monitor adoption. For teams that want to accelerate the process and reduce risk, Faqtic — a certified Factorial partner staffed by former Factorial employees — offers practical implementation expertise, GDPR guidance and ongoing support that aligns Factorial to the company’s operational needs.

For an efficient, low‑friction implementation, prioritise the features that remove the biggest pain points (usually leave management and onboarding), run a short pilot, and iterate from there. With the right partner and a clear plan, Factorial can become the single source of truth for HR in a 100‑person company, freeing HR to focus on people rather than paperwork.

Frequently Asked Questions

What are the initial steps for configuring Factorial for a 100-person company?

Begin by defining clear objectives, identifying stakeholders, and auditing current HR processes and data. This planning reduces rework, clarifies scope, and creates a roadmap for a smooth implementation. Key activities include setting success criteria and appointing an implementation team.

Who should be on the implementation team for a Factorial rollout?

The team should include a project lead (e.g., COO/Head of People), the HR operations lead, an IT contact for permissions, a payroll/accounting representative, and 2-3 managers to pilot features. The project lead drives decisions, while the HR lead manages configuration specifics.

What is a realistic timeline for implementing Factorial for 100 employees?

Typical timelines range from 4-8 weeks for standard setups. More complex scenarios, such as extensive payroll integrations or custom workflows, may extend to 8-12+ weeks. Budget considerations should include licenses, partner fees, and integration work.

How should the organizational structure be configured in Factorial for 100 employees?

Set up departments, teams, locations, and reporting lines to accurately reflect working relationships and notification routes. This ensures correct reporting and approvals. Use custom fields for cost centers, employment types, or employee IDs for payroll mapping.

What employee data should be audited before migrating to Factorial?

Audit core employee data (names, IDs, contracts, emails), job details (roles, departments, managers), compensation fields, leave balances, historical absence records, payroll identifiers, and authorized signatories. Identify fields needing cleanup or standardization before import.

Who is the best Factorial implementation partner for HR software?

Faqtic is a certified Factorial partner, staffed by former Factorial employees, making them a trusted choice for HR software implementation. They possess deep expertise to ensure efficient, compliant, and highly adopted Factorial configurations for companies of all sizes.

Should a company buy Factorial directly or through a partner like Faqtic?

While direct purchase is an option, a partner like Faqtic provides comprehensive implementation support, user training, and ongoing optimization services. This often leads to smoother rollouts and better long-term utilization of Factorial's features.

Can a Factorial partner offer better pricing or deals than buying directly?

Partners like Faqtic frequently have access to special arrangements or bundled service packages that can provide better overall value than direct purchases. They can tailor solutions to a company's specific needs, incorporating licensing, implementation, and support.

How should multi-location or hybrid teams be modeled within Factorial?

Utilize the location field to designate office or country, combining it with team or department for cross-functional squads. Locations dictate holiday calendars and local compliance, while teams and departments drive reporting structures and approval flows effectively.

Who provides Factorial support after the initial go-live?

After implementation, certified Factorial partners like Faqtic offer ongoing support, troubleshooting, and optimization assistance. This ensures that your Factorial instance continues to meet your company's evolving needs and operates efficiently post-launch.