1. Delivery Notes
eINVOICING
  • eInvoicing Service
    • About Us
    • What We Offer
    • Changelog
    • On Boarding
    • FAQ (EN)
    • FAQ (GR)
    • eInvoicing Service API
      • API Authentication
        • Bearer Token Authentication (JWT)
          • Authentication Login Bearer Token
            POST
          • Authorization Refresh
            POST
        • OAuth 2.0 Authentication
          • Oauth 2.0 Client Credentials Token
            POST
          • Oauth 2.0 Refresh Token
            POST
      • API Endpoints
        • API Validations
        • Sending a Document
          • Sending a Document
          • Mandatory and Optional (Best Practice) Fields Descriptions
          • Customer Notifications
          • IAPR SIGN POLICY METHODS
          • Record Type
          • Invoice/json
            POST
          • Invoice/secure
            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
          • Q&A
          • /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
          • ΕΓΚΥΚΛΙΟΣ ΠΡΟΣ ΠΑΡΟΧΟΥΣ-ΠΡΟΜΗΘΕΥΤΕΣ ΥΠΗΡΕΣΙΩΝ ΥΓΕΙΑΣ ΓΙΑ ΤΗΝ ΗΛΕΚΤΡΟΝΙΚΗ ΤΙΜΟΛΟΓΗΣΗ
          • B2G Invoicing v8.2 | EKAPY
          • /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 PDF Upload (Invoice/File)
          POST
      • Other ERP Related Segments
        • Elise - WDC Translator
        • 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
      • ActivationRequest
      • Orientation
      • IrisErrorResponse
      • ActivationResponse
      • PdfHtmlOptions
      • IrisPaymentStatusSuccessResponse
      • AdditionalFieldDto
      • GetKeysRequest
      • PdfUrlOptions
      • IrisPaymentsRequest
      • AddressType
      • GetTemplateResponse
      • ProblemDetails
      • IrisQrSuccessResponse
      • Address2
      • UploadImageRequest
      • AzureFunctionPayload
      • StringStringKeyValuePair
      • PayeeInfo
      • IrisQrSuccessResponseDto
      • UploadImageResponse
      • PaymentStatus
      • AddressX
      • YpahesEnum
      • AlcType
      • AlcX
      • B2GInvoiceStatusResponse
      • Attribute
      • NullableOfGeoLocation
      • CountryType
      • Bank2
      • CurrencyType
      • Dienergia
      • Classification2
      • EcrTokenType
      • CoreDoc
      • CountryX
      • EntityType
      • ExpensesClassification
      • ExpensesClassificationCategory
      • ExpensesClassificationType
      • DeliveryDetails2
      • IaprError
      • IaprTaxType
      • IncomeClassification
      • IncomeClassificationCategory
      • IncomeClassificationType
      • Invoice
      • Entity
      • InvoiceHeader
      • Entity2
      • InvoiceLine
      • InvoiceSummary
      • InvoiceType
      • InvoicesEnvelope
      • HeaderX
      • NspCode
      • OtherDeliveryNoteHeaderType
      • IFormFile
      • PartyType
      • PaymentMethodType
      • ProviderSignatureType
      • RefreshToken
      • Response
      • ResponseEnvelope
      • KeyValuePairOfintAndstring
      • LineX
      • SignatureDurationTypeCodes
      • SignaturePlaygroundData
      • MorfotyposDetailsDto
      • SignaturePlaygroundResponse
      • MyDataClassification
      • MyDataConnectPayload
      • SignedData
      • MyDataDirection
      • SigningDataRequestModel
      • NullableOfAddressX
      • SigningECCKeyPair
      • NullableOfB2GDetailsX
      • SpecialInvoiceType
      • NullableOfCountryX
      • StringStringValueTuple
      • NullableOfCurrencyX
      • NullableOfDeliveryDetail
      • NullableOfDeliveryDetail2
      • NullableOfDistributionDetailsX
      • TransmissionFailureType
      • NullableOfPaymentDetailsX
      • TransportDetail
      • NullableOfValueTupleOfstringAndstring
      • UsedSignature
      • ValidateProviderSignatureResponse
      • Party2
      • Party3
      • PartyType2
      • XmlSerializerNamespaces
      • PaymentMethod2
      • PaymentMethodMd
      • PaymentTermX
      • ProviderInfo
      • ReceptionEmailsType
      • ReceptionProvider
      • SummaryX
      • SynopsiClassificationsDto
      • SynopsiDetailsDto
      • TaxTotalDto
      • UblAllowancesCharge
      • UblInvoiceDocumentReferenceType
      • VatX
    • AccountPackageResponse
    • AdditionalDetails
    • Address
    • AllowanceCharge
    • AllowanceChargeTypeEnum
    • AuthenticationRequest
    • AuthenticationResponse
    • B2GDetails
    • B2GLastStatusResponse
    • B2GReseedInvoiceRequest
    • BadRequestResult
    • BadRequestResponse
    • Bank
    • BaseResponse
    • CardLine
    • CashLine
    • ChequeLine
    • Classification
    • CompanyAuthenticationError
    • ContractOrderDetails
    • CreditInvoiceDto
    • CustomField
    • DeliveryDetails
    • DeliveryNoteCancellationRequest
    • Detail
    • DistributionDetails
    • DocumentStatusEnum
    • FieldType
    • EliseCoreDocument
    • FnBDocumentResponse
    • EliseCoreReceipt
    • GeoLocation
    • IAPRSignPolicyEnum
    • PackingDeclaration
    • PosPaymentsRequestDto
    • PaymentMethodMetaData
    • PosPaymentsResponseDto
    • PaymentUpdate
    • Int32StringKeyValuePair
    • PosSignaturesRequestDto
    • MiscellaneousData
    • Party
    • PaymentDetails
    • PaymentMethod
    • PaymentTerm
    • RecordTypeEnum
    • RemittanceLine
    • ShipType
    • SignatureResponse
    • Summaries
    • Tax
    • TransmissionFailureEnum
    • UpdatePaymentMethodRequest
    • Vat
    • VesselDetails
    • VoucherLine
    • RefreshTokenDto
  1. Delivery Notes

