GSTR-1 reconciliation with TallyPrime

“This is not a GSTR-1 JSON file. The portal gives you a .zip file. Extract it and upload the .json file inside.”

Where you see it: Accounts > GSTR-1 Reconciliation, Upload file step, in the red box This file could not be read.

This page reads only the GSTR-1 JSON file. Get it from the GST portal or the offline tool. The portal often gives it inside a .zip file, so extract it first. Excel, PDF and other returns do not work here. Nothing was read or saved in TallyPrime.

1. 1

   On the GST portal, open the Returns Dashboard, choose the financial year and month, and open GSTR-1.

2. 2

   Choose Download, then choose the JSON file.

3. 3

   If the download is a .zip file, right-click it, choose Extract All, and use the .json file inside.

4. 4

   Upload the .json file here.

5. 5

   If the message says it is a GSTR-2B file, upload it on Accounts > GSTR-2B Reconciliation instead.

It worked when: The page moves on to Check against TallyPrime.

Next time: See how to download the GSTR-1 JSON.

“Only in GSTR-1”

Where you see it: Accounts > GSTR-1 Reconciliation, Check against TallyPrime step, the Only in GSTR-1 tab and tile.

The invoice or note is in the return, but not in TallyPrime. No sale or note there has that number, and no close match was found. For B2C (small), TallyPrime has no sales for that place of supply and rate in the month. Nothing is saved in TallyPrime yet.

1. 1

   Look for the invoice in TallyPrime's sales register or Day Book. It may have another number, or a date in another month.

2. 2

   If it is there under another number, correct the number in TallyPrime (or in the return, if that is wrong), then choose Check again.

3. 3

   If a yellow box says a month had more than 1,000 sales, check these rows with care. See more than 1,000 sales.

4. 4

   If it is really missing from your books, tick it and choose Continue to save, or enter it by hand in TallyPrime.

It worked when: After you save or correct it, Check again shows it under Matched.

“In TallyPrime, not in this GSTR-1. Add it before you file, or check its date.”

Where you see it: Accounts > GSTR-1 Reconciliation, Check against TallyPrime step, the Only in books tab.

A sale or note dated in the return month is in TallyPrime, but this GSTR-1 does not report it. This tab does not save or change anything in TallyPrime.

1. 1

   Check the voucher date in TallyPrime. A sale dated in another month goes in that month's return.

2. 2

   If it belongs in this return and you have not filed yet, add it to GSTR-1 on the portal.

3. 3

   If the return is already filed, report it in the next month's GSTR-1, as your CA advises.

4. 4

   For the B2CL line, report the sale as B2C (large), or add the customer's GSTIN in TallyPrime if they are registered.

5. 5

   If the sale was entered twice in TallyPrime, cancel the extra one there, then choose Check again.

It worked when: After you download the corrected GSTR-1 and upload it, the sale shows under Matched.

““Sharma Traders” has no GSTIN in TallyPrime. GSTR-1 has 27AABCS1234F1Z5.”

Where you see it: Accounts > GSTR-1 Reconciliation, Mismatch tab, What differs column.

The sale was found by its number. But the customer's GSTIN in TallyPrime is empty or not the same as in the return. Nothing was changed in TallyPrime.

1. 1

   Find out which GSTIN is right, from the customer's GST certificate or the GST portal's Search Taxpayer.

2. 2

   If TallyPrime is wrong, open the customer ledger (Gateway of Tally > Alter > Ledger) and set the right GSTIN/UIN.

3. 3

   If the sale itself was saved with the wrong GSTIN, open the sale in TallyPrime and correct the party's GSTIN in its party details.

4. 4

   If the return is wrong and not filed yet, correct it on the portal. If it is filed, amend it in a later return.

5. 5

   Choose Check again.

It worked when: The row moves to Matched.

Next time: Keep every registered customer's GSTIN on their ledger under Sundry Debtors.

“Taxable value differs by ₹1,500.00: ₹25,000.00 in TallyPrime, ₹23,500.00 in GSTR-1.”

Where you see it: Accounts > GSTR-1 Reconciliation, Mismatch tab, What differs column, with TallyPrime's figure under each value.

The sale was found, but it does not match the return. The date, taxable value, tax, type of tax or total is different. Differences of ₹1 or less are left out. Nothing was changed in TallyPrime.

