GSTR-1 reconciliation with TallyPrime

Match your GSTR-1 JSON with the sales register in TallyPrime: B2B, B2CL, B2CS and notes. See every difference and book missing sales with tax as filed.

Updated 29 October 2026

The GSTR-1 check reads the GSTR-1 file from the GST portal and matches it against the sales, credit notes and debit notes in TallyPrime. You see what agrees, what differs, and what is in one but not the other, before or after you file. Sales that are in GSTR-1 but missing from your books can be booked in TallyPrime, each only once.

Before you start

  • The Balancely connector is running and TallyPrime is open with the company.

  • Your customers' ledgers under Sundry Debtors carry their GSTIN.

  • The GSTR-1 JSON file for one month, from the GST portal or the offline tool.

  • Only Owner, Admin and Accountant roles can use this page. Viewers cannot open it.

How to download the GSTR-1 JSON

  1. 1

    Sign in to the GST portal and open the Returns Dashboard.

  2. 2

    Pick the month, open GSTR-1, choose Download and pick the JSON file.

  3. 3

    The JSON from the offline tool works too.

The file must be JSON and no larger than 20 MB. One file covers one return month.

Check the file against TallyPrime

  1. 1

    In Balancely, open Accounts and then GSTR-1 check.

  2. 2

    Choose the company at the top under Company. The return month comes from the file.

  3. 3

    Drop the file on Upload your GSTR-1. It is read in your browser.

  4. 4

    The check reads your customers, sales and tax ledgers, and the sales around the return month. Credit and debit notes are read when the file has notes.

  5. 5

    Read the results in the tabs. Use Check again after you correct something in TallyPrime.

If the GSTIN in the file is not the company's GSTIN in TallyPrime, nothing can be booked until you pick the right company, or confirm This file belongs to the company.

How B2B, B2CL, B2CS and notes are matched

SectionHow it is matched
B2BBy invoice number, since your sales numbers are your own. Then GSTIN, date, taxable value, tax and tax type are compared. TT/045 and tt-45 count as the same number.
B2C (large)By invoice number, the same way. A sale in TallyPrime over ₹1 lakh to another state with no GSTIN (₹2.5 lakh before 1 Aug 2024) that GSTR-1 does not have is flagged as belonging in B2CL.
B2C (small)Your sales of the month without a GSTIN are added up by place of supply and rate, and compared with each B2CS row.
NotesCredit and debit notes, registered and unregistered, by note number among your Credit Notes and Debit Notes.

Amounts within ₹1 count as equal. A sale with the same customer and total, up to three days apart but with another number, shows under Mismatch as a likely match. If it is a different sale, choose Not the same sale and it moves to Only in GSTR-1.

Read the results

TabWhat it meansWhat to do
Only in GSTR-1In the return, but not found in TallyPrime.Select the ones to book here, or enter them by hand.
MismatchFound, but the GSTIN, date, taxable value, tax, tax type or value differs, or the number is used more than once.Read What differs. Correct TallyPrime or the return, then choose Check again.
MatchedSame number, or the same B2C (small) totals, with everything agreeing.Nothing.
Only in booksSales and notes of the month in TallyPrime that this GSTR-1 does not have.Add them to the return before you file, or check their date. Notes are listed only when this GSTR-1 has notes of that kind, and only for customers with a GSTIN.
Not booked hereExports, SEZ and deemed exports, reverse charge, amendments, and the nil-rated, exempt and advance summaries.Each row says why, and whether it was found in TallyPrime. Handle it by hand.

The tiles show the count and tax for In GSTR-1, Matched, Mismatch and Only in GSTR-1. The Only in books tile shows its count and the taxable value of the file's HSN summary.

