The e-FACT service of the AOC Consortium will eliminate the receipt of invoices via FTP/sFTP from October 1, 2025 . The Public Administrations (AAPP) will have to adopt the new integration mechanism through the 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 only affects Public Administrations that receive invoices through the e-FACT service via FTP/sFTP . Entities that manage invoice statements from EACAT will not be affected by this migration.
The AAPPs affected must:
- Implement the integration mechanism via REST API.
- Ensure that your technology providers make the necessary adaptations to move away from FTP/sFTP.
Options available until deadline
- Receipt of invoices via REST API (mandatory method from September 2025):
- AAPPs can request integration via the REST API by filling out the integration request form at eFACT .
- All the 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 October 1, 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 via REST API can now be requested by filling out the integration request form at e-FACT and sending it via thee-FACT support form with the subject "Migration API REST". Once the request is received we will provide you with the connection token to perform the integration tests in the test environment. - Coordinate with the technology provider:
Communicate this change to your technology provider and ensure they use the technical documentation as a guide to implement the new system. After testing in the test environment, the final production environment token will be issued, and the system will be fully operational.
Support and technical documentation
The AOC Consortium puts at your disposal:
- Technical documentation on GitHub.
- Technical support , which will accompany you throughout the process.