Uber Challenges the Karnataka Gig Welfare Fee: Provisioning an Escrowed Levy While the Insurance Obligation Stays Live

When we covered the February 2026 welfare-fee notification, the question was how aggregators should structure insurance around a new statutory cost line. Five months later the question has moved to a courtroom, and the fee itself is sitting in escrow.

Two dates matter. On 3 July 2026, a coordinate bench of the Karnataka High Court passed an interim order directing Zomato, Swiggy, Blinkit and Zepto to deposit the gig workers' welfare fee with the Court Registry, granting them protection from coercive action upon such deposit. The money leaves the platform, but it does not reach the Karnataka Platform Based Gig Workers Welfare Board.

On 28 July 2026, as reported by LiveLaw, a single judge bench of Justice Suraj Govindaraj issued notice on a petition by Uber India Systems Private Limited challenging the constitutional validity of the Karnataka Platform-Based Gig Workers (Social Security and Welfare) Act, 2025 and the Rules framed under it. The Court extended the same interim arrangement to Uber, giving it three weeks from 28 July to make the deposit. Uber has also challenged the 27 January 2026 notification constituting the Welfare Board itself, and its petition was tagged with the pending batch, WP No. 19746/2026. The Economic Times reported on 29 July that the Court issued notice to both the Centre and the State.

The fee being litigated is real money already. As per the State's February 2026 notification, aggregators are liable to pay the welfare fee for the April to June quarter, at a notified rate of 1 per cent. So the food-delivery, quick-commerce and ride-hailing platforms covered by these orders are now depositing a live quarterly levy into a registry account while arguing that the statute behind it should not exist.

The litigation coverage has revived a confusion the February notification first created: treating the welfare fee, the platform's own insurance for workers, and the platform's liability exposure as one blended "gig compliance cost". They are three separate legal obligations, and the Court's interim order touches exactly one of them.

1. The statutory welfare fee. A levy under the 2025 Act, payable quarterly, now deposited with the Court Registry instead of the Welfare Board. This is the only obligation the interim arrangement addresses, and only to the extent of protecting depositing platforms from coercive action.
2. The aggregator's own group cover for platform workers. Group personal accident and group health cover are contractual promises the platform makes to its riders and driver-partners, bought from insurers on terms the platform negotiates. No court order in this batch suspends, dilutes or substitutes for them.
3. Vicarious and third-party liability. When a rider injures a pedestrian or damages property, the injured party's recovery runs through motor third-party cover and the platform's own liability programme. The welfare fee never touched this exposure, and the litigation does not either.

From a treasury standpoint, deposit with the Court Registry is the worst of both interim outcomes. The platform does not keep the money, so there is no cash-flow relief relative to paying the Board. And the worker does not receive a benefit, because the Board cannot draw on a registry deposit to fund schemes. The levy has become a quarterly outflow with no offsetting welfare delivery and no certainty about its final destination.

Three outcomes are possible at the end of the litigation. If the Act survives, the deposits presumably transmit to the Welfare Board and the fee becomes an ordinary statutory cost, as it was designed to be. If the Act or the Rules are struck down, the platforms have a claim to refund of what sits in the Registry. A middle path, where the Act survives but specific Rules or the fee computation are read down, could leave part of the deposit payable and part refundable.

For working-capital planning, the outflow must be treated as continuing. The protection from coercive action is conditional on deposit, so skipping a quarter to preserve cash forfeits the protection. Uber's three-week window from 28 July shows the Court expects the deposit to be made promptly once the benefit of the arrangement is extended.

There is also a worker-facing consequence platforms should not ignore. The 2025 Act was framed around a welfare fund that pays notified benefits to registered gig workers. While the money sits in escrow, the only benefits actually reaching a rider after an accident are the ones the platform's own group personal accident and health policies pay. That makes the insured layer, not the statutory one, the entire safety net for the duration of the litigation.

The finance question is genuinely awkward: how do you account for a statutory levy you have paid into a court registry, under protest, with a live constitutional challenge that could return the money?

The conservative framework runs like this. The obligation to pay arises from the notified statute, which remains in force; no court has stayed the levy itself, only channelled where it is deposited. So the quarterly fee accrues as an expense when the liability arises, on the same basis as any statutory levy. The deposit with the Registry is then a separate question: it is an outflow made under an interim order, and whether it becomes a recoverable amount depends on the outcome of WP No. 19746/2026 and the tagged petitions.

Under the Ind AS 37 framework for provisions, contingent liabilities and contingent assets, a potential refund contingent on winning a constitutional challenge is a contingent asset. Contingent assets are not recognised until recovery is virtually certain; at best, when an inflow becomes probable, it is disclosed. Recognising the registry deposit as a recoverable asset today, on the strength of having filed or joined a writ petition, would be aggressive and hard to defend at audit.

The practical posture

