Greece myDATA 2.0.2: What Changes for Digital Goods Movement?

Greece has activated myDATA version 2.0.2, expanding the digital management of goods movements, deliveries, returns and receiving documents. The update affects ERP systems, e-Invoicing providers, carriers, recipients and businesses preparing for the next mandatory phase.

The Greek Tax Authority (AADE) put myDATA version 2.0.2 into production on September 10, 2026, introducing additional functionality for the digital monitoring of goods movements.

This is primarily a technical upgrade to the existing Digital Goods Movement framework, rather than a separate new reporting obligation. Its timing is nevertheless relevant because Greece is approaching the next stage of mandatory implementation. From October 12, 2026, Phase B1 requires the transmission of data concerning loading, transshipment, receipt and the quantitative and qualitative control of goods for businesses within the scope of the Digital Goods Movement regime.

One of the first changes is the expansion of document types that may also function as documents containing goods-movement information. Version 2.0.2 adds types 1.4, 3.1, 3.2 and 11.5 to the relevant movement functionality.

These include the Sales Invoice for sales on behalf of third parties (1.4), acquisition documents covered by types 3.1 and 3.2, and the Retail Sales Receipt for sales on behalf of third parties (11.5). The Tax Authority distinguishes these documents, which may contain both value and movement data, from dedicated movement documents that contain movement information without transaction value.

For retailers, this distinction matters because a retail or invoice document may in certain cases also carry the information necessary to document the movement of inventory rather than requiring the process to be treated separately.

Version 2.0.2 also changes the lifecycle and statuses of movement documents, allowing the myDATA system to represent more stages of the physical movement and its completion.

The Tax Authority has expanded the treatment of Quantity Receipt Notes, represented in myDATA by document types 10.1 and 10.2.

Version 2.0.2 allows a 10.1 document to be correlated with a 10.2 document and permits both types to be cancelled through the ERP channel. E-Invoicing providers receive a new CancelReceivingNote method for handling these cancellations. The Tax Authority has also added a mandatory field identifying the reason for issuing the Quantity Receipt Note.

Quantity Receipt Notes should not be confused with documents that accompany goods during transport. The Tax Authority explains that types 10.1 and 10.2 are issued after completion of a movement in order to document the receipt of inventory, whereas digital Delivery Notes accompany the inventory during transportation.

ERP and provider implementations therefore need to distinguish clearly between initiating a movement and recording the subsequent receipt of the goods.

The update also introduces additional functions for carriers.

Through RegisterTransfer, the carrier can now declare the packaging associated with a movement when transportation begins or during a transshipment. This gives myDATA additional information about the physical handling of the shipment as it progresses through the supply chain.

Version 2.0.2 also formally supports a PARTIAL outcome where the carrier has delivered only part of the goods. The Tax Authority specifies that this value may be used only when the relevant call is made by the carrier and represents a partial delivery performed by that carrier.

Additional validation has been introduced in ConfirmDeliveryOutcome. The system now checks that the party making the call is actually the carrier associated with the specific movement document. This strengthens the link between an electronic action and the participant authorised to perform it.

For retail chains and other businesses using external logistics providers, this makes the correct identification and technical correlation of the carrier more important within ERP, logistics and myDATA integrations.

Another addition is the ConfirmDeliveryReturn method. It is called by the issuer of a movement document to declare completion of the movement in specified return scenarios and subject to the conditions defined by the technical documentation.

The technical documentation also introduces and adjusts movement statuses to support the return process. This allows the system to distinguish more accurately between a normal delivery, failed or partial delivery and goods moving back as part of a return.

The existing GetDeliveryNoteStatus function has also been expanded. The status of a movement document can now be retrieved using the QR URL parameter, providing another way for systems to identify and check the progress of a movement.

The Tax Authority has updated its own applications alongside the APIs.

Impact on retailers, ERP providers and logistics processes

The practical effect of v2.0.2 is that the goods-movement process becomes more event-based. Systems increasingly need to follow not only the original issuance of a movement document but also what happens afterwards: commencement of transport, transshipment, receipt, partial delivery, rejection, return and completion.

For retailers with warehouses, distribution centres, store transfers or external carriers, ERP and logistics systems should therefore be able to maintain the correct document relationships and identify which party is permitted to perform each action.

This is particularly relevant ahead of October 12, 2026, when Phase B1 becomes mandatory and loading, transshipment, receipt and inventory-control data become part of the compulsory digital monitoring process.

What should affected businesses do?

Businesses should confirm that their ERP, e-Invoicing provider or other myDATA integration supports version 2.0.2, including the revised document lifecycle, new cancellation and return methods, partial-delivery treatment and the additional validation rules.

Retailers should also review workflows involving carriers, goods receipt, rejected deliveries and returns so that responsibility for each myDATA action is correctly assigned. Testing is particularly advisable for businesses preparing for mandatory Phase B1 reporting from October 12.

The main importance of myDATA 2.0.2 is not the introduction of another reporting system, but the greater digitalisation of the physical goods-movement lifecycle. The update connects documents, participants and delivery events more closely, which means ERP, warehouse and logistics processes need to reflect what actually happens to the goods from dispatch through final delivery or return.

The main source for this article is the official Tax Authority press release of September 9, 2026. Source

Ivana Picajkić, Medior Legal Consultant at Fiscal Solutions

Linkedin profile