
Ask an Indian manufacturing SME what software it uses, and the answer is almost always "Tally" — plus Excel. Tally does accounting, GST returns, TDS and statutory reports very well, and every accountant and auditor knows it. What it was never designed to do is run a factory: plan production by machine, track jobs through operations, control material issue against work orders, record inspections or manage job work with vendors in operational detail.
So as a factory grows, owners face a choice: replace Tally with a full ERP, or keep Tally and add factory software for operations. Many choose the second, and it works well — if responsibilities are clear. This guide explains how to divide the work between Tally and factory software, how to handle master data and transfers, and how to avoid the double entry and mismatches that make some combinations painful.
Why many SMEs keep Tally
- The accountant and auditor use it. Changing accounting software means retraining, new audit procedures and risk at year-end.
- GST and statutory compliance work. Returns, e-invoicing and TDS are already set up and familiar.
- History is there. Years of ledgers, balances and reports live in Tally.
- Cost and disruption. Replacing accounts at the same time as operations doubles the size and risk of the project.
The sensible approach for most SMEs is to leave accounts where they are and focus new software where the factory's problems are — operations.
Dividing responsibilities
The single most important decision is which system owns each kind of data. "Owns" means it is entered there first and is the reference if the two disagree. A typical division:
| Area | Owner | Notes |
|---|---|---|
| Ledgers, journals, bank, GST returns, TDS | Tally | Unchanged |
| Enquiries, quotations, sales orders | Factory software | Tally doesn't need them |
| Purchase indents and purchase orders | Factory software | Linked to material needs and jobs |
| Goods receipt (GRN) and inward inspection | Factory software | Purchase bill data passes to Tally |
| Stores, issues, transfers, job work | Factory software | Detailed stock lives here |
| Production, quality, maintenance | Factory software | Not in Tally at all |
| Delivery challan and sales invoice | Factory software (usually) | Invoice data passes to Tally |
| Receipts and payments | Tally | Optionally shown in factory software for follow-up |
The pattern is simple: operational transactions start in the factory software; their financial effect is passed to Tally; everything purely financial stays in Tally.
Master data: one source for each master
Customers, vendors, items and tax details exist in both systems. If they are created independently, names and codes drift apart and every transfer becomes a matching exercise. Decide which system creates each master and copy it to the other:
- Customers and vendors: often created in Tally by accounts (who check GSTIN, PAN and bank details) and copied to the factory software — or created in the factory software with accounts approval, then passed to Tally. Either way, one creates and one copies.
- Items: created in the factory software, which needs far more detail (drawings, BOMs, routings, units, locations). Tally may only need stock groups or a summarised set of items.
- Tax details: HSN codes and GST rates kept consistent in both, ideally maintained in one place and copied.
Moving transactions to Tally
The main transactions that pass from factory software to Tally are sales invoices, purchase bills (from GRN and the supplier's invoice), and sometimes stock journals or production entries. How they move depends on your Tally version, its configuration and your accountant's preference:
- Export and import: the factory software produces a file of the day's or week's transactions in a format Tally can import. Simple and transparent; the accountant controls the import.
- Direct connection: where your Tally setup allows it, transactions can be posted automatically. Faster, but needs careful handling of errors and duplicates.
- Summary entry: for low volumes, the accountant enters daily or weekly summaries from a report.
We confirm the practical option for your setup during scoping rather than promising one in advance. Whatever the method, each transaction should carry a reference to its source document so it can be traced in both directions.
Stock: one detailed ledger, not two
The most common pain in Tally-plus-factory-software setups is two stock ledgers that never agree. The factory software tracks stock by item, lot, location and work order; Tally tracks stock by item from purchase and sales entries. Every issue, transfer, rejection and job-work movement creates a difference.
The cleanest solution for most SMEs is to keep detailed stock only in the factory software, and post stock values to Tally at period end — raw material, WIP and finished goods by group — for the balance sheet. Tally's own inventory can be switched off or kept at a summary level. This needs agreement with the accountant and auditor, but it removes the monthly reconciliation exercise entirely.
GST documents
Tax invoices, delivery challans and job-work challans generated in the factory software must carry the details GST requires: GSTIN of both parties, HSN or SAC codes, tax rates and amounts, place of supply and document numbering. Numbering series must not overlap with any documents still raised in Tally. If e-invoices or e-way bills are generated, decide which system generates them; where the factory software is to do it, the route is confirmed during scoping. Our guide to GST e-invoicing and e-way bills in custom software covers the details.
Job work
Job-work challans for material sent to vendors, and the material's return, are operational and belong in the factory software. The challan data that matters for GST — quantities sent and received, and periodic job-work reports — can be produced from the factory software for the accountant. Our guide to job-work challans and balances explains the operational side.
Costing
Job and product costing needs operational detail — material issued, machine hours, labour, rejections — which lives in the factory software, and overhead rates, which come from accounts. A practical approach is to take overhead rates from Tally's figures once a quarter or year and apply them in the factory software, which calculates job costs. Our guide to machine hour rate calculation explains how.
Common mistakes
- Entering the same invoice in both systems by hand. Double entry causes errors and resentment. Pass data, don't retype it.
- Masters created in both systems. Leads to "ABC Engg", "A.B.C. Engineering" and "ABC Engineering Pvt Ltd" — the same customer three times.
- Two detailed stock ledgers. They will never agree. Keep one.
- Not involving the accountant early. The accountant's agreement on invoice ownership, transfer method and stock treatment is essential. Bring them into scoping.
- Changing too much at once. Moving invoicing to the factory software is a big change for accounts. Do it after orders and stores are stable, with a parallel run.
Purchase bills and three-way matching
When purchase orders and GRNs live in the factory software, the supplier's invoice can be checked against both before it is booked in Tally: was this item ordered, at this rate, and was this quantity received and accepted? This "three-way match" catches overbilling, rate differences and invoices for material that was rejected at inward inspection. A practical flow is for stores to record the GRN, quality to accept or reject, and accounts to match the invoice in the factory software before the bill passes to Tally. Accounts then books only verified purchases, and disputes with suppliers are raised with evidence.
Receivables follow-up
Payments are recorded in Tally, but the people who follow up with customers — sales or the owner — often live in the factory software. Showing outstanding invoices and their age in the factory software, updated from Tally daily or weekly, lets sales see a customer's overdue amount before accepting a new order, and lets the daily report include receivables. Where a direct link isn't practical, a simple outstanding report exported from Tally and imported each morning is enough.
Year-end and audit
Auditors will ask how stock, sales and purchases in Tally relate to the operational records. Prepare for this from the start: keep source document references on every transferred transaction, keep the period-end stock valuation report from the factory software with the books, and document the division of responsibilities and the transfer method. A short note describing the arrangement, agreed with the auditor in the first year, saves considerable discussion later.
Credit notes, debit notes and returns
Sales returns, rate differences and customer debit notes create credit notes; purchase returns and supplier rate differences create debit notes. These are easy to forget when setting up the division between systems. Returns of material are operational and should be received or sent in the factory software, so stock and quality records are right; the financial document can be raised there and passed to Tally like an invoice, or raised in Tally with a reference to the return. Decide which, and apply it consistently, so stock and accounts move together.
Multiple companies and branches
Many SME groups run more than one company or GST registration — a manufacturing company, a trading company, a unit in another state — each with its own Tally company. The factory software can serve all of them, keeping each company's documents, numbering and stock separate while giving management one view. Transfers between units, which are often taxable supplies between registrations, need clear rules about which documents are raised in which system.
A worked example
A sheet-metal component maker with 80 employees ran Tally for accounts and inventory, and Excel for orders, production and job work. Stock in Tally never matched the stores, and the accountant spent days each month adjusting it.
The company implemented factory software for orders, stores, job work and production, with invoices generated from dispatch. Customers and vendors continued to be created in Tally by accounts and copied to the factory software. Sales invoices and purchase bills were exported daily and imported by the accountant. Detailed stock moved entirely to the factory software; Tally received month-end stock values by group. The monthly stock adjustment exercise disappeared, and the accountant's time went into receivables follow-up instead.
Questions to settle before you start
- Which system raises the sales invoice?
- Which system creates customers, vendors and items?
- How will invoices and purchase bills reach Tally?
- Where will detailed stock be kept, and how will stock values reach the balance sheet?
- Who generates e-invoices and e-way bills, if you use them?
- Has the accountant — and ideally the auditor — agreed?
Settling these questions in writing before development starts takes an afternoon with the owner and the accountant, and prevents most of the problems described above.
If you are unsure where to begin, start with orders, stores and dispatch in the factory software while invoices continue in Tally for the first few weeks; move invoicing across once the team trusts the new dispatch records.
Working with Corposol
Corposol builds custom factory software for Indian SMEs that runs operations while accounts stay in Tally. We agree the division of responsibilities and the data transfer method with your accountant during scoping, before anything is built. All custom code is transferred to you on final payment.
Frequently asked questions
Can we keep Tally if we implement factory software?
Yes. Many Indian manufacturers keep Tally for accounting, GST returns and statutory reports while running operations — orders, stores, production, quality and dispatch — in factory software. The key is to decide clearly which system owns which data.
Which system should make the sales invoice?
Usually the factory software, because the invoice depends on what was actually dispatched against which order. The invoice data is then passed to Tally for accounting. Some companies prefer the reverse; either works if it is decided and followed.
How does data move from factory software to Tally?
Depending on your Tally setup and your accountant's preference: an export file imported into Tally, a direct connection where your Tally version and configuration support it, or a summary entered by the accountant. We confirm the practical option during scoping.
Will stock in Tally match stock in the factory software?
It should match in value at period end if both systems are fed from the same transactions. Many companies keep detailed stock only in the factory software and post summarised stock values to Tally, which avoids two detailed stock ledgers drifting apart.
