HR & workforce operations · built for the floor
Most HR software starts at a web form. Flume starts at the hardware — a biometric terminal on your plant floor — and carries every punch, unbroken and auditable, through reconciliation, approval and payroll to a number you can defend in front of a labour inspector.
The month-end you already know
A punch goes missing. A supervisor swears someone was on site. Payroll runs on a spreadsheet that four people have touched. Then an inspector asks why one line on one payslip in March was adjusted — and nobody can answer without a week of digging. Flume closes that gap by making the whole path one system, with a record at every step.
The chain · a punch, end to end
ZKTeco terminals push punches to Flume the moment they happen — no nightly export, no USB stick. Staff who move between sites are recognised at any registered terminal and flagged as cross-branch. Office and field staff clock in from the mobile app inside a geofence instead.
ADMS push · device pairing · fleet health · punch & operation logs · GPS self-service
A biometric punch is a physical fact, so Flume records it and reconciles rather than overwrites. Earliest punch wins; the one it superseded is kept, not deleted. A nightly close-out flags every day that ended incomplete — clocked in, never out — so those days reach a human before they reach payroll.
Duplicate & superseded handling · nightly close-out · needs-review queue · backfill
Corrections are append-only history, never silent edits, and records are never hard deleted. Leave, overtime and shift swaps route through the approval tiers you configure — supervisor, then HR — and every decision keeps its author, timestamp and reason.
HR corrections with before/after · multi-tier approvals · swap requests · audit log
Payroll reads the reconciled facts directly — hours, overtime, absence, leave — instead of a re-typed summary. Build earnings and deductions as formula-driven components with eligibility rules, preview a run before you commit it, and model a raise or a new allowance with what-if before anyone is paid.
Component engine · eligibility rules · preview & what-if · arrears · multi-step approval
Payslips are generated and cached as PDFs, in Arabic or English. Export a bank disbursement file in the WPS-style format your disbursing bank expects, track spend against departmental budgets, and let staff draw on pay they have already earned instead of taking an informal advance.
Payslip PDFs · WPS-style bank export · budget vs actual · earned wage access · loans
Every figure walks backwards. Any adjusted number traces to who changed it, when, and why — down to the original punch and the terminal that recorded it. That is the question an Egyptian labour inspection actually asks, and the reason the audit trail is a first-class feature rather than a log file.
Full lineage · immutable corrections · audit log · role-scoped access · anomaly history
The platform · every module, one database
Everything below ships in Flume and reads from the same records. No connector to buy, no nightly sync to babysit, no two systems disagreeing about who worked on Tuesday.
PILLAR 01
Explore in depth →The floor-level truth everything else is calculated from.
PILLAR 02
Explore in depth →A configurable engine, not a fixed formula you have to work around.
PILLAR 03
Explore in depth →What people are working toward, and what they can actually do.
PILLAR 04
Explore in depth →Proving that the people on the line are certified to be there.
PILLAR 05
Explore in depth →One continuous employee record, from application to final settlement.
PILLAR 06
Explore in depth →The half of HR that keeps people, not just counts them.
Built here, not localised later
Global HR platforms treat Egypt as a translation problem. Flume treats it as the specification. The rules below are configuration inside the product, kept current as thresholds change.
Compliance coverage
Command Center
Flume watches its own data. Detectors run continuously across payroll, attendance, leave and overtime, raise what looks wrong, and quietly close it again when the condition clears — so the list in front of you is only what is still true.
Three surfaces, one record
Role-scoped dashboards — self, team, company — with live attendance, workforce movement, turnover, payroll variance and open anomalies. Full administration for payroll, rosters, policies, branches and permissions.
Clock in, request leave and overtime, read a payslip, complete a course, give recognition, sign a document, browse the org chart — in Arabic or English, on the phone people already carry.
ZKTeco biometric devices pair to Flume and push punches as they happen, with fleet health, operation logs and per-device reporting. No manual export, no missing day.
Straight answers
We already have terminals. Do we replace them?
No. Flume pairs with the ZKTeco devices you have and starts reading them. The hardware you have already paid for becomes the front of the system rather than a box that exports a file once a night.
Our payroll has rules nobody else has.
That is the assumption the engine is built on. Pay is assembled from components you define with your own formulas and eligibility rules, so a shift allowance that applies to three grades on night shift is configuration, not a change request.
What happens when an inspector asks about one number?
You open the payslip line and walk it backwards — to the adjustment, its author and reason, to the reconciled day, to the punch and the terminal that recorded it. Nothing in that chain was overwritten to get there.
Half our staff barely use email.
They do not need to. For most of the workforce the interaction is a thumb on a terminal at the gate; anything beyond that lives in an Arabic mobile app with push notifications, not an inbox.
Book a demo
The fastest way to judge Flume is to run it against a period you already argued about. Send a month of punches and the payroll you produced from it, and we will show you the same month reconciled — including what the anomaly detectors flag.