Focus
APIs for sending receipts to the Revenue Agency in 2026: operating models and API solutions
API for sending receipts to the Revenue Agency in 2026: the regulatory and technical framework
How to send receipts without a physical telematic cash register: the role of certified APIs
Electronic receipts 2026: how to avoid compliance errors with sending APIs
Designing receipt sending in 2026 with an API-first approach
API for sending receipts to the Revenue Agency in 2026: the regulatory and technical framework
The APIs for sending receipts to the Revenue Agency are now the most effective solution for managing the transmission of tax data in a compliant and automated way. Until recently, the only way to transmit receipts to the Revenue Agency was the use of certified physical devices. Today, however, it is also possible via certified software and API integrations; this makes it possible to reduce hardware dependence and improve traceability, automation and control. The option of sending receipts to the Revenue Agency without a telematic cash register also opens up new opportunities for those who need to comply with the rules.
Since 1 January this year, the operating model based on the two certified software modules PEM (Point of Emission) and PEL (Point of Processing) has come into force. The new obligation affects all entities carrying out retail sales or similar activities. In short: a physical telematic cash register is no longer sufficient, but a system is required that enables the electronic sending of receipts in accordance with the rules of the Revenue Agency.
The new solutions must:
generate and digitally sign the commercial document;
synchronise data in real time with the PEL module;
transmit receipts according to official protocols;
ensure compliant digital preservation.
This translates, for retail businesses and multi-store chains such as beauty salons and hairdressers, into the ability to overcome hardware constraints and rely on truly scalable and secure tax flows.
BOX - In-depth regulatory note: Legislative Decree 127/2015
The obligation to store and transmit daily receipts was introduced by Legislative Decree 127/2015. Subsequent measures by the Revenue Agency then clarified the technical specifications and introduced the possibility of using certified software instead of traditional telematic cash registers.
Sending receipts to the Revenue Agency: from the physical telematic cash register to certified software solutions
Telematic cash register, middleware and APIs: operational differences and limitations
According to the 2026 POS Revenue Agency regulations, businesses can choose from three different operational approaches. The first involves using the traditional telematic cash register, which, however, entails significant hardware constraints. Although it allows tax data to be sent via the Revenue Agency's interchange system in a compliant manner, it is overall not very flexible, especially in digitalised businesses, those with multiple locations or high volumes.
Some opt for enterprise middleware, i.e. software that connects telematic cash registers to management systems (such as ERP, CRM, databases) to simplify the collection and organisation of data. These solutions improve internal integration but do not solve the problem of dependence on physical devices. This is therefore still a complex and costly system to maintain.
The third and most advanced alternative is the adoption of APIs for sending receipts to the Revenue Agency, which allow fully digital management of the flow. Those who adopt this model can transmit receipts without a telematic cash register. With APIs, it is also possible to operate fully in line with the technical specifications and completely automate processes, from the generation to the preservation of the commercial document. In the next paragraphs we will see how API telematic receipt sending works.
BOX - Electronic receipts 2026: real-time, near real-time and batch
In addition to the technical obligations, 2026 also brings a substantial change in the methods and timing of electronic receipt transmission.
Real time: data are generated, signed and sent instantly. Ideal for cloud POS, digital payments and high-traffic environments that require immediate traceability.
Near real time: transmission within a few minutes or at the end of the transaction, useful for light synchronisations or environments with intermittent connectivity.
Batch: periodic sending (for example at the end of the day) of blocks of receipts. A less suitable solution for the new regulatory model, at risk of delays and lack of granularity.
The A-Cube approach with certified PEM/PEL APIs is designed to support both real time and near real time, ensuring compliance, traceability and seamless integration with modern systems.
How to send receipts without a physical telematic cash register: the role of certified APIs
From a regulatory perspective, the obligation to have a system that performs the functions of the telematic cash register remains, but it does not necessarily coincide with a physical device. Already today, in specific contexts and according to clarifications provided in Revenue Agency rulings, it is possible to automate the sending of receipts via accredited software solutions and API integrations, provided they comply with the technical specifications and control requirements. With the regulation expected during 2026, this model will be formalised and made explicit, definitively overcoming the association between tax obligation and physical hardware.
The solution designed by A-Cube is based precisely on this approach. It is called Scontrino Elettronico Smart, the API-first platform designed to integrate with POS, software and ERP systems in use. It allows sending receipts to the Revenue Agency without a telematic cash register, digitally signing each document and managing transmission and preservation in real time.
The entire process is automated and minimises manual intervention and the risk of errors and oversights. The platform allows the use of dedicated webhooks for every relevant event such as success, errors, cancellations or re-sends. This makes constant monitoring and real-time alignment with cash register systems, document flows and payment platforms possible.
From an infrastructure point of view, the API for sending receipts to the Revenue Agency designed by A-Cube is intended to be highly scalable: it can manage both single points of sale and complex distributed networks without changing the underlying architecture. Native integration with Stripe also makes it possible to automate the fiscalisation of digital transactions, connecting the payment directly to the issuing of the commercial document.
This architecture makes the solution fully compatible with the 2026 POS Revenue Agency model and is designed to support multichannel businesses, high-volume platforms and digital environments in continuous evolution. It also allows you to avoid penalties prescribed for those who do not comply with the rules on electronic receipts 2026.
BOX - Fixed telematic cash register vs. A-Cube APIs
Fixed telematic cash register
It is a certified hardware device that stores and sends data to the Revenue Agency. It is a compliant solution but requires physical installation, maintenance and updates that are often complex and not well suited to digital environments.
A-Cube APIs
It is based on a certified API architecture that enables receipts to be sent to the Revenue Agency without a telematic cash register. Receipts are generated, signed and transmitted via APIs directly from POS systems, management software or payment platforms. It ensures greater flexibility, scalability and native integration with the company's digital ecosystem.
Electronic receipts 2026: how to avoid compliance errors with sending APIs
Using an API for sending receipts to the Revenue Agency makes it possible to automate numerous activities related to the daily transmission of data. This is where the added value of the A-Cube solution with the API telematic receipt sending comes in. The platform is designed to prevent possible problems before they happen thanks to a design oriented towards automatic compliance, operational stability and sending receipts to the Revenue Agency without a telematic cash register.
One of the critical aspects of sending electronic receipts in 2026 is the need for a qualified digital signature. Each document must be signed in accordance with the technical specifications of the PEM module. The A-Cube API automates this step, ensuring that each commercial document is intact, authenticated and ready for transmission.
Compliant digital preservation is also a point often underestimated. It is not enough to send the documents: they must be archived according to the rules of Legislative Decree 127/2015, with controlled and traceable access over time. Scontrino Elettronico Smart integrates a legally valid preservation system that ensures the availability of documents over time.
A further risk concerns compliance with the Revenue Agency's technical specifications, which may change over time. The A-Cube API solution is constantly updated to maintain full compliance with the latest regulations, avoiding the need for manual updates by integrators.
Finally, handling unforeseen issues is also crucial: network interruptions, system errors or incomplete data can block the fiscal flow. Thanks to a system of intelligent webhooks, the sending of receipts via API is always monitored and traceable, with the possibility of intervening promptly in the event of problems.
Designing receipt sending in 2026 with an API-first approach
The obligation to send electronic receipts 2026 is not just a necessary adjustment. It is also an opportunity to simplify, digitise and automate your fiscal architecture. Adopting an API for sending receipts to the Revenue Agency makes it possible to overcome process fragmentation and design natively compliant solutions. Our platform is scalable and compliant, easy to install and use. The simplest solution for carrying out receipt sending to the Revenue Agency without a telematic cash register.
Want to test the API or receive support for integration? Write to info@acubeapi.com or visit www.acubeapi.com to discover our API-centric document solutions.
