Countries & entities
Define employing entities, workforce populations, locations, payroll ownership, and rollout sequence.
Entity scope / Population / OwnershipPLETOX / GLOBAL PAYROLL SETUP
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.
| Employee | Input | Reviewer | Status |
|---|---|---|---|
| Asha Shah | Shift correction | Team lead | Approved |
| Rohan Patel | Missing punch | Manager | In review |
| Meera Rao | Leave request | Team lead | Approved |
| Component | Input | Amount (INR) | Status |
|---|---|---|---|
| Night allowance | 8 x 250 | 2,000 | Calculated |
| Additional allowance | Approved input | 1,200 | Approved |
| Total allowances | 2,000 + 1,200 | 3,200 | In review |
| Request | Owner | Next step | Status |
|---|---|---|---|
| Attendance exception | Manager | HR review | In review |
| Variable allowance | HR team | Payroll review | Approved |
| Payroll release | Finance | Payment export | Awaiting sign-off |
OUR CUSTOMERS
Helping teams simplify everyday operations,
from manufacturing to healthcare and beyond.






SET UP PAYROLL IN YOUR PLETOX ACCOUNT
Follow the setup that matches the employing entity. Menu items appear according to your subscription, enabled modules, role, permissions, and confirmed country scope.
INDIA / ACCOUNT CHECKLIST
Collect the Indian legal entity, locations, INR payroll calendar, salary structure, statutory registrations, opening balances, bank output, and approval owners.
Access depends on your account. Ask your Pletox administrator to enable the required modules and permissions if a menu is not visible.
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
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.
Worldwide statutory coverage is not assumed. Country availability, local rules, integrations, manual controls, and partner dependencies must be confirmed before launch.
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.
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.
Define employing entities, workforce populations, locations, payroll ownership, and rollout sequence.
Entity scope / Population / OwnershipSet payroll currencies, pay frequencies, payroll periods, cut-offs, correction windows, and payout dates.
Currency / Pay cycle / Cut-offsConfigure salary components, eligibility, effective dates, allowances, deductions, recoveries, and employer costs.
Components / Eligibility / Effective datesConnect reviewed attendance, leave, overtime, expenses, incentives, and other variable inputs.
Time / Leave / Variable payConfirm applicable reports, deductions, payslip content, filing needs, remittance ownership, and adviser responsibilities.
Reports / Filing / RemittancePlan employee imports, attendance sources, finance exports, bank files, local partners, and supported integrations.
Imports / Partners / FinanceFROM POLICY TO A REVIEWED PAY RUN
Each implementation follows four practical phases. Scope, owners, dependencies, and acceptance evidence are agreed before configuration begins.
Review countries, entities, policies, salary structures, source data, exceptions, integrations, roles, and acceptance criteria.
Output: country and entity blueprintSet up the HR foundation, payroll calendars, salary rules, approved inputs, reports, access, and supported connections.
Output: reviewable payroll workflowRun sample or parallel payroll, compare employee and component results, investigate differences, and obtain HR and finance approval.
Output: accepted payroll resultsTrain users, confirm handover and escalation, then monitor the first live cycle within the agreed support scope.
Output: controlled first live cycleCOUNTRY AND ENTITY BLUEPRINT
For every country and employing entity, confirm the operating model with the responsible payroll, finance, compliance, and implementation owners.
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
Payroll is easier to review when the employee, salary structure, working-day record, approved request, and calculation stay connected.
Maintain employee, employment, department, location, reporting, bank, and salary information with effective dates.
Employee master / Salary historyReview attendance, shifts, weekly offs, leave, corrections, and eligible overtime before payroll cut-off.
Attendance / Leave / OvertimeApprove allowances, reimbursements, incentives, deductions, loans, recoveries, and adjustments with a clear source.
Approved inputs / AdjustmentsProcess the relevant period and population, review component results, resolve exceptions, and confirm control totals.
Calculation / Review / ExceptionsFinalize the approved run, release enabled payslips, and prepare supported finance, partner, or bank outputs.
Payslips / Exports / HandoffRetain source inputs, approvals, variance explanations, exports, sign-off, and the relevant audit history.
Traceability / Retention / ReviewCalculation 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
Define who maintains data, approves payroll inputs, reviews results, authorizes release, executes payment, completes filings, and handles employee questions.
MIGRATION AND PARALLEL PAYROLL
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.
Example values illustrate reconciliation logic and are not customer results or statutory amounts.
BEFORE YOU START
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 discoverySign 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.
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.
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.
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.
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.
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.
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.
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.
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
We will map the implementation scope, country dependencies, validation plan, and ownership model with your team.