eINVOICING
  1. eInvoicing Service
eINVOICING
  • eInvoicing Service
    • About Us
    • What We Offer
    • Changelog
    • On Boarding
    • FAQ (EN)
    • FAQ (GR)
    • eInvoicing Service API
      • API Authentication
        • API Key Authentication
          • /Authentication/login
            POST
        • Bearer Token Authentication
          • Authentication Login Bearer Token
            POST
          • Authentication Refresh
            POST
      • API Endpoints
        • API Validations
        • Sending a Document
          • Sending a Document
          • Mandatory and Optional (Best Practice) Fields Descriptions
          • Mobile Notifications
          • IAPR SIGN POLICY METHODS
          • QR OF THE DOCUMENT
          • Record Type
          • Invoice/json
            POST
          • /Invoice/credit
            POST
        • Purchase Orders for F&B
          • FnB Purchase Orders Documentation
          • Offline QR Code Implementation
          • Retrieve Open Order Documents (FnB)
            GET
        • Document Management
          • Retrieving a document
          • PDF Invoice as an Attachment
        • Alternative Currency Holding
          • ALTERNATIVE CURRENCY (AC)
        • Delivery Notes
          • Delivery Notes Documentation
          • /Invoice/cancelDeliveryNote
            POST
        • POS Integration
          • POS Integration
          • POS 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
          • B2G fields for ERP Configurator 3
          • ΕΓΚΥΚΛΙΟΣ ΠΡΟΣ ΠΑΡΟΧΟΥΣ-ΠΡΟΜΗΘΕΥΤΕΣ ΥΠΗΡΕΣΙΩΝ ΥΓΕΙΑΣ ΓΙΑ ΤΗΝ ΗΛΕΚΤΡΟΝΙΚΗ ΤΙΜΟΛΟΓΗΣΗ
          • /B2GInvoice/ReSeedInvoice
            POST
          • /B2GInvoice/GetLastStatus
            GET
      • 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
          GET
      • 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. eInvoicing Service

On Boarding

To start sending documents using the EINVOICING service, the following procedure should be followed:
1.
A valid VAT number and email address are provided by the client to the EINVOICING team.
2.
Using this VAT number, a demo company is created by the EINVOICING team.
3.
The EINVOICING team creates a demo company that will be used as the issuer in the demo environment and sends the API key to the client, through which the authentication procedure takes place.
4.
The provided email address is used to register a user to the web portal, so that the sent invoices can be reviewed.
5.
The setup is ready.
6.
The final part requires the client’s development department to create the http request payload for their software to start issuing invoices.
💡 Tip:
During the UAT period, make sure to cover all business cases. We strongly suggest you send multiple versions of each invoice that describe your business cases
Modified at 2025-08-28 07:22:47
Previous
Changelog
Next
FAQ (EN)
Built with