Retyping data between systems is not admin work, it is a missing integration

Retyping data between systems feels like work, but it produces nothing. Someone reads a number on one screen and types it into another. That is not admin work, that is a missing integration.

Short answer. Manually retyping data between systems is a symptom, not a task. It arises because two systems need the same data but do not talk to each other. You solve it by appointing one source of truth and building an integration that passes the data through automatically, so no one has to retype it again.

The universal pain: swivel-chair work

There is a term for it in the process world: swivel-chair work. An employee swivels on their office chair from one screen to another and retypes what already exists somewhere. An order number from the webshop into the accounting package. Hours from a work order into the payroll administration. A customer address from the CRM into the invoicing system.

I come across this in every industry. Webshop, wholesale, construction, manufacturing, finance: the form differs, the pain is identical. Every time the information already exists somewhere, and every time someone is paid by the hour to move that information by hand to the next place.

This costs money in three ways. First the direct time: someone who is retyping creates no value during those minutes. Then the errors: every manual transfer is a chance for a typo, the wrong version, a forgotten line. The annoying part is that these errors only surface later, in a wrong invoice or wrong stock figure, where they are far more expensive to put right. And third the overview: as long as figures are kept separately in two places, they drift apart and you no longer know which one is correct.

This loss hides itself. It is spread across the salaries of people who spend part of their day retyping instead of making something. No single day feels like a disaster. But added up over a year serious money leaks away, like a tap that drips just softly enough to go unnoticed.

Why it keeps coming back: no one appointed a single source

Retyping does not arise from laziness. It arises because systems have grown up separately. First came the accounting package. Then the webshop. Then a planning tool. Each system has its own place where data lives, and no one ever agreed which place is in charge.

That is how duplicate entry creates itself. System A has the customer address, system B needs it too, so someone types it over. Multiply that by the number of orders, work orders or customers per day, and you have an invisible full-time task that no one deliberately set up.

The solution does not start with buying software. It starts with one question: for this piece of data, what is the source of truth? Which system is leading for the order number, for the hours, for the address? Once that is settled, the rest becomes a matter of passing through instead of retyping.

How I approach this: goal, process, then build

I work in three steps, and I do not skip any of them.

First the goal. Not "we want an integration", but what you concretely gain from it: figures that are correct, less manual work, a better overview and a grip on your operation. That goal determines what the integration needs to be able to do.

Then reviewing the process. Before I build anything, I look at the steps as they run today. Often it turns out that the retyping is a grown habit around a step that could be smarter or removed entirely. Building an integration around a messy process means you automate the mess. Clean up first, then connect.

Then building. Sometimes there is a standard package that fits neatly, and I will say so honestly. But often no off-the-shelf package fits the way your business works, with that one supplier, that custom format, that exception that always exists. That is where I build the integration, the AI workflow or the dashboard that does fit. That custom work, at the point where standard falls short, is exactly where the gain sits and what is hard to copy.

How this plays out in practice

The same pain, a different industry. Below are the places where retyping turns up most often, and how I approach it per situation.

Sales and orders

• Retyping everything at the end of the day: in a webshop a pile of orders builds up that goes into the accounting by hand at the end of the day. That can happen automatically, live.
• Preventing order retyping: in e-commerce orders ideally flow straight from the ordering platform to processing, without a manual intermediate step.
• Importing orders from a supplier portal: in wholesale orders come in via a portal and are retyped into your own system. That import can happen automatically.

Hours, work orders and production

• Linking a work order to invoicing: in construction hours end up on a paper or loose work order that later has to go into the invoice by hand. Link the work order directly to invoicing.
• Registering shop-floor hours: in manufacturing hours and production tickets are written down on the floor and then retyped. Register them digitally at the source straight away.
• Linking hours to payroll administration: registered hours often still have to go into payroll processing by hand in finance. That transfer can run directly.

Finance and administration

• Preventing duplicate entry in CRM and accounting: customer and invoice data live in both the CRM and the accounting and are maintained in both places. One source, passed through automatically.
• Automatically importing invoices and receipts: purchase invoices and receipts are retyped into the administration by hand. With automatic recognition you import them directly.