Back to Blog
Case Studies

Replacing 12 Spreadsheets: A Chemical Company's Digital Transformation

8 July 2026 14 min read Case Studies
Replacing 12 Spreadsheets: A Chemical Company's Digital Transformation
Case Studies

Company Background

Srivastava Chemicals Industries Pvt. Ltd. is a specialty chemicals manufacturer based in the GIDC (Gujarat Industrial Development Corporation) estate in Ankleshwar, Gujarat — part of India's Golden Corridor, the densest concentration of chemical manufacturing units in the country. Established in 2003, the company manufactures industrial adhesives, surface treatment chemicals, and specialty solvents for the automotive, electronics, and packaging industries.

With an annual turnover of INR 86 crore, Srivastava Chemicals operates two manufacturing units with a combined production capacity of 12,000 metric tonnes per annum. The company employs 145 people including 8 chemists in the R&D and quality control departments. Their customer base includes tier-1 automotive OEMs, electronics contract manufacturers, and packaging companies across Western and Southern India.

The "12 spreadsheets" referenced in the title is not an exaggeration. When Indivar's assessment team arrived for the initial business study, they documented the following spreadsheet ecosystem:

  • Spreadsheet 1: Customer order tracker (maintained by sales coordinator)
  • Spreadsheet 2: Production schedule (maintained by production manager)
  • Spreadsheet 3: Raw material inventory (maintained by stores supervisor)
  • Spreadsheet 4: Finished goods inventory (maintained by dispatch supervisor)
  • Spreadsheet 5: Formula/recipe master (maintained by R&D head)
  • Spreadsheet 6: Quality control test results (maintained by QC chemist)
  • Spreadsheet 7: Supplier price comparison (maintained by purchasing head)
  • Spreadsheet 8: Customer credit and receivables tracker (maintained by accounts executive)
  • Spreadsheet 9: Regulatory compliance tracker — pollution consent, factory licence, PESO permit (maintained by admin manager)
  • Spreadsheet 10: Vehicle dispatch and e-Way Bill log (maintained by logistics coordinator)
  • Spreadsheet 11: Employee attendance and overtime (maintained by HR)
  • Spreadsheet 12: Monthly MIS report (compiled by the accounts head from all the above)

The financial backbone was Tally ERP 9, used strictly for accounting and GST compliance. All operational management ran on this spreadsheet ecosystem.

The Challenge

Replacing 12 Spreadsheets: A Chemical Company's Digital Transformation

The problems caused by this fragmented setup were pervasive and expensive:

  • Formula management errors caused losses of INR 22 lakh in a single year. The R&D team maintained product formulas (recipes specifying the exact ratio of raw materials for each product) in an Excel spreadsheet. On three separate occasions in the previous year, production used an outdated formula version — the R&D head had updated the formula in his Excel file but had not informed the production floor. Two of these incidents resulted in off-spec batches that had to be reprocessed (at significant cost), and one resulted in a batch that was scrapped entirely
  • Month-end closing took 18 days — the accounts head had to collect data from all 11 operational spreadsheets, reconcile discrepancies (which were always present), enter adjustments into Tally, and compile the monthly MIS report. The MIS for January was typically ready by the third week of February, rendering it largely useless for timely decision-making
  • Quality control was disconnected from production — QC test results lived in their own spreadsheet and were communicated to production via email or printed reports. There was no system-enforced hold on dispatching a batch until QC clearance was recorded. On at least two occasions, batches were dispatched before QC results were available
  • No real-time cost visibility — product costs were calculated quarterly (when the accounts team had time). The formula for a product might specify 12 raw materials, each at different prices with different yields. Calculating the actual cost of a specific production batch required pulling data from the formula sheet, the raw material inventory sheet, the latest purchase price sheet, and the production log. It took 2-3 hours per product, and the result was approximate
  • Raw material procurement was reactive — without MRP, the stores supervisor manually tracked stock levels and raised purchase requests when material ran low. Lead times for specialty chemicals range from 2 weeks to 6 weeks, and stockouts of critical raw materials caused production delays averaging 12 days per quarter
  • Regulatory compliance tracking depended on one person's memory — the admin manager tracked consent renewal dates, inspection schedules, and filing deadlines. When he was unavailable, items slipped. The company had received two show-cause notices from GPCB (Gujarat Pollution Control Board) in the past three years for late consent renewals
  • Data integrity was questionable — with 12 spreadsheets maintained by 10 different people, version conflicts were routine. The production manager's raw material numbers rarely matched the stores supervisor's numbers. The sales coordinator's order status did not match the dispatch supervisor's records. Arguments about "whose numbers are correct" consumed management meetings

