eINVOICING
  1. Sending a Document
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
            POST
          • Invoice/credit
            POST
        • 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}
          • /Receipt
          • /PosTransactions/signpos
        • 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. Sending a Document

Mobile Notifications

When sending an invoice to a customer’s mobile device, there are two available methods, determined by the value set in the TransmissionMethod field:
1.
M (Mobile only):The invoice will be sent to the recipient via Viber. If the recipient does not have Viber, a fallback SMS will be sent after a short period.
2.
C (Email + Mobile): The invoice will be sent to both the customer’s email and Viber. If Viber is not available, a fallback SMS will be sent instead.
To enable invoice delivery via Viber/SMS, you must populate the "CustomerCellNumbers" field with the customer’s mobile number.
💡
Supported Phone Number Format:
Phone numbers must be in international format.
Greek numbers should start with +30 or 69, followed by the 10-digit mobile number (e.g., +30
6912345678).
Landline numbers are not supported for SMS and Viber messaging.
Do not include spaces, dashes, or special characters (e.g., +306912345678 is correct, while +30-691-234-5678 is incorrect).
Important Note 1: When sending an invoice to a mobile device, attachments are not supported.
Important Note 2: SMS and Viber messaging are only supported within Greece (SMS messaging
will soon be supported for international numbers, while Viber messaging will be available in both
Greece and Cyprus)
Note: When sending an invoice to a mobile device, attachments are not supported.
Example Object:
json
ΑντιγραφήΕπεξεργασία
"AdditionalDetails": {
    "AccountingDepartmentEmails": [
        "test@email.gr", "test1@email.com"
    ],
    "TransmissionMethod": "C", // C: email + mobile, M: mobile only, E: email only
    "AvoidEmailGrouping": false,
    "SendAsPdf": false,
    "PdfNotificationEmails": [
        "test@email.gr"
    ],
    "CustomerCellNumbers": [
        "69000000xx"
    ]
}
This ensures that the invoice is delivered according to the selected method while maintaining proper fallback mechanisms for reliable delivery.
Modified at 2025-05-21 12:36:14
Previous
Mandatory Fields B2C, B2B
Next
IAPR SIGN POLICY METHODS
Built with