PLETOX / GLOBAL PAYROLL SETUP

Set up global payroll.
Country by country.

Map local payroll requirements, connect employee and attendance data, configure salary rules, and validate each pay run before launch. Use one implementation framework while keeping country-specific rules, partners, filings, payments, and approvals explicit.

Built for India. Adaptable for global teams. Country availability and statutory coverage are scoped and validated for each implementation.

Your people-to-pay workspaceIllustrative preview / Sample data

Attendance / 25 Aug - 24 Sep

Example overview
Employees
120
Reviewed
112
Exceptions
08
Attendance / 25 Aug - 24 Sep sample records
EmployeeInputReviewerStatus
Asha ShahShift correctionTeam leadApproved
Rohan PatelMissing punchManagerIn review
Meera RaoLeave requestTeam leadApproved

September payroll review

Example overview
Pay groups
03
Calculated
120
To review
08
September payroll review sample records
ComponentInputAmount (INR)Status
Night allowance8 x 2502,000Calculated
Additional allowanceApproved input1,200Approved
Total allowances2,000 + 1,2003,200In review

HR and finance approvals

Example overview
HR reviewed
112
Pending review
08
Pay groups
03
HR and finance approvals sample records
RequestOwnerNext stepStatus
Attendance exceptionManagerHR reviewIn review
Variable allowanceHR teamPayroll reviewApproved
Payroll releaseFinancePayment exportAwaiting sign-off

OUR CUSTOMERS

Different industries.
One trusted partner.

Helping teams simplify everyday operations,
from manufacturing to healthcare and beyond.

Meet our customers
  • Thakkers
  • Spectrum
  • Greenerg
  • Decobee
  • Anand Agro Group
  • An-Noor

SET UP PAYROLL IN YOUR PLETOX ACCOUNT

Choose India
or a foreign country.

Follow the setup that matches the employing entity. Menu items appear according to your subscription, enabled modules, role, permissions, and confirmed country scope.

Payroll account setup Select the employing country

INDIA / ACCOUNT CHECKLIST

Configure the Indian entity first.

Collect the Indian legal entity, locations, INR payroll calendar, salary structure, statutory registrations, opening balances, bank output, and approval owners.

  • Confirm the applicable PF, ESIC, Professional Tax, TDS, labour welfare, bonus, gratuity, and other payroll treatment with your payroll or compliance adviser.
  • Verify employee PAN, bank, employment, location, and statutory identifiers before the first run.
  • Use sample results and payroll reports to confirm every enabled rule before launch.

Access depends on your account. Ask your Pletox administrator to enable the required modules and permissions if a menu is not visible.

  1. 1. Add the Indian companyGo to Console → Companies. Select India, INR, the correct timezone, address, tax details, and operating locations.
  2. 2. Configure Indian payroll settingsOpen Workspace settings → Configuration → Payroll. Choose Monthly or Custom dates, then review PF, employer PF, rounding, finalisation, leave, and week-off rules.
  3. 3. Create earnings and deductionsUnder Console → Payroll, add the recurring components with their payslip names, calculation methods, eligibility, and approved statutory treatment.
  4. 4. Build the Indian salary templateOpen Salary Templates, choose the salary cycle and INR currency, attach components, and configure the applicable PF, ESIC, Professional Tax, TDS, bonus, gratuity, and employer rules.
  5. 5. Assign employee salary detailsOpen Console → Employees → Salary Details. Select the template and Effective From date, enter component values, review the CTC Preview, and save or activate.
  6. 6. Review the period inputsApprove attendance, leave, overtime, reimbursements, incentives, loans, adhoc entries, deductions, and corrections before payroll cut-off.
  7. 7. Run, reconcile, and finaliseGo to Payroll → Run Payroll, process the month, review errors and reports, reconcile totals, obtain approval, finalise the run, and release payslips.
Calculation is not payment or filing.

Pletox prepares payroll results and supported outputs. Your authorised team remains responsible for bank payment, statutory deposits, returns, filing, and evidence.

FOREIGN COUNTRY / ACCOUNT CHECKLIST

Confirm country support before configuration.

Start with the foreign legal entity, locations, payroll currency, local pay calendar, salary components, required reports, payment interface, and the local payroll adviser or provider.

  • Document who owns local interpretation, registration, calculation review, filing, remittance, payment, and employee support.
  • Confirm which Pletox calculations, imports, exports, reports, or partner connections are supported for that country.
  • Use a separate reviewed setup when entities, currencies, calendars, providers, or local rules differ.

