How to Reconcile IRNs With Your Invoice Register

Generating an e-invoice does not automatically mean your GST invoice records are accurate. An invoice may be recorded in your billing software while its Invoice Reference Number (IRN) is missing, rejected, cancelled, or incorrectly linked. These differences can create problems during GST return preparation and customer invoice verification.

To reconcile IRN invoice register records correctly, businesses need to compare the invoices maintained in their books with the e-invoice information registered on the Invoice Registration Portal (IRP).

Regular IRN reconciliation helps identify invoices that have not been registered, incorrect transaction details, duplicate records, and differences between billing data and GST reporting.

This guide explains how to reconcile IRNs with your invoice register, which fields to compare, how to identify mismatches, and how to build a reliable monthly reconciliation process.

Key Takeaways

  • IRN reconciliation compares invoice-register records with successfully registered e-invoice information.
  • The invoice number, supplier GSTIN, financial year, and document type help identify the correct record.
  • Businesses should verify invoice values, GST amounts, buyer details, IRN status, and acknowledgement information.
  • Missing, rejected, and cancelled IRNs must be tracked separately.
  • Matching IRNs with the invoice register before GSTR-1 filing helps identify reporting differences.
  • A reconciliation spreadsheet or structured billing system can help reduce manual errors.

What Is IRN Reconciliation?

IRN reconciliation is the process of comparing the invoices maintained in a business's invoice register with the corresponding e-invoices successfully registered on the Invoice Registration Portal.

Each applicable e-invoice receives a unique 64-character Invoice Reference Number after successful registration.

The reconciliation process helps establish whether:

  • An invoice exists in the business records.
  • The invoice was required to be reported under the e-invoicing system.
  • An IRN was successfully generated.
  • The correct IRN is linked to the corresponding invoice.
  • Invoice values and GST amounts match.
  • The IRN is active or cancelled.
  • The invoice details are appropriately reflected in GST reporting.

For example, a business may have 250 invoices in its sales register, but only 220 of those transactions may require IRNs. The remaining 30 may be outside the applicable e-invoicing scope.

The objective is not to generate 250 IRNs automatically. It is to identify the invoices requiring registration and confirm that those invoices have valid IRN records.

Understanding the distinction between these identifiers is important. For additional details, read IRN vs Invoice Number: What Is the Difference Under GST?.

Why Should Businesses Reconcile IRNs With Their Invoice Register?

Invoice register reconciliation helps businesses keep their e-invoice records aligned with their accounting and GST reporting data.

Without regular reconciliation, discrepancies can remain unnoticed until a customer raises an issue or the business begins preparing its returns.

1. Identify invoices without IRNs

An invoice may be created in accounting software but never successfully reported to the IRP.

This can happen because of:

  • Internet or API connectivity failures
  • Incorrect GSTIN details
  • Invalid invoice information
  • Rejected JSON submissions
  • Incomplete approval workflows
  • Manual oversight

For invoices requiring e-invoicing, these exceptions need prompt investigation.

2. Detect incorrect invoice information

An IRN may have been generated successfully even though the information submitted does not match the latest accounting record.

For example, the invoice register may show a taxable value of ₹80,000, while the registered e-invoice contains ₹75,000.

The difference must be investigated rather than assuming either record is automatically correct.

3. Prevent duplicate and incorrectly linked records

Duplicate entries may be created in accounting systems through repeated imports, manual entries, or incorrect invoice numbering.

Reconciliation helps identify whether one genuine registered document has been linked to multiple local records.

4. Improve GST return accuracy

Applicable e-invoice data is transferred from the IRP to the GST system for auto-population in GSTR-1.

However, businesses should still compare this information with their sales records before filing.

Regular GSTR-1 reconciliation helps identify missing documents, incorrect values, amendments, and cancelled transactions requiring review.

5. Maintain an organised audit trail

A documented reconciliation process helps the accounts team explain how invoice records were verified, what differences were identified, and how those differences were resolved.

What Data Is Required to Reconcile IRNs?

Before beginning e-invoice reconciliation, collect the relevant information from your billing or accounting software and the available IRP records.

