Why Greece’s Digital State Still Breaks at the Interfaces Between Justice, Tax and Civil Registry

Greece’s digital transformation is real, and in many places it is impressive. Platforms like gov.gr and the tax administration’s online services have reduced queues, standardised a growing number of procedures, and made routine interactions faster. Yet for expats and families navigating life events across borders, the most painful delays rarely happen inside a single portal. They happen in the gaps between institutions—where one authority’s “completed” step is another authority’s missing prerequisite.

The Greek state has digitised many tasks, but it has not fully digitised the journeys that citizens actually live through. A birth, a death, a marriage, a divorce, a move abroad, an inheritance—these are not single transactions. They are chains of legal and administrative consequences that cut across civil registry, courts, tax administration, banks, and property registries. The system breaks not because the state lacks websites, but because it lacks a reliable way to hand off responsibility from one institution to the next.

Most digital services in Greece are built vertically. Each authority digitises its own responsibilities, its own forms, and its own internal workflow. That approach produces visible progress: a tax declaration can be filed online; a certificate can be requested online; an appointment can be booked online. But the lived experience of bureaucracy is rarely vertical. It is horizontal, because life events do not respect ministerial boundaries.

In practice, a single event triggers obligations across multiple authorities, and each authority acts as if it is operating in a closed system. Civil registry records the event. Courts validate or certify legal consequences. Tax administration updates status, obligations and rights. Banks and registries require confirmation before acting. The citizen—often an expat at a distance—becomes the messenger carrying “proof” from one silo to another, even when each silo is already “digital.”

This is where the digital state breaks: at the interfaces. AADE may be technically digital, but it depends on upstream confirmations from civil registries and courts that still operate with delays, local discretion, and inconsistent formats. No API can compensate for a process that has no single owner and no enforceable sequence.

The fragmentation becomes clearer when you look at how responsibilities typically spread across the state. The issue is not that multiple institutions are involved; it is that their involvement is not orchestrated end-to-end.

The table reads like a normal division of labour. The problem is what happens between the columns. Each institution can be “done” with its part while the overall journey remains stuck, because the next institution either cannot proceed or will not proceed without a specific upstream output—sometimes in a particular format, sometimes from a particular office, sometimes after a particular internal update has actually propagated.

Birth registration abroad is a typical example of systemic delay. A child may be registered at a consulate, but the civil registry update may lag for months. Until that update is finalised, tax identifiers cannot be issued, health coverage cannot be activated, and digital identity remains incomplete. The family is not waiting for a single document; they are waiting for the state’s internal sequence to complete—without any mechanism to ensure that it actually does.

The experience is especially punishing because it is invisible. From the citizen’s point of view, the event has happened, the paperwork has been submitted, and the state is “digital.” From the state’s point of view, one subsystem is still pending, and the downstream systems are behaving correctly by refusing to act. The result is a paradox: the more “rules-based” the downstream digital services become, the more they will block citizens when upstream steps remain unresolved.

Deaths are even more complex because they trigger multiple consequences that are both legal and financial. A death typically requires deregistration in the civil registry, court-issued inheritance certificates, tax declarations and estate filings, and banking freezes and reactivations. Each authority waits for another to move first, and there is no central process owner to coordinate the sequence or resolve disputes about what constitutes “sufficient” proof.

This is how administrative paralysis becomes the default outcome. Families face months of uncertainty at precisely the moment when time, clarity, and legal certainty matter most. The delays are not simply frustrating; they can prevent access to funds, stall property-related actions, and lock heirs into a holding pattern where every step depends on a confirmation that is outside their control.

Inheritance cases expose the architecture most clearly. Courts certify heirs, but tax systems require specific formats and confirmations. Civil registries may not synchronise name changes or marital status correctly. Banks demand updated tax and registry confirmations before releasing funds. Each institution is acting rationally within its own mandate, yet collectively the system behaves irrationally because no one is responsible for the entire journey from death registration to asset transfer.

Greece has invested heavily in APIs and interoperability layers. This is necessary, and it is progress. But interoperability is not the same thing as orchestration. APIs move data; they do not own responsibility. They can transmit a status, but they cannot guarantee that the status will be produced on time, in a consistent format, or in a way that downstream institutions accept without discretionary interpretation.

When an inheritance stalls, the problem is often not missing data. The problem is that no system is accountable for completing the entire journey. Each authority exposes an interface and considers its task complete. The citizen or professional becomes the de facto process coordinator, chasing updates, aligning documents, and translating one institution’s output into another institution’s input.

Rejection is not an anomaly. It is the default outcome when documents are even slightly misaligned with the expectations of the receiving authority. In Greece, where document requirements vary not just by process but by individual tax office, the margin for error is extraordinarily narrow. Digitalisation without orchestration simply moves paperwork online. It does not create a functioning digital state.

What Greece lacks is not another platform or another form. It lacks an orchestration layer that treats life events as end-to-end processes rather than isolated transactions. Orchestration does not replace authorities. It connects them logically, tracks dependencies, and ensures that one completed step automatically triggers the next—or, at minimum, that the next step becomes unblocked without the citizen having to manually broker the handover.

In a mature digital state, the citizen should not need to understand which institution is “upstream” and which is “downstream.” They should not have to guess which certificate will be accepted by which office, or whether a registry update has propagated sufficiently for a tax change to be processed. The system should make the journey legible, sequenced, and accountable.

While Ellytic doesn't handle civil registry and justice systems directly, many prerequisites — like obtaining your AFM or getting documents certified — are exactly what Ellytic streamlines.