Offline QR Code Implementation

This functionality ensures accessibility to document summaries even in offline scenarios, enhancing compliance and operational efficiency.

Below you can find the algorithm needed for implementation.

💡

SoftOne Provider:
Demo: https://einvoice-demo-portal.s1ecos.gr/
Production: https://einvoice.s1ecos.gr/

IMPACT Provider:
Demo: https://einvoiceportaluat.impact.gr
Production: https://einvoice.impact.gr

A QR code must be generated by forming the following algorithm:

{portalUrl}/TransmissionFailure with the following parameters (as query parameters):
• IssuerTin is the VAT number of the issuer, including the country code prefix, i.e.,
EL111222333.
• CustomerTin is the VAT number of the counterparty, including the counterparty code
prefix, i.e., EL333222111. In the case of B2C, where the VAT is unknown, you must
leave it blank.
• CustomerName is the name of the counterparty, i.e., Demo Company.
• InvoiceType is the invoice type code according to IAPR (ie 1.2).
• Series is the fiscal series of the document, i.e., ΤΔΑ.
• Number is the fiscal number of the document, i.e., 60.
• DateIssued is the date the document is issued in the following format:
yyyyMMddHHmmss, i.e., 20221231143059.
• TotalAmount is the total amount of the invoice, i.e., 100.50.
• TotalNetAmount isthe total net amount of the invoice, i.e. 80.50
• TotalVatAmount is the total vat amount of the invoice, i.e., 24.58.
• InternalId is the unique internal document ID, the identifier of the document. The
same value is sent when posting the document in the
DistributionDetails.InternalDocumentId field.
• dateTransmitted is the date the document was transmitted to IAPR myDATA.
(Optional)
• Signature is a unique string produced by the following algorithm:

The signature is generated by the following algorithm:
Produce the following string: {issuerTin}-{customerTin}-{series}-{number}-{dateIssued}-{totalAmount}-{internalId}{APIKey}

The values of the variables are identical to those mentioned above

i.e.: EL118058830-EL987654321-ΤΔΑ-123-20231010162042-124-1.2_ΤΔΑ_1230383223f-06ff4e7c-bd36-29a1acdb41b0

Convert to UTF8 byte array.

Hash the byte array using the SHA1 algorithm

The signature is the generated byte array as a hexadecimal string (without delimiter)
i.e.: 92fea653224fd17d9b92a209f2cc9aacd300130f

Example of URL:

https://einvoice-demo-portal.s1ecos.gr/TransmissionFailure?issuerTin=EL135952929&customerTin=EL000000000&customerName=&invoiceType=8.6&series=A&number=4&dateIssued=20250626143059&totalAmount=200&totalNetAmount=200&totalVatAmount=0&internalId=ZBC2&signature=bc90801a2ec4f57f8a27e1068b65f2864b706393

The previous example URL leads to the page displayed until the document is sent.

Note: The offline QR code is officially supported only for the provider. While it is technically supported for ERP e-invoice or documents that do not update MyData, the legalization of offline
documents applies exclusively to provider-issued documents.