02-07-2026 | myDATA v2.0.2 (UAT)

Added

1. New Delivery Note Invoices

For delivery note invoices (INV-DEL.NOTE), myDATA now supports additional document types that can also be issued as delivery notes. This is indicated through the JSON field: IsDeliveryNote: true – specifies that the document is also treated as a delivery note.

Transactions (B2B – B2C)	Indication of Delivery
1.4 - B2B Sale on Behalf of Third Parties _ Delivery of Goods	Yes (myDATA v2.0.2)
3.1 - Proof of Expenditure (non-liable Issuer) _ Delivery of Goods	Yes (myDATA v2.0.2)
3.2 - Proof of Expenditure (denial of issuance by liable Issuer) _ Delivery of Goods	Yes (myDATA v2.0.2)
11.5 – B2C Retail Sales on Behalf of Third Parties _ Delivery of Goods	Yes (myDATA v2.0.2)

2. New JSON fields:

The fields withoutDigitalTransportTracking and nonObligatedRecipient are supported for Delivery Note Invoice and Delivery Note transactions.
The fields receivingNotePurposeCode and otherReceivingNotePurposeTitle are used exclusively for document types 10.1 and 10.2.

JSON Field	Type	Max Length	Description
`withoutDigitalTransportTracking`	boolean	—	Without Digital Transport Tracking
`nonObligatedRecipient`	boolean	—	Non-Obligated Recipient (transport-document related)
`distributionDetails.receivingNotePurposeCode`	integer	1–7	Receipt Note issuance reason code
`distributionDetails.otherReceivingNotePurposeTitle`	string	150	Receipt Note issuance reason Title/description

3. New Code list for receivingNotePurposeCode

Applies to Quantitative Receipt Note types 10.1 and 10.2:

Code	Description
1	QRN — Issuer not obliged to issue
2	QRN — Refusal to issue / accidental failure to issue
3	QRN — Intra-community acquisition
4	QRN — Acquisition from a third country
5	QRN — Quantity verification
6	QRN — Non-delivery / partial delivery
7	QRN — Other cases

4. New Cancel API /cancelReceivingNote

For Quantitative Receipt Note ( QRN 10.1 and 10.2) transmitted via Provider mode.

5. Portal Cancel button

The Portal Cancel button now supports cancellation of document types 10.1 and 10.2, for documents transmitted via both Provider mode and ERP mode.

19-03-2026 | OAuth 2.0 authentication & Invoice/secure (Encryption)

1. Αdded a new `OAuth 2.0 authentication`

The service now provides secure access through OAuth 2.0 access and refresh tokens issued by an authorization server, enabling seamless and reliable integration with third-party systems for authorization API requests (e.g., invoice/json).

This update includes:

1.1 client_credentials

API request for authorization (access token and refresh token) using the Client Credentials flow

1.2 refresh_token

API request for refreshing the OAuth access token.

2. Αdded a new API Request `invoice/secure`

The specific API call was introduced for security purposes, ensuring that the payload is transmitted entirely in encrypted form using PGP Encryption, in order to safeguard sensitive data.

17-02-2026 | e-mail as an attachment (customer PDF) & Uniqueness Validation

When the customer chooses to upload their own PDF for invoice preview/visualization in the portal, and the invoice is sent via email as an attachment (using the sendAsPdf = true field, sent through the portal), the recipient will receive the customer-uploaded PDF as the attachment instead of the default system-generated form that was previously sent.

This functionality will apply provided that one of the following conditions is met:

Parallel PDF Viewing (urlPDF)

Invoice Document Upload (Invoice/File)

📌

In case the customer uses the Invoice Document Upload (Invoice/File) call, it is mandatory to include the following field: "notificationDelay": 5 within the additionalDetails entity of the JSON.

Additional analysis on UID Uniqueness Validation for invoices

02-02-2026 | Delivery Notes and B2G Updates

1. Delivery Notes

