eINVOICING
  1. B2G Documents
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}
          • /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
            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
      • 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. B2G Documents

B2G Soft Reject

1. Introduction#


If a Contracting Authority identifies errors in the completion of invoice fields that are not part of the mandatory content of the invoice as defined in Article 9 of Law 4308/2014 (Joint Ministerial Decision), it may reject the invoice with the option for "resubmission by the Supplier."
In this NEW rejection message, the Contracting Authority specifies the fields that were incorrectly completed. The invoice is resubmitted by the Supplier without being assigned a new MARK.
The Supplier is allowed to modify ONLY the following fields (one or more, or even make no changes in case of miscommunication or accidental rejection):

Field NameField Description
BT-10 buyerReferenceBuyer Reference Element
BT-11 projectReferenceIdReference Element for Goods/Services/Study/Project
BT-12 contractReferenceIdContract Reference Element
BT-13 purchaseOrderReferencePurchase Order Reference Element
BT-46 buyerPartyIdContracting Authority Code

The SoftReject message can only be sent when the invoice is in status 1 or 7 (Received by IT or Under Dispute)
Resubmitting the invoice initiates a new cycle of invoice statuses (Status 0, 1, etc.).
The Seller/Provider cannot issue a credit note when the related debit note is in status -50 (SoftReject sent – awaiting resubmission of the invoice). If the Seller still wishes to issue a credit note, they must first resubmit the debit note and then immediately issue the credit note.
The Seller/Provider may receive a Rejection (RE) for an invoice previously subjected to SoftReject without waiting for any further response. (This includes cases where the Contracting Authority mistakenly sent a SoftReject instead of an RE. The sending of an RE should occur after coordination with the Seller).

When the Contracting Authority sends a rejection message for resubmission with corrections to the permissible fields, the following indicative message appears in the document's action history:
image.png

Instructions on how to use SOFT REJECT via the Production Portal#


1.
Navigate to "Outgoing Invoices" and select "View" for the invoice in question.
Then, click on the relevant icon to view the B2G details of the invoice, which you can update.
image.png

2.
Make the necessary corrections and select "Send" to resubmit the invoice with the required updates.
image.png

In the case where the changes are successful, the Contracting Authority will accept the document, and a "Received by IT" message will be generated.
In case incorrect data is resubmitted, the Contracting Authority will issue a new rejection message, granting the right to resubmit, along with updated instructions in the rejection message.
Once resubmitted with the corrected B2G fields, the updated details can only be viewed in the "Action History" of the invoice.

Additional Information on B2G Fields#

Contracting Authority Code (BT-46):
This field is mandatory and should be completed using the unique number of the Contracting Authority, which can be found at the following link: https://webapps.gsis.gr/dsae2/foreisreg/faces/pages/mainmenu/entrance.xhtml;jsessionid=_lNlbYy9QXPTFBGQOb5phpiABFTMGs9PSWMlnJOa4radBOlJ3jGE!-1827188021
Project Reference (BT-11):
This field follows the format "a|b," where:
The first component (a) represents the funding source:
(1|) Regular Budget
(2|) Public Investment Program (PIP)
(3|) General Government Body Budget
The second component (b) is determined as follows:
"1|ADA" (Public Posting Number): For Central Administration bodies with expenses charged to the Regular Budget, include "1," the separator "|," and the Public Posting Number (ADA).
"2|Encoded Project Code": For other General - Government Bodies or expenses solely from the PIP Budget, include "2," the separator "|," and the Project Code.
"3|ADA": For expenses from the General Government Body Budget, include "3," the separator "|," and the Public Posting Number (ADA).
If no contract exists, use one of the following values: "1|0," "2|0," or "3|0."
Contract Document Reference (BT-12): This field should be filled with the contract reference. If no contract exists, use the value "0.
Modified at 2025-03-19 15:21:30
Previous
B2G Status response
Next
RESEED INVOICE
Built with