Where the Figures Cross by Hand

1. At a Glance

Issue study · From the public record. No organisation is named here, because the public record we went through names no manufacturer with this problem. IOanyT had no part in anything described. Everything in section 3 comes from the public record, and everything we add to it is labelled as our reading.

Organisation type	Smaller and mid-sized manufacturers, as a group: the producers described in a report of an Indian industry summit, set beside two surveys of firms and one of IT professionals
Size band	Small and mid-size firms. Our reader: a mid-size manufacturer with an ERP, applications it built or had built beside it, and plant records kept on sheets and in spreadsheets
Region	India for the summit report, one survey and the e-invoice rule. One survey gives no country; one is of IT professionals in the US
The decision at stake	Whether to wait for a new ERP or a connection product to “connect the systems”, or to find out first how the figures travel today and deal with the crossings one at a time
The public outcome	No single outcome is on record. The summit report suggests that without groundwork on data, a pilot that succeeds may never grow beyond a pilot
Why it matters to a mid-size manufacturer	Every plan to see the plant’s figures in one place, plan from them or try AI on them needs figures that arrive by themselves. While they are carried by hand, such a plan runs once and stops

2. The Business Problem, in the Buyer’s Words

“Our Monday review starts with three numbers for the same shift, and all three are right for a different moment. My planner types the night’s output into the ERP, then the planning sheet, then a customer’s portal. We tried an AI project last year; it worked on three months of sheets someone typed up, and stopped when they stopped typing. Every time I ask for the systems to be connected, I am told it will come with the next ERP. I do not need a bigger system as much as I need to know where my figures go.”

These words are imagined. They describe the decision as the research shows it, not a real conversation.

The firm is caught between figures that are recorded with care and systems that cannot take them from one another. The request to connect them is made as one large wish, so it waits for one large decision.

3. What We Found

Method. We went through the public record on smaller and mid-sized manufacturers whose figures do not travel between their systems: a report of an industry summit in India in 2026, an industry body’s survey of manufacturers on barriers to AI, a news report of a survey of small and mid-size Indian firms, one survey on why firms keep old systems, and an advisory from India’s GST Network on reporting e-invoices.

The barrier, as the summit report describes it. The report comes from a market-data firm that rewrites news, published in 2026.

What	Public record
Who it is about	Smaller and mid-sized producers in India
The barrier	A barrier deeper than tools: data split across systems, old machinery, and no standard way of operating
What follows without that groundwork	A pilot that succeeds may never grow beyond a pilot
Firms named	None of that size. The report names one large firm, which is not used here
Figures	None
Why the data is fragmented	Not examined by us; we draw no cause from the record

What manufacturers say holds them back. In an industry body’s survey of manufacturers, published in 2026, respondents picked their top three barriers to AI. About six in ten named data issues, and about a quarter named the need to upgrade old equipment. The page gives no sample size or country, and the survey is about AI, not about connecting systems.

Where small and mid-size firms stand. In a survey of more than 400 small and mid-size Indian firms across IT, manufacturing, education and retail, reported in mid-2025, more than four in ten had reached basic digital maturity, meaning an ERP and the cloud, and more than half cite a lack of technical skills.

Why firms leave things as they are. In one survey of about 500 IT professionals in the US, run by a firm that sells software services, half said a reason they had not modernised was that the current system still works, more than four in ten named budget limits and more than a third fear of disrupting operations. The survey covers every sector, not manufacturing alone.

A rule with a deadline. An advisory from India’s GST Network, dated 5 November 2024, says that from 1 April 2025 “taxpayers with an AATO of 10 crores and above would not be allowed to report e-Invoices older than 30 days from the date of reporting on IRP portals”. Its example: an invoice dated 1st April 2025 “cannot be reported after 30th April 2025”. It applies to invoices, credit notes and debit notes for which an IRN is to be generated, and is for taxpayers with an aggregate annual turnover (AATO) of 10 crore rupees or more; the advisory says there is “no such reporting restriction on taxpayers with an AATO of less than 10 crores as of now”. The advisory says nothing about old or in-house systems. That an invoice raised in one old application and uploaded by hand later can miss the window is IOanyT’s reading, not a statement of what the rule requires of any firm, and whether it applies to a particular firm is for its tax adviser.

