eINVOICING
  1. Sending a Document
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
          • Authorization 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
          • Record Type
          • Offline QR Code Implementation
          • Invoice/json
            POST
        • Purchase Orders for F&B
          • FnB Purchase Orders Documentation
          • Offline QR Code Implementation 8.6
          • Retrieve Open Order Documents (FnB)
            GET
        • Document Management
          • Retrieving a document
          • PDF Invoice as an Email Attachment
        • Alternative Currency Holding
          • ALTERNATIVE CURRENCY (AC)
        • Heating Allowance
          • Heating Allowance Requirements
        • Delivery Notes
          • Delivery Notes Documentation
          • Quantitative Receipt Note - 10.1, 10.2
          • Consolidated Delivery Note -9.2
          • /Invoice/cancelDeliveryNote
            POST
        • POS Integration
          • POS Integration
          • POS Offline QR Code Implementation
          • Offline POS Connection Procedure
          • /PosSignatures/{issuerTin}
            POST
          • /PosTransactions/signpos
            POST
        • IRIS Integration
          • IRIS Payments via POS
          • IRIS Payments via Provider
            • Provider IRIS Documentation
            • 1.1 With IRIS via Provider Payment Method
            • /IrisPayments/InitiatePayment
            • /IrisPayments/GetPaymentStatus
        • 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
        • Parallel PDF Viewing (pdfUrl)
        • 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
  • Schemas
    • Sample Schemas
      • Pet
      • Category
      • Tag
    • Schemas
      • AccountPackageResponse
      • ActivationRequest
      • Orientation
      • IrisErrorResponse
      • AdditionalDetails
      • ActivationResponse
      • PdfHtmlOptions
      • IrisPaymentStatusSuccessResponse
      • Address
      • AdditionalFieldDto
      • GetKeysRequest
      • PdfUrlOptions
      • IrisPaymentsRequest
      • AddressType
      • GetTemplateResponse
      • ProblemDetails
      • IrisQrSuccessResponse
      • AllowanceCharge
      • Address2
      • UploadImageRequest
      • AzureFunctionPayload
      • StringStringKeyValuePair
      • PayeeInfo
      • IrisQrSuccessResponseDto
      • AllowanceChargeTypeEnum
      • UploadImageResponse
      • PaymentStatus
      • AuthenticationRequest
      • AddressX
      • YpahesEnum
      • AuthenticationResponse
      • AlcType
      • B2GDetails
      • AlcX
      • B2GInvoiceStatusResponse
      • B2GLastStatusResponse
      • B2GReseedInvoiceRequest
      • Attribute
      • BadRequestResult
      • BadRequestResponse
      • Bank
      • BaseResponse
      • CardLine
      • CashLine
      • ChequeLine
      • Classification
      • CompanyAuthenticationError
      • ContractOrderDetails
      • NullableOfGeoLocation
      • CountryType
      • Bank2
      • CreditInvoiceDto
      • CustomField
      • CurrencyType
      • DeliveryDetails
      • DeliveryNoteCancellationRequest
      • Detail
      • Dienergia
      • DistributionDetails
      • Classification2
      • DocumentStatusEnum
      • EcrTokenType
      • CoreDoc
      • FieldType
      • EliseCoreDocument
      • FnBDocumentResponse
      • EliseCoreReceipt
      • CountryX
      • GeoLocation
      • EntityType
      • ExpensesClassification
      • ExpensesClassificationCategory
      • ExpensesClassificationType
      • DeliveryDetails2
      • IAPRSignPolicyEnum
      • PackingDeclaration
      • IaprError
      • IaprTaxType
      • IncomeClassification
      • PosPaymentsRequestDto
      • PaymentMethodMetaData
      • IncomeClassificationCategory
      • PosPaymentsResponseDto
      • IncomeClassificationType
      • PaymentUpdate
      • Int32StringKeyValuePair
      • Invoice
      • Entity
      • InvoiceHeader
      • Entity2
      • PosSignaturesRequestDto
      • InvoiceLine
      • InvoiceSummary
      • InvoiceType
      • InvoicesEnvelope
      • MiscellaneousData
      • HeaderX
      • NspCode
      • OtherDeliveryNoteHeaderType
      • IFormFile
      • Party
      • PartyType
      • PaymentDetails
      • PaymentMethod
      • PaymentMethodType
      • PaymentTerm
      • ProviderSignatureType
      • RecordTypeEnum
      • RefreshToken
      • RemittanceLine
      • Response
      • ResponseEnvelope
      • KeyValuePairOfintAndstring
      • ShipType
      • LineX
      • SignatureDurationTypeCodes
      • SignaturePlaygroundData
      • MorfotyposDetailsDto
      • SignaturePlaygroundResponse
      • MyDataClassification
      • SignatureResponse
      • MyDataConnectPayload
      • SignedData
      • MyDataDirection
      • SigningDataRequestModel
      • NullableOfAddressX
      • SigningECCKeyPair
      • NullableOfB2GDetailsX
      • SpecialInvoiceType
      • NullableOfCountryX
      • StringStringValueTuple
      • NullableOfCurrencyX
      • Summaries
      • NullableOfDeliveryDetail
      • Tax
      • NullableOfDeliveryDetail2
      • TransmissionFailureEnum
      • NullableOfDistributionDetailsX
      • TransmissionFailureType
      • NullableOfPaymentDetailsX
      • TransportDetail
      • NullableOfValueTupleOfstringAndstring
      • UpdatePaymentMethodRequest
      • UsedSignature
      • ValidateProviderSignatureResponse
      • Party2
      • Vat
      • Party3
      • VesselDetails
      • VoucherLine
      • PartyType2
      • XmlSerializerNamespaces
      • PaymentMethod2
      • PaymentMethodMd
      • PaymentTermX
      • ProviderInfo
      • ReceptionEmailsType
      • ReceptionProvider
      • RefreshTokenDto
      • SummaryX
      • SynopsiClassificationsDto
      • SynopsiDetailsDto
      • TaxTotalDto
      • UblAllowancesCharge
      • UblInvoiceDocumentReferenceType
      • VatX
  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.
If you include AccountingDepartmentEmails in the JSON payload and leave the SendMethod field empty, the service will send the email by default. If you do not want the email to be sent, you must set the SendMethod field to "A". Additionally, we no longer accept SendMethod as a URL parameter — it must now be provided exclusively within the JSON payload.
Modified at 2025-12-10 11:54:16
Previous
Mandatory and Optional (Best Practice) Fields Descriptions
Next
IAPR SIGN POLICY METHODS
Built with