Payroll Systems

India payroll complexity: 1) Salary Structure: Indian CTC (Cost to Company) is NOT the same as gross salary. CTC = Gross Salary + Employer PF + Employer ESI + Gratuity provision + other employer costs. Gross Salary = Basic + HRA + Special Allowance + other components. Basic: typically 40-50% of CTC. HRA: linked to Basic (50% for metro, 40% for non-metro). Each component has different tax treatment. 2) Gross-to-Net Calculation: Start with monthly gross. Add: arrears, bonus, overtime, reimbursements. Deduct: Employee PF (12% of Basic, capped at ₹1800 on ₹15000 Basic for statutory, many companies contribute on full Basic). ESI: 0.75% of gross if gross ≤ ₹21,000/month. Professional Tax: varies by state (Maharashtra: ₹200/month, Karnataka: ₹200/month, Tamil Nadu: different slabs). Income Tax TDS: computed annually, divided by remaining months. 3) Tax Regime Implementation: Old Regime: lower basic exemption (₹2.5L), but allows deductions — 80C (₹1.5L), 80D (₹25K-₹75K), HRA exemption, standard deduction (₹50K), NPS (80CCD ₹50K). New Regime (default from FY 2024-25): higher exemption (₹3L), lower slab rates, but almost no deductions. System must: a) allow employee to choose regime, b) show comparison calculator, c) compute TDS under chosen regime, d) allow switching before filing (but employer follows declared regime monthly). 4) Data Model: Employee → PayStructure → [PayComponent]. PayComponent = {name, type: EARNING|DEDUCTION|EMPLOYER_CONTRIBUTION, amount/formula, taxable: boolean, statutory: boolean}. PayrollRun → [PayrollResult]. PayrollResult = {empId, earnings[], deductions[], employerContributions[], grossPay, totalDeductions, netPay}. TaxComputation = {empId, fy, regime, grossIncome, exemptions[], deductions[], taxableIncome, taxAmount, cessTDS}. 5) Rule Engine: Tax rules change annually (budget). Implement as configurable rules (not hardcoded). Rule: {ruleId, category, effectiveFrom, effectiveTo, jurisdiction, formula/slabs}. Example: PF rule: IF basic ≤ 15000 THEN employer_pf = basic × 0.12 ELSE employer_pf = 1800. ESI rule: IF monthly_gross ≤ 21000 THEN esi_employee = gross × 0.0075. Use Drools or custom rule engine for complex calculations. 6) Validation: Post-calculation validation critical: net pay should not be negative, TDS should not exceed gross, PF should match formula, total debits = total credits (accounting). Flag anomalies for manual review before approval.

EPF is India's largest social security scheme affecting 65M+ subscribers: 1) Contribution Structure: Employee contribution: 12% of Basic + DA (capped at ₹15,000 for statutory, but many companies contribute on actual). Employer contribution: 12% of Basic + DA, split as: 3.67% → EPF (Employee Provident Fund), 8.33% → EPS (Employee Pension Scheme — capped at ₹15,000 Basic). Admin charges: 0.50% of Basic (EPFO admin) + 0.50% EDLI (Employee Deposit-Linked Insurance). 2) UAN & KYC: Each member gets Universal Account Number (UAN) — stays same across jobs. KYC linking: Aadhaar, PAN, bank account, mobile. New joiner: employer registers on EPFO portal → UAN generated. Transfer: when employee changes company, PF balance auto-transfers via UAN. 3) ECR (Electronic Challan cum Return): Monthly filing required by 15th of following month. ECR file format: pipe-delimited text file with employee-wise breakdown. Fields: UAN, Name, Gross Wages, EPF Wages, EPS Wages, EDLI Wages, EPF contribution (EE+ER), EPS contribution, and NCP days. Validation: UAN must be active, name must match EPFO records (mismatch = rejection), wages ≤ 0 not allowed. After upload: EPFO validates, generates challan. Payment via internet banking (SBI, HDFC, etc.). 4) Technical Implementation: a) Monthly computation: For each employee: identify EPF-applicable components (Basic + DA typically). Apply ceiling if statutory (₹15,000). Calculate: EE share = wage × 12%, ER EPF = wage × 3.67%, ER EPS = min(wage, 15000) × 8.33%. Track NCP (Non-Contribution Period) days for partial month. b) ECR generation: Query all employees with EPF flag. Generate fixed-format text file. Validate against EPFO rules. Upload via EPFO employer portal API (or manual upload). c) Challan tracking: After ECR accepted, payment challan generated. Track TRRN (Transaction Reference Number). Reconcile: amount deposited = computed amount. d) Annual: interest credit (8.1% for FY 2023-24) by EPFO. Form 12A filing. 5) Edge Cases: International workers: Social Security Agreements (SSAs) with 20+ countries — may be exempt from EPF. VPF (Voluntary Provident Fund): employee contributes >12%, no matching employer contribution. Exit: employee can withdraw after 2 months of unemployment, or transfer. If withdrawn before 5 years: taxable. 6) New Labor Code Impact: Social Security Code 2020 (not yet implemented) will: expand PF to gig workers, introduce universal social security, change definition of 'wages' (could increase PF base).