Our reading of why the figures do not travel. These four are our reasoning from the record above. None is a finding of any source.

1. Nobody has drawn the crossings. Each system has an owner. The places where a figure passes from one to the next, by a person, a timed file or a script, are listed nowhere.
2. People are the joins. A clerk types the shift sheets into the ERP; a planner copies the same output into a planning sheet. The work is careful, and every hand-over is a place where a figure can change or arrive late.
3. Small joins are tied to large decisions. A request to connect two systems is deferred to the next ERP, which is years away, and a spreadsheet macro fills the gap.
4. A pilot runs on figures gathered for it. Without figures that arrive by themselves, a project works once, on records typed up for the purpose, and stops when the typing stops.

4. The Options a Firm in This Position Had

Option	When it fits	What it risks	Our view
Wait for a new ERP to connect everything	A new ERP is already approved and close	A new ERP connects to what it is told about; the firm’s own applications and its plant records may still be outside it, and every join waits for its date	Right only if the ERP is near and the joins are written down for it
Buy a connection product from a specialist	The firm runs several packaged systems the product already joins, and has people to run it	The firm’s own older applications may have no way in or out, and crossings made by hand stay off the product’s map	The firm’s option with specialists; we do not supply, install or run such a product
Build one connection between two of the firm’s own applications	One crossing is plainly the costliest, and both ends are understood	One more thing to own, and every other crossing is left as it was	Right for a single, well-understood crossing, once the others are known
Map every crossing first, then rebuild the firm’s own application one module at a time, so each figure is entered once	Nobody can list how figures travel today, and the firm’s own application is where a figure is typed again	Costs money before anything changes; old and new run side by side for a time	Our recommendation

5. Our Recommendation, and the Decision It Asks of the Board

For the applications a manufacturer built or had built beside its ERP: map every crossing first, including those made by hand, by timed files and through spreadsheets, count the copies of each figure and name its source. Then rebuild the firm’s own application one module at a time, beside the old one, so each figure is entered once and read from there. Each module is accepted by the firm’s own people against a benchmark agreed before work starts. The old application keeps running until each module is accepted; the firm’s own team or supplier keeps it running. A connection product, and anything that reads from machines or captures records on the plant floor, is the firm’s option with specialists. The packaged ERP itself is not part of this work.

6. Benchmark: Where You Are Now, and Where You Should Be

These are targets, not results. In an engagement the starting points are replaced by the manufacturer’s own figures, taken in the first review.

Measure	Typical starting point	Where it should be	How it is checked
Crossings between the firm’s applications, its ERP and its plant records	Listed nowhere	Every crossing mapped, including by hand, timed files and spreadsheets	The map of the system
Figures re-typed from one place to another	Not counted	Counted, and falling as each module is accepted	Reported at every review
The source of each figure	Several copies, none named as the source	One named source for each figure	The specification
Disagreements between systems	Argued in meetings and adjusted	Each traced to the crossing that makes it	The risk register, at every review
Scripts, macros and timed files that carry figures	Unknown, with no owner	Listed, each with an owner on the firm’s side	The risk register
Invoices uploaded by hand from an old application	Not listed	Listed, with where each is raised and how it travels	The specification and the risk register

7. How IOanyT Would Work

