Invoice-by-invoice outward-supply matching against the books register — GSTR-1 reconciliation completed in under 60 seconds per return period.
For most mid-market finance teams in India, reconciling the filed GSTR-1 against the books sales register is a manual, spreadsheet-driven exercise that consumes two to three working days every return period — and still misses the exception class that triggers GST notices.
A tax analyst exports the B2B outward supplies table from the GST portal, pulls the sales register from the ERP, and attempts an invoice-by-invoice comparison across six fields — customer GSTIN, invoice number, taxable value, IGST, CGST, SGST, and place of supply — across hundreds of rows. At 200 invoices per period, even an experienced analyst needs the full two days just for the raw comparison, leaving no time for exception investigation.
Manual VLOOKUP-based matching breaks when invoice numbers carry leading spaces, inconsistent prefixes, or trailing slashes — common artifacts of Tally or Zoho Books exports. A GSTR-1 entry for INV/2025-26/0142 silently fails to match the books entry for INV/2025/0142, routing both to the "unmatched" pile without flagging the reason. The analyst has to re-examine every unmatched row manually, which can add another full day to the cycle.
A place-of-supply mismatch — where the books record the supply as intra-state (CGST+SGST) while the filed GSTR-1 treats it as inter-state (IGST) — often carries the same total tax rupee amount, making the error invisible to an analyst who compares only amounts. The misclassification means the wrong government received the tax, which is not self-correcting and requires a formal amendment under Section 37(3) of the CGST Act 2017, often with interest under Section 50 at 18% per annum.
An invoice present in the books sales register but absent from the filed GSTR-1 constitutes an unreported outward supply. If the discrepancy is not caught during the monthly or quarterly reconciliation, it accumulates through the year and surfaces only during GSTR-9 annual return preparation — when the amendment window under Section 37(3) may already have closed and the liability for interest and penalty under Section 73 or 74 has grown materially.
The interest rate per annum under Section 50 of the CGST Act 2017 on tax not paid or short-paid by the due date of the return. For a mid-market company with Rs 50 lakhs of outward supplies per month, a Rs 1 lakh under-reported taxable value generates Rs 18,000 per year in interest exposure alone — before any penalty under Section 73 or 74. Manual GSTR-1 reconciliation that misses even 0.2% of invoices each period creates compounding statutory risk that only systematic GSTR-1 reconciliation can close.
GSTR-1 sits at the intersection of four overlapping CGST / IGST provisions. An error in any one of them triggers a chain reaction: the wrong amount flows into the recipient’s GSTR-2B, their ITC claim is capped or reversed, and a reconciliation mismatch in GSTR-3B follows automatically.
Every registered supplier must furnish details of outward supplies in GSTR-1 that agree with the books of account maintained under Section 35. The return is not optional even for nil-tax periods — and any omission of an invoice that appears in the books creates a prima facie discrepancy that the department can examine under Section 61 (scrutiny of returns) without further notice.
Since the Finance Act 2021 amendment, a buyer’s Input Tax Credit is restricted to the amount the supplier has reflected in their GSTR-1 and auto-populated in GSTR-2B. If your filed GSTR-1 under-reports taxable value for an invoice, the buyer’s available ITC is correspondingly reduced — a direct cash-flow impact on your customer that can damage commercial relationships and trigger contractual disputes.
The place of supply determines whether IGST (inter-state, levied by the Centre) or CGST+SGST (intra-state, split between Centre and state) applies. Booking the wrong tax type means the revenue reaches the wrong government. This is not reversible through a credit note — it requires a formal GSTR-1 amendment and, in the case of SGST, coordination with the state tax authority where the supply was actually consumed.
GSTR-1 errors can be corrected via GSTR-1A (effective from 2024) or in any subsequent month’s GSTR-1, but only within the amendment deadline — typically the GSTR-1 for September of the next financial year or the date of filing the annual return under Section 44, whichever is earlier. Errors that miss this window are locked and can only be addressed through voluntary payment with interest, making period-by-period GSTR-1 books reconciliation a statutory control, not a best practice.
Seven deterministic passes from two Excel uploads to a signed-off reconciliation working paper — in under 60 seconds per return period, with every exception classified, quantified, and linked to the source row.
Accepts the GSTR-1 Filed extract and the books sales register as .xlsx uploads for the same tax period. Validates that both files carry the required column structure (customer name, customer GSTIN, invoice number, invoice date, place of supply, taxable value, IGST, CGST, SGST) before processing begins — returning a clear error if any required column is absent or misnamed.
Classifies each uploaded file as either GSTR-1 Filed or Books Register using column-header signals and GSTIN presence. The classification is tolerance-aware: files named generically (e.g., export_feb2026.xlsx) are classified by content, not filename. The workflow rejects ambiguous files and prompts the uploader to confirm classification manually before proceeding.
Matches every GSTR-1 row to its counterpart in the books register using a composite key of customer GSTIN + invoice number, tolerating common formatting differences (leading/trailing whitespace, inconsistent prefix separators, case differences) via normalized key comparison. Records that match on GSTIN but differ on invoice number are flagged as potential typo mismatches rather than silently dropped.
For each matched pair, compares taxable_value, igst, cgst, and sgst field-by-field. Differences within ±Rs 1 are treated as rounding artefacts and suppressed. Differences beyond Rs 1 are flagged as taxable-value or tax-amount mismatches, with the absolute rupee gap and the resulting tax differential surfaced in the exception queue — ready for a GSTR-1A amendment assessment.
Compares place_of_supply state codes between the two documents independently of tax amounts, then verifies that the IGST/CGST/SGST split is internally consistent with the declared place of supply under Section 5 of the IGST Act 2017. Any invoice where the tax-head selection conflicts with the declared state code — even if the total tax rupee amount is identical — is routed to the place-of-supply exception bucket.
Collects every GSTR-1 row with no books counterpart into a GSTR-1-only exception bucket (potential revenue-recognition gap or duplicate filing), and every books row with no GSTR-1 counterpart into a books-only exception bucket (unreported outward supply, GST notice risk under Section 37 of the CGST Act 2017). Each unmatched row includes the identifier values used for the lookup so the controller can investigate quickly.
Generates a sign-off summary table (total invoices per source, matched count, exception count by type, aggregate taxable-value difference, aggregate tax difference), a line-level Excel diff of every matched and unmatched row, and an exception queue grouped by issue type — ready for controller sign-off, GSTR-9 preparation, or a departmental scrutiny response under Section 61 of the CGST Act.
A battery of synthetic test scenarios that exercise every failure mode encountered in real-world GSTR-1 data. Each scenario produces a deterministic outcome a controller or auditor can verify in seconds.
INV/2025-26/0142 while books use INV/2025/0142 for the same transaction — a prefix inconsistency from Tally’s FY-format export that causes a silent no-match in VLOOKUP.Six seeded Excel files covering all four exception classes. Each pair exercises one failure mode end-to-end, from upload to exception queue.
Baseline pair: customer GSTIN 27ACMEA1234B1Z5 (Acme Corp Ltd), taxable value Rs 4,50,000, IGST Rs 81,000, place-of-supply 27-Maharashtra. Validates the zero-exception clean-match path and confirms inter-state IGST routing is correctly verified.
Books show Rs 4,75,000 taxable value against GSTR-1’s Rs 4,50,000 for invoice INV/2025-26/0142. The Rs 25,000 under-reporting and resulting Rs 4,500 IGST shortfall are surfaced in the exception queue with an amendment recommendation.
Total tax amount matches but the tax head is wrong. The workflow catches this class of error — invisible to a purely amount-based comparison — by comparing state codes and tax-head selection independently under Section 12 / 13 of the IGST Act 2017.
Running all six sample files in sequence exercises: the zero-exception clean match, the Rs 25,000 taxable-value under-reporting, the IGST vs CGST+SGST flip, and separate GSTR-1-only and books-only invoice scenarios. The output working paper covers all exception types on a single sheet, ready for GSTR-9 preparation or departmental scrutiny response.
A GSTR-1 reconciliation that a mid-market tax team completes in two to three working days manually — exporting portal data, aligning columns, writing VLOOKUP formulas, reviewing flagged rows — runs to completion in under 60 seconds on Cadel, with four exception classes caught deterministically on every run.
Each exception includes the specific difference amount and the relevant statutory provision — GSTR-1A amendment guidance for under-reported taxable value, interest-exposure calculation for the books-only bucket under Section 50 — so the controller can act on the output without additional research. Running the reconciliation monthly instead of quarterly reduces the compounding interest exposure from an 18% annual rate to near zero.
The reconciliation output — a sign-off summary table plus a line-level Excel diff — provides the documented management review of tax filings required under ICAI SA 500 (Audit Evidence) and satisfies the indirect-tax schedule in Form 3CD under Section 44AB of the Income Tax Act. It also provides the specific invoice-level trail a GST officer would request in a scrutiny notice under Section 61 of the CGST Act, reducing response time from days to the duration of a file retrieval.
Place-of-supply flips that carry the same total tax rupee amount are deterministically identified by comparing state codes and tax-head selection independently — the exception class that a spreadsheet-only process systematically misses. Normalized key matching also catches the invoice-number format differences common in Tally, Zoho Books, and SAP FICO exports, routing them to a typo-mismatch bucket rather than silently dropping both rows into the unmatched pile.
The questions tax controllers and finance teams ask most often before deploying GSTR-1 reconciliation software.
Two files for the same tax period: your GSTR-1 Filed extract (the outward-supplies return as filed on the GST portal) and your books sales register. Both are tabular .xlsx files with one row per invoice — customer name, GSTIN, invoice number and date, place of supply, taxable value, IGST, CGST and SGST. Drop them together; Cadel classifies each automatically using column-header signals.
It matches on the customer GSTIN and invoice number first (the primary keys), then confirms the pair describes the same transaction by checking taxable value, the tax split, the invoice date and the customer name. Invoices that line up on identifier and amounts reconcile cleanly. Invoices that match on GSTIN but differ on invoice number are flagged as potential typo mismatches rather than routed to the unmatched pile, so you can investigate the format difference rather than counting both as missing.
Four deterministic exception classes: taxable-value mismatch (difference beyond ±Rs 1 between GSTR-1 and books), place-of-supply flip (inter-state supply booked as CGST+SGST or vice versa), GSTR-1-only invoices (filed on the portal but absent from books), and books-only invoices (booked in the register but not filed — GST notice risk under Section 37 of the CGST Act 2017). Invoice-number format mismatches and date differences beyond five days are surfaced as secondary flags.
The place of supply decides the tax type: inter-state supplies attract IGST (levied by the Centre), intra-state supplies attract CGST + SGST (split between Centre and state). If your books split the tax the wrong way for the customer’s state, the total rupee amount on the invoice may still be correct — making the error invisible to any comparison that checks only amounts. But the wrong government has received the tax, which is not self-correcting and requires a formal amendment. Under Section 12 and Section 13 of the IGST Act 2017, the place of supply determines the entitled government, and correcting a misrouted SGST payment requires coordination with the state tax authority.
Taxable value and each tax head (IGST, CGST, SGST) must agree within ±Rs 1, so genuine rounding from paisa truncation in ERP exports never raises a false break. Anything beyond Rs 1 per invoice is surfaced in the Exceptions view with the field name and the rupee delta so you can see at a glance whether it is a data-entry slip or a real difference requiring a GSTR-1A amendment. Controllers can adjust the tolerance threshold in the workflow settings before running the reconciliation.
Open the Exceptions view and click the row. You see the GSTR-1 entry and the Books entry side by side with the differing field highlighted — GSTIN, taxable value, tax split, or invoice date. Correct whichever side is wrong in your source system (book a missing invoice, fix a GSTIN, re-split the tax, or file a GSTR-1A amendment for an under-reported value) and re-run. The workflow produces a fresh working paper on each run, so the exception count decreases visibly as each break is resolved.
Yes. Export the reconciled invoices and the exception list to Excel from the Inbox toolbar. The export preserves the line-level diff alongside an exception queue grouped by issue type (GSTR-1-only, books-only, taxable-value mismatch, place-of-supply mismatch), which corresponds to the reconciliation evidence expected under ICAI SA 500 (Audit Evidence) and is sufficient documentation for the indirect-tax schedule in Form 3CD under Section 44AB of the Income Tax Act.
No. Your GSTR-1 and books data is processed only to produce this GSTR-1 reconciliation and is never used to train any model. The reconciliation run stores the input files, extracted row data, and exception classifications as an immutable, timestamped audit record accessible only to users in your organization.