What to check in India
For contributors receiving service-export income in India, confirm the receiving bank’s documentation and purpose-code requirements before your first batch. Keep the agreement, invoice or earnings statement, and payment reference connected. The Income Tax Department distinguishes return forms for people with business or professional income; the right form depends on the person’s circumstances.
An India launch should distinguish your ability to engage an individual from that person’s own tax and registration obligations. Do not describe a foreign payer or per-task calculation as a tax exemption.
Check the relationship before choosing task pay
Indian Supreme Court decisions consider the substance of the relationship, including control and integration into the business. For an annotation program, document who decides how the work is done and how the role fits into ongoing operations; a per-task rate does not answer those questions.
Define the role you are recruiting in India: occasional labeling, regular quality review, or specialist work such as writing evaluation tasks. Document whether contributors choose tasks, whether you require fixed schedules, and how ongoing supervision works. Ask for a country-specific classification assessment of those facts.
Per-task compensation does not by itself establish contractor status. Agree acceptance criteria, rework, dispute handling, and bonus eligibility in writing. If your operating model changes, revisit the engagement rather than assuming the original agreement still fits.
Tax registration and reporting
India’s Income Tax Department identifies ITR-3 for individuals with business or professional income and ITR-4 for eligible presumptive-tax cases. Determine the applicable form from the individual’s actual status and income; do not assign one form to everyone in an annotation network.
Choose a route the contributor can actually receive
Start with the receiving account and the agreed currency. INR is the domestic currency to consider, but the available settlement currency and route depend on the bank, contributor, provider, and applicable rules. Confirm those details before promising a payment method.
The options below are a comparison checklist, not a confirmed Toku country-coverage matrix. Agree the available route, recipient eligibility, fees, and settlement currency in your program setup.
| Method | What to verify |
|---|---|
| Bank transfer | Beneficiary match, currency, fees, bank details, and required payment references |
| Card payout | Provider and recipient eligibility; do not assume every card can receive funds |
| Stablecoin, where permitted | Local payment rules, supported asset and network, recipient eligibility, and conversion needs |
Define the unit you will pay for
“One annotation” can mean a simple label, a multi-step review, or a submission that needs correction. Put the unit, rate, acceptance criteria, and rework policy in the task specification. Version that specification so a payment can be reproduced after the project changes.
For illustration, 120 accepted tasks at $0.50 each produce $60 before any separately agreed bonus. That is an arithmetic example, not a market rate or a recommended compensation level. Record the currency and conversion basis as clearly as the task count.
General information for teams planning contributor programs. Classification, tax, payment eligibility, and data obligations depend on the actual arrangement and applicable local requirements.