Running alongside your old attendance software
If your company already records attendance with other software, you do not have to switch it off. MekongHRM can read the punches that software has stored, a few seconds after they are made, and use them like any other punch. Your machines, your fingerprint enrolment and the old software stay exactly as they are. MekongHRM only reads.
This works with any make of machine, because MekongHRM does not talk to the machine. It reads what the software of the machine has written down.
Before you start
- The attendance module, on a plan that includes devices. Each connection counts as one machine against the plan's limit.
- The old software must keep its punches in Microsoft SQL Server.
- Every person in the old software must have the same Staff number in MekongHRM as the number the old software holds for them. That number is how a punch finds its owner.
What your company prepares
MekongNet sets the connection up. You do not have a screen for it, and you do not need one. You give MekongNet three things:
- An address that the MekongHRM server can reach: a fixed IP address or a domain name, and the port of the SQL Server.
- A read-only SQL Server user. It can read the tables that hold the punches and nothing else. It cannot change anything, so MekongHRM could not change your old data even by mistake.
- A firewall rule that opens that port to the MekongHRM server's address only, and to nobody else.
Your network administrator knows how to do all three. MekongNet gives them the server's address and the exact steps.
What happens next
- MekongNet declares the connection and tests it against your data. It shows them the first rows it finds, and which person each number belongs to.
- When the test is right, MekongNet turns it on.
- MekongHRM then looks for new punches every 5 seconds. The first time, it reads from the first day of the attendance period that is open now. If the period before it is not locked yet, it counts as open too, and reading starts from its first day, so punches that arrive late across the end of a period are not missed. It never goes back further than that, and locked periods are not read.
What you should see
- A punch made on a machine of the old system appears in the punch log within seconds, marked with the source Old attendance software. Open Punch log to see it.
- The day is worked out from it like any other: it is placed in the stretch of the shift whose window it falls in, and the attendance grid follows.
- The person gets a confirmation where they normally receive notices, as with a machine: in Telegram, or in the mobile app's inbox for staff who use the app. It is sent only if the punch is no more than ten minutes old when it is read. The first read and the hourly re-read do not send messages about old punches.
- A punch from the old software has no position and no photo. MekongHRM does not know which machine it came from, and does not ask.
- Once an hour, MekongHRM reads again from the same starting point. Old software sometimes receives punches late, for example when a machine lost its network for half a day. Reading again picks them up. Nothing is counted twice.
If something goes wrong
A person's punches do not appear. Their staff number in MekongHRM is not the number the old software holds. MekongNet can see the numbers that matched nobody, with how many punches each has. Nothing is lost: the punches are kept, and as soon as a record with that number exists, because HR created it or corrected its number, they join it. Numbers are compared as numbers, so 123 and 00123 are the same.
Punches stopped coming. The old server may be switched off, the network down, or the firewall changed. MekongHRM asks again, a little less often each time, and starts again at once when the server answers. Punches made meanwhile are read afterwards, and nothing is lost. MekongNet is told after ten minutes. Your HR team does not receive this alert, because the people who can fix it are MekongNet and your network administrator.
A punch arrived for a period that is already locked. It is kept in the punch log and marked, and the locked period is not recalculated. This is the same rule as for every other source; see Closing the month.
The time looks wrong. MekongHRM takes the time the old software wrote as the local time of the person's branch. If the old software saves its times in another zone, tell MekongNet so the connection can be corrected. A punch dated more than a day in the future, from a machine whose clock is set to the wrong year, is ignored.
Your plan was downgraded or expired. Reading stops, like a machine that stops being listened to. When the plan is back, reading continues from the start of the open period.
Last checked 16/11/2026