SShortSingh.
Back to feed

Four Rule 3 perquisites that cut tax bills under India's New Tax Regime

0
·1 views

Salaried employees in India who have opted for the New Tax Regime may be missing out on up to ₹1,20,000 in annual tax savings through four employer-provided benefits that remain exempt under Rule 3 of the Income Tax Rules 1962. Unlike Section 10 exemptions such as HRA and LTA, which were removed by the 2020 New Regime, Rule 3 perquisite valuations were left untouched and apply equally in both regimes. The four benefits are meal vouchers (capped at ₹26,400/year), employer gifts (capped at ₹5,000/year), telephone and internet bill reimbursements (no monetary cap), and a company car used for mixed purposes (fixed monthly taxable value regardless of actual cost). The key distinction in each case is the payment mechanism: reimbursements against actual bills or structured vouchers qualify, while cash allowances for the same purposes are fully taxable. Employees are advised to review their CTC structure and, where possible, ask HR to restructure cash allowances into qualifying reimbursement arrangements at no additional cost to the employer.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

Log in to join the discussion and vote.

Log in

Related stories

0
ProgrammingDEV Community ·

Engineering Guide Explains Why QR Codes Fail in the Field and How to Fix Them

A technical guide published on DEV Community outlines the engineering decisions that determine whether a QR code scans reliably in real-world conditions, not just on screen. The piece frames QR codes as input/output systems, where payload size, version, error correction level, and module size must be matched carefully to the physical medium. It explains that the four error correction levels — L, M, Q, and H — offer trade-offs between capacity and damage tolerance, with higher correction increasing module density and reducing effective scanning distance at a fixed print size. The guide warns that a payload near a version boundary can be pushed into a denser, harder-to-scan version by even a single extra URL parameter. Practical recommendations include computing the required version before generating a code and sizing up the physical print area when higher error correction is necessary, such as when overlaying a logo.

0
ProgrammingDEV Community ·

Developer Builds AI Agent in CI Pipeline to Automate Multi-Repo Release Notes

A developer at Entire automated the company's weekly release notes, called Dispatches, by integrating an AI agent named Goose into a GitHub Actions CI pipeline. The task proved far more complex than a similar project built at Block, where a single repository with clean release tags made automation straightforward. Entire's Dispatches span multiple projects with different deployment cadences, feature flags, and mixed public-private visibility, making it difficult to determine which changes were safe to announce. The developer iterated through several approaches, eventually shifting from release-tag-based triggers to a time-window method using the previous Dispatch's publication date to avoid duplicating entries. The pipeline was designed not just to surface what changed, but to assess whether each change had fully shipped, was stable, and was appropriate for public communication.

0
ProgrammingDEV Community ·

Dev cuts Next.js CI/CD pipeline from 15 minutes to 4 by fixing artifact bloat

A developer discovered their Azure DevOps pipeline was packaging a 1.2 GB artifact — including full node_modules and source files — despite Next.js already generating a lean 24 MB standalone build directory. The fix involved updating the pipeline to copy only the .next/standalone folder into the deployment zip, shrinking the transferred artifact from 614 MB compressed down to 24 MB. This single change reduced the total pipeline runtime from roughly 15 minutes to about 4 minutes. The developer also added a dedicated /api/health route after finding health checks were hitting auth middleware and returning redirects instead of status responses. A separate cookie-naming bug that caused an infinite sign-in loop locally was resolved by basing the secure cookie prefix on the actual NEXTAUTH_URL protocol rather than NODE_ENV.

Four Rule 3 perquisites that cut tax bills under India's New Tax Regime · ShortSingh