1. Invoice register data

Your invoice register should contain:

  • Supplier GSTIN
  • Financial year
  • Invoice number
  • Invoice date
  • Customer name
  • Customer GSTIN, where applicable
  • Document type
  • Taxable value
  • CGST, SGST, IGST and cess, where applicable
  • Total invoice value
  • Invoice status
  • IRN, where already stored

2. IRP registration data

Use the available registered e-invoice data, including:

  • IRN
  • IRP acknowledgement number
  • Acknowledgement date
  • Invoice/document number
  • Document date
  • Document type
  • Supplier GSTIN
  • Buyer GSTIN
  • Taxable value
  • GST amount
  • Invoice total
  • Signed QR code information
  • Cancellation status, where available

These details may be available through your connected e-invoicing software, stored IRP responses, or applicable portal download facilities.

3. GSTR-1 data

For return-level verification, review the relevant GSTR-1 records, including available auto-populated e-invoice information.

The GST Portal provides an option to download e-invoice details in Excel format from the GSTR-1 interface.

The downloaded information can support a further comparison between registered e-invoices and outward-supply reporting.

How to Reconcile IRNs With Your Invoice Register: Step-by-Step

The following process can be used by businesses maintaining invoice records in Excel, accounting software, or an ERP system.

Step 1: Export your invoice register

Start by downloading the sales invoice register for the reconciliation period.

For example, if you are reconciling September transactions, extract the relevant invoices for September and separately consider any documents registered or cancelled outside the month that affect those records.

Ensure the register includes:

Field

Example

Financial year

2026–27

Invoice number

INV/2026/101

Invoice date

05-09-2026

Customer

ABC Traders

Taxable value

₹50,000

GST amount

₹9,000

Invoice total

₹59,000

Local IRN status

Pending

The examples in this article are illustrative.

Keep the original register unchanged and work on a separate reconciliation copy.

Step 2: Identify invoices requiring IRN generation

Not every invoice in a business's sales register necessarily requires an IRN.

Review the business's e-invoicing applicability and classify documents according to the relevant GST requirements.

Typical categories include:

  • Applicable B2B tax invoices
  • Applicable export invoices
  • Applicable supplies to SEZ units or developers
  • Credit notes requiring e-invoice reporting
  • Debit notes requiring e-invoice reporting
  • Transactions outside the e-invoicing scope

Where relevant, consider exemptions and other taxpayer-specific conditions.

Create a column labelled IRN Required and mark each record as:

  • Yes
  • No
  • Review required

This prevents your reconciliation from incorrectly identifying every invoice without an IRN as non-compliant.

Step 3: Download or collect registered IRN information

Next, obtain the corresponding e-invoice records.

If your business uses an integrated billing system, export its IRN generation report or the stored registered e-invoice responses.

Where supported, retrieve the relevant information from the IRP or e-invoice portal.

For GST reporting checks, you can also review the e-invoice data auto-populated in GSTR-1.

Keep in mind that GSTR-1 data may not represent every recent IRP transaction immediately because system transmission and processing can take time.

Also, an Excel download of e-invoice information from GSTR-1 is not necessarily a complete replacement for the original IRP acknowledgement and signed response.

Step 4: Match invoice numbers with registered IRNs

This is the central part of invoice number and IRN matching.

Compare the invoice register with the registered e-invoice dataset.

Use a combination of:

  • Supplier GSTIN
  • Financial year
  • Document type
  • Document number

For detailed verification, compare the invoice date and buyer GSTIN as well.

Do not rely on invoice number alone.

For example, INV/001 may be used under different GST registrations or in different financial years. These should not be treated as the same document.

A matching record should contain the correct IRN and corresponding invoice information.

Step 5: Compare invoice values and GST details

Once the document identity matches, compare the financial information.

Check:

  • Taxable value
  • CGST
  • SGST/UTGST
  • IGST
  • Cess, if applicable
  • Total invoice value
  • Buyer GSTIN
  • Invoice date

For example:

Particular

Invoice register

IRP record

Taxable value

₹50,000

