Technical specifications – Versions of myDATA

a

 

 

New version v1.0.12- what's included:

 

1. Decision 1128/2025 Electronic invoicing B2B, B2C, B2G (Relates to an E.I. Provider)

Enrichment of myDATA format with field downloadingIncoiceUrl - transmission of url from E.I. Provider where the recipient of the document will be able to receive the document by calling it and defining a parameter

url call parameter:

  • /pdf            --> download to pdf (default parameter in case no parameter is included in the url call, then the url will return the document in pdf format)
     
  • /myDATA   --> download in Detailed myDATA format - InvoicesDoc_detailed.xsd 
    -all lines of the document in detail per item/service,
    -each line will also include the item/service code,
    -the taric code (if available),
    -the item/service description,
    -the information on the classifications is not included,
    -for reasons of convenience and consistency, the data should be in accordance with the currently applicable InvoicesDoc_detailed.xsd InvoicesDoc_detailed.xsd
     
  • /EN16931  --> download in European Standard (ELOT EN 16931)
     

the url (downloadingInvoiceUrl) should be used to create the QR Code that is printed on the documents issued through an E.I. Provider.

it will become mandatory to fill in downloadingIncoiceUrl  
 

2. Shipping Note

Reverse Movement - Possibility to issue 9.3 Shipping Note with the indication "Reverse Movement" - filling in the Reason for Issuing Reverse Movement

1 - NOT OBLIGED TO ISSUE 
2 - REFUSAL OF ISSUE/NON-ISSUE DUE TO CLERICAL ERROR
3 - INTRA-COMMUNITY ACQUISITION
4 - THIRD COUNTRY ACQUISITION
5 - REVERSAL OF OBLIGATION
 

Issuance of Movement Documents

  • in the case of an E.I. Provider, downloadingInvoiceUrl should be used to create the QR Code that is printed on the documents
  • in the case of ERP, one should use the qrCodeUrl which is returned upon successful call of SendInvoices to create the QR Code that is printed on the documents
     
     

3. Decision 1112/2025 article 6 - Declaration of data issuance via a Provider or Proprietor

  • Creating a data release statement via a Provider or Proprietor - SendStatement Method
  • Recall of a data issuance statement via a Provider or Proprietor - RecallStatement Method
  • Receiving transmitted data issuance statements via a Provider or Proprietor - RequestStatements Method


 

  1. Upgraded SendExpensesClassification method
  2. expensesClassification-v1.0.6.xsd
  3. Εnrichment of RequestDocs Method, return of deviation/rejection information from counterparty
     

 

Examples of xml transmission:

  1. Sales invoice with self-billing
  2. Sales invoice with taxes stated at document level
  3. Sales invoice with taxes stated at document line level
  4. Product invoice with taxes stated at document line level
  5. Product invoice with taxes stated at document line level
  6. Sales invoice (composite) stated at document line level
  7. Sales invoice / Sale on Behalf of Third Parties Type of invoice  
  8. Sales Invoice / Third-party Sales Settlement – Fee from Third-party Sales with taxes stated at document line level
  9. Sales Invoice / Third-party Sales Settlement – Fee from Third-party Sales with taxes stated at invoice level
  10. Invoice for Services Provided with taxes stated at invoice level
  11. Correlated credit note
  12. Invoice – Intra-community acquisitions
  13. 13. Payroll with taxes (withheld taxes / solidarity contribution) stated at document level
  14. Depreciation

 

Older Versions: