The month's marketplace files in. Your GSTR-1 JSON out.

Drop the reports exactly as Amazon, Flipkart, Meesho, Myntra and the rest give them. KashClick reads every line, checks it, and builds the JSON the GST portal's offline upload takes - one per GSTIN.

Create an account How it works

What you give it

Amazon MTR (B2C and B2B), and the Stock Transfer report
Flipkart Sales Report and GSTR sheets - Shopsy split out, cashback notes included
Meesho GST report (zip) with its Orders report
Myntra B2C report and its GSTR Packed / RT / RTO files
Nykaa, Eternz, Snapdeal, Shopify orders export, Kirana Club
Your own invoices too: Excel register, PDF invoices, even photos
A Vyapar GSTR-1 workbook, or last month's portal JSON

What you get

B2B, B2CL and B2CS, credit and debit notes (CDNR / CDNUR)
Table 12 HSN summary, split B2B / B2C
Table 13 documents issued, Table 8 nil-rated
Table 14 supplies through e-commerce operators, with their GSTINs
The portal's 21-sheet offline workbook as well
One JSON per registration when the files hold several

How it works

Three steps.

No new format to learn - the files exactly as the portals give them.

Client and period

Choose the client and the month. Saved clients come back with their names, operator GSTINs and HSN memory.

Drop the files

All the month's reports at once - zips, CSVs, Excel. Each is recognised by what it holds, not its name.

Review and download

Fix what it points out - a missing HSN, a wrong state, a date outside the month - then download the JSON.

Checked, not guessed

Every figure has to add up - or it is named.

HSN missing or not in the master, and the right unit (UQC)
Rows dated outside the return month
Several registrations in one upload - each gets its own return
Body = Table 12 = Table 14: the totals have to agree
TCS: your supplies against what each operator declared

Questions

Before you start

Does it file the return?

It makes the JSON the portal's offline upload takes, checked before you upload it. Signing in to the portal and the OTP stay with you.

What if the portal rejects something?

Load the portal's error report back: the refused rows open for correction, and the next JSON carries the fix.