E-Invoice Reconciliation: How to Match E-Way Bills
Dynamite Docs, 2026-08-14
Start with three records for one movement of goods
E-invoice and e-way bill reconciliation compares the supplier invoice, the Invoice Registration Portal record, and the e-way bill used for movement. They are related records, but they do different jobs. The invoice records the sale, the e-invoice record supplies the IRN and signed QR data, and the e-way bill records consignment and transport details.
Build one comparison row per invoice before looking for differences. Keep a source link or file name for each record. A reviewer should be able to open the exact invoice, e-invoice record, and e-way bill behind the row instead of searching through a month of PDFs.
Compare identity, value, tax and transport fields separately
Start with document identity. Compare supplier and recipient GSTINs, document type, invoice number and invoice date. Then compare taxable value, tax components and document value. Finally, check the transporter, vehicle and movement fields that belong to the e-way bill. A match in one group does not clear a difference in another.
Keep original and normalized values in separate columns. Normalization can remove spaces or standardize dates for matching, but it must not replace what the document shows. This is important for invoice numbers, vehicle numbers and GSTINs, where a small character change may describe a different record.
Use Excel or Google Sheets as an exception queue
A reconciliation sheet should answer what failed and who owns the next step. Use clear statuses such as exact match, missing e-way bill, missing e-invoice record, GSTIN mismatch, value mismatch, transport mismatch, amended, cancelled, or awaiting review. Add an owner, due date and note for each open item.
Dynamite Docs can extract the document fields into Excel, CSV, JSON or Google Sheets. It does not verify portal status, decide GST treatment, or confirm transport compliance. The operations and tax reviewers should check official records and close each exception with evidence.
Create one comparison record for the invoice and movement documents
Reconciliation works best when every commercial transaction has a stable internal record. Attach the supplier invoice, e-invoice data, and e-way bill to that record, then compare the fields that should agree. Useful keys include supplier and recipient GSTIN, invoice number and date, IRN when present, document value, place of supply, HSN or SAC context, transporter details, and vehicle number.
Do not overwrite differences during normalization. Keep the printed value, extracted value, and normalized comparison value separately. Removing spaces or punctuation from an invoice number may help a match, but the reviewer still needs to see what each source contained. The same rule applies to dates, GSTINs, and vehicle numbers.
Give every comparison an explicit result such as exact match, value mismatch, identity mismatch, transport detail mismatch, missing document, cancelled document, or needs review. That turns reconciliation into an exception queue and prevents a partial match from looking complete.
Separate identity, value, tax, and transport checks in the report. A correct invoice reference does not prove the taxable value agrees, and a matching value does not prove the vehicle or transporter detail belongs to the shipment. Field-level results let operations and tax reviewers resolve the part they own without reopening every document.
Handle amendments, cancellations, and timing differences without losing history
The documents may not arrive together. An invoice can reach accounts before transport details are complete, and later corrections can change the record the team first reviewed. Store versions and timestamps instead of replacing the earlier file. When a value changes, show the old value, new value, source, and reviewer decision.
Use field-level rules for high-risk differences. GSTIN and invoice-reference mismatches should stop automatic acceptance. A vehicle update may follow a different review path from a taxable-value change. Duplicate IRNs or reused invoice numbers should remain visible until a person resolves them. The result is a controlled matching file, not a claim that every document proves the transaction by itself.
Close the batch with counts for complete matches, open exceptions, missing documents, cancellations, and amendments. Reconcile the value of the matched set to the accounting register, then preserve the comparison file and source versions used for review. A later correction should create a new result rather than silently changing the closed report.
- Confirm document identity before comparing amounts.
- Keep missing and cancelled documents in the exception report.
- Record amendments as new versions with their source time.
- Require review before sending mismatched values downstream.
Frequently asked questions about e-invoice and e-way bill matching
- What should be the primary match key? Use the strongest available combination of GSTIN, invoice reference, date, and IRN, then confirm values and movement details.
- Should punctuation differences create an exception? Preserve the originals, but use normalized helper values to distinguish formatting differences from real identity mismatches.
- Can document matching replace GST review? No. It exposes agreements and differences. A qualified reviewer decides their tax and operational treatment.
Reconcile one shipment before applying the rules to a batch
Choose a transaction with an invoice, e-invoice record, and e-way bill. Compare identity, value, tax, and transport fields separately, then record the reason for every difference. Expand the workflow only after the reviewer can retrieve each source and understand the final status without reconstructing the match by hand.
Sources checked for this note
Related workflow: GST e-invoice data extraction and IRN verification.
Keep reading
Try it yourself. Upload a PDF, scan, or image and let Dynamite Docs infer the schema.