₹50,000

CGST

₹4,500

₹4,500

SGST

₹4,500

₹4,500

Total

₹59,000

₹59,000

Result

Match

Match

If the IRN exists but the taxable value or GST amount differs, classify the invoice as a value mismatch.

Before making corrections, determine whether the difference came from the original invoice, the data submitted to the IRP, or a later accounting adjustment.

Step 6: Identify missing IRNs

A missing IRN occurs when a document requiring e-invoicing has no confirmed successful registration record in the available data.

Do not assume an IRN is missing simply because the field is blank in your billing software.

First check:

  1. Whether the invoice required e-invoicing.
  2. Whether the invoice was submitted to the IRP.
  3. Whether the submission was rejected.
  4. Whether the IRN was generated but not saved in the billing system.
  5. Whether the IRN exists under a different local record.
  6. Whether the invoice is a draft, voided, or otherwise not a valid issued document.

If registration is genuinely pending, review the applicable reporting requirements and resolve the underlying issue as permitted.

For taxpayers with aggregate annual turnover of ₹10 crore or more covered by the applicable restriction, eligible e-invoice documents must be reported within 30 days of the document date.

For the detailed reporting deadline controls, refer to E-Invoice 30-Day Reporting Checklist for ₹10 Crore+ Businesses.

Step 7: Review cancelled IRNs and rejected submissions

Not every IRN-related record should be treated as active.

During cancelled IRN reconciliation, compare cancellation information with the corresponding invoice register.

Check:

  • Original invoice number
  • Original IRN
  • Cancellation date
  • Cancellation reason
  • Local invoice status
  • Whether a replacement document was issued
  • Relevant GST return treatment

A cancelled IRN should remain traceable in the records but should not be presented as an active registered invoice.

Rejected submissions require different treatment. A rejected e-invoice submission does not establish that an IRN was successfully generated.

For detailed correction guidance, see How to Handle E-Invoice Cancellation Within 24 Hours.

Step 8: Reconcile registered e-invoices with GSTR-1

After reconciling IRNs with the invoice register, complete a further review against the relevant GSTR-1 data.

The recommended process is:

Invoice Register → Registered E-Invoice Data → GSTR-1

Check whether:

  • Registered invoices appear in the relevant return records.
  • Invoice values match.
  • Customer GSTIN details are correct.
  • Credit and debit notes are included appropriately.
  • Cancelled invoices are handled correctly.
  • Duplicate or missing outward-supply records exist.

The reconciliation should identify differences before filing, wherever possible.

Step 9: Prepare an exception report

Create a separate report showing records that need investigation.

Possible statuses include:

  • Matched
  • IRN not required
  • Missing IRN
  • IRN generated but not updated locally
  • Value mismatch
  • GST mismatch
  • Cancelled IRN
  • Rejected submission
  • Duplicate local invoice
  • IRP-only record
  • GSTR-1 difference
  • Under review

Assign an owner, record the action required, and maintain a resolution date.

Step 10: Close the reconciliation and retain evidence

Once differences have been reviewed, prepare a final IRN reconciliation report.

Retain the relevant invoice-register export, registered e-invoice records, reconciliation results, and supporting explanations.

This creates a useful reference for future GST checks, audit enquiries, and internal financial reviews.

IRN Reconciliation Example: Matching 8 Invoices

Consider a distributor with eight invoice-register entries.

The accounting team exports the sales register and compares it with the registered e-invoice records.

Invoice number

Invoice value

IRN status

Reconciliation result

Action

INV-101

₹59,000

Generated

Matched

No action

INV-102

₹82,600

Generated

Matched

No action

INV-103

₹35,400

Not found

Missing IRN

Investigate submission

INV-104

₹47,200

Generated

Value mismatch

Compare source data

INV-105

₹23,600

Cancelled

Cancelled record

Review invoice treatment

INV-106

₹70,800

Rejected

Registration pending

Correct rejection

INV-107

₹11,800

Not required

Outside scope

Document classification

INV-108

₹94,400

Generated

Matched

No action

What does this reconciliation show?

