Czech E-Government Integrations
We connect software to ARES, data boxes (datové schránky), the contract registry and the National Electronic Tool (NEN) — systems most studios in the Czech market don't offer as a named service. Our ARES integration runs in production; Czech invoicing formats, payment matching and health-insurer billing documents run in our product Innea Pro.
What can we connect?
We can design and build connections to ARES (company verification by IČO), data boxes (receiving and sending messages), the contract registry and NEN. Fakturoid and the GoPay or Comgate payment gateways are commercial services, not state systems, but we connect those too.
Where does this run in production?
In Innea Pro, the practice-operations system for therapists that shares its code with Innea. At registration it verifies companies by IČO through ARES; it issues invoices under Czech rules with a QR payment (SPAYD) and ISDOC/UBL export, matches payments from Fio, takes payments through Comgate, exports to Fakturoid, iDoklad and Pohoda, generates health-insurer billing documents including KDAVKA/FDAVKA batches, syncs with Google Calendar and sends SMS reminders through BulkGate. Public-procurement data is read by an in-house tool that processes TED and ISVZ.
What we don't run in production yet, we say plainly: data boxes, the contract registry, NEN and GoPay we build to order — we can design and connect them, but we cannot point to a running product.
Frequently asked questions
Can you read data from ISVZ and NEN?
From ISVZ yes, from NEN not yet. An in-house tool reads public tenders from TED and ISVZ; NEN is a separate register we have no production connection to, and we design the integration around what you need to read from it or write into it.
Can you handle two-way communication with a data box?
Yes, receiving and sending — but as custom work, not an off-the-shelf module: we don't yet have a two-way data-box connection in any product we run. We build it with tests and monitoring, the same way as invoicing and insurers in Innea Pro.
What if the state changes an API format?
Automated tests against the real formats and monitoring catch the change, so we know about it before it does much damage, and the fix is routine maintenance, not an emergency. Changes at short notice are part of how we design integrations with state interfaces from the start.
How do you handle outages of state interfaces?
With a queue and retries: the request is stored, resent after the outage, and the process does not stop. An interface outage then means a delay, not lost data — and monitoring tells you it happened before your client does.