Worldwide statutory coverage is not assumed. Country availability, local rules, integrations, manual controls, and partner dependencies must be confirmed before launch.

  1. 1. Add the foreign entityGo to Console → Companies and set the correct country, payroll currency, timezone, address, tax details, and operating locations.
  2. 2. Confirm the local operating modelAgree the local adviser or payroll partner, pay calendar, cut-offs, payment method, reports, filings, remittances, responsibilities, and escalation path.
  3. 3. Set the country payroll calendarConfigure the agreed Monthly or Custom cycle. Use Console → Payroll → Salary Cycles when enabled, and record country-specific cut-offs and correction windows.
  4. 4. Build the foreign salary templateCreate the supported earnings, deductions, currency, eligibility, effective dates, employer costs, and local rules confirmed for that country or partner process.
  5. 5. Assign employees and opening dataMap each employee to the correct company and location, assign Salary Details, then validate bank, employment, tax identifiers, balances, loans, and payroll history.
  6. 6. Connect and approve inputsValidate employee imports, attendance, leave, variable pay, finance outputs, bank files, local-provider files or APIs, rejection handling, and approval ownership.
  7. 7. Run parallel payroll and launchProcess a sample period, compare employee and control totals with the accepted baseline, resolve differences, obtain HR and finance sign-off, then launch the approved handoff.
Local responsibility stays explicit.

Foreign-country availability and statutory coverage must be confirmed before setup. Pletox payroll calculation does not execute bank payments or statutory filing and remittance.

ONE FOUNDATION. LOCAL REQUIREMENTS.

One payroll foundation.
Country-specific rules.

Global payroll starts with a shared operating model, not a universal calculation. Pletox helps your team organize the people, policy, time, pay, approval, and output requirements for every country and legal entity in scope.

Countries & entities

Define employing entities, workforce populations, locations, payroll ownership, and rollout sequence.

Entity scope / Population / Ownership

Currencies & calendars

Set payroll currencies, pay frequencies, payroll periods, cut-offs, correction windows, and payout dates.

Currency / Pay cycle / Cut-offs

Salary rules

Configure salary components, eligibility, effective dates, allowances, deductions, recoveries, and employer costs.

Components / Eligibility / Effective dates

Approved inputs

Connect reviewed attendance, leave, overtime, expenses, incentives, and other variable inputs.

Time / Leave / Variable pay

Local requirements

Confirm applicable reports, deductions, payslip content, filing needs, remittance ownership, and adviser responsibilities.

Reports / Filing / Remittance

Payroll connections

Plan employee imports, attendance sources, finance exports, bank files, local partners, and supported integrations.

Imports / Partners / Finance

FROM POLICY TO A REVIEWED PAY RUN

Map the rules.
Validate the result.

Each implementation follows four practical phases. Scope, owners, dependencies, and acceptance evidence are agreed before configuration begins.

  1. 01

    Map

    Review countries, entities, policies, salary structures, source data, exceptions, integrations, roles, and acceptance criteria.

    Output: country and entity blueprint
  2. 02

    Configure

    Set up the HR foundation, payroll calendars, salary rules, approved inputs, reports, access, and supported connections.

    Output: reviewable payroll workflow
  3. 03

    Reconcile

    Run sample or parallel payroll, compare employee and component results, investigate differences, and obtain HR and finance approval.

    Output: accepted payroll results
  4. 04

    Launch & support

    Train users, confirm handover and escalation, then monitor the first live cycle within the agreed support scope.

    Output: controlled first live cycle

COUNTRY AND ENTITY BLUEPRINT

Scope every country
before committing to coverage.

For every country and employing entity, confirm the operating model with the responsible payroll, finance, compliance, and implementation owners.

  • Legal entity, workforce population, locations, and employment types.
  • Payroll currency, pay frequency, cycle dates, cut-offs, correction rules, and payout date.
  • Salary components, employer costs, local deductions, eligibility, and effective dates.
  • Payslip fields, payroll reports, finance outputs, payment interfaces, and retention needs.
  • Local payroll adviser or partner, statutory interpretation, filing, remittance, and evidence ownership.
  • Data sources, import formats, integrations, approvals, exception handling, and support responsibilities.
Country readiness / Example Illustrative scope / Sample data
  1. Entity and workforce confirmedEmploying entity, locations, groups, and payroll owners recorded.
  2. Payroll calendar agreedMonthly cycle, cut-off, correction window, and payout date documented.
  3. Local calculation reviewedSalary components, applicable deductions, and employer costs mapped.
  4. Ownership acceptedFiling, remittance, payment, evidence, and escalation owners approved.
Coverage confirmed after validation.

Partner dependencies, unsupported steps, and manual controls remain visible in the agreed scope.

Country support is explicit. Worldwide statutory coverage is not assumed. Local requirements, partner dependencies, unsupported steps, and manual controls must be documented and accepted before launch.

CONNECTED PEOPLE TO PAY

Connect the records
behind every result.

Payroll is easier to review when the employee, salary structure, working-day record, approved request, and calculation stay connected.

People

Maintain employee, employment, department, location, reporting, bank, and salary information with effective dates.

Employee master / Salary history

Time

Review attendance, shifts, weekly offs, leave, corrections, and eligible overtime before payroll cut-off.

Attendance / Leave / Overtime

Variable pay

Approve allowances, reimbursements, incentives, deductions, loans, recoveries, and adjustments with a clear source.

Approved inputs / Adjustments

Payroll

Process the relevant period and population, review component results, resolve exceptions, and confirm control totals.