Out of eight invoice-register records:

  • Three are fully matched.
  • One has no confirmed IRN.
  • One has a value mismatch.
  • One has a cancelled IRN.
  • One has a rejected submission.
  • One does not require an IRN.

The business should focus its follow-up on the unresolved exceptions rather than treating all eight invoices as failed records.

This example also shows why comparing only the number of invoices with the number of generated IRNs can produce misleading results.

Common IRN Reconciliation Mismatches and How to Resolve Them

An IRN mismatch can arise from several causes. The correct response depends on the type of difference and whether the underlying document is valid.

Mismatch

Possible reason

Recommended action

Invoice exists but IRN missing

Failed submission or missing update

Check IRP response and registration status

IRN exists but invoice missing locally

Incorrect import or deleted local record

Identify the source document and restore the audit trail

Invoice value differs

Incorrect submission or later edit

Compare original document and registered data

Wrong GSTIN

Incorrect customer or supplier master

Investigate applicable correction process

Same IRN in multiple local rows

Duplicate local entry or mapping error

Check record identity and remove incorrect links

IRN cancelled but invoice active

Status not synchronised

Review cancellation and accounting treatment

Invoice rejected by IRP

Schema or validation issue

Correct the cause and resubmit where permitted

IRN generated but absent in GSTR-1

Processing delay or data discrepancy

Review portal status and return data

Credit note not reconciled

Notes excluded from report

Include applicable note records separately

What if the invoice exists but the IRN is missing?

First verify whether IRN generation was required.

If required, check the original submission and response logs.

If an IRN was already generated, retrieve and link the correct registration information where available.

If the submission failed, investigate the rejection and follow the permitted process.

What if the IRN exists but the invoice amount differs?

Do not change the invoice register merely to force a match.

Instead, compare:

  • Original issued invoice
  • IRP-submitted document
  • Signed registration response
  • Accounting entries
  • Subsequent credit/debit notes

The appropriate correction depends on the nature of the discrepancy.

What if an incorrect IRN has already been generated?

A registered e-invoice cannot simply be edited on the IRP.

The permitted cancellation window, the underlying transaction and the applicable GST correction rules determine the next action.

For cases involving returns, price reductions, or subsequent adjustments, read E-Invoice Cancellation vs Credit Note: When to Use Each.

How to Perform IRN Reconciliation in Excel

Businesses managing a moderate number of invoices can use Excel or a spreadsheet for IRN reconciliation in Excel.

Create three worksheets:

Sheet 1: Invoice Register

Invoice key

Invoice number

GSTIN

Invoice total

IRN required

29ABCDE1234F1Z5|2026-27|INV|101

INV-101

29ABCDE1234F1Z5

₹59,000

Yes

Sheet 2: IRP Data

Invoice key

IRN

Invoice total

IRN status

29ABCDE1234F1Z5|2026-27|INV|101

Sample IRN

₹59,000

Active

Sheet 3: Reconciliation

Use formulas to look up the relevant IRN and compare invoice values.

Formula to retrieve the IRN

Assuming the invoice key appears in cell A2 and the IRP Data sheet contains invoice keys in column A and IRNs in column B:

=XLOOKUP(A2,'IRP Data'!A:A,'IRP Data'!B:B,"Not Found")

Formula to compare invoice totals

Assuming invoice-register value is in C2 and the matched IRP value is in D2:

=IF(ROUND(C2,2)=ROUND(D2,2),"Matched","Value Mismatch")

Formula to identify missing IRNs

Assuming column B contains whether an IRN is required and column E contains the IRN:

=IF(B2="No","Not Required",IF(E2="Not Found","Investigate IRN","Review Match"))

These formulas are simplified examples.

For production reconciliation, use a properly constructed composite invoice key, check for duplicate keys before lookup, verify cancellation status, and compare individual tax components rather than only invoice totals.

Important: A spreadsheet match does not independently confirm that an IRN is active or legally valid. Use authenticated IRP information and appropriate status checks.

IRN Reconciliation vs GSTR-1 Reconciliation: What's the Difference?

Although related, these two checks serve different purposes.