1.1 Delivery Notes, Updates and Changes

9.3 Reverse uploaded in apidog, in delivery notes section JSON sample.

1.2 New Delivery Note Types of Transfer Documents

Code	Document Type
9.1	Associated Dispatch Note
9.2	Consolidated Dispatch Note
10.1	Associated Quantitative Receipt Note
10.2	Non-Associated Quantitative Receipt Note

1.3 New Fields for Delivery Note Invoices & Delivery Notes

deliveryNoteMarks – Associates the delivery note marks within invoices.
Exceptions: Not applicable for types 1.6, 2.4, 5.1, 9.1, 10.1 (use correlatedInvoices), and 8.4, 8.5, 8.6 (use multipleConnectedMarks)

packingsDeclarations – Declarations of Transfer Packings

toWeigh – Indicator for weighing

movePurposeLineCode – Transfer purpose at line level

otherMovePurposeLineTitle – Title for other transfer reason at line level

1.4 Changes / Deletions

Removal of the field otherTransportDetails

Updated descriptions: These fields will relate to the planning (Estimated) of the movement and not to the actual values:

dispatchDate

dispatchTime

vehileNumber

1.5 New ERP Methods (MyData Delivery Lifecycle)

RegisterTransfer – Method to declare the start or transfer of a movement by the carrier

ConfirmDeliveryOutcome – Method to declare the delivery outcome by the carrier or recipient

RejectDeliveryNote – Method for total rejection of a movement by the recipient

GetDeliveryNoteStatus – Method to retrieve the status and history of a Dispatch Note

GenerateGroupQRCode – Method to generate a group QR Code for multiple Dispatch Notes

RequestGroupQRDetails – Ability to retrieve individual QR Codes contained in a Group QR Code

2. B2G Invoicing v8.2 | EKAPY

Regarding the EKAPY announcement and Greek B2G Electronic Invoicing Format v8.2 (PEPPOL BIS 3.0 CIUS page:160), suppliers transacting with the National Central Healthcare Procurement Authority must correctly complete the mandatory fields BT-44, BT-10, BT-160, and BT-161, following the specified instructions and deadlines.

3. Mass Print-available functionality

The “Bulk Printing” functionality is now available, allowing users to print invoice PDFs in batches of up to 20. Additionally, an option has been added to print all selected invoices into a single combined PDF file.

!Please note that:
the order of the PDFs is based on the date issued.
invoices with Parallel view (invoice/file) are not included

The following rules apply:

Users must select the invoices they want to print.

The “Select all” option selects only the invoices currently visible on the screen. To view and select all invoices, use “Load more”.**

01-12-2025 - Production Version

1. Unified Invoice Download URL Structure

Our platform’s invoice retrieval mechanism has been aligned with IAPR’s myDATA v1.0.12 specification and expanded with improved routing logic.

1.1 Expanded Download Formats

All invoice documents now support the following download formats:

Endpoint	Description
`/`	Commercial visualization of the document
`/mydata`	Detailed MyDATA XML (InvoicesDoc_detailed.xsd)
`/pdf`	PDF rendering of the invoice/document
`/EN16931`	European Standard format (ELOT EN 16931)

These formats mirror the capabilities of IAPR’s new downloadingInvoiceUrl introduced in v1.0.12.

2. Reverse Movement Implementation (myDATA v1.0.12)

The Reverse Movement workflow introduced by IAPR in version 1.0.12 is now fully supported.

2.1 Reverse Delivery Note Flag

We now support the new IAPR-required flag:

reverseDeliveryNote = true
For implementation details, refer to: Reverse Movement

2.2 Purpose Codes

We also support the mandatory IAPR-defined field:

reverseDeliveryNotePurpose, including:
1 - NOT OBLIGED TO ISSUE
2 - REFUSAL TO ISSUE / FAILURE TO ISSUE BY MISTAKE
3 - INTRA-COMMUNITY ACQUISITION
4 - THIRD COUNTRY ACQUISITION
5 - REVERSE CHARGE

