Skip to content
LekhaPro
Returns · Payments

GST payments and challans, on the record

LekhaPro keeps a GST challan register — per-head (CGST/SGST/IGST/CESS, plus interest and late fee) cash entries — and a financial-year liability-vs-paid view, so your tax payment history and any interest or late fees are recorded and exportable.

Know what was due, what was paid, and what’s outstanding for the year, without a spreadsheet.

  • Challan register

    Record each payment per tax head, with interest and late-fee lines where relevant.

  • Liability vs paid

    A financial-year view shows liability against what’s been paid, by head.

  • History you can export

    A clean tax-payment history to Excel for your records or your CA.

What’s included

  • Challan register
  • Per-head cash entries
  • Interest & late-fee lines
  • FY liability-vs-paid
  • Tax payment history
  • Excel export

Frequently asked

Does it auto-compute interest and late fees?

You record interest/late fee per challan today; automatic computation needs filing dates and is on the roadmap.

Can I see what’s still due for the year?

Yes — the FY liability-vs-paid view shows outstanding amounts per tax head.

What exactly is included in Returns · Payments?

challan register, per-head cash entries, interest & late-fee lines, FY liability-vs-paid, tax payment history and excel export. 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 · payments handled differently here?

It rests on challan register, liability vs paid and history you can export. 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 · Payments work offline?

On the Desktop edition, yes — completely. challan register and per-head cash entries 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 · payments runs in the browser and needs a connection.

Where does Returns · Payments get its data from?

From your own posted books, not a separate register you maintain twice. challan register 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.

How does Returns · Payments affect my GST?

It feeds it directly rather than sitting alongside it. CGST/SGST and IGST are split from HSN or SAC and place of supply as each document is raised, so whatever returns · payments produces is already correct when GSTR-1, 3B and 2B reconciliation are drawn off the same books. The return matches the accounts because it was never a separate exercise.

Does Returns · Payments cost extra?

No. Returns · Payments is part of the accounting core rather than a paid add-on, so liability vs paid 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 · Payments before committing?

Yes — 14 days, no card. Test returns · payments 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 · Payments generated by AI?

None of the figures. Everything challan register 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.