"We had a Monday meeting every week where the first 45 minutes were spent arguing about data. Is the sales number correct or the dispatch number? Does the inventory match or not? By the time we agreed on the facts, we had 15 minutes left for actual decision-making. It was exhausting and completely unproductive."

Amit Srivastava, Director, Srivastava Chemicals

The Solution

Indivar Software Solutions implemented SAP Business One as a comprehensive replacement for the entire spreadsheet ecosystem — not just Tally, but all 12 operational spreadsheets.

Phase 1: Core ERP and Formula Management (Weeks 1-10)

SAP B1 was implemented across sales, purchasing, inventory, production, and financials. The most critical configuration was the Bill of Materials (BOM) structure adapted for chemical manufacturing:

  • Product formulas migrated to SAP B1 BOMs — each product's recipe is defined as a multi-level BOM specifying every raw material, its proportion, and the expected yield. Formula revisions are version-controlled — the current active version is locked, and only authorised users (R&D head with MD approval) can create new versions. Production orders automatically pull the current active formula version, eliminating the risk of using outdated recipes
  • Yield and loss factors built into BOMs — chemical manufacturing involves process losses (evaporation, residue, test samples). The BOM specifies the theoretical yield, and actual production receipts are compared against it. Yield variances above 3% trigger automatic investigation alerts
  • Batch management activated for all raw materials and finished goods with full traceability from input batches to output batches
  • Warehouse structure configured with zones: bulk tank farm (for liquid raw materials), drum storage, hazardous material zone, WIP area, finished goods, and rejected/expired zone. Storage compatibility rules prevent incompatible chemicals from being stored in adjacent zones

Phase 2: Quality Control Integration (Weeks 11-16)

Quality control was integrated directly into the production and dispatch workflow:

  • Incoming QC: Every raw material receipt triggers an automatic inspection request. The QC chemist records test results (purity, viscosity, pH, moisture content, etc.) against predefined specifications. Only batches that pass QC are released to the production-available zone
  • In-process QC: At defined stages during production (e.g., after mixing, after reaction, after filtration), the system generates sampling requests. Results are recorded against the production batch
  • Final QC: Finished goods cannot be moved to the dispatch-available zone until the QC chemist records final test results and marks the batch as "approved." The system physically prevents creation of a delivery note for an unapproved batch
  • Certificate of Analysis (CoA) generation: Customer-facing CoAs are generated automatically from QC data in SAP B1, with batch number, test parameters, results, and specifications — eliminating the manual CoA preparation that previously took 30 minutes per batch

Phase 3: Compliance and Automation (Weeks 17-22)

The remaining spreadsheets were replaced with integrated SAP B1 functionality:

  • Regulatory compliance tracker — all licences, consents, and permits catalogued in SAP B1 with validity dates and automatic renewal alerts at 90, 60, and 30 days before expiry
  • E-invoicing and e-Way Bill automation — replacing the manual dispatch and compliance spreadsheets with automatic generation from SAP B1 transactions
  • MRP configuration — weekly MRP runs generate purchase recommendations based on confirmed orders, forecasted demand, current stock, and supplier lead times. The reactive purchasing approach was replaced with planned procurement
  • Customer credit management — credit limits and payment terms configured per customer, with automatic blocks on order processing when limits are exceeded

Results