1. 1

   Open the sale in TallyPrime and compare it with the invoice you issued.

2. 2

   If TallyPrime is wrong (date, rate, sales ledger, place of supply), correct the voucher in TallyPrime.

3. 3

   If the return is wrong, correct it before filing, or amend it in a later return.

4. 4

   For a tax type difference, check the place of supply on the sale and the customer's state. Another state means IGST. The same state means CGST and SGST.

5. 5

   If TallyPrime shows tax as ₹0.00, check that the tax ledgers are under Duties & Taxes with the right type of duty (IGST, CGST, SGST/UTGST or Cess).

6. 6

   Choose Check again.

It worked when: The row moves to Matched.

“Choose a sales ledger for 18% within your state.”

Where you see it: Accounts > GSTR-1 Reconciliation, Save missing sales step, the status of each row. Rows that need a choice are not saved.

Balancely needs to know which ledgers to use, and the HSN/SAC for each rate. Then it can save the sale in TallyPrime. This is normal in the first month for each company. Nothing is saved until the row shows Ready.

1. 1

   Under Ledgers to use, choose a sales ledger for each rate. Choose one for your state and one for other states.

2. 2

   Choose your output CGST, SGST, IGST and cess ledgers. They must already be in TallyPrime.

3. 3

   Enter the HSN/SAC for each rate, 4 to 8 digits. Do this for 0% nil rated too.

4. 4

   For B2C rows, choose the Party for B2C sales, often Cash. For a rounding row, choose a Round-off ledger.

5. 5

   Under Customers, choose Use a ledger in TallyPrime and choose the ledger. Or choose Add as a new customer.

6. 6

   When the rows show Ready, choose Save.

It worked when: Every row you want shows Ready.

Next time: Balancely keeps your choices for the company. Next month needs far fewer.

“This file is for another GSTIN”

Where you see it: Accounts > GSTR-1 Reconciliation, Check against TallyPrime step, red box above the results. Continue to save stays greyed out.

The GSTIN in the file is not the one TallyPrime has for the company chosen at the top. Nothing was saved.

1. 1

   Choose the right company under Company at the top. The check starts again for it.

2. 2

   Is this the right company, with an old GSTIN or more than one registration in TallyPrime? Tick This file belongs to the company.

3. 3

   Better still, correct the GSTIN in the company's GST details in TallyPrime. Then the next check matches.

It worked when: The red box goes away, or turns amber once ticked, and Continue to save can be chosen.

“TallyPrime could not be read”

Where you see it: Accounts > GSTR-1 Reconciliation, Check against TallyPrime step, in place of the results, with Try again.

Balancely could not get your sales from TallyPrime. The title says why: TallyPrime could not be read, Too many reads at once, or The check could not finish. The text under the title gives the reason. Nothing was saved.

1. 1

   Make sure the computer with TallyPrime is on, the connector is running and TallyPrime has this company open.

2. 2

   If it says too many reads, wait a minute and close other Balancely tabs that are reading reports.

3. 3

   Choose Try again.

4. 4

   For took too long to answer, the dates come from the file and cannot be changed here. Try again when TallyPrime is not busy. If it keeps failing, tell us the month and company.

5. 5

   For The check could not finish, check your internet connection and try again in a minute.

It worked when: The tabs and tiles appear.

Next time: See Connector and TallyPrime for each connector message.

“TallyPrime was only partly read”

Where you see it: Accounts > GSTR-1 Reconciliation, Check against TallyPrime step, yellow box above the tiles.

The check covers up to 1,000 sales and 1,000 notes a month. Entries after that were not checked. So they can wrongly show under Only in GSTR-1. A document saved from here before in that month is never saved again from this check. Its note says the month was only partly read, and you cannot tick it. Nothing was saved.

1. 1

   Rows under Only in GSTR-1 may not be missing. Look for each one in TallyPrime before you save it.

2. 2

   Sales invoices are safe to save. TallyPrime stops a number it already has. The progress card counts it as already in TallyPrime.

3. 3

   Check each credit or debit note in TallyPrime by hand before you save it. Notes are not stopped this way.

“TallyPrime has GSTIN 27AABCS1234F1Z5 for “Sharma Traders”: a registered customer belongs in B2B.”

Where you see it: Accounts > GSTR-1 Reconciliation, Mismatch tab, What differs column.

