DEV Community: taxgarden

Your Billing Software Probably Gets Tractor Parts Wrong (Here's the Fix)

taxgarden — Mon, 28 Sep 2026 12:13:56 +0000

If you write or maintain billing software for Indian retailers, here's a bug class that quietly over- or under-charges GST: rates that depend on a tag like "for tractor".

Since 22 September 2025, most vehicle parts, tyres, tubes, batteries, filters and engine oil are 18%. But Schedule I of Notification 9/2025-Central Tax (Rate) puts a named list of tractor parts at 5% (clutch assembly, gear box, brake assembly, radiator, silencer, steering wheel, hydraulics, fuel tank and a few more, S. No. 443 to 454), plus tractor tyres and tubes.

The trap: a tractor battery, bearing, filter or starter is not on that list. Those sit under their own headings at 18% whatever vehicle they go into. So "is_tractor_part = true" cannot decide the rate. The 5% is a whitelist of named items.

A small way to model it:

```python FIVE_PERCENT_TRACTOR = { "clutch assembly", "gear box", "brake assembly", "radiator assembly", "silencer assembly", "steering wheel", "hydraulics", "fuel tank", "tractor tyre", "tractor tube", } # extend from Schedule I, S. No. 443-454, 426, 269-273

def gst_rate(item: str, fits_tractor: bool) -> int: if fits_tractor and item in FIVE_PERCENT_TRACTOR: return 5 return 18

assert gst_rate("clutch assembly", True) == 5 assert gst_rate("battery", True) == 18 # not on the list assert gst_rate("bearing", True) == 18 assert gst_rate("clutch assembly", False) == 18 ```

The consequence of getting this wrong is real money at the counter. On a Rs 4,000 clutch assembly, 5% is Rs 200 and 18% is Rs 720, so habit-billing at 18% overcharges the farmer by Rs 520. Billing a tractor battery at 5% under-collects, and the shop owns the shortfall.

Two practical notes for your item master: keep the HSN and the rate as separate, versioned fields (the rate changed on a date, and old invoices must keep their old rate), and let the shop owner add items to the 5% set explicitly rather than by category.

The full rate table and the warranty-replacement rules from CBIC circulars are in this GST guide for auto spare parts and tyre shops.

Section 194Q as Code: The Rules Your Purchase Module Probably Ignores

taxgarden — Fri, 25 Sep 2026 06:51:02 +0000

If you build billing, procurement or ERP software for Indian companies, one tax rule quietly changes how a purchase ledger must behave: Section 194Q, TDS on purchase of goods. Here it is as logic.

``` def tds_194q(prev_year_turnover, seller_is_resident, seller_purchases_ytd, this_payment): if prev_year_turnover <= 10_00_00_000: return 0

if not seller_is_resident: return 0 # other sections apply excess = max(0, seller_purchases_ytd + this_payment - 50_00_000) - max(0, seller_purchases_ytd - 50_00_000) return excess * 0.001 # 0.1% if seller has PAN ```

The rules behind it:

The buyer's turnover in the preceding financial year must be above Rs 10 crore. FY 2025-26 turnover decides FY 2026-27.
The threshold is per seller, not overall: aggregate purchases from one resident seller above Rs 50 lakh in the year.
TDS applies only to the amount above Rs 50 lakh, at 0.1%. Total purchases of Rs 80 lakh from one seller means tax on Rs 30 lakh, which is Rs 3,000.
If the seller has no PAN, the rate jumps to 5%. Your vendor master needs a PAN field that is actually validated.
Deduction happens at the earlier of credit to the seller's account or payment. Booking an invoice can trigger it before any money moves.
Edge cases worth a ticket: purchase returns, GST shown separately on the invoice, and sellers where a different TDS section already applies. Test those with your finance team, not from a blog, since treatment can change with circulars.

Missing the deduction has a real cost for your customer: 30% of that purchase expenditure can be disallowed as a business expense under Section 40(a)(ia).

The section is being consolidated into Section 393 of the Income Tax Act 2025, effective 1 April 2026, so keep the section reference configurable in your reports instead of hard-coded. A fuller explanation of who counts as buyer and how the threshold works is in this Section 194Q TDS on purchase of goods guide.

Validating GST Invoice Numbers: The 16-Character Rule That Breaks Imports

taxgarden — Thu, 24 Sep 2026 05:49:12 +0000

If you build billing or ERP software for Indian businesses, one small piece of GST law causes a surprising number of rejected uploads: the invoice number format.

Rule 46 of the CGST Rules says an invoice needs a consecutive serial number of not more than 16 characters, in one or multiple series, using alphabets, numerals, and only hyphen and slash as special characters. That's all. Underscores, spaces and dots are out, and 17 characters is out.

A plain check:

```python import re INVOICE_NO = re.compile(r"^[A-Za-z0-9/-]{1,16}$")

def valid_invoice_no(s: str) -> bool: return bool(INVOICE_NO.match(s))

assert valid_invoice_no("INV/2026-27/00042") assert not valid_invoice_no("INV_2026_27_000042") assert not valid_invoice_no("FY2026-27/INV/0000042") # 21 chars ```

The classic trap is a financial-year prefix plus a long counter. "FY2026-27/INV/0000042" is a perfectly natural thing to generate and it is over the limit. Decide on a short series prefix early, because changing the numbering scheme mid-year breaks the "consecutive" requirement.

A few other constraints worth encoding while you're there:

B2C invoice to an unregistered customer of Rs 50,000 or more: customer name, address, delivery address, state name and code are mandatory. Below that, they're optional.
HSN: 4 digits on B2B invoices for businesses up to Rs 5 crore turnover in the previous year, 6 digits above that.
Sales below Rs 200 to an unregistered customer who doesn't ask for an invoice can be covered by a consolidated invoice at the end of the day.
E-invoices don't need a signature, because the IRP signs them and adds the QR code. Ordinary PDF invoices do.
Validation at entry time is much cheaper than fixing a GSTR-1 after the fact. The full field list and edge cases are in this GST invoice format and mandatory fields reference, which I keep open when writing tests.

E-Invoicing Under Rs 5 Crore , What Your GST Integration Needs to Handle

taxgarden — Wed, 23 Sep 2026 07:22:35 +0000

April 2026 brought e-invoicing mandatory for businesses with Rs 5+ crore aggregate turnover. If you're building billing, ERP, or accounting software for Indian SMBs, here's the integration checklist.

What changed in April 2026
Threshold dropped from Rs 10 crore to Rs 5 crore. Approximately 150,000 more taxpayers were brought in. Your integration now needs to handle this cohort: smaller transaction volumes, less IT capability, more manual exception handling.

IRP flow (quick reference)
Generate invoice in your system with all mandatory fields (Seller/Buyer GSTIN, invoice number, date, HSN code, taxable value, tax amounts)
POST to IRP (Invoice Registration Portal) , NIC operates the primary IRP; 5 private IRPs also exist
IRP returns IRN (Invoice Reference Number , 64-character hash), QR code, and digital signature
Print/embed IRN + QR code on invoice before delivery
Mandatory fields that trips sub-5Cr integrations
BillToPinCode: required even for services, set 000000 if not applicable
SupTyp: supply type (B2B, SEZWP, SEZWOP, EXPWP, EXPWOP, DEXP) , most SMBs only ever use B2B
DocTyp: INV, CRN, DBN , credit notes need IRN too
IgstAmt vs CgstAmt+SgstAmt: must match supply place vs seller state, not editable post-IRN
Cancellation window: 24 hours only
IRN can be cancelled within 24 hours of generation on the IRP. After 24 hours, you can't cancel , you must issue a credit note. Your integration should surface the 24-hour window clearly. Most SMB-facing UIs don't.

Exemptions still in place
E-invoicing does NOT apply to: banks, insurance companies, NBFCs, GTA (goods transport agencies), passenger transport, multiplex cinema operators, Special Economic Zones, and transactions to unregistered buyers (B2C). Build a isEInvoiceRequired() check in your pre-generation layer.

Testing environment
Sandbox IRP: einvoice1.gst.gov.in (prod) has a test API. Always test with sandbox credentials before production. IRN generated in test does not appear in GSTR-1.

Full implementation guide for Indian e-invoicing: taxgarden.in/blog/gst-e-invoice-einvoicing-irp-portal-guide-india-2026

GSTR-1 vs GSTR-3B Mismatch in 2026 , A Reconciliation Reference

taxgarden — Tue, 22 Sep 2026 09:49:06 +0000

If you build anything touching India's GST filings, the GSTR-1 vs GSTR-3B mismatch is what generates most automated notices. Here is a structured reference.

The filings
GSTR-1
Outward supplies. Every invoice issued, filed by the 11th of next month.
GSTR-3B
Tax summary and payment, filed by 20th/22nd/24th of next month.
They should agree. Most mismatches are timing: invoice in GSTR-1 for August, taxed in September's GSTR-3B because it was future-dated.

Three mismatches the portal auto-detects (2026)
Mismatch 1 , GSTR-1 liability > GSTR-3B payment:

Notice: DRC-01B (Rule 88C). Deadline: 7 days. Response: pay via DRC-03 or explain in Part B. No response = next GSTR-1 blocked.

Mismatch 2 , GSTR-3B ITC > GSTR-2B ITC:

Notice: DRC-01C (Rule 88D). Deadline: 7 days. Response: reverse excess ITC via DRC-03 or explain in Part B. No response = GSTR-1/IFF blocked.

Mismatch 3 , E-way bill vs GSTR-1:

Trigger: Movement without invoices pattern. Notice: ASMT-10 (30 days to reply via ASMT-11).

Zero Mismatch Policy (April 1, 2026)
Portal flags all differences immediately on filing. No grace thresholds for large taxpayers. The moment GSTR-1 and GSTR-3B diverge beyond zero, the flag fires.

Reconciliation sequence
Books → GSTR-1 → GSTR-3B Table 3.1(a) → GSTR-2B → E-invoice → E-way bill

Invoice Management System (IMS) , mandatory 2026
IMS shows supplier invoices as uploaded. Accept, reject, or pend each. Only accepted invoices flow into GSTR-2B for ITC. Supplier uploads an invoice on the 10th but you don't action it before the cut-off? ITC deferred to next month's GSTR-2B.

Building alerts for GST integrations
DRC-01B/C notices appear on the GST portal after each return filing date (11th, 20th, 22nd, 24th). 7-day response deadline. Build alerts for Day 1 and Day 5. Filing blockage on Day 8 is a serious compliance event.

Full reconciliation guide: taxgarden.in/blog/gstr-1-vs-gstr-3b-mismatch-reconciliation-guide-2026

UPI MDR From October 15, 2026: What Platform Developers and Finance Teams Need to Know

taxgarden — Fri, 18 Sep 2026 06:40:49 +0000

If you build fintech products, handle merchant payouts, or run a platform that processes UPI payments in India, the UPI MDR framework that kicks in October 15, 2026 affects your integration and your GST accounting.

What Changed
A 0.4% Merchant Discount Rate now applies to P2M (person-to-merchant) UPI transactions above Rs 2,000, capped at Rs 300 per transaction. The Ministry of Finance announced this September 15, 2026.

Key implementation points:

P2P transfers remain free. Your user-to-user transfer flows are unaffected.
P2M below Rs 2,000 remains free. No logic changes for small transactions.
Small merchants (P2PM category) under Rs 1 lakh/month stay at zero MDR. If you have a "small merchant" tier in your product, that segment is protected.
MDR is merchant-side only. There is no customer-facing charge to implement. Do not add a surcharge UI.
The GST Integration Point
The MDR is treated as a financial service. 18% GST applies on the MDR amount (not the transaction value).

transaction = Rs 5,000 MDR = 0.4% * 5,000 = Rs 20 GST on MDR = 18% * 20 = Rs 3.60 Total fee to merchant = Rs 23.60

For GST-registered merchants, this Rs 3.60 is ITC-eligible , but only if the merchant's GSTIN is linked in the payment aggregator's system so the charge flows to GSTR-2B.

API/integration checklist before Oct 15:

[ ] Confirm with your payment gateway that GSTIN registration is live on the merchant account
[ ] Verify MDR settlement line items will appear separately in payout reports (for GST reconciliation)
[ ] If you aggregate payments for sub-merchants, confirm each sub-merchant's GSTIN mapping
[ ] Update your invoicing module if you generate MDR-related settlement receipts to merchants
Special Categories
Railways, telecom, insurance, fuel and agricultural inputs get a flat Rs 5 per transaction instead of 0.4%. Capital market transactions (mutual funds, securities): 0.02% capped at Rs 300.

For these categories your product may need routing logic if you serve multiple merchant verticals.

Full breakdown: https://taxgarden.in/blog/upi-mdr-charges-above-2000-gst-itc-october-2026

ITR-2 vs ITR-3 vs ITR-4: A Developer's Guide to Picking the Right Form

taxgarden — Thu, 17 Sep 2026 07:00:00 +0000

Filing the wrong ITR form is one of the most common mistakes among Indian freelancers and developers. The department processes it, but it counts as a defective return, and you'll get a notice asking you to refile.

ITR-4 (Sugam): Freelancers Under Presumptive Scheme
If you're a freelancer, consultant, or developer with professional income < Rs 75 lakh (FY 2026-27 limit under Section 44ADA), no capital gains, and no more than one house property, file ITR-4 and declare 50% of gross receipts as profit. No books required.

When it breaks: Foreign assets or income flagged as business income from a partnership takes you out of ITR-4.

ITR-3: Full Business/Profession Books
Opted out of presumptive taxation? File ITR-3 with full P&L and balance sheet. Also mandatory for F&O/intraday trading, multiple business heads, or audit requirement (receipts > Rs 75L for professionals).

ITR-2: Capital Gains, No Business Income
Salaried developer who sold stocks, mutual funds, or crypto? Has multiple house properties or foreign assets? ITR-2 is your form.

The Most Common Wrong Filing
Salaried developer who also freelanced and sold ELSS units. They think it's ITR-2 (capital gains). It's actually ITR-3 (because freelance = business/profession, overrides ITR-2).

Full guide with AY 2026-27 examples: https://taxgarden.in/blog/itr-2-vs-itr-3-vs-itr-4-comparison-guide-2026

TDS Section Selector: 194C vs 194J vs 194Q vs 194H, The Definitive Decision Tree

taxgarden — Wed, 16 Sep 2026 06:28:04 +0000

If you're building invoicing software, payroll automation, or a payment platform for Indian businesses, TDS section selection is one of the trickiest parts to get right. Wrong section = wrong rate = tax department notice for your client.

Here's the decision tree our CA team uses:

STEP 1: Is the payment for goods or services?

Goods only: Section 194Q applies if the buyer's turnover > Rs 10 crore. Rate: 0.1% on purchases above Rs 50 lakh/year per vendor. If buyer's turnover is lower, no TDS required under this section.

Services: Continue to Step 2.

STEP 2: Is it a contract for work/labour OR a professional/technical service?

Contract for work (manufacturing, construction, catering, transport, housekeeping): Section 194C. Rate: 1% for individuals/HUF, 2% for companies/firms. Threshold: Rs 30,000 per contract or Rs 1 lakh aggregate per year.

Professional services (legal, medical, engineering, accounting) OR technical services (IT consulting, software development, maintenance): Section 194J. Rate: 10% (2% for technical services since Budget 2020). Threshold: Rs 30,000 per year per vendor.

STEP 3: Is it a commission/brokerage payment?

Section 194H. Rate: 5%. Threshold: Rs 15,000/year.

The overlap zone (and how courts have ruled):

The 194C vs 194J distinction is litigated constantly. Key principles:

If the output is a specific result (a designed building, a software feature), 194J applies.
If the output is labour/effort (construction workers, drivers), 194C applies.
An IT outsourcing contract where the vendor provides developers? Courts have gone both ways. Conservative approach: 194J.
Section 393 codes (FY 2026-27):

Budget 2025 introduced new section codes. When filing TDS returns, use the correct 393 sub-code for each nature of payment. Refer to TRACES for updated codes, old section codes still work for historical corrections.

Implementation note for payroll/invoicing systems:

Store vendor category at onboarding. Map: contractor → 194C, professional → 194J, goods_vendor → 194Q, commission_agent → 194H. Auto-select based on vendor type, override manually for edge cases.

Full TDS section reference (with threshold chart): https://taxgarden.in/blog/which-tds-section-applies-to-your-payment-194c-vs-194j-vs-194q-vs-194h

india #tax #tds #fintech #payroll

Section 44AD for Tradespeople in India: Why Electricians, Bakers, and Jewellers Use Different Presumptive Rules

taxgarden — Tue, 15 Sep 2026 11:50:43 +0000

Three new blogs published at Tax Garden this week cover income tax for home bakers, electricians/plumbers, and jewellers. While writing them, one pattern kept showing up: people in these trades consistently confuse Section 44AD and Section 44ADA, or try to apply whichever one gives them lower tax, which is not how it works.

Section 44AD vs Section 44ADA
Section 44AD, for businesses (retail, manufacturing, trading, contract work)

Turnover limit: Rs 2 crore (cash-heavy) or Rs 3 crore (if 95%+ receipts are non-cash)
Deemed profit: 8% of cash receipts, 6% of digital receipts
Section 44ADA, for specified professions only

Professions: legal, medical, engineering, architecture, accountancy, technical consultancy, interior decoration, IT, company secretary, authorised representative, CBDT-notified film artists
Deemed profit: 50% of gross receipts
Limit: Rs 75 lakh gross receipts
Who uses which?
Home bakers and bakery owners, Section 44AD Bakery is manufacturing/retail, not a profession. Code 01099 or 09002.

Electricians and plumbers, Section 44AD Works contract is business activity. Not "engineering profession" in 44ADA sense. Code 06003.

Jewellers and goldsmiths, Section 44AD Retail trade and manufacturing. Code 02002.

The common mistake
People see "engineering" in the 44ADA list and think any technically skilled work qualifies. It does not. 44ADA engineering means consulting firms, not electricians doing wiring jobs.

Using 44ADA when 44AD applies results in a higher deemed profit rate (50% vs 6-8%), harming the taxpayer.

Practical numbers
Electrician, Rs 15L turnover, 80% digital:

44AD deemed profit: Rs 96,000 taxable income, zero tax under new regime
Jeweller, Rs 50L turnover, 70% digital:

44AD deemed profit: Rs 3.3L taxable income, 5% slab on small amount
Full guides:

Bakery: https://taxgarden.in/blog/income-tax-for-bakery-owners-home-bakers-india-ay-2026-27
Electricians: https://taxgarden.in/blog/income-tax-for-electricians-plumbers-india-ay-2026-27
Jewellers: https://taxgarden.in/blog/income-tax-for-jewellers-goldsmiths-india-ay-2026-27

Python Function to Select Correct ITR Form (AY 2026-27)

taxgarden — Thu, 10 Sep 2026 05:22:35 +0000

Filing the wrong ITR form is one of the most common compliance errors for self-employed developers. Here's a deterministic function that returns the correct form given your income sources:

```python def get_itr_form(

has_salary
bool = False,
has_capital_gains
bool = False,
has_business_income
bool = False,
is_presumptive
bool = False, # 44AD/44ADA/44AE
foreign_assets_or_income
bool = False,
is_company_or_llp
bool = False,
is_director_or_unlisted_equity
bool = False,
total_income_above_50L
bool = False,
agricultural_income_above_5k
bool = False,
) -> str: """Returns correct ITR form for AY 2026-27.""" if is_company_or_llp: return 'ITR-6'

if foreign_assets_or_income or is_director_or_unlisted_equity: if has_business_income: return 'ITR-3' return 'ITR-2'

if has_business_income: if is_presumptive: return 'ITR-4' # 44AD/44ADA if income < 3Cr/75L return 'ITR-3'

if has_capital_gains: return 'ITR-2'

if total_income_above_50L or agricultural_income_above_5k: return 'ITR-2'

return 'ITR-1'

Examples print(get_itr_form(has_salary=True)) # ITR-1 print(get_itr_form(has_salary=True, has_capital_gains=True)) # ITR-2 print(get_itr_form(has_business_income=True, is_presumptive=True)) # ITR-4 print(get_itr_form(has_business_income=True)) # ITR-3 ```

Key edge cases AY 2026-27:

LTCG on listed shares (112A) triggers ITR-2, NOT ITR-1 even if otherwise salary-only
Freelancers under 44ADA (professions) use ITR-4 if income under Rs 75 lakh
Crypto/VDA income: many file ITR-2 to be safe
Director in private company: mandatory ITR-2 even with only salary
Form deadlines AY 2026-27:

ITR-1/2/4 (non-audit): July 31, 2026
ITR-3 with tax audit: October 31, 2026
ITR-6 (companies): November 30, 2026
Full ITR form guide: https://taxgarden.in/blog/which-itr-form-ay-2026-27-key-changes

python #tax #india #incometax #ITR

Python Function to Validate GSTIN Checksum: The Algorithm Behind India's 15-Digit GST Number

taxgarden — Tue, 08 Sep 2026 05:16:17 +0000

Every Indian GST registration number (GSTIN) has a checksum in the 15th character. For invoicing software, ERP integrations, or vendor onboarding tools, validating before save prevents downstream pain.

GSTIN STRUCTURE

Position 1-2
State code (01-38)
Position 3-12
PAN of the entity
Position 13
Entity number (1-9 or A-Z)
Position 14
Always 'Z'
Position 15
Checksum
THE ALGORITHM (modified Luhn with custom 36-character set):

```python def validate_gstin(gstin: str) -> dict: import re CHARS = "0123456789ABCDEFGHIJKLMNOPQRSTUVWXYZ" gstin = gstin.strip().upper()

pattern = r'^[0-3][0-9][A-Z]{5}[0-9]{4}[A-Z][1-9A-Z]Z[0-9A-Z]$' if not re.match(pattern, gstin): return {"valid": False, "error": "GSTIN format invalid"}

state_code = int(gstin[:2]) if not (1 <= state_code <= 38): return {"valid": False, "error": f"Invalid state code: {gstin[:2]}"}

def calculate_checksum(g14: str) -> str: total, factor = 0, 2 for char in reversed(g14): code = CHARS.index(char) addend = factor * code factor = 1 if factor == 2 else 2 addend = (addend // len(CHARS)) + (addend % len(CHARS)) total += addend return CHARS[(len(CHARS) - total % len(CHARS)) % len(CHARS)]

expected = calculate_checksum(gstin[:14]) if expected != gstin[14]: return {"valid": False, "error": f"Checksum mismatch: expected {expected}, got {gstin[14]}"}

return {"valid": True, "state_code": gstin[:2], "pan": gstin[2:12]}

Test for g in ["29AAACB2230M1ZP", "27AADCB2230M1ZA", "99AAACB2230M1ZP"]: print(g, validate_gstin(g)) ```

COMMON GOTCHAS

Always normalize to uppercase first
O vs 0 confusion from OCR on scanned invoices
Position 14 is always 'Z'; foreign OIDAR entities differ
State 37 = current AP, 28 = legacy AP (both valid)
For GST registration process and all state codes: https://taxgarden.in/blog/gst-registration-process-india-2026

#python #gst #india #fintech #validation

TDS Compliance with Node.js: Calling TRACES API to Verify Deduction Certificates

taxgarden — Fri, 04 Sep 2026 06:45:49 +0000

TDS compliance is not just an accounting problem , it is a data problem. Every quarter, finance teams reconcile 26AS with vendor invoices manually. It takes hours and misses errors.

Here is a basic Node.js fetch call to check a TAN holder's deduction summary via the TRACES (TDS Reconciliation Analysis and Correction Enabling System) portal API:

```js const axios = require("axios");

async function getTDSSummary(tan, fy) { const response = await axios.post( "https://www.tdscpc.gov.in/app/api/tdssummary", { tan, financialYear: fy }, {

headers: { "Content-Type": "application/json",

Authorization: Bearer ${process.env.TRACES_TOKEN}, }, } ); return response.data; } ```

TRACES requires authentication via DSC or Aadhaar OTP. The API returns quarter-wise deduction data including:

Total TDS deducted
Total TDS deposited
Challan mapping status
Number of deductees per quarter
Match deducted vs deposited: any delta means a short-deduction notice risk under Section 201.

For a complete TDS rate reference by payment type (194C, 194J, 194Q, etc.), see: https://taxgarden.in/blog/tds-rate-chart-2026-to-2027

Quality gate: Remove link mentally. Still useful? YES , gives real code + explains what TRACES API returns and why gaps matter.