About Lemorange
We build attendance software in Cyprus.
Attendance sits between the terminals on your walls and the payroll run at the end of the month. This page is about how it is built, because that is what determines whether you can trust the numbers that come out of it.
Who builds it
Attendance is a Lemorange product.
Lemorange Ltd is a software house in Cyprus. It builds finished products rather than prototypes and owns the whole of them: architecture, engineering, deployment, and the support that comes after. Enterprise and desktop systems, mobile apps, payment and HR platforms, and the integrations that make one talk to another.
Attendance is one of those products rather than a side project. That is the reason the terminals, the phone app and the payroll connector are a single piece of work instead of three that have to be talked into agreeing with each other.
Lemorange is a member of ISACA, the body behind the COBIT governance framework, and follows its standards for IT governance, risk management and information security.
Why it exists
Attendance data is easy to collect and hard to defend.
Most organisations already have the raw material. Terminals record punches, spreadsheets record corrections, and someone reconciles the two at the end of the month from memory and a pile of emails.
The problem is not capture. It is that by the time a number reaches payroll, nobody can say precisely how it got there, which punch it came from, who changed it, when, and why. When an employee disputes a figure, or an inspector asks, the answer is a rebuild rather than a record.
Attendance was built so that the path from a punch at a door to a line on a payslip is one continuous, inspectable record. Every rule that transforms it is configured rather than hidden, and every human decision along the way carries a reason and a name.
How we work
Three habits worth knowing about before you buy anything.
We do not call a terminal integrated until it has passed on real hardware.
Seven checks against a physical unit: enrolment ids match, every verification method produces a punch, in and out map correctly, a disconnected gateway backfills everything it missed, a duplicate event stays one punch, an unknown enrolment is held and replays, and a shift across midnight lands on its local start date. The model, firmware and gateway version get recorded with the result.
We prove the arithmetic instead of asserting it.
A simulation suite runs three hundred seeded scenarios through the engine and checks against an independent oracle that no minute is created or destroyed between a punch and a payroll line. Conservation is a test that fails, not a claim on a page.
We describe what is unfinished as unfinished.
Our CSV payroll export delivers today. Our CyCom connector is built and tested but is not carrying hours yet, because CyCom have not opened their interface. Until they do we say so plainly and your hours go across as a file. You will find that written on the product page too, because finding it out later is worse.
What the software will not do
Boundaries we hold on purpose.
- It does not track where anybody is. The live map shows sites and headcounts, never a person's position or movement.
- It does not silently change an approved day. Once a manager approves, reprocessing leaves it alone.
- It does not discard a punch it cannot place. Unknown badges are held and replayed, never dropped.
- It does not hide a refusal. A rejected check-in is recorded with its reason, the distance measured and the network seen.
- It is not a payroll engine. It prepares reviewed, approved time and hands it over.
Reaching us
A phone number that a person answers.
If you are weighing this up, the fastest route is a conversation about your own sites, departments and shift patterns rather than a feature list.