Skip to content
Free for up to 5 employees — face check-in in minutes.Start free →·Book a demo →
Integrations & API

Connect NCheck to the systems you already run.

Attendance data is only useful once it reaches payroll, HR and access control. NCheck gives you three ways to get it there: file exports, a REST API and event triggers on the device itself.

Read the API docsTalk to us
NCheck attendance data flowing to payroll and HR systems

Three ways to integrate

Every deployment — cloud or on your own server — offers the same three routes for getting data in and out of NCheck. Most companies start with exports and add the API when they want to automate.

ExportsAttendance and work-hour reports as CSV or Excel, ready for payroll import. REST APIRead events, users and reports, and manage devices and enrolments from your own software. Device triggersRun an action on the check-in device the moment a person is verified — open a door, call a URL.

Payroll and HR exports

The Total Work Hours report sums each employee's verified time by day, week, month or a custom pay period, and exports it as CSV or Excel. Times can be shown as hours in decimals, which is what most payroll systems expect. Because every record comes from a biometric match, the hours you import are the hours that were actually worked.

Step-by-step guides for two common payroll systems:

Tally ERPExport work hours and format them as attendance vouchers. QuickBooks DesktopExport work hours and convert them to IIF for import. All report typesWhat each attendance report contains and when to use it.

Other systems. Any payroll or HR product that imports CSV can take the same file. If yours needs a specific column layout, the report export lets you choose the fields and order.

REST API

The NCheck server exposes a REST API so your own applications can work with attendance data directly: list users and their groups, read check-in and check-out events, pull reports, register devices and manage enrolments. The API is identical on cloud and on-premises, so an integration built against one deployment works on the other.

Typical uses are syncing employees from an HR system, pushing daily hours into payroll automatically, or feeding live presence into a dashboard or ERP.

Read the developer manual and API reference →

Event triggers on the device

Each check-in device — a terminal, a shared tablet or an IP camera — can run an external application or call a URL the moment a person is verified. This is how NCheck controls physical access: the device, not the server, signals a relay over MQTT, HTTP or Bluetooth to open a door, turnstile or vehicle barrier. It also works for lighter automations, such as posting to a chat channel or logging to a third-party system.

Triggers are configured per device and per event (check-in, check-out, failed match), so a warehouse gate and a reception tablet can behave differently. See how access control works →

Same integration, either deployment

Cloud customers reach the API at their cloud.ncheck.net tenant. On-premises customers reach it on their own server — including in offline or air-gapped networks, where exports and device triggers keep working without any internet connection. About on-premises deployment →

Need a hand?

API integrations are usually built by an integrator or an in-house developer. If you'd like us to review your plan, recommend an approach, or put you in touch with a partner who has done it before, get in touch.

Talk to us

Product names mentioned in the guides belong to their respective owners and are used only to identify the systems the exports are formatted for.