A sheet metal fabricator in Pune called me last year with a problem he could not articulate clearly. Business was growing — ₹12 crore revenue, 85 people, three product lines. But something was breaking. Quotes were slow. Material costs were always a surprise. Nobody could tell him which jobs made money and which ones bled. His accountant was producing beautiful GST returns in Tally every month. And yet, the factory felt like it was running blind.
His exact words: "My Tally is perfect. My factory is chaos."
That sentence captures a pattern I have seen in hundreds of Indian manufacturing SMEs. Tally is doing its job. The problem is that Tally's job was never to run a factory. When your manufacturing complexity grows beyond a certain point, the gap between what Tally handles and what your business needs becomes the most expensive blind spot in your operations.
This is not an article against Tally. Tally is brilliant software — arguably the most successful business software product India has ever produced. This is an article about recognising when your business has outgrown what Tally was designed to do, and what the practical path forward looks like.
What Tally does well
Before we talk about gaps, let us acknowledge where Tally excels. Understanding this is important because the answer is not to throw Tally away — it is to complement it.
Accounting and bookkeeping. Double-entry accounting, journal vouchers, ledger management, bank reconciliation — Tally handles this with a reliability that most ERPs cannot match. Your accountant knows Tally inside out. The keyboard shortcuts are muscle memory. The data entry speed is remarkable.
GST compliance. Tally was one of the first software products to handle India's GST transition comprehensively. GSTR-1, GSTR-3B, e-invoicing, e-way bills — the compliance engine is mature and well-tested. Thousands of CAs across India work in Tally. The ecosystem is unmatched.
Basic inventory. Stock in, stock out, stock summary, godown management, batch tracking for simple scenarios. For a trading company or a business with straightforward inventory, Tally handles stock management adequately.
Receivables and payables. Outstanding tracking, ageing analysis, payment reminders — Tally's receivables management is solid. Most Indian business owners check their outstanding position in Tally daily.
Statutory compliance. TDS, TCS, professional tax, and other statutory requirements are well-handled. The annual updates keep pace with regulatory changes.
For a trading business, a services company, or even a very small manufacturer with a single product line and 10-15 people, Tally might be all you need. The problems begin when manufacturing complexity enters the picture.
Where Tally breaks for manufacturers
Here is the honest assessment. These are not bugs in Tally — they are things Tally was never designed to do.
No Bill of Materials (BOM)
This is the single biggest gap. If you manufacture assembled products — a control panel, a modular kitchen, a machine frame, a food processing unit — you need to define what goes into each product. Material, sub-assemblies, fasteners, bought-out parts, labour hours, outside processing. Tally has no native BOM structure.
What factories do instead: they maintain BOMs in Excel. The sales engineer opens the Excel BOM, manually calculates material cost, adds labour and overheads as a percentage, and types the total into Tally as the selling price. The BOM and the accounting live in different systems. When steel prices change by 15% in a quarter, the Excel BOMs do not automatically update. Quotes go out at stale costs. Margins erode silently.
No production tracking
Tally cannot tell you which jobs are on the shop floor, which operations are complete, where the bottleneck is, or whether a job is running ahead or behind schedule. There is no concept of a work order, a routing, or a work centre in Tally.
What factories do instead: whiteboards, verbal updates, WhatsApp messages. The production manager knows which jobs are running because he walks the floor three times a day. This works at 20-30 jobs per month. At 100+ jobs, it breaks down. Jobs slip through cracks. Material gets consumed against the wrong order. Nobody catches the delay until the customer calls asking where their shipment is.
No quoting engine
Tally can generate a sales invoice. It cannot generate a quotation with configurable line items, BOM-driven costing, approval workflows, revision tracking, or customer-specific pricing rules. This means your quoting process — the activity that directly generates revenue — lives entirely outside your accounting system.
No job costing
This is where the real money leaks. Job costing means tracking the actual cost of producing a specific order — material consumed, labour hours spent, power, outside processing charges — and comparing it against what you estimated when you quoted. Tally tracks expenses by ledger head. It does not track expenses by job. So you know your total steel consumption last month was ₹18 lakh, but you have no idea how much steel went into Job 1247 versus Job 1253.
Without job costing, you cannot answer the most important question in manufacturing: which jobs made money and which ones lost money?
No multi-location manufacturing visibility
If you have raw material in Bhiwandi, WIP in your Pune factory, and finished goods in your Faridabad warehouse, Tally can track stock in each godown separately. But it cannot give you a unified view of material availability across locations linked to production requirements. Moving stock between locations is a manual voucher entry, not an automated transfer linked to a production plan.
No procurement linked to production
When a production order is created, the system should automatically check raw material availability and generate purchase requisitions for shortfalls. Tally has no mechanism to link a production requirement to a purchase order. Your purchase manager relies on the production supervisor walking over and saying "we need 500 kg of MS sheet for next week's jobs." This verbal chain breaks constantly.
Tally vs manufacturing ERP: capability comparison
| Capability | Tally | Manufacturing ERP |
|---|---|---|
| Double-entry accounting | Excellent | Good (often synced to Tally) |
| GST returns and compliance | Excellent | Good to excellent |
| Bill of Materials (BOM) | Not available | Multi-level BOM with costing |
| Quotation management | Basic proforma invoice only | Full quoting with BOM costing, revisions, approvals |
| Production order tracking | Not available | Work orders, routing, job status |
| Job costing (estimated vs actual) | Not available | Core feature |
| Inventory (raw, WIP, finished goods) | Basic stock tracking | Full manufacturing inventory with stages |
| Purchase linked to production | Not available | Auto-requisition from BOM |
| Shop floor visibility | Not available | Real-time job status and bottleneck tracking |
| Dispatch and fulfilment tracking | Basic delivery note | Full dispatch with packing, transporter, tracking |
| Dealer/distributor management | Basic ledger | Dealer portal, credit limits, dealer pricing |
| Mobile access | Limited (Tally on Mobile) | Full browser-based mobile access |
| Reporting and dashboards | Primarily financial | Operational + financial dashboards |
| Multi-location manufacturing | Godown-level stock only | Unified production planning across locations |
The pattern is clear. Tally covers the accounting column. A manufacturing ERP covers the operations column. The question is whether your business has reached the point where the operations gaps are costing you real money.
The 7 signs you have outgrown Tally
These are the signals I watch for. If three or more apply to your factory, you are already losing money to the gap.
1. Your quoting takes more than 30 minutes per quotation
If a sales engineer spends 30-90 minutes building each quote — pulling up BOMs in Excel, calling the workshop for current rates, waiting for the owner to approve pricing — you are losing deals to competitors who respond faster. This is not a Tally problem. It is a problem that Tally cannot solve.
2. You do not know your actual job cost until months later
If the only time you see whether a job made money is when your CA prepares the annual P&L, you are operating with a 12-month feedback loop. In that time, you may have repeated the same unprofitable job pattern fifty times. Manufacturing ERP gives you job costing in real-time — while the job is still on the floor, in time to take corrective action.
3. Material shortages surprise you
If your production manager regularly stops a job because a key material ran out — even though you thought you had stock — your inventory system is not connected to your production system. In Tally, stock levels are updated when purchase invoices are booked. In reality, material has been issued to the floor and consumed long before the invoice arrives. The stock in Tally says 800 kg. The actual usable stock on the shelf is 200 kg.
4. You have more than 50 active jobs per month
Below 50 jobs, a good production manager can keep track in his head and on a whiteboard. Above 50, things start slipping. Jobs get delayed, material gets mixed up between orders, and dispatch dates are missed. If you are above 100 jobs per month and still tracking on whiteboards, you are definitely losing orders.
5. Your sales team maintains separate Excel sheets
If every sales engineer has their own Excel file with customer details, product pricing, and pending follow-ups, your business knowledge is distributed across personal laptops. When an engineer leaves, that knowledge walks out with them. This is a CRM and quoting problem that Tally does not address.
6. You cannot answer "what is our current order book value?" in 30 seconds
If answering this question requires opening three Excel files, checking WhatsApp for recent orders, and calling the sales head, your order management is fragmented. A manufacturing ERP gives you this number on a dashboard, updated in real-time as quotations convert to confirmed orders.
7. GST reconciliation is a monthly nightmare
If your accounts team spends 3-5 days every month reconciling purchase data, stock movements, and invoice data because information sits in different systems, the reconciliation burden will only grow. When purchase, production, and sales data flow through one system, GST reconciliation becomes a verification step instead of a reconstruction project.
The emotional resistance: "We have used Tally for 15 years"
This is real. I do not dismiss it. When a factory owner or an accountant has used Tally for 15 years, it is not just software — it is identity. They know every shortcut. They can generate a trial balance in 30 seconds. Asking them to learn a new system feels like asking them to forget their own language.
The resistance typically comes from three sources.
The accountant fears becoming irrelevant. If the ERP handles GST and invoicing, what is left for them? The answer is that ERP data needs a qualified accountant more than Tally data does — because there is more data, more complexity, and more financial insight to extract. The accountant's role shifts from data entry to analysis.
The owner fears disruption. The factory is running. Orders are being delivered. Revenue is coming in. Why take the risk of changing the system? The answer is that the inefficiency is already costing you — you just cannot see it because you do not have the data to measure it.
The team fears extra work. A new system means learning new screens, entering data in new places, and dealing with the inevitable teething problems of the first month. This fear is legitimate. The answer is to implement in a way that adds value to the team's daily work, not just creates reporting for management.
The most important thing to understand about the Tally-to-ERP transition is this: Tally does not go away. In most Indian SME implementations, Tally stays as the accounting backbone. The ERP handles operations — quoting, production, inventory, job costing, dispatch — and feeds the relevant financial data into Tally. Your accountant keeps working in Tally. Your factory starts working in the ERP. They coexist.
The practical migration path
Here is the migration approach that works for Indian manufacturing SMEs. It is not a big-bang switchover. It is a gradual, low-risk expansion.
Phase 1: Quoting and sales (Week 1-2)
Start with the module that generates revenue. Move your quotation process into the ERP. Import your customer master, product catalogue, and pricing rules. Start generating quotations from the ERP instead of Excel. Tally continues handling everything else.
Why start here: the sales team sees immediate value. Quotes go out faster. Follow-ups are tracked. Conversions are measured. There is no disruption to accounting or production.
Phase 2: Inventory and purchase (Week 3-4)
Connect your raw material inventory to the ERP. Set up stock items with reorder points, link them to BOMs, and start raising purchase orders from the ERP. Goods receipt notes update stock in real-time.
At this stage, Tally still handles the purchase invoice booking and payment. The ERP handles the operational side — what to buy, when to buy, and how much is in stock.
Phase 3: Production and job costing (Week 5-8)
This is the phase that delivers the biggest value. Start creating production orders from confirmed sales orders. Track material issues against jobs. Record labour hours. Capture outside processing costs. At the end of each job, compare actual cost against estimated cost.
The first month of job costing data is usually eye-opening. Factory owners consistently discover that 15-25% of their jobs are below target margin — and the reasons are almost always fixable (material wastage, wrong estimates, untracked rework).
Phase 4: Financial integration (Week 9-12)
Once operations are stable in the ERP, set up the data bridge to Tally. Sales invoices generated in the ERP auto-post to Tally. Purchase invoices reconcile between the two systems. The accountant verifies and finalises in Tally, but no longer re-enters data.
This phased approach means that at no point is the factory running without a system. Tally keeps working throughout. The ERP adds capability incrementally, and each phase delivers standalone value.
Tally integration patterns
There are three common patterns for connecting a manufacturing ERP with Tally. Understanding these helps you evaluate vendor claims about integration.
Pattern 1: XML/JSON data export
The ERP generates voucher data (sales, purchase, journal) in Tally-compatible XML or JSON format. The accountant imports this into Tally with one click. It is not real-time, but it is reliable and the accountant retains control over what enters the books.
This is the most common pattern and works well for most SMEs. Data is typically synced daily or weekly.
Pattern 2: Direct Tally integration via API
Some ERPs connect directly to Tally Prime's API and push vouchers in real-time. This eliminates manual import but requires careful configuration to avoid duplicate entries and data mismatches.
This works well when the ERP vendor has deep Tally expertise. It breaks when either system updates and the integration has not been tested against the new version.
Pattern 3: Tally as the accounting engine
In this pattern, the ERP uses Tally as its accounting backend. All financial transactions flow from ERP to Tally automatically. The ERP handles operations, and Tally handles all accounting logic including depreciation, provisions, and statutory compliance.
This is the cleanest pattern but requires the vendor to have built the integration natively, not as an afterthought. Ask for a demo of the specific integration — not a slide showing arrows between logos.
Stories from the floor
A precision machining shop in Rajkot (₹9 crore revenue, 55 people) was using Tally for accounting and Excel for everything else. Their quoting turnaround was 4-6 hours because the engineer had to manually cost each job from scratch. After moving quoting and BOM management to a manufacturing ERP, quotation time dropped to 15 minutes. They kept Tally for accounting. Six months in, the owner said the ERP had paid for itself three times over — not from cost savings but from increased quote volume leading to more orders.
A food processing OEM in Hyderabad (₹22 crore revenue, 140 people) discovered through job costing that their flagship product line — which they thought was their most profitable — was actually running at 8% margin instead of the assumed 18%. The reason: untracked material wastage during batch processing that Tally's stock records could not capture because consumption was recorded at the aggregate level, not per batch. Fixing the wastage issue alone saved ₹14 lakh per year.
A modular furniture manufacturer in Bengaluru (₹7 crore revenue, 40 people) was losing 1-2 orders per week because their quoting process could not keep up with enquiry volume. The owner was personally approving every quotation because there were no pricing guardrails — the sales team could give any discount they wanted. After implementing an ERP with pricing rules and approval workflows, the owner was removed from 80% of quotes, the team handled 3x the enquiry volume, and the average discount dropped from 12% to 7% because the rules enforced discipline.
The question to ask yourself
Here is the simplest way to decide whether it is time to move from Tally to a manufacturing ERP. Ask yourself this question:
Can I tell you — right now, without calling anyone or opening a spreadsheet — the actual production cost of my last 10 completed jobs, compared to what I quoted?
If the answer is no, you are running your factory on intuition and memory. Tally is handling the accounting. Nothing is handling the manufacturing.
Taking the next step
If the signs in this article feel familiar, it is worth exploring what a manufacturing ERP built for Indian SMEs can do for your operations. QuoteERP is designed specifically for this gap — it handles quoting, BOM costing, production tracking, job costing, and dispatch while integrating cleanly with Tally for accounting.
You do not have to replace Tally. You need to complement it with the operational layer that Tally was never designed to provide.
Talk to our team about a migration plan specific to your factory. We will map your current Tally setup, identify the operational gaps, and show you exactly how the two systems work together — with your data, not a generic demo.