Skip to main content

Data flow myDATA Greece

Harald Krondorfer
  • Updated

This article provides an overview of the data flow between the RetailForce fiscalisation service and the myDATA system in Greece.

Systems

Systems involved in the data transmission process:

  • Upstream system – cash register, accounting system, etc.; system connected to the RetailForce Fiscalisation Service.
  • RetailForce middleware – name for the RetailForce Fiscalisation Service (also RetailForce Fiscal Middleware); receives data from the upstream system and processes it in accordance with country-specific regulations/requirements.
  • myDATA provider – myDATA provider authorised by the Greek tax authorities (Independent Authority for Public Revenue – AADE / ΑΑΔΕ); provides communication with the myDATA system.
  • myDATA system – platform developed and provided by the AADE / ΑΑΔΕ for the digitisation of corporate taxes and declarations. Among other things, invoice data must be transmitted digitally to the myDATA platform.

Flowchart

The following BPMN diagram provides an overview of the data flow. Some internal processes within the individual systems or input validations, handshakes, etc. are not shown. An explanation of the diagram can be found below. Please contact us if you require the diagram in a higher resolution.

Process-flow_Greece.png

Flow description

No. System Action Description
1. Upstream system Store transaction The accounting system wants to complete a business transaction.
2. Upstream system Create JSON Payload (Request) A JSON object is generated from the transaction data in accordance with the RetailForce document model (DOM) ("Request (JSON RF-DOM)").
3. Upstream system Submit Request The upstream system sends the request (JSON RF-DOM) to the RetailForce fiscalisation service using the endpoint POST /api/v1/transactions/storeDocument.
4. RetailForce Middleware Validate Request RetailForce middleware validates the request to ensure that it complies with the RetailForce document model and that any special requirements based on the fiscalCountryProperties have been met.
5. RetailForce Middleware Check payload valid?

Payload valid: continue with 8.

Payload invalid: continue with 6.
6. RetailForce Middleware Return validation error If the request is invalid, the RetailForce middleware generates an error message and returns it to the upstream system (fiscalResponse (error)).
7. Upstream system Correct errors The upstream system must correct errors in the payload and retransmit it – continue with 3.
8. RetailForce Middleware Convert data to myDATA provider format The middleware converts the incoming request (request (JSON RF-DOM)) into the format of the myDATA provider and (9.)
9. RetailForce Middleware Forward data to provider ... transmits the converted data to the myDATA provider (myDATA JSON).
10. myDATA Provider Convert to myDATA XML format The myDATA provider system converts the incoming request into the XML format specified by myDATA (myDATA XML).
11. myDATA Provider Weiterleiten an myDATA System The invoice data in myDATA XML format is transmitted to the myDATA system.
12. myDATA System Validate Request The myDATA system validates the incoming request.
13. myDATA System Check payload valid?

Payload valid: continue with 14.

Payload invalid: continue with 18.
14. myDATA System Generate error message and send to provider In the event of an invalid request, the myDATA system generates a corresponding error message (including error code) and returns it to the myDATA provider's system.
15. myDATA Provider Forward error message to RF The myDATA provider forwards the error message to the RetailForce middleware.
16. RetailForce Middleware fiscalResponse (error) from myDATA Generate error message The middleware generates a fiscalResponse (error) from the error message from myDATA and (17.)
17. RetailForce Middleware Return fiscalResponse to upstream system

... gibt diese an das Vorsystem zurück.

Continue with 7.
18. myDATA System Process request data If the request is valid, the myDATA system processes the data and generates the invoice ID data (invoice ID, MARK, etc.).
19a. myDATA System Provide invoice The complete invoice data is made available in the myDATA portal.
19b. myDATA System Return invoice ID data to provider The myDATA system returns the invoice ID data to the provider.
20a. myDATA Provider Provide invoice The complete invoice is available on the provider's website (via a link displayed as a QR code on the corresponding invoice document).
20b. myDATA Provider Forward invoice ID data to RetailForce Furthermore, the provider forwards the invoice ID data to the RetailForce middleware.
21. RetailForce Middleware Create fiscalResponse The RetailForce middleware generates the fiscalResponse from the invoice ID data and the result of internal processing and (22.)
22. RetailForce Middleware Return fiscalResponse ... returns it to the upstream system.
23. Upstream system Generate invoice document The upstream system generates the invoice document (print, digital).
24. Upstream system Provide invoice document After creation, the invoice document is made available to the customer.

 

Related articles

Comments

0 comments

Please sign in to leave a comment.

Powered by Zendesk