Keep the systems you already paid for
Klok does not ask you to rip anything out. The biometric machine stays on the wall, your accountant keeps working in the package they know, and the data moves between them without anybody retyping it.
Six ways data moves in and out
Biometric Devices
Export the punch dump from the device you already own and load it into the attendance register. Rows import one at a time, so a thousand-row file with three bad rows brings in nine hundred and ninety-seven and tells you which three it refused, and why.
Your Other Systems
A token-authenticated REST API covers employees, attendance, leave and claims, so an ERP, a plant system or an in-house tool can read and write without a person in the middle.
Accounting And Tally
Payroll, statutory and register output downloads as CSV or XLSX in the shape your accounts team already posts. Not a live connector - a clean file, on time, every month, with nothing re-keyed.
WhatsApp And Email
Payslips, approvals and reminders reach people on the channel they actually read, sent from your own company mailbox rather than a shared sender nobody recognises.
One Sign-In
If you run more than one BeyondBox product, people move between them on a single signed session instead of a second password to forget.
Bulk Import
Employees, salary structures, leave balances and past attendance come in by spreadsheet, validated before anything is written - so a bad column is a message, not a mess to unpick later.
What we mean by an integration
Plenty of software claims to integrate with everything. In practice that often means an export button and a hope.
We would rather be exact, because the difference decides who does the work every month. There are three honest levels, and Klok tells you which one you are getting.
A file that imports cleanly. Your biometric device already writes a punch dump. Klok reads it row by row, applies your shift, grace, late-mark and overtime rules, and shows you exactly which rows it could not accept. An import that half-works and says nothing is worse than no import at all, because the gap gets trusted.
An API you can build against. Token-authenticated, covering the records that matter: people, punches, leave, claims. If your ERP is the system of record for headcount, it stays that way, and Klok hands attendance and payroll input back.
A file that posts. Payroll output lands as CSV or XLSX shaped the way your accounts team posts a journal. We are not going to call this a Tally connector, because it is not one. It is the right file, in the right shape, on the right day.
If what you need is not on this page, tell us the system and which way the data has to travel. That is usually a short conversation rather than a project.
Usually the same afternoon
Bring your list
Employees and salary structures import from a spreadsheet, validated before a single row is saved.
Point the device at it
Export from your biometric machine exactly as you do today and load the file. The register fills in with your rules already applied.
Take the output
Run payroll, download the journal file, post it in your accounting package. Nobody retypes a number.
Integration questions we actually get
Do I have to replace my biometric machine?
No — keeping it is the point. The device on your wall already captures punches perfectly well; what it cannot do is apply your shift, grace, late-mark and overtime rules or feed payroll. Export its punch file exactly as you do today and import it: rules apply on the way in, rows that fail are reported with reasons, and the machine keeps earning its keep. You are not running two attendance systems — you are finally finishing the one you have.
Is there a live Tally connector?
No, and we would rather say so here than let you find out after you have paid. What exists is payroll and statutory output as CSV or XLSX, shaped the way an accounts team actually posts a journal — for most businesses that is a two-minute monthly step, not a workflow. If a live connector is a hard requirement, tell us before you buy; if clean files on time solve the real problem, that is what we are honestly offering.
Can our ERP stay the system of record for employees?
Yes. The REST API is token-authenticated and covers employees, attendance, leave and claims in both directions — your ERP pushes joiners and exits, Klok hands back attendance and payroll input. The pattern to avoid is two systems both believing they own the employee master; decide which one is the record, point the API accordingly, and the reconciliation meetings stop happening.
What happens to rows that fail an import?
They are reported with the reason, never silently dropped. Imports run row by row rather than all-or-nothing, so a thousand-row device dump with three bad rows brings in nine hundred and ninety-seven and hands you a list of exactly three problems to fix. The alternative — an import that half-works and says nothing — is how bad data gets trusted, and it is the specific failure this design exists to prevent.
Is the API charged separately? Is it documented?
It is part of the product, not a line on the invoice. Documentation is not published yet — a fair criticism we would rather acknowledge than deflect — so before you build against it, talk to us: we will give you the endpoint reference, the auth model and rate limits, and tell you which endpoints are stable and which are still moving. That conversation costs nothing and prevents building on sand.
How long does connecting everything actually take?
Usually an afternoon, honestly. Employee list and salary structures import from spreadsheets with validation before anything is saved; the biometric export loads the same day; payroll output is a download from the first run. The week-long integration project mostly does not exist here because the integration surface is deliberately narrow: files that import cleanly, an API for what must sync, files that post.
What about WhatsApp and email?
Payslips, approvals, OTPs and reminders go out over WhatsApp through Meta's business platform, and email sends from your own configured company mailbox where you set one — so messages arrive from a sender your staff recognise rather than a shared address nobody trusts. The channel your workforce actually reads is the one the product treats as primary.
Tell us what you are running
Bring the device model and the package your accountant uses. We will tell you honestly what connects today and what does not.