The return shows this sale as unregistered (B2C large, or a note in CDNUR). But the customer has a GSTIN in TallyPrime. Nothing was changed in TallyPrime.

1. 1

   Check whether the customer is registered, on the GST portal's Search Taxpayer.

2. 2

   If they are registered, report the sale under B2B, or the note under CDNR. If it is filed, amend it. Then they get their credit.

3. 3

   If they are not registered, remove the GSTIN from the customer ledger and from the sale in TallyPrime.

4. 4

   Choose Check again.

It worked when: The row moves to Matched.

“Invoice number differs: TT/0456 in TallyPrime, TT/0465 in GSTR-1.”

Where you see it: Accounts > GSTR-1 Reconciliation, Mismatch tab, with the button Not the same sale.

No sale has the filed number. But a sale with another number has the same customer and total, on a close date. It is likely the same sale, entered with a different number. Nothing was changed in TallyPrime.

1. 1

   If it is the same invoice, correct the number in TallyPrime (or in the return) so both agree, then choose Check again.

2. 2

   If it is a different sale, choose Not the same sale. The row moves to Only in GSTR-1, and you can save it.

3. 3

   Chose it by mistake? On Only in GSTR-1, choose Show the likely match again.

It worked when: The row moves to Matched, or to Only in GSTR-1 if you said it is not the same sale.

“Number used 2 times in TallyPrime. The closest is matched here; check the others in TallyPrime, as one may be entered twice.”

Where you see it: Accounts > GSTR-1 Reconciliation, Mismatch tab, What differs column.

More than one sale or note in TallyPrime has this number. One may be entered twice. Nothing was changed in TallyPrime.

1. 1

   In TallyPrime, find the vouchers with that number in the Day Book or the sales register.

2. 2

   If one is entered twice by mistake, cancel or delete the extra one.

3. 3

   If they are different sales, give one its correct number in TallyPrime, and correct the return if needed.

4. 4

   Choose Check again.

It worked when: The row moves to Matched.

“Reverse charge: your customer pays this tax. Enter these in TallyPrime by hand.”

Where you see it: Accounts > GSTR-1 Reconciliation, the Not saved here tab, with a reason on each row and In TallyPrime as or Not found in TallyPrime under it.

Some rows are only listed here. These are reverse charge, SEZ, deemed export and export sales, amendments, and the nil-rated, exempt and advance summaries. Saving them needs details the return does not have, such as shipping bills. Nothing is saved in TallyPrime from this tab.

1. 1

   Read the reason on each row, and the line under it.

2. 2

   If it says Not found in TallyPrime, enter the sale by hand in TallyPrime. Add the shipping bill details for an export. Set reverse charge for an RCM sale.

3. 3

   For an amendment, correct the first sale in TallyPrime. Do not enter a second sale.

4. 4

   For listed twice, you need to do nothing. It is counted once.

“The sales could not be saved in TallyPrime”

Where you see it: Accounts > GSTR-1 Reconciliation, Save missing sales step, red box above the Save button.

Before the sales are saved, each new customer is added to TallyPrime. One customer could not be added. Or the whole save stopped, for example with a connector or plan message. Customers added before this stay in TallyPrime. No sales were saved this time.

1. 1

   If a customer already exists and it is the same customer, under Customers choose Use a ledger in TallyPrime and choose that ledger.

2. 2

   If it is a different party with the same name, enter a new name under Add as a new customer.

3. 3

   If that ledger has another party's GSTIN, use a new name. Or correct the GSTIN on that ledger in TallyPrime.

4. 4

   For a connector or plan message, see Connector and TallyPrime or Plans and billing.

5. 5

   Choose Save again. Customers already added switch to Use a ledger. No sale is saved twice.

It worked when: The progress card Saving sales from appears.

“Invoice "TT/0465" for "Sharma Traders" is already in TallyPrime as Sales TT/0465 dated 06-09-2026. Nothing was added. Use the correct number, or check the existing entry in TallyPrime.”

Where you see it: The progress card after Save, and each row in Accounts > Activity History.

Some rows were not saved. Already in books means TallyPrime has that invoice number, so nothing was added twice. Other failures show TallyPrime's reason. Rows shown as saved are in TallyPrime. Failed rows and rows already there added nothing.

1. 1

   For Already in books, you need to do nothing.