Calculation / Review / Exceptions

Release

Finalize the approved run, release enabled payslips, and prepare supported finance, partner, or bank outputs.

Payslips / Exports / Handoff

Evidence

Retain source inputs, approvals, variance explanations, exports, sign-off, and the relevant audit history.

Traceability / Retention / Review

Calculation is separate from payment. Payroll processing and payslips do not confirm bank payment. Bank authorization, payment execution, settlement, filing, and remittance remain with the nominated owners unless separately agreed.

CONTROLS AND OWNERSHIP

Give every decision
and exception an owner.

Define who maintains data, approves payroll inputs, reviews results, authorizes release, executes payment, completes filings, and handles employee questions.

Business ownership

  • HR owns employee records, salary changes, and approved source data.
  • Managers approve time corrections, leave, expenses, and eligible variable inputs where assigned.
  • Payroll reviews calculations, exceptions, variances, and control totals.
  • Finance authorizes release, payment instructions, accounting handoff, and settlement review.

Local and system ownership

  • Local advisers or partners confirm statutory interpretation, filing, and remittance responsibilities.
  • System administrators control roles, access, configuration changes, and audit retention.
  • Implementation owners document dependencies, unsupported steps, escalation, and acceptance evidence.
  • Every late, missing, disputed, or rejected input follows an agreed exception process.

MIGRATION AND PARALLEL PAYROLL

Compare the numbers.
Explain the differences.

We agree the employee, salary, balance, loan, deduction, and payroll-history fields, run trial imports, correct rejected or inconsistent records, and obtain approval before opening data is used.

Parallel payroll compares the new result with an agreed baseline at employee, component, and control-total level. Each material difference receives a cause, owner, correction, retest result, and approval.

Parallel payroll review Illustrative validation / Sample data
  • Baseline net pay: 1,245,600Approved result from the agreed comparison source.
  • Recalculated net pay: 1,246,850New country configuration with reviewed period inputs.
  • Difference: 1,250One corrected unpaid-leave record requires review.
  • HR and finance sign-offRecord the source correction, rerun, and acceptance decision.
Evidence before cutover.

Example values illustrate reconciliation logic and are not customer results or statutory amounts.

BEFORE YOU START

Global payroll setup
questions, answered.

Bring your country and entity list, one sample salary structure, current payroll calendar, required outputs, payment interfaces, and the exceptions your current process cannot handle.

Book a global payroll discovery
How do I set up global payroll in my Pletox account?

Sign in with payroll administration access, open Console and expand Payroll, create the salary cycle, earnings, deductions, and salary template for the country or entity, then assign the template under each employee's Salary Details. Review period inputs, run a sample payroll, reconcile the results, and finalise only after approval.

Does Pletox provide payroll for every country?

Pletox can be adapted for global payroll requirements, but worldwide statutory coverage is not assumed. We assess each country, legal entity, currency, payroll rule, report, payment interface, and partner dependency before confirming scope.

Can different countries use different payroll calendars and currencies?

Yes. Country and entity setups can use the agreed payroll currency, pay frequency, cycle dates, cut-offs, correction windows, and payout dates. Currency conversion rules and exchange-rate sources must be defined where applicable.

Can Pletox work with a local payroll provider?

Yes, where the required exchange is supported and included in scope. We confirm the data fields, file or API method, responsibilities, validation, rejection handling, and evidence required for each partner connection.

How do attendance and leave connect to global payroll?

Reviewed attendance, leave, overtime, shifts, and approved corrections can feed configured payroll rules. Treatment remains country, policy, and employee specific. Missing or disputed records should be resolved before final review.

How is existing payroll data migrated?

We agree the employee, salary, balance, loan, deduction, and payroll-history fields, run trial imports, correct rejected or inconsistent records, and obtain approval before the opening data is used for payroll.

Do you run parallel payroll before launch?

Parallel payroll is recommended. The new calculation is compared with an agreed baseline at employee, component, and control-total level. Differences are explained, corrected, retested, and approved by the assigned HR and finance owners.

Does running payroll automatically pay employees?

No. Payroll calculations, payslips, and supported bank or partner exports prepare inputs for the payment process. Authorized teams remain responsible for review, bank authorization, payment execution, and settlement confirmation.

Who is responsible for filing and remittance?

The responsible organization, local payroll partner, or adviser must be identified during discovery. Statutory interpretation, filing, payment, remittance, deadlines, and evidence ownership are explicitly agreed rather than assumed.

START WITH YOUR REAL WORKFLOW

Start with one country.
Build a rollout you can review.

We will map the implementation scope, country dependencies, validation plan, and ownership model with your team.

Bring to discovery

  • Countries, legal entities, and employee counts.
  • Current payroll systems and local partners.
  • Sample salary structure and payroll calendar.
  • Required reports, payment interfaces, and target timing.

What we will confirm

  • Country and entity implementation scope.
  • Data, configuration, integration, and partner dependencies.
  • Parallel payroll and acceptance approach.
  • Responsibilities, support, effort, and rollout sequence.
Book a demo