Aspect

IRN reconciliation

GSTR-1 reconciliation

Main purpose

Match invoices with registered e-invoice information

Match outward supplies with GST return data

Primary records

Invoice register and IRP data

Sales register and GSTR-1

Key identifier

Invoice identity and IRN

Invoice details and reporting tables

Main errors identified

Missing IRNs, incorrect mapping, cancelled records

Missing supplies, incorrect tax values, reporting differences

Timing

Daily, weekly, or before filing

Before applicable return filing

Key outcome

Verified e-invoice register

Reviewed outward-supply reporting

Businesses should not treat these processes as substitutes for each other.

An invoice may have a valid IRN but still require review in GSTR-1. Similarly, recording invoice details in a GST return does not necessarily resolve missing e-invoice registration for a document that required an IRN.

How Often Should Businesses Reconcile IRNs?

The appropriate frequency depends on invoice volume, transaction complexity and applicable reporting requirements.

Business situation

Suggested reconciliation frequency

Low-volume invoicing

Weekly, with a review before filing

Regular B2B invoicing

Daily exception checks and monthly closure

Large invoice volumes

Daily or automated matching

Multiple branches or GSTINs

Daily or frequent GSTIN-wise review

High volume of cancellations/notes

Daily exception monitoring

A practical workflow is:

Daily: Review rejected submissions, missing acknowledgements, and recent cancellations.

Weekly: Compare newly issued documents with registered IRNs and investigate unmatched records.

Before return filing: Complete invoice-register, IRP-data, and GSTR-1 reconciliation.

For faster resolution, businesses should not leave missing IRN investigations until the end of the month, especially where reporting restrictions apply.

Best Practices to Prevent IRN Reconciliation Errors

1. Maintain consistent invoice numbering

Use a controlled invoice numbering process and avoid duplicate document identities.

Where multiple GST registrations or branches exist, maintain clear document identification.

2. Validate invoice data before submission

Review supplier and buyer GSTINs, invoice dates, document types, taxable values and GST amounts.

The GST Invoice Mandatory Fields Audit Checklist Under Rule 46 provides a detailed guide to invoice-field verification.

3. Save IRN responses immediately

A successfully generated IRN should be linked to the correct invoice record.

Store acknowledgement details and relevant signed response information as part of the document history.

4. Monitor rejected submissions separately

Rejected invoices should not appear as successfully registered.

Maintain error logs and ensure corrections are reviewed.

5. Control manual invoice edits

Restrict changes to invoices after successful IRN generation.

Where a correction is required, follow the applicable cancellation, credit/debit note or return-amendment procedure rather than silently changing the original invoice record.

6. Review credit and debit notes

Include credit notes and debit notes requiring e-invoice reporting in your reconciliation process.

Use their correct document types and separate numbering records.

7. Maintain an exception tracker

Track unresolved differences with an owner, reason, status and resolution date.

An exception report makes it easier to identify recurring issues across teams or branches.

How GimBooks Can Help Manage IRN and Invoice Records

Maintaining invoice registers, customer details, GST calculations, and e-invoicing data across separate systems can increase manual reconciliation work.

Using structured GST billing and e-invoicing workflows can help businesses keep transaction records more organised.

With GimBooks, businesses can manage GST-related billing workflows, including:

  • Creating GST invoices
  • Maintaining customer and product information
  • Recording invoice values and tax details
  • Managing applicable e-invoicing workflows
  • Maintaining billing and transaction records
  • Preparing GST-related reports

For businesses that generate IRNs, linking registered e-invoice information with the corresponding billing records can support an easier reconciliation process.

Before selecting or configuring a reconciliation workflow, confirm which IRN exports, status updates, exception reports and integrations are supported by your software setup.

The goal is to reduce repeated manual entry while keeping appropriate checks and reviews in place.

Monthly E-Invoice Reconciliation Checklist

Use this e-invoice reconciliation checklist before completing your GST return review.

Invoice register

  • Sales invoice register is updated.
  • Invoice numbers and financial years are verified.
  • Supplier GSTIN and document types are correctly recorded.
  • Invoices requiring IRNs are identified.
  • Credit and debit notes are included where applicable.