2. 2

   For other failures, read the reason in Accounts > Activity History. Fix it in TallyPrime, for example a missing ledger, a voucher type or a date outside the books.

3. 3

   On the progress card, choose Save failed entries again. Nothing is saved twice.

4. 4

   Or choose Check the file again and save the rows still under Only in GSTR-1.

It worked when: The rows move to Matched after checking again.

Next time: Do not use Fix & retry in Activity History for these sales. Save them again from the progress card or from this page.

“The tax as filed differs from TallyPrime’s own working (IGST ₹1,234.57, TallyPrime ₹1,234.56), so TallyPrime lists this sale as uncertain until you accept it there.”

Where you see it: Accounts > GSTR-1 Reconciliation, Save missing sales step, under a row marked Ready.

The sale is saved with the tax exactly as filed. TallyPrime also works out the tax itself. If its figure differs by even a paisa, its own GSTR-1 report lists the sale as uncertain. Nothing is saved until you choose Save.

1. 1

   Save the sale as usual. The tax goes in exactly as filed.

2. 2

   In TallyPrime, open the GSTR-1 report and find the sale under the uncertain transactions.

3. 3

   Accept it as it is, or correct the tax if the return is wrong.

4. 4

   A ledger set to another rate needs nothing. Each line has its own rate and HSN/SAC.

It worked when: TallyPrime's GSTR-1 report no longer lists the sale as uncertain.

“Sent from here, but TallyPrime did not confirm it was saved, so it is held back. Look for it in TallyPrime; if it is not there, choose Save again.”

Where you see it: Accounts > GSTR-1 Reconciliation, Only in GSTR-1 tab, in the note. You cannot tick the row until you choose Save again.

The sale was saved from here before. Either it is still being saved, or TallyPrime's answer was lost. So Balancely cannot tell if it was saved. TallyPrime may already have the sale. Nothing more is saved until you say it is not there.

1. 1

   If it says on its way, wait for it to finish. Then choose Check again.

2. 2

   Otherwise, look for the invoice in TallyPrime, in the Day Book or sales register on its date. If it is there, choose Check again.

3. 3

   If it is not there, choose Save again under the note. Then tick the row and save it.

4. 4

   If the note says the month was only partly read, there is no Save again. If the sale is really missing, enter it by hand in TallyPrime.

It worked when: The row shows under Matched after checking again.

Next time: Failed entries keep their details for 14 days. Save them again within that time. Do not use Fix & retry for these sales.

“The invoice value ₹29,500.00 is ₹100.00 away from taxable value plus tax (₹29,400.00), so it is not saved as filed. Enter it in TallyPrime with the right figures; a filed return is corrected through an amendment in a later GSTR-1.”

Where you see it: Accounts > GSTR-1 Reconciliation, Save missing sales step, a row marked Cannot be saved here.

Nothing on this page can fix this. The return has a figure that does not add up, a missing date or an unknown place of supply. This row is never saved from here.

1. 1

   Untick the row. It is not saved anyway.

2. 2

   Check the invoice on the GST portal. If the return is not filed yet, correct it there. Then download the JSON again and upload it.

3. 3

   If the return is filed, enter the right sale by hand in TallyPrime. Amend the return later if needed.

“The GSTR-1 for Sep 2026 has no sales in it.”

Where you see it: Accounts > GSTR-1 Reconciliation, Upload file step, in the red box This file could not be read.

The file has no invoices or summaries, as in a nil return. Or the month is missing because the file was edited or cut short. Nothing was read or saved.

1. 1

   Check that you chose the right month and GSTIN on the portal.

2. 2

   Download the GSTR-1 JSON again and upload it without opening or editing it.

3. 3

   If the return really has no sales, there is nothing to check.

“Saved from here as Sales no. 1042, but TallyPrime no longer has it”

Where you see it: Accounts > GSTR-1 Reconciliation, Only in GSTR-1 tab, and under the row on Save missing sales.

This sale was saved from here before. Now TallyPrime has no sale with that number, and the whole month was checked. If you tick it, it is saved again. If the month was only partly read, the note says so. Then you cannot tick the row, so nothing is saved twice. Nothing is saved until you choose Save.

1. 1

   Check in TallyPrime whether the sale was deleted, or its number changed.

2. 2

   If its number changed, correct the number. Do not save a second one.

3. 3

   If it was deleted by mistake and you need it, save it again here.