Q&A

1. When is the correlation using the field multipleConnectedMarks used?
👉 The correlation of value documents is performed with all related value and/or movement documents (either type 9. or 10.) using the multipleConnectedMarks method.
2. When is the correlation using the correlatedInvoice used?
3. How should cases of shortages and surpluses be managed?
4. When can the Third-Party Receiver (3PL warehouse operator) issue a reverse delivery note?
👉 The Third-Party Receiver (3PL warehouse operator), upon instruction from the Receiver, may issue a reverse 9.3 delivery note.
5. How do I handle cases where I want to transport products for an exhibition?
👉 1st Alternative (when no inventory is sold at the exhibition venue):
Issue a Movement Document by the Sender, with the issuer’s VAT number as their own, the recipient’s VAT number also as their own (purpose of movement: 'Other Movements_[Exhibition]') or zeros (purpose of movement: 'Exhibition'), and the completion address of the movement outside the recipient’s premises.
Upon return, issue a Movement Document (ΨΔΑ) marked as 'reverse', with the issuer’s VAT number as their own, the recipient’s VAT number as their own or zeros, and the starting address of the movement outside the issuer’s premises.
👉 2nd Alternative:
Issue a Consolidated Movement Document by the Sender, with the issuer’s VAT number as their own and the recipient’s VAT number as zeros. For each delivery, issue a Delivery Note (9.1), and for returned goods issue a Goods Return Note (10.), referencing the related Consolidated Movement Document (9.2)."
6. Triangular transactions, in cases where there is more than one additional related VAT number.
👉 For triangular transactions, in cases where there is more than one additional related VAT number, the responsibility for reporting shortages/surpluses lies with the recipient of the inventory (the entity at whose premises the inventory was received).
7. Issuance of the reverse 9.3 delivery note.
👉 The issuance of a 9.3 Delivery Note marked as 'reverse' by a Third-Party Receiver acting on behalf of the Recipient is acceptable.
👉 The responsibility for reporting shortages/surpluses lies with the final Recipient of the inventory (the entity at whose premises the inventory was received).
8. Invoices Correlation
👉 The correlation of sales delivery invoices with value documents is carried out for those that result in a sale, as can be determined at a minimum from the relevant purposes of movement.
Modified at 2026-04-17 13:44:29
Previous
Quantitative Receipt Note - 10.1, 10.2
Next
/Invoice/cancelDeliveryNote
Built with