Most Indian businesses do not start with a full accounting system — they start with GST filing, because that is the part with a due date attached to it. Invoices, marketplace sales, and bank statements come first; a proper set of books tends to arrive later, often stitched together in Tally or Excel after the fact. This article lays out where accounting software for Indian businesses using OneBooks GST stands today, and the roadmap for turning existing GST and invoicing data into full double-entry books.
Everything under "roadmap" below is planned, not yet available. We are describing it here so you can see how it will connect to the GST workflow you may already be using, and plan your own systems accordingly.
What's already available today
| Capability | Status |
|---|---|
| GST invoicing and direct invoice entry, with invoice PDF and templates | Available today |
| Marketplace sales import (Amazon, Flipkart, Meesho, Myntra, AJIO, JioMart, Excel/CSV) | Available today |
| GSTR-1 preparation (B2B, B2C, credit/debit notes, HSN summary, validation) | Available today |
| Bank statement upload and parsing with ledger mapping | Available today |
| Exports to GSTR-1 JSON, CSV, Excel, Tally XML, Miracle, Profit NX | Available today |
| Chart of accounts, vouchers, ledgers | Roadmap |
| Receivables and payables tracking | Roadmap |
| Profit and loss statement, balance sheet | Roadmap |
In other words: the data capture layer — invoices, marketplace sales, bank transactions — already exists inside OneBooks GST. What is planned is the layer above it that turns that data into a formal set of books.
Why GST-first businesses eventually need full books
A business that only files GST returns can operate for a while without formal accounting, but it runs into limits: banks and lenders ask for a profit and loss statement and balance sheet before extending credit, investors expect proper books before due diligence, and even simple questions like "what do my customers owe me right now" become hard to answer reliably from invoices alone. Accountants often end up rebuilding books from scratch in Tally each year, using the same GST data that was already sitting in the filing system, just in a different format.
The roadmap: from invoices to full double-entry books
Chart of accounts (planned)
A structured chart of accounts — assets, liabilities, income, expenses, and equity, each broken into ledger heads — is the foundation every other planned feature builds on. The intent is to offer sensible defaults suited to Indian GST-registered businesses, with room to customise as needed.
Vouchers and ledgers (planned)
Every transaction — a sale, a purchase, a payment, a receipt, a journal adjustment — is planned to post as a voucher that flows into the relevant ledgers automatically, rather than requiring manual double entry for information the system already has (an invoice you raised, a bank transaction you imported).
Receivables and payables (planned)
Tracking what customers owe you and what you owe suppliers, tied back to the actual invoices and bills raised, is planned as a natural extension of the invoicing you already do today.
Profit and loss statement and balance sheet (planned)
Once vouchers, ledgers, and the chart of accounts exist, standard financial statements can be generated directly from that data rather than compiled separately at year-end.
What "roadmap" means in practice
It is worth being direct about what calling something a roadmap item means: it describes intended direction, not a committed release date. Priorities on any product roadmap can shift based on regulatory changes, customer feedback, or engineering realities that only become clear once a feature is being built. If full accounting is a hard requirement for your business right now, plan around your existing setup rather than around a roadmap timeline, and treat this article as a signal of direction rather than a commitment.
How this connects to what you already use
The design intent is that none of this roadmap work should mean starting over. Today's GSTR-1 automation already classifies your sales by B2B, B2C, and HSN — that same classification is what a chart of accounts and ledger postings would draw on. Your bank statement parser already maps bank transactions to ledger heads for export — the roadmap extends that mapping into a live bank ledger inside full books rather than an export-only view. And accounting software invoicing already produces the sales records that would feed receivables tracking. The goal is that your GST work and your books stay reconciled by construction, not by a separate end-of-year exercise.
What this means for planning your systems now
If you are setting up processes today, it is worth keeping data clean at the source rather than waiting for full books to arrive: use consistent HSN codes, keep invoice numbering series tidy, and reconcile bank statements regularly. All of that groundwork carries forward directly once ledgers and statements are available, and it also makes your current GST filings more accurate in the meantime. Businesses that need full books today should continue using Tally or another accounting package alongside OneBooks GST's exports, rather than waiting on the roadmap.
A practical checklist while you wait
| Action today | Why it matters once books are available |
|---|---|
| Use one consistent invoice numbering series per GSTIN | Vouchers and ledgers will need a clean, gap-free source to post from |
| Reconcile bank statements against invoices every month, not just at filing time | A live bank ledger is only as reliable as the reconciliation habits feeding it |
| Record purchases and expenses with correct GST treatment even if not yet in a formal ledger | Reduces the volume of retrospective correction needed when a chart of accounts is set up |
| Track outstanding customer payments manually if needed | Gives you a baseline to migrate into receivables tracking rather than starting from zero |
None of this is wasted effort even if the roadmap timeline shifts — clean GST data is valuable on its own, independent of when full accounting features arrive.
Inventory-heavy businesses should also look at the parallel inventory software roadmap, since stock valuation and cost of goods sold are two areas where inventory and accounting roadmaps are planned to connect directly.
Frequently asked questions
Is full double-entry accounting available in OneBooks GST today?
Not yet. Chart of accounts, vouchers, ledgers, receivables and payables, and financial statements are on the roadmap and not currently shipped. Today's platform covers GST invoicing, GSTR-1 preparation, marketplace imports, and bank statement parsing.
Will I need to re-enter my data once full accounting launches?
The intent behind the roadmap is to build on data you are already capturing — invoices, marketplace sales, bank transactions — rather than require a fresh start, though the exact migration path will be detailed closer to release.
What should I use for books in the meantime?
Continue using Tally or another accounting package for full books, using OneBooks GST's Tally XML, Miracle, or Profit NX exports to bring GST-related data across without re-entry.
Will the chart of accounts be customisable?
The plan is to provide sensible defaults suited to Indian GST-registered businesses with room to customise, though final configurability will be confirmed as the feature is built.
How does this roadmap relate to the inventory software roadmap?
They are planned to connect, particularly around stock valuation feeding into cost of goods sold on the profit and loss statement, but each is being described here as a separate roadmap since they ship independently.