1. We listen: a free Reliability Review. A first conversation about your applications, the figures that disagree, and the joins that wait for a new ERP. You leave with a short written note of what we found. You can start with a conversation about the system; we ask for read-only code access only when the assessment begins.
2. We research. We research your sector, the regulator’s position and what the public record says about firms in your situation. This study is an example of that work.
3. We read the system and propose: the Legacy System Specification Assessment. Here the system is the applications you built or had built beside your ERP, and the files, scripts and hand-offs that carry figures in and out of them. It produces a map of the system as it stands, a written specification of what it does, a risk register, a cost comparison between keeping and replacing the system, and a staged plan with a fixed quote. AI does a first pass, our senior engineers review it and trace it to the code, and your own experts confirm it. Code access is read-only and logged, never used for training, and deleted within 30 days of the evaluation ending unless we engage.
4. If you approve, we build. We replace a system one module at a time while the old one keeps running. Here that means your own application that receives a figure, rebuilt one module at a time so the figure is entered once. We never do a single cutover. A traceability matrix links every old function to its replacement. The work is billed by milestone, each milestone tied to a module you accept, and you can pause after any accepted module.
5. We review against the benchmark. Before work starts we set the benchmark. After each module we show you where each measure stands, and the filled-in benchmark is yours at the end.

The Review is free. Every paid step is fixed price, agreed at scoping. Stop after any step. The findings are yours. The assessment fee is credited in full against the first build stage if it starts within 90 days of the report.

8. What the Client Would Own

• The map and the specification: every crossing between the firm’s own applications, its ERP and its plant records, and what the applications do, in writing, confirmed by the firm’s own people.
• The risk register: what the assessment found, listed before any price is set, including scripts and timed files with no owner and rules nobody owns, listed for the business to decide.
• The traceability matrix: for every module IOanyT rebuilds, every old function linked to its replacement, with how it was checked.
• The code: the rebuilt modules are the client’s. No runtime or platform fee.
• The filled-in benchmark: each measure, where it started and where it stands, including how many copies of each figure remain.

9. What This Approach Does Not Cover

• IOanyT has no connection or integration product and sells none.
• IOanyT does not connect to machines, read machine signals, or work on plant control systems, machine software or shop-floor control systems. How a figure is first captured on the plant floor is the firm’s decision, with its own specialists.
• IOanyT cannot see inside or change a packaged ERP product, and is not a partner of any ERP maker. Where a crossing ends inside one, the map records it from the outside, and anything on its side is the firm’s ERP specialist’s work.
• IOanyT does not run, monitor or support a connection or a rebuilt module after hand-over, does not keep the old applications running during the work, and does not host them. The manufacturer’s own team or supplier does.
• IOanyT does not clean, correct or reconcile records as a stated service, train plant or office staff, or manage change. Some differences begin on the plant floor, with a late sheet or a count taken at another moment, and no map of software removes them.
• IOanyT gives no tax or legal advice. Whether the e-invoice limit applies to a firm, and how, is for its tax adviser, and IOanyT’s work does not make any firm compliant with it.
• IOanyT promises no result from AI or analysis on a plant’s figures.
• This study does not say IOanyT would have changed anything described, or that IOanyT has done this work for a manufacturer. IOanyT has no published case of this work for a manufacturer.

About this study: IOanyT did not work on this case. It is drawn from published findings, cited below.

10. Sources

Source	Used for
A market-data firm’s report of an Indian industry summit, 2026	The barrier for smaller and mid-sized Indian producers, and pilots that go no further
An industry body’s survey of manufacturers, 2026	Barriers to AI: data issues and legacy equipment
News report of a research firm’s survey of Indian small and mid-size firms, 2025	Digital maturity and skills
A vendor’s survey of about 500 US IT professionals, 2025	Why firms keep old systems
GSTN advisory, 5 November 2024 (copy hosted by the Maharashtra GST Department)	The 30-day limit for reporting e-invoices

IOanyT is a consultancy with its own engineering team: we study the problem, recommend, and prove it by building only what you approve. We start by drawing how the figures travel today, so that a pilot has figures that keep arriving.

Book a free Reliability Review →

Get a fixed quote →

See the Legacy System Specification Assessment →