Phase B of the Digital Dispatch Note

The mandatory implementation date for Phase B of the Digital Dispatch Note has been announced as May 1, 2026. At the same time, since early December 2025, the Independent Authority for Public Revenue (AADE) has activated the relevant functionalities in the Production environment, allowing liable parties who wish to begin earlier to start submitting the required data.

Phase B introduces several significant changes for obligated businesses. This time, it does not merely involve the obligation to transmit certain “data” to AADE for the purpose of digitizing the Dispatch Note. Instead, it introduces new procedures into the day-to-day operations of all parties involved in transactions.

More specifically, it establishes a workflow in which the sender, the recipient, and even intermediate carriers must participate and collaborate digitally. This represents a fundamental shift compared to what businesses were familiar with under myDATA, where actions were unilateral and self-contained — for example, “I send a sales invoice” or “I receive a purchase invoice.” After submitting an invoice to myDATA, no further action or continuation of the transaction was required (aside from internal controls unrelated to AADE).

The Digital Dispatch Note enters a new era. Phase B is not just about sending data to AADE. It introduces a complete workflow that follows goods from dispatch to final delivery — digitally and in real time.

Since the implementation of a workflow is now required for core business transactions, the only logical place for this to be realized is within the ERP software that a business already uses (or needs to acquire). In summary, the required steps are:

• Initial submission of the Dispatch Note to myDATA (Phase A, already in effect)

• Initiation and recording of the transportation by the sender/seller (this is where the new Phase B requirements begin)

• Recording of loading and initiation of transportation by each intermediate carrier(this marks the first direct impact on carriers’ systems and may require mobile applications)

• Confirmation of receipt (or rejection) by the final recipient (customer)

• Other supporting actions (such as cancellation, failed transaction, etc.)

For the first time, businesses are required to record business events in their ERP systems that may not have been tracked until now — and to report these events to AADE.

ERP systems move to the center of compliance. The new requirements cannot live outside your core systems. They must be embedded in the ERP that already supports daily operations.

It is therefore essential to promptly make the necessary adjustments to organizational operations in order to:

• Understand and document the actual operational steps as required by AADE

• Identify the ERP system points that need customization or adjustment to capture these events

• Connect these points to the appropriate AADE web services

• Implement monitoring and control procedures for exception handling

• Train users to properly follow the new processes

  
  

There is no doubt that this constitutes a new IT project within the organization. As such, it must be approached with the appropriate structure and planning, including sufficient time for testing and adaptations.

This time, everyone is involved. Sender, receiver, and even intermediate carriers must participate in a shared digital process. Transactions are no longer unilateral — they are connected.

E-ON INTEGRATION can support you:

• Through its cloud ERP solution, E-ON RIX, which is ready to model all relevant business processes in simple, structured steps

• Through its integrated Electronic Invoicing Service Provider (ΥΠΑΗΕΣ), certified by AADE, allowing businesses to address electronic invoicing requirements with a single product and service

• Through its extensive experience with myDATA and related requirements, having been a pioneer in myDATA integration since the early design stages back in 2018!