GSTR-1, built from your books
LekhaPro assembles GSTR-1 directly from your sales — B2B, B2CS and HSN summary, with credit/debit notes and supply-type breakups — as portal-ready JSON, and can save and file it on the GSTN with EVC (OTP) through your GST Suvidha Provider.
No manual data entry into the portal: the return is computed from the invoices you already raised, correct by construction.
Computed, not keyed
B2B, B2CS, HSN summary and CN/DN are derived from your actual invoices — no re-entry on the portal.
Portal-ready JSON
Export the section-wise GSTN JSON (and Excel) any time, with or without API credentials.
File on GSTN
Save → file with EVC (OTP) → check status, directly through your GSP, with a persisted filing log.
What’s included
- B2B / B2CS / HSN summary
- Credit & debit notes
- Supply-type breakups
- Section-wise GSTN JSON + Excel
- Direct save/file with EVC via GSP
- Filing log persisted
How to file GSTR-1 with LekhaPro
- 1Record your sales invoices and any credit/debit notes for the period.
- 2Open GST → GSTR-1 and review the computed B2B/B2CS/HSN summary.
- 3Export the GSTN JSON, or click “File on GSTN” and authenticate with EVC (OTP) via your GSP.
- 4Check the filing status — the result is logged on the return.
Frequently asked
Can I file GSTR-1 directly?
Yes — with your GSP credentials, LekhaPro saves and files GSTR-1 on the GSTN with EVC and tracks the status. Without credentials it still exports portal-ready JSON.
Where does the data come from?
Entirely from the sales invoices, credit and debit notes you’ve recorded — so the return matches your books.
What exactly is included in Returns · GSTR-1?
B2B / B2CS / HSN summary, credit & debit notes, supply-type breakups, section-wise GSTN JSON + Excel, direct save/file with EVC via GSP and filing log persisted. Every item on that list is a working screen you can open in the trial rather than a capability described in the abstract.
How is returns · gstr-1 handled differently here?
It rests on computed, not keyed, portal-ready JSON and file on GSTN. The distinction that matters is that these are structural rather than cosmetic — the behaviour is built into how records are posted, not layered on as a report you have to remember to run.
Does Returns · GSTR-1 work offline?
On the Desktop edition, yes — completely. B2B / B2CS / HSN summary and credit & debit notes run against a local database on your own machine, so the screens behave the same with the network unplugged as with it connected. AI and billing are the only two things that reach out. On the Cloud edition returns · gstr-1 runs in the browser and needs a connection.
Where does Returns · GSTR-1 get its data from?
From your own posted books, not a separate register you maintain twice. computed, not keyed is built from the invoices, masters and rates already entered, so there is nothing to re-key before filing and nothing that can quietly disagree with the ledger it was drawn from.
Does Returns · GSTR-1 cost extra?
No. Returns · GSTR-1 is part of the accounting core rather than a paid add-on, so portal-ready JSON is there on the entry tier exactly as it is on the highest one. What the tiers change is reach and depth — devices, multi-branch and multi-warehouse reporting, and whether the conversational AI copilots are switched on.
Can I try Returns · GSTR-1 before committing?
Yes — 14 days, no card. Test returns · gstr-1 against your own masters and your own transactions rather than sample data: the questions worth answering here are about your business's edge cases, and a demo dataset is built not to have any.
Is anything in Returns · GSTR-1 generated by AI?
None of the figures. Everything computed, not keyed produces is computed by tested engines and would be identical with the model switched off — what AI contributes is the sentence around a number and the routing that brings the right one to your attention. Nothing it writes posts to your books without your approval.
Can I get my returns · gstr-1 data out again?
Yes. On the Desktop edition everything Returns · GSTR-1 records sits in a local database on a disk you choose, with scheduled encrypted backups you control — stopping payment leaves you holding a readable file. On the Cloud edition your data is isolated to your business by row-level security and exportable from the reports it feeds.