A Jaipur restaurant purchasing deliveries and a company operating a delivery marketplace do not necessarily have the same role. Yet calling the restaurant a customer is not enough to settle its position. The Rajasthan legislation uses a broad aggregator definition, including entities coordinating with aggregators to provide services. Classification needs the actual operating arrangement, not only the heading on an invoice.
The first task is therefore to describe what your business does. The second is to identify the instruments that make the relevant Rajasthan obligations operative. A third, separate task is to check central social-security requirements and any sector regulation. Combining these questions into a single “gig registration” checkbox creates avoidable errors.
This article provides an applicability method. It does not state that a particular Rajasthan welfare-fee rate or payment deadline has been established merely because the 2023 Act exists. As at 18 October 2026, a business preparing an actual remittance should obtain the applicable commencement, rate and collection instruments rather than infer them from a registration page.
Draw the service relationship before classifying it
Start with one real order from acceptance to settlement. Identify the customer, merchant, technology provider, delivery enterprise and individual performing the work. Record which entity contracts with each participant and which system allocates the task. Then trace the money, including refunds, incentives, deductions and commissions.
A payment gateway may process money without deciding who performs the delivery. A merchant may simply purchase a completed delivery service. Conversely, an enterprise describing itself as a merchant might also onboard riders, allocate work across multiple platforms or coordinate service provision. Those additional functions change the analysis.
Use a short factual table:
| Question | Evidence to collect | Why it matters |
|---|---|---|
| Who connects customers and service providers? | Application screens and agreements | Identifies intermediary functions |
| Who recruits or onboards workers? | Onboarding records and identity checks | Shows the working relationship |
| Who allocates or rejects tasks? | Dispatch logs and operating manuals | Reveals operational control |
| Who determines payment? | Rate cards and settlement statements | Explains earnings and deductions |
| Who coordinates several platforms? | Integration contracts and service schedules | Tests the extended aggregator definition |
| Where is the service performed? | Order locations and delivery logs | Establishes the Rajasthan connection |
Do not collect a worker’s entire personal file merely to answer these questions. Begin with contractual and operational records; obtain personal information only where the registration or other lawful process requires it.
The Rajasthan definition extends beyond the application owner
The Rajasthan Platform Based Gig Workers (Registration and Welfare) Act, 2023 covers an aggregator operating in the State and relevant platform-based work. Its aggregator concept includes both digital intermediation and certain coordination with aggregators. The platform and gig-worker definitions must also be considered together.
That makes two shortcuts unreliable. First, a company cannot assume it is outside the framework because another enterprise owns the application. Second, buying an application subscription does not automatically turn every subscriber into an aggregator. The legal question is what the subscriber actually undertakes through the arrangement.
Prepare an entity-specific note. A corporate group may contain a technology company, a merchant company and a logistics company. Explain each entity’s functions rather than treating the group brand as the legal person. If an agreement assigns a coordination role to one entity while another performs it in practice, record the discrepancy and correct the contract or classification as appropriate.
Employee classification remains a separate issue. Describing someone as a gig worker does not resolve whether the facts create an employment relationship under another applicable law. A welfare-registration exercise should not become a device for changing existing employment rights.
Enactment, commencement and operational directions are different
The Act requires a separately appointed commencement date. Its legislative design includes aggregator and worker registration, a welfare fund, transaction monitoring and grievance arrangements. Several operational matters depend on additional instruments.
For an actual compliance decision, maintain an instrument register with four columns: instrument, issuing authority, effective date and obligation affected. Attach the signed document, not just a news report. A draft rule belongs in a watch list; an operative notification belongs in the compliance schedule.
The distinction matters particularly for the Act’s registration periods, which are linked to enforcement. Do not calculate a deadline from legislative passage, assent, Gazette publication of the Act or the launch of a website without establishing the relevant legal trigger.
The official Rajasthan worker-registration page is useful evidence that a registration facility exists. It is not, by itself, proof of an aggregator fee rate, the commencement of every provision, or a prescribed transaction-reporting format. Ask what the page actually does and retain the acknowledgement for the service used.
Where the operative instrument cannot be located, prepare a precise query to the department. State the entity, activity, location and proposed action; ask for the notification and prescribed route. A general email asking “Are we compliant?” is unlikely to produce an answer that can support payroll or finance decisions.
Build registration data that can be reconciled
Worker registration and aggregator registration concern different records. An individual registration acknowledgement does not replace the enterprise’s own applicability assessment. Similarly, an enterprise account does not prove that every engaged worker has been captured correctly.
The Rajasthan worker portal asks for identity and contact particulars, the company or work category and supporting records. Follow its current instructions when assisting an individual. Avoid promising that uploading documents guarantees any particular benefit. Eligibility for a scheme and registration in a database are different questions.
For internal preparation, give each worker a stable internal identifier and retain the external identifier separately. Track platform associations and engagement dates. A worker using several applications should not be represented internally as several unrelated people simply because the platforms assign different IDs.
Reconcile onboarding, active engagements and settlements. A worker may remain onboarded without earning in a month; another may receive a delayed adjustment after ceasing active work. Record these situations expressly. They are data questions that a registration count alone cannot explain.
Restrict access to Aadhaar, bank and identity documents. Operational teams generally need confirmation that verification occurred, rather than unrestricted copies of every document. Record who submitted information, when it was submitted and how a correction was requested.
Design a transaction ledger before programming a fee
The Act envisages a notified welfare fee associated with transactions and excludes taxes from the transaction value. This does not justify inventing a percentage, using another State’s percentage or charging an estimated amount to workers.
Before configuring a deduction or liability, finance should obtain the applicable rate notification and collection rules. The signed instruments should answer the relevant period, covered transaction, valuation treatment, return, recipient and payment timing. Where they do not answer an issue such as cancellations or later refunds, seek clarification rather than quietly selecting the easiest accounting treatment.
Prepare the ledger so that it can support the eventual verified requirement. Capture the order identifier, service location, transaction date, gross charge, separately identified taxes, worker payment, platform charges, cancellation status and subsequent adjustment. These are recommended controls; their inclusion here does not mean every field is already a prescribed Rajasthan return field.
Consider a ₹600 order with separately shown tax, a delivery charge and a later partial refund. The restaurant’s sales value, the delivery enterprise’s charge and the worker’s earnings are different figures. The team must identify which legal transaction and valuation rule applies before multiplying anything by a fee rate. A spreadsheet containing one undifferentiated “order value” column may be inadequate.
assureOffice can sit alongside the business’s financial and practice records when organising the supporting reconciliation. A specialist Rajasthan registration or welfare-fee filing capability should not be assumed from the availability of general financial tools at assureoffice.in.
Central social security is a separate workstream
The Code on Social Security, 2020 and the final central rules made in May 2026 create a distinct framework for gig and platform workers. The central rules address sharing existing worker details through electronic means and registering new engagements and exits on a real-time or daily basis. These requirements should not be overlooked while a business investigates State implementation.
Assign the central registration work to an accountable owner and test whether information actually reaches the designated system. An API design document is not proof of successful submission. Retain batch responses, rejected-record reports and corrected submissions. Match the worker identifier returned by the system to the internal record.
Do not treat central registration as automatic qualification for every welfare benefit. Schemes may impose additional conditions. Nor should a business assume that the statutory funding framework supplies a currently payable contribution rate without the required notification.
A marketplace may also face transport, food, consumer, tax or establishment regulation. A transport licence does not answer whether its gig-worker registration data is complete. Conversely, welfare registration does not authorise an otherwise regulated passenger-transport activity. Keep the legal bases separate even where one operational team supplies the same documents.
Use three practical classifications
For an application operator that matches customers with independent service providers, examine aggregator classification directly. Gather the platform terms, worker onboarding process and settlement architecture. The fact that the platform does not own vehicles is not a complete answer.
For a restaurant purchasing deliveries, document whether it merely places orders or also coordinates worker deployment and platform services. If it does the latter, obtain advice on the extended definition. Preserve the purchased-service contract and evidence of the actual process rather than relying on a sales representative’s assurance.
For a fleet or logistics coordinator working across applications, examine the coordination limb carefully. A business with no consumer-facing application can still play a material coordinating role. Review who provides the service, who sets worker terms and which entity communicates with the platforms.
These classifications are working conclusions, not permanent certificates. Review them when a business launches an application, begins onboarding workers, changes its delivery model or enters a new State.
An applicability dossier that survives a handover
Keep a dated diagram of the service chain, entity agreements, representative orders, worker engagement documents and the instrument register. Add a short conclusion explaining the classification, the facts on which it depends and any unresolved operational question.
Give each action an owner. Legal verifies the instrument and scope; operations confirms the real process; technology establishes data transmission; finance reconciles the ledger. These are recommended management allocations, not statutory job titles.
The final sign-off should identify what has actually been completed. “Worker records reconciled through September” is useful. “Gig law done” is not. At assureoffice.in, related financial records can provide supporting context, while the business retains responsibility for specialist legal classification and the actual government processes.
Frequently asked questions
1. Does every Rajasthan merchant using a delivery application become an aggregator?
Not automatically. Examine the merchant’s functions, including any coordination with aggregators. A purchased delivery service and an arrangement for managing platform-based work may produce different conclusions even when the invoices use similar descriptions.
2. Can a business without its own application fall within the definition?
Potentially. The coordination limb means application ownership is not the only relevant fact. Review contracts, dispatch functions and communications between the business, platforms and workers before concluding that the technology provider alone carries responsibility.
3. Does the Act’s 2023 date establish every compliance deadline?
No. The commencement clause requires an appointed date. A deadline tied to enforcement needs that legal trigger, and an operational payment may also need a rate and prescribed collection process. Record each instrument separately.
4. Is the live worker portal evidence that a welfare fee is payable?
It proves that a particular registration facility is available. It does not establish a fee percentage, valuation method or remittance deadline. Use the portal for its stated service and obtain the legal instruments needed for a payment decision.
5. Should we register workers before resolving our own classification?
Do not obstruct an individual’s access to an available registration service. At the same time, assess the enterprise’s role separately. Assisting a worker should not be represented as a definitive conclusion about every obligation of the assisting business.
6. Can we use Karnataka’s welfare-fee rate in Rajasthan?
No. State legislation and notifications have their own scope and effective dates. Copying another State’s configuration can create an unsupported charge and inaccurate accounting. Keep separate legal and system configurations for each jurisdiction.
7. Should tax be included when preparing transaction data?
Keep tax separately identifiable. The Rajasthan Act’s transaction-value provision excludes tax, but the applicable notified framework still needs to be applied to the correct transaction. Separating fields is better than trying to reconstruct tax from a net total later.
8. Can we recover a proposed fee from worker earnings?
Do not introduce a deduction merely because the business anticipates a welfare cost. Establish the operative liability and any lawful recovery mechanism first. Worker contracts and settlement statements should transparently reflect only supportable deductions.
9. What if workers use several platforms?
Keep one verified individual record linked to the different platform identifiers. Record the relevant engagements separately. This reduces duplicate records while preserving the information needed to understand payments and associations with several enterprises.
10. Is an e-Shram identifier the same as Rajasthan enterprise registration?
No. A worker identifier and an enterprise registration serve different purposes. Keep the issuing system and purpose against each identifier. Do not use one acknowledgement as evidence that all central and State actions have been completed.
11. Do central registration rules matter while State implementation is investigated?
Yes. The final central social-security rules have their own worker-data requirements. Allocate ownership and verify the designated submission process independently. An unresolved Rajasthan procedural question does not justify ignoring a separate central obligation.
12. Does registration guarantee health insurance or another benefit?
No. A particular scheme may require additional eligibility conditions and its own operational process. Explain this distinction when helping workers register so that an acknowledgement is not mistaken for an insurance policy or an approved benefit claim.
13. How should a company handle a departmental notice?
Preserve the notice and its receipt date, identify the legal entity addressed and collect the requested records. Check the cited instrument and respond through the specified route. Do not ignore the notice because a general online search did not locate the same instruction.
14. What evidence should a platform customer request from its provider?
Request a clear description of the provider’s role, relevant registration acknowledgements and responsibility for worker information. Avoid collecting unnecessary personal documents. Contractual allocation helps manage the relationship but cannot override a duty imposed directly by law.
15. Does a transport licence replace gig-worker compliance?
No. Transport authorisation concerns a different legal question. Map both workstreams, their responsible entities and renewal or reporting requirements. Shared documents can be reused appropriately, but the approvals should not be conflated.
16. What should technology teams build first?
Build reliable identifiers, engagement histories, transaction fields and submission logs. Avoid hard-coding an unverified fee. A configurable system with traceable inputs is easier to adapt when an operative notification or an authoritative clarification is obtained.
17. Can we upload an old worker list without checking it?
That risks duplicates, incorrect contact details and missing engagements. Reconcile the list to onboarding and payment records, document unresolved discrepancies and validate the accepted submission. Preserve an audit trail of corrections rather than overwriting the original without explanation.
18. Is calling workers independent contractors sufficient?
No. A label does not conclusively determine employment status or all statutory rights. Review the actual relationship when the facts indicate employment, and avoid using welfare registration to remove benefits that otherwise apply.
19. When should the classification be reviewed?
Review it after a material operational change, such as direct worker onboarding, a new dispatch role, a new application or expansion into Rajasthan. A periodic review also helps identify changed instruments, but the review frequency itself is a recommended control.
20. What should management approve before launch?
Approve the factual classification, verified legal instruments, responsible owners, data process and treatment of unresolved questions. A launch sign-off should explain concrete completed actions and outstanding dependencies, allowing management to understand the actual position rather than a generic compliance label.