Everything Greenote does, in the order you ask about it
Not sorted by what was interesting to build. Sorted by the questions a practice actually asks before trusting software with a client's books, starting with the one that stops most people trying anything at all.
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.
Text-layer PDFs only, no OCR guesswork
A photograph of a printout has no text in it, only a picture of text. Greenote declines rather than running OCR and handing back figures that look confident and were invented.
On-premise processing, DPDP Act compliant
Processing happens on your own machine. The file is not sent to Greenote or any third party, so your firm stays the data fiduciary for client bank data under the DPDP Act, and you can answer the question a client actually asks.
Sandbox demo company with a sample statement
A guided demo company and a sample statement ship with the app, 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.
Custom column mapping, saved per bank
When a statement will not read automatically, you mark the columns on the real document and tick "remember this layout". Greenote then applies it to every future statement from that bank, 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 the app, 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 for inter-account transfers
Cash paid to yourself is a Contra and is still cash. Own-account movement booked as a payment plus a receipt inflates turnover by twice the amount, on both statements.
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.
All seven voucher types, with GST multistock invoicing
Sales, Purchase, Payment, Receipt, Contra 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.
Gateway recovery and bank ledger discovery
A dialog left open in Tally blocks the gateway completely. Greenote recovers from that quickly, waits and retries a slow company instead of reporting it to you as empty, and finds bank ledgers wherever they are filed.
Does it help the whole practice, not just one file?
Where a converter stops and software for a firm begins. These are also the features that justify more than one seat.
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.
In-app tutorials, Hindi or English narration
The full walkthrough and each step on its own, with the narration language selectable. The interface stays in English.
Draft statements resume where you left off
A statement you have not finished reading is still there when you return to it.
App 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.
In-app ticketing with file attachments
Raise a ticket from inside the app with the statement attached, and open the files we send back.
Go deeper
Map your own columns
What happens when a statement will not read, and why you only do it once
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
Compared with other tools
Including where the other tool is the better choice
The only test that settles it is your own statement
A feature list is an argument. Seven days on the banks your clients actually use is evidence. There is a demo company in the app if you would rather not start on real books.
7-day free trial, no card required. Windows, with TallyPrime or Tally ERP 9.