eINVOICING
  1. POS Integration
eINVOICING
  • eInvoicing Service
    • About Us
    • What We Offer
    • FAQ
    • Changelog
    • On Boarding
    • eInvoicing Service API
      • API Authentication
        • API Key Authentication
          • /Authentication/login
        • Bearer Token Authentication
          • Authentication Login Bearer Token
          • Authentication Refresh
      • API Endpoints
        • API Validations
        • Sending a Document
          • Sending a Document
          • Mandatory Fields B2C, B2B
          • Mobile Notifications
          • IAPR SIGN POLICY METHODS
          • QR OF THE DOCUMENT
          • einvoice/json
          • Invoice/credit
        • Purchase Orders for F&B
          • FnB Purchase Orders Documentation
          • Offline QR Code Implementation
          • Retrieve Open Order Documents (FnB)
        • Document Management
          • Retrieving a document
          • PDF Invoice Attachment
        • Alternative Currency Holding
          • ALTERNATIVE CURRENCY (AC)
        • Delivery Notes
          • Delivery Notes Documentation
          • /Invoice/cancelDeliveryNote
        • POS Integration
          • POS Integration
          • Offline QR Code Implementation
          • /PosSignatures/{issuerTin}
            POST
          • /Receipt
            POST
          • /PosTransactions/signpos
            POST
        • Delayed POS Payment
          • Delayed POS Payment
        • B2G Documents
          • B2G Documents
          • B2G Mandatory Fields
          • B2G Status response
          • B2G Soft Reject
          • RESEED INVOICE
          • ΕΓΚΥΚΛΙΟΣ ΠΡΟΣ ΠΑΡΟΧΟΥΣ-ΠΡΟΜΗΘΕΥΤΕΣ ΥΠΗΡΕΣΙΩΝ ΥΓΕΙΑΣ ΓΙΑ ΤΗΝ ΗΛΕΚΤΡΟΝΙΚΗ ΤΙΜΟΛΟΓΗΣΗ
          • BT-10 BuyerReference
          • /B2GInvoice/ReSeedInvoice
          • /B2GInvoice/GetLastStatus
      • JSON Structures & Payloads
        • EliseCoreDocument Structure
          • EliseCoreDocument Structure
        • Minimum & Conditional Fields
          • Minimum & Conditional Fields
        • Response Examples & Error Handling
          • Response Examples & Error Handling
      • Offline QR Code
        • Offline QR Code Instructions
      • Status MyData
        • MyData/status
      • Extra Functionalities
        • Archiver
          • Archiver Functionality
      • Terminology
        • Document Type Codes
        • VAT & TAX Codes
        • Country & Currency Codes
        • Measurement Unit Codes (IAPR & EN16931)
        • Self-Billing Remarks (IAPR)
        • Classification & Payment Method Codes (IAPR)
        • Special Invoice Category
      • VAT Validation
        • Greek VAT Check
        • EU VAT Check
      • Attachments
        • Attaching Media & PDFs
        • Invoice Document Upload (Invoice/File)
      • SOFTONE ERP Related Segments
        • SOFTONE Configurator
          • SOFTONE Configurator - B2G Mapping
    • eInvoicing Portal
      • Template Configuration (Default Template)
      • Single Sign-On (SSO)
        • Single Sign-on (SSO) Setup Instructions
        • Single Sign-On (SSO)
    • WIKI JSON Samples
      • 1.1 B2B
      • 1.3 B2B Sales Invoice Third Country
      • 5.2 B2B Credit Invoice Non-Associated
      • 2.1 B2B Service Rendered Invoice
      • 1.1 Debit B2G
      • 11.1 B2C Retail Sales Receipt
      • 11.4 Retail Sales Credit Note
  1. POS Integration

Offline QR Code Implementation

The Offline QR Code feature has been implemented for myDATA document types 8.4, 8.5.
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 for 8.4:
https://einvoice-demo-portal.s1ecos.gr/TransmissionFailure?issuerTin=EL135952929&customerTin=EL000000000&customerName=&invoiceType=8.4&series=A&number=2&dateIssued=20250626143059&totalAmount=100&totalNetAmount=100&totalVatAmount=0&internalId=ZBC&signature=76559ddb81445a69656b66d11769328a5c7cbaa3
Example of URL for 8.5:
https://einvoice-demo-portal.s1ecos.gr/TransmissionFailure?issuerTin=EL135952929&customerTin=EL000000000&customerName=&invoiceType=8.5&series=A&number=3&dateIssued=20250626143059&totalAmount=200&totalNetAmount=200&totalVatAmount=0&internalId=ZBC1&signature=d0ec9f1ecaf15b967e89c10551b28c8f0836123d
The previous example URLs 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 ofline
documents applies exclusively to provider-issued documents
Modified at 2025-06-26 10:17:28
Previous
POS Integration
Next
/PosSignatures/{issuerTin}
Built with