This is a sample article, kept here so the page design can be reviewed. Replace it with the published piece by dropping the real markdown file into articles-src and running python build.py.
Between 2024 and 2026 I led product for a global VAT and e-invoicing domain, which meant living inside the mandates of a dozen-plus jurisdictions at once. Seen from that vantage point, India's e-invoicing design holds up better than most practitioners give it credit for.
Three models, one goal
Broadly, the world has settled into three architectures: clearance models where the government validates before the invoice is legal, post-audit models where you invoice freely and answer later, and hybrid reporting models in between. Each trades friction for control differently.
India's IRP approach sits in the clearance family but with a deliberately thin validation layer: schema, uniqueness, and little else. That thinness is the feature. Validation that tries to be clever becomes a business bottleneck; validation that stays mechanical becomes infrastructure.
What travels well
The IRN-plus-QR pattern, the fixed schema, and the ecosystem of ASPs that grew around the API are the parts other jurisdictions keep reinventing badly. The parts that travel less well, the published piece covers in detail, along with what practitioners advising exporters should watch as more trading partners switch on their own mandates.