IRP records

  • Successfully generated IRNs are available.
  • IRNs are linked to the correct invoice records.
  • Acknowledgement details are retained.
  • Missing IRNs are investigated.
  • Rejected submissions are reviewed.
  • Cancelled IRNs are correctly identified.

Value and GST matching

  • Buyer GSTINs are compared.
  • Invoice dates are verified.
  • Taxable values match.
  • CGST, SGST/UTGST and IGST are compared.
  • Total invoice values are reviewed.
  • Any mismatches are documented.

GST return review

  • Relevant GSTR-1 e-invoice data is checked.
  • Missing outward-supply records are investigated.
  • Duplicate reporting is reviewed.
  • Credit/debit note treatment is checked.
  • Reconciliation exceptions have assigned owners.
  • Final reports and supporting records are retained.

Frequently Asked Questions

How do I reconcile an IRN with an invoice register?

To reconcile an IRN with an invoice register, export your invoice records and registered e-invoice details, match documents using the appropriate invoice identity, verify IRN information, compare transaction values and GST amounts, and investigate missing or cancelled records. Then review the relevant GSTR-1 information.

What is IRN reconciliation in GST?

IRN reconciliation in GST involves matching invoices maintained in accounting records with their corresponding e-invoice registration information. It helps identify missing IRNs, incorrect mappings, cancelled documents and value differences.

Can one invoice have multiple IRNs?

An individual document identity should not have multiple independently valid IRNs generated through repeated registration. If multiple IRNs appear against what your accounts team considers a single invoice, investigate whether different document numbers, types, GSTINs or financial years were used, or whether the records were incorrectly mapped.

How can I check whether an IRN is valid?

Use the appropriate official e-invoice verification functionality or authenticated registered e-invoice information, including the signed QR code, where applicable. A locally stored IRN value alone is not sufficient to establish its current status.

Why is an IRN missing from my invoice register?

An IRN may be missing because the invoice was not registered, the submission was rejected, the system failed to save the IRP response, or the transaction was outside the applicable e-invoicing scope. Check the original submission status before taking corrective action.

Can I reconcile IRNs in Excel?

Yes. Businesses can use Excel to compare invoice-register exports with IRP registration data through matching keys, lookup formulas and difference checks. However, Excel reconciliation should also account for cancellations, duplicate records and IRN applicability.

Does generating an IRN automatically update GSTR-1?

Applicable e-invoice details are transmitted from the IRP to the GST system for auto-population in specified GSTR-1 tables. Processing may take time, and businesses should independently verify the populated records before filing.

What happens if the IRN amount and invoice-register amount do not match?

Review the original issued invoice, registered e-invoice data and accounting entries to determine the cause. Depending on the error, the appropriate action may involve accounting correction, an applicable cancellation, credit/debit note or GST return amendment.

Should cancelled IRNs be included in reconciliation?

Yes. Cancelled IRNs should remain part of the audit trail, clearly marked as cancelled. They should not be treated as active registered invoices.

Is IRN reconciliation mandatory every month?

GST e-invoicing rules impose applicable document-registration and reporting requirements, but the operational frequency of an internal IRN-to-register reconciliation is a business control rather than a universal standalone monthly statutory filing requirement. Regular reconciliation is advisable to identify discrepancies early.

Conclusion

Learning how to reconcile IRN invoice register records helps businesses maintain consistency between GST invoices, registered e-invoice data and outward-supply reporting.

An effective reconciliation process begins with identifying invoices that require IRNs, matching them with authenticated registration records, comparing transaction values, and resolving missing, rejected or cancelled documents.

Businesses should also review the relevant GSTR-1 information before filing to ensure that e-invoice registration and GST return reporting remain appropriately aligned.

By maintaining organised invoice records, checking IRN information regularly and documenting exceptions, businesses can reduce manual reconciliation errors and improve their GST compliance workflows.

GimBooks can support structured GST billing and e-invoicing workflows, helping businesses manage transaction information in one place.