Starting from May 1st 2025, the following changes will be applied to our service’s API, aiming to ensure the proper transmission of documents to the Independent Authority for Public Revenue (AADE).1.
Validation on the CPV Code field: This field must always be populated. If it is left empty (Null), the API will return a completeness error. (This applies only to B2G invoices.)
2.
Validation on fields using standardized AADE code lists/tables (e.g. InvoiceTypeCode, paymentMethodTypeCode, etc.):
When using such fields, they must always be submitted with valid, predefined values according to AADE specifications, regardless of the document type.
3.
Validation on the VAT Number (AFM) field:
All documents with CountryCode = GR must include a VAT number (AFM) that complies with the required format of 8 or 9 digits. In the case of retail transactions, when counterparty details are provided, the VAT number field must either be left empty or follow a compatible placeholder format (e.g. 000000000).
Invalid Counterparty VAT Number (AFM) for Country Code -GR-
A validation error will occur if the counterparty’s VAT number meets any of the following conditions:-It is shorter than 8 digits or longer than 9 digits.
-It starts with "EL" or "GR" and is not exactly 8 or 9 digits in lengthThe Counterparty VAT Number (AFM) is NOT validated when:
The countryCode field is missing.-The countryCode exists but is different from "GR".
-The document type is retail or classified as 8.2.
-The AFM field is empty.4.
Validation of POS Signature sent to AADE:
For documents that include PaymentDetails.PaymentMethods, if a PaymentMethod contains both PosInput and ProviderSignature, then the signature must match the one generated from the given PosInput.
5.
Documents of types 1.1, 1.6, 2.1, 2.4, 5.1 & 5.2 will be classified as B2G documents, provided that the Contracting Authority Code is filled in the file transmitted during the call.
Modified at 2025-06-13 13:32:39
