What is rekeying, and why does nobody budget for it?
Rekeying happens whenever a person reads a value from one place and types it into another. A customer sends a WhatsApp message with their address and a job description, and someone copies both into the job card system. An email quote arrives, the estimator types the same lines into a spreadsheet, then again into the accounting package. A delivery note gets written out by hand because the delivery app cannot print what the warehouse actually needs.
The reason it survives is that no single instance feels expensive. Forty seconds here, ninety seconds there. Nobody is sitting idle while it happens either, which is exactly why it never shows up on anyone's radar. It surfaces later as a quote that went out a day late, a job booked with the wrong suburb, an invoice that had to be reissued, or an owner doing the books on a Sunday because the data never made it into the system.
How many times does the same data get typed each week?
Do this for one week before changing anything. Pick a single transaction type — a customer job, a supplier invoice, a stock order — and follow one of those all the way through. Write down every point where a person retypes information that already exists earlier in the chain.
Then price it:
weekly rekeying cost = (rekeying events per week) x (minutes per event) x (loaded hourly cost)Loaded hourly cost is not the wage. Take the person's pay, add employer costs, add the share of a manager's or bookkeeper's time that goes into checking and correcting their work. A person paid R45 an hour who costs the business R60 an hour to employ, plus checking, is a R60 an hour problem. Use your own figures, because nobody outside your business can supply them accurately.
Then do the same exercise for the errors, not the typing. Count how many times last month a job was booked with a wrong address, a quote missed its follow-up date, or an invoice was reissued because a reference number was mistyped. Multiply each by what it cost to put right — a wasted trip, a lost customer, an hour of rework.
The number that changes decisions is rarely the typing time. It is the time lost because the data reached the system too late to be useful.
Which rekeying costs a small South African business the most time?
Sort your own list by how often it happens multiplied by what it costs when it goes wrong. For most businesses the ranking looks close to this:
| Where the retyping happens | Why it hurts |
|---|---|
| WhatsApp to job system | Most requests arrive here, and the volume is the highest |
| Email quote to spreadsheet | Creates duplicates, and the spreadsheet is stale within a day |
| Supplier invoice to accounts | Slows the payment run and leaves queries unanswered |
| Delivery note to stock file | Stock figures drift from reality, so recounts get longer |
| Bank statement to reconciliation | Built entirely on manual matching |
| Supplier bank details to the payment file | The one rekeying step that can cost you real money |
That last row deserves a closer look. Copying bank details by hand is a routine target for invoice and supplier impersonation fraud, and a small business is exactly the size of organisation where nobody performs an independent second check. Any supplier that changes banking details should trigger a verification step that does not depend on one person trusting their memory or a phone number that arrived by email.
How do you stop rekeying without buying a new system?
Most rekeying disappears when one entry point feeds the others.
- Decide where a piece of information is first captured, and write it down. For most businesses that is the job or order system, not email and not WhatsApp.
- Get every other channel to capture there too. A shared inbox, or a number that forwards messages into the job system, removes the transcription step rather than making it faster.
- Give each field one home. An address that lives in three places will be correct in at most one of them, and the other two are now a liability.
- Automate the copy, not the typing. Where two systems genuinely cannot talk to each other, a scheduled extract and re-import is a legitimate interim answer.
- Add a validation step wherever a human still has to look. A reference number typed twice that does not match should stop the process, not pass through it.
What should you fix first?
Start with the rekeying that happens most often, not the one that looks most impressive. In a small team, volume beats elegance every time. A messy process that runs forty times a week and costs a customer a wrong quote is worth more attention than a tidy one that runs twice a month.
Measure before and after, using the same transaction, the same week and the same counting method. Otherwise you will not know whether the change helped, and you will be arguing about a number nobody can defend.
The companion checklist walks you through a one-week rekeying log, and the templates include a system map and a before-and-after measurement sheet you can fill in today.
Not sure which of your rekeying is worth removing first? Book a free strategy session with Agentcy.