Global payroll is one of the most complex enterprise systems due to country-specific regulations: 1) Architecture: Aggregator Model (most common): Core platform provides unified UI, reporting, and data management. Country-specific payroll engines (either owned or partnered) handle local calculations. Example: Papaya Global — unified platform, local engines in each country. Alternative: Local Vendor Model: ADP GlobalView uses local ADP engines. Deel partners with local providers in each country. 2) Key Challenges per Country: Tax calculations: progressive vs flat tax, social contributions, municipal tax (Sweden has 290 municipalities with different rates). Pay frequency: US (bi-weekly), UK (monthly), some countries (weekly). Statutory requirements: pension (PF in India, CPF in Singapore, 401k in US), health (ESI in India, NHS in UK), social security. Paid leave: India (15-30 earned leave), France (25 vacation + RTT), unlimited in some US companies. Termination: at-will (US), notice period + severance (India), near-impossible without cause (France). Currency: local currency for salary, HQ currency for reporting. 3) Data Model: Employee: global ID + country-specific profile. GlobalPayStructure: {baseComponents + countrySpecificComponents}. CountryConfig: {taxRules, statutoryContributions, payFrequency, calendarRules, reportingRequirements}. PayrollRun: {countryCode, period, status, localCurrency, exchangeRate, grossLocal, netLocal, grossHQ}. 4) Compliance Framework: Regulatory database: maintain tax tables, contribution rates, minimum wages for 50 countries. Update mechanism: legal team + automated monitoring for regulatory changes. Country goes live: 6-12 months for localization (understand laws, build rules, test, certify). Audit trail: every calculation must be explainable for tax authority audit. 5) Reporting: Unified dashboard: total payroll cost by country, department, currency. Consolidation: convert all local currencies to HQ currency for financial reporting. Statutory reports: country-specific formats (Form 16 India, P45 UK, W-2 US). Analytics: cost per employee by country, tax efficiency, benefit utilization. 6) Integration: Global HRIS (Workday, SAP SuccessFactors) as system of record. Local banking for salary disbursement (SWIFT for international transfers). Local tax portals (EPFO India, HMRC UK, IRS US). GL posting: multi-entity, multi-currency journal entries. 7) Build vs Buy Decision: Build in-house: only feasible for 2-3 countries, years of effort. Buy platform: ADP, Papaya Global, Deel — 3-6 month implementation. Most companies: own-country payroll built/bought + partner for international. Hybrid: managed payroll for small offices (<50 employees in a country), owned for large.

