May is not the month to replace the books
GST season in an Indian SME is a calendar fact, not a software mood. Returns have dates. Notices have dates. The person who files is already working evenings. That is a poor week to discover that invoices now live in a new screen nobody has reconciled, or that the auditor’s usual export is gone because someone called the old stack legacy.
We still see the same pitch every April and May: replace everything before the quarter closes. The pitch sounds tidy. The building is not tidy. Sales are in a group chat. Dispatch is a printed list. Opening stock is a branch workbook. Tally is the only place where a number has a legal meaning. If you swap that last piece while the first three are still informal, you have not modernised accounts. You have moved the argument into the return.
Keep Tally. Automate the retype. That sentence is the useful project in May. A fuller custom ERP can come later, as a phased operations layer, once finance will look at a screen without treating it as a rumour. Filing season is when you earn that look, or lose it for a year.
What the spreadsheet is actually doing
Call it a workbook, a control sheet, a MIS file, a “final_final” tab. It is doing three jobs that software vendors like to pretend are one job. It is a scratchpad for people who do not have a form. It is a reconciliation layer between systems that disagree. It is a political document: the version the owner trusts when two other versions exist.
In a Kochi or Thrissur trading office that usually means this: the salesperson confirms a rate on WhatsApp, someone types a bill in Tally, someone else updates a stock sheet if they remember, and on the 8th or the 11th accounts builds a third sheet to see whether outward supply matches what the portal will accept. None of those people is lazy. They are protecting themselves from a number they cannot defend.
If you only “digitise the spreadsheet”, you often copy the political document into a prettier grid. The scratchpad and the reconciliation stay. Staff keep a side file because the pretty grid cannot take an exception. That is how you spend a project and still run accounts on Excel in May. The honest first question is which of the three jobs you are removing, and which one you are leaving on purpose.
Photograph the workbooks. Note who updates which tab, and which tab is the one people actually trust when a notice arrives. You will find item codes that collide, a branch book that never got last month’s returns, and a rate list that lives in someone’s downloads folder. That pile is the process. A workshop that ignores it produces empty screens and a very busy May.
Keep Tally
Accounts know Tally. Auditors know Tally. Many CAs will not open your new dashboard with the same comfort they open a company in Tally. That is not conservatism for its own sake. The books are how you stay legal. Ripping them out so a new product can “do GST” is how implementations fail in the first filing cycle.
Tally is also already paid for, already trained, already full of history. A May project that asks finance to relearn posting while they are matching e-invoices is asking them to take a career risk for your demo. They will not. They will export, they will retype, and they will tell the owner the new system is not ready. They will be right.
Keeping Tally does not mean you are stuck in 2014. It means the system of record for the books stays where trust already lives. Operations — orders, jobs, stock movements, the thing Tally will never grow — can sit beside it. That split is normal. It is how a lot of Indian manufacturers already live, except the “beside it” part is a spreadsheet and a junior who retypes until midnight.
If you later want the books to move, that is a separate decision with a separate calm month. Do not attach it to GSTR-1. Do not attach it to a festival. Do not attach it to a vendor’s quarter-end target. Finance’s job in May is a return that matches reality. Help that job or get out of the way.
Automate the retype
The retype is the expensive, quiet work. An invoice that already exists as an order is typed again so Tally has a voucher. A dispatch that already happened is typed again so stock looks right. A job that already has a value is typed again so GST has a taxable amount. Each retype is a chance to change a HSN, a place of supply, a credit note that never made it, a round-off that only one person understands.
Automation here is not a robot clicking Tally. It is a single operational fact that becomes the voucher. Order confirmed, dispatch confirmed, invoice posted — same quantities, same GSTIN, same document number you can find later. That is business process automation in the sense that matters to accounts: the path is official, exceptions have a place, and nobody is “just updating the sheet for this month”.
What you automate first is the path that already has a paper or a chat trail you can check. Outward invoices from confirmed orders. Credit notes that follow a written complaint. Stock out on dispatch, not on a weekly guess. What you do not automate first is the clever consolidation the owner does in their head on Sunday night. Encode that too early and you have encoded a guess. Leave it as a review step until the simple path is boring.
A nightly or on-post push into Tally — or a voucher file accounts import and then look at — is a phase, not a failure. Accounts should still see the voucher. They should still be able to reject it. Trust is not “the software posted while we slept and we hope the portal agrees”. Trust is “we can walk from this line in Tally back to the order without ringing three people”.
What finance will trust in May
Finance will trust a list they can tick. Yesterday’s invoices, today’s invoices, a total that matches Tally, a total that matches the portal after the usual timing lag. They will trust a document number that does not change because a developer “cleaned up” the series. They will trust a GSTIN that came from the customer master, not from whoever typed fastest.
They will not trust a dashboard that says revenue is healthy while the GSTR-1 draft is short. They will not trust a live stock number that cannot explain last week’s physical count. They will not trust a vendor who says “GST is handled” and then asks accounts to map HSN in a spreadsheet the night before filing. That spreadsheet is the old job with a new logo.
What they will sign, if you are lucky, is a parallel run: both paths, every day, for a stretch you agreed in writing. The new path produces the voucher or the import. Tally still files. When the numbers match without a hero in accounts, you can talk about switching the retype off. Switching off is a management act. Software cannot retire a workbook people still need for the notice that arrived this morning.
Bring the CA into that definition of done. Not for a product demo. For the export they already use, the way they want credit notes shown, the place of supply cases that already bit you last year. If the CA cannot find last Tuesday’s invoice the way they found it in April, you have not gone live. You have created a second archive.
A table accounts can use in a meeting
| Proposal | What May actually needs | What to do instead |
|---|---|---|
| Replace Tally before the return | Books that file without a new login | Keep Tally; integrate or import |
| A full ERP go-live this month | One path that matches yesterday | One slice, parallel run |
| GST “module” with no masters | HSN, GSTIN, place of supply that survive audit | Clean masters first, then post |
| Dashboard instead of a voucher | A document finance can open | Same facts, same number, in Tally |
| Staff will “pick it up in a week” | Evenings already booked for filing | Do not train a new book in May |
If a slide cannot survive that table, it is not a May project. Park it until July. The business will still be there. The return will not wait.
What not to buy this month
Do not buy a package comparison as if choosing a logo will file GSTR-3B. That meeting belongs in a calm quarter, and it is a different article than this one. Do not buy a rewrite of Tally that promises to be friendlier and then needs six weeks of master data you do not have. Do not buy a chatbot that “explains GST” to the owner while the junior is still copying invoices.
Do not buy a go-live date that sits on the same week as a return. Vendors who have not filed a return for a company like yours will treat that date as motivational. Your CA will treat it as a threat. Believe the CA.
Do not buy a warehouse app, a dealer portal, and a new chart of accounts as one purchase order because May felt urgent. Urgency is real. The bundle is how you get three half-used systems and the same spreadsheet, still running accounts, still open at midnight.
If you need a name for the work that is allowed in May, call it a first operations slice with a Tally path. That work lives under ERP solutions when it is more than a macro, and under automation when it is “this fact, entered once”. It does not live under “we are changing how the company is accounted for, starting Friday”.
A first slice that survives filing
Sit with the person who actually enters invoices, not only with the person who bought the project. Write the path for one location or one team. Example: confirmed orders at the main godown become invoices with the HSN and GSTIN already on the customer and item. Accounts see a queue. They post or they send back. Tally remains the book. The portal remains the portal.
Migrate enough history that yesterday’s invoice can be found. Not five years. Enough that a customer dispute this week does not force a dive into the old folder. Parallel-run until the daily totals match without a hero. Then, and only then, stop the retype for that slice. Leave the other locations on the old path. That looks slow on a slide. It is how you still have a business in June.
Exceptions need a home on day one. A bill-to that is not the ship-to. A job that is part-billed. A credit that is not yet agreed. If those fall on the floor, staff invent a side sheet “just for May”. That side sheet becomes next year’s system of record. Put the exception in the queue, even if the action is “hold and call”. Official and ugly beats unofficial and clever.
Training in May is not a two-day workshop. It is one job, on the machine they already use, with the person who will be blamed if the return is late sitting next to them. If that person will not sit, you do not have a project. You have a vendor and a hope.
After the return is filed
Use the quiet week. Write down every retype that still happened. Those lines are the backlog. Some of them are software. Some of them are a missing owner for customer GSTIN. Some of them are a salesperson who still confirms rates in a group because the official price list is a rumour. Do not automate the rumour. Fix the list, then encode it.
That is also when a wider custom ERP conversation becomes honest. You now know which facts were entered once and which still needed a hero. You know whether Tally integration is a file, an API, or a junior with a checklist. You know whether the spreadsheet was a scratchpad or the real political document. Budget the next slice from those sentences, not from a brochure module list.
Automation that does not retire a retype is decoration. Automation that retires a retype and keeps the books familiar is how finance starts to trust the next screen. We would rather ship that in May than a new chart of accounts and a smile in the demo.
If you want help drawing that line — Tally stays, this path is official, this workbook can die after the parallel run — that is the shape of our ERP work. We will ask for the embarrassed workbooks and a day with the person who files. If those are missing, you are not buying a system. You are buying a discovery, and May is a fine month for that if you do not pretend it is a go-live.
What “done” looks like on a filing Monday
Done is not a green dashboard. Done is accounts opening Tally and seeing yesterday’s invoices without a pile of chits. Done is a credit note that exists in the same place as the original, with a reason a CA can read. Done is a stock figure you can defend when someone walks the godown, even if the figure is still maintained in a careful sheet for one more quarter.
Done is also knowing what you did not do. You did not move the books. You did not train the whole company on a new posting logic. You did not promise the portal that the new system is the only GST brain. You made one path official and left the rest of the building standing. That humility is what May rewards.
If after go-live of the slice the WhatsApp group is still the sales register, you have a reporting skin. Say so. Fix the path or admit the project was a screen. The spreadsheet that still runs accounts is not an insult. It is a measurement. Your job is to make it smaller, then unnecessary, without making the return late. Keep Tally until that measurement says you can talk about more. Automate the retype until finance is bored. Bored finance in May is a compliment.