E-invoicing for MSME: a step-by-step checklist

If you run an MSME with B2B customers, e-invoicing is no longer a large-enterprise problem. Once your aggregate turnover crosses the current GST threshold, every B2B, export and SEZ invoice needs an IRN from the Invoice Registration Portal before it is legally valid. The hard part is rarely the concept; it is the fortnight you lose to field mapping, API testing and retraining accounts while month-end is already late. This checklist is the sequence that tends to work when a finance team has to go live without stopping billing.

Confirm whether e-invoicing for MSME applies to you

Start with the threshold, not the software. As of the August 2023 notification, e-invoicing applies to registered taxpayers whose aggregate turnover in any financial year from 2017-18 has exceeded ₹5 crore. That catches plenty of MSMEs. Turnover is PAN-level across GSTINs, so a ₹4 crore unit in Gurgaon and a ₹2 crore unit in Pune can push you over. Check the latest CBIC notification before you build anything—thresholds have moved before.

• It applies to B2B invoices, exports and SEZ supplies. It does not apply to B2C invoices in the same way.
• Exempt categories include banking, insurance, NBFC, GTA and passenger transport services. Confirm your specific case.
• If you are at ₹4.5 crore and growing, treat the next quarter as your planning window, not the next month.

Map your invoice data to the e-invoice schema

The IRP schema (INV-01) is strict. Your invoice PDF may look fine to a human and still fail because one field is missing. Pull one month of B2B invoices and check every mandatory field.

• Supplier and recipient GSTIN, including correct state code.
• Invoice number (keep it within 16 characters and avoid special characters) and date.
• Line items with description, HSN/SAC, quantity, UQC, taxable value, tax rate, CGST/SGST/IGST/Cess.
• Place of supply, reverse charge flag, shipping and billing address if different.
• Document type: invoice, credit note or debit note.

Common gaps are boring and predictable: missing UQC, HSN at the wrong digit level, place of supply copied from the billing address for a service, and invoice numbers with slashes or longer than 16 characters. If your billing software already captures these, the mapping is a config exercise. If it does not, a GST billing automation layer can sit between your ERP and the IRP so your team does not re-key data.

Worked example: you issue 400 B2B invoices a month. If 30% have at least one schema gap, that is 120 invoices to correct before your first sandbox test. That is not a technical problem; it is a data cleanup project.

Choose the integration route and test in sandbox

You have three practical routes:

• Direct API to the IRP, if you have an in-house developer who can own token management, error handling and uptime.
• Through a GST Suvidha Provider (GSP), which handles the IRP connection for a per-invoice or subscription fee.
• Through your accounting or billing software vendor, if they already have e-invoicing built in.

Whichever you pick, do not test with real invoices on day one. Register for sandbox credentials, generate a test IRN, print the signed QR code, and deliberately trigger errors: wrong GSTIN, duplicate invoice number, invalid HSN. Write down what each error means and who fixes it.

Budget for the run cost, not just the licence. If you are comparing build versus buy, our pricing page gives a rough range for custom finance integrations, but the bigger number is usually internal time. A manual IRN entry might take 3 minutes per invoice. At 400 invoices a month, that is 20 hours of repetitive data entry. At an ops salary of ₹40,000 a month (roughly ₹230 an hour), you are looking at about ₹4,600 a month in avoidable labour—before you count rejections and rework.

Run a parallel month and reconcile hard

Do not switch off your old process on the day you go live. Run e-invoicing in parallel for one full billing cycle. Generate an IRN for every B2B invoice, add the QR code, and keep your old invoice copy as a backup. Then reconcile.

• Every invoice in your books should have an IRN, and every IRN should map back to a ledger entry.
• Check GSTR-1 auto-population against your sales register. Mismatches usually come from cancelled invoices or credit notes.
• Remember the 24-hour cancellation window on the IRP. If an IRN is wrong, you cancel and reissue; you do not edit it.
• If your turnover is ₹10 crore or more, check the 30-day reporting limit for IRP reporting. It was extended to more taxpayers in 2024, so verify the current rule.

Train the team and write the failure SOP

E-invoicing is a finance process with an API attached. Name one owner for IRN generation, one for QR verification, and one for reconciliation. Write a one-page SOP: what to do when the IRP is down, when a GSTIN is invalid, when an invoice is cancelled, and when the buyer says they cannot see the QR code. Review it after the first month and again after the first quarter.

Where to start

If you are below the threshold, do not buy software yet. Clean your invoice data now: standardise invoice numbers, fix UQC and HSN fields, and keep place of supply accurate. If you are above it, pick one B2B invoice series, map it to the schema, and run a sandbox test this week. The teams that struggle are usually the ones that treat e-invoicing as an IT project on the last day of the month. If you want help with the IRP integration, data mapping or a billing workflow that stays inside your existing systems, Maysan Labs builds that kind of finance plumbing for growing companies.