E Invoicing Integration With Accounting Software

A worked example of e invoicing integration with accounting software at an Indian mid-market company, from IRN generation to GST returns.

Maysan Insights · · 4 min read

Xin

Most Indian mid-market companies do not have an e-invoicing problem; they have a reconciliation problem. The IRN gets generated, the invoice goes out, and then someone spends the last week of the month matching portal downloads to Tally or Zoho Books. It hits finance and operations teams at firms with enough B2B volume to cross the e-invoicing threshold but not enough people to absorb manual work. The fix is not another portal login; it is e invoicing integration with accounting software that makes the compliance step part of invoice creation.

What does e invoicing integration with accounting software actually change?

It changes where the IRN is generated: inside the invoice entry screen, not in a separate government portal. With a working integration, the accounting system sends invoice data to the Invoice Registration Portal (IRP) when a user saves a sales invoice, receives the IRN, acknowledgement number and signed QR code back, and stores them against the same voucher. The finance team stops exporting JSON files, uploading them, downloading signed invoices and attaching PDFs by hand. More importantly, invalid master data can be blocked before the invoice is posted, so a wrong GSTIN or missing HSN does not become a month-end cleanup item.

A worked example: 2,400 invoices a month in Tally and a B2B portal

Consider an illustrative Gurgaon industrial-components distributor with ₹180 crore turnover, 2,400 B2B invoices a month and a finance team of nine. About 1,900 invoices need an IRN. Before integration, two executives spent roughly 2.5 minutes per invoice on portal upload, download and attachment, which is about 79 hours a month before rework. After integrating its custom dealer portal with Tally Prime through a middleware layer, the flow became: dealer places order, portal validates GSTIN and place of supply, invoice posts to Tally, IRP call returns IRN in a few seconds, and the QR code prints on the PDF. The same team now spends about 12 hours a month on exceptions. At a loaded cost of ₹450 an hour, that is roughly ₹30,000 a month of recovered capacity, before counting faster collections from cleaner invoices.

What data has to match before the IRN call succeeds?

Four master-data fields cause most IRN failures: recipient GSTIN status, invoice number series, HSN/SAC with tax rate, and place of supply. Check them before the API call: - Recipient GSTIN status: cancelled, suspended or inactive GSTINs should fail fast, not post. - Invoice number series: duplicate or skipped numbers break the IRN and GSTR-1 match. - HSN/SAC and tax rate: a wrong HSN can change tax and invite a notice. - Place of supply: a customer address in the wrong state creates a return problem even when the IRN succeeds.

The IRP schema also expects supplier GSTIN, document type and number, invoice date, taxable value and tax amounts. A good integration validates the full set and returns a clear error to the person raising the invoice.

How do credit notes, cancellations and GST returns fit together?

Treat the IRN lifecycle and month-end reconciliation as one workflow, not two clean-up jobs. If an invoice is wrong, an IRN can be cancelled within 24 hours of generation; after that, issue a credit note and report it in GSTR-1. Your accounting software should link the credit note to the original invoice number and IRN, store the reason, and pull the latest status from the IRP. At month-end, compare invoice number, IRN, taxable value and tax amount across books, IRP data and GSTR-1. In the distributor example, three days of manual matching became a half-day exception review covering 30-40 items. Keep TDS and TCS out of the IRN payload; they belong in the accounting entry and tax return, not the e-invoice schema.

What should you check before choosing an integration route?

Choose based on invoice volume, your accounting system and who owns master data, not on the demo. There are three common routes: a native connector inside Tally, Zoho Books or SAP B1; a middleware API from an e-invoicing provider that sits between accounting and the IRP; or a custom build on a GSP/IRP API. Native connectors are cheapest but vary in error handling. Middleware is usually fastest for mid-market firms with one or two accounting systems. Custom builds suit companies with a dealer portal or ERP that already owns invoice data. For a 2,000-3,000 invoice per month operation, a middleware or custom integration typically pays back in 4-8 months. Review GST billing automation options and pricing before committing to a licence.

Where to start

Start with one invoice series and one customer segment, not the whole company. List every field the IRP needs, compare it with your accounting master, and run the integration in parallel for two weeks before switching off manual uploads. Measure exceptions per 100 invoices, not just successful IRNs. If you want help mapping the flow for your accounting stack, Maysan Labs builds GST billing automation and can scope the integration against your current Tally, Zoho or ERP setup.

Buying software or a website?

Twelve questions to ask any vendor before you sign: price, your data, fit for an Indian business and support.

Get the free checklist

Written by Maysan Insights at Maysan Labs, a software studio in Gurgaon, India. Follow us on LinkedIn