An office building in The Hague has Paxton Net2 for the doors and a separate barrier system for the car park — two systems, two databases, double the admin for every new employee. How connecting ANPR to Paxton fixes that, and what it concretely means for the facilities manager.
Revtek · 15 April 2026
Most office buildings with a car park follow the same pattern: there's an access control system for the doors — Paxton, HID, Nedap, or a variant — and a separate system for the car park barrier. Sometimes the barrier system is still manual: a shared code or a stack of transponders.
The result is that a new employee needs to be registered in two places. And when they leave, they need to be removed from two places — of which the car park is rarely first. This is precisely the kind of administrative slip that lets ex-employees access the car park for months after they've left.
The Revtek integration with Paxton Net2 and Paxton10 runs via the Paxton API. When an employee is created in Paxton and their plate is added to their profile, Revtek automatically synchronises that plate to the ANPR whitelist for the car park. No double entry, no separate parking platform to maintain.
The same applies to removal: as soon as an employee is deactivated or deleted in Paxton, their plate disappears automatically from parking access. That's the side that delivers the most value — not the creating, but the removing at exactly the right moment.
The integration synchronises plate rights based on Paxton users. What you manage separately are the parking-specific settings: time windows (when does someone have access?), capacity limits per time block, and visitor registration for people not in Paxton.
Visitors go through a separate channel: a WhatsApp registration flow or a QR code at the entrance. That logs their presence without them needing to be created in Paxton. More on that visitor process on the office page.
Paxton Net2 is the on-premise system, Paxton10 is the cloud variant. Both have an API that enables the integration, but there are small differences in how real-time the sync is. With Paxton10 the connection is generally faster because the API is always reachable; with Net2 it depends on the network configuration on site.
In practice you notice little difference as an administrator — synchronisation completes within seconds for both. The choice between Net2 and Paxton10 is made on other grounds: existing infrastructure, preference for on-premise or cloud, and the scale of the building.
The most direct gain: no separate parking platform to maintain. One system — Paxton — is the single source of truth for who has access to the building and the car park. That saves an average of two to three hours of admin per month at a complex with fifty to a hundred employees.
Added benefit: the parking log is now linked to employee names rather than anonymous plate strings. If there's a question about when someone was on site — from HR, from security, or for an incident report — the answer is available in a few clicks.
More on the full integration options with Paxton on the Paxton integration page.
Book a free demo and find out what Revtek can do for your situation.
Book a demoOr email info@revtek.nl