Payroll contains the most sensitive employee data and is a common fraud target: 1) Common Payroll Frauds: Ghost employees: fake employees on payroll, salary goes to fraudster's account. Buddy punching: one employee clocks in for absent colleague. Overtime fraud: inflated overtime hours, especially in manufacturing/retail. Commission fraud: manipulated sales figures for higher commission. Expense fraud: fake or inflated reimbursement claims. Salary diversion: changing bank account to fraudster's account. 2) Prevention Controls: a) Ghost Employee Detection: Cross-reference payroll with HRIS — every payee must have active employee record with hiring documentation. Aadhaar/PAN verification: ensure unique individuals. Biometric attendance: prevent attendance for non-existent employees. Periodic headcount audit: physical verification vs payroll count. AI/ML: detect anomalies — employee with no manager, no email activity, no attendance but getting paid. b) Segregation of Duties: Person who adds employees ≠ person who runs payroll ≠ person who approves disbursement. Four-eye principle: every payroll run requires two approvers. Bank account changes require: employee self-service request + HR verification + additional authentication (OTP to registered mobile). c) Technical Controls: Encryption: payroll data encrypted at rest (AES-256) and in transit (TLS 1.3). Access control: RBAC with minimum privilege — payroll admin can run payroll but can't change salary structure. Audit log: every action logged — who viewed, modified, approved payroll data. Cannot be tampered (write-once log or blockchain-backed). Database: salary fields in separate encrypted columns, access logged. Masking: in non-production environments, use anonymized/synthetic payroll data. d) Anomaly Detection: Compare month-over-month: flag if total payroll changes >5% without explanation. Flag: new bank accounts added close to payroll date. Flag: same bank account for multiple employees. Flag: employees with no attendance records getting full pay. Flag: overtime >20% of regular hours consistently. Statistical analysis: employees paid significantly above/below band for their grade. 3) Compliance Controls: SOX compliance (for US-listed companies): documented payroll controls, quarterly testing. SOC 2 Type II: for SaaS payroll providers — certified security controls. GDPR (EU): salary data is personal data — consent, access rights, data minimization. India DPDP Act 2023: similar privacy obligations for employee data. 4) Incident Response: If fraud detected: freeze payments, preserve evidence, investigate. Notify: legal team, internal audit, law enforcement if material. Recovery: attempt to recall wire transfers (limited window). Post-incident: root cause analysis, strengthen controls, retrain staff.

India is consolidating 29 central labor laws into 4 codes. While passed in 2019-2020, implementation is pending (states must notify rules): 1) Four New Codes: a) Code on Wages, 2019: Redefines 'wages' — basic pay must be ≥50% of total remuneration. Impact: if company currently has basic at 30% of CTC, PF/gratuity base increases dramatically. Allowances like HRA, conveyance still allowed but cannot exceed 50% of total. Universal minimum wage floor for entire country. b) Code on Social Security, 2020: Extends PF, ESI to gig/platform workers (Uber drivers, Swiggy delivery). New social security fund for unorganized workers. ESI threshold may change. Maternity benefit, gratuity provisions consolidated. c) Code on Industrial Relations, 2020: Standing Orders mandatory for 300+ employees (currently 100+). Fixed-term employment recognized (contract workers get same benefits as permanent). Strike/lockout rules modified. d) Code on Occupational Safety, Health and Working Conditions, 2020: Working hours: max 48 hours/week (unchanged) but allows 4-day work week (12 hours/day). Overtime: 2x wages (currently defined differently across acts). Inter-state migrant worker protections. 2) Payroll System Impact: a) Wage Restructuring: Current CTC: Basic (30%) + HRA (15%) + Special Allowance (40%) + Employer PF (12%) + others. New CTC: Basic must be ≥50% of (Basic + DA + all allowances). This means: Basic increases → PF base increases → employer cost increases (or take-home decreases). System must: re-model all pay structures, simulate cost impact, allow mass updates. b) PF/Gratuity Impact: Higher basic = higher PF contribution (both employee and employer). Gratuity (15 days salary per year): higher basic = higher gratuity liability. Companies may need to provision for increased gratuity (balance sheet impact). c) Leave & Working Hours: New overtime rules: system must track weekly hours (not just daily). Leave encashment: may change with new leave provisions. Compensatory off rules: standardized. d) Compliance Changes: New forms and returns (replacing old formats). Different thresholds for applicability. State-specific rules (each state notifies independently — may implement at different dates). 3) Technical Preparation: a) Configurable Wage Definition: Wage = configurable formula per jurisdiction + effective date. Same employee may have different wage definitions for PF vs ESI vs Gratuity vs Bonus. Support transition: old definition until date X, new definition from date Y. b) Mass Restructuring Tool: Simulate: 'if we move basic to 50%, show impact on every employee's take-home and company cost'. Bulk update: change pay structures for all employees with audit trail. What-if analysis: model different restructuring options. c) Dual Compliance: During transition: some states may implement codes while others haven't. System must support: old rules for state A, new rules for state B. Date-effective configuration: on notification date, automatically switch to new rules. d) Testing Strategy: Regression: every existing payroll scenario must still work. New scenarios: gig worker payroll, fixed-term employee benefits, 4-day work week overtime. Parallel run: run payroll under old and new rules simultaneously, compare, validate. 4) Timeline: Companies should prepare NOW — the codes can be notified with 30-90 days notice. Payroll vendors (greytHR, Keka, ADP) are building readiness. Smart companies are already restructuring CTC to minimize disruption.