Greek compliance, data and access
Compliance and data handling in Serat: AADE tax identifier validation, Greek e-invoicing, EU hosting, role-based access and signed integration requests.
Software sold to Greek businesses has to deal with Greek obligations rather than treat them as a localisation afterthought. This page covers what Serat handles and how your data is treated.
Greek compliance
ΑΦΜ validation. Tax identifiers are checked against the AADE registry, so a customer or client record starts from a real, correctly formatted number.
Electronic invoicing. Invoices are issued electronically in line with Greek requirements.
WRAPP. Supported as part of the same compliance surface.
The point of building these in is that they stop being a monthly scramble. A correct tax number captured at the start prevents an invoice problem at the end.
Where data lives
Serat is built and hosted in Europe, and customer data stays within the EU. Documentation media and business data are backed up with checksums, and restoration is tested rather than assumed.
Access control
Access is role-based. The clearest example is the analytics assistant: it is restricted to administrator roles because a plain-language interface to business data is effectively access to all of it. The same reasoning applies elsewhere, so a till operator does not hold the ability to rewrite the catalogue.
Integration access
Connections between services use access controls appropriate to their purpose. An administrator manages which integrations are connected; access to one feature does not automatically grant access to another. If a connection stops working, check its status in the relevant settings area and ask an administrator to review it.
This website
The marketing site you are reading is separate from the product. Details about enquiries and optional analytics are in the privacy notice.