GST accounting, built for e-commerce sellers
Selling across marketplaces means interstate GST, marketplace TCS and messy settlements. LekhaPro numbers invoices per channel, gets IGST right on interstate orders, tracks TCS, and reconciles payouts straight from your bank statement.
What gets in the way today
Interstate orders need IGST, not CGST and SGST
Shipping across states changes the tax split, and getting it wrong on volume orders causes filing headaches. Place of supply has to drive the tax automatically.
Marketplace TCS is hard to track
Platforms deduct TCS on your sales, and matching it back for credit is fiddly. It needs to be recorded as it happens.
Settlement payouts do not match sales
Marketplaces net out fees and returns before paying, so the bank credit rarely equals the sale. Reconciling by hand is slow and error-prone.
How LekhaPro fits your work
Every capability below is built in — offline-first, GST-correct by construction, and posted to a real double-entry ledger.
Per-channel invoice numbering
Keep separate numbering series for each marketplace and your own website so every channel stays cleanly identifiable.
Interstate IGST invoices
Apply CGST and SGST or IGST automatically by place of supply, with correct HSN on every order.
Marketplace TCS tracking
Record TCS deducted by platforms so the credit is captured and reflected in your returns.
Bank settlement reconciliation
Import any Indian bank statement, auto-map and dedupe entries, and use rule-based categorisation to reconcile marketplace payouts.
GST returns and GSTR-2B
Export GSTR-1 and 3B as JSON and Excel and reconcile purchases against GSTR-2B before claiming input credit.
Live stock across channels
Track on-hand quantity with low-stock alerts and COGS-based profit so you never oversell a listing.
How a typical day looks
- 1
Raise each order on its channel series, with CGST and SGST or IGST set by place of supply.
- 2
Record marketplace TCS on the sale so the credit is captured.
- 3
Import the bank statement and reconcile the settlement payout against the sales, netting fees and returns.
- 4
Watch live stock and low-stock alerts so no listing oversells.
- 5
Reconcile purchases with GSTR-2B, then export GSTR-1 and 3B to file.
Questions e-commerce sellers ask
Does it apply IGST correctly on interstate sales?
Yes. Tax is driven by place of supply, so interstate orders get IGST and intrastate orders get CGST and SGST automatically, with the right HSN on each line.
Can it help reconcile marketplace settlements?
Yes. Import your bank statement, and auto-mapping, dedupe and rule-based categorisation let you match net payouts back to sales after fees and returns.
Does it collect payments from a payment gateway?
No. LekhaPro records sales, TCS and settlements and reconciles the bank credit, but it does not collect money through a gateway. Payment collection stays with your marketplace or bank.
Is there a dedicated E-commerce Sellers pack, or is this the general product?
No dedicated pack — this trade runs on the core suite, and we would rather say so plainly than imply a vertical exists. The core covers it — per-marketplace numbering series, interstate IGST invoices and TCS tracking, with settlements reconciled from your imported bank statement. For most businesses in this line of work that is the whole requirement, but if you were expecting trade-specific screens, this is the honest answer.
Which edition should a e-commerce sellers business choose?
Either edition covers this trade, so pick on how you work rather than on features. Desktop keeps the books on your machine and runs with the internet off; Cloud puts the same books in a browser for a team spread across locations.
What does LekhaPro give a e-commerce sellers business specifically?
Per-marketplace numbering, interstate IGST invoices, TCS tracking, and settlement reconciliation from your bank statement. Concretely: per-channel invoice numbering, interstate IGST invoices, marketplace TCS tracking and bank settlement reconciliation — every one of them a working screen described in full further up this page, not a roadmap item.
What problems does this actually solve?
The ones this trade runs into rather than the ones that demo well: interstate orders need IGST, not CGST and SGST, marketplace TCS is hard to track and settlement payouts do not match sales. Each is set out with its cause above, because a business recognising its own problem in writing is worth more than a feature list it has to translate.
What does a normal day look like once it is running?
In order: raise each order on its channel series, with CGST and SGST or IGST set by place of supply., record marketplace TCS on the sale so the credit is captured., import the bank statement and reconcile the settlement payout against the sales, netting fees and returns. and watch live stock and low-stock alerts so no listing oversells.. It is one sequence in one application, which is the point — the alternative is the same day spread over a billing tool, a spreadsheet and an accountant's inbox.
Can I move across from what I use today?
Masters and opening balances come across; transaction history does not. There is no automated Tally import yet — it is on the roadmap, and we would rather say so than oversell it. You start clean on a date you choose and keep the old system as a read-only archive, which is why most businesses switch at the start of a financial year or quarter.
What happens when the internet goes down?
On the Desktop edition, nothing — billing, stock and the books run against a database on your own machine, so an outage is invisible. On Cloud, the POS till is built to keep selling when the line drops and replay what it took once it returns.
Set up your e-commerce sellers books in minutes
Offline-first, GST-correct, no card required.