Your Planner Types the Same Figure Three Times. Four Ways to Stop It, Weighed.

The production planner is at the desk by half past six. The night shift’s sheets are waiting.

First the output goes into the ERP, line by line. Then the same figures go into the planning sheet, which the ERP cannot feed. Then the day’s dispatch plan goes into the customer’s portal. By half past seven the planner has typed the same numbers three times and has not yet planned anything.

The planner asked two years ago whether the systems could be connected. The answer was yes, in the next version of the ERP.

What We Found

For this article we went through the public record on firms that carry figures between their systems by hand, and why: a news report of a survey of small and mid-size Indian firms, one survey on why firms keep old systems, a report of an Indian industry summit, and an advisory from India’s GST Network on reporting e-invoices.

Four findings stand out.

Many firms have the systems, and not the joins. 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. In the same survey, more than half cite a lack of technical skills.

The pull to leave things as they are is strong. 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, and more than four in ten named budget limits.

A pilot does not travel on figures carried by hand. A report of an Indian industry summit held in 2026 says that where smaller and mid-sized producers lack that groundwork, a pilot that succeeds may never grow beyond a pilot.

Since April 2025, some e-invoices have 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”. The limit applies to invoices, credit notes and debit notes for which an IRN is to be generated. The limit 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”.

Our reading is that the re-typing is not a failure of the people who do it. It is how the firm’s own applications, its ERP and its plant records are joined: a figure is written once where the work happens and carried by hand to every other place that needs it. And where an invoice is raised in one old application and uploaded by hand later, it can now miss a window. That last point is IOanyT’s reading of the rule, not a statement of what it requires of any firm.

What Opens Up When a Figure Is Entered Once

Re-typing is usually seen as a small inefficiency. Our reading is that the larger opening is in what the figure can then do.

• Planning starts from last night’s figures. When the night’s output reaches the planning sheet by itself, the first hour goes on planning.
• A pilot can run every day. A project that worked on figures gathered by hand can go on running when they arrive by themselves.
• An invoice reaches the portal while it can still be reported. For a taxpayer at or above the threshold, an invoice raised and reported from one place does not wait to be uploaded by hand. This is IOanyT’s reading, for your tax adviser to confirm.
• The people who copy figures do the work they were hired for. The copying is the problem, never the people.

This is our reading of the evidence. It is not a measured market figure.

Four Ways to Stop the Re-Typing, Weighed

There are four real options. Each one is right for somebody.

Option	When it fits	What it risks
Buy a connection product from a specialist	The firm runs several packaged systems the product already joins, and people to run it	The firm’s own older application may have no way in or out, and figures typed by hand stay off the product’s map
Build one connection between two of the firm’s own applications	One crossing is plainly the costliest, and both ends are well understood	One more thing to own: when either end changes it must change too, and every other crossing is left as it was
Rebuild the firm’s own application, one module at a time, so the figure is entered once	The firm’s own application is the reason a figure is typed again	Old and new run side by side for a time, and anything on the ERP’s side still needs the firm’s ERP specialist
Map every crossing first, including by hand, then decide	Nobody can list today where each figure is typed again	It costs money before anything changes, and the map connects nothing by itself

Where You Are Now, and Where You Should Be

Before any work begins we set a benchmark: a few measures taken from your own applications, each with a target.

Measure	Typical starting point	Where it should be	How it is checked
Places each figure is typed again	Not counted	Counted, figure by figure	The map of the system
Figures re-typed from one place to another	Several each day, by hand	Falling as each module is accepted	Reported at every review
The place each figure is first entered	Wherever the work happens to be recorded	One named place, in your own application	The specification
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

The starting points above are what the public record suggests and what we expect to find. In an engagement they are replaced by your own figures, taken in the first review. The targets are what we would work towards with you. They are not results we have already achieved for a manufacturer.

How We Work With You

1. We listen: a free Reliability Review. A first conversation about your applications, and the figures your people type more than once. 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 article 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 every place a figure is typed into or 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. You get the options and our recommendation.
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 rebuilt module by module, so each figure is entered once while the old screens carry on. We never do a single cutover. Each module has a traceability matrix. 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.

This approach has limits. A rebuilt module is one more thing your team owns, and we do not look after it for you. We cannot see inside or change a packaged ERP product; anything on its side is your ERP specialist’s work. Some crossings cannot be closed at all, because a customer’s portal or a packaged product offers no way in. We have no connection or integration product, we do not connect to machines, read machine signals or work on plant control systems, and we do not run or monitor a connection after hand-over. We give no tax advice: whether the e-invoice limit applies to your firm is for your tax adviser, and our work does not make any firm compliant with it. We have no published case of this work for a manufacturer.

What changes for the business:

Role	What they gain
CEO	A long-standing irritation is dealt with as a job of its own, not deferred to a new ERP.
CTO or CIO	One crossing is carried by code with an owner on the firm’s side, in place of a spreadsheet and one person’s memory.
CFO	Spend goes first to the crossing that is typed again most often, and the rest wait their turn on the map.
COO	A figure is entered once, and the planner’s first hour goes on the plan.
Head of digital	Each module rebuilt is one more figure that reaches other systems on the day it is made.

The cases in this article, and what IOanyT does about that kind of problem:

The case	What IOanyT does
In a survey of more than 400 small and mid-size Indian firms across four sectors, more than four in ten had reached basic digital maturity, and more than half cite a lack of technical skills.	Our part is narrower: we supply no product and no staff. For a manufacturer’s own applications, we map where each figure is typed again and rebuild the application that receives it, module by module.
In an advisory dated 5 November 2024, India’s GST Network set a 30-day limit for reporting e-invoices, from 1 April 2025, for taxpayers with an aggregate annual turnover of 10 crore rupees or more.	Our assessment shows where invoices are raised in a firm’s own applications and how they reach the system that reports them. Meeting the limit is the taxpayer’s own work, and we give no tax advice.

IOanyT is a consultancy with its own engineering team: we study the problem, recommend, and prove it by building only what you approve. We look for the one place each figure should be entered.

Book a free Reliability Review →

Get a fixed quote →

See the Legacy System Specification Assessment →