Book missing sales

  1. 1

    On Only in GSTR-1, tick the sales to book and choose Continue to book.

  2. 2

    Under Ledgers to post to, choose a sales ledger for each GST rate, within state and other state, and your output CGST, SGST, IGST and cess ledgers.

  3. 3

    Fill HSN/SAC for each rate, 4 to 8 digits. It comes from the HSN summary in your GSTR-1 where it can.

  4. 4

    For B2C sales, choose the Party for B2C sales, usually Cash. Voucher type is optional: Sales, unless you keep a separate series.

  5. 5

    Under Customers, choose Use a ledger in TallyPrime or Add as a new customer, which goes under Sundry Debtors as GST Regular with the state from the GSTIN.

  6. 6

    Choose Book with the count, for example Book 8 sales in TallyPrime. Only rows marked Ready are booked; rows that need a choice are left out. Up to 500 go in one batch.

Your ledgers, HSN codes and customer picks are saved for the company, for next month.

Uncertain sales in TallyPrime's own GSTR-1

Each rated sales line carries its GST rate and HSN/SAC, so TallyPrime includes the sale in its own GSTR-1 whatever the ledger's setup.

When a row warns of uncertain
TallyPrime works out the tax itself. If the tax as filed differs from its working by even a paisa, the row says so before you book, and TallyPrime lists that sale as uncertain until you accept it there.

What happens in TallyPrime

In GSTR-1Booked in TallyPrime as
B2B or B2CL invoiceA Sales voucher with the invoice number as filed, tax exactly as filed, and the place of supply. B2CL goes to the B2C party. If the voucher type numbers itself, TallyPrime uses its own number and keeps the filed number as the reference.
B2C (small) rowOne sales entry per place of supply and rate, dated the last day of the month, numbered like B2CS/092026/27/18, to the B2C party.
Credit noteA Credit Note: the sale and its output tax are reversed.
Debit noteA Debit Note raised on the customer: the sale and its output tax go up.
To keep the filed invoice numbers as the voucher numbers, set Method of Voucher Numbering to Manual or Automatic (Manual Override) on your sales voucher type in TallyPrime.
  • Entries already in TallyPrime are never changed or deleted.

  • A sale booked from here before is held back. If it is no longer found in TallyPrime, the row says so and it is booked again.

  • A document dated after the return month cannot be booked, since GSTR-1 cannot carry it.

  • Each entry saved in TallyPrime counts towards your plan's monthly entries. New customer ledgers created here count too. Reading and checking do not.

Only the first 1,000 sales of a month are read. If a month has more, the page warns you, and some sales may show as only in GSTR-1. Balancely refuses a sales invoice number TallyPrime already has. Credit and debit notes are not checked this way, so for a month over 1,000 sales check notes in TallyPrime before booking them.

Download the results as CSV

Choose Download as CSV to save the tab you are on. Each row has the section, GSTIN, the values in GSTR-1 and in TallyPrime, and the reasons.

Common questions

How do I reconcile GSTR-1 with Tally?

Download the GSTR-1 JSON from the GST portal, open GSTR-1 check in Balancely, pick the company and upload the file. Each sale and note is matched with TallyPrime by number, and B2C (small) by state and rate.

How do I match my sales register with GSTR-1?

The check reads the sales, credit notes and debit notes in TallyPrime and shows what is matched, what differs, what is only in GSTR-1 and what is only in your books.

Does it check B2CS sales?

Yes. Your sales of the month without a GSTIN are added up by place of supply and rate and compared with each B2CS row.

Can it book sales that are missing in Tally?

Yes. Select rows on Only in GSTR-1 and book them as Sales vouchers, Credit Notes or Debit Notes, with the tax exactly as filed.

Will it create duplicate entries?

No. Each document is booked under its own key and is held back if it was booked from here before. Balancely also refuses a sales invoice number TallyPrime already has; credit and debit notes are not checked this way.

Why does TallyPrime show a sale as uncertain in GSTR-1?

TallyPrime works out the tax itself, and if the tax as filed differs by even a paisa it marks the sale uncertain until you accept it. The booking screen warns you about such rows.

Something missing on this page? Tell us and we will fix it.