The validation gate
Most tools show what the model guessed. We check the math first. Checksums, HSN, does it add up. The entry has to earn its place.
See the checks before export.
Most tools show a guess. We check it. Checksums. Directory. Does the math on the page add up.
Below is a real invoice from the test corpus. Pick a scenario and run the gates.
Core checks and reference safeguards
A printed IRN must be 64 hexadecimal characters and have value-bound transcription evidence, or a person must confirm it. Unresolved or conflicting reads stay in review. This is not IRP issuance or signature verification; invoices without an IRN remain supported.
These checks catch specific errors, not every possible misread. A valid checksum is not proof of the intended supplier, and we do not query live GST registration.
GSTIN mod-36 checksum
A GSTIN’s fifteenth character is a check digit computed over the first fourteen. Invalid checksums block automatic approval. Some wrong GSTINs still pass, so checksum validity alone cannot prove counterparty identity.
HSN directory
Every line’s HSN code is checked for format. Directory misses are warnings by default, not export blockers. Neither check proves that the supplier chose the correct classification.
Arithmetic closure
Line items must sum to taxable value; taxable value times rate must equal the taxes; taxes plus taxable must equal the grand total. The product uses a default arithmetic tolerance of ±₹1. Balanced numbers alone do not prove that every field was read correctly.
Regime consistency
Place of supply decides CGST plus SGST versus IGST. Intra-state invoices claiming IGST, or the reverse, stop at the gate instead of your books.
When something fails, your operator sees this
Held invoices reach the review queue. The scan sits beside the fields and current failure reasons. Fit or zoom the source, correct the fields and confirm to open the next exception. Confirmation is logged; it does not import into Tally.
This preview is live: the scanner misread one character of the seller's GSTIN. Correct it and watch the checksum gate flip to green.
Verified
fix the GSTIN above; the checksum gate re-runs as you type
Try it: change G to 6 in the GSTIN field.
Every field carries its evidence
EntryLedger keeps the source reference, validation results and confirmation history with the invoice. The selected-batch manifest lists invoice IDs, source references and XML hashes. It is not proof of a successful Tally import or a tax-compliance certificate.