- Electronic invoice
Indicators on invoices in e.FACT (June 2024)
As we already announced in the month of June'24, the e-FACT service of the AOC Consortium will eliminate the receipt of invoices via FTP/sFTP from theOctober 1, 2025. The Public Administrations (AAPP) will have to adopt the new integration mechanism through REST API to guarantee continuity in the receipt of electronic invoices.
A REST API (Representational State Transfer) is a type of architecture for designing web services that allows communication between systems through the HTTP protocol. It is particularly popular because it is lightweight, easy to understand and scalable. It is an interface that connects applications or services efficiently, using simple web standards.
Who does this change affect?
This change it only affects Public Administrations who receive invoices through the e-FACT service via FTP/sFTP. The entities that manage invoice statements fromEACAT will not be affected for this migration.
The AAPPs affected must:
- Implement the integration mechanism via REST API
- Make sure your technology providers make the necessary adaptations to abandon FTP/sFTP.
Options available until deadline
- Receipt of invoices via REST API (mandatory method from October 2025):
- AAPPs can request integration via REST API filling the eFACT integration request form.
- The whole technical documentation is available on the GitHub of the AOC Consortium.
2. Receipt of invoices via FTP/sFTP (until September 2025):
- Currently available, but this service will stop working on the 1st of October 2025.
What should Public Administrations do?
- Start integration via REST API:
It is essential to start the process as soon as possible to ensure that the receipt of invoices is not affected. Integration can now be requested via REST API filling the e-FACT integration request form and sending it through the e-FACT support form with the subject «Migration API REST». Once the request is received we will provide you with the connection token to carry out the integration tests in the test environment. - Coordinate with the technology provider:
Communicate this change to your technology provider and make sure they use the technical documentation as a guide to implement the new system. Once the tests are completed in the test environment, the final production environment token, and the system will be fully operational.
Support and technical documentation
The AOC Consortium puts at your disposal:
- La technical documentation on GitHub.
- El technical support, which will accompany you throughout the process.