<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Priyom Sarkar on Medium]]></title>
        <description><![CDATA[Stories by Priyom Sarkar on Medium]]></description>
        <link>https://medium.com/@priyomsarkar?source=rss-197efc53e9b2------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*RAvlOh84ZvlfQeUW</url>
            <title>Stories by Priyom Sarkar on Medium</title>
            <link>https://medium.com/@priyomsarkar?source=rss-197efc53e9b2------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 14:54:02 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@priyomsarkar/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[7 Checks Before You Sign a Payroll Software Contract in India]]></title>
            <link>https://priyomsarkar.medium.com/7-checks-before-you-sign-a-payroll-software-contract-in-india-3864c9b603ce?source=rss-197efc53e9b2------2</link>
            <guid isPermaLink="false">https://medium.com/p/3864c9b603ce</guid>
            <category><![CDATA[employer-of-record]]></category>
            <category><![CDATA[smart-contracts]]></category>
            <category><![CDATA[global-hiring]]></category>
            <dc:creator><![CDATA[Priyom Sarkar]]></dc:creator>
            <pubDate>Mon, 02 Nov 2026 12:10:00 GMT</pubDate>
            <atom:updated>2026-11-02T12:10:00.416Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pDdaync8c6qRu6vBtETYQg.jpeg" /></figure><p><em>By Priyom Sarkar, Founder &amp; CEO, Asanify AI</em></p><p>Most payroll software demos look identical. A clean dashboard, a “run payroll” button, a payslip PDF. The differences show up in month three, when a state-level tax changes, an employee leaves mid-month, or your auditor asks who approved a salary revision.</p><p>So skip the feature tour. Here are the seven checks I would run before signing anything, whether you are a 30-person startup or a 300-person company moving off spreadsheets.</p><p><em>Disclosure: I run Asanify, which sells payroll software in India, so I have a stake in this. I have tried to write the checklist so it works on any vendor, including us.</em></p><p>First, what payroll in India actually has to get right?</p><p>Indian payroll is not one calculation. It is a stack of separate obligations that each have their own rules and deadlines:</p><ul><li>Provident Fund contributions, administered by the EPFO</li><li>ESI contributions for employees under the wage ceiling, administered by ESIC</li><li>TDS on salary under the Income Tax Act, with quarterly returns and annual Form 16</li><li>Professional Tax and Labour Welfare Fund, which differ state by state</li><li>Payslips, bonus and gratuity rules, and the labour codes now being phased in</li></ul><p>Rates, ceilings and due dates change. Treat any number in a sales deck as a claim to verify on the official portal, not a fact.</p><h3>Check 1: Does it handle your states, not just “India”?</h3><p>Professional Tax and Welfare Fund rules vary by state. If you have people in Karnataka, Maharashtra and Delhi, ask the vendor to show you the exact setup for each state and how often the rules are updated. “We cover all states” is an answer. “Here is last month’s update log” is a better one.</p><h3>Check 2: Can you run payroll twice before you commit?</h3><p>Ask for a parallel run. Take one real month, run it in the new system and your current process, and compare net pay line by line. A vendor confident in its engine will agree to this. Every difference you find in the parallel run is a difference your employees would have found in production.</p><h3>Check 3: Who approved that change?</h3><p>Salary revisions, one-off bonuses and deductions should leave a trail: who changed it, when, and who signed off. Ask to see the audit log and whether the system supports a maker-checker step, where one person prepares and another approves. For anyone who has sat through a statutory audit, this is not optional.</p><h3>Check 4: How does it deal with the messy middle of the month?</h3><p>Joiners, leavers, loss of pay days, arrears, and mid-month salary changes are where spreadsheets break and where cheaper tools quietly fall over. Give the vendor three ugly cases from your own history and watch how the proration works. If they cannot show it live, they probably cannot do it cleanly.</p><h3>Check 5: Tax declarations and Form 16</h3><p>Employees submit investment declarations, proofs come in late, and the projected tax changes every month. Check how declarations are collected, whether proofs can be uploaded by employees from a phone, and how Form 16 and the quarterly TDS return data are produced. This is the single biggest source of HR inbox traffic every February and March.</p><h3>Check 6: Is payroll connected to attendance and leave?</h3><p>Payroll that does not read attendance and leave data means someone re-keys the loss of pay days every month. That someone makes mistakes. Ask whether attendance, leave and payroll live in one system or three, and what happens when a leave request is approved after the cut-off. For a view of how we approach the attendance side, see our attendance management page.</p><h3>Check 7: What will it cost at 50, 150 and 300 employees?</h3><p>Pricing models differ. Some charge per employee per month, some add setup fees, some charge extra for statutory filings or payslip customisation. Ask for a written quote at your current headcount and at double it. Then ask what is not included. The cheapest line item on the quote is rarely the cheapest outcome.</p><h3>A fair way to score the shortlist</h3><p>Give each check a score from 0 to 2 and total them for each vendor. Weight Check 2 and Check 3 double, because they predict whether you will trust the numbers. Do not weigh the price above 20 per cent of the total. A payroll mistake costs more than a software fee.</p><p>Where we try to win is ease of use. Asanify is rated number one for ease of use on G2 in HRMS, payroll and EOR, which you can verify on G2 directly. We are a small, profitable team, and we know that does not suit every buyer. If your priority is a very large enterprise suite with deep customisation, put that on your shortlist criteria and test us against it.</p><p>If you want to see how we handle these seven checks, our guide to payroll software in India walks through the criteria and what we cover. And if you also hire outside India, our global EOR page explains how that side works.</p><h3>Questions to take into your next demo</h3><p>Can we do a parallel run on one real month of our data?</p><p>Show me the audit log for a salary revision.</p><p>How are state-level Professional Tax changes rolled out?</p><p>What is the total cost at our headcount and at twice our headcount, in writing?</p><p>Who do I call when a filing deadline is two days away?</p><p>If a vendor answers all five without hesitation, you are talking to a team that has done this before.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3864c9b603ce" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Hiring One Person in Luxembourg Is Easy. Hiring Them Correctly Takes Reading the Fine Print]]></title>
            <link>https://priyomsarkar.medium.com/hiring-one-person-in-luxembourg-is-easy-hiring-them-correctly-takes-reading-the-fine-print-b88d7fac67db?source=rss-197efc53e9b2------2</link>
            <guid isPermaLink="false">https://medium.com/p/b88d7fac67db</guid>
            <category><![CDATA[luxembourg]]></category>
            <category><![CDATA[employer-of-record]]></category>
            <category><![CDATA[hiring-strategy]]></category>
            <category><![CDATA[cross-border-payments]]></category>
            <category><![CDATA[global-hiring]]></category>
            <dc:creator><![CDATA[Priyom Sarkar]]></dc:creator>
            <pubDate>Fri, 23 Oct 2026 04:01:02 GMT</pubDate>
            <atom:updated>2026-10-23T04:01:02.555Z</atom:updated>
            <content:encoded><![CDATA[<p><em>By Priyom Sarkar, Co-founder &amp; CEO, Asanify</em></p><blockquote>Disclosure first. I run a company that provides Employer of Record services, and Luxembourg is one of the countries we cover. I will try to make this useful whether or not you ever speak to us.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4axhWFXZc_C0QSlDDj5ybg.jpeg" /></figure><p>Luxembourg tends to show up on a hiring plan for a specific reason. A fund administrator you need. A sales lead who lives on the French or Belgian border and wants a Luxembourg contract. A compliance hire close to an EU regulator. Rarely is it “we are building a team of 40 there next year.” It is one person, sometimes two, and the company has no entity in the Grand Duchy.</p><p>That is exactly the situation an Employer of Record (EOR) exists for. But the same features that make Luxembourg attractive to employees, strong protections and generous pay, are the ones that catch foreign employers off guard.</p><h3>The probation clause only exists if you write it down</h3><p>Probation is not automatic in Luxembourg. If the contract does not contain a probation clause, there is no probation. Full stop.</p><p>When a clause is included, the legal ceilings for an open-ended contract are generally 6 months for most salaried roles and 3 months for lower-qualified roles, with a longer window possible for senior hires whose pay is well above the qualified minimum wage. Terminating during probation still requires notice, scaled to the time already served, with a legal minimum and maximum. The labour inspectorate (ITM) publishes the exact rules, and they are worth reading before you draft anything (ITM Q&amp;A on probation notice).</p><p>&gt; If you copy a probation clause from your US or UK template, assume it is wrong for Luxembourg until someone local has checked it.</p><h3>Notice after probation grows with tenure</h3><p>Once probation is over, an employer dismissing someone owes notice that steps up with length of service. Commonly cited figures are 2 months for under 5 years, 4 months for 5 to 10 years and 6 months beyond that. Employees resigning have shorter periods. Add the procedural rules around dismissal (in many cases a prior meeting and written reasons on request), and the “we will just let them go if it does not work” mindset gets expensive fast.</p><p>This is the single biggest reason I tell founders to budget for the exit on day one, not the day they need it.</p><h3>What it costs on top of salary</h3><p>Employer social security in Luxembourg is moderate by EU standards, which surprises people. Published employer rates include pension insurance at 8%, health insurance around 3%, dependency insurance, a sector-dependent accident insurance rate, and family-related contributions, among others. Ceilings apply to some contributions. Always confirm the current year’s rates with a local payroll provider before you sign an offer, because they are reviewed regularly.</p><p>The items that actually move the budget are often not the contributions at all:</p><ol><li>Salary indexation. Luxembourg wages are index-linked. When the cost-of-living index triggers, salaries rise automatically. If your offer is a fixed number in a spreadsheet, it will be wrong within the year.</li><li>Minimum wage levels. There is a statutory social minimum wage, with a higher “qualified” rate. Senior hires are well above it, but it matters for probation length and some thresholds.</li><li>Leave. Statutory paid annual leave is generous by global standards, plus public holidays. Plan coverage accordingly.</li><li>Cross-border workers. A large share of Luxembourg’s workforce commutes from France, Belgium or Germany. Their social security and tax position can depend on how many days they work outside Luxembourg. Ask where your hire will actually sit day to day.</li></ol><h3>Where foreign employers typically trip</h3><p>Assuming &#39;EU&#39; means &#39;uniform&#39;. Luxembourg rules are not French, German or Belgian rules, even when the employee lives in one of those countries.</p><p>Ignoring the commute. A hire who works two days a week from home across the border can change which country’s social security applies. That is a question for before the contract, not after.</p><p>Under-scoping the contract. Working time, overtime, IP assignment, confidentiality and any non-compete need to be written for Luxembourg law. Non-competes in particular have strict conditions there.</p><p>Treating EOR as a permanent answer. If Luxembourg becomes a real hub, your own entity will usually make more sense per head over time. EOR is strongest when you are entering before you are sure.</p><h3>A short checklist before you make the offer</h3><ul><li>Who is the legal employer in Luxembourg, by name? The provider’s own entity, or a partner?</li><li>Does the draft contract include a probation clause that fits the role’s legal ceiling?</li><li>Has indexation been built into your multi-year cost model?</li><li>Where will the employee physically work each week, and has the cross-border position been checked?</li><li>What notice and severance would apply if you had to end the contract in month 13?</li></ul><p>If a provider cannot answer those five clearly, keep looking.</p><h3>Questions I get asked about Luxembourg</h3><p><strong>Can a foreign company employ someone in Luxembourg without a local entity?</strong></p><p>Yes, through an Employer of Record. The EOR’s Luxembourg entity becomes the legal employer, runs payroll and social security, and issues a contract under Luxembourg law. You direct the person’s work.</p><p><strong>Is a contractor arrangement an option instead?</strong></p><p>Sometimes, for genuinely independent professionals with their own business and several clients. For someone who works like a member of your team, the risk of the relationship being treated as employment is significant.</p><p><strong>How long does onboarding take?</strong></p><p>Once the candidate has accepted and the documents are in, the contract and registrations typically take a few weeks. The candidate’s notice period at their current job is usually the longer constraint.</p><p><strong>Will indexation really affect my budget?</strong></p><p>Yes. When the index is triggered, salaries rise automatically by law. Build at least one adjustment into any multi-year model.</p><p>We cover Luxembourg as part of our global EOR coverage. Our Luxembourg EOR page has the country specifics, including a deeper breakdown of Luxembourg employment laws.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b88d7fac67db" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The “EOR vs Staffing Agency” Confusion Can Get Expensive]]></title>
            <link>https://priyomsarkar.medium.com/the-eor-vs-staffing-agency-confusion-can-get-expensive-a0615b2231ea?source=rss-197efc53e9b2------2</link>
            <guid isPermaLink="false">https://medium.com/p/a0615b2231ea</guid>
            <category><![CDATA[employee-onboarding]]></category>
            <category><![CDATA[employer-of-record]]></category>
            <category><![CDATA[staffing-agency]]></category>
            <category><![CDATA[staffing-and-recruiting]]></category>
            <category><![CDATA[global-hiring]]></category>
            <dc:creator><![CDATA[Priyom Sarkar]]></dc:creator>
            <pubDate>Wed, 21 Oct 2026 05:31:01 GMT</pubDate>
            <atom:updated>2026-10-21T05:31:01.511Z</atom:updated>
            <content:encoded><![CDATA[<p><em>By Priyom Sarkar, Asanify AI</em></p><blockquote>Disclosure up front: I run Asanify, and we offer Employer of Record (EOR) services. This is a question our customers ask us, so I have a commercial interest in the answer. But the distinction matters regardless of which provider you choose.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qUJHiPsuDDdjWtDklFQxoA.jpeg" /></figure><p>I have seen founders compare staffing agencies and EOR providers as if they were two versions of the same service.</p><p>On the surface, the logic makes sense. Both involve a third party. Both can put a worker on someone else’s payroll. Both promise to take some administrative work off your plate.</p><p>But there is one question that can change the entire decision:</p><p><strong>Who is legally responsible for employing this person?</strong></p><p>If you get that wrong, the consequences can extend well beyond the vendor fee.</p><h3>The difference starts with what you are buying</h3><p>A staffing agency primarily helps you find people. Its value lies in sourcing candidates, matching skills to roles, and helping you fill positions.</p><p>Depending on the arrangement, the agency may also employ temporary workers or manage certain employment responsibilities. The exact allocation of responsibilities depends on the contract and local law.</p><p>An EOR solves a different problem.</p><p>Suppose you have already found the right person in India, but your company does not have an Indian legal entity. You want to hire them without spending months establishing a subsidiary and setting up local employment operations.</p><p>An EOR can become the legal employer, employ the individual through its local structure, and manage payroll, statutory obligations, and other employment administration within the agreed scope.</p><p>You manage the employee’s day-to-day work. The EOR handles the employment relationship and associated responsibilities assigned to it.</p><p>That is the fundamental distinction.</p><p>A staffing agency helps you find talent. An EOR helps you employ talent in a market where you may not have your own legal entity.</p><p>Of course, real-world arrangements can overlap. Some staffing companies offer extensive employment services, and some EOR providers offer recruitment support. The labels alone tell you very little about the legal structure.</p><p>Which is why I would never make this decision based on a sales presentation alone.</p><h3>When does the distinction actually matter?</h3><p>Usually, when something goes wrong.</p><p>Imagine you hire someone in another country through a vendor. Six months later, you need to terminate the employment relationship. The employee disputes the termination, raises questions about statutory entitlements, or challenges how their compensation was handled.</p><p>Who is responsible for addressing the issue?</p><p>Or imagine a payroll audit identifies incorrect statutory contributions. Who is accountable for the filings? Who needs to correct the error? What does your contract say about liability?</p><p>These are not questions you want to start asking after a problem appears.</p><p>If you assumed your vendor was the legal employer, but the agreement establishes a different arrangement, you may discover that your company has responsibilities you never accounted for.</p><p>The point is not that staffing agencies are inherently risky or that EOR providers eliminate every employment risk. Neither conclusion would be accurate.</p><p>The point is that <strong>the legal structure must match your expectations before you sign the contract.</strong></p><p>A smooth onboarding process does not automatically mean you have the right employment arrangement.</p><h3>Three questions I would ask before choosing a provider</h3><p>When evaluating an EOR or staffing vendor, I would start with three questions.</p><p><strong>1. Which legal entity will employ the worker?</strong></p><p>Ask for the specific legal entity and jurisdiction. If you are hiring in India, establish which entity will be the employer and how the employment relationship will be documented.</p><p>A vague assurance that the provider handles employment is not enough.</p><p><strong>2. Who is responsible for payroll and statutory compliance?</strong></p><p>Ask how payroll, statutory contributions, tax-related obligations, employment documentation, and termination processes are handled.</p><p>More importantly, clarify which responsibilities the provider assumes, which remain with your company, and how errors or disputes are addressed.</p><p><strong>3. Does the contract reflect what the sales team promised?</strong></p><p>Pay close attention to terms such as co-employment, temporary staffing, employee leasing, and employer of record.</p><p>These terms can describe different arrangements. If the sales conversation promises one thing but the contract describes another, get the discrepancy resolved in writing.</p><p>I would also ask which local entity will sign the employment agreement and what happens if the employment relationship ends.</p><p>These questions take a little time. Discovering the answers during a dispute can take considerably more.</p><h3>Can pricing tell you which service you need?</h3><p>Pricing is a useful clue, although it is not definitive.</p><p>Staffing agencies often charge a placement fee, a percentage of the candidate’s salary, or a recurring margin for temporary staffing. The commercial model depends on whether the agency is recruiting, supplying temporary workers, or providing an ongoing staffing arrangement.</p><p>EOR providers typically charge an ongoing fee per employee, often monthly, alongside employment costs and other applicable charges.</p><p>That recurring fee reflects an ongoing employment service rather than simply introducing a candidate.</p><p>But pricing alone cannot establish who the legal employer is. A vendor may bundle recruitment, payroll, and employment administration into one price.</p><p>Look at the pricing model alongside the contract, the services included, and the legal entity responsible for employment.</p><p>The better question is not simply, “Which provider is cheaper?”</p><p>It is, “Am I paying for the service my business actually needs?”</p><h3>So, which one should you choose?</h3><p>The decision becomes much easier when you start with the problem you are trying to solve.</p><p>If you need help finding candidates, a recruitment firm or staffing agency may be the right choice.</p><p>If you have already found someone in a country where your business does not have a legal entity, an EOR may be the more appropriate route.</p><p>If you need both, a provider offering recruitment and EOR services may be able to support the entire process. Just make sure the recruitment arrangement does not create ambiguity about who employs the individual and assumes the relevant legal responsibilities.</p><p>For companies hiring internationally, this distinction is particularly important. Expanding into a new country involves more than paying a salary. Local employment requirements, statutory contributions, documentation, and termination rules all need to be addressed.</p><p>The right operating model depends on where you are hiring, how you intend to manage the employee, and which responsibilities your business is prepared to retain.</p><h3>Where Asanify fits into this</h3><p>At Asanify, we help companies employ people in markets such as India without having to establish their own local entity first.</p><p>Our EOR service covers employment administration, payroll, and statutory compliance within the scope of the agreed arrangement.</p><p>We are not a recruitment agency, and finding candidates is not our core service. If your primary challenge is sourcing talent, a recruiter may be the better starting point.</p><p>If you have already found the person you want to hire and need a compliant way to employ them locally, that is where an EOR becomes relevant.</p><p>You can read our detailed comparison of the two models here:<a href="https://asanify.com/blog/employer-of-record/employer-of-record-vs-staffing-agency-key-differences-explained/"> Employer of Record vs Staffing Agency: Key Differences</a>.</p><p>If you are evaluating international hiring options, our<a href="https://asanify.com/global-employer-of-record/"> Global EOR page</a> explains how the model works and where it may fit your business.</p><p>My advice is simple: before comparing quotes, ask every provider who the legal employer will be, what responsibilities they assume, and what your company remains accountable for.</p><p>Get those answers in writing.</p><p>It is a small step that can save you from making a much more expensive decision later.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a0615b2231ea" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[EOR Pricing Decoded: What Every Line Item on That Quote Actually Buys You]]></title>
            <link>https://priyomsarkar.medium.com/eor-pricing-decoded-what-every-line-item-on-that-quote-actually-buys-you-9c18313bf7c2?source=rss-197efc53e9b2------2</link>
            <guid isPermaLink="false">https://medium.com/p/9c18313bf7c2</guid>
            <category><![CDATA[global-expansion]]></category>
            <category><![CDATA[hiring-costs]]></category>
            <category><![CDATA[employee-benefits]]></category>
            <category><![CDATA[employer-of-record]]></category>
            <category><![CDATA[global-hiring]]></category>
            <dc:creator><![CDATA[Priyom Sarkar]]></dc:creator>
            <pubDate>Mon, 19 Oct 2026 08:31:01 GMT</pubDate>
            <atom:updated>2026-10-19T08:31:01.727Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jm5ebECJTZRLqtnmOFoqQA.jpeg" /></figure><p>Most Employer of Record quotes I have seen in the last year fit on a single screen. A USD figure per employee per month. A small note about country setup. Maybe a one-time onboarding charge. The pages that produce those quotes are designed to look simple, because simplicity converts.</p><p>The simplicity hides about 8 things you are actually paying for, and another 4 things you are paying for, whether the vendor lists them or not. Founders and CFOs come to me confused about why two EORs quoting the same headline number end up costing very different amounts at year-end. This is a walkthrough of the line items, what they cover, and where the gaps usually sit.</p><p>I run an EOR that hires across 100+ countries. The numbers below are based on quotes our prospects share with us during evaluation, plus what our own pricing decomposes into. The exact rupee or dollar values vary by country and vendor; the structure does not.</p><h3>What you are buying when you pay an EOR</h3><p>An EOR fee bundles three things, in roughly this order of weight.</p><p>First, it pays for the legal entity in the country your employee sits in. Setting up and running a private limited company in India costs the EOR a multi-lakh annual amount in compliance filings, statutory audits, and director KYC. Maintaining a UAE free-zone entity is several thousand AED per year on licensing alone. Maintaining a Singapore Pte Ltd is the local accountant fee plus the annual returns. The “per employee” math you see on the brochure is the entity overhead amortized across the EOR’s book in that country.</p><p>Second, it pays for payroll execution. That is the actual processing each month, the statutory contributions, the tax withholding, the slip generation, the filings on PF, ESIC, professional tax in India, or SSS, PhilHealth, Pag-IBIG in the Philippines, or the corresponding labour and social funds wherever your hire sits.</p><p>Third, it pays for risk transfer. The EOR is the legal employer. If the worker sues for wrongful termination, files a labour claim, raises a tax dispute, or triggers a compliance audit, the EOR’s name is on the paperwork. The fee includes a portion of the EOR’s exposure to that risk pool.</p><p>If a vendor is not pricing all three things into the line item, they are either subsidizing one to win the deal or excluding it from scope. Both are worth asking about.</p><h3>The 8 components inside a typical EOR fee</h3><p>Here is what is bundled into the fee, decomposed.</p><ul><li>Entity maintenance and statutory filings. Annual returns, statutory audit, director KYC, RoC filings, in India. Trade licences and free-zone renewals in the UAE. Equivalent in every country.</li><li>Payroll processing. Calculation of net pay, statutory contributions, tax withholding, slip generation, payroll register, and employee ledger.</li><li>Statutory deposits and filings. PF, ESIC, professional tax, and TDS in India. SSS, PhilHealth, Pag-IBIG, BIR in the Philippines. Country-specific equivalents elsewhere. The filings themselves are mostly free; the work of preparing them is not.</li><li>Contracts and HR documentation. Local-law-compliant employment contract, NDAs, IP assignment, leave policy, code of conduct.</li><li>Onboarding and offboarding. UAN linking in India, statutory registrations on first hire, full-and-final settlement on exit, and gratuity calculation where applicable.</li><li>Compliance updates. Every Budget cycle, every state-level rule change, every social security wage-ceiling revision, somebody has to read the gazette and update the system. Customers do not see this work; they feel it when it does not happen.</li><li>Customer support and HR ops layer. Employee questions on payslips, tax queries, and leave queries. Most EORs absorb this as part of the fee; a few charge for HR ops separately.</li><li>Platform access. Whatever the dashboard is, however good or bad it is.</li></ul><p>If your quote does not implicitly cover all 8, ask the vendor where the gap sits.</p><h3>The 4 things you pay for, whether they are listed or not</h3><ol><li>Statutory employer contributions. The PF and ESIC contributions in India, social security in the US or EU, and end-of-service gratuity in the UAE. These are pass-through. The EOR collects them from you and pays them to the government. Nothing the EOR can negotiate. Many vendors hide them in a “fully loaded” employer cost figure, which is convenient until you want to compare two quotes line by line.</li><li>The 13th-month bonus is mandatory. The Philippines mandates 13th-month pay. Brazil mandates the 13th salary. India does not.</li><li>Termination notice or severance. In India, 30–90 days’ notice depending on cadre. In Indonesia, severance can run to 9 months of base salary at the higher end. In France, dismissal compensation rules are tight. The EOR cannot waive these even if you want to fire the person tomorrow.</li><li>FX and remittance costs. If you pay the EOR in USD or GBP and they pay the employee in local currency, somebody is taking the FX spread. In a stable currency, it is a few basis points. In a volatile one, it is real money. Ask which side absorbs the spread.</li></ol><h3>How to compare two quotes that look identical on the front page</h3><p>Three questions surface the differences fast.</p><p><strong>Question 1.</strong> What is the total landed monthly cost for a [specific role, specific city, specific gross salary] employee, including all statutory contributions, all mandatory accruals, and your fee? Ask for it as a single number, then ask for the line items.</p><p><strong>Question 2. </strong>What happens if I terminate this employee at the end of the probation period? Walk me through the cost, the timeline, and the documentation.</p><p><strong>Question 3.</strong> What is your default response time for a payroll discrepancy raised by an employee on the 7th of the month, and what is your default response time for a tax compliance query raised by my finance team on the 25th of the month?</p><p>The first question surfaces hidden bundling. The second surfaces how seriously the vendor takes local labour law. The third surfaces the operational quality of the team you will actually be working with.</p><h3><strong>Where the brochure-quote founders get hurt</strong></h3><p>Three patterns repeat.</p><p>The first is the FX spread on a foreign-currency-quoted EOR fee paid by a local-currency entity. As exchange rates fluctuate, your effective per-employee cost quietly drifts over time without clear visibility upfront.</p><p>The second is the “all-inclusive” claim that excludes statutory employment costs such as Provident Fund (PF), Employee State Insurance (ESI), statutory bonuses, and end-of-service gratuity accruals. A good EOR fee covers the calculation, filing, and remittance work, but the statutory contributions themselves are pass-through employment costs borne by you, often surfacing as unexpected balloon payments when employees exit.</p><p>The third is the support-and-platform line item, which vendors squeeze when margins compress. You signed up for white-glove HR operations but ended up waiting days for simple payslip corrections.</p><p>None of these are scams; they are operational trade-offs every vendor makes. To evaluate proper employment risk management and legal-employer responsibility, you need to know which decisions your EOR has made.</p><h3>A grounded, line-by-line view of EOR cost in India</h3><p>For founders evaluating an EOR for India specifically, the <a href="https://asanify.com/blog/employer-of-record-india/employer-of-record-india-cost/">India corridor pricing breakdown</a> lays out the full landed cost on a per-role basis, including PF, ESIC, professional tax, gratuity accrual, and the implied annual bonus expectation. We publish ours because the comparison work is faster when both sides are on the same axes.</p><p>If you are evaluating the broader question of <a href="https://asanify.com/blog/employer-of-record-india/eor-vs-payroll-providers-international-hiring/">whether an EOR is the right setup </a>at all versus an own-entity or a contractor structure, the trade-off depends on headcount, country count, and how predictable your runway is.</p><p>Pricing is the easiest thing to compare and the hardest thing to compare correctly. Decompose the fee, ask the three questions above, and the right vendor will surface inside<a href="https://calendly.com/asanify/international-catchup-30-min"> a 30-minute call.</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9c18313bf7c2" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[7 Questions to Ask Before You Pick an EOR (the Ones the Sales Deck Skips)]]></title>
            <link>https://priyomsarkar.medium.com/7-questions-to-ask-before-you-pick-an-eor-the-ones-the-sales-deck-skips-15de58b93887?source=rss-197efc53e9b2------2</link>
            <guid isPermaLink="false">https://medium.com/p/15de58b93887</guid>
            <category><![CDATA[employer-of-record]]></category>
            <category><![CDATA[global-hiring]]></category>
            <category><![CDATA[business]]></category>
            <category><![CDATA[sales-question]]></category>
            <category><![CDATA[b2b-sales]]></category>
            <dc:creator><![CDATA[Priyom Sarkar]]></dc:creator>
            <pubDate>Sat, 17 Oct 2026 05:04:31 GMT</pubDate>
            <atom:updated>2026-10-17T05:04:31.549Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DqwQavN8LNBRBDZCaaKyKw.jpeg" /></figure><p>If you are evaluating Employer of Record vendors for the first time, the demo calls all start to feel the same.</p><p>A platform tour. A coverage map. A pricing slide. A logo wall.</p><p>I have been on the other side of those calls for the last 3 years, running an EOR platform across 100+ countries. The things that actually predict whether the relationship works for the customer over 24 months almost never come up in the demo, because they are uncomfortable to ask and uncomfortable to answer.</p><p>This is the diagnosis I wish more buyers ran.</p><p>7 questions, each with what a good answer looks like and what to watch for. None of them are about price. Pricing is the easiest thing to compare and the worst thing to optimise for in this category.</p><h3>Question 1. In the country where I am hiring, do you hold your own legal entity, or do you subcontract to a partner?</h3><p>This is the single most important question, and it is almost never asked.</p><p>Most EORs are direct in 5–15 countries and partnered in the rest. The brochure shows “150+ countries” because the partner network is included. There is nothing wrong with the partner model. There is something wrong with not knowing whether you are buying it.</p><p>A good answer is direct and specific. “Yes, we own the entity in India. Here is the entity name and the Ministry of Corporate Affairs registration link.” Or, “No, we partner with a local provider in Egypt. Here is who they are, here is the partner’s track record, and here is how SLAs flow through to you.”</p><p>A poor answer is generic. “We have global coverage.” That sentence does no work for you.</p><p>If you are partnered, the failure modes are different. Payroll and visa timing have an extra hop. Employee data sometimes lives with the partner, not the EOR you signed with. Termination disputes have an extra layer. None of this is disqualifying. It is information you need.</p><h3>Question 2. Show me a sample payslip from a real (anonymized) employee in the country I am hiring in.</h3><p>EOR sales decks have stylized example payslips. The real payslips have the actual statutory line items, the actual rounding rules, the actual structure of the payroll register that your finance team will reconcile against.</p><p>A good answer is, “yes, here is one from last month, anonymized.” The payslip will show whether contributions are computed correctly, whether the structure aligns with local norms, and whether the line items match what your in-country lawyer or accountant would expect to see.</p><p>A poor answer is, “we will send you a sample after we sign.” That is a deferral pattern, and the deferral often means the live payslips have something the vendor does not want to send before signature.</p><p>For India specifically, a payslip should show basic, HRA, special allowance, PF deduction (employee), ESIC if applicable, professional tax by state, TDS. If those line items are not there, the payslip is wrong, and the payroll system that produced it is going to need correction in your first month.</p><h3>Question 3. What is the median time from contract signing to my employee receiving their first salary?</h3><p>The honest answer for time-to-first-salary is 3–6 weeks in India (faster with prior PF/UAN history), 4–6 weeks in the Philippines, 3–6 weeks in the UAE (1–2 weeks for locals), 1–3 weeks in the US, and 4–8 weeks across most EU countries.</p><p>A good answer cites the country, provides realistic ranges, and highlights core failure modes: delayed government tax or social security registrations, missing employee documentation, and missed payroll cutoff dates.</p><p>A poor answer claims “24 hours” or “1 week” — this reflects contract signing, not actual salary delivery.</p><p>This matters because paying an employee directly to bridge onboarding delays bypasses the legal EOR framework, creating severe tax and misclassification risks. Always align start dates around EOR payroll cutoffs to manage timelines safely.</p><h3>Question 4. What is your incident response process for a payroll error reported on the 7th of the month?</h3><p>Payroll errors happen. Statutory contribution rules change at quarter ends, banking systems have outages, employee bank account details get mistyped. The question is not whether errors happen. It is what the response looks like.</p><p>A good answer is structured. “Errors reported within 48 hours of payroll run trigger a same-day fix and a re-credit before the 10th. Errors reported between days 3–7 trigger a verification cycle and a corrective payment within 2 business days. Errors reported after day 7 are handled in the next payroll cycle unless the amount is large, in which case we trigger an off-cycle payment.”</p><p>A poor answer is, “we have a support team.” That is not a response process. That is the existence of a support team.</p><p>Press for the SLA. Press for the escalation path. Press for what happens if the error is the EOR’s fault versus your fault versus a government system’s fault.</p><h3>Question 5. Walk me through what termination of an employee looks like in this country, end to end, with timing and cost.</h3><p>Termination is the second most expensive thing in an EOR relationship after the salary itself. It is also where vendors differentiate the most, because handling it badly creates labour disputes that haunt the EOR’s exposure.</p><p>A good answer covers notice periods (statutory and contractual), severance computation, full-and-final settlement timing, gratuity (where applicable), unused leave encashment, and what the EOR’s role is in the documentation. The timing should be specific to the country, not a generic “30–90 days&quot;.</p><p>A poor answer is “we follow local law.” Of course they do. That is the floor. The question is what they do above the floor, particularly around documentation that protects the customer in case of a labour dispute.</p><p>For India, a good vendor will walk you through the difference between probation termination and post-probation termination, retrenchment versus dismissal, the role of the standing orders in your industry, and how the EOR documents performance issues to support a defensible exit.</p><h3>Question 6. How many of your customers are companies of my approximate size in my approximate country footprint, and can I speak to two of them?</h3><p>Coverage and scale references matter. If you are a 200-person US company hiring 8 people in India, you do not want to learn from a vendor whose entire India book is 15 employees across small companies.</p><p>A good answer is specific. “We have 12 customers of your shape; here are 2 we can connect you with this week.” If the references are willing to take the call within a week, the vendor has established that relationship in advance and treats it as a real asset.</p><p>A poor answer is, “we have many enterprise customers.” Names, please. References, please.</p><p>If the vendor has zero customers of your shape, that is information. It is not necessarily disqualifying. It is information.</p><h3>Question 7. What does your data residency and security posture look like for my country’s data protection law?</h3><p>For India, the DPDP Act is now in force. For the EU, GDPR has been in force for years. For the UAE, the federal data protection law is operational. For the Philippines, the DPA. For Singapore, the PDPA.</p><p>The EOR holds extensive personal data on your employees. Salary, ID documents, bank account, home address, and dependent information. The EOR’s compliance posture is your compliance exposure if anything goes wrong.</p><p>A good answer covers the data classification, the storage region, the access controls, the retention policy, the breach notification SLA, and the named DPO contact. Bonus points if there is a SOC 2 Type II report and an ISO 27001 certificate; they can share.</p><p>A poor answer is, “we are GDPR compliant.” Compliance is not a binary. It is a posture. Ask for the evidence.</p><h3>What good looks like overall</h3><p>If a vendor answers all 7 questions clearly, with specifics, in writing, before you sign, the working relationship over the next 24 months is going to be operationally clean. The vendors who run their business well are happy to answer these questions. The ones who run it badly find reasons not to.</p><p>The 30-minute discovery call is a poor format for these questions because the salesperson cannot answer most of them on the spot. That is fine. Send the 7 questions in advance, ask for written answers, and <a href="https://calendly.com/asanify/international-catchup-30-min?">use the discovery call to test the answers</a>.</p><p>If you are sizing an <a href="https://asanify.com/global-employer-of-record/india/">EOR for India</a> specifically, the India corridor diagnostic walks through the country-specific answers I would expect from a credible vendor. For multi-country evaluations, the global EOR overview covers the corridor-by-corridor differences.</p><p>I would rather lose a deal because we answered honestly than win one and let the customer find out later. Most of my peers in this category will tell you the same thing. Test which ones actually mean it.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=15de58b93887" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What hiring your first employee in Singapore actually involves, and where founders get it wrong]]></title>
            <link>https://priyomsarkar.medium.com/what-hiring-your-first-employee-in-singapore-actually-involves-and-where-founders-get-it-wrong-4e3e87353603?source=rss-197efc53e9b2------2</link>
            <guid isPermaLink="false">https://medium.com/p/4e3e87353603</guid>
            <category><![CDATA[remote-hiring]]></category>
            <category><![CDATA[singapore]]></category>
            <category><![CDATA[international-hiring]]></category>
            <category><![CDATA[employer-of-record]]></category>
            <category><![CDATA[global-hiring]]></category>
            <dc:creator><![CDATA[Priyom Sarkar]]></dc:creator>
            <pubDate>Mon, 05 Oct 2026 07:06:01 GMT</pubDate>
            <atom:updated>2026-10-05T07:06:01.538Z</atom:updated>
            <content:encoded><![CDATA[<p>By Priyom Sarkar, Founder &amp; CEO, Asanify</p><blockquote>Disclosure: I run Asanify, an HR and payroll platform that supports EOR hiring in Singapore, among other markets. I’m writing this because most of the “how to hire in Singapore” content I’ve read online glosses over the two numbers that actually matter, CPF and the Employment Pass salary floor, and buries them under generic “Singapore is business-friendly” filler.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uGLKs0U_d_B6H3QbBD6fOA.jpeg" /></figure><p>Singapore is usually the first Southeast Asia hire for a foreign company, and for good reason, with an English-language business environment, a stable legal system, and a hub position for the rest of APAC. But “business-friendly” doesn’t mean “no compliance to think about&quot;. It means the compliance is well-documented, which is different.</p><h3>CPF, the number that changes your unit economics</h3><p>If you’re hiring a Singapore citizen or permanent resident, Central Provident Fund contributions apply, and this is the single biggest line item foreign founders underestimate. For employees aged 55 and below, the combined CPF rate is 37% of wages, split as 20% from the employee and 17% from the employer, per the CPF Board’s published rates. The employer’s 17% is not optional, and it’s not something you negotiate around; it’s statutory.</p><p>There’s a wage ceiling too. Effective January 1, 2026, the Ordinary Wage ceiling rose from S$7,400 to S$8,000, meaning CPF applies up to that monthly figure for base wages, with a separate annual ceiling of S$102,000 covering both ordinary and additional wages like bonuses, per the CPF contribution rate guides published this year. If you’re budgeting a Singapore hire at, say, S$6,000 a month, plan for roughly S$1,020 a month in employer CPF on top of gross salary, not an afterthought.</p><p>One more thing worth knowing if you’re hiring anyone over 55: rates step down by age band, but the 2026 change specifically raises the combined rate for the 55-to-65 bracket further, with the increase channelled into the employee’s Retirement Account. If your Singapore hire is a senior operator (which, for a lot of first Singapore hires setting up a regional office, they are), this is not a rounding error.</p><h3>The levy almost nobody budgets for</h3><p>There’s a third statutory cost that gets left out of most “cost of hiring in Singapore” spreadsheets entirely: the Skills Development Levy. It’s small individually, 0.25% of monthly gross wages per employee, but it’s mandatory for every employee working in Singapore, citizens, PRs, and foreign pass holders alike, so it applies across your entire headcount with no exemptions for who you’re hiring. The levy is calculated on the first S$4,500 of monthly wages, working out to a minimum of S$2 a month for someone earning under S$800, up to a maximum of S$11.25 a month for anyone earning above S$4,500, per CPF Board’s SDL guidance. On its own it’s not going to change your hiring decision. Where it matters is that it’s one more mandatory line item that a lot of first-time-in-Singapore budgets simply don’t include, and when you’re stacking it on top of CPF at 17% employer contribution, the gap between “salary” and “actual monthly cost to the company” keeps widening in ways that surprise people who only budgeted the headline number.</p><h3>Employment Pass, the number that decides if you can even hire the person</h3><p>CPF only kicks in for citizens and PRs. If you’re hiring a foreign national to run your Singapore office, which is the more common first-hire scenario for companies expanding out of the US, UK, or India, you’re dealing with the Employment Pass instead.</p><p>The minimum qualifying salary for new EP applications and for pass renewals expiring from January 1, 2026, is S$5,600 a month in non-financial sectors, climbing progressively with age to S$10,700 a month at age 45 and above. Financial services roles sit higher, with a minimum of S$6,200, rising to S$11,800 at 45-plus, per the Ministry of Manpower’s published EP salary framework. And salary alone doesn’t get you the pass. Every application also runs through COMPASS, a points-based test weighing salary, qualifications, your company’s workforce diversity, and how much local hiring you’re doing, so a borderline salary can still fail on the COMPASS score.</p><p>Worth flagging since it changes near-term planning: the non-financial-sector minimum is set to rise again, from S$5,600 to S$6,000, for new applications from January 1, 2027 and renewals from January 1, 2028. If you’re planning a Singapore hire for next year, budget against the higher number now rather than the current one.</p><h3>Not every foreign hire needs an Employment Pass</h3><p>Worth a callout since I’ve seen this assumption cause confusion: EP is for professionals, managers, and executives, the PMET category. If you’re hiring for a role that doesn’t clear the salary threshold or doesn’t fit the PMET profile, mid-skilled technical or support roles, for example, the relevant pass is usually the S Pass instead, which has its own separate salary floor and a quota system tied to your company’s local-to-foreign headcount ratio. The quota piece specifically catches people off guard, unlike EP, S Pass approval isn’t purely a salary-and-qualifications question, it also depends on how many S Pass and Work Permit holders your company already has relative to your total headcount. If Singapore is going to be more than a one-person office for you, it’s worth understanding the quota mechanics before you’re three hires in and hit a wall on the fourth.</p><h3>What does go wrong?</h3><p>The most common mistake I’ve seen (again, based on conversations with founders going through this, not a formal count) isn’t miscalculating CPF or missing the EP threshold; both of those show up early because they’re gating requirements. It’s underestimating the total cost of employment by treating base salary as the number, when CPF alone adds up to 17% on top for local hires, and EP-sponsored roles need to clear a salary floor that’s meaningfully above what the same role might cost in a lower-cost hiring market.</p><p>The second mistake is the timeline. EP processing typically takes a few weeks, not days, and COMPASS adds a layer of uncertainty that a straightforward visa process doesn’t have. If your plan assumes a Singapore hire starts in three weeks, build in slack.</p><p>Where an EOR actually helps here</p><p>None of the above is exotic or hidden; it’s all published by the CPF Board and MOM. Where an Employer of Record earns its fee in Singapore specifically isn’t secrecy; it’s operational load. Running CPF contributions correctly every cycle, keeping pace with the annual rate and ceiling changes (which happen almost every year), and handling EP applications and renewals without your team learning MOM’s submission process from scratch. <a href="https://asanify.com/global-employer-of-record/singapore/">Asanify supports EOR hiring in Singapore</a> alongside other APAC and global corridors. A full breakdown of the Singapore hiring process, statutory obligations, and what an EOR handles versus what stays with you is on <a href="https://asanify.com/global-employer-of-record/singapore/how-to-hire/">asanify.com</a>.</p><p>If you’ve hired in Singapore and hit a compliance surprise that isn’t covered above, I’d like to hear it, this is a space where the rules genuinely do shift year to year and I’d rather this piece stay accurate than complete.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4e3e87353603" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Employer of Record India: What Happens After You Decide to Hire?]]></title>
            <link>https://priyomsarkar.medium.com/employer-of-record-india-what-happens-after-you-decide-to-hire-2baf023d0a1a?source=rss-197efc53e9b2------2</link>
            <guid isPermaLink="false">https://medium.com/p/2baf023d0a1a</guid>
            <category><![CDATA[indiaeor]]></category>
            <category><![CDATA[payroll]]></category>
            <category><![CDATA[hrtech]]></category>
            <category><![CDATA[employer-of-record]]></category>
            <category><![CDATA[global-hiring]]></category>
            <dc:creator><![CDATA[Priyom Sarkar]]></dc:creator>
            <pubDate>Wed, 30 Sep 2026 08:21:09 GMT</pubDate>
            <atom:updated>2026-09-30T08:21:09.100Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>By Priyom Sarkar, Founder &amp; CEO, Asanify</strong></p><p><em>Disclosure up front: I run Asanify, and employer-of-record services are part of what we sell. Factor that in.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*o5UPr3Q0bY6MEakUkIm1QA.jpeg" /></figure><p>I get asked about <a href="https://asanify.com/global-employer-of-record/india/"><strong>employer of record India</strong></a> arrangements in a surprisingly specific way.</p><p>Usually, the company already has the person they want to hire. The candidate has cleared the interviews. Compensation is agreed. Everyone is ready to move.</p><p>Then someone asks, <em>“Okay, but who employs them?”</em></p><p>That’s where the confusion starts.</p><p>The simple answer is this: an EOR in India becomes the employee’s legal and statutory employer, while your company continues to control the person’s actual work, priorities, reporting and performance.</p><p>But that sentence leaves out the part buyers actually need to understand.</p><ul><li>What does the EOR do when the offer is accepted?</li><li>Who signs what?</li><li>Where does the salary money go?</li><li>Who handles TDS and statutory filings?</li><li>And what happens when the employee eventually leaves?</li></ul><p>So let’s walk through the actual process.</p><h3>Who Is the Employer Here?</h3><p>Let’s separate two things that people tend to mix together: <strong>legal employment</strong> and <strong>day-to-day management</strong>.</p><p>With an EOR, the EOR is the legal employer of the employee in India. The EOR enters into the local employment relationship, runs payroll and handles the applicable statutory employment obligations.</p><p>Your company remains the organisation managing the person.</p><p>You decide:</p><ul><li>What role they have</li><li>What work they do</li><li>Who they report to</li><li>How their performance is evaluated</li><li>What compensation do you want to offer</li><li>Whether they receive a promotion or salary increase</li></ul><p>The EOR manages the employment infrastructure around that relationship.</p><p>Think of it as outsourcing the <strong>legal and payroll layer of employment</strong>, not the employee themselves.</p><p>That’s the first distinction I’d want any first-time EOR buyer to understand.</p><h3>What Happens During EOR Onboarding?</h3><p>This is another area where EOR explanations tend to become vague.</p><p>“We handle onboarding” sounds reassuring. It also doesn’t tell you much.</p><p>There is actual paperwork involved.</p><p>Once you’ve selected the candidate and agreed on the commercial terms, the EOR collects the information needed to create the employee’s Indian employment record.</p><p>That can include KYC and identity documents, bank details, tax information and other employment documentation.</p><p>The EOR then prepares the applicable employment documentation, including the employment contract and offer-related paperwork.</p><p>The employee reviews and signs the documents.</p><p>That’s when the formal employment relationship is created through the EOR.</p><p>There can be some back-and-forth here. Documents need to be checked, compensation needs to be structured correctly, and the employment terms need to align with applicable requirements.</p><p>That’s normal.</p><p>What shouldn’t be normal is discovering after the employee joins that nobody is clear about who is actually employing them.</p><h3>How Does an Employer of Record Work When Payroll Runs?</h3><p>This is probably the part buyers should understand before anything else.</p><p>Let’s say you have an employee in Bengaluru.</p><p>It’s the end of the month.</p><p>You don’t directly calculate their net salary and transfer it to their personal bank account. The EOR runs that payroll process.</p><p>The flow is roughly:</p><p><strong>You fund the EOR → EOR processes payroll → applicable deductions and statutory obligations are handled → the employee receives the net salary.</strong></p><p>You receive an invoice from the EOR based on the agreed commercial structure and fund it.</p><p>The EOR then calculates payroll, applies the applicable deductions, withholds salary TDS where required, processes statutory obligations and pays the employee.</p><p>The employee receives their net salary.</p><p>This distinction matters because <strong>the EOR invoice is not simply the employee’s salary</strong>.</p><p>It can include salary, employer-side statutory costs, benefits or other agreed employment costs, plus the EOR’s service fee.</p><p>If you’re comparing providers, ask for an itemised breakdown.</p><p>I would.</p><p>It makes the economics much easier to understand.</p><h3>What Statutory Contributions Does the EOR Handle?</h3><p>“Compliance handled” is one of those phrases that sounds useful until you ask what it actually means.</p><p>In an India EOR arrangement, the applicable statutory layer can include obligations around:</p><ul><li>Employees’ Provident Fund (EPF)</li><li>Employees’ State Insurance (ESI), where applicable</li><li>Professional tax</li><li>Labour welfare fund obligations</li><li>Salary TDS</li><li>Statutory payroll filings and records</li></ul><p>The exact obligations depend on the employee, compensation structure, establishment and applicable state and central rules.</p><p>I’m deliberately not putting a fixed EPF or ESI percentage and wage threshold into this article. These rules and thresholds can change, and EPFO’s current employer portal is already flagging a revision to the EPF wage ceiling.</p><p>The useful question for an EOR isn’t “Do you handle compliance?”</p><p>Ask:</p><p><strong>“Which filings do you make, which contributions do you remit, and can I see the records?”</strong></p><p>The answer should be specific.</p><h3>What Happens When the Employment Ends?</h3><p>This is the part of EOR that gets surprisingly little attention.</p><p>Everyone talks about hiring.</p><p>Eventually, someone leaves.</p><p>Maybe they resign. Maybe the company eliminates the role. Maybe the employment relationship reaches its end.</p><p>Whatever the reason, the EOR has to manage the employment exit properly.</p><p>That can involve:</p><ul><li>Notice-period handling</li><li>Salary through the final working date</li><li>Leave balance calculations</li><li>Reimbursements and outstanding amounts</li><li>Gratuity, where applicable</li><li>Final settlement</li><li>Employment and tax documentation</li><li>Payroll closure</li></ul><p>The exact mechanics depend on the employee’s circumstances and the applicable employment terms and laws.</p><p>This is why I wouldn’t evaluate an EOR only by asking, “How quickly can you onboard someone?”</p><p>Ask how they handle <strong>offboarding</strong> too.</p><p>A provider can make hiring feel incredibly easy and still have a messy exit process.</p><h3>What an EOR Doesn’t Do?</h3><p>This is worth stating because the opposite assumption creates unnecessary confusion.</p><p>An EOR doesn’t decide who you hire.</p><p>It doesn’t create your hiring strategy.</p><p>It doesn’t run your team’s weekly one-on-ones.</p><p>It doesn’t set your product roadmap.</p><p>And it shouldn’t be deciding whether an employee gets promoted.</p><p><strong>Those remain your responsibilities.</strong></p><p>The <em>EOR’s job</em> is to provide the compliant employment infrastructure around the person you’ve decided to hire.</p><p>While you’re managing the <strong>work, </strong>the EOR manages the <strong>employment administration and statutory layer</strong>.</p><h3>The Question I’d Ask Before Signing With an EOR?</h3><p>If you’re evaluating an <strong>EOR India</strong> provider for the first time, I wouldn’t start with the monthly fee.</p><p>I’d ask them to walk you through one employee from beginning to end.</p><p><strong>Candidate selected → offer issued → employment contract signed → employee onboarded → payroll processed → statutory obligations handled → salary paid → employee exits → final settlement completed.</strong></p><p>Then ask:</p><p><em>“Which parts of that workflow are actually yours, and which parts are mine?”</em></p><p>That conversation will tell you far more than a pricing page.</p><p>It will also expose whether the provider actually operates the employment infrastructure or whether you’re going to be passed between multiple parties whenever something unusual happens.</p><p>At <strong>Asanify</strong>, this is how we think about <a href="https://asanify.com/global-employer-of-record/india/">EOR</a>.</p><p>The value isn’t simply that a foreign company can say, “We have an employee in India.”</p><p>The value is that the company can hire that person without having to build an entire local employment and payroll operation around the first hire.</p><p>If you’re evaluating your first India hire, here’s<a href="https://asanify.com/blog/payroll/detailed-guide-employer-of-record-eor-india/"> our detailed guide to how EOR works in India</a> for the broader hiring, payroll and compliance context.</p><p>The practical question isn’t really <em>“What is an EOR?”</em></p><p>By the time you’re reading this, you probably know.</p><p>The better question is:</p><p><strong>“Show me exactly what happens to my employee, my money and my compliance obligations from the day they sign the offer to the day they leave.”</strong></p><p>A good EOR should be able to answer that without making it complicated.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2baf023d0a1a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The EPF Wage Ceiling Has Changed. The Bigger Change Is What It Demands From Payroll Technology.]]></title>
            <link>https://priyomsarkar.medium.com/the-epf-wage-ceiling-has-changed-the-bigger-change-is-what-it-demands-from-payroll-technology-ef5bc5e8004f?source=rss-197efc53e9b2------2</link>
            <guid isPermaLink="false">https://medium.com/p/ef5bc5e8004f</guid>
            <category><![CDATA[epfo]]></category>
            <category><![CDATA[compliance]]></category>
            <category><![CDATA[india]]></category>
            <category><![CDATA[statutory-compliance]]></category>
            <category><![CDATA[minimum-wage]]></category>
            <dc:creator><![CDATA[Priyom Sarkar]]></dc:creator>
            <pubDate>Mon, 28 Sep 2026 12:44:38 GMT</pubDate>
            <atom:updated>2026-09-28T12:44:38.128Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*z_v01lekE1m6ekX81PFdvQ.png" /></figure><p>There is a tendency to look at payroll regulations as a series of numbers.</p><p>A wage ceiling moves from ₹15,000 to ₹25,000. A contribution rate changes. A new notification comes in. Payroll teams update a formula, run the numbers and move on.</p><p>But after spending years building HR and payroll technology, I have come to see these changes differently.</p><p>A regulatory change is rarely just a change in a number. <strong>It is a test of how well the entire payroll system can adapt.</strong></p><p>The recent <strong>revision to India’s EPF wage ceiling</strong> is a good example.</p><p>On <strong>17 September 2026</strong>, the <strong>Ministry of Labour and Employment</strong> issued Gazette Notification <a href="https://cdnbbsr.s3waas.gov.in/s36547884cea64550284728eb26b0947ef/uploads/2026/09/202609241085718651.pdf"><strong>S.O. 5109(E)</strong></a>, revising the statutory EPF wage ceiling from ₹15,000 to <strong>₹25,000 per month</strong>. The change is effective from the date of publication of the notification.</p><p>On the surface, that sounds straightforward.</p><p>For payroll teams, it isn’t.</p><h3>The real challenge starts after the notification</h3><p>Once a regulatory notification is published, HR teams have to translate it into operational decisions.</p><ul><li>Which employees are affected?</li><li>What are their applicable PF wages?</li><li>Who was previously outside the mandatory coverage threshold?</li><li>How should their contributions change?</li><li>What happens to employer costs?</li><li>Does their CTC need to be reviewed?</li><li>Will their take-home salary change?</li></ul><p>And then there is statutory reporting.</p><p>The payroll calculation has to eventually flow into the relevant records and filings without creating inconsistencies.</p><p>This is where I think the conversation around payroll technology needs to change.</p><p><strong>Compliance should not be something HR teams manually reconstruct every time a regulation changes.</strong></p><p>The system should be capable of understanding the change and applying it to the right employees and the right payroll period.</p><h3>The ₹15,000 to ₹25,000 change isn’t about gross salary</h3><p>One detail in this update is particularly important.</p><p>When we talk about the revised ₹25,000 ceiling, we need to talk about <strong>PF wages</strong>, not simply gross salary.</p><p>An employee’s gross salary may be significantly higher than ₹25,000. That alone does not tell us how the EPF wage ceiling applies to them.</p><p>Payroll teams need to look at the applicable PF wage components and the employee’s existing PF status.</p><p>This matters because the revised ceiling brings a new group of employees into the review process, particularly those whose PF wages fall between the old ₹15,000 ceiling and the new ₹25,000 ceiling.</p><p>For a payroll system, that means identifying the right employees is just as important as calculating the right contribution.</p><h3>September is a particularly interesting payroll month</h3><p>There is another layer to this particular change that makes it a useful example of why payroll software needs to be more adaptive.</p><p>The new ceiling did not become effective on 1 September.</p><p>It became effective on <strong>17 September 2026</strong>.</p><p>That makes September a transition month.</p><p>Payroll teams need to account for the period from <strong>1–16 September under the earlier ₹15,000 ceiling</strong> and the period from <strong>17–30 September under the revised ₹25,000 ceiling</strong>, with the applicable calculations handled for each period.</p><p>This is not simply a matter of changing ₹15,000 to ₹25,000 in a payroll configuration.</p><p>The system needs to understand <strong>when the rule changed</strong> and apply the appropriate treatment to the appropriate period.</p><p>That distinction is easy to overlook when payroll is managed manually.</p><p>It becomes much more important when you’re processing hundreds or thousands of employees.</p><h3>This is where payroll automation earns its place</h3><p>I often hear automation described in terms of saving time.</p><p>That’s certainly part of it.</p><p>But I think the bigger value of payroll automation is <strong>consistency when complexity increases</strong>.</p><p>When nothing changes, almost any payroll process can appear to work.</p><p>The real test comes when a regulation changes midway through a payroll cycle.</p><p>A good payroll system should be able to take a regulatory change and connect it to the employee data, payroll configuration and statutory workflow that it affects.</p><p>The HR team shouldn’t have to start with a spreadsheet and ask, “Which employees do I need to check?”</p><p>The system should help answer that question.</p><h3>A higher ceiling can have a wider payroll impact</h3><p>The revised EPF ceiling also has consequences beyond the PF contribution itself.</p><p>For an employee whose applicable PF wages are ₹25,000, a 12% employee contribution would amount to ₹3,000 for a full month, compared with ₹1,800 when the ₹15,000 ceiling applied.</p><p>That can affect the employee’s take-home pay.</p><p>On the employer side, the applicable contribution and allocation toward EPF, EPS and related statutory components can affect employment costs and, depending on the company’s salary structure, the overall CTC structure.</p><p>So what looks like one regulatory number can eventually touch several parts of the employee lifecycle.</p><p><strong>Payroll → CTC → Employee deductions → Take-home pay → Statutory records → Compliance</strong></p><p>That’s why regulatory updates need to be treated as system changes, not isolated payroll changes.</p><h3>What this tells us about the future of HR technology</h3><p>This is probably the part of the EPF update that interests me the most as a founder.</p><p>India’s employment and payroll environment is becoming increasingly dynamic. Regulatory frameworks evolve, businesses hire across states, salary structures become more complex and companies expect HR teams to do more with fewer manual processes.</p><p>In that environment, an HRMS cannot simply be a digital version of a spreadsheet.</p><p>It needs to be an operating system for HR.</p><p>That means employee information, payroll, attendance, compliance and statutory calculations need to work together. When one part changes, the relevant downstream processes should be able to respond.</p><p>The technology should absorb complexity rather than pass it on to HR.</p><h3>Compliance should be built into the product</h3><p>At Asanify, this is one of the principles behind how we think about payroll.</p><p>We don’t want HR teams to spend their time interpreting every regulatory update and manually translating it into payroll logic.</p><p>Our job as an HR technology company is to make that process easier.</p><p>The <strong>EPF wage ceiling revision from ₹15,000 to ₹25,000</strong> is one example. Tomorrow, there will be another notification, another threshold or another statutory requirement that needs to be incorporated.</p><p>That’s the reality of running payroll in India.</p><p>The question for HR technology isn’t whether regulations will change.</p><p><strong>They will.</strong></p><p>The real question is whether your payroll system can keep up.</p><p>And, in my view, that is one of the most important measures of good payroll technology.</p><p>Not just whether it can process payroll when everything is predictable.</p><p>But whether it can remain accurate, compliant and operational when the rules change.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ef5bc5e8004f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[I get asked, “EOR or PEO?” Almost Every Week. Here’s the Answer.]]></title>
            <link>https://priyomsarkar.medium.com/i-get-asked-eor-or-peo-almost-every-week-heres-the-answer-2d6dc6c667c1?source=rss-197efc53e9b2------2</link>
            <guid isPermaLink="false">https://medium.com/p/2d6dc6c667c1</guid>
            <category><![CDATA[hiring-partner]]></category>
            <category><![CDATA[peo]]></category>
            <category><![CDATA[global-hiring]]></category>
            <category><![CDATA[hiring]]></category>
            <category><![CDATA[employer-of-record]]></category>
            <dc:creator><![CDATA[Priyom Sarkar]]></dc:creator>
            <pubDate>Wed, 23 Sep 2026 09:50:59 GMT</pubDate>
            <atom:updated>2026-09-23T09:50:59.244Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2WpSUYFYEvhdeadE1mStbA.png" /></figure><blockquote>By Priyom Sarkar, Founder &amp; CEO, Asanify</blockquote><blockquote>Disclosure: I run an EOR company, Asanify, and not a PEO. So take the framing below with that in mind, though I’ve genuinely tried to keep it fair, because a wrong answer here wastes a founder’s quarter, not just their money.</blockquote><p>The question usually shows up the same way. A founder has a US entity, is hiring fast, and someone on their team said “we should get a PEO,&quot; and someone else said, “no, we need an EOR,” and now there’s a Slack thread with four opinions and zero decisions.</p><p>So, quick version first, then the reasoning, because the quick version is genuinely useful and I don’t want to bury it under three paragraphs of context.</p><h3>The quick version</h3><p>PEO assumes you already have a legal entity in the country you’re hiring in, and it co-employs your workers alongside you, mostly to simplify HR admin, benefits, and payroll within that entity. EOR means you don’t have an entity there, and the EOR becomes the actual legal employer on paper so you can hire without setting one up.</p><p>That’s it. That’s genuinely most of the decision.</p><h3>Where people get stuck anyway</h3><p>The confusion isn’t really about definitions; most founders can repeat the definition back to me correctly within thirty seconds of hearing it. It’s about applying it to their specific, messy, half-formed hiring plan.</p><p>Common one: “we have a US entity, but we’re hiring someone in Portugal.” A traditional PEO requires a local entity, so EOR or local incorporation would be needed. You need EOR for Portugal. Unless you’re planning to incorporate there yourself, which, unless you have a real reason to, I’d generally advise against for one hire.</p><p>Another one, and this one’s a bit more of a judgment call: “we’re testing a new country; it might scale there, it might not.” This is squarely EOR territory too, precisely because the whole point of EOR is not committing capital and legal overhead to a market you haven’t validated yet. I’ve watched founders regret setting up an entity six months before deciding the market wasn’t working. That’s an expensive way to learn a market doesn’t want you.</p><p>And then there’s the case that actually causes the confusion in the first place: a company using PEO domestically, deciding to expand internationally, and someone assuming their PEO relationship “just extends.” It doesn’t, not automatically. Most PEOs are geography-locked to where you have your entity. Ask directly before you assume anything.</p><h3>When PEO genuinely is the better call</h3><p>I want to say this clearly because I think comparison content from vendors tends to undersell the other option, and that’s a trust problem, not just an accuracy one. If you already have a US entity, are hiring only domestically, and want help with benefits administration, payroll processing, and HR compliance at scale without international complexity. A PEO can often be the more appropriate and cost-effective option. Co-employment gives you access to broader benefits options or pooled benefits administration. That’s a real advantage EOR doesn’t replicate, because EOR isn’t solving that problem; it’s solving a different one.</p><p>Don’t let anyone, including me, talk you out of PEO if that’s genuinely your situation.</p><h3>What this costs to get wrong</h3><p>I want to make this concrete instead of abstract, because “wrong tool for the job” sounds low-stakes until you’ve lived it. I know of a company, I won’t name it, that signed with a PEO, assuming it would cover an upcoming hire in Germany. It didn’t. A PEO does not automatically provide legal-employer infrastructure in countries where you don’t have an entity. By the time this surfaced, they’d already made a verbal offer to the candidate. They ended up scrambling to set up an EOR relationship in under two weeks, paying a rush fee, and nearly losing the candidate to a competing offer during the delay. The mistake wasn’t malicious or even careless; exactly, it was just an assumption nobody checked out loud.</p><p>Cost is another area where the comparison can be misleading. <a href="https://asanify.com/blog/employer-of-record/peo-vs-eor/">PEO and EOR services</a> are both often priced per employee per month, but the fee covers very different things. PEOs typically spread HR, payroll, and benefits administration costs across multiple clients, which can make the per-employee price look lower. An EOR, however, becomes the legal employer and takes responsibility for employment contracts, statutory requirements, payroll, and local compliance. So, comparing the two prices directly can be misleading, especially when entering a market where you have no local infrastructure. The important question is not just what each service costs, but what responsibilities and services are included in that cost.</p><h3>The axis that decides it</h3><p>Forget the acronyms for a second. Ask one question: do you have a legal entity in the country where this specific person will work?</p><p>Yes, and you want help managing employment there. PEO.</p><p>No entity there, and you need to hire anyway. EOR.</p><p>Everything else is detail layered on top of that one fork.</p><h3>A caveat I should be honest about</h3><p>Some companies genuinely need both, PEO domestically and EOR for a handful of international hires, run in parallel. That’s not an edge case anymore; it’s increasingly the default shape for companies scaling past their home market. If that’s you, the two decisions are separate; don’t try to force one vendor to be both unless you’ve specifically confirmed they do both well. Some claim to. Fewer actually execute both well.</p><h3>Where I’d point you next</h3><p>We wrote a <a href="https://asanify.com/blog/employer-of-record/peo-vs-eor/">fuller comparison</a>, with a table uploaded on Asanify.com. The entity-ownership framing above is the part I’d want you to walk away with regardless of who you choose.</p><p>And if you’re specifically in the “no entity, need to hire internationally” bucket, <a href="https://asanify.com/global-employer-of-record/">here’s</a> country by country, including where we do and don’t have coverage yet. I’d rather tell you upfront than have you find out mid-onboarding.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2d6dc6c667c1" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Three Months on One Research Report: What Building the State of India EOR 2026 Taught Me]]></title>
            <link>https://priyomsarkar.medium.com/three-months-on-one-research-report-what-building-the-state-of-india-eor-2026-taught-me-d07f051cfac5?source=rss-197efc53e9b2------2</link>
            <guid isPermaLink="false">https://medium.com/p/d07f051cfac5</guid>
            <category><![CDATA[hiring-marketplace]]></category>
            <category><![CDATA[market-research-reports]]></category>
            <category><![CDATA[hiring-in-india]]></category>
            <category><![CDATA[research]]></category>
            <dc:creator><![CDATA[Priyom Sarkar]]></dc:creator>
            <pubDate>Tue, 15 Sep 2026 11:51:41 GMT</pubDate>
            <atom:updated>2026-09-15T11:51:41.717Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_uyyqndIupJBVRR9B-qFKg.png" /></figure><p>We launched the State of India EOR 2026 report in May. It is the biggest piece of long-form research my team has shipped. Three months of work, 15+ data sources, and seven findings that I think will shape how founders and CFOs think about India hiring for the next 18 months.</p><p>I want to share what we learned, not the findings themselves, but the process of building it and what surprised me about the market while we were inside the dataset.</p><h3>Why we did this in the first place</h3><p>For two years, the most common question on our intro calls has been some variant of “Is it still a good time to hire in India?&quot; The question is sensible. Indian engineering salaries have moved. The rupee has moved. The competitive landscape for India EOR has gotten more crowded. The new Labour Codes have created uncertainty.</p><p>We had answered the question a thousand times in private conversations. We had never answered it in public with data. Every time someone asked it, we were assembling a fresh response from memory and partial benchmarks. That is a sign that the right artifact is missing.</p><p>I also wanted us to test our own beliefs. When you run an EOR business, you develop strong intuitions about the market that you do not always verify. Writing a public research report forces you to verify. If a number we have been quoting internally for a year turns out to be wrong, the report would surface it and we would correct ourselves on the way out.</p><h3>The three things that surprised me</h3><p>I expected the research to confirm what we already knew. It did, mostly. But three findings genuinely changed my mental model.</p><p>The first surprise was the gap between US search demand and India delivery capacity. The number of US companies actively searching for India EOR is growing faster than the number of credible India EOR providers is scaling. This is a market in which the demand side is moving from early-adopter to early-majority while the supply side still operates like a specialist niche. That gap creates the conditions for the next 12–18 months to look very different from the last 12.</p><p>The second surprise was how much of the cost equation is now compliance-priced rather than salary-priced. The headline salary saving against US engineering hires is well-known. The thing that was less obvious to me before we ran the numbers is how much of the all-in cost of an India hire sits in the statutory layer, the gratuity accrual, the mandatory bonus expectations, the social security contributions. The salary is the visible part of the iceberg. The full landed cost is where the actual evaluation happens, and it is the part most quick benchmarks miss.</p><p>The third surprise was buyer behaviour. We had assumed the typical India EOR buyer was a US-based engineering leader. The data showed something subtler. The buyer was increasingly a CFO or a Head of People making a decision under risk pressure rather than under cost pressure. The shift from cost-first to compliance-first conversations that we have felt in our own pipeline shows up in the broader dataset, and it shows up consistently across company sizes.</p><p>If you have been hiring in India over the last 18 months, you have probably felt one or more of these shifts without naming them. Putting them on paper made them real for us.</p><h3>What was hard about building it?</h3><p>Three things were harder than we expected.</p><p>The first was source quality. India&#39;s hiring data is a fragmented landscape. Salary benchmarks from one source, headcount data from another, regulatory updates from a third, and market sizing from a fourth. We rejected at least 40% of the data we initially pulled because the methodology did not hold up to scrutiny. Building a piece of research that you want defenders of your numbers to back-check requires more rejection than acceptance.</p><p>The second was the editorial discipline. The temptation, when you have 80 charts and 7 findings, is to publish everything. The discipline is to publish only the findings that change a decision. The first draft of our report had 14 findings. We cut it to seven. The cut findings were not wrong; they just did not change what a reader would do on Monday morning.</p><p>The third was the framing. The early drafts of the report were neutral and survey-like, in the style of large consulting reports. They were boring. Worse, they were forgettable. We rewrote the report with a point of view, with specific recommendations on when <a href="https://asanify.com/global-employer-of-record/india/">India EOR</a> is the right structure and when it is not. A research report that does not take a position is a brochure with footnotes.</p><h3>What I changed my mind about</h3><p>Two specific things.</p><p>I used to believe that the right pitch to a US founder hiring in India was the cost saving. I no longer believe that is the right opening. The cost saving is real and substantial, but it is the second thing the buyer wants to know in 2026, not the first. The first thing they want to know is whether you will be the named employer who shows up if a labour authority sends a notice. Cost is the close. Trust is the open.</p><p>I also used to believe that India EOR was a self-evident category that did not need much explanation. The research told me otherwise. Even sophisticated buyers conflate EOR with PEO, with contractor management platforms, and with offshore development centers. Each of these structures has different liability characteristics and different cost shapes. We will be doing more category-defining work in the next 12 months, not less.</p><h3>What I want to do next</h3><p>Two things, in order.</p><p>The first is to build out the underlying datasets so that next year’s report can be quarterly rather than annual. The research methodology we built is reusable. The data refresh is the hard part. If we get the data pipeline right, the State of India EOR 2027 report becomes a much smaller lift, and the early-warning value goes up.</p><p>The second is to do the corresponding research for the next two corridors that I think will follow India’s path: the Philippines and Indonesia. Both have a similar demographic dividend, a similar English-language engineering talent pool, and a more confusing regulatory landscape that makes EOR more valuable, not less. If the State of India EOR 2026 is useful, the State of Philippines EOR 2027 should be doubly so.</p><h3>How to read the report</h3><p>If you are running an engineering team in India, the cost and Labour Codes sections will probably tell you things you already know in more rigorous form. The buyer behavior section will probably tell you things you suspect but have not seen confirmed in data.</p><p>If you are considering hiring in India for the first time, read the Labour Codes section before the cost section. It will save you a quarter of bad assumptions.</p><p>If you are evaluating EOR vendors specifically, read the compliance section against your shortlist. Most vendor pitches answer two of the three questions in that section. The vendor that answers all three is usually the one to start with.</p><p>We gated the report behind an email capture because we wanted to know who is reading it and what role they sit in. That information feeds back into the next round of research. If you are thinking about hiring in India and want a 30-minute conversation about your specific shape, the calendar is open at <a href="https://calendly.com/asanify/international-catchup-30-min/?from=eor-blog&amp;utm_source=eor-blog&amp;month=2026-09&amp;utm_medium=website&amp;utm_campaign=blog&amp;utm_content=%2Fblog%2Femployer-of-record%2Fbest-employer-of-record-providers-2026%2F&amp;utm_term=blog&amp;a5=https%3A%2F%2Fasanify.com%2Fblog%2Femployer-of-record%2Fbest-employer-of-record-providers-2026%2F&amp;asfy_rw=1&amp;_gl=1%2At6klis%2A_gcl_au%2AODUxNjA1MzI0LjE3ODkzNjE0MzY.%2A_ga%2ANDQwMTIzODA2LjE3ODkyMTIzMDE.%2A_ga_XPG016Y00R%2AczE3ODk0NjA1NTYkbzUkZzEkdDE3ODk0NjEyNzkkajU4JGwwJGgw">calendly.com/asanify</a>, and if you would rather just download the report first, the research page is<a href="https://asanify.com/research/state-of-india-eor-2026/"> here</a>.</p><h3>A note on the team</h3><p>Research reports of this depth are not solo founder projects. Five people on our team spent serious hours on this, including a research lead who spent her nights triple-checking statutory contribution rates, a designer who turned ugly Sankey diagrams into legible charts, and a content lead who held the editorial line when I wanted to add more findings. The report is theirs, more than mine.</p><p>If you read it and find something we got wrong, I genuinely want to know. We will fix it in the next version. The research is most valuable when the people who use it tell us how to make it more accurate.</p><p>Building a public research artifact is a slow way to move a market. It is also one of the few ways that lets you tell the truth, in detail, with sources. I think the India EOR conversation deserves that level of rigor in 2026. We will keep producing more of it.</p><p>— -</p><p>If you want a conversation about hiring in India specifically, the calendar is here. If you prefer to read the data first, the <a href="https://asanify.com/research/state-of-india-eor-2026/?utm_source=linkedin&amp;utm_medium=article&amp;utm_campaign=parasite_india_eor_research_journey_202605&amp;utm_content=inline_cta_2">report download is here</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d07f051cfac5" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>