Results were measured over the first eight months post go-live:

  • All 12 spreadsheets eliminated — every operational function previously managed through Excel is now handled within SAP B1. The MIS report that previously took 18 days to compile is now generated on demand from live data
  • Month-end closing reduced from 18 days to 4 days — a 78% reduction. Because every transaction generates automatic financial postings, the month-end close is a validation exercise, not a data-entry marathon
  • Formula management errors reduced to zero — version-controlled BOMs with authorisation controls eliminated the risk of production using outdated recipes. The INR 22 lakh annual loss from formula errors was completely eliminated
  • Zero batches dispatched without QC approval since go-live — system-enforced controls replaced human-dependent checks. The two previous incidents of pre-QC dispatch cannot recur under the new system
  • Production delays due to raw material stockouts reduced by 85% — from 12 days per quarter to under 2 days per quarter. MRP-driven procurement with supplier-specific lead times ensures materials arrive when needed
  • Product costing accuracy improved dramatically — batch-level actual costing (incorporating actual raw material prices, actual yields, and actual overhead) is now available within minutes of production completion. The company identified two products where actual costs exceeded selling prices and adjusted pricing accordingly
  • CoA generation time reduced from 30 minutes to 2 minutes per batch — automatic generation from QC data in SAP B1 freed the QC team for analytical work instead of documentation
  • Monday management meetings transformed — the first 45 minutes of data arguments were replaced with 45 minutes of decision-making. All participants view the same dashboard data in real time — no more "my numbers versus your numbers"
  • Regulatory compliance achieved 100% — zero show-cause notices since go-live. Automatic renewal alerts ensure that consent renewals are initiated well before the deadline
  • Working capital improved — better inventory management through MRP, faster invoicing through automation, and tighter receivables management through credit controls freed approximately INR 42 lakh of working capital in the first six months

"The Monday meeting is a completely different experience now. We walk in, look at the dashboard together, and start discussing what to do about the numbers. Nobody argues about whether the numbers are correct because there is only one set of numbers — from SAP B1. We have gained back 45 minutes every week, which over a year is nearly 40 hours of productive management time."

Amit Srivastava, Director

Key Learnings

  • The spreadsheet count is a reliable indicator of ERP readiness. When your operational management depends on more than three spreadsheets maintained by more than three people, you have outgrown manual systems. Every additional spreadsheet adds a potential point of data conflict, version confusion, and information lag
  • Formula/recipe management in chemical manufacturing is a safety-critical function. An Excel file with no version control, no access restrictions, and no audit trail is not an acceptable system for managing chemical formulations. SAP B1's version-controlled BOMs with approval workflows are the minimum standard for formula management in the chemical industry
  • QC integration into the dispatch workflow is a system-level control. Telling your dispatch team "do not ship until QC approval" is a procedural control. Configuring SAP B1 to block delivery note creation for unapproved batches is a system control. One depends on human diligence; the other does not
  • The MIS bottleneck is almost always a data-collection problem, not an analysis problem. Srivastava Chemicals' accounts head is a competent professional. The 18-day closing was not due to analytical complexity — it was due to the time required to collect, reconcile, and enter data from 12 separate sources. Eliminate the collection step, and closing accelerates dramatically
  • Replace all spreadsheets at once, not gradually. The temptation is to implement SAP B1 for "core" functions first and keep some spreadsheets running in parallel. We resisted this approach. Parallel systems inevitably diverge, and users revert to their spreadsheet habits. A clean break — all 12 spreadsheets retired on go-live day — is painful for two weeks but transformative within two months

Running Your Business on Spreadsheets?

If your chemical manufacturing, food processing, or formulation-based business relies on disconnected spreadsheets for critical operations, the risk of errors, delays, and compliance failures grows with every additional spreadsheet. SAP Business One can consolidate your entire operation into a single, integrated platform. Contact Indivar Software Solutions for a confidential discussion about your digital transformation roadmap.

Indivar Software Solutions

SAP Business One consulting and custom software development since 2009. Offices in India, New Zealand, and the USA.

Related Articles

More on Case Studies

Need Help with SAP Business One?

Whether you need implementation support, custom add-ons, or strategic ERP advice, our team is ready to help. over 17 years of SAP B1 experience across India, New Zealand, and the USA.