• Accrue the fee as an expense each quarter on the notified basis, and pay the deposit within the ordered timeline.
• Carry the deposit in records as an amount paid under interim court orders, with the order references, so the refund claim is fully documented if the challenge succeeds.
• Disclose the litigation and the possible refund as a contingent asset where the reporting framework calls for it, rather than netting it against the expense.
• Do not release or reverse the expense on the strength of interim orders alone. Reversal follows a final, favourable outcome, not the filing of a petition.

This is the point most worth repeating to a CFO who has just approved another registry deposit and is looking for offsetting savings. The constitutional challenge does not create any.

Motor third-party cover remains statutory under the Motor Vehicles Act for every vehicle on the platform, regardless of what happens to the Karnataka Act. Group personal accident and group health cover remain the platform's contractual promises to its worker base, and cancelling or thinning them mid-litigation would remove the only accident benefits currently reaching Karnataka riders at all, since the welfare fund is not paying anything while the fee sits in escrow. The platform's liability exposure to third parties and to workers is a function of tort law and the platform's operational control, not of the 2025 Act, and it runs on undisturbed.

If anything, the litigation raises the stakes on the insured layer. A serious rider fatality in Bengaluru during the escrow period will be examined against what the platform itself provided, because the statutory scheme will have paid nothing. The policy wording points flagged at the February stage still apply in full: the insured-person definition must capture registered gig partners, the on-duty versus 24-hour scope needs to be explicit, and the insurer's position on set-off should be confirmed in writing.

Statutory auditors reviewing the September 2026 quarter will find a levy expensed, cash deposited with a court registry, and a constitutional challenge in progress. The platforms that have a clean audit conversation will be the ones that prepared the file before the auditor asked.

The file should contain, at minimum:

• Copies of the 3 July 2026 interim order and the 28 July 2026 order extending the arrangement, with the platform's own petition or the order extending the benefit to it.
• The quarterly fee computation on the notified basis, including the transaction data behind it, showing the deposit amount was derived the same way a payment to the Board would have been.
• Proof of deposit with the Court Registry within the ordered timeline, since the protection from coercive action is conditional on the deposit being made.
• A position memo recording the accounting treatment: fee accrued as expense, deposit tracked as paid under interim orders, refund treated as a contingent asset, and the disclosure language used in the financial statements.
• Board or audit-committee minutes noting the litigation, the deposit obligation and the treatment adopted, so the judgment is documented as a considered one.

Consistency matters more than optimism. A platform that expenses the fee in one quarter and books a receivable the next, without a change in the litigation's status, invites a qualification. The defensible line is simple: the statute is in force, the levy is accrued, the deposit is made under court orders, and any recovery waits for a final outcome.

The escrow adds a wrinkle to a problem multi-state platforms already had: gig workers are mobile, and state welfare regimes are not harmonised. A rider may log sessions in Bengaluru for part of the year and in Hyderabad or Chennai for the rest, while other states advance their own platform-worker legislation with different fee bases. Layered on top sits the central Code on Social Security, 2020 framework for aggregator contributions into a national fund.

The operational requirement is transaction-level tagging by state. The Karnataka fee is computed on Karnataka transactions, and the registry deposit must be derived from the same base, because the deposit stands in for the fee. A platform that cannot cleanly split its transaction data by state cannot compute the Karnataka deposit defensibly, and it will face the same problem in every state that legislates next. Build the attribution logic once, at the transaction level, rather than reconstructing it quarterly.

The insurance programme should do the opposite: stay national. Group personal accident, group health and liability cover are placed for the whole worker base, and carving cover by state to mirror welfare-fee geography would create gaps every time a rider crosses a border. The clean architecture is state-tagged statutory contributions on one side, and a single national insured layer on the other, with the rider fleet programme priced on the full exposure.

One practical dividend: reconcile the state-tagged transaction data built for welfare-fee compliance against the exposure data given to insurers. Underwriters price better on category-split, state-split volumes, and a mismatch between the two datasets is exactly the kind of inconsistency that surfaces at claim stage.

For a platform or aggregator with Karnataka operations, the near-term list is short and concrete.

1. If the platform has not been extended the benefit of the interim arrangement, take advice on joining the batch or seeking the same protection. The protection from coercive action attaches to depositing platforms, not to the industry at large.
2. Diarise the deposit deadlines. Uber's window was three weeks from 28 July; each platform's obligation runs from its own order.
3. Fix the accounting posture now, in a position memo, rather than negotiating it with auditors after the quarter closes: expense the fee, document the deposit, disclose the contingency.
4. Hold the insurance programme steady. Renew group personal accident, group health, motor and liability lines on their own merits, and close out the wording endorsements flagged in the February cycle.
5. Keep worker communication honest. Riders should know what the platform's own policies pay after an accident, because for the duration of the escrow those policies are the only benefits actually flowing.

The February post ended by noting that the welfare fee is a cost of doing business and insurance is how the platform transfers risk. The litigation has not changed that division. It has only added a third instrument to manage: a deposit in a court registry that is neither a paid tax nor a recoverable asset until the Karnataka High Court says which it is. Treat the fee as live, the deposit as documented, the refund as contingent, and the insurance programme as untouched by all of it.