TallyPrime E-Invoice Error Checklist: IRN, GSTIN, HSN and QR-Code Troubleshooting

Find the stage that failed before changing the invoice

An e-invoice problem can occur before submission, during portal validation, after a response is lost, or when printing an already registered invoice. These situations need different checks. Capture the exact error and current voucher status before editing data or trying another submission.

The practice cases below explain how to isolate the problem in TallyPrime. They do not establish whether a particular business must use e-invoicing or whether a correction is legally permitted. Confirm applicable rules and the authorised correction process for the actual transaction.

Core concepts to learn

Build a practice scenario

1. Step 1: Record the company registration, voucher reference, exact error, time and submission status.
2. Step 2: Compare the rejected fields with the approved invoice and master-data evidence.
3. Step 3: Check whether an IRN already exists before retrying generation or recreating a voucher.
4. Step 4: Verify the returned registration details and printed output, then retain the reviewed resolution.

Use sample, authorised or fictional data. Do not publish credentials, business data, account numbers or customer information in a portfolio. If a task has financial, security or production impact, include a review or approval step before any change.

What good work looks like

Distinguish the accounting voucher, IRN and printed QR code

A saved sales voucher is the accounting record in TallyPrime. Successful registration through an Invoice Registration Portal returns the registration information associated with the submitted document. The invoice reference number, or IRN, is part of that evidence. A print preview alone does not establish whether registration succeeded.

TallyHelp explains that successful online generation updates IRN details in the voucher and that the invoice can then be printed with the IRN and QR code. If a QR code is missing from a printout, first determine whether the voucher contains the returned registration information. A print configuration problem should not be treated as a reason to create another tax invoice.

The signed e-invoice QR code is also different from a payment QR code. The GSTN-authorised IRIS portal provides verification for signed invoice JSON and signed QR data. Compare the verified supplier, buyer and document information with the invoice under review. Do not judge authenticity solely by the presence of a square graphic on paper.

Check identities and document fields together

For a GSTIN-related error, compare the selected company registration, buyer details and transaction data with the approved source records. A correct party master does not prove every saved voucher contains the intended details. Bill-to, ship-to and place-of-supply information also deserve separate inspection where applicable; one address field should not be used as a shortcut for all three concepts.

For an HSN or item-validation error, identify the exact rejected line and field. Review the product or service classification, description and supporting classification decision. Do not choose a different code merely because the portal accepts it. The software validates the submitted data, while the business remains responsible for the underlying classification.

Record the document type, number and date consistently. A number conflict may concern an earlier registration rather than a typing error in the current screen. Preserve the genuine business document identity during investigation. Changing its number to bypass a rejection can create a second record and make subsequent reconciliation harder.

A fictional value-check exercise

Suppose an approved training invoice contains two lines with taxable values of Rs 6,000 and Rs 4,000. For this arithmetic exercise only, assume tax of Rs 1,800 in total and no freight, cess, discounts or rounding. The expected invoice value is Rs 11,800. These amounts do not prescribe a classification or tax rate for any real supply.

If the submitted document shows Rs 10,000 taxable value, Rs 1,800 tax and Rs 11,900 invoice value, explain the Rs 100 discrepancy before resubmission. Inspect additional-charge and rounding fields and compare the voucher with the source invoice. Do not reduce a tax amount or add a balancing discount solely to make the figures fit.

If the totals agree but a line fails, inspect the line-level values rather than changing the invoice total. Quantity, rate, discount and taxable amount can disagree even when a manually entered grand total looks plausible. Keep the before-and-after field values and the source evidence supporting any correction.

Handle duplicate or uncertain registration carefully

Imagine a request is submitted and the connection drops before TallyPrime displays the result. The missing response does not prove the portal rejected the request. Check the registration status and retrieve existing details through the supported workflow before attempting another generation.

TallyHelp’s duplicate-IRN guidance points to retrieving an existing IRN when one has already been generated. Match the returned details to the intended voucher. If the information belongs to a different document, stop and investigate the identity conflict. Do not assume every duplicate message should be resolved by renumbering, deleting or issuing a credit note.

Keep the request time, portal response where available, local voucher status and retrieval result in the exception log. If support assistance is needed, provide a redacted example and exact error text. Passwords, API credentials and OTPs do not belong in that log or in a learner’s portfolio.

Finish with status and print verification

After an authorised correction, confirm that the expected document is registered and that the local voucher reflects the returned details. Compare the invoice number, date, parties and amount. Then examine the print or PDF output and use an appropriate official verification facility for the signed QR or signed invoice data.

A cancellation or later correction requires its own controlled process. Editing or deleting the local voucher does not by itself establish the corresponding portal status. Check the current rules, related records and permitted correction route before acting. This guide deliberately avoids fixed cancellation windows and turnover thresholds, which must be checked for the actual case.

Can I paste a QR image from another invoice?

No. The signed data relates to its own registered document. The printed invoice and returned registration evidence must correspond.

Does successful IRN generation settle every GST question?

No. Registration is not a general ruling on tax classification, credit eligibility or every subsequent return obligation.

What should a practice submission include?

Prepare one value-error case, one uncertain-response case and one print-only issue. For each, state the evidence required before changing data, the expected resolution and the final checks. Use fictional documents and a suitable training environment rather than sending test invoices to production.

Official documentation for further checks

• TallyHelp: generate IRN and print QR code
• TallyHelp: duplicate IRN investigation
• TallyHelp: e-invoice rejection reference
• GSTN-authorised IRIS IRP: signed invoice and QR verification

Frequently asked question

What should a beginner practise after learning TallyPrime e-invoice error checklist?

Build one small, documented exercise that uses the concepts safely, validate the result, and explain the decisions and limitations. Repeating this cycle makes learning more reliable than collecting disconnected tutorials.