3. myDATA Compatibility Enhancements

To maintain compliance with IAPR myDATA v1.0.12:

Updated schema handling based on the new XSD files.

Enhanced invoice download URL generation to align with IAPR’s new QR-code and deep-linking rules.

Improved MyDATA-format generation for accurate /mydata XML responses.

Improved support for producing EN16931-compliant documents for standardized EU invoicing.

4. IRIS Payments — Mandatory Support (EFT/POS Only)

To comply with new regulatory requirements, our system now supports mandatory IRIS payments through EFT/POS terminals. For more information you can click here: IRIS Payments

4.1 Mandatory IRIS Acceptance

Businesses are required by law to support IRIS payments.
Our platform now fully supports IRIS payment registration, tracking, and compliance flows.

4.2 IRIS via EFT/POS Terminal

The payment is initiated through a physical EFT/POS device, which manages:

IRIS payment initiation

Authorization

Confirmation

5. Summary of Improvements

This release introduces:

A unified and simplified invoice-download system compliant with myDATA v1.0.12.

Full support for IAPR’s Reverse Movement workflow.

Updated schema mappings, validations, and XML structures via the newest XSD files.

Standardized document export formats including MyDATA XML and EN16931.

Full compliance with IRIS payments via EFT/POS, as mandated by current regulations.

22-08-2025 - Production Version

➕Αdded

Add support in the default form to display the vatPaymentSuspension: true field on the document.

The TipAmount field under PaymentDetails >> PaymentMethods will now be displayed whenever it is populated.

Two new objects, deliveryOriginDetails and deliveryDestinationDetails, have been added to the distributionDetails object. More information is available in the Invoice/json request regarding the schema. For the functionality you can learn more here: Delivery Notes Documentation.

In document type 8.6 Restauration Order Forms, a new validation was added regarding Internal Document ID.

🔄Changed

The LegalMonetaryTotal.PrepaidAmount field in PEPPOL is now populated with the value from Summaries.TotalPaidAmount. This amount is also displayed in the default form.

Swagger URLs (Demo & Production) now redirect to the new landing page, which provides navigation to either the service’s technical documentation or the Support Portal.

✨Improved

The cancellation process for type 9.3 Delivery Notes now aligns with the transmission method. Delivery Notes sent via Certified Provider Mode are cancelled using cancelDeliveryNote, while those sent via ERP Mode are cancelled using CancelInvoice. The portal’s cancellation button handles the correct request automatically, requiring no further action from the user.

Users can now export Restauration Order Forms in Excel format, with a new date range, supporting up to 31 days.

In document type 8.6 Restauration Order Forms, the Excel export now includes a “Cancelled by” column to provide detailed reporting for forms that are cancelled instead of closed.

General Improvements occured in the Bearer Token Authentication functionality. More information: Bearer Token Authentication.

Updated Restauration Order Forms (MyDATA Type 8.6) with general UI improvements for better visibility, usability and consistency.

Updated POS Transactions with general UI improvements for better visibility, usability and consistency.

🛠️Fixed

Broken "All Time" filter functionality in Incoming Invoices – filters now work as expected.

Resolved an issue where duplicate F&B document transmissions caused related records to remain open. All affected documents are now correctly closed and data consistency has been restored.

Addressed an issue where the PDF URL field (A28) for Atlantis ERP was populated during testing but not displayed in the corresponding document view.

Uploaded attachments on the Portal now retain their original language in file names instead of being converted to English characters.

10-07-2025 - Production Version

➕Αdded

Email Notification functionality for Soft Reject Statuses in B2G invoices (check Portal Documentation).

⬆️Improved

The Export Data feature in Outgoing Invoices (Beta) has been updated to support CSV files, removing the previous .xlsx limitation. The functionality of Export Data if you use the checkboxes to select specific documents from the grid, remains the same and exports .xlsx.

