Skip to main content
Download OpenAPI

Receipt lifecycle

lifecycle.png

new​

  1. The document is sent via REST API specifying all the necessary data in a JSON document. The A-Cube platform will manage the life cycle of the document ensuring delivery if the provided data is correct.

  2. A-Cube Platform will perform a pre-validation before sending the document to the Tax Authority web portal. In case of errors you will synchronously receive a 400 response with the error details.

  3. Once the JSON document is received via API, the A-Cube platform marks the receipt as new and it is signed using the ECDSA_SHA_512 digest algorithm to guarantee the integrity of the data. The client immediately receives a unique identifier for the document in response.

submitted and ready​

  1. At the same time, a process will start in the background managing communication with the Tax Authority web portal. After successfully communicating the document, it will be marked as submitted.

  2. Right after the document is submitted, A-Cube will generate the PDF version of the receipt. Once this job is done, the receipt will be set as ready for download and a message will be sent via webhook to your software systems for the receipt event.

retry and failed​

  1. If there is a communication problem with the Tax Authority web portal, the document will be marked as retry, placed in a waiting queue, and re-sent after a predetermined interval. Each new attempt is notified via webhook with the receipt-retry event. Once the sending is completed, the document will be set to submitted.

  2. The causes of failure to communicate may include incorrect or expired credentials or the unavailability of the Revenue Agency portal. There is no maximum number of attempts: the document is re-sent until 11:58 PM (Italian time) on the day it was acquired. If it is not possible to send the document successfully by then, the document will be marked as failed.

  3. If the Tax Authority web portal rejects the message due to a data error, the document is not re-sent and is marked as failed immediately.

In both cases, immediate communication will be sent via webhook to your software systems with the receipt-error event.

For a list of possible error codes, see the receipt-error event.

Last updated on