Everything Greenote does, feature by feature
The full list first, grouped the way a year happens. Then the questions a practice asks before trusting software with a client’s books, starting with the one that stops most people trying anything at all.
33 features, in the order your year happens
One licence covers all of them. Every name below is the name you will see in Greenote, so what you read here is what you look for on the first evening.
- Import
- Map the columns
- Reports
- Assign Ledgers
- Vouchers
- Bills
- Other statements
- Quick Entry
- Masters Import
- Bank Reconciliation
- Ledger Cleanup
- Proof report
- Masters
Every month, and once a year
GST returns
5 features
- GSTR-1: Before filing
- GSTR-2B Reconciliation
- GSTR-3B Working
- GSTR-9 Working
- Supplier Filing
Quarterly, and at assessment
TDS
2 features
- Missed TDS
- 26AS and AIS
July to September
Tax audit
4 features
- Cash Limits
- MSME Payments
- Audit Warnings
- Tax Audit Papers
- Capital Gains
- Computation Sheet
- Advance Tax
- Provisional Financials
All year
Your practice
5 features
- Clients
- Fees
- My work
- Staff
- People
Home, Settings, Support, the tutorials and the licence pages are not counted above. They are in Greenote too, and none of them is a reason to buy.
Income tax returns (ITR)
Greenote does the working that goes into the return. You key the figures into your filing software or the portal; the hours of ITR prep before that are done.
26AS and AIS
Read and matched with the books, deductor by deductor, so the TDS credit you claim is the TDS that is there.
Capital gains
From Zerodha, Groww, CAMS and KFintech files: first in first out, grandfathering at 31 January 2018, short and long term, the 23 July 2024 rates and the Rs 1.25 lakh exemption on section 112A, with the totals Schedule CG needs.
Computation sheet
All the heads of income, the deductions, old and new regime side by side, presumptive income under 44AD, 44ADA and 44AE, and interest under 234B and 234C.
Advance tax
The four instalments, what the client has paid, what is still short, and the interest on it.
Notices
Income tax and GST notices on a register with their reply dates.
And what it does with a client’s books
A list of features does not say what happens when the software is unsure, when a statement will not read, or when you change your mind after posting. These are in the order a practice asks, hardest objection first.
Can I trust it with a client’s books?
This is the question that decides whether a trial happens at all, so it goes first. Every answer here is about what the software does when it is unsure, or when you change your mind.
Import rollback: bulk deletion of posted vouchers
An import can be reversed by deleting exactly what Greenote wrote, and nothing else. Tally has no bulk undo of its own, which is the single reason most firms never risk automating bank entry. This is what makes a first run on a real client thinkable.
Balance continuity check on every row
Rather than importing quietly and letting you find it at reconciliation. Every vendor claims accuracy, so accuracy claims are worth nothing. Being told when the software is unsure is worth a great deal when you are the one signing.
Pre-posting voucher review and ledger approval
Every transaction is shown before a single voucher is written, and suggested ledgers are reviewed rather than applied. A row heading for Suspense shows you that before it goes.
Statements read on your own PC
Reading happens on your own machine. The statement is not sent to Greenote or to anyone else to be read, so you can answer the question a client actually asks: who holds it.
Sandbox demo company with a sample statement
A guided demo company and a sample statement ship with Greenote, so nobody has to learn on a client’s books.
Will it read MY client’s statements?
The objection that kills more deals than price. The honest answer is that most files read on their own, and for the ones that do not there is a way through that does not involve waiting for us.
Even a bank we have never seen
A bank Greenote has never met? Point at its columns once on the real document and tick "remember this layout". Greenote then reads every future statement from that bank by itself, for every client. A firm with forty clients at one co-operative bank does the work once.
User-defined bank masters
Type the name in the picker and add it. It then has its own identity and its own saved layout, so your bank list ends up matching the banks your clients actually use.
Bank-specific statement layouts
The major banks have readers written for their specific statement structure, including the ones that print four different layouts, spell out month names, or omit the year entirely.
Co-operative and regional rural bank formats
Apna Sahakari reads without any mapping at all, and Bassein Catholic is in the picker. The long tail is exactly where generic converters give up.
PDF, XLS / XLSX and CSV input
Including spreadsheets a client has already edited, statements printed newest first, narrations that wrap onto a second line, and figures that one of the statement’s own ruled lines cuts through.
Automatic OD and CC account detection
The statement says which it is, so Greenote reads it rather than putting a checkbox in front of you. This is also where sign errors used to come from.
Re-map and re-extract
If the figures look wrong, go back, mark the columns again, and the file is read afresh. The first reading is not a decision you are stuck with.
Does it remove the work I actually do?
Reading the table is the easy half. The half that takes the afternoon is deciding what every line was and who it was with, and that is what this group is about.
Counterparty extraction and ledger binding from narration
A bank line arrives as NEFT-N12345678-ACME TRADERS PVT LTD-HDFC0000123. Greenote strips the transport noise, takes the name, and binds it to a ledger that already exists in your Tally company rather than inventing a new one.
Auto-categorisation with user-defined rules
What the transaction was, and who it was with, as two independent answers. The rules ship with Greenote, and rules you write yourself apply on top of them.
Bank charge segregation from bundled withdrawals
When a bank folds its charge into the withdrawal itself, the fee reaches a charges ledger and the cash figure is the cash actually taken. Left alone it also changes the voucher type, so the fee posts as a Contra into the client’s own cash in hand instead of to an expense head.
Contra detection across the client’s own accounts
When money leaves one account and arrives in another the same client owns, it is on both statements - a debit on one, a credit on the other. Greenote checks every line against the client’s other statements, matches on amount, reference number and direction, and asks you to confirm. One Contra voucher then carries both sides and the second row is held back, so the movement is recorded once instead of twice. Cash drawn from the bank is the same rule, between Bank and Cash in hand.
Instrument number and UTR carried to the voucher
The instrument number reaches Tally with the voucher, which is what makes the reconciliation actually work later. Switch it on under Settings.
Dr / Cr derived from the running balance
The running balance decides whether a line is a debit or a credit, rather than looking for words in the narration and hoping. This is what stopped deposits posting as withdrawals.
Will it fit the Tally I actually run?
Usually asked late, and usually the thing that turns out to matter. Firms run whatever their clients run, which is rarely one version.
Version-aware voucher XML: TallyPrime, ERP 9, Silver, classic
Not one shape sent to everything. This matters more than it sounds: an older Tally does not reject an element it has never seen, it accepts the voucher and drops that element, then reports success. Building for the wrong family fails silently.
8 Tally voucher types, with GST multistock invoicing
Payment, Receipt, Contra, Sales, Purchase, Journal and both notes, including multistock invoicing.
Duplicate-free re-import: vouchers update in place
Each voucher carries a stable identifier, so running the same statement again corrects what is there instead of leaving you with two of everything.
Rejected-voucher log with cause and amounts
With the likely cause named, and the amounts that were sent recorded after the upload, rather than a count you cannot reconcile.
Waits for Tally, and finds your bank ledgers
If Tally has a dialog open, Greenote waits and retries instead of failing. A slow company is retried too, not shown to you as empty, and your bank ledgers are found wherever you have filed them.
Does it hold a whole client, not one file at a time?
A client is four accounts, a year that crosses 31 March and a report somebody else will open. This is what happens once the second statement arrives.
Party-wise Ledger Summary, in a twenty-sheet workbook
The statement rearranged around who the money moved between, with every counterparty’s transaction count, debits, credits and net position. Twenty analysis sheets in one workbook, and this is the one an audit opens first.
Append a statement to an existing report
A client’s second account joins the report that is already open rather than starting a new one.
Multi-account consolidation: combined, per bank or per file
Everything combined, split by bank, or one file at a time. A client with four accounts gives you one consolidated view instead of four disconnected ones.
Financial-year filtered import
A statement that spans a year end stops polluting the year you are filing.
Filtering, paging and bulk selection at scale
Real filters on All Entries and Assign Ledgers, paging that totals every page as well as the whole statement, filtering by voucher type, and three select-all scopes: this page, this group, or everything.
Is it pleasant to run every day?
Nobody buys software for this list. People stop using software because of it.
Performance on 100+ page statements
A 107-page statement used to take ten minutes and lock everything up. It no longer does.
Differential (delta) updates
Only what changed is downloaded, which matters on the connections a lot of Indian offices actually have.
Tutorials inside Greenote, Hindi or English narration
The full film and each of its nine chapters, with the narration language selectable.
Draft statements resume where you left off
A statement you have not finished reading is still there when you return to it.
PIN lock and one-account-per-PC activation
And can be locked from the sidebar. One account per PC, so a colleague cannot silently take over an activation.
Support tickets from inside Greenote, with file attachments
Raise a ticket from inside Greenote with the statement attached, and open the files we send back.
Watch Greenote do a practice’s whole year
The whole of Greenote, in one film
Bank statements into Tally, the rest of the books, GST, TDS and audit, income tax and the running of the office, in nine chapters.
Whoever closes the books, Greenote fits
From a one-person practice to a multi-desk office - the same tool, on your own PC, slots into how you already work. No new habits, no client data leaving the room.
Solo CA & small practice
Do a month of bank statements before lunch, on your own PC.
- One person, every client - statements in, Tally vouchers out, no junior needed
- Reads PDF, Excel or CSV from any Indian bank with no per-bank setup
- One yearly price, and no per-page or per-client counting
CA firm & multi-CA office
Standardise across every desk, on one simple bill for the office.
- Every PC produces the same clean, review-ready vouchers
- One bill for the whole office, and auto-renew only if you want it
- Manage and release each device's licence from your dashboard
Accountant, bookkeeper & article assistant
Hand the grunt work to Greenote and review, not retype.
- Juniors and articles are productive in under an hour
- Balance reconciles and flags before anything posts to Tally
- Nothing posts until a senior approves - control before commitment
Go deeper
Map your own columns
What happens when a statement will not read, and why you only do it once
Contra entries, found for you
Money moved between a client’s own accounts, posted once instead of twice
The party-wise ledger
The statement rearranged by who the money moved between
Bank statement to Excel
What the twenty-sheet workbook contains
Bank statement to Tally XML
How the voucher XML is built, and why the version matters
All 25 supported banks
Per-bank layouts, date formats and the quirks each one has
Which files it reads
PDF, Excel and CSV, with sample files you can try
Compared with other tools
Including where the other tool is the better choice
Every price and period
What a licence costs, for one person and for an office
The only real test is your own statement
A feature list is an argument. Your own clients’ banks are evidence. The free trial runs for 2 days or 10 statements, whichever comes first, and needs no card. If you need more statements to be sure, ask us and we will add them. There is a demo company in Greenote if you would rather not start on real books.
Free trial: 2 days or 10 statements, no card. Windows, with TallyPrime or Tally ERP 9.