🛠️Fixed

Outgoing B2G Documents now display the correct status icon in the Outgoing Invoices Page.

The display of the H251 field (Soft1 Configurator) in the Provider form.

Clearance time for MyData type 8.6 documents updated on the portal.

Form editor icon is not visible to non-admin users.

Fixed issue where recipients with Viber were incorrectly receiving SMS messages.

In POS Receipts, the behavior of the “More” button.

The behavior of the “Leave company” button.

12/06/2025 - UAT Version -> 30/06/2025 Production Version

➕ Added

cancelDeliveryNote Endpoint /Invoice/cancelDeliveryNote
Allows cancellation of a submitted Delivery Note (type 9.3) via a certified Provider.

New myDATA Document Button
Added to the public document link: redirects to IAPR's official record.

Validations for cancelDeliveryNote: Delivery Notes Documentation

Disallows cancellation if not a Delivery Note (type 9.3)

Disallows cancellation if already canceled

Disallows cancellation if not submitted via Provider

New MovePurposeCode 20: Delivery Notes Documentation
Transfers / Couriers (Μεταφορές - Ταχυμεταφορές)

Special Line Type Support Delivery Notes Documentation
Enabled use of Rec_type 6 ("Gift Voucher – Gift") in supported documents, even with zero value.

New transmissionFailure Value 4: EliseCoreDocument Structure
Applies to entities listed under Article 5(1)(c) of Decision A.1138/2020:

Electricity/gas providers (e.g., PPC)

EYDAP

Water sellers (non-therapeutic)

Telecom & subscription TV providers

Toll operators

Credit institutions and Bank of Greece
→ May transmit data via Provider within T+2 days, until 31.12.2025

♻️ Changed

VAT Number Validation Rules: Delivery Notes Documentation

For purpose “Internal Transfer” (Ενδοδιακίνηση):
➤ Recipient's VAT must match issuer's VAT

For purpose “Other Transfers”:
➤ Recipient's VAT may match or differ from issuer's

For the MovePurposeCode field, it is not possible to transmit movement purposes with codes 6, 15, 16, 17, and 18: Delivery Notes Documentation

6 Storage (Φύλαξη)

15 Return from Storage (Επιστροφή από φύλαξη)

16 Recycling (Ανακύκλωση)

17 Destruction of Unusable Materials (Καταστροφή άχρηστου υλικού)

18 Movement of Fixed Assets (Διακίνηση παγίων - Ενδοδιακίνηση)

New coding of vatExemptionCategoryCode VAT & TAX Codes due to amendments introduced by Law 5144/2024 (Value Added Tax Code).

Changelog

02-07-2026 | myDATA v2.0.2 (UAT)#

Added#

1. New Delivery Note Invoices#

2. New JSON fields:#

3. New Code list for receivingNotePurposeCode#

4. New Cancel API /cancelReceivingNote#

5. Portal Cancel button#

19-03-2026 | OAuth 2.0 authentication & Invoice/secure (Encryption)#

1. Αdded a new OAuth 2.0 authentication#

1.1 client_credentials#

1.2 refresh_token#

2. Αdded a new API Request invoice/secure#

17-02-2026 | e-mail as an attachment (customer PDF) & Uniqueness Validation#

02-02-2026 | Delivery Notes and B2G Updates#

1. Delivery Notes#

1.1 Delivery Notes, Updates and Changes#

1.2 New Delivery Note Types of Transfer Documents#

1.3 New Fields for Delivery Note Invoices & Delivery Notes#

1.4 Changes / Deletions#

1.5 New ERP Methods (MyData Delivery Lifecycle)#

2. B2G Invoicing v8.2 | EKAPY#

3. Mass Print-available functionality#

01-12-2025 - Production Version#

22-08-2025 - Production Version#

10-07-2025 - Production Version#

12/06/2025 - UAT Version -